> 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/manage-inventory/returning-or-swapping-services.md).

# Returning or swapping Services

{% @arcade/embed flowId="KdS0p92rTnEofmAGJmU0" url="<https://app.arcade.software/share/KdS0p92rTnEofmAGJmU0>" %}

Returning or swapping services follows the same structured logic as ordering services, but from a different angle.\
Instead of requesting something new, an existing service is changed, replaced, or returned.

As an administrator, your role is not to initiate these requests, but to **review and approve them** once they are submitted.

***

### How swap and return requests are created

Swap or return requests are initiated directly on the service itself.\
The process is described in detail in the documentation and focuses on how a request is created from an active service.

Once submitted, the request does not execute immediately.\
It is routed into the approvals, just like a regular order.

If you want to understand how swap requests are created from a service, you can find the full step by step explanation in the documentation linked below.

{% content-ref url="/spaces/sefXXH6Iz8RCwoM5daoW/pages/GmpvcmWUDY0Yvcrs6w3v" %}
[How to request a swap](/equipme/assets/understanding-the-inventory/how-to-request-a-swap.md)
{% endcontent-ref %}

***

### Swap requests in approvals

For administrators, swap and return requests appear in the approvals view as **changes**.

While the flow is similar to approving an order, the context is different:

* the service already exists
* the request modifies or replaces it
* no new service is being requested

This allows you to clearly distinguish between new orders and changes to existing services.

***

### Reviewing a swap or return request

When reviewing a swap or return request, you see all relevant information needed to make a decision.\
This includes the affected service, the assigned employee or location, and the requested change.

From an admin perspective, this keeps the process consistent. Whether it is a new order or a service change, approvals always follow the same pattern.

***

### Approval and execution

Once the swap or return request is approved, the change is executed.\
The existing service is updated accordingly and continues through the standard fulfillment process.

This may include returning hardware, exchanging devices, or adjusting the service configuration, depending on the request.


---

# 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/manage-inventory/returning-or-swapping-services.md?ask=<question>
```

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.