Skip to content

Simulation & Approvals

Two control instruments before prices go live: the dry run shows what the engine would do — the approval workbench holds large changes until a human approves them.


Price Simulation (dry run)

What happens if you lower the margin, switch the rounding, raise a fee? The Price Simulation answers that without writing anything — neither price lists nor log.

  1. Make the rule change in the Price Calculation Setup (or simply review the current state)
  2. Open Price Simulation → Run Simulation — the complete pipeline calculates the whole item universe
  3. Result per item: current price, simulated price, change %, result (including "would be rejected" / "would wait for approval") — with a summary line: X simulated, Y would change, Z of them > 10 %, W rejected/held
  4. Apply calculates the selected rows for real — through the same path as a normal run, including all safety limits, price fixes, and approval rules. Rows of base lists are written before those of the derived lists; on periodic lists every change becomes a proposal

The views filter to Would change, Change > 10%, Would be rejected, and Suppressed / pending approval.

Before every larger rule change

Simulate first, then go live — the delta preview instantly shows whether the change does what you expect. With derived lists, apply the row of the base list as well: applying calculates for real, and for real the new base price is only on the list once it has been applied.


Price Approvals

For channels where no price should go live unchecked: set the Approval Threshold % of the price list. Changes above the threshold are not published but parked as drafts. On periodic lists every change becomes a proposal on review, regardless of the threshold.

The Price Approvals workbench shows per proposal the Current Price and the Proposed Price with Change % — and the full why via Why This Price?. Minimum Quantity and Ending Date tell whether a row is a regular price, a quantity tier or a campaign price.

Action Effect
Approve activates the proposal like a real price write: the old line closes, quantity tiers follow, the channels are notified. A proposal for the next period of a periodic list is scheduled instead (see below)
Reject discards the proposal; the current price stays. On a scheduled proposal it withdraws the approval

Per item and list there is always only one open proposal — a newer one replaces the older. Parked proposals appear in the log with the result Pending Approval.

When a proposal disappears on its own

  • Superseded: if a later run writes a regular price for item and list or confirms the running one — also when the hysteresis suppresses a small change — it withdraws the waiting proposal. The calculations that waited for it then show Superseded. If the later run ends in Rejected, No Offer or Error, the proposal stays.
  • Fixed: when you fix a price, the engine withdraws the waiting proposal; the waiting calculations then show Fixed. Approve does not activate a proposal for a fixed price — the result message counts it separately, reject it. Likewise, a proposal made before the price now in force took effect is not activated.

Your own drafts

The workbench also shows drafts you created or edited yourself in a list of the engine, for instance after Allow Editing Active Price. The engine never withdraws or overwrites them. Approve activates a regular price of your own like a proposal, and a campaign or tier as you entered it; Reject deletes the draft and with it the edited line. If your price should stay, fix it — otherwise the next regular run replaces it.

Only the approval decides a proposal

A proposal of the engine stays a draft when Business Central activates the other lines: Verify Lines leaves it out, so does a status change of the price list to Active or Inactive, and Implement Price Change in the price worksheet does not activate it. Only through Approve does the engine notify the channels, keep the price timeline and close the waiting calculations.

Proposals for the next period

On a periodic list with a Next Period Lead Time, the proposals carry the start of the next period as their Starting Date. Approve does not put them into force right away but marks them as Scheduled: the current price stays in force until the period ends, a scheduled proposal no longer counts as an open approval, and later runs do not overwrite it. On the first day of the new period the job queue entry QUEUE puts it into force. If the price has been fixed or superseded by then, the proposal returns as an open proposal. Details: Pricing mode.

The special cases — edited prices, copies, migration mode — are described in the manual, chapter Preisfreigaben.