Short-delivery / shortfall
Did fewer units arrive than you billed, and was the claim raised within the relevant delivery window?
Evidence: Signed POD, ASN, invoice, received quantity
You supply Coles, Woolworths, Metcash, ALDI, or Costco, and money comes off your remittance under promotion, short-delivery, DIFOT, shrinkage, or a prior credit. We rebuild the document chain and mark every line supportable, missing proof, worth challenging, or Code risk.
One remittance, examined
Not every claim is wrong. The ones worth reviewing do not announce themselves. This illustrative teardown shows how each line is classified.
| Deduction | Retailer’s reason | Amount | Verdict |
|---|---|---|---|
| Short-delivery claimINV-4471 | Quantity received under invoiced | −$3,120 | missing proof |
| Promo scan deductionPROMO-W32 | Scan claim past funding cap | −$8,640 | worth challenging |
| Shrinkage chargeDN-2210 | In-store loss charged back | −$1,450 | Code risk |
| DIFOT penaltyWK-32 | Delivery KPI penalty | −$2,200 | missing proof |
| Trading-terms rebateTT-Q2 | Agreed quarterly rebate | −$5,900 | supportable |
Illustrative figures only.
Who this is for
Claim types
Did fewer units arrive than you billed, and was the claim raised within the relevant delivery window?
Evidence: Signed POD, ASN, invoice, received quantity
Does the deduction match the agreed amount, cap, dates, and store scope?
Evidence: Signed promotion agreement, funding cap, scan report
Was an in-store loss charged back after the retailer took possession?
Evidence: Reason code, supply agreement, remittance line
Was delivery actually late or incomplete on the agreed measure, or is the scorecard wrong?
Evidence: ASN, booked window, dock timestamp, POD
Has the same claim already been deducted, set off, or credited?
Evidence: Prior remittance, credit note, claim ID
Does the retailer price match the accepted price list and effective date?
Evidence: PO, invoice, price list, effective date
Was there written consent, or does the supply agreement allow a reasonable set-off?
Evidence: Written consent, supply agreement, claim basis
Does the historic claim match the original agreement and transaction trail?
Evidence: Original PO, price list, promotion agreement
How it works
Pull claims from retailer portals, remittance advices, debit notes, and accounting short-pays.
Sort every claim by type and reason code.
Tie each claim to the PO, ASN, POD, invoice, promotion agreement, price list, credit note, and prior remittance.
Mark each line supportable, missing proof, worth challenging, or Code risk.
Rank by dollar value and days left in the dispute window.
Assemble the claim, required proof, proof found, gap, and suggested wording.
Support your challenge through the normal retailer process.
Track responses and surface recurring patterns worth fixing upstream.
Food and Grocery Code
Set-offs, shrinkage, wastage, shelf-space charges, damage claims, and payment timing can depend on the supply agreement and Code preconditions. We flag those facts for legal or commercial review; we do not make legal conclusions.
The retailer’s claim and reason
The agreement or rule it depends on
The supporting document trail
The missing evidence
Any Code point to review
Days left in the dispute window
Clear limits
We identify evidence gaps worth raising. The retailer decides whether to credit a claim.
Code points are review flags drawn from public guidance.
The first teardown uses one document you send us.
No percentage of recoveries or success fee.
You own the relationship and decide what to send.
Your remittance is used only to prepare your teardown. Ask and we delete it.
We send a private upload link shared with your email. Do not email the document as an attachment.
Hide bank details, account numbers, personal names, phone numbers, signatures, and unrelated customer details.
Keep the reason, claim ID, date, retailer, invoice number, amount, reference, and dispute deadline readable.
Read our privacy policy and terms.
Before you send anything
The claim types, evidence requirements, Code checks, and a worked teardown are published here. Use the free tools and send a remittance only if the method holds up.
A public triage checklist and the evidence each claim type needs.
Open resourceA worked teardown of DIFOT, promotion scan, and shrinkage lines.
Open resourceIdentify the evidence gap behind a single DIFOT deduction.
Open resourceDeduction families, evidence gaps, and Code risk before accepting a short-pay.
Open resourceRead a supermarket remittance and triage short-paid invoices.
Open resourceWhere Code facts can make a deduction worth reviewing.
Open resourceLeave your work email. We reply with a secure upload link. Every deduction line is marked supportable, missing proof, worth challenging, or Code risk, with urgent dispute windows flagged.
No recovery guarantee. Not legal advice. No system access for the first teardown.