Expired, near expiry, unreadable, or misread. Four different findings that arrive under one heading.
For cases we accept: the exact lot and its date code, the shelf-life rule that applies, the inventory and fulfilment history, and rotation records that show the control runs.
A real person reads your case and replies within about an hour.
ASA Compliance Group operates Amazon Sellers Appeal. On expiry files we reconcile the lot, the date code and the shelf-life rule, then evidence the rotation control in Seller Central.
Include the affected orders, photographs of the date marking on the unit and carton, and how stock is rotated. Four short steps. Or Shamosh reads every intake.
Or Shamosh · Founder and lead strategist
5,500+ enforcement cases since 2016. Every intake is personally assessed before acceptance.
Send what you have, including prior DIY or agency appeals. We say what is viable in writing before you commit.
Questionnaire
If the questionnaire does not load, open intake on the account page.
* Across ASA’s accepted and fully managed enforcement cases (all notice types we take on), not expiry matters alone. Details under Proof.
Several different findings arrive under this heading, and they need different answers. A unit genuinely past its date. Too little remaining shelf life at the point it shipped. A date that is missing, unreadable or inconsistently formatted. Incorrect expiry data in the catalog. Or a customer reading a production or best-by code as an expiry date.
The last of those is common and is not a dismissal of the customer. If a marking is ambiguous enough to be misread, that is a labelling finding in its own right, and it usually recurs until the marking or the explanation changes. Where the product also failed to perform, it may be a defect complaint as well.
Three markings that are routinely treated as one:
The date after which the product should not be used. Carries product, regulatory and marketplace meaning depending on category.
Commonly about quality rather than safety. Not automatically interchangeable with an expiry date, and not automatically distinct either.
Identifies when and where it was made. Often a Julian or batch format, and the one most often mistaken for a date.
Requirements differ by product, category and fulfilment programme, so there is no single shelf-life number that governs everything. Amazon publishes separate guidance for seller-fulfilled and fulfilment-centre inventory, and the applicable one has to be read for the actual product and channel.
Amazon's FBA baseline is a floor, not the whole rule. Inventory must arrive with enough remaining life for the product to be used or consumed in full, plus a further 90 days at fulfilment-centre check-in. Categories and individual products carry their own requirements on top of that, so read the baseline as the minimum the network enforces rather than as the standard your product is held to.
Only the first of these is what the notice appears to say. The other four are at least as common.
The straightforward version. A unit shipped after its expiry, usually because stock rotation did not catch it or the oldest stock was not picked first.
Trace the lot, the order, the storage and the picking decision. The finding here is rarely the unit itself: it is the rule that should have stopped it and either did not exist or did not run.
The unit was in date and did not have enough of it remaining for the channel or category. This is a different finding from expiry and it is judged at a different moment, usually receipt or dispatch rather than delivery.
Read the applicable requirement for that product and channel rather than applying a familiar number. A single remaining-days rule quoted across every date-sensitive category is one of the more reliable ways to lose this argument. Where consuming an out-of-date unit could cause harm, the case also touches product safety compliance.
The date is absent from the unit, rubbed off, printed only on the outer carton, or in a format the customer cannot parse. From the buyer's side an unreadable date and an expired product look identical.
A production or lot code interpreted as an expiry. This is disputable, and only with the manufacturer's own decoding tied to the exact lot and a clear photograph of the actual marking.
Altering a date marking after production to improve the record is not a correction. It is a different and much worse finding. Correcting expiry data held in the catalog is a separate exercise, covered by incorrect detail page.
Stock is picked by convenience or location rather than by date. First in first out and first expired first out are different rules, and for date-sensitive goods only the second reliably protects the customer, because receiving order and expiry order are not the same.
This branch is where most repeat complaints come from, and it is the one with the most convincing fix available, because rotation produces records by its nature.
Reviewers are reconciling a specific unit against a specific rule. Most rejected responses answer in general terms.
The claim made without the exact unit, lot, date format, order timing and remaining shelf life that would establish it.
A manufacturer shelf-life letter that does not connect to the lot the customer received or to the stock actually held.
Expiry data corrected in the catalog while older units remain in fulfilment centres or in the warehouse.
A familiar remaining-days figure applied across products and channels that do not share it.
Controls described with no receiving dates, no date capture, no stop threshold and no retained records.
A date marking changed after production and presented as a correction, which is a more serious finding than the original one.
Establish what the marking meant, then whether the rule was met, then whether the control runs. In that order.
Record the complaint and order dates, the affected product and code, the lot or batch, the expiry or best-by date, the fulfilment channel, and any return photographs. Then photograph the marking itself, clearly, on both the unit and the carton, because the difference between those two is sometimes the entire case.
Obtain the manufacturer's own interpretation of the date format, tied to that lot. A general explanation of the company's coding is a start; what settles a dispute is a decoding that names the lot in question.
An illustrative example, and only illustrative: requirements differ by product, category and channel, so the numbers below are the shape of the calculation rather than a rule.
The stage matters as much as the answer. A unit compliant at receipt and short at dispatch is a rotation finding; short at receipt is a purchasing and inbound one.
Use lot, shipment, inventory age and date data to define what else could share the problem. Expiry cases scope unusually well, because date-marked goods carry their own population boundary and inventory age reports make it visible.
Then decide containment against that boundary: removal, disposal, or continued sale with a documented stop threshold. Blanket removal without a scope decision proves nothing about which orders were affected or why the control failed.
A rotation control is receiving records that capture lot and date, pick logs that show oldest or soonest-expiring stock going first, a minimum remaining-life threshold that stops a unit shipping, exception reports, removal records, a named owner, and periodic audits.
A written procedure supports the explanation and completed transaction records are what show the control operates on current stock. Fulfilment-centre and self-fulfilled inventory produce different movement records, and both need lot and date traceability where the goods are date-marked.
If the marking on the customer's unit cannot be identified, say so. An honest gap is workable; a confident decoding of a marking nobody photographed is not.
Scoped historical outcomes on cases we accepted and fully managed. One seller voice below; deeper galleries live on account reinstatement.
Population: historical cases ASA accepted and fully managed (we prepared the compliance response and ran follow-ups in Seller Central). The figure combines reinstatement and restoration work across notice types in that managed population, not expiry matters alone. Declined intakes and self-serve template buyers are not in the rate.
Success: reinstatement or restoration of the privileges Amazon had restricted for that file (account, listing, verification, funds, or related, depending on the case). Amazon decides every outcome; the rate is not a guarantee for future cases.
Review: the underlying records were independently reviewed. Verified as of .
More methodology context and galleries: account reinstatement proof.
“In less than 24 hours after the appeal, my account was reactivated with all products available for sale.”
More outcomes and video proof: account reinstatement proof.
For sellers who already have the Performance Notification. Broader questions: full FAQ library.
If Amazon flagged an expired or near-expiry product, start with the questionnaire.
Listing removed rather than mis-described: listing reinstatement. Other notice names: all suspension types.
