> For the complete documentation index, see [llms.txt](https://docs.solutioo.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solutioo.de/datanorm-item-import/datanorm_en_us/prices/scale-prices.md).

# Scale Prices

Quantity-dependent prices from the Z record as additional price lines with a minimum quantity.

## Where they come from

Scale prices come from the **Z record**. The supplier states from which quantity a lower price applies – for example 12.50 from 10 pieces and 11.80 from 50 pieces.

## How the app represents them

With **Write Scale Prices (Z Records)** enabled, each tier becomes an additional line in the same purchase price list for the vendor, carrying the minimum quantity from the Z record.

<table><thead><tr><th width="230">From the Z record</th><th>In the price line</th></tr></thead><tbody><tr><td>Article number</td><td>Item of the price line</td></tr><tr><td>Minimum quantity</td><td><strong>Minimum Quantity</strong></td></tr><tr><td>Scale price</td><td><strong>Unit Cost</strong></td></tr><tr><td>Validity date</td><td><strong>Starting Date</strong>, where delivered</td></tr></tbody></table>

Business Central automatically picks the line with the highest applicable minimum quantity on a purchase order.

<details>

<summary><strong>Example</strong></summary>

An article has a base price of 13.20 and two tiers:

| Minimum quantity | Price |
| ---------------- | ----- |
| 0                | 13.20 |
| 10               | 12.50 |
| 50               | 11.80 |

Ordering 30 pieces uses the line with minimum quantity 10, so 12.50.

</details>

## Prerequisites

{% hint style="info" %}
Two toggles must be on for scale prices to arrive: **Process Surcharges** in the **Record Filters** section – so that Z records are read at all – and **Write Scale Prices (Z Records)** in the **Price Lists** section.
{% endhint %}

## If no tiers show up

<table><thead><tr><th width="330">Cause</th><th>Check</th></tr></thead><tbody><tr><td>The file contains no Z records.</td><td>Many deliveries come without scale prices. Price staging shows what was read.</td></tr><tr><td>Z records are switched off.</td><td><strong>Process Surcharges</strong> in the setup.</td></tr><tr><td>Writing is switched off.</td><td><strong>Write Scale Prices (Z Records)</strong> in the setup.</td></tr><tr><td>The article is not synchronised.</td><td>Synchronise the articles first, then write the price list.</td></tr></tbody></table>

## Surcharges

Besides scale prices, the Z record carries surcharges such as copper-dependent add-ons. The app takes those values as information on the article but derives no price from them. A day-to-day copper recalculation is not part of the app, see [Limitations](https://docs.solutioo.de/datanorm-item-import/datanorm_en_us/importing-datanorm-files/limitations.md).


---

# 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.solutioo.de/datanorm-item-import/datanorm_en_us/prices/scale-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.
