> For the complete documentation index, see [llms.txt](https://docs.commercelayer.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.commercelayer.io/data-model/pricing-and-markets/price-lists-and-currencies.md).
# Price lists and currencies
SKU pricing per market, schedulers, tiered pricing, and external price calculation
{% hint style="info" icon="lightbulb" %}
Price lists are collections of SKU prices defined by currency and market. Only SKUs with a price in the active price list and stock in a market location are sellable. Schedulers, price tiers, and external pricing add further flexibility.
{% endhint %}
## Price lists
[Price lists](/core-api-reference/price_lists.md) are collections of SKU prices, defined by currency and market. When fetching SKUs, only those with a price in the market's active price list and at least one stock item in one of the market's stock locations are returned. You can create price lists to manage international business or B2B/B2C pricing models.
### Price list schedulers
A [price list scheduler](https://docs.commercelayer.io/core-api-reference/) associates an alternative price list with a market, overriding the market's default price list for a defined time frame. The scheduler and the market must share the same currency and tax policy. If multiple schedulers are active at the same time, the one that started first takes priority. If multiple schedulers start at the same time, the one that ends first applies.
## Prices and currencies
A [price](/core-api-reference/prices.md) is the cost of an SKU associated with a currency and a price list. When a customer purchases an SKU, the price is taken from the order's active price list for that market. The same SKU can have a different price in each market — for example, $50 in *List A* for the US market and €45 in *List B* for the EUR market.
{% hint style="warning" %}
SKUs without a price in the active price list are not *sellable* in that market.
{% endhint %}
### Price tiers
Commerce Layer supports up to **10 price tiers** per price. Two types of [tiers](/core-api-reference/price_tiers.md) are available:
* **Volume-based tiers** — the price of an SKU is determined by the tier the total quantity purchased falls within.
* **Frequency-based tiers** — the price of an SKU is determined by the tier the purchase frequency falls within. Typically used to apply discounts for recurring purchases.
### External prices
For more dynamic pricing or custom calculation logic, you can manage SKU prices [using an external service](/core/external-resources/external-prices.md). Set the external API endpoint at the market level and it will calculate the unit price of each SKU upon request.
---
# 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.commercelayer.io/data-model/pricing-and-markets/price-lists-and-currencies.md?ask=&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.
