> 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/integrations/order-management/omnium-oms-integration/prices.md).

# Prices

### Overview

Price data flows **one-way from Omnium to Flow**. Omnium maintains the master price lists, and prices are distributed to Flow stores through scheduled tasks. All monetary values are converted to **cents (integers)** before transmission to Flow (e.g., 199.50 NOK becomes `19950`).

### Price types

The integration supports three distinct price types, each handled by a separate scheduled task:

| Price type         | Scheduled task               | Description                                       |
| ------------------ | ---------------------------- | ------------------------------------------------- |
| **Selling prices** | `FlowPriceScheduledTask`     | Regular unit prices and recommended retail prices |
| **Cost prices**    | `FlowCostPriceScheduledTask` | Purchase/cost pricing for margin calculations     |
| **SOA prices**     | `FlowSoaScheduledTask`       | Stock on Account amounts per store                |

### Price list handling

* Omnium maintains **external price lists** that map to Flow price lists
* Each tenant has a `MainPricesListUid` that serves as the default price list
* Store-specific price lists can be created when `StorePriceListsInFlow` is enabled (see Stores)
* Prices are resolved per market or market group

### Selling prices

Selling prices are the customer-facing prices displayed at the POS. They are synced from Omnium's external price indices and include:

* **Unit price** — The base selling price
* **Recommended retail price** — The suggested retail price (RRP)

Selling price sync runs on a configurable schedule (typically every 30 minutes to a few hours).

### Cost prices

Cost prices represent the purchase cost of products and are used for margin and profitability calculations in Flow. They can be synced:

* As part of the product export (via the `Cost` field on the product)
* Through the dedicated `FlowCostPriceScheduledTask`
* Optionally included in inventory updates (when `UseCostPriceListInInventoryExport` is enabled)

### Currency conversion

All prices undergo the following transformation during sync:

* **Omnium format:** Decimal float (e.g., `199.50`)
* **Flow format:** Integer in cents (e.g., `19950`)

The conversion is: `Flow value = Omnium value × 100`

### Configuration reference

| Setting                             | Description                           | Default  |
| ----------------------------------- | ------------------------------------- | -------- |
| `MainPricesListUid`                 | Primary price list UID in Flow        | Required |
| `DefaultVatCodeUid`                 | Default VAT code for products         | Required |
| `StorePriceListsInFlow`             | Generate per-store price lists        | `false`  |
| `UseCostPriceListInInventoryExport` | Include cost prices in inventory sync | `false`  |


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.flowretail.com/docs/integrations/order-management/omnium-oms-integration/prices.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.