> 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/administrative-functions/fulfill-internal-orders.md). # Fulfill internal orders {% @arcade/embed flowId="1Bx0CcIO3Ox5i2Tyajan" url="" %} *** #### From approval to fulfillment After an order has passed all approvals, it appears in **Order processing**. At this point, no further decisions are required. The order is ready to be handled operationally. This marks a clear transition in the process. The Marketplace and approval steps focus on defining what should be ordered and in which context it will be used. Order processing focuses on execution and delivery. Here, approved orders become actionable items.
*** #### Order processing as the operational view Order processing provides a consolidated view of all internal orders that are waiting to be fulfilled, currently in delivery, or already completed. Each entry represents a concrete service or asset that requires action. This might be a device coming from internal inventory, a service that needs to be provisioned, or an asset that must be assigned before it can be used. This view helps ensure that fulfillment is handled consistently and that no approved order is left unattended. *** #### Reviewing an order before delivery Opening an internal order shows the full service view. This is where all relevant details come together before delivery begins.
You can review the selected options, such as configuration or variants, and verify the intended assignment. Depending on how the order was prepared, the service may already be linked to an employee, a location, or a group. Contract and billing related information is also visible, providing additional context for the service lifecycle. This review step helps ensure that delivery aligns with what was approved and expected. *** #### Updating the delivery status Internal fulfillment is tracked using delivery statuses. These statuses reflect the current state of execution and make progress visible without additional coordination.
When fulfillment starts, the delivery status is set to **Delivery in progress**. This indicates that the service or asset is being prepared, provisioned, or physically delivered. Once the service is available or the asset has been handed over, the status is updated to **Delivery completed**. This marks the completion of the fulfillment phase and confirms that delivery has taken place. *** #### Completing or adjusting assignment during fulfillment In some cases, services are ordered before the final assignment is known. During fulfillment, assignment can be completed or adjusted if needed. Services can be assigned to an employee, a location, or a group directly from the service view. This allows fulfillment to remain flexible while still ensuring that services are correctly linked once delivery is complete. After assignment and delivery completion, the service becomes fully active and traceable within the system. *** #### Fulfillment as part of the service lifecycle Fulfillment connects approvals with ongoing service management. Once delivery is completed, the order itself becomes less relevant, but the service continues as an active part of the environment. From this point forward, the service can be monitored, modified, extended, or eventually offboarded. A clean fulfillment process ensures that this lifecycle starts with accurate data and clear status information. Internal fulfillment helps maintain consistency, transparency, and reliability across all services. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://hub.equipme.io/classes/administrative-functions/fulfill-internal-orders.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.