Contract prices for a customer

A framework agreement (Rahmenvertrag) says this customer pays these prices for these articles until this date. This is how you put that into the shop so the buyer sees exactly the numbers their procurement department has on file.

Create the customer's price list

1. Go to Order Management › Prices › Price lists and select New price list.
2. Code: use the ERP customer number, e.g. kd-10042. Add a year only if you intend to replace the list each year.
3. Name: say who and what: "Müller Industriebedarf — Rahmenvertrag 2026".
4. Currency: the currency of the agreement.
5. Create the list, then select Edit list and set:
   • Prices are: net or gross, matching the agreement. For a German B2B framework agreement this is net.
   • Account: the organization. This is the field that makes it a customer list. Without it the list applies to everyone.
   • Logged-in buyers only: on. Always, for a contract list.
   • Priority: 10, above your standard list.
   • Valid from / Valid until: the term of the agreement.
6. Save.

Add only the agreed articles

Put entries in the list only for the articles the agreement covers. Everything else falls through to your standard list automatically.

This is worth being firm about. A customer list holding 300 agreed articles is one you can check line by line against the signed agreement. The same list padded out to your full 40,000-article catalogue is one nobody will ever audit, and it silently freezes those 39,700 prices for that customer at whatever they were on the day you copied them.

For anything above a handful of lines, prepare a file and import it. See Import prices in bulk.

Prices for one person at the company

A list can also be bound to a single contact instead of an organization. A contact-bound list is more specific than an account-bound one and wins over it.

Real uses are narrow: a purchasing agent at a large group who buys under different conditions than the rest of the company, or a test account for your own sales team. If you find yourself creating many contact lists, the requirement is usually segmentation and belongs on the account. See Segments.

The account's own price list field

An organization record also carries a Price list field holding the code of the list that company buys on. It is the customer-side record of the same fact and it is what your ERP integration typically writes.

Keep the two consistent: if the organization says kd-10042, the list with code kd-10042 should name that organization under Applies to. When they disagree, somebody moved a customer to a new agreement in one system and not the other, and that is the sort of mismatch that produces a price nobody can explain.

Renewals and endings

Valid until is what makes a contract price end. Set it, and the customer falls back to your standard price the day after the agreement expires, which is commercially correct and also the moment they will call.

So put the renewal in a calendar. A contract list that expires unnoticed does not produce an error; it produces a higher price and a phone call from someone who thought they had an agreement.

When you renegotiate, prefer updating the entries in place over creating a second list. Two overlapping customer lists for the same account, both active, is the classic route to a price nobody can account for.

What to check

• The Applies to column on the price list grid shows the account. If it is empty, every buyer in your shop is currently on this customer's prices.
• Logged-in buyers only is on.
• The entry count matches the number of articles in the agreement, near enough to explain.
• Log in as a test contact at that organization and check three articles: one in the agreement, one outside it, and one where a scale price should also apply. The first should show the agreed price, the second your list price, the third the correct rung.

Next

• Check which price a buyer sees — when the answer is not what you expected.
• Scale and volume prices — tiers inside a contract list.