Amazon return policy 2026: refunds, claims and seller deadlines

The customer has been refunded, the warehouse has not finished inspection, and the team is searching for a single Amazon return deadline. No single clock covers all three situations.

Sellers and support teams should first separate the customer’s refund from any seller reimbursement claim, then check whether the order was seller-fulfilled or fulfilled by Amazon. That keeps a valid rule from being applied to the wrong workflow.

Reviewed October 23, 2026 for Amazon US only. Other Amazon stores have their own rules. Check the current notice and eligibility requirements for the individual case before acting.

Do FBM sellers have four days before every refund?

No. Amazon’s refund-processing announcement extended the window from two business days to four calendar days, effective January 26, 2026. The help page on issuing refunds for seller-fulfilled orders now states the same rule: refund within four calendar days after you receive a return, or Amazon may refund the customer on your behalf and charge your account.

Neither the announcement nor the help pages define which returns are covered. In the same Seller Forums thread, an Amazon moderator clarified that the four days apply only to returns where Amazon has not already refunded the buyer through Refund at First Scan on a prepaid return label. Refund at First Scan remains in place, so eligible cases can be refunded before the parcel reaches you, let alone before inspection. The older Manage seller-fulfilled returns page still says two business days; the refund and SAFE-T pages carry the newer rule.

Missing the four days has a cost. Under the SAFE-T policy, an automatic refund issued because you did not act in time is not eligible for a SAFE-T claim, except when the return delivery was never confirmed, or when you believe the buyer used an inaccurate return reason code (then only return shipping costs can be claimed). Amazon points sellers to its Guided Refund Workflow within the four days to grade the item, apply any restocking fee and upload evidence.

Treat the receipt event and refund status as separate records. Before issuing money manually, check whether Amazon has already refunded the buyer. A parcel arriving at the warehouse does not mean the refund is still awaiting your decision.

Where the applicable period counts calendar days, plan for weekend coverage. Set an internal reminder earlier than the platform deadline and label it as your operational target, not an Amazon rule.

Which claim process applies after a refund?

FBM SAFE-T and FBA inventory reimbursement are different processes. Do not route them into a generic “claim within 60 days” queue.

Amazon’s US SAFE-T announcement cut the filing period for US seller-fulfilled orders from 60 days to 30, effective February 16, 2026. The announcement counts from the return delivery scan or the refund date, whichever is later, and from the last scan event for lost shipments. The SAFE-T help page words it as 30 calendar days from the refund being charged to your account, or from receipt of the returned item for a free replacement. Where the two readings give different dates, work to the earlier one.

Eligibility still matters. The help page lists ineligible cases, including refunds you issued yourself, orders with an A-to-z Guarantee claim, chargebacks, items damaged or lost in return transit (a carrier claim instead) and FBA orders. Review the policy and the case record rather than assuming every refunded order qualifies.

Record the refund date, carrier events, warehouse receipt and evidence of any discrepancy. If the item returned differs from what was shipped, the person preparing a claim needs the relevant records, not a general note saying “customer abuse.”

Why can an FBA reimbursement be below the sale price?

For inventory lost or damaged before a customer order, Amazon moved to a manufacturing-cost basis. The official timing update, a Seller Forums announcement, moved the effective date from March 10 to March 31, 2025. Amazon’s policy explanation distinguishes manufacturing cost from selling price and other expenses.

The current FBA inventory reimbursement policy calls the same figure “sourcing cost”: what you paid a manufacturer, wholesaler or reseller, or your production cost, excluding shipping, handling and customs duties. It applies to shipment-to-Amazon, removal and fulfillment-center claims. Customer return claims are still valued at the refund or replacement on the original order minus applicable fees. If you do not enter a sourcing cost on the Manage Your Sourcing Cost page, Amazon uses its own estimate.

A lower reimbursement therefore does not by itself prove a processing mistake. Check the event type and cost basis before challenging the amount. The inventory or finance owner should hold the relevant cost evidence; frontline support should not have to reconstruct it.

In a Seller Forums announcement, Amazon also set different FBA claim windows by event type, effective October 15, 2025. Confirm the specific route for warehouse loss, customer returns or removals rather than applying one window to all of them.

What should your return tracker contain?

Use a record that supports the next decision:

Field	Why it matters
Order and fulfillment type	Distinguishes FBM from FBA work
Case or claim type	Identifies the applicable process
Trigger event and timestamp	Determines which clock has started
Refund status	Prevents duplicate action
Deadline and official rule	Keeps the instruction auditable
Evidence and owner	Makes the next action possible

This is a suggested operations checklist, not a replacement for Seller Central. Check discrepancies against the platform record and preserve the relevant notification.

How can support and the warehouse avoid working at cross-purposes?

Agree on how receipt and condition findings reach the case owner. Where appropriate, keep packaging and condition evidence before anything is disposed of. If a parcel cannot be matched to an order, flag it as an exception.

Use responsive support handoffs for customer updates and return-cause analysis for recurring operational problems. Start by reviewing one recent refund and tracing which events happened before the team noticed them. Fix that visibility gap before adding more reminders to the wrong deadline.