> For the complete documentation index, see [llms.txt](https://docs.flowretail.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowretail.com/docs/getting-started/software-clients/assistant/returns-and-exchanges.md).

# Returns and exchanges

Take back items the customer bought earlier, give the money back, or swap them for something else in the same go. The return is linked to the original order, so stock, reports and the customer's history stay right.

## Start a return

Tap the red **Start return** button on the **Sales** tab. Scan the barcode on the customer's receipt, or type the order number. Assistant finds the order straight away.

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FDBNgi2GoO3YVxnT4zFP4%2Freturns-01_start_return-ee1a612e.png?alt=media" alt="Create return / exchange with the order number field, Search orders and Create empty return" width="300"><figcaption><p>Start a return</p></figcaption></figure>

* No receipt? Tap **Search orders** and find the paid order by order number or customer.
* The order can't be found? Tap **Create empty return** and scan the items that come back.

You can also start from the order itself: open it, tap **⋯** and **Return or exchange** (see [Orders and receipts](https://docs.flowretail.com/docs/getting-started/software-clients/assistant/orders-and-receipts.md)).

{% hint style="info" %}
Your store may ask for your PIN before a return.
{% endhint %}

## Choose what comes back

Choose the warehouse the items go back into under **Return to warehouse**, and the **Return reason**. Then use **+** on each product to choose how many come back, and tap **Confirm**.

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FRHhRhyHfZ3eIiobpygch%2Freturns-02_choose_items-f0665b92.png?alt=media" alt="Return or exchange: warehouse, reason and the sweater chosen" width="300"><figcaption><p>Choose the items, the warehouse and the reason</p></figcaption></figure>

Items that are on a delivery on its way can't be returned until the delivery is set back to new or handed over. Assistant tells you which delivery it is.

## Pay out or exchange

The return opens as a sale. The returned item is red, marked **Return**, with a minus quantity.

* For a plain return, tap **Pay out** and choose how the customer gets the money back.
* For an exchange, add the new item to the same sale, for example the sweater in another size. Then tap **Pay** if the customer owes something, or **Pay out** if you owe the customer.

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FN3Yxgm7XraEOKRXue2nk%2Freturns-03_pay_out-d6221b61.png?alt=media" alt="The returned sweater in red, with To refund and the Pay out button" width="300"><figcaption><p>Ready to pay out</p></figcaption></figure>

## Exchange notes

An exchange note lets the customer swap a gift later without the receipt. Tap **Print exchange note** on the paid receipt, or under **⋯** on the order.


---

# 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://docs.flowretail.com/docs/getting-started/software-clients/assistant/returns-and-exchanges.md?ask=<question>&goal=<user_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.
