The order that can't be priced
What the user reports
Monday 2 November at Rockford. Brennock Water Utility phones in an order for 4 ES-200 pumps. Customer service can't save it: the order has no price. Distributor orders for Hallam still go through. On Friday the project removed some old test settings from the sales configuration.
The error: Sales order for Brennock refused: no pricing procedure is assigned to sales area CPUS/10/PU.
What you'll do
- See the problem as the customer service representative: On Sales orders, create an order for 10000001 Brennock in CPUS/10/PU: 4 ES-200, requested 2026-11-20, customer reference BWU-PO-7781.
- Find the cause: Brennock's list price for ES-200 exists, and Hallam's orders in channel 20 are priced fine. Why can't Brennock's order be priced, and what fixes it?
- Fix it as the order-to-cash consultant.
- Prove it: run the step that failed again.
The drill runs in the lab on its own prepared copy of the fictional Calder Pumpworks, saved in this browser apart from your company. All codes and values are fictional course labels.
Answer and explanation (open after the drill)
The fix: The sales area CPUS/10/PU no longer points at a pricing procedure, so the order doesn't know which steps to run.
Prices are built by a pricing procedure: the list of steps (list price, discount, freight, tax) an order runs through. Each sales area is assigned one procedure, and the order looks it up from the sales area it is taken in. The direct channel's assignment was deleted, so orders in CPUS/10/PU have no procedure at all. The procedure itself still has its steps, which is why Hallam's orders in channel 20 still work, and missing payment terms would make the order incomplete rather than unpriced.
Why it broke
An order finds its price in three hops: sales area, then the pricing procedure assigned to it, then the condition records each step reads. The middle hop was missing for the direct channel, so the order stopped before it looked for a single price. Prices and the procedure were fine; only the link between them was gone.
How teams prevent it
Treat configuration clean-ups like any other change: list exactly which rows go, test an order in every sales area before and after, and move the change through the test system first. A short regression set (one order per sales area) catches this in minutes.
Across teams
Customer service saw the error with the customer on the phone, but the cause was a project change to sales configuration. The fix belongs to the order-to-cash consultant, and the change process belongs to whoever approved the clean-up.
Where AI fits
Plain automation does most of the work: a regression test that saves one order per sales area after every configuration transport. An assistant can help the person who takes the call: it reads the error, follows the chain from sales area to procedure to conditions and names the missing hop (retrieve). It shouldn't change pricing configuration itself; that goes through the change process.
Learn more: Order to cash end to end