> 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/returning-or-swapping-services.md). # Returning or swapping Services {% @arcade/embed url="" flowId="KdS0p92rTnEofmAGJmU0" %} Returns and swaps start on the service itself, usually from the person who has it, not from you. Your part is the decision. They arrive in the same approvals list as new orders, but marked as changes. The difference is worth noticing: the service already exists, and you are approving a modification to something in use rather than a new cost. Approving does not move the device. The return goes into order processing and only lands in your warehouse once that is completed. That split is deliberate, it gives whoever handles processing a chance to catch a mistake before stock officially changes. A swap keeps the service running and replaces what sits behind it, which is why the old device and the new one can briefly both be booked. ### Read more {% content-ref url="/spaces/sefXXH6Iz8RCwoM5daoW/pages/GmpvcmWUDY0Yvcrs6w3v" %} [How to request a swap](https://app.gitbook.com/o/tyg0OyVUuxExVkZRRN7N/s/sefXXH6Iz8RCwoM5daoW/assets/understanding-the-inventory/how-to-request-a-swap) {% 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/inventory/returning-or-swapping-services.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.