What is wholesale proof of delivery?
Wholesale proof of delivery is documented evidence that a B2B shipment reached the agreed delivery point, on the agreed basis, with a clear record of who received it and in what condition. In proof of delivery B2B practice, POD is not a courtesy scan—it is the bridge between dispatch, retailer acceptance, claims, and invoice settlement.
For brands and distributors, weak POD shows up as endless email trails, unpaid short shipments, and chargebacks that are hard to refute. Strong POD is a shared standard across warehouse, carrier or 3PL, finance, and the retailer. Delivery confirmation wholesale only holds when the same shipment identity runs from pick list through carrier event to invoice line.
sealed carton beside a clipboard and delivery stamp
What should a wholesale POD capture from carriers and 3PLs?
A usable wholesale proof of delivery record answers four questions: what was shipped, where it arrived, when it arrived, and who accepted it. Carrier POD requirements should be explicit enough that ops can match the file to an order without detective work.
At minimum, ask carriers and 3PLs to return:
- Shipment and order references that match your packing slip and ASN
- Delivery timestamp and delivery location (address and, where available, geo-stamp)
- Recipient name or role, plus signature and/or photo POD
- Exception codes for failed delivery, refusal, damage, or short shipment
- Links or file IDs for images, signed notes, and any CMR or pallet label scan
Signature / photo POD is common on parcel and many pallet networks. For international road freight, the CMR consignment note remains the core paper or electronic trail of handover between sender, carrier, and consignee.[1] Photo evidence helps on condition disputes; a signature alone rarely proves carton count or damage state.
Align packing-slip content with what the driver or depot will scan. If the slip, label, and portal order number diverge, POD arrives orphaned and finance cannot close the loop. For EU packing detail that supports clean handover, see wholesale packing slip requirements for EU.
How do you set POD standards in carrier and 3PL contracts?
How do you set POD standards in carrier and 3PL contracts? You write the evidence format, timing, and exception codes into the service schedule so POD is a deliverable, not a favour.
Contract clauses that usually matter:
- Evidence type by service — signature, photo, geo-stamp, depot scan, or CMR, by product (parcel, pallet, groupage).
- Return timing — when electronic POD and images must appear in the portal or EDI feed after delivery or failed attempt.
- Reference integrity — mandatory capture of your order and SSCC or label IDs.
- Exception taxonomy — shared codes for short shipment, damage, refusal, access issues, and redelivery.
- Retention — how long the carrier keeps images and signed notes for claim defence.
- Liability interface — how POD feeds notice periods for loss, damage, and delay under the carriage contract.
Audit a sample of deliveries each month. If POD routinely lacks recipient identity or arrives days late, the standard exists only on paper. Tie performance reviews to complete POD rate and exception quality, not only on-time percentage.
Dispatch cut-off and carrier book-in rules belong in the same operating agreement. Late handovers create “delivered late” disputes that POD alone cannot fix. Pair POD rules with clear wholesale order status tracking so retailers see the same milestones your 3PL reports.
driver handing a pallet to a retailer at a loading bay
How does proof of delivery link to wholesale claims and chargebacks?
How does proof of delivery link to wholesale claims and chargebacks? POD is the primary evidence file when a retailer claims non-delivery, short shipment, damage, or refuses a deduction you believe is wrong.
Delivery claims typically turn on three mismatches: quantity on the packing slip versus quantity accepted, condition at handover versus condition reported later, and delivery place or party versus the booked address. Without POD tied to the order, the brand argues from memory and the retailer argues from store process—and chargebacks stick by default.
Practical linkage:
- Store POD against the sales order and shipment ID before the invoice is considered settled
- Require claim notices inside a fixed window from delivery timestamp, not from invoice date alone
- Treat “no POD on file” as an internal failure first; chase the carrier before conceding the claim
- Separate genuine short shipments from admin deductions dressed up as delivery issues
A disciplined wholesale claims process after delivery uses POD as the gate: open the claim only when the retailer supplies order lines, photos if relevant, and the delivery reference you already hold. For margin leakage dressed as deductions, align the same evidence trail with your approach to wholesale chargebacks and deductions.
What POD rules belong in retailer terms and conditions?
What POD rules belong in retailer terms and conditions? Spell out what counts as delivery, how long the retailer has to report shortages or damage, and which documents govern the dispute.
Useful T&C elements:
- Definition of delivery — arrival at the named place under the chosen Incoterms, not “when the store finishes put-away”
- Acceptance window — a short, fixed period to report short shipment, visible damage, or wrong goods
- Evidence the retailer must supply — order number, line quantities, photos, and booking reference
- Failed delivery — who pays storage, redelivery, and re-label costs when access, hours, or refusal block handover
- Authority to sign — that a signature or site scan by site staff binds the buyer for quantity at handover
- Risk and title — cross-reference Incoterms so risk transfer is not reinvented in claim emails
Keep retailer wording consistent with carrier contracts. If your T&Cs promise photo POD on every lane but the 3PL only offers depot scans on groupage, you have written a dispute into every pallet. Use a wholesale terms and conditions checklist when you refresh the pack, and align delivery language with Incoterms for wholesale EU delivery.
two contract folders connected by a single continuous path to a delivery dock
Which POD formats work across EU cross-border wholesale shipments?
Which POD formats work across EU cross-border wholesale shipments? The workable set mixes mode-specific legal documents with electronic carrier events, not a single universal file type.
Road groupage and full loads often rely on the CMR consignment note plus receiver remarks for damage or shortage.[1] Parcel and many pallet networks rely on electronic delivery events with signature, photo, or safe-place rules defined by the product. Cross-border lanes may also need customs or booking references that must stay joined to the commercial invoice and packing list.
Incoterms set where delivery and risk transfer occur; they do not replace POD.[2] A DAP or DDP sale still needs proof that the goods reached the named place. EXW or FCA shifts earlier risk to the buyer, but brands still collect carrier POD when they arrange main carriage as agent—or they lose visibility when claims arise.
Choose formats retailers and carriers already support. Forcing a bespoke PDF on every EU lane creates gaps; requiring structured events plus CMR or signed delivery note where the mode expects them keeps B2B shipment documentation portable across borders.
How should brands handle missing, late, or disputed POD?
How should brands handle missing, late, or disputed POD? Run a fixed exception path: detect, chase, escalate, then decide the commercial outcome.
A simple internal path:
- Flag shipments with no POD after the carrier’s agreed return window
- Auto-chase the carrier or 3PL with shipment ID and delivery slot
- If POD arrives incomplete, request image or signed note before the retailer’s claim window closes
- If the retailer disputes condition or quantity, compare POD, packing slip, and any booking photos side by side
- Record the outcome on the order so invoice credit or chargeback defence is traceable
Do not let sales “promise a credit” while ops is still waiting on the depot. Disputed POD is a three-party problem—brand, carrier, retailer—and only one owner should drive the timeline. Failed delivery needs its own branch: rebook, return to stock, or hold with cost allocation spelled out in the T&Cs.
How do you operationalise POD from dispatch to invoice?
How do you operationalise POD from dispatch to invoice? You keep order, shipment, and invoice identifiers linked so POD is a status on the same record finance uses to release or hold settlement.
Operational checklist:
- Freeze ship-from, cut-off, and label data at dispatch so the carrier event can match your order
- Push shipment IDs into tracking the retailer already uses
- Land POD files and exception codes on the order before dunning or chargeback response
- Only fully close order-to-invoice when delivery evidence and invoice lines reconcile—or when a coded exception explains the gap
- Review repeat short-shipment and failed-delivery patterns by lane and customer, not only case by case
Clean POD fails when evidence lives in a carrier portal, claims live in inboxes, and invoices live in the ledger with no shared key. A branded B2B storefront and order-to-invoice layer such as Brandgate gives ops one place to match retailer orders, dispatch status, and claim evidence without re-keying across tools.
When order, packing slip, carrier POD, and invoice share the same backbone, wholesale proof of delivery stops being a filing chore and becomes the control that keeps delivery claims and proof of delivery chargebacks from eroding margin.
Next step: Book a demo to see how Brandgate keeps orders, dispatch, and invoices aligned—or see pricing.
