What Proof Wins Shortage Deductions
Shortage deductions are one of the most common CPG deduction types. Here is the evidence finance teams need to prove what shipped, what arrived, and what should be recovered.
Shortage deductions are usually simple on the surface.
The retailer says it received less than what the brand invoiced. The brand believes it shipped the full order. The payment comes in short, and someone in finance has to figure out which version of the story the documents support.
That last part is the work.
A shortage dispute does not win because the brand says the product shipped. It wins when the evidence makes that conclusion easy for the reviewer to see.
The Reviewer Needs A Clean Chain Of Proof
A good shortage packet tells the story in order.
What did the retailer order?
What did the brand invoice?
What did the warehouse ship?
What did the carrier accept?
What did the retailer receive?
What did the retailer deduct?
If the packet answers those questions clearly, the reviewer can follow the claim. If the packet is a folder of loosely related documents, the reviewer has to do the work. That is where many valid shortage disputes fail.
The packet should make the mismatch obvious.
Start With The Transaction
The first layer is the commercial record.
The purchase order shows what the retailer ordered. The invoice shows what the brand billed. The remittance shows what the retailer paid and what it deducted.
Those three documents define the shortage.
If the PO ordered 100 cases, the invoice billed 100 cases, and the remittance deducted 12 cases, the team has a clear claim to investigate. If those numbers already disagree before shipment evidence is added, the brand needs to solve the data mismatch first.
Many teams skip this step because they are hunting for the BOL or POD. That creates problems later. The shipment proof matters, but the reviewer still needs to understand the transaction being disputed.
Then Prove What Left The Brand
The second layer is shipment evidence.
The bill of lading is the starting point. It shows what was tendered to the carrier. A signed BOL helps establish that the shipment left the brand or warehouse in the stated quantity and condition.
The packing list can support the case-level detail. Warehouse shipping confirmation can help when the BOL is not granular enough. Weight tickets may help corroborate quantity when case counts are disputed.
The goal is not to attach every document the team can find.
The goal is to prove what left.
Then Prove What Arrived
The third layer is receiving evidence.
The proof of delivery matters because it shows what happened at the receiving end. Was the delivery signed clean? Were there shortage notes? Was there damage? Was the shipment received at the DC or somewhere else in the network?
This is where shortage disputes often become harder than they look.
The brand may have strong internal shipping proof, but the retailer or distributor may rely on receiving counts. If receiving documentation shows a different quantity, the dispute has to address that difference directly.
A strong packet does not pretend the retailer's record does not exist. It explains why the brand's evidence should control the outcome or why the retailer's receiving record appears wrong.
Match Units Before Filing
Shortage disputes can fail because the packet mixes cases, units, pallets, and eaches without reconciling them.
The reviewer should not have to guess whether 10 cases means 120 units or 240 units. The packet should make unit conversion clear. If the retailer deducted eaches but the warehouse shipped cases, show the pack size and translate the quantities.
This sounds small. It is not.
A valid claim can look weak when the unit math is hard to follow.
Do Not Let Missing PODs Kill The Queue
Many shortage disputes stall because the POD is sitting in a carrier portal, a 3PL folder, or someone's inbox.
By the time finance asks for it, the dispute window may already be closing. That turns document retrieval into the bottleneck.
The better process is to know where PODs live before deductions arrive. For each carrier or 3PL, the team should know who has access, what reference number is needed, and how long retrieval usually takes.
Shortage recovery gets much easier when POD retrieval is a standard step instead of a scavenger hunt.
Watch For Patterns
One shortage may be a receiving error.
A pattern of shortages may be a root-cause issue.
If the same carrier, DC, lane, item, packaging type, or retailer keeps appearing, finance should flag the pattern. The recovery team may win individual disputes, but the larger opportunity is stopping the same deduction from recurring.
That is where shortage data becomes useful beyond AR.
It can point to packaging weakness, pallet instability, label problems, picking errors, carrier issues, or retailer receiving behavior that needs escalation.
Where PackPay Fits
PackPay treats shortage recovery as evidence work.
The system should know which documents are needed, where they are likely to live, which quantities need to match, and when a missing document should stop the claim from being filed.
For a lean CPG team, that changes the math. A shortage deduction should not sit untouched because the POD is hard to find or the packet takes too long to assemble.
If the product shipped, the evidence should be able to prove it.