Amazon SAFE-T Claim: The Four and Thirty Day Windows

The return scan posts at 4:12 p.m. on a Tuesday. Two clocks start at that instant, and neither is displayed anywhere as a countdown.

The first runs four calendar days. It expires Saturday afternoon, weekend included. If you have not inspected the item and made a refund decision by then, Amazon can issue the refund for you, and in most situations that automated refund takes your reimbursement rights with it.

The second runs thirty days from that same scan, or from the refund date if the refund lands later. That one is the window for the SAFE-T claim itself. Until 16 February 2026 it was sixty.

Both numbers moved in the first eight weeks of this year, in opposite directions, and a large share of the SAFE-T guidance sitting in search results still runs on the old ones. If you are still working out which of the four money-back tracks you are even on, start with the sender of the notice and come back once you know it is a return that got refunded.

Policy as of 2026-08-21. The underlying help pages sit behind a Seller Central login — the SAFE-T reference page at sellercentral.amazon.com/help/hub/reference/G201818410 redirected to a sign-in screen when tested on that date — so everything below is cited to Amazon-staff posts on the public Seller Forums, with the age of each post stated. Re-check both figures every 90 days.

The two 2026 changes, side by side

The source for both is a Seller Forums post, "Two Major Changes to Seller-Fulfilled Returns & SAFE-T Claims", from the Amazon community manager account Joey_Amazon. The forum shows relative dates only; on 2026-08-21 it displayed as seven months old, which puts it around the January change. A follow-up from the same account, "SAFE-T Claims in 2026: New Rules + How to Get Reimbursed", displayed as four months old and repeats both figures with the filing steps attached.

Read together, they describe a trade: two extra days of inspection time, thirty fewer days of filing time. For a one-person operation the second half is the expensive half, because the sixty-day window used to quietly absorb the week you spent doing something else.

What the four days buy, and what they cost if you spend them wrong

The four calendar days run from the return delivery scan at your address, not from the day you got round to opening the box. The four-month-old post is direct about what belongs inside them: inspect, photograph, then make the decision through the Guided Refund Workflow under Orders in Seller Central. Full refund, partial refund with a restocking fee where the item came back in a different condition, or dispute.

The catch is stated in both posts. If Amazon issues an automatic refund after that window closes, SAFE-T eligibility for the order is gone. Two carve-outs survive: items lost in return transit, and cases where delivery confirmation was incorrect through no fault of your own. Returns refunded through Refund at First Scan are described as remaining eligible regardless of the four-day rule, because on those the refund fires at the carrier's first scan by design rather than by your inaction.

So the decision that keeps the claim alive is not the claim. It is the refund decision you make yourself, on time, before the timer makes it for you. That takes some getting used to, because the instinct with a return you intend to dispute is to sit on it and think.

One more line from that same post deserves to live next to the scale: do not issue the refund before you have finished assessing the item, and photograph the return before it goes back into inventory, because once it is restocked the visual evidence is gone. If you already run the ten-minute outbound record on everything you ship, the inbound half is that same habit pointed the other way. It is also the half a SAFE-T investigator actually reads.

Where day one of the thirty falls

Three different start dates, depending on what happened:

• The return arrived. The clock starts at the return delivery scan at your address, or at the refund date, whichever is later.
• The refund came after the item. Then the refund date is the later of the two, and it is the one that counts.
• The return never arrived. The clock starts at the last tracking scan event on the return leg.

Whichever applies, the practical move is identical and takes ten seconds. When the scan posts, write the calendar date plus thirty next to the order ID. Not "end of the month". The date.

What the eligibility checker will and will not let through

Filing starts at a gate. From the Orders tab, Manage SAFE-T Claims, File a new SAFE-T claim, enter the order ID, Check eligibility. Amazon's older walkthrough, "How to file a SAFE-T claim: steps and best practices" from the staff account KJ_Amazon (three years old as displayed on 2026-08-21), is blunt about that gate: if the order comes back ineligible, there is no appeal of the ineligibility itself.

That post lists the qualifying situations as Amazon determining the customer abused the return or refund policy; an item returned in unsellable condition where Amazon finds you not at fault; a materially different item returned where Amazon finds you not at fault; no return at all, evidenced by the absence of a return merchandise authorisation or a carrier first scan; Amazon refunding the customer for a return label the customer was responsible for paying; a non-receipt claim you can rebut with Buy Shipping or delivery signature confirmation; and a return Amazon initiated on the buyer's behalf for an item that was already outside the return window when the buyer asked.

The 2026 post frames the same territory more loosely: a damaged item back in a return, the wrong item entirely, a return missing parts or accessories, or an RFS refund. It also states that SAFE-T is for US sellers on the Merchant Fulfilled Network, Seller Fulfilled Prime included.

Now the discrepancy nobody flags, and it sits on Amazon's own forums. The three-year-old list puts "the item was lost or damaged during the return shipment" in the not eligible column, and also excludes any order you refunded yourself, fully or partially. The 2026 posts say lost in return transit is precisely the exception that survives an automatic refund, and that refunding it yourself inside four days is what preserves eligibility. Both cannot be current. The 2026 posts are newer and describe the rules the two changes created, so that is the version to work from — but the older page is still up, and it is the one several third-party guides are still copying. When the two disagree about your specific order, the only answer that binds is what the eligibility checker returns for that order ID.

What SAFE-T does not reach at all

Four categories where the claim is the wrong instrument, plus one where it is simply too late:

• FBA orders. This is the one exclusion both lists agree on, from opposite directions: the older post rules out orders fulfilled by Amazon, and the 2026 post says SAFE-T is for the Merchant Fulfilled Network. Fulfilment errors and inventory lost or damaged inside Amazon's network run through the FBA reimbursement process instead.
• A granted A-to-z claim. Once Amazon has decided that claim against you, the money moved under a different policy and SAFE-T does not reopen it. The appeal on the claim itself is the only route, and a pending appeal still counts as a defect while it sits.
• Card chargebacks. Neither Amazon post mentions these, and that is the point — a chargeback was never Amazon's proceeding. The issuing bank decides it, on the bank's calendar, through representment on the payments side.
• A return you refused. The older Amazon walkthrough lists refusing a return shipment, for any reason, as an exclusion. Nothing in the 2026 posts softens it, but nothing restates it either, so this one rests on a three-year-old page.
• Anything filed on day 31. Here the 2026 post is unambiguous, and it is the current one: miss the window and the claim is denied, no exceptions.

The clock nobody counts, and the metric it costs you

There is a third deadline in the return flow, older than either 2026 change, and it runs before both of them: your response to the return request itself.

An Amazon News announcement, Seller's response to return requests required within 48 hours (posted by the News_Amazon account, seven years old as displayed), says two things. A buyer must file a return request and wait 48 hours for your response before they are even allowed to open an A-to-z claim. And if they do open one and you never answered the return request inside those 48 hours, Amazon grants the claim and debits your account for the amount.

Seven years is a long time to lean on one announcement, so be clear about what that citation is worth. It is the plainest public statement of the rule that exists, but Amazon's current buyer-facing A-to-z pages did not open on 2026-08-21 — two attempts that day returned an error page rather than the policy text — so nobody outside Seller Central can confirm the 48 hours is still the live number. Treat it as the last figure Amazon stated publicly, not as one re-confirmed in 2026. Your own Manage Returns queue is the authority that matters: it shows the outstanding request and the time left on it.

That is the expensive path, and not because of the debit. A granted A-to-z claim is one of the three inputs to order defect rate, measured over a rolling 60 days against a 1% ceiling. At low volume a single claim can hold you over the line for two months, and refunding afterwards does not remove it. A SAFE-T claim is not an ODR input at all. Filing one costs you nothing on the metrics.

Which settles the tempting move fairly cleanly. Sitting on a return request, or rejecting it to keep the money in your account a while longer, converts a dispute that would have cost nothing in account health into one that costs a defect for sixty days. Authorise the return, take the item back, decide inside the four days, and argue about the money afterwards through the channel that does not touch your numbers.

The packet: what goes in before you press submit

Assemble this before you open the form. The description field and the attachments are read together, and a thin claim invites a request for more information, which arrives with its own three-business-day reply deadline attached.

• Photos of the returned item. Several angles, damage or discrepancy in frame and in focus.
• A comparison shot where you can produce one: the returned unit beside an undamaged unit of the same product.
• The return package itself, photographed with the mailing label and tracking ID readable.
• The packing slip that came back in the box, if there was one.
• Your outbound record for that order: the label, the weight you wrote down, the photo taken the day it shipped, the serial number if the item carries one.
• The invoice or purchase documentation showing the item and what it cost you.
• Screenshots of the original order and the return request, plus any buyer messages about the return.
• A description that names the amount you want back, split into parts: product cost, return shipping, outbound shipping. Amazon's own guidance says to be explicit about what you are requesting rather than leaving the investigator to work it out.
• Highlighting. The older walkthrough specifically recommends red boxes or highlights on supporting documents so the investigator finds the relevant part faster.

After submission, keep the conversation on the Manage SAFE-T Claims page. Seller Support does not decide these, and routing it there burns days you no longer have. Watch the status field for Awaiting Seller Response, which is the one with a fuse on it, and note the Reply by and Appeal by timestamps the moment they appear. Seven days for the appeal, once only, per Amazon's older post. The timestamp printed on your own claim is what you actually work to.