First setup

Configure pricing

A default price list, one list price and one scale rung, so you have seen how a price resolves before a customer asks.

A price is not a field on a product. It is a row in a price list, and a product can appear in several lists at once: the catalog price, a customer's contract price, a rung that drops at 50 pieces. Which one a buyer sees is resolved at request time. This walkthrough builds the smallest structure that works, one list with two rungs, and shows you the screen that explains any price afterwards.

Before you begin. You need a product with a SKU, from Create products, and your markets and tax classes set under Configuration › Markets and Configuration › Tax classes. Currency lives on the market; a price list in CHF is invisible to a buyer shopping in EUR, and nothing converts it. See Currencies and tax.

Create the default list

  1. In Commerce Studio, go to Order Management › Prices › Price lists.
  2. Select New price list.
  3. Enter the code standard, a name your colleagues will read in the grid, and the currency as three letters, EUR.
  4. Select Create list. You land on the list, which is empty.
  5. Select Edit list and set three things:
    • Prices are net or gross. State it. An empty basis makes the stored amounts mean whatever a tenant-wide setting says, and the list shows a warning banner until you do.
    • Default list on. Exactly one list carries this flag; it is the last resort when nothing more specific applies to a buyer.
    • Applies to left empty, all three fields. Empty widens, filled narrows, and the standard list applies to everyone.
  6. Save.

Add a list price

  1. On the list, in the Price entries grid, add an entry.
  2. Pick the catalogue product; the SKU fills itself.
  3. Leave Type on Standard and From quantity at 1.
  4. Enter the unit price, net or gross according to the list's basis, and the unit: PCE for pieces, M for metres, KG. Use the same codes your ERP uses, because a mismatch surfaces at order transfer, not in the shop.
  5. Leave Valid from and Valid until empty. A catalog price should not expire.
  6. Save.

Add a scale rung

Add a second entry for the same product with From quantity 50 and a lower unit price. There is no separate tier object: the two entries with the same SKU in the same list are the ladder. A buyer ordering 12 gets the rung at 1; a buyer ordering 60 gets the rung at 50.

Never enter 0.00 to mean "no price". Zero is an orderable price and a B2B buyer will order at it. An article with no entry resolves as on request, which is the honest answer. If you want to say so explicitly, set Type to On request and leave the amount alone.

What to check

  • Open Order Management › Prices › Price entries and filter by the SKU. You see exactly two entries, both on standard, at quantities 1 and 50.
  • In the price list grid, exactly one row has Default, and the list shows a Net / gross value rather than a blank.
  • The list's Status is active. An inactive list never resolves, whatever else it says.

How to explain any price later

Which price wins is decided in a fixed order: the buyer's currency, then status and validity, then market, then whether anonymous buyers may see the list, then specificity (a list bound to a contact beats one bound to an organization, which beats one bound to a channel, which beats an open list), then priority among equals, then the highest rung at or below the ordered quantity. Specificity beats priority, always. When a customer says the shop shows 19.90 and their agreement says 16.20, Check a price walks that order by hand in five minutes.

Next

Create products

One real product by hand, from your own catalog, so the data model shows you what it needs before you import eight thousand rows.

Add a customer

One organization, one contact who may order, and the terms that decide what they see, so the buyer side of the chain exists.