> 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/fulfill-internal-orders.md). # Fulfill internal orders {% @arcade/embed url="" flowId="1Bx0CcIO3Ox5i2Tyajan" %} Order processing is the part with no decisions left in it. Everything here has passed approval, and what remains is doing it: provisioning a service, preparing a device, handing something over. The delivery status is how that becomes visible to everyone else. Delivery in progress means someone is on it. Delivery completed means it has actually reached the recipient. Without those two steps, the rest of the organisation has no way to tell a stalled order from a busy one. You can still fix the assignment here. Orders are often placed before anyone knows who exactly gets the device, so the service can be attached to an employee, a location or a group during fulfilment rather than at order time. How busy this area gets depends on how much you provide yourself. A portal that only orders from suppliers sees little here. The moment your own teams offer services, business cards from marketing, a phone contract from IT, every request lands here as a task. Once delivery is complete the order stops being interesting. The service continues as part of your inventory. ### Read more {% content-ref url="/spaces/sefXXH6Iz8RCwoM5daoW/pages/TI1LOUelAPU9tSD8NLAP" %} [Order and Delivery Status Overview](https://app.gitbook.com/o/tyg0OyVUuxExVkZRRN7N/s/sefXXH6Iz8RCwoM5daoW/controlling/orders/order-and-delivery-status-overview) {% endcontent-ref %} {% content-ref url="/spaces/sefXXH6Iz8RCwoM5daoW/pages/O6uL7KhFHbl8jqjY9DWx" %} [Pending and approved order requests](https://app.gitbook.com/o/tyg0OyVUuxExVkZRRN7N/s/sefXXH6Iz8RCwoM5daoW/main-menu/approvals/pending-and-approved-order-requests) {% endcontent-ref %} --- # 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/fulfill-internal-orders.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.