> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/api-documentation/api-guides/configuration/unit-handling-service.md). # Unit Handling Service Defines and manages various unit systems, including metric, imperial, USC, and custom in which your products may be sold. ### Key features and benefits * Defines unit types for length, mass, quantity, and volume * Creates and manages units for each type, and defines the conversions between them * Performs unit conversions * Manages unit code symbols and localized names * Provides a flexible unit management system that supports widely used measurement systems such as metric, imperial, and US customary * Enables flexible product sales by defined units rather than by piece only — for example: * 50 meters of steel tubing * 250 liters of lubricant * 250 grams of fresh-cut cheese --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://developer.emporix.io/api-documentation/api-guides/configuration/unit-handling-service.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.