Warehousing, wholesale and distribution · OD-03 · Distribution: dispatch and returns

The goods left the warehouse. Then they came back.

Manufacturers report that distributors are not ready for product marking and scanning, and that shipments are being returned. The cause often lies in the warehouse: at dispatch, it is unclear what was actually loaded.

Platform: Goods Flow

8–9 / 10

Shipments returned due to scanning and display errors, according to one manufacturer.1

2 / 20

Distributors actually ready for marking, according to the same manufacturer.1

2–3 hours

Time spent on the evening order report before automation, in an example from a sponsored article.2

Goods not scanned at dispatch become errors on the road.

Who it is for

Distributor owner
Returned trips and lost sales.
Warehouse manager
Picking and loading.
Logistics
Trips and drivers.
Sales director
Stock visibility for sales agents.

Where the problem lies

  • Loading by list

    When goods are loaded onto a truck by list, what actually left the warehouse is unknown.

  • Stock not visible to agents

    Agents take orders for goods that are not in the warehouse; the shortage only becomes clear in the evening.

  • Returns not recorded

    If returned goods and the reason for return are not recorded, stock and code data become inaccurate.

  • Orders picked at night

    The evening report and picking keep warehouse staff working late into the night.

How the loss is calculated

Returned tripsreturned shipments per month × cost per trip
Lost salesunfulfilled orders per month × average margin per order
Night workovertime hours per employee per month × number of employees × hourly rate
Re-sortingreturned cases per month × handling time per case (hours)

Calculate with your data

Returned Shipment Cost: Current State vs. Your Scenario

This calculator estimates the extra monthly transport cost caused by shipments that are sent from the warehouse to points of sale and then returned.

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 / 4 values entered

Enter your operating figures to see the estimate.

Results are estimates, not guaranteed savings. Only part of your returns may stem from loading or labelling errors. Others may be caused by closed stores, cancelled orders or other reasons, so analyse WMS returns by reason code first. The scenario rate is your own assumption and cannot be confirmed without an audit and measurement. Implementation costs, timelines, penalties and store-side equipment are not included.

Formulas and assumptions

This calculator estimates the extra monthly transport cost caused by shipments that are sent from the warehouse to points of sale and then returned. Enter all values from your own data: monthly shipment count, the return rate recorded in your WMS, and the actual extra trip cost of one returned shipment. You define the scenario return rate yourself. It is not presented as an achievable outcome. The scope is limited to returned-trip cost. Lost sales, overtime or night-shift hours and re-sorting labour are excluded and are not added to this figure.

Returned-trip cost, current state
Monthly shipments (shipments/month) × current return rate (%) ÷ 100 × trip cost per returned shipment (currency units/shipment) = monthly cost (currency units/month).
Returned-trip cost, your scenario
Monthly shipments (shipments/month) × your scenario return rate (%) ÷ 100 × trip cost per returned shipment (currency units/shipment). This is an assumption, not a forecast.
Difference between current state and scenario
Current monthly cost minus scenario monthly cost (currency units/month). If the scenario rate is higher than the current rate, the difference is shown as 0. This is an estimated cost gap for returned trips only, not a guaranteed saving.

Facts and global practice

  • Juice and beverage manufacturer

    8–9 out of 10 shipments return to the plant due to scanning and display errors; a driver visits 5–7 outlets a day instead of 10–15.1

  • Same manufacturer

    Of 20 distributors, only 2 are actually ready.1

  • UzBev association

    There is no scanner standard for retail and no mechanism for returning unreadable codes.1

  • Juice manufacturer, sponsored article

    Before automation, no one could see actual warehouse stock, the evening report took 2–3 hours and orders were picked at night; afterwards, an agent visited 32 outlets a day instead of 20.2

  • IBC Global

    3PL and distribution account for 28% of new warehouse demand.3

These figures reflect individual companies' experience, not industry averages. The result in the sponsored article has not been independently verified.

Scanner-tracked from warehouse to outlet

Warehouse data is connected to the agent system, picking and loading are confirmed by scanner, and returns are recorded with a reason. The existing agent app is not replaced; it is integrated.

  1. 01Order
    • From the agent system
    • Stock check
    • Picking task
  2. 02Picking
    • Picking with a handheld terminal (TSD)
    • Code and quantity
    • During the day
  3. 03Dispatch
    • Scanning per truck
    • Shipping document
    • For ESF/ETTN
  4. 04Return
    • Reason
    • Restocking
    • Codes

Modules

The current maturity level is shown next to each module.

WMS and TSDPicking, loading and returns by scannerCommercially available
Agent app integrationOrder and stock data exchangeCommercially available
1C integrationDocuments and stockCommercially available
Re-linking returnsReturned cases and codesCommercially available

How we start

  1. 01

    Dispatch audit

    Picking, loading and returns are observed over several days.

    Outcome: error map.

  2. 02

    Warehouse scanning

    Picking and loading with TSD.

    Outcome: clear view of what is on each truck.

  3. 03

    Integration

    The agent system and 1C are connected.

    Outcome: agents see actual stock.

  4. 04

    Subscription

    Returns are tracked by reason.

    Outcome: monthly report.

What is measured

Returned shipmentsReturned / total, by reasonWMS
Loading errorsDifference between documented and actual loadTSD log
Picking timeFrom order to truckWMS
Stock accuracyDifference between system stock and physical countWMS

What is needed to start

  • Person responsible for warehouse and logistics
  • Access to the agent system and 1C
  • Daily order and trip data
  • One warehouse for the pilot

What we do not promise

  • Exact timeline and price without an audit
  • Government decisions and deadlines
  • Warehouse space expansion
  • Unmeasured results or savings
  • Supplying equipment on the store side

Self-check

  1. Are goods scanned when loaded onto trucks?
  2. Do agents see actual warehouse stock?
  3. Are orders picked during the day?
  4. Are returned shipments recorded with a reason?
  5. Are returned goods restocked and their codes re-linked?
  6. Is the evening report generated automatically?
  7. Are loading errors measured?
  8. Are marked goods dispatched by code?
  9. Is the agent app connected to the warehouse system?
  10. Is there a person responsible for dispatch?

Dispatch audit

We observe picking, loading and returns at your warehouse and show where errors occur.

  • Error map
  • Scanner process plan
  • WMS: implementation fee and monthly subscription

Sources

  1. Statements by manufacturers and UzBev. gazeta.uz, 15.04.2026.
  2. Juice manufacturer's automation experience (sponsored). spot.uz, 31.07.2026.
  3. IBC Global, Central Asia Warehouse Summit (Tashkent). bizmedia.kz, 20.04.2026.