Set a list price

A supplier confirmation lands on your desk with a new article, 4711-A, and sales has agreed the catalogue price: €19.90 net per piece. Until that number is on your standard list, the article sits in the catalogue and the shop answers "on request" for it.

Putting it there is the base price every other layer starts from. It is the single most common task in the Pricing area, and it takes about twenty seconds once the lists exist.

Add a price to a list

1. Go to Order Management › Prices › Price lists and open the list. For a catalogue price, that is your default list.
2. In the Price entries grid, add an entry.
3. Pick the catalogue product. Choosing it fills the SKU for you. If the catalogue does not carry the SKU (a service, a surcharge article, a supplier item you sell but do not describe), leave the product empty and type the SKU instead. An entry needs one or the other.
4. Leave Type on Standard.
5. Leave From quantity at 1. This is the base rung of the ladder.
6. Enter the unit price. Net or gross follows the list's basis; the field takes the number only.
7. Enter the unit if you use one: PCE for pieces, M for metres, KG, L. Use the same codes your ERP and your BMEcat export use.
8. Leave Valid from and Valid until empty for a normal catalogue price. A list price should not expire.
9. Save the entry.

Change a price that already exists

The Unit price column in the entries grid on a price list is editable in place. For a handful of corrections, that is the fastest route: open the list, search the SKU, type the new amount.

For anything larger, do not click through rows:

• A whole list moving by a percentage → Adjust a whole price list.
• A file from the ERP or a spreadsheet → Import prices in bulk.

Units, and why they matter more here than anywhere

The unit is part of the price. A price of 0.0185 means nothing until somebody says whether that is per piece or per 1,000 pieces, and in cable, fasteners, seals and fittings both are normal.

Three rules:

• Use the same unit code as your ERP. If the ERP says PCE, do not write Stk. The mismatch only surfaces at order transfer.
• Price in the unit you sell in. If an article is ordered per metre, price it per metre. Do not price per roll and expect the storefront to divide.
• A price per 1,000 keeps its decimals. Stored prices are returned exactly as entered, so 0.0185 stays 0.0185. Only computed amounts are rounded.

Units and packaging quantities on the article itself belong in the catalogue; see Attributes and attribute groups.

Pricing an article you cannot publish a price for

Set Type to On request and leave the amount alone. The price call then answers "on request" rather than a number, so the article stays in the catalogue and stays findable while the buyer is directed to ask.

An on-request entry outranks a number in another list, which makes it a decision rather than a gap. If you want the buyer to get a price from another list, do not create the on-request entry at all.

What to check

After adding a handful of prices:

• Open Order Management › Prices › Price entries and filter by the SKU. You should see exactly the entries you expect, on the lists you expect. If the same SKU appears on a customer list you forgot about, that customer is not getting this price.
• Confirm the list's Net / gross badge says what you assumed while typing.
• Look at the article in the storefront as an anonymous visitor and again as a logged-in test buyer. Those two answers are allowed to differ, but only in ways you intended.

Next

• Scale and volume prices — add quantity rungs to the entry you made.
• Contract prices for a customer — the negotiated layer above it.