A B2B ordering platform with per-customer contract pricing.

The situation

A Nordic FMCG group needed an ordering platform that could serve two kinds of customers at once: contract customers with negotiated per-customer pricing, availability rules, and approval flows — and walk-in customers buying at list price.

[PLACEHOLDER — what the brittle legacy stack was and how it failed: where pricing lived before, what broke, what manual work it forced.]

[PLACEHOLDER — the hard constraint: why contract pricing + ERP integration is the difficult part — pricing precedence rules, stock availability, credit limits, approval chains.]

The approach

[PLACEHOLDER — architecture and key decisions: how pricing resolution was modelled, how SAP and the product information system were integrated, sync vs. async boundaries.]

[PLACEHOLDER — the engineering detail worth telling: e.g. how a price is resolved for a given customer/product/date, or how order state is reconciled with SAP.]

[PLACEHOLDER — how correctness was proven: pricing parity tests against the legacy, staged rollout, or parallel-run strategy.]

The result

The legacy stack is gone. Ordering runs end-to-end: from the customer's basket, through contract pricing and approvals, into SAP and back with confirmations and invoicing.

[PLACEHOLDER — what the group can do now that they couldn't before; ongoing maintenance relationship. Round any numbers broadly or omit — see README discretion rules.]