A customer says a delivery was short, the warehouse says it was complete and the driver says he handed over everything on the list. Without shared evidence, each side defends its own count, claims drag on and credit notes are issued by default. Short shipment reconciliation compares what was ordered, what was loaded and what was received, and records proof at each step so the true gap can be traced to its cause. Teams that capture evidence early close claims faster and fix problems at their source. To see how this could work for your operation, you can review a reconciliation workflow with our team.
Returns, reverse logistics and delivery claims
Close the Gap Between What Was Ordered, What Was Loaded and What Was Received
iFactory AI links order, load and delivery counts with scan evidence, so short shipment claims are settled with facts instead of arguments.
Three counts that must agree
Ordered
Loaded
Received
Variance
The claim problemEveryone Has a Count and Nobody Has Proof
Quantity disputes are among the most common delivery claims, and the time spent resolving them is often far greater than the value of the goods in question. Customer service, dispatch, the warehouse and the driver each hold part of the story, but rarely the same version of it.
Order is placed
The customer expects an agreed quantity
Goods are loaded
The warehouse believes the load is complete
Delivery is made
The customer counts what arrives
Claim arrives
Each party defends its own count
Without evidence captured at each step, the default outcome is a credit note. That feels quick, yet it hides the real cause, so the same shortages keep returning week after week.
The three quantitiesOrdered, Loaded and Received Tell Three Different Stories
Reconciliation starts by keeping three numbers apart. Each one answers a different question about where the shortage began.
Ordered
What the customer asked for and what was confirmed
Loaded
What was scanned or counted onto the vehicle
Received
What the customer accepted at the door
Variance
The gaps between the three, with reasons
Short shipment rate = (ordered quantity - received quantity) / ordered quantity
Reading the gapsWhat Each Gap Usually Means
The position of the gap points to where to look. A gap between ordered and loaded is a warehouse issue. A gap between loaded and received is a transit or receiving issue.
1
Ordered higher than loaded
The shortage began in picking, stock availability or loading. The customer never had a chance to receive it.
2
Loaded higher than received
Goods may have been lost, damaged, mis-delivered or miscounted at the customer site.
3
Received higher than ordered
An over-delivery, which causes returns and invoicing problems of its own.
4
All three agree but the customer disputes
The claim may relate to quality or an order entry error rather than quantity.
Treat over-deliveries as seriously as short ones. They create returns, invoice corrections and stock errors that surface weeks later.
See Where Your Quantity Gaps Really Begin
Share a few weeks of delivery claims and see how iFactory AI would trace each variance back to the order, load or delivery step.
Where variances beginAn Illustrative Split of Shortage Sources
Every operation has its own pattern, but most find that a handful of causes account for most of the claims. This split is an example, not a benchmark.
35 percent: Picking and loading
Wrong quantity picked or loaded, or stock not available.
25 percent: Customer receiving
Miscounts, unit-of-measure confusion or late counts.
25 percent: Transit and handling
Damage, loss or goods left on the vehicle.
15 percent: Order and data errors
Wrong quantities entered or changed after confirmation.
Measure your own split over a few months. The biggest slice tells you where improvement effort will pay back first.
Scan evidenceFour Layers of Proof From Warehouse to Doorstep
Evidence is most useful when it is captured at the moment of the event, not rebuilt afterwards from memory or paperwork.
Load scan
Each case, tote or pallet is scanned onto the vehicle against the order.
Seal and condition check
Photos or checks confirm the state of the load at departure.
Delivery scan
Items are scanned off at the customer site, with exceptions noted.
Customer sign-off
The receiver confirms the count, or records the dispute at once.
Even partial evidence helps. A load scan with a delivery signature already settles many disputes in minutes.
Discrepancy reasonsA Reason Code List That Makes Patterns Visible
Reason codes turn free-text complaints into data. Keep the list short, clear and used consistently by every team.
| Reason code | Typical source | Evidence that helps | Usual action |
|---|
| Short at pick | Warehouse stock or picking | Pick records and stock counts | Correct stock, retrain, credit if needed |
| Loading error | Dispatch and load check | Load scan against order | Re-ship and fix the check |
| Lost or damaged in transit | Vehicle and handling | Condition photos and handover notes | Carrier claim or internal write-off |
| Customer count error | Receiving site | Delivery scan and sign-off | Decline the claim or agree a count |
| Substitution or unit change | Order and master data | Order and invoice history | Correct master data and communicate |
| Order entry error | Sales or customer service | Original order and amendments | Correct order, fix process |
The reconciliation flowFour Steps From Delivery to a Closed Claim
A clear flow ensures every discrepancy gets the same treatment, whoever receives the call.
1
Capture
Record the claimed quantity, reason and evidence at the time of delivery or call.
2
Compare
Match ordered, loaded and received counts and review scan history.
3
Decide
Assign the cause and the outcome: re-ship, credit, decline or investigate.
4
Close and learn
Record the result and feed it into trend reports.
Speed matters. A claim settled within a day is cheaper and keeps the customer relationship intact.
Approval and closureMatch the Level of Approval to the Value and Risk
Not every variance needs the same scrutiny. Tiered approval keeps small claims moving and gives larger ones proper review.
Auto-close
Small variances within agreed tolerance with matching evidence.
Supervisor review
Medium variances or repeated issues for the same customer or route.
Manager and finance review
Large claims, disputed counts or suspected loss.
Tolerances should be written down and agreed with customers. A clear rule avoids negotiation on every small case.
A worked exampleOne Order From Ordered to Closed
Consider one illustrative order of 100 cases. The numbers show how reconciliation finds the cause.
| Step | Count | What the evidence shows |
|---|
| Ordered | 100 cases | Confirmed order |
| Loaded | 98 cases | Load scan shows two cases not picked |
| Received | 97 cases | Delivery scan shows one case damaged and refused |
| Variance | 3 cases | 2 short at pick, 1 damaged in transit |
| Outcome | Credit 1, re-ship 2 | Warehouse stock check and packaging review opened |
Without scans, the customer might have claimed three missing cases and received a credit with no learning at all.
Repeat patternsFind the Hot Spots Behind the Claims
Look across weeks and months, not just individual orders. Patterns by product, route, picker or customer point to fixable causes.
Claim pattern
Frequent
Occasional
High value
Fix the process
Chronic, costly shortages deserve root cause work
Investigate each case
Large claims need individual review
Lower value
Standardise the handling
Small repeating claims are process noise
Monitor
Low impact, track for change
Chronic small claims are often the most valuable to fix because they happen so often.
Who does whatReconciliation Is a Team Effort
Quantity accuracy runs through the whole delivery chain, so the work belongs to more than one function.
Warehouse supervisor
I make sure picks and loads match the order before the door closes.
Driver
I scan at delivery and record any dispute with the customer on the spot.
Customer service
I log claims with a reason code and check the evidence first.
Finance
I approve credits against evidence and track the total cost.
Share the same dashboard with all four roles, so each can see how their step affects the result.
What improvement looks likeBefore and After Evidence-Based Reconciliation
Track the same measures before and after introducing scans and codes. This view is illustrative.
Paper and memory
Claims credited without evidence
Visibility of repeat causes
Scan-based reconciliation
Claims credited without evidence
Visibility of repeat causes
The bars are illustrative. Measure your own baseline before the pilot so benefits are credible.
With and without evidenceWhy Claims Cost Less When Proof Exists
Evidence changes the conversation with the customer from opinion to fact.
Claims without evidence
Customer's count is accepted by default
Credits issued to keep the peace
Causes remain hidden
Disputes repeat
Claims with evidence
Counts are compared with scans
Credits match verified shortages
Causes are coded and tracked
Disputes fall over time
Customers also benefit. Fair, fast resolution builds trust and encourages them to confirm counts at the door.
Data flowConnect Order, Warehouse and Delivery Data
Reconciliation depends on information flowing between systems that rarely talk to each other.
Order managementWarehouse and loading scansDelivery app and signatures
Reconciliation layer
Claim workflowCredit and re-ship decisionsTrend reports
Start with the data you already have and add scans where the gaps are largest. To plan the data flow, ask our team about connecting order and delivery data.
Key measuresSix Numbers That Show Whether Reconciliation Works
| Measure | What it shows | Why it matters |
|---|
| Short shipment rate | Share of ordered quantity not received | Overall accuracy |
| Claims per thousand orders | How often customers raise disputes | Customer experience |
| Claim resolution time | Days from claim to closure | Cost and satisfaction |
| Evidence rate | Share of claims with scan evidence | Fairness and speed |
| Cost per claim | Handling and credit cost | Business case |
| Repeat cause share | Claims from the same cause | Root cause progress |
RolloutFive Steps From Pilot Route to Standard Practice
A focused pilot proves the value without disrupting the whole operation.
1
Pick a pilot
Choose a route or customer group with frequent quantity claims.
2
Set the baseline
Record claim rates, resolution time and credits for a few weeks.
3
Add evidence capture
Introduce load scans, delivery scans and reason codes.
4
Run the workflow
Apply the reconciliation flow and approval levels.
5
Review and scale
Compare results with the baseline and extend to more routes.
Ordered, loaded and received counts captured for every order
Load scans match the order before departure
Delivery scans and customer sign-off recorded
Reason code list agreed and trained
Tolerance rules written and shared with customers
Approval levels set by value and risk
Weekly review of repeat causes
Owner named for claim data quality
Expert reviewWhat a Distribution Operations Director Would Check First
Reconciliation works when evidence is captured at the point of action and reason codes are used honestly. If drivers and pickers see scans as extra work with no benefit, quality of data falls quickly.
Verdict
Strong when scans are simple, codes are few and results are shared with every team.
Watch for
Credits issued by default and codes that default to other.
Do next
Pilot one route, compare claim handling time before and after, and show the results to drivers.
Frequently asked questionsWhat Delivery Teams Ask About Short Shipment Reconciliation
How do we start if we have no scan data today?
Begin with simple evidence you can capture quickly, such as a load check against the order and customer sign-off with the count noted. Add barcode scans on the busiest routes first. Even partial evidence settles many disputes faster and shows where fuller scans would help most.
Plan a first evidence step.
What tolerance should we allow before a claim is investigated?
Tolerances depend on product value, order size and customer agreements, so there is no universal number. Write tolerances down, agree them with key customers and review them with the data. Small variances can be auto-closed, while larger ones follow review.
Ask about setting tolerances.
How do we handle disputes where the driver and customer disagree?
Compare the load scan, delivery scan and any photos, and ask the customer to confirm counts at the door whenever possible. Consistent evidence usually settles the case, and the outcome is recorded with a reason code for learning.
See a dispute example.
Do reason codes really matter?
Yes. Without them, claims remain stories. With them, you can count causes, see repeat patterns and focus fixes where they pay back. Keep the list short and review it quarterly.
Ask about reason code design.
How do we show the business case?
Record baseline claim volume, handling time, credits issued and repeat causes, then compare after the pilot. Use conservative cost assumptions and include time saved by customer service and finance.
Plan a business case.
Ordered, loaded, received: one version of the truth
Settle Delivery Quantity Claims With Evidence, Not Opinion
Book a session with iFactory AI to review your claim data, plan scan evidence at load and delivery and build a reconciliation workflow your teams and customers will trust.
