> 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.md). # Service portfolio The portfolio is everything you offer, listed before anyone has requested it. Devices, software, internal services, whatever your organisation provides. Two things live here, and keeping them apart makes the rest easier. A service is what someone books, with a price, a term and a lifecycle. A product is the physical item that ships and gets tracked in inventory. A service can carry products, which is why a laptop offer is a service with a device behind it rather than a product on its own. A portfolio entry is only finished when it has an offer and, where something physical is involved, a bill of materials. Without the first it has no price. Without the second, nothing is delivered when the request goes through. ### Read more {% content-ref url="/spaces/sefXXH6Iz8RCwoM5daoW/pages/S0bezxo4Cr2c6vac6ijG" %} [Service Portfolio](https://app.gitbook.com/o/tyg0OyVUuxExVkZRRN7N/s/sefXXH6Iz8RCwoM5daoW/offer-management/service-portfolio) {% endcontent-ref %} {% content-ref url="/spaces/sefXXH6Iz8RCwoM5daoW/pages/K0VatCfmDUG6nhnDZE4a" %} [Products vs. Services](https://app.gitbook.com/o/tyg0OyVUuxExVkZRRN7N/s/sefXXH6Iz8RCwoM5daoW/offer-management/service-portfolio/products-vs.-services) {% endcontent-ref %} ### Next Start with the structure your catalogue sits in: [Categories](/classes/admin/offer-management/service-portfolio/categories.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.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.