Adjust a whole price list

Once a year, or whenever a supplier moves, you need every price in a list to change at once. This is the task the Adjust prices action exists for, and the preview step is the part that matters.

Adjust a list

1. Go to Order Management › Prices › Price lists and open the list. Adjust prices is also available as a row action directly from the grid.
2. Choose Adjust prices.
3. Enter either a percentage or a fixed amount, not both:
   • Change by (%): 5 for +5 %, -10 for a 10 % cut.
   • Change by (amount): a fixed amount added to every unit price, in the list's currency.
4. Optionally set Only SKUs starting with to limit the change to part of the list, for example one supplier's article-number prefix. Leave it empty to change every priced entry.
5. Set Round results to. Leave it empty to use your tenant default; see Rounding, defaults and resolution rules.
6. Leave Preview only switched on and run it.
7. Read the preview. Then run it again with Preview only off to apply.

Preview only is on by default. Leave it on for the first run, every time. It writes nothing and shows what would change. A bulk adjust across a list has no undo button; the previous prices are gone unless you have the file they came from.

What the adjustment touches

• Every priced entry in the list, including every rung of every scale ladder. A 5 % rise moves the quantity-1 price and the from-50 price alike.
• Not on_request entries. Those are never touched.
• Not any other list. Adjusting your standard list leaves customer, campaign and foreign-currency lists exactly where they were.

Rounding, and why the preview matters

A 7 % increase turns €19.90 into €21.293. Nobody prints that. The Round results to option snaps every computed price to an ending you would publish: whole units, x.99, x.95, x.50, or exact.

Snapping goes to the nearest matching price in both directions. €21.293 snapped to x.95 becomes €20.95, below the exact result and below a straight 7 %. On one article that is trivia. On 40,000 entries it is a number your controller can see. Read the preview before you apply.

The annual price round, in order

Doing this properly is a sequence:

1. Adjust the standard list. Preview, read, apply.
2. Adjust each foreign-currency list separately. They do not follow the EUR list and they need their own percentage, because exchange rates have moved too.
3. Decide, per contract list, what happens. This is a commercial decision and it is the step that gets skipped. Your largest customers are on net contract prices; if you do nothing, they do not move at all, and they are the ones with the volume.
4. Check the campaign lists. A campaign priced against last year's list price may now be above it.
5. Tell the people who quote. Innendienst and field sales must hear about a price change before a customer tells them.

Where an agreement forbids it

Framework agreements frequently fix prices for a term. Adjusting a customer list inside its term is a breach of contract, and the customer's procurement system will detect it at the next order, because their ERP holds the agreed number.

Before adjusting any list bound to an account, check its Valid until. If the agreement is still running, prepare the new prices for the renewal date and leave the list alone until then.

What to check

• Sort the list's entries by unit price after the change. The extremes tell you whether the rounding did something you did not intend.
• Pick three articles whose old price you know and confirm the new one is what you expected, including a scale article, so you can see all its rungs moved.
• Confirm on_request entries still say on request.
• Check one contract customer in a test session. Their price should be unchanged, which is correct, and the reminder that step 3 above still needs a decision.

Next

• Price list hygiene — the review that stops the next round being archaeology.
• Where your prices come from — if your ERP owns prices, the price round happens there instead.