> 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/inventory.md). # Inventory {% hint style="info" %} Walkthrough goes here. {% endhint %} Everything that made it through fulfilment ends up here. Hardware, software, services, anything with a lifecycle, in one list with a system wide identifier. The status tells you where a thing is in that lifecycle. Ordered, in progress, shipping, active. Only when it becomes active does it start counting, which is when a contract term or service duration begins. Two kinds of detail sit on an object and people mix them up. Characteristics that come from the product, such as sixteen gigabytes of memory, are the same for every unit. Values that come from the actual instance, such as the serial number, arrive when the device does. Worth knowing for finance: the provider and the party that invoices you do not have to be the same. A phone can be provided by one company and billed by another, and inventory keeps those apart. If you always need a particular attribute in the table, serial number being the usual candidate, you can promote a custom field to a column instead of opening each object. The three chapters below cover what happens to an object after delivery. ### Read more {% content-ref url="/spaces/sefXXH6Iz8RCwoM5daoW/pages/lUvic7onM1k0YEpy4nh3" %} [Understanding the inventory](https://app.gitbook.com/o/tyg0OyVUuxExVkZRRN7N/s/sefXXH6Iz8RCwoM5daoW/assets/understanding-the-inventory) {% endcontent-ref %} ### Next Start with the step most people skip: [Confirmation of receipt](/classes/admin/inventory/confirmation-of-receipt.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/inventory.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.