Return Not Received vs Refund Dispute: Who Holds Liability?

Return Not Received is a merchant claim that a customer return was not received despite a refund request or return shipment. Determining liability in such cases depends on the return method, who paid for return shipping, and the evidence each party can present.

Liability can fall on the customer, the merchant, or the carrier. The simplest dividing line is who controls the shipment and who bears the shipping risk: if the merchant provided and paid for a return label, the carrier and merchant typically bear the risk until delivery; if the customer arranged and paid for return shipping, risk often remains with the customer until the merchant confirms receipt.

Key Differences Between A Return Claim And A Refund Dispute

A "Return Not Received" claim is operational: the merchant asserts an expected inbound item did not arrive. A refund dispute (or chargeback) is a financial claim with the card issuer: the cardholder asserts the charge should be reversed for reasons such as non-delivery or fraud.

• Operational Issue: Document-oriented and resolved by proving the item was received and processed.
• Financial Dispute: Handled through payment networks; requires different evidence to defend (POD, refund records, communications).

Who Is Responsible?

Responsibility depends on contractual terms and the return flow. Typical scenarios:

• Merchant-Provided Prepaid Label: Merchant usually controls the label and can open claims with the carrier. If the carrier confirms loss, the carrier or merchant often assumes liability; the merchant should refund or replace promptly.
• Customer-Shipped Return (Customer Pays): Risk typically stays with the customer until the merchant receives the item. The customer should use tracked shipping; otherwise, the customer bears the risk.
• Third-Party Returns (3PL/Marketplace): Liability follows contract terms between merchant, 3PL, and marketplace. The 3PL’s receiving records and the marketplace’s return policy determine outcomes.

How Evidence Shifts Liability

Evidence changes who looks responsible in the eyes of payment processors and courts.

• Tracking And POD: A delivered scan or signature transfers liability away from the merchant. No scans often shift the obligation back to the customer unless the merchant issued and tracked the return label.
• RMA And Process Compliance: If your return policy requires an RMA and the customer did not comply, you may lawfully deny a refund — document the policy, that it was shared, and that the customer failed to follow it.
• Inspection Records: Receiving timestamps, quarantine notes, and photos showing return condition prove that the merchant received and inspected an item and issued or denied a refund accordingly.

Resolving Liability Disputes

Resolve these disputes efficiently to limit chargebacks, preserve customer relationships, and avoid unnecessary refunds.

• If Carrier At Fault: Open a carrier claim and either refund the customer immediately (with the intention to recover from the carrier) or issue a replacement while the claim matures.
• If Customer At Fault: Provide evidence to the card issuer showing no receipt and note that the customer arranged shipping; deny refund requests when your policy supports that position.
• When Ambiguous: Offer a partial refund, store credit, or replacement when liability is unclear and the dollar amount is small relative to customer lifetime value.

Practical Workflow For Liability Assessment

Create a fast, repeatable workflow so support, operations, and payments teams follow the same path:

• Step 1: Collect the tracking number and customer evidence; attempt to validate carrier scans.
• Step 2: Query WMS and receiving teams for inbound records and CCTV evidence.
• Step 3: If merchant-labeled, open carrier trace/claim; if customer-labeled, require customer to open a carrier claim and provide results.
• Step 4: If the customer has filed a chargeback, prepare documentation for the acquirer: shipping labels, returned-item photos, inspection notes, and policy copies.

Tips To Reduce Liability Exposure

• Require Tracked Returns: Insist on a tracked return method for higher-value items; merchant-paid returns should use a prepaid, trackable label.
• Define Policy Clearly: Publish return windows, RMA requirements, and who is liable for lost return shipments in your terms.
• Keep Records: Retain all communications, tracking, and WMS logs for the period required by payment networks and local regulations.

In short, the Return Not Received situation becomes a question of evidence and contract: who arranged and paid for shipping, what scans or POD exist, and whether warehouse records show receipt. Clear returns policies and tracked return processes shift liability toward predictable, manageable outcomes.