> 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/selling/order-lines.md).

# Order lines

What each line on an order carries, how it is reserved against stock, and how lines relate to each other.

Every product on an order is a **line**. A line is not just a product and a quantity — it also records **where the goods are coming from** and **how it relates to other lines** on the same order.

Those two things explain most of what looks surprising on an order.

## How a line is reserved

The reservation type says where the stock for this line is expected to come from.

| Reservation               | Where the goods come from                                   | Reserves stock? |
| ------------------------- | ----------------------------------------------------------- | --------------- |
| `NONE`                    | Nothing is set aside                                        | No              |
| `WAREHOUSE`               | Stock you already hold                                      | Yes             |
| `PURCHASEORDER`           | A purchase order that exists                                | Yes             |
| `PURCHASEORDER_CONFIRMED` | A purchase order the supplier has confirmed                 | Yes             |
| `REQUEST_PURCHASEORDER`   | A purchase order that has been requested but not yet placed | Yes             |

Everything except `NONE` reserves. That matters: a line can hold a reservation against goods that **do not exist yet**. `REQUEST_PURCHASEORDER` and `PURCHASEORDER` both reserve against a supplier order, not against anything on your shelf.

This is what lets you sell an item you have not got, promise a date, and have the reservation follow the goods in. The counterpart on the purchasing side is [Receiving goods](/docs/day-to-day-operations/purchase-and-receivement/receiving-goods.md) — receiving is what converts that promise into stock.

## How lines relate to each other

Lines are linked in **pairs**. Each relationship has two sides, and each side has its own link type, so you can read the relationship from either end.

| One side            | The other side        | What it is                                           |
| ------------------- | --------------------- | ---------------------------------------------------- |
| `INSURANCE`         | `INSURED`             | An insurance line and the product it insures         |
| `SERVICE`           | `HAS_SERVICE`         | A service line and the product it applies to         |
| `FREIGHT_SERVICE`   | `HAS_FREIGHT_SERVICE` | A freight line and what it ships                     |
| `PACKAGE_COMPONENT` | `PACKAGE`             | A component and its parent package                   |
| `COMPENSATION`      | `COMPENSATED`         | A compensation line and what it compensates          |
| `AUTO_ADD`          | `AUTO_ADDED`          | A line that was added automatically, and its trigger |
| `CREDIT`            |                       | A credit reference                                   |

These links come from the product's own relationships — see [Linked products](/docs/day-to-day-operations/products/linked-products.md) for how they are set up.

The pairing is why removing a line can change others. An insurance line points at the product it insures, so removing that product removes the insurance with it. An accessory holds no such dependency, so it stays.

## What this means for you

* **Check the reservation type before promising a date.** A reserved line does not mean the goods are in the building. Only `WAREHOUSE` means that.
* **Expect lines to disappear in pairs.** Insurance, auto-added products and package components are tied to a parent line and go when it goes.
* **Package component lines are derived.** Their prices are a split of the package price, not the product's own price — see [Package products](/docs/day-to-day-operations/products/adding-products/package-products.md).

## Limitations

* A line has one reservation type. Splitting a quantity across stock on hand and an incoming purchase order means more than one line.
* A credit link is one-directional; there is no paired type on the other side.

***

*Last updated 19.09.2026*


---

# 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/day-to-day-operations/selling/order-lines.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.