A wholesale claims process is the structured way a brand or distributor handles post-delivery damage and shortage claims from retailers—intake on the order, evidence review, decision, credit note or invoice adjustment, and accounting handoff. It sits inside order-to-invoice operations, not in ad-hoc email threads.
Without a defined path, damage photos sit in inboxes, shortage disputes drag past invoice due dates, and finance re-keys adjustments by hand. This guide walks through a practical B2B claims workflow you can run consistently across Nordic and EU wholesale accounts.
What is a wholesale claims process?
A wholesale claims process is a defined workflow for receiving, validating, deciding, and settling retailer notices of post-delivery damage or a shortage claim on goods already shipped against a wholesale order. It covers first notice, evidence standards, liability checks, commercial decision, and the financial document that closes the loop.
It is not a full reverse-logistics programme. Most approved claims end in a credit note or invoice adjustment, not a physical return of every unit—especially when goods are unsellable, perishable, or not worth shipping back.
Clipboard checklist linked to a sealed wholesale carton
How does a wholesale claim differ from a return or a chargeback?
A wholesale claim differs from a return or a chargeback because it disputes condition or quantity on a delivered order and seeks a commercial adjustment, whereas a return sends goods back under a returns policy and a chargeback or deduction is a unilateral payment shortfall.
| Path | Trigger | Typical outcome |
|---|---|---|
| Claim (damage/shortage) | Wrong qty, damaged units, wrong lot after delivery | Credit note or partial invoice adjustment |
| Return | Agreed reverse shipment under policy | RMA, restock or scrap, credit after receipt |
| Chargeback / deduction | Buyer short-pays invoice | Dispute, recovery, or write-off risk |
Keep your wholesale returns policy for goods that should come back. Treat wholesale chargebacks and deductions as a separate leakage problem—ideally prevented by settling valid claims before payment is due.
What should retailers submit when filing a post-delivery claim?
Retailers should submit order identity, claim type, quantities, and evidence that ties the issue to the delivery—ideally within your published claim window.
Minimum intake fields
- Wholesale order number and invoice number (if already issued)
- Delivery date and ship-to location
- Claim type: damage, shortage, wrong item, or quality/lot issue
- SKU or line, ordered qty, received qty, claimed qty
- Proof of delivery (POD) reference and any delivery exception noted on arrival
- Photos and lot/batch evidence (outer pack, label, damage close-up, batch/lot codes where relevant)
- Contact person and preferred remedy (credit, replace, partial re-ship)
Evidence checklist that speeds decisions
- Wide shot of pallet or carton as received
- Close-ups of damage or seal integrity
- Readable product and lot labels
- Count variance vs packing list for shortages
- Carrier delivery note with damage or short notation when the driver was still present
Incomplete files create back-and-forth. Publish the checklist in onboarding and on the order confirmation path so retailers know the standard before they open the box.
How do you run claims intake from first notice to decision?
You run claims intake by logging first notice against the order, validating window and evidence, checking liability and stock reality, then recording approve, partial approve, or deny with a clear reason.
1. First notice and claim window
Define a claim window / SLA—for example, visible damage noted at delivery where possible, and hidden damage or shortages reported within a fixed number of business days after POD. State the clock start (delivery date vs invoice date) in your terms so both sides measure the same way.
Late notices can still be reviewed commercially, but the bar for approval should be explicit so operations is not inventing rules per account.
2. Structured intake on the order
Capture the claim on the same order record used for fulfilment and invoicing. That keeps line quantities, ship dates, and prior credits visible. Email-only intake loses context when sales, warehouse, and finance each hold a different thread.
3. Validation
Operations checks:
- Is the claim inside the window?
- Do photos and counts match the shipped lines?
- Does warehouse shipping evidence (pick confirmation, packing list, weight/photo if you use them) contradict or support the claim?
- Is this a pattern account or a one-off?
4. Decision and remedy
Decide approve in full, partial approve, deny, or request more evidence. Remedies are usually credit, replacement ship, or a mix. Record who decided and why—future audits and retailer conversations depend on it.
Branching path from delivery notice to decision stamp
Who is liable under common Incoterms for damage in transit?
Under common Incoterms, liability for damage in transit follows the agreed risk-transfer point in the contract—not whoever booked the courier—so you must map each claim to the term on the order.[1]
Incoterms for wholesale EU delivery set when risk passes from seller to buyer. In broad terms used in B2B practice:
- Terms where the seller carries risk further along the journey place more transit damage exposure on the seller until the named place or destination rules are met.
- Terms where risk passes earlier (for example when goods are handed to the first carrier) place more exposure on the buyer, subject to your commercial policy and any carrier claim you help pursue.
Carrier liability is a parallel track. Even when commercial credit is issued to keep the retailer whole, your team may still file against the carrier using POD, consignment notes, and damage notation rules that apply to the mode (parcel, pallet, or international road consignment practice). Train receiving teams at retailer sites to note visible damage before signing where the delivery document allows exceptions.
Never assume “we always credit transit damage” without tying the decision to the Incoterm on that order—margin leakage hides in blanket habits.
What SLAs and evidence rules keep wholesale claims fair?
SLAs and evidence rules keep wholesale claims fair when they are published, applied evenly, and allow documented exceptions for hidden defects.
Practical policy elements
- Claim windows by type (visible damage, shortage, hidden/quality)
- Required evidence list (POD, photos, lot/batch, counts)
- Response SLA for acknowledgement and for decision
- Partial-approve rules when only some lines are proven
- Fraud and abuse signals (repeated undocumented shortages, altered packaging photos)
- Escalation path for high-value claims
Fairness is consistency: the same incomplete file should get the same “needs evidence” reply whether the account is large or small. Goodwill credits can still exist—but label them as goodwill so finance and sales do not treat them as precedent for every future dispute.
How should credit notes and accounting handle approved claims?
Approved claims should be settled with a credit note or controlled invoice adjustment linked to the original order and invoice, then posted cleanly in accounting so VAT, receivables, and revenue stay aligned.[2][3]
Wholesale credit note process essentials
- Reference original invoice and order lines[2]
- Credit only approved quantities and values
- Apply correct VAT treatment for B2B credit notes under the rules that apply in your jurisdiction[2][3]
- Block double remedies (credit plus free replacement for the same units without intent)
- Notify the retailer with a document they can match in wholesale invoice reconciliation
For Nordic brands on Fortnox, the handoff matters: once the commercial decision is final, the credit should flow through the same Fortnox wholesale accounting sync path you use for invoices, not as a disconnected manual journal that drifts from the order history.
Invoice and credit note connected by one continuous loop
How do you prevent repeat claims without blocking good customers?
You prevent repeat claims by fixing root causes in pick, pack, and carrier performance while keeping a fast lane for complete, timely claims from reliable accounts.
Operational levers
- Shortage patterns by SKU or pick face → warehouse process checks
- Damage patterns by lane or packaging type → pack spec and carrier review
- Wrong-item claims → label and scan controls at pack
- Account-level patterns → coaching on receiving process, not automatic denial
Commercial levers
- Publish the claims process in retailer onboarding
- Show order and shipment context in the portal so claims cite real lines
- Separate goodwill from validated liability
- Review chronic claimants with facts, not anecdotes
A branded B2B portal helps here when orders, claims context, and invoice outcomes live in one place. Brandgate is built as a distributor portal for wholesale brands—so intake and credit outcomes do not depend on hunting email threads—then finance stays aligned through order-to-invoice automation and accounting sync where you use Fortnox.
Putting the wholesale claims process into order-to-invoice
Fold claims into the same operating rhythm as fulfilment and invoicing:
- Terms state windows, evidence, and Incoterms risk points
- Delivery and POD are visible on the order
- Claim intake is structured and time-stamped
- Decision is recorded with remedy
- Credit note or adjustment posts to accounting
- Patterns feed warehouse and carrier improvement
That is post-delivery claims B2B done as operations, not as firefighting.
If you want orders, claims context, and invoice outcomes in one wholesale workspace—with a path into Fortnox—book a demo or see pricing.
Simplified Europe map with careful parcel handoff