> 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/prices.md).

# Prices

The three prices every product carries, and how Flow Retail values stock.

Flow Retail's price and campaign system covers everything from a single shelf price to customer-specific agreements.

## The three prices

#### 1. Sales price (RRP — recommended retail price)

* What you sell the product for.
* **Includes** VAT, unless the B2B extension's **Product Prices Excluding VAT** is switched on.

#### 2. Purchase price

* What you pay your supplier.
* **Excludes** VAT.
* This is the one you actively manage.

#### 3. Average cost price

* What the stock you hold is actually worth, based on purchase history and stock adjustments.
* Calculated automatically, though you can set it manually for a given quantity.
* Held **per warehouse**, so it can differ between them.
* **Excludes** VAT.

For how the average is worked out, what moves it and what does not, see [How cost price is calculated](https://docs.flowretail.com/docs/day-to-day-operations/prices/how-cost-price-is-calculated.md).

## Cost price uses a weighted average

Flow Retail uses average cost pricing — a weighted average — rather than FIFO.

FIFO values each sale at the cost of the oldest unit still in stock, so margin jumps around depending on when purchase orders happened to land. A weighted average smooths that out and makes product profitability readable over time.

{% hint style="warning" %}

## Adding a customer re-prices the order

Adding a customer to an order — or removing one — looks up the price of every line again, so customer-specific prices and campaigns are taken into account.

**Prices set manually are not changed.** A price someone typed in is treated as a deliberate decision and survives the recalculation. A line whose lookup returns no price also keeps its price.

Add the customer before discussing price, not after. See [Adding a customer to an order](https://docs.flowretail.com/docs/day-to-day-operations/selling/adding-a-customer-to-an-order.md).
{% endhint %}

*Last updated 24.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/prices.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.
