> 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/orders-and-receipts.md).

# Orders and receipts

Every sale is kept as an order. On the **Sales** tab you find the orders that need something done: sales on hold, orders that are not paid yet, items waiting to be handed over, offers and customer orders. Open any order to see what happened with it, send the receipt again or start a return.

## The lists on the Sales tab

Under **Sales and orders** on the Sales tab:

* **Parked**: sales put on hold. Tap one to carry on with it.
* **Confirmed**: orders that are confirmed but not paid yet.
* **Settled**: paid sales and their receipts.
* **Sold, not delivered**: paid, waiting to be handed over (see [Deliveries and receiving goods](https://docs.flowretail.com/docs/getting-started/software-clients/assistant/deliveries-and-receiving-goods.md)).
* **Offers**: offers that can become a sale.
* **Customer orders**: orders and reservations for customers.

Each list can be searched by order number or customer, and you can scan the order's receipt to open it right away. The filter button has more choices.

## Parked sales

The list shows who parked the sale, when, and what it is worth. If the sale has an expiry date, you see when it is deleted, for example **Expires 13 Oct**. Tap a sale to open it and carry on where you left off.

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FB0OXeLbPB9YZEt5YsY66%2Forders-01_parked-7fee8f63.png?alt=media" alt="Three parked sales, two of them with an expiry date" width="300"><figcaption><p>Parked sales</p></figcaption></figure>

Old parked sales also show up as a reminder on the Home tab (see [Home screen](https://docs.flowretail.com/docs/getting-started/software-clients/assistant/home-screen.md)).

## Customer orders

**Customer orders** lists the orders that hold products for a customer, with a pill on each line: **In stock** when the item is in the store, **Not in stock** when it is still waiting, or **Delivered**. Use **Show only unconfirmed purchase orders** to find what the supplier has not confirmed yet, and **Show delivered items** to see the whole order.

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FHRUKAfWonmIIMxrqI9xu%2Forders-06_customer_orders-3d9f9517.png?alt=media" alt="Two customer orders, one waiting for stock and one in stock" width="300"><figcaption><p>Customer orders</p></figcaption></figure>

Tap **⋯** on an order to open the **Sales order** or its **Purchase order**, or to **Send SMS** to tell the customer that the goods have arrived.

## The order

Open an order to see its status, payment and delivery, the total, the seller and when it was created. Below that come the customer, the notes and the lines, grouped by how they are delivered, then the receipts and the payments.

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FOC1svqKq8OeTikoOMUuA%2Forders-02_order_details-73cf436f.png?alt=media" alt="An order with status, payment, delivery, the customer and the note" width="300"><figcaption><p>The order</p></figcaption></figure>

Tap **⋯** at the top for the **Order actions**. Which ones you see depends on the order:

* **Open in sales**: carry on with an order that is not paid yet.
* **Deliver**: hand over items that are paid but not delivered.
* **Return or exchange**: take items back (see [Returns and exchanges](https://docs.flowretail.com/docs/getting-started/software-clients/assistant/returns-and-exchanges.md)).
* **Note**: the note on the order, visible to the customer or internal.
* **Send order by e-mail**, **Send SMS** or **Send gift card**.
* **Message history**: the SMS and e-mails sent about the order.
* **History**: everything that has happened with the order (see below).
* **Print exchange note** or **Print pickup labels**.
* **Refund prepayment**, when the customer has paid more than the order costs.

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FVOxsLAqvFDcMfwPJ0YhQ%2Forders-03_order_actions-5690c35e.png?alt=media" alt="Order actions: return or exchange, note, send, history and print" width="300"><figcaption><p>Order actions</p></figcaption></figure>

A line for service work, from a sale made on a service case, lists the products behind it under the line, with the serial number as **S/N** where there is one and what the case charges for each (see [Service orders](https://docs.flowretail.com/docs/getting-started/software-clients/assistant/service-orders.md)).

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FMBGC2nRWRc5deT8k4eLr%2Forders-07_service_line-641504cc.png?alt=media" alt="An order with a service line and the products behind it" width="300"><figcaption><p>A service line on the order</p></figcaption></figure>

## Receipts

Tap a receipt on the order to see it the way the customer got it. **⋯** has the **Receipt actions**: **Send receipt** by e-mail again, and for an invoice, **Pay invoice** or **Register payment received** when the invoice was paid elsewhere.

Under **After the payment** you see what Flow did when the sale was paid, such as updating the stock, printing the receipt and syncing loyalty points. If a task failed, tap **Try again**, now or later.

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FO3aZ2x1dRBEUMNAEo9dE%2Forders-04_receipt-c8f594e1.png?alt=media" alt="The receipt with the lines, the total and the tasks after the payment" width="300"><figcaption><p>The receipt</p></figcaption></figure>

The products behind a service line are on the receipt too, under the line with their price, and are printed on the paper receipt.

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FE4iELNeQKRW4Genj6I6L%2Forders-08_service_receipt-5a9e5be3.png?alt=media" alt="A receipt with a service line and the products behind it" width="300"><figcaption><p>A receipt with a service line</p></figcaption></figure>

## History

**History** shows what has happened with the order, newest first: who added the items, the payment, the order handling, the delivery, notes, and SMS and e-mails sent to the customer.

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FVFTnAipABCaeRnql8rPY%2Forders-05_history-354ae724.png?alt=media" alt="The order&#x27;s history from the payment to the hand-over" width="300"><figcaption><p>The order's history</p></figcaption></figure>


---

# 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/orders-and-receipts.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.
