erpkaizen

Measuring the value

New orders carry the customer's own price list: 1,061 of 1,140 orders once carried the wrong list, after the fix 0

Has a measurement By 8 Nov 2026 About 8 minutes
A new sales order. The price list field pre-filled with the default list is struck out and replaced by the customer's list. An item with no price in the customer's list is left empty for a person to type, instead of taking a price from another list. The save to list box is no longer ticked automatically. No real figures. New sales order Price list Default Customer's list Item A 30,000 Item B type it Save to list The order carries the customer's price list no price means empty, never another list
The price list field pre-filled with the default list is replaced by the customer's list; an item with no price is left empty for a person to type.

The order screen pre-filled the default price list, so 93% of one store group's orders carried another customer's list; the quick sales screen also took prices from other lists and wrote them over the customer's list. Now orders always carry the customer's list, and a missing price stays empty. How far each item was off, and what it is worth each month.

When an order carries the wrong price list, how far off is each line, in which direction, and what does it cost a month?

It needs only the orders a month, the lines per order, the share of orders on the wrong list and the share of wrongly priced lines caught before invoicing. The gap per product is a real, anonymised measurement. Everything is editable.

Measured: 1,140 orders in 30 days, one store group
Measured: 2,987 lines on 1,061 orders
Measured: 93% before the fix, 0% after
Measure it in your company; the preset is illustrative

Derived (per month)

Item lines on orders with the wrong list–
Of which priced differently from the customer's list–
Short-billed lines that reach the invoice–
Over-billed lines that reach the invoice–
Assumptions — open to see and edit every number

Money

Time

Default-list price against the customer's list price, product by product Left: cheaper on the default list — the invoice would be short · right: dearer — the invoice would be over · hover a row for both prices
Default-list price against the customer's list price, product by product

A. Revenue no longer billed short–
B. No more credit notes for over-billing–
C. No catching and fixing prices line by line–
Per month, in money–

This is an estimate, not a promise. Set the share of orders on the wrong list to 0 — exactly what was measured after the fix: every line goes to 0. The gap per product comes from one company's price lists; yours will differ.

One group of a supermarket chain's stores has its own price list. Over 30 days, 1,061 of 1,140 sales orders for that store group instead carried the system's default price list — the list of an entirely different customer. Nobody chose wrongly: the order screen pre-fills the default list into the price list field, and the system only fills fields that are still empty, so the customer's own list never got set.

This article asks: if a new order always carries the customer's own price list, never falls back to another list when the customer's list has no price, and never silently writes over the price list — what is that worth each month, and which part of the figure do you have to measure yourself?

1. A wrong price list gets into orders by three routes

The pre-filled price list field. The quick order screens start from a new document that already has the default list. Measured on orders created from 30/9 to the morning of 30/10/2026: for the store group above, 1,061 of 1,140 orders (93%) carried the default list. For every other customer with its own list, 419 of 2,856 orders (15%) carried a list that was not theirs — 414 of them exactly that same default list.

Falling back to another list. On the quick sales screen, when the customer's list had no price for an item, the screen took the price from any selling list that had one. One guava item came out at 21,000 VND — another list's price — while the chain's purchase order said 30,000.

Silent overwriting. Next to each line is a «Save to list» box, and that box is ticked by default. The 21,000 that had just fallen through was written straight into the customer's list, with no check of the unit of measure and no record of who saved it. Next time, the customer's list already «had a price» — the wrong price.

2. What changes

  1. One fix for every order-creation route. Before a sales order or delivery note still in draft is saved: if it carries the default list (or no list) and the customer has its own list — looked up on the customer, then the customer group, then the parent group — it switches to the customer's list and re-fetches prices for lines that were following the old list or had no price. Lines where the user typed a different price are kept. Delivery note lines taken from a submitted sales order keep the sales order's price. A list the user chose themselves — not the default list — is left as it is.
  2. No falling back to another list. The quick sales screen looks up only the customer's list. That list has no price ⇒ the price field stays empty, and the person entering the order types it from the purchase order. Only customers without their own list use the fallback price as before.
  3. No silent overwriting. The «Save to list» box is ticked automatically only when the customer's list has no price for that item. On saving, the price goes through the same checks as any other price list line, in the line's own unit of measure, and leaves a note: who saved it, the old price, the new price.
  4. Orders created from the quick sales screen carry the customer's price list, not the default list.

3. What was measured

Orders carrying a list that is not the customer'sPrevious 30 daysAfter the fix
The chain's store group1,061 / 1,1400 / 46
Every other customer with its own list419 / 2,8560 / 82

«After the fix» runs from noon on 30/10 to the morning of 31/10/2026 — less than one working day. There were no price saves from the quick sales screen in that period. One day shows the mechanism works; it does not yet say the number stays at 0. Measure again after four weeks.

What a wrong price list is worth depends on how far apart the two lists are. Of the 41 items that store group ordered over 30 days, 4 had no price in the customer's list. 34 items had a price in both lists and could be compared (three pairs were excluded on purpose: one pair is two different pack sizes, two pairs carry 1–2 VND placeholder prices). Of those 34 items:

  • 17 items are cheaper in the default list, on average by 18.3% — an order carrying the wrong list would be under-invoiced;
  • 14 items are dearer, on average by 12.5% — the invoice would be over-invoiced;
  • 3 items are the same.

The figure below plots each item one by one.

4. Source one: revenue no longer under-invoiced

Money/month = orders/month × lines per order × share of orders carrying the wrong list × share of items that are cheaper × share reaching the invoice × value of one line × average gap
Example 1,140 orders × 2.8 lines × 93% ≈ 2,969 lines carrying the wrong list. Half (17/34) are cheaper: 1,484 lines. 10% reach the invoice without anyone correcting them: 148 lines, 300,000 VND each, 18.3% short. About 8.1 million VND a month.

How to measure. Take one month of invoices and compare each line's unit price with the customer's price list (or with the customer's purchase order, if the customer pays by that). Count the lines invoiced lower that were never made up. That is your own company's miss rate.

Confidence: low to fair — because it rests almost entirely on the miss rate. In a company where the accountant checks every line against the customer's purchase order before invoicing, the miss rate is close to 0 and this source is close to 0: with 99% caught, it comes to 0.8 million.

5. Source two: no more adjustment invoices for over-invoicing

Over-invoicing does not lose revenue — the customer pays by its own price — but every line that slips through is one receivable that does not match, one reconciliation, one adjustment invoice.

Money/month = lines carrying the wrong list × share of items that are dearer × share reaching the invoice × minutes per adjustment ÷ 60 × cost per hour
Example 2,969 × 14/34 ≈ 1,222 dearer lines; 10% slip through: 122 lines, 20 minutes each to make the adjustment and reconcile with the chain: 41 hours. About 2.4 million VND a month.

How to measure. Count the downward adjustment invoices over three months whose reason was the unit price, and ask the person who makes them how long one invoice takes.

Confidence: moderate. The number of adjustment invoices can be counted exactly.

6. Source three: no catching and correcting prices line by line

The part that gets caught costs no money, but it costs people.

Money/month = lines carrying the wrong list × share priced differently from the customer's list × share caught × minutes to catch and correct one line ÷ 60 × cost per hour
Example 2,969 × 31/34 ≈ 2,707 lines priced differently; 90% caught, 1.5 minutes a line: 61 hours. About 3.7 million VND a month.

How to measure. Time one session of checking orders before invoicing, and divide by the number of lines whose price had to be corrected.

Confidence: high, in that it can be measured with a clock. These hours are money or capacity for other work — count them once.

Each wrongly priced line sits in only one of the three sources: either it reaches the invoice (under- or over-invoiced), or it gets caught. Nothing is counted twice.

7. Adding it up

Source90% caught99% caught
Revenue no longer under-invoiced8.15 m0.81 m
No more adjustment invoices2.44 m0.24 m
No catching and correcting line by line3.65 m4.02 m
Per month14.2 m5.1 m

At 1,140 orders a month, between 5 and 14 million VND a month, depending on how much your accountant catches. The right-hand column says something real: in a careful company, the value of this fix is the careful person's time; in a company where nobody checks, it is revenue.

8. What assumptions this ROI rests on

Today's price lists represent the price lists at the time of ordering. The gap between the two lists was measured on the price lists of 31/10, while the chain's prices change in batches. In another month the gap will be different — and its direction may flip.

The customer's list is correct. Switching orders to the customer's list only helps if that list is kept correct. Four of the 41 items had no price in the customer's list: for them, the price field is now empty instead of wrongly filled — the person entering the order still has to type it.

A list a person chose is kept. This fix replaces only the default list. If someone picks the wrong other list by hand, the system respects that choice — as intended, but it is a real gap.

Draft documents only. Orders submitted before the fix still carry the old list; the 1,061 does not vanish from history by itself.

The numbers to watch each week: the share of new orders carrying a list that is not the customer's — it must stay at 0 — and the number of price saves from the quick sales screen, with old and new prices, to know who is changing the price list.

9. Measure it in your own company

  1. Take a baseline. One query: 30 days of orders, the price list on the order against the customer's list (customer → customer group → parent group). Split by customer group — in the sample above, one group was wrong 93% of the time, the rest 15%.
  2. Measure the gap between the two lists on exactly the items that customer orders, by direction: how many items cheaper, how many dearer.
  3. Count the part that gets caught: lines whose price is corrected before invoicing, adjustment invoices for unit price.
  4. After four weeks, run step 1 again. If orders still carry the wrong list, find which order-creation route went around the fix.

Price is one half of an invoice line; the other half is quantity, and the article signed delivery note checked the same day covers that half.

10. What to remember

A pre-filled field is a decision made on the user's behalf. Here, it decided wrongly for 93% of one customer group's orders for a whole month, and nobody noticed because nothing raised an error. Put the customer's list on the order in one single place every order-creation route passes through; when there is no price, leave it empty rather than guess; and when a price is saved, leave a trace.

An empty price makes people ask. A wrong price filled in for them makes nobody ask at all.

The number of orders carrying the wrong list before and after the fix, the lines per order and the gap between the two price lists across 34 items were measured on the live system of a fresh-produce supplier to supermarket chains on the morning of 31/10/2026, anonymised. The value of one line, the share caught, minutes and wages are illustrative figures. Replace them with your own.

Read next