Water and beverages · WB-03 · Code errors in distribution
The goods left the plant. They came back with a code error.
Manufacturers report slower deliveries and returned shipments. The cause is often not at the plant but at the point where the code chain breaks between plant, warehouse, vehicle and shop.
Platform: Goods Flow
Shipments returned to the plant because of scanning and display errors, according to one manufacturer.1
Outlets a driver reaches per day, previously 10–15, according to the same manufacturer.1
Distributors actually ready for marking, according to the same manufacturer.1
A code may be applied correctly at the plant. If it cannot be read at dispatch, the goods still come back.
Who it is for
- Distribution Director
- Delivery runs, returns and number of outlets.
- Warehouse Manager
- Scanning at dispatch and receiving returns.
- Logistics
- Routes, drivers and vehicle loads.
- Chief Accountant
- Matching returned goods with the ESF (electronic invoice).
Where the problem lies
No scanning at dispatch
If pallets or cases are loaded by count rather than by code, what is on the vehicle may differ from the documents.
Delivery run results are not visible
Which outlet rejected goods, and why, is not known until the run is finished.
Codes cannot be read at the outlet
If a small shop has no scanner or the code cannot be read, the goods are returned or left without documents.
Returned goods drop out of the chain
If returned case and unit codes are not re-linked, they become new errors in the warehouse.
How the loss is calculated
| Returned delivery runs | Returned shipments (per month) × cost per delivery run |
|---|---|
| Lost outlet visits | (planned − actual outlets visited per day) × average sales per outlet visit |
| Additional transport | Additional vehicles × daily cost per vehicle |
| Rework | Returned cases (per month) × re-sorting time per case (hours) × hourly labour rate |
Calculate with your data
Code-related returned shipments: re-delivery and re-sorting cost per month
This calculator estimates the monthly cost of shipments returned because of code errors (unread, wrong or unlinked codes).
Use spaces for thousands and a dot or comma for decimals. Use the same currency throughout.
Values stay in this page and are not sent to the server.
Scenario estimate
0 / 6 values entered
Enter your operating figures to see the estimate.
Enter only returns whose recorded reason is a code error. The scenario return count is your own target and is not guaranteed to be achievable. If your re-delivery cost per return already includes re-sorting labour, do not add the labour result to it, as that would double count the cost. The calculator does not total re-delivery and labour costs. Firm timelines, prices and outcomes can only be determined after an audit and measurement.
Formulas and assumptions
This calculator estimates the monthly cost of shipments returned because of code errors (unread, wrong or unlinked codes). It calculates the re-delivery cost for your current situation and for a scenario you define, and shows the difference between them. The labour cost of re-sorting returned boxes is shown as a separate result. Enter all values from your own WMS, TMS and driver app data. Lost outlet sales, extra vehicles, fines and investment costs are excluded. Results are estimates, not guaranteed savings.
- Re-delivery cost: current
- Returned shipments per month (shipments/month) × re-delivery cost per shipment (currency/shipment).
- Re-delivery cost: scenario
- Scenario returned shipments (shipments/month) × re-delivery cost per shipment (currency/shipment). This is a calculation based on your target, not a guarantee.
- Re-delivery cost difference: current vs scenario
- (Current returns − scenario returns) (shipments/month) × re-delivery cost per shipment (currency/shipment). Negative values are shown as 0. This is an estimated difference, not guaranteed savings.
- Labour cost of re-sorting returned boxes: current
- Returned shipments (shipments/month) × boxes per shipment (boxes/shipment) × re-sorting time (minutes/box) ÷ 60 × hourly labour cost (currency/hour). This is shown separately from re-delivery cost. If your re-delivery cost already includes this labour, do not add the two together.
Facts and global practice
Juice and beverage manufacturer
8–9 out of 10 shipments are returned to the plant because of scanning and display errors.1
Same manufacturer
A driver visits 5–7 outlets per day instead of 10–15; one driver serves 20 shops instead of 40.1
Same manufacturer
Only 2 out of 20 distributors are actually ready.1
Carbonated soft drink and water manufacturer
Distributors are not ready; driver time per outlet has increased several-fold, sometimes tens of times; rail shipments have been suspended.1
UzBev Association
The country has approximately 85,000 retail outlets; about 90% of sales go through markets and small shops.1
UzBev Association
No scanner standard has been developed for retail; there is no mechanism for returning unreadable codes.1
The figures reflect individual manufacturers' own experience and are not industry averages. The source does not state why rail shipments were suspended.
One code flow from plant to outlet
Every handover is confirmed by scanning, and the result is visible without waiting for the delivery run to finish.
- 01Dispatch
- Pallet-level scanning
- Vehicle load
- Dispatch document
- 02Delivery run
- Route
- Driver app
- Status by outlet
- 03Outlet
- Delivery confirmation
- Unread code record
- Return
- 04Accounting
- ESF
- Return linking
- Stock
Modules
The current maturity level is shown next to each module.
| Warehouse and handheld terminals (WMS) | Dispatch by pallet and case, receiving returns | Commercially available |
|---|---|---|
| Transport and delivery runs (TMS) | Route, vehicle load, delivery run status | Commercially available |
| Driver or sales agent app | Recording delivery and unread codes at the outlet | Engineering capability |
| Re-linking returns | Re-placing returned cases and units by code | Engineering capability |
| Asl Belgisi and 1C integration | Dispatched and returned codes in documents | Commercially available |
How we start
- 01
Distribution audit
Several delivery runs are observed, and returns are recorded by cause.
Outcome: map of break points.
- 02
Scanning at dispatch
Dispatch by pallet and case is introduced in the warehouse.
Outcome: the vehicle contents are known exactly.
- 03
Delivery run and outlet
The driver app is piloted on one route.
Outcome: delivery run results are visible during the day.
- 04
Scale-up
Remaining routes and distributors are connected.
Outcome: monthly indicators.
What is measured
| Returned shipments | Returned / total, by cause | WMS, TMS |
|---|---|---|
| Outlets per day | Outlets delivered per driver | Driver app |
| Unread codes | Number of codes unread at outlets | Driver app |
| Dispatch time | Time to load one vehicle | WMS |
| Return linking | Difference between returned and re-placed codes | WMS, Asl Belgisi |
What is needed to start
- Person responsible for distribution
- List of routes and delivery runs
- A driver for a pilot on one route
- Test access to the warehouse system and 1C
What we do not promise
- Firm timelines and prices without an audit
- Government decisions and deadlines
- Changes to line software without the equipment supplier's permission
- Unmeasured results or savings
- Supplying equipment on the distributor and shop side
Self-check
- Are pallets and cases scanned at dispatch?
- Does the list of codes on the vehicle match the dispatch document?
- Are returned shipments recorded with their cause?
- Are delivery run results visible before the run is finished?
- Is the number of outlets each driver reaches per day measured?
- Are unread codes recorded at the outlet?
- Are codes of returned goods re-linked?
- Has distributor readiness been assessed?
- Are dispatched and returned codes correctly reflected in the ESF?
- Is there a person responsible for distribution?
Distribution audit
We trace the code flow from plant to outlet and identify where returns and lost time occur.
- Map of break points
- Analysis of returns by cause
- Step-by-step plan
Other solutions in this industry
- WB-02Line speed after marking
- WB-04Code and stock reconciliation
- WB-05Total cost of ownership of a marking system
- WB-06Production lines during internet and power outages
- WB-07Filling Line Efficiency (OEE)
- WB-08Energy in bottle production
- WB-09Sugar: quota, excise and labelling
- WB-10Export batches and codes
Sources
- Statements by manufacturers and UzBev. gazeta.uz, 15.04.2026.