erpkaizen

Measuring the value

One screen for a delivery crew's day: 43% of notes posted before the truck delivers, and returns nobody can record

Has a measurement By 10 Nov 2026 About 10 min
Two cards on one phone screen: a delivery note already issued from stock still waits for the driver to record delivered and returned quantities; the vehicle card records kilometres and litres, read by AI from a photo. No real data. Delivery note Issued — not delivered Delivered 9 Returned 1 Signed slip ✓ photo taken Vehicle & fuel ODO 48 215 km Fuel 32.5 L AI reads photo One screen for a delivery crew's day returns back to stock, fuel to the right truck
One screen for the driver's day: a note already issued from stock still waits for delivered and returned quantities, and the vehicle card records kilometres and litres read from a photo.

The warehouse posts the delivery note as the truck leaves; the driver's screen read it as "done" and locked the returns field. Over 14 days, early-posted notes had a signed slip 1% of the time and a returned quantity 0.4%, against 89% and 15.5%. Reopen the note for the driver, add a vehicle & fuel tab that reads photos with AI — what that saves a month.

One screen for a delivery crew's day — how much does it save a month?

All it needs is delivery notes per day, the share the warehouse posts before the truck delivers, the number of trucks and the km each one drives a day. Every money figure follows from those. Change any of them.

Measured about 120 a day (1,722 notes in 14 days)
Measured 43%: 737 of 1,722 notes
Illustrative — put in your own fleet
Illustrative

Derived from the four numbers above

Notes posted before delivery per month–
Returns nobody records per month (before)–
Fuel spend per month–
Odometer + pump photos per month–
Assumptions — open to see and change every number

Customer returns

Signed delivery slip

Fuel

Matching fuel invoices to trucks

Reading photos

Each month: before and after A line going down is a saving; the dashed line going up is a new cost
Each month: before and after
A. Returns that reach the warehouse–
B. Disputes avoided by the slip–
C. Fuel above the norm recovered–
D. Hours matching fuel invoices–
E. Photo reading cost–
Net benefit per month–

The measured figures are the rates marked "measured"; the rest are illustrative. Set the early share and the trucks to zero and every line goes to zero — try it.

At a fresh-food distributor, the delivery trucks leave the warehouse early in the morning. To keep stock right hour by hour, the storekeeper posts the delivery note the moment the truck pulls out. Sensible — until you count. On the driver's phone, a posted note showed "Completed" and locked the delivered, support and returned fields. The driver saw "done" and never opened the note again: no photo of the signed slip, no returned goods recorded. Returns still happened — nobody could write them down.

We measured 14 days at that company. 43% of notes (737 of 1,722) were posted before the truck delivered. Of those, only 1% had a signed-slip photo (8 of 737), against 89% (150 of 168) on notes the driver completed; and 0.4% had a returned quantity (3 of 737), against 15.5% (153 of 985). Meanwhile the fleet sent odometer and pump photos into a group chat, and some 170 fuel e-invoices arrived over three months without being tied to any vehicle.

The change in this article is one screen for the driver's whole day: the "Deliveries" tab accepts notes already issued from stock, and a "Vehicle & fuel" tab replaces the group chat. We work out how much a month that saves, and which assumptions the number stands on.

1. What changes

A note issued from stock still waits for the driver

  1. The list shows "Issued — not delivered", not "Completed". Stock posted as the truck leaves is not goods in the customer's hands, and the screen now says exactly that.
  2. Delivered, support and returned can still be recorded. The quantity issued from stock does not change — these three are recorded figures. Every edit keeps its history: who, when, old value to new value.
  3. Pressing Complete turns the returned goods into a stock receipt — into a clearance warehouse or back into the selling warehouse, configured per company, because some returns can still be sold. Change the returned figure later and the receipt is rebuilt to match.
  4. A note that already has an invoice is locked, and the message says who to ask: accounting.

The "Cancel" button also disappears on an issued note; in its place is one line: if the customer refused an item, record it as returned. This continues the article on customer returns and the one on signed delivery slips: the mechanism existed, half the notes simply could not reach it.

A sample driver's delivery list on a phone: three notes for three sample stores, each labelled Issued — not delivered; the bottom tab bar has Deliveries and Vehicle & fuel
Three notes posted as the truck left, now shown as "Issued — not delivered" instead of "Completed". Sample data; the screen is in Vietnamese.
An issued note open on a phone: a button to photograph the signed slip at the top, each item with issued, support, delivered and returned fields; at the bottom a hint about recording returns and the Complete button, with no Cancel button
An issued note can still record delivered, support and returned quantities and the signed slip. Sample data.

Vehicle & fuel

  1. The driver picks a vehicle (the phone remembers the last one), presses one of three buttons — Start, Refuel, Finish — and takes a photo.
  2. The AI reads the number on the odometer, or the litres, unit price and amount on the pump, and checks litres × price = amount. The figures appear under the photo; the driver taps "Correct" or fixes them.
  3. Each refuel becomes a draft fuel expense claim, deducted from any open cash advance. The fuel station's e-invoice that arrives later is matched to the refuel by amount, litres and date.
  4. The manager gets an analysis button: kilometres, litres, money, L/100 km and cost per km by vehicle and by driver; and alerts — over the norm, odometer going backwards, more fuel than the tank holds, idle vehicle, overdue advance, invoice with no vehicle.
The Vehicle and fuel tab for a sample driver: a reminder that the start odometer has not been photographed, the current vehicle preselected, three large buttons Start, Refuel, Finish, and a Cash advance section
The Vehicle & fuel tab: pick the vehicle once, three photo buttons, the advance. Sample data.
The manager's fleet analysis for three sample vehicles: tiles for total kilometres, litres, fuel cost, litres per 100 km, cost per km, share of refuels with an e-invoice, advances held and items to review; vehicle cards below
The manager's analysis button: three sample vehicles over 30 days. Sample data.

2. How well the machine reads photos

We ran the reader on 11 real photos drivers took in one day. 8 the machine marked "confident" — checked by eye, all 8 right: five- and six-digit kilometre readings on five different dashboards, and one pump at 66.375 L × 31,640 = 2,100,105 VND. 3 the machine flagged "not sure" itself: two taken at night, one with glare. None was read wrong while marked confident.

The rule follows: on a "not sure" photo the driver checks the number on the spot and fixes it if needed; if the driver changes the amount read from a pump, the claim waits for the manager, because that is money. A changed kilometre reading is only logged — a night shot of a dashboard is hard to read, and that is normal.

3. First stream: returned goods make it back to stock

Benefit/month = early-posted notes × (return rate when the driver completes − return rate being recorded) × value per return × share that becomes a loss
Example 120 notes a day, 43% posted early: about 1,548 notes a month. 15.5% − 0.4% = 15.1% of those have returns nobody records: about 234 a month — consistent with the roughly 110 counted in 14 days. Each return worth 150,000 VND, 30% of that lost (spoiled, invoiced in full and then disputed, wrong book stock). 234 × 150,000 × 30% ≈ 10.5 million VND/month.

How to measure. A month after the change, count early-posted notes with a returned quantity. If the rate climbs towards the 15% of driver-completed notes, the extra count is exactly the returns that used to fall through. Value per return comes from the returned-goods receipts themselves.

Confidence: high on the count (both rates were measured), low on the money — 150,000 and 30% are illustrative, and this is the largest line in the article.

4. Second stream: quantity disputes avoided thanks to the signed slip

Benefit/month = early-posted notes × (89% − 1%) × share of slip-less notes that turn into a dispute × value of a dispute
Example 1,548 × 88% ≈ 1,362 notes a month without a slip. If 0.5% of those turn into an argument about quantity with the store, each worth 400,000 VND. ≈ 2.7 million VND/month.

Confidence: low. The slip rate was measured; the dispute rate and dispute value nobody has counted. A slip is evidence — its value only shows on the day someone argues.

5. Third stream: fuel over the norm

Benefit/month = fuel spend × share over the norm × share recovered once it is visible
Example 12 vehicles × 60 km/day × 26 days × 12 L/100 km × 21,500 VND ≈ 48.3 million VND of fuel a month. 5% over the norm, half of it recovered once seen. ≈ 1.2 million VND/month.

How to measure. L/100 km only means something over a period of a week or more: drivers fill by round amounts, not to a full tank, so a single refuel gives a meaningless figure. Set a norm per vehicle, run four weeks, compare each vehicle's L/100 km with its own norm.

Confidence: medium. Before the change there were no kilometres anywhere, so nobody knows today's overrun — 5% is an assumption, and the first four weeks exist to replace it with a real number.

6. Fourth stream: hours matching fuel invoices to vehicles

Benefit/month = refuels × (minutes matching by hand − minutes glancing) × cost per hour
Example 12 vehicles × 5 refuels = 60 invoices a month. Matching one invoice to a vehicle and driver by hand — scrolling the chat, finding the photo, checking the amount — 10 minutes; glancing at an auto-matched refuel 1 minute; 70,000 VND/hour. 60 × 9 min × 70,000 VND/hour ≈ 0.63 million VND/month.

Confidence: medium. The smallest line, but the one accounting feels most.

7. To subtract: reading photos

About 2.4 photos per vehicle per day (start, finish, the occasional refuel), 1,000 VND per read: about 0.75 million VND a month for 12 vehicles. It is the only line in the chart that goes up.

8. Adding it up

LinePer monthPer year
Returns back to stock10.52 m126.2 m
Disputes avoided by the slip2.72 m32.7 m
Fuel overrun recovered1.21 m14.5 m
Hours matching fuel invoices0.63 m7.6 m
Reading photos−0.75 m−9.0 m
Net benefit14.33 m172.0 m

Amounts in VND.

The slope chart in the calculator draws each line from "before" to "after" on one money axis. Four lines go down, one dashed line goes up. What it shows most clearly: nearly three quarters of the money is in customer returns — that is, in fixing one status label and unlocking three number fields, not in the AI.

9. What this ROI stands on

The share of notes posted early. Here it is 43%. Where the warehouse waits for the driver to complete before posting, the first two lines are zero — and that is the right answer: the problem does not exist there. Set this field to 0 in the calculator to see it.

Value and loss share of a return. These two numbers decide the largest line, and both are illustrative. Returns that can be resold lose little; fresh produce loses a lot.

Whether drivers actually record. Unlocking a field makes nobody fill it in. The yardstick is the share of early-posted notes with a slip and a returned figure after a month — if it does not move towards 89% and 15%, the benefit has not arrived.

The overrun share. Without kilometres there is no norm to exceed; 5% is only a place to start.

Set the early-posted share and the number of vehicles to 0: every line goes to 0, cost included.

10. Measure it at your own company

  1. Take a baseline. Count 14 days of delivery notes along the two paths — posted before delivery, and completed by the driver — and compare the share with a slip and with a returned figure. The gap between the two is what is falling through.
  2. Set a norm and tank capacity for each vehicle before switching on the photos, so the first week already has something to compare.
  3. Measure again after 7 and 30 days: slip rate, return rate, number of returned-goods receipts, L/100 km per vehicle, share of refuels matched to an e-invoice — then replace the calculator's numbers with real ones.

11. What to remember

One wrong status label can hide half the work. Posting stock early is right for inventory; the driver's screen reading it as "done" is wrong for everything that follows. Fixing that is cheaper than any AI in this article, and worth more.

The system did not lose the returns. It just left no place for the person who wanted to record them.

Figures marked as measured come from 14 days of live operation at a food distributor, anonymised; the 11 odometer and pump photos are real and were checked by eye. The value per return, dispute rate, number of vehicles, kilometres, norm, fuel price, overrun share and AI cost are illustrative. Screenshots were taken on sample data. Replace them with your own numbers.

Read next