Shelfdoc
Operator checklist

Amazon FBA Expiration-Date Self-Audit

Seventeen yes/no checks that surface the gaps in how you manage expiration-dated FBA inventory — before a short-dated batch turns into a non-returnable write-off. Score yourself, then close the gaps.

Last reviewed·2026-05-31

Short version

An Amazon FBA expiration-date self-audit is a 17-point review of whether your process actually keeps dated inventory from going unsellable. It checks four areas: mapping (every batch has its own MSKU with an Expiration Date and an Unsellable by Date), reconciliation (your dates are checked against Amazon's record), acting in time (FEFO pricing and a disposal decision before the Unsellable by Date), and cadence(new dated ASINs are detected and worked on a schedule). Any "no" is a gap where money leaks — Amazon disposes units near expiry and does not return them. US marketplace.

How to use this

Answer each line yes or no for your own account. A "no" isn't a failing grade — it's a pointer to the one process change that prevents the next write-off. Work top to bottom: mapping is the foundation (everything downstream depends on per-MSKU dating), then reconciliation, then acting in time, then the cadence that keeps it from drifting. A printable version is on the way; for now, copy the four lists below.

1 · Mapping & data hygiene

  • Every expiration-dated ASIN has its own MSKU per batch — never one MSKU shared across two production dates. See FNSKU and MSKU expiration date tracking.
  • Each MSKU has a mapped Expiration Date and an Unsellable by Date.
  • Lot number, PO, and invoice are recorded for each batch (the evidence a Seller Support case needs later).
  • Batches with different expiration dates are never merged under one MSKU or commingled by date.

2 · Reconciliation & discrepancies

  • You've reconciled your mapped date against Amazon's reported date from the inbound record.
  • Open date discrepancies are tracked, not ignored.
  • When a discrepancy needs Amazon, you file a Seller Support case yourself from a prepared template — and you know Amazon decides the outcome.

3 · Acting before the Unsellable by Date

  • You review days-to-expiry on a set cadence (for example, weekly).
  • FEFO pricing is applied to your at-risk (shorter-dated) MSKUs so the soonest batch clears first.
  • You have a disposal/return decision rule in place before the Unsellable by Date — see disposal vs. return orders.
  • Disposal Requests are scheduled for a date you choose and reviewed before submission.

4 · Coverage & operational cadence

  • New expiration-dated ASINs are detected and routed to an Unmapped queue instead of being missed on a re-order.
  • The Unmapped queue is worked down regularly.
  • You run periodic Bin Checks on expiration-dated stock — see FBA inventory bin check.
  • Subscribe & Save inventory exposure is monitored so subscriptions don't ride a short-dated MSKU.
  • You re-run this self-audit on a recurring schedule.

Reading your score

Count your gaps— the lines you answered "no." The more gaps, the more urgent the review. Find your band:

0–4 gaps — Basic review needed

  • What it means: Your expiration process is solid — only light upkeep is needed.
  • What to review first: Keep the weekly days-to-expiry review and date reconciliation tight.
  • Suggested next step: Spot-check any new dated batch with the free Unsellable by Date calculator. A repeatable tool is optional until your dated-SKU count grows.

5–9 gaps — Moderate expiration risk

  • What it means: The foundation is there, but drift is likely — usually in reconciliation and coverage.
  • What to review first: Re-check your MSKU/FNSKU expiration mapping (Section 1) and your reconciliation against Amazon’s record (Section 2).
  • Suggested next step: Run the calculator on at-risk batches. If the manual cadence is slipping, Shelfdoc can systematize per-MSKU mapping, discrepancy flagging, and alerts.

10–13 gaps — High operational risk

  • What it means: Several core workflows are missing, so losses are likely recurring.
  • What to review first: Fix per-MSKU/FNSKU mapping first (Section 1) — every later check depends on it — and review what Inventory Intelligence would surface from your FBA history.
  • Suggested next step: Use the calculator now. Consider Shelfdoc to map per-MSKU, flag Date Discrepancies, run FEFO pricing, and schedule Disposal Requests you review.

14–17 gaps — Urgent review needed

  • What it means: Dated inventory is exposed to full-cost, non-returnable write-offs.
  • What to review first: Map per-MSKU/FNSKU expiration dates today, then put a weekly days-to-expiry review on the calendar.
  • Suggested next step: Calculate your soonest Unsellable by Date today. A repeatable workflow (e.g. Shelfdoc) puts detection, reconciliation, FEFO, and removals on a schedule — you stay in control and Amazon controls acceptance.

The fastest wins are almost always (1) splitting commingled batches into per-MSKU dates and (2) putting a weekly days-to-expiry review on the calendar.

Next: estimate your soonest Unsellable by Date with the free calculator, or create an account to track every MSKU on a schedule. You decide; Amazon controls acceptance.

What Shelfdoc does not do

Shelfdoc supports this audit's workflow — per-MSKU date mapping, date-discrepancy reconciliation with a Seller Support case template you file, FEFO pricing on at-risk MSKUs, and scheduled Disposal Requests you review. What it does not do:

  • Does not read or assign expiration dates for you — you map each MSKU's date.
  • Does not file Seller Support cases or change Amazon's records.
  • Does not submit anything to Amazon without your review — Amazon controls acceptance, timing, and outcomes of every request.
  • Covers the US marketplace only; AWD history is used only where authorized and available.

Frequently asked questions

What is an FBA expiration-date self-audit?
It is a short yes/no review of the process you run to keep expiration-dated FBA inventory from quietly going unsellable. It checks four things: that every expiration batch has its own MSKU with a mapped Expiration Date and Unsellable by Date; that your dates are reconciled against Amazon's record; that you act (price down, dispose, or remove) before the Unsellable by Date; and that new dated inventory is detected and worked on a cadence. The point is to surface the gap that turns into a write-off before it does.
Why does each expiration batch need its own MSKU?
One ASIN can have several production batches in FBA at once, each with a different printed date. If two batches share one MSKU, you can't tell which Amazon will ship, and a short-dated batch can go unsellable while a long-dated batch of the same ASIN keeps selling. Per-MSKU dating keeps the batches distinct so the soonest-dated one can be priced down or removed on time. See FNSKU and MSKU expiration date tracking.
What is the Unsellable by Date and why does the audit center on it?
The Unsellable by Date is the internal cutoff Amazon uses to FEFO-block a unit — it comes before the printed expiration date. Amazon generally stops shipping an expiration-dated unit a window before the printed date (often described as around 50 days — confirm the current rule in Seller Central) and disposes units close to expiry, and disposed units are not returnable to the seller. Every "act in time" check on this audit is about doing something before that date arrives.
The audit says to file a Seller Support case "yourself" — why not automatically?
Shelfdoc compares your mapped date against Amazon's reported date and, when they differ, produces a ready-to-paste Seller Support case template. It does not file the case for you and cannot make Amazon change a record — Amazon controls acceptance, timing, and outcomes. The audit reflects that: the controllable step is keeping the discrepancy tracked and bringing a clean case, not assuming the system fixes Amazon.
How often should I re-run this self-audit?
Re-run it whenever your catalog or cadence changes materially, and at least quarterly. The two checks most worth repeating are reconciliation (your date vs. Amazon's) and coverage (are new dated ASINs being detected and worked). Those are where drift accumulates between audits.
Do I need software to pass this audit?
No — a disciplined seller with a small catalog can pass it with a spreadsheet plus calendar reminders. The audit measures the process, not the tool. Software earns its place when the per-MSKU count and the reconciliation step grow past what you can reliably hold by hand. See the spreadsheet-alternative comparison for an honest look at where each option fits.

Turn the checklist into a system

Every "no" on this audit is a workflow Shelfdoc runs: per-MSKU dating, date-discrepancy reconciliation, FEFO pricing, and scheduled Disposal Requests you review — with a timestamped audit trail. Choose a plan to set it up and connect Amazon.

Create account