> 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/day-to-day-operations/reports/sales-reports/sold-not-delivered.md).

# Sold, not delivered

The **Sold, Not Delivered** report shows all completed sales transactions where products have been paid for but haven't been marked as delivered yet.

This report helps you monitor outstanding orders and ensure timely fulfillment.

Each line represents a product waiting to be shipped or picked up by the customer. This gives you a clear overview of your fulfillment backlog.

<div data-with-frame="true"><figure><img src="/files/8N4fAwM3On6M46aI6OyJ" alt=""><figcaption></figcaption></figure></div>

### What does it give?

The report exports essential transaction details of each product on each order awaiting to be delivered.

**Output format:** Excel XLSX

#### The included fields are:

* SKU
* Name
* Brand
* Product Group
* Order Number
* Quantity
* Cost Price
* Sales Price
* Sold Date

Products appear in this report from the moment a sale is completed until they're marked as delivered in your system. This means the list updates automatically as you process deliveries.

You can use the sold date column to identify orders that have been waiting longest. This helps you prioritize which deliveries need immediate attention.

### Who is it for?

* **Store managers** and **sellers** wanting to keep track of sold but not yet delivered products, to make sure customers gets what they have ordered.
* **Accountants**, to keep track of sold but not yet delivered products.

### How do I get started?

1. Find and download the report in the `Flow Retail Admin` under the **Reports** section.
2. Once downloaded, use the sold date column to prioritize older orders first. Reference the order number when coordinating with your fulfillment team or updating delivery status.
3. Filter by product group or brand if you need to focus on specific categories. This is especially useful if different teams handle different product types.


---

# 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://docs.flowretail.com/docs/day-to-day-operations/reports/sales-reports/sold-not-delivered.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.