Product · Scope

What Shelfdoc does — and doesn't.

Line-by-line scope so you can decide whether Shelfdoc fits before signing up. We'd rather lose a deal than oversell.

Last reviewed·May 8, 2026

Overview

What Shelfdoc is

Shelfdoc gives FBA sellers one place to manage expiration risk before it becomes a customer complaint. Track MSKUs, prioritize older inventory with FEFO pricing, review Disposal Requests, monitor Subscribe & Save risk, surface Bin Check opportunities from Amazon return signals, and keep proof of every action in the Audit Log. It is not an inventory-management suite, a re-pricer, or a forecasting tool — that focus is what lets us be precise about scope.

Requirements

Operating requirements — read before you sign up

Shelfdoc only works when each expiration-date batch can be tracked separately. These are not preferences — they are the prerequisites the workflow depends on. None of them require a custom MSKU; they require a one-MSKU-per-batch discipline.

One MSKU per ASIN and expiration-date batch

Before using Shelfdoc, make sure each expiration-date batch has its own MSKU in Amazon. You can do this with a Flat File for the ASIN or Add a Product under the ASIN. Then map that MSKU in Shelfdoc to the correct expiration date. FNSKU labels keep the FBA units tied to the right MSKU.

FNSKU barcodes on every unit

Every unit you ship into FBA must carry an FNSKU barcode tied to the correct MSKU. Amazon's commingling defaults are off the table — that is what lets Shelfdoc act on a specific batch when its Unsellable by Date arrives.

Not a replacement for Amazon catalog discipline

Shelfdoc is built for sellers who can separate expiration-dated inventory by MSKU and FNSKU. If you cannot or will not assign one MSKU per expiration-date batch and label every unit with its FNSKU, Shelfdoc's expiration-date control is not the right tool — Amazon's own Automated Unfulfillable Settings may be a better fit.

What Shelfdoc handles

What Shelfdoc handles for you

Every capability below ships in every plan. Tiers differ only by active mapped-MSKU count.

Per-MSKU expiration tracking

Every mapped MSKU carries an Expiration date and an Unsellable by Date you set. The dashboard names what is approaching expiration before it costs you.

Inventory Intelligence — auto-enrollment from FBA or AWD history

During setup, Shelfdoc reviews recent FBA history (and AWD history when wired) for ASINs that appear to have expiration-dated inventory. Detected ASINs are added to Inventory Intelligence; unmapped MSKUs under them surface in your Unmapped queue for review. You can also mark ASINs manually. Shelfdoc does not auto-assign expiration dates — you map each MSKU's Expiration Date and Unsellable by Date. AWD support depends on your Amazon authorization and connector availability.

Scheduled Disposal Request submission (seller-reviewed)

On the Unsellable by Date, Shelfdoc takes the listing off-sale and files a Disposal Request with Amazon. You review every submission; Amazon controls acceptance and the physical disposal. Pending → Submitted → Processing → Completed is visible end-to-end.

Request Early Disposal (exception path)

For inventory that needs to leave FBA before its scheduled Unsellable by Date, the Mapped row offers Request Early Disposal. Confirming the acknowledgement makes the MSKU unsellable, strands it from FBA selling, and submits the Disposal Request to Amazon immediately. Removal orders cannot be cancelled once submitted to Amazon.

FEFO pricing automation

One rule per ASIN: discount the soonest-expiring MSKU so it sells first. Other MSKUs stay at the reference price you save in Shelfdoc. Re-evaluates whenever a date changes, a winner sells out, or a new MSKU is mapped.

Override price (per MSKU)

Per-row toggle that inflates a listing's price (typically 10×) so it cannot accidentally sell while you are working it — useful right before a Stranded Inventory Override or while waiting on a Subscribe & Save transfer.

Stranded Inventory Overrides

A 3-hour override that lets you submit a fresh inbound shipment under an ASIN whose prior MSKU is stranded. Auto-closes safely; restores the original blocked state when it ends.

Daily date audit vs. Amazon

Every day, Shelfdoc compares your mapped expiration dates against Amazon's inbound shipment records. Mismatches show up in a one-click resolve queue.

Subscribe & Save monitoring

Daily read of your enrolled offers, active subscribers, and 30-day revenue. When the soonest-expiring MSKU is rotating next month, Shelfdoc names the replacement MSKU and the rotation deadline. You move the subscribers in Amazon's Subscribe & Save dashboard; Shelfdoc keeps the ledger.

Bin Check opportunities from Amazon return signals

When Amazon's FBA customer-returns report flags a mapped MSKU, Shelfdoc rolls the signal up to the parent ASIN and surfaces it as a bin-check opportunity. Shelfdoc generates the Seller Support message body for you to paste; you open the Seller Support case; Amazon performs the physical bin check. One bin check per ASIN per 30 days; outcomes (Sellable, Defective, or Rejected) flow back into the Audit Log.

Date Discrepancy workflow with Seller Support follow-up

When the Shelfdoc Expiration Date and the Amazon reported Expiration Date disagree, Shelfdoc surfaces the row in a queue with a status workflow (Needs review → Confirmed → Case opened → Waiting on Amazon → Resolved or Dismissed). When Amazon's record appears wrong, Shelfdoc shows you an example Seller Support case template you can copy and edit. You open the case manually in Seller Central; Shelfdoc records the case ID, tracks the outcome, and preserves every step in the Audit Log. Shelfdoc does not submit Seller Support cases automatically and cannot force Amazon to update an expiration date.

Operational Health monitor (not Amazon Account Health)

Shelfdoc's internal view of your account — connection trust, sync freshness, stranded inventory, date discrepancies, and disposal lifecycle. It tells you what to fix on the Shelfdoc side. It is NOT the same thing as your Amazon Account Health Rating in Seller Central, which Amazon owns.

Audit Log with PDF and Excel export

Every mapping change, Disposal Request, FEFO price update, Override price apply or restore, discrepancy resolution, and bin check is timestamped. Custom date-range CSV exports plus a PDF (with Excel companion) of every action you and Shelfdoc took.

Email alerts

Configurable thresholds at 30, 60, 90, or 120 days. Weekly summary digest. Disposal Request reminders and completion receipts. Date-discrepancy alerts. Bin Check alerts. Subscribe & Save alerts. Toggle individually in Settings.

What Amazon controls

What Amazon still controls

Some operations belong to Amazon, not Shelfdoc. We surface the right context so you can act, but the action itself happens on Amazon's side.

The actual disposal date

Amazon's stated SLA is 7–14 business days. We can't make Amazon move faster — we file on the day you choose and show the lifecycle clearly.

Subscribe & Save subscriber transfer

The transfer click happens in Amazon's Subscribe & Save dashboard. Shelfdoc names the timing and the MSKU pair; the click is yours.

Amazon's inbound expiration record

Amazon's record comes from the inbound shipment plan you submitted in Seller Central. Shelfdoc flags mismatches and helps you prepare a Seller Support case template, but Shelfdoc cannot rewrite Amazon's record. Amazon controls whether any date is updated.

Stranded-inventory recovery

When Amazon's "Fix Stranded Inventory" worker auto-relists a strand, Shelfdoc detects it and re-strands. We can't prevent the auto-relist itself.

Pricing decisions outside FEFO

FEFO sets the discount math. We don't bid against the Buy Box or adjust for competitors — repricers do that.

Listing creation, suppression, content

Shelfdoc reads catalog metadata only. We don't create listings, edit titles, manage images, or appeal listing-level violations.

Disposal Request rejection appeals

If Amazon rejects a Disposal Request, we show you the verbatim error and let you Retry. The Seller Support conversation is yours.

What you do

What you still do as the seller

Shelfdoc is a tool, not a managed service. The work below stays with you.

FNSKU labeling

Every unit, one MSKU per distinct expiration-date batch. Shelfdoc's tracking model assumes this — commingled stickered and unstickered units break it.

Inbound shipment creation

You create shipments in Seller Central or your prep tool. Shelfdoc picks up once units land in FBA.

Disposal confirmation

Every Disposal Request requires explicit confirmation by default. Opt into auto-removal per row when you want it.

Subscribe & Save subscriber transfer

Amazon doesn't expose this to third-party tools. You complete the transfer in Amazon's dashboard; Shelfdoc tells you when and which MSKUs.

Anything Amazon-side

You handle every conversation with Amazon — Account Health appeals, Seller Performance, Seller Support cases. Shelfdoc gives you a PDF (with Excel companion) of every action you took: risk summary, mapped dates, Disposal Requests, discrepancy resolutions, bin checks, and the Audit Log. Whether and how to share it is your call.

Roadmap

On the roadmap, not yet shipped

Listed so you don't buy expecting them today. Rough priority — not a committed timeline.

Marketplaces beyond US

Today: US only. Canada and UK on the roadmap once we have active sellers in each marketplace.

Return-style removals

Today: disposal-only. Removal-as-return is on the roadmap for sellers with secondary channels.

Direct Subscribe & Save subscriber transfer

Only ships if Amazon opens this up to third-party tools. Until then, the transfer stays a step you complete in Amazon's dashboard.

Multi-user team accounts

Shelfdoc is single-user today. Multi-seat is on the roadmap.

Forecasting and restock recommendations

Today: velocity and sellthrough projections only. Full restock planning is a separate product area.

Definitions

Plain-English definitions

The terms used throughout the app, in seller language.

MSKU: Merchant Stock Keeping Unit. One batch of inventory under one ASIN. Multiple MSKUs can share an ASIN; Shelfdoc tracks at MSKU resolution.
ASIN: Amazon Standard Identification Number. The product ID Amazon uses for the listing.
FNSKU: Fulfillment Network SKU. The barcode Amazon prints on each unit so it can route the correct MSKU. Required for Shelfdoc's tracking model.
Tracked MSKU: A mapped MSKU with status "mapped". Counts toward your plan cap. Monitoring, expired, ignored, and unmapped MSKUs do not count — Monitoring MSKUs remain under permanent disposal monitoring even though they sit outside the cap.
Reference price: The price saved in Shelfdoc for an ASIN. FEFO discounts the priority MSKU from this reference price.
Unsellable by Date: The date you want Shelfdoc to start the disposal cycle. Distinct from expiration because Amazon's removal SLA is 7–14 business days.

For a deeper read on each capability, /resources carries the full operator content library with worked examples.

Operator references

Go deeper on the FBA mechanics

Amazon FBA Expiration Date Management — the four-stage lifecycle and the levers a seller actually controls.
Amazon FBA Unsellable by Date — how Amazon calculates it, and how to schedule Disposal Requests against it.
FNSKU and MSKU Expiration Date Tracking — why per-MSKU is the correct unit of work.
Amazon FBA Expiration Date SOP — the full operator playbook (intake routine, weekly rhythm, scheduled removals, Subscribe & Save transfers, recovery actions).
Expiration Date Glossary — plain-English definitions of the terms used throughout this page.