> 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/place-orders.md). # Place orders {% @arcade/embed url="" flowId="eXMIsWy9lYPWo2MHqXQ3" %} Ordering starts in the marketplace, but the decisions that matter are made on the assignment screen, not on the product page. The first one is the destination. A location can receive goods in active use, or into its warehouse. Ordering ten laptops into the warehouse of your site in Czechia means they arrive as stock you can hand out later, instead of landing on someone's desk. The second is the delivery address. If an employee has a home office address stored as their default, that is where their device goes. In a single order you will notice. In a rollout for 300 people you will not, so check it before you confirm. The third is the group. Assigning the order to a group reserves those units for the apprentices starting in September or for a site that opens later, so nobody else takes them in the meantime. Confirming here still does not order anything. The request goes into approvals, and only an approved request becomes an order. ### Read more {% content-ref url="/spaces/sefXXH6Iz8RCwoM5daoW/pages/K3WXhG9RWzhErvdaLqTn" %} [Marketplace](https://app.gitbook.com/o/tyg0OyVUuxExVkZRRN7N/s/sefXXH6Iz8RCwoM5daoW/main-menu/marketplace) {% endcontent-ref %} {% content-ref url="/spaces/sefXXH6Iz8RCwoM5daoW/pages/1ADvCRH3JrRJGUukC8vo" %} [Preparing Devices for Later Delivery](https://app.gitbook.com/o/tyg0OyVUuxExVkZRRN7N/s/sefXXH6Iz8RCwoM5daoW/assets/warehouse-management/preparing-devices-for-later-delivery) {% endcontent-ref %} ### Next Every request now waits for a decision. That is [Approvals](/classes/admin/approvals.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/place-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.