> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/classes/admin/offer-management/service-portfolio/categories.md). # Categories {% @arcade/embed url="" flowId="fqwXNjvPPZKC5nutLFQ2" %} Categories are not labels. They are the filter users navigate with, so the tree you build here is exactly what appears on the left side of the marketplace. Display order is what puts a category on its level. Devices at the top, Smartphones below it, iOS below that. Three levels turn a full catalogue into a short path: broad area, device type, platform. A user looking for an iPhone gets there in three clicks instead of scrolling past printers and licences. That makes the shape of the tree more important than the naming. A flat list of twenty categories is a wall of choices, and users pick the first thing that looks close enough. Keep the top level small and let the depth do the work. Build it the way users search, not the way your asset list is organised. Nobody looks for a phone under a procurement class. There is a second reason to set categories up early. A category can define which fields every product inside it should carry, for example serial number or IMEI for devices. The category does not hold the values, it decides that those fields exist on each item later in inventory. Deciding that before you add fifty services saves you from filling the gaps afterwards. ### Read more {% content-ref url="/spaces/sefXXH6Iz8RCwoM5daoW/pages/ebWpvIdQNNe7NtckeDMW" %} [Organising services with categories](https://app.gitbook.com/o/tyg0OyVUuxExVkZRRN7N/s/sefXXH6Iz8RCwoM5daoW/offer-management/service-portfolio/organising-services-with-categories) {% endcontent-ref %} {% content-ref url="/spaces/sefXXH6Iz8RCwoM5daoW/pages/2xpHE8y5zk0Ea9KeZb90" %} [Category Attributes](https://app.gitbook.com/o/tyg0OyVUuxExVkZRRN7N/s/sefXXH6Iz8RCwoM5daoW/offer-management/service-portfolio/category-attributes) {% endcontent-ref %} ### Next With the structure in place, fill it: [Creating a service](/classes/admin/offer-management/service-portfolio/creating-a-service.md). --- # 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://hub.equipme.io/classes/admin/offer-management/service-portfolio/categories.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.