What is an FBA inventory bin check?

An FBA inventory bin check is a periodic reconciliation between the seller's authoritative record of what should be in FBA — per MSKU, per expiration batch, with an expected quantity — and what Amazon's reports show is actually there. The cadence is usually weekly. The work catches date discrepancies, missing units, and at-risk batches before Amazon's automated tooling (FEFO blocking, listing suppression) catches them.

Why do operators run weekly bin checks on FBA inventory?

Three reasons. First, Amazon's public reports do not surface expiration-date discrepancies until a unit goes FEFO-blocked — usually weeks too late. Second, quantity drift from Amazon-side losses, customer returns, and warehouse moves accumulates silently. Third, a weekly cadence catches problems on a known schedule rather than reacting after a buyer complaint. The bin check is the operator ritual that keeps the per-MSKU model honest against Amazon's record.

How does a bin check differ from a normal inventory report?

A normal inventory report shows Amazon's view — quantities by MSKU, totals across the account. A bin check is a side-by-side reconciliation: the seller's expected quantity per MSKU per expiration batch vs. Amazon's reported quantity, with flags on every divergence. The reconciliation makes the discrepancies actionable rather than just visible.

What does a thorough bin check actually look at?

Three layers per MSKU. (1) Quantity — does Amazon's reported quantity match the seller's expected quantity after accounting for sales, returns, and pending Removal Orders. (2) Expiration date — does the date Amazon recorded at receiving match the date on the actual batch. (3) Status — are there units stranded, FEFO-blocked, or in pending Removal Orders that the operator needs to act on. Each layer surfaces a different category of problem.

How often should a seller run an FBA bin check?

Weekly is the operator floor for any account with expiration-dated inventory. Monthly is acceptable only for low-volume accounts where each MSKU has months of runway. Daily is reasonable for high-volume accounts during periods of fast inventory turnover. The wrong cadence is "when I remember" — bin checks only work as a ritual on a known schedule.

Can a seller run bin checks without software?

Yes, but the manual version requires pulling Amazon reports into a spreadsheet, joining against the seller's own per-MSKU record, and computing the deltas. For an account with 20 MSKUs and a clean record this takes maybe an hour per week. At 200+ MSKUs the manual version stops being feasible — software like Shelfdoc surfaces the divergences as a queue rather than asking the operator to compute them.

FBA Inventory Bin Check

Short version

An FBA inventory bin checkis a weekly reconciliation between the seller's authoritative per-MSKU record — expected quantities and expiration dates per batch — and what Amazon's reports show. The work catches date discrepancies (the dates Amazon stored at receiving differ from the dates on the actual batch), quantity drift (Amazon-side losses, returned units, pending Removal Orders), and at-risk batches before Amazon's FEFO blocking or listing suppression catches them. Weekly cadence is the operator floor for accounts with expiration-dated inventory.

What a bin check is, in operator terms

The bin check is the ritual that keeps the seller's per-MSKU record honest against Amazon's record. Without it the two records drift silently — Amazon's public reports do not surface expiration-date discrepancies until a unit goes FEFO-blocked, and they do not surface quantity drift in actionable form until the seller queries the right report at the right time.

A bin check is not an audit of Amazon. It is an audit of the seller's own record against Amazon's. Where the two disagree, the seller's job is to decide which one is authoritative for that field — usually the seller's record for expiration dates (because the seller knows what was in the case-pack), and Amazon's record for current quantity (because units move through fulfillment continuously).

Cadence — weekly is the right floor

Weekly is the floor for any account with expiration-dated inventory. Catches discrepancies before they age into FEFO blocks.
Daily is appropriate during high-velocity periods (Prime Day prep, Q4 ramp, new-product launch).
Monthly is only safe for accounts where every MSKU has at least 4 months of runway before Unsellable by Date and the operator is willing to accept some FEFO-block surprises.
Ad-hoc — "when I remember" — is the failure mode. Bin checks only work as a ritual on a known schedule because the value is in catching problems before they age, and ad-hoc rituals don't catch fast-aging problems.

The bin-check workflow

Pull Amazon's current FBA inventory report. Per-MSKU current quantity, current Unsellable by Date, current FEFO status.
Pull Amazon's inbound plan records. The dates Amazon stored at receiving for each MSKU.
Reconcile quantity per MSKU. Expected = previous quantity + inbound received − units sold − units removed − units returned. Compare against Amazon's current quantity. Flag any delta exceeding a tolerance threshold.
Reconcile expiration dates per MSKU. Compare the seller's recorded expiration date for each MSKU against the date Amazon recorded at receiving. Flag every divergence.
Triage status. Surface FEFO-blocked units, suppressed listings, and pending Removal Orders that need attention.
Decide per flag. File a Seller Support case for incorrect Amazon-side dates. File a Disposal Request on FEFO-blocked units. Investigate quantity divergences exceeding the tolerance.
Log the result. Even a clean bin check is worth recording — proves the cadence was honored. The audit trail matters for downstream reimbursement appeals and accounting reconciliation.

A working example

A coffee seller runs a Friday-morning bin check across 84 active MSKUs. The reconciliation surfaces three flags:

Date discrepancy on COF-B0COF7-2026-09. The seller recorded Unsellable by Date of August 14 2026. Amazon's inbound record shows August 4 2026 — Amazon read the case-pack date 10 days early. The operator files a Seller Support case with the case-pack photo and the actual manufacturer date.
Quantity drift on COF-B0COF3-2026-05. Expected 480 units; Amazon reports 467. 13-unit delta exceeds the seller's 5-unit tolerance. Investigation: 8 units returned and not yet restocked, 5 units missing — Amazon's reimbursement queue is the next step.
FEFO-block on COF-B0COF1-2025-12. 18 residual units past Unsellable by Date. The scheduled Disposal Request fired Wednesday; Amazon's status shows Processing. No action needed — the operator notes the timestamp in the audit log.

Total bin-check time: ~12 minutes. Without the weekly ritual the date discrepancy would not have surfaced until those units went FEFO-blocked on August 4 — at which point the seller would have lost 10 days of sales velocity on the batch and the Seller Support case would have been harder to win without the receiving-date evidence captured close to receipt.

Common mistakes

Treating Amazon's quantity as authoritative. Amazon's reports are usually right but quantity drift is real and reimbursable. The seller's expected quantity is the baseline; Amazon's reported quantity is the comparison.
Skipping date reconciliation. Quantity-only bin checks miss the highest-leverage flag — date discrepancies that produce wrong-batch disposals weeks later.
Running bin checks ad-hoc. The discipline is the value. A weekly cadence on every Friday morning catches problems on a known schedule; an ad-hoc cadence catches whatever was about to break at the moment the operator remembered to check.
Not logging clean bin checks. The audit trail matters for downstream cases. A clean bin check is evidence that the cadence was honored.

How Shelfdoc helps

A Bin Checks queue that surfaces date discrepancies, quantity drift, FEFO blocks, and pending Removal Orders in one view.
Daily reconciliation against Amazon's inbound record. Discrepancies queue for review with a one-click resolution path.
A weekly bin-check ritual the operator can run inside Shelfdoc — surfacing flags, accepting clean MSKUs, drafting Seller Support cases on the divergences that need them.
A timestamped audit trail of every bin check — including clean ones — exportable to PDF and Excel for accounting and Seller Support cases.

What Shelfdoc does not do

Shelfdoc does not negotiate reimbursement with Amazon Seller Support — but it does prepare the case data and audit-trail evidence for the operator to file.
Shelfdoc does not move physical inventory or instruct Amazon's receiving operation.
Shelfdoc does not guarantee Amazon's response time on a Seller Support case.
Shelfdoc does not provide legal, tax, accounting, or regulatory advice.

Amazon FBA expiration date management — the full lifecycle.
Amazon FBA stranded inventory + expiration — what the bin check catches before it strands.
FNSKU and MSKU expiration date tracking — the per-MSKU model the bin check reconciles.
Amazon FBA Removal Order expiration — the disposition path for flagged batches.
Resources hub — every guide, glossary entry, calculator, and decision framework, organized by topic.

Frequently asked questions

What is an FBA inventory bin check?: An FBA inventory bin check is a periodic reconciliation between the seller's authoritative record of what should be in FBA — per MSKU, per expiration batch, with an expected quantity — and what Amazon's reports show is actually there. The cadence is usually weekly. The work catches date discrepancies, missing units, and at-risk batches before Amazon's automated tooling (FEFO blocking, listing suppression) catches them.
Why do operators run weekly bin checks on FBA inventory?: Three reasons. First, Amazon's public reports do not surface expiration-date discrepancies until a unit goes FEFO-blocked — usually weeks too late. Second, quantity drift from Amazon-side losses, customer returns, and warehouse moves accumulates silently. Third, a weekly cadence catches problems on a known schedule rather than reacting after a buyer complaint. The bin check is the operator ritual that keeps the per-MSKU model honest against Amazon's record.
How does a bin check differ from a normal inventory report?: A normal inventory report shows Amazon's view — quantities by MSKU, totals across the account. A bin check is a side-by-side reconciliation: the seller's expected quantity per MSKU per expiration batch vs. Amazon's reported quantity, with flags on every divergence. The reconciliation makes the discrepancies actionable rather than just visible.
What does a thorough bin check actually look at?: Three layers per MSKU. (1) Quantity — does Amazon's reported quantity match the seller's expected quantity after accounting for sales, returns, and pending Removal Orders. (2) Expiration date — does the date Amazon recorded at receiving match the date on the actual batch. (3) Status — are there units stranded, FEFO-blocked, or in pending Removal Orders that the operator needs to act on. Each layer surfaces a different category of problem.
How often should a seller run an FBA bin check?: Weekly is the operator floor for any account with expiration-dated inventory. Monthly is acceptable only for low-volume accounts where each MSKU has months of runway. Daily is reasonable for high-volume accounts during periods of fast inventory turnover. The wrong cadence is "when I remember" — bin checks only work as a ritual on a known schedule.
Can a seller run bin checks without software?: Yes, but the manual version requires pulling Amazon reports into a spreadsheet, joining against the seller's own per-MSKU record, and computing the deltas. For an account with 20 MSKUs and a clean record this takes maybe an hour per week. At 200+ MSKUs the manual version stops being feasible — software like Shelfdoc surfaces the divergences as a queue rather than asking the operator to compute them.

Make weekly bin checks a 12-minute ritual

Surface date discrepancies, quantity drift, and at-risk batches in one queue. Resolve in-place. Keep a timestamped audit trail of every check.

Create account