Amazon FBA unfulfillable inventory is stock in Amazon’s fulfillment network that is in unsellable condition. Start by identifying the affected units and their disposition category, then separate the investigation into what happened from the decision about what to do with the stock. A damage category is a starting point for investigation, not a promise of reimbursement.
This guide covers diagnosis and responsibility routing. For the actual removal workflow, use the separate FBA removal orders guide.
What Amazon FBA Unfulfillable Inventory Means
Amazon’s official FBA Inventory API model defines totalUnfulfillableQuantity as the total number of units in its fulfillment network in unsellable condition. The same model separates customer-damaged, warehouse-damaged, distributor-damaged, carrier-damaged, defective, and expired quantities. Source checked November 7, 2026.
These are inventory classifications. They do not establish that every unit of an ASIN has the same condition, that a refund has been issued, or that a reimbursement claim will succeed. Work at the seller SKU and affected-unit level rather than treating an entire product as a write-off.
Keep neighboring problems separate:
- Unsellable condition: investigate the unfulfillable disposition and the affected stock.
- Reserved stock: investigate why units are reserved rather than assuming they are damaged. Follow the reserved inventory guide for that branch.
- An offer or listing problem: investigate the offer separately. Fixing a listing does not establish that a damaged physical unit is now sellable.
- Inventory under research: check its research status before assigning a final outcome.
The API model also has a separate researching quantity for misplaced or warehouse-damaged units being confirmed at fulfillment centers, checked November 7, 2026. That distinction matters when reconciling exports: a provisional investigation and a final disposition should not become two separate losses in your records.
Classify the Units Before Assigning Responsibility
Use the disposition to select the evidence trail, not to decide who pays. The categories below come from Amazon’s official API model, checked November 7, 2026; the investigation questions are a practical way to organize your work.
| Amazon inventory category | First investigation question | Evidence to gather | Internal owner |
|---|---|---|---|
| Customer damaged | What does the return history say about the affected unit? | Return reference, condition information, relevant product or packaging images | Returns operations |
| Warehouse damaged | Which inventory event recorded the warehouse damage? | Inventory event, quantity, date, related case references | Inventory reconciliation |
| Distributor damaged | What condition was recorded around supply and receipt? | Supplier lot, inbound preparation records, shipment references | Sourcing and receiving |
| Carrier damaged | Which movement and carrier records relate to the damage? | Tracking, shipment references, packaging records, available delivery evidence | Logistics |
| Defective | Is there a repeat fault in the product or batch? | Complaint pattern, lot number, supplier specifications, inspection results | Product quality |
| Expired | Which lot and date information identifies the stock? | Lot code, printed dates, receiving and rotation records | Inventory planning |
The model names these categories; it does not describe a complete reimbursement policy for them. A field called warehouse damaged is not, by itself, proof that a payment is due. Likewise, a customer-damaged category does not tell you that the buyer acted improperly.
Keep the recorded category and your hypothesis in different columns. For example, a cluster of defective returns might suggest a supplier problem, but the investigation still needs to connect the returns to a particular lot or failure mode. Recording the hypothesis as fact makes later supplier discussions harder.
If the category is missing or unclear, collect the identifiers and request clarification before attributing blame. A specific question about an identified quantity is more useful than a general complaint that inventory has disappeared.
Build an Evidence Packet Before Disposition
Preserve the available record before arranging a physical disposition. If you later need to explain a condition discrepancy, an export and a clear timeline are more useful than a remembered dashboard total.
Create a case folder for each distinct incident or batch. Include:
- Marketplace, ASIN, seller SKU, and FNSKU where available.
- The affected quantity and the date and time of the snapshot.
- The exact disposition label or field name as recorded.
- Related inbound shipment, return, inventory event, and removal references.
- Supplier lot or batch identifiers when you can connect them to the units.
- Available images, inspection notes, and correspondence.
- The next action, its owner, and a follow-up date.
Preserve original files alongside your working spreadsheet. If someone revises the working quantity, retain the earlier snapshot and explain the change. Otherwise, a perfectly reasonable status update can look like a contradiction when another teammate reviews the case.
A useful handoff looks like this:
Affected stock: [marketplace / SKU / quantity]. Recorded category: [exact label]. First observed: [date]. Related references: [IDs]. Evidence saved: [files]. Open question: [what needs confirming]. Requested action: [investigate condition / review eligibility / arrange disposition]. Owner and next review: [name / date].
This is an incident template, not a quoted Amazon submission form. Adapt it to the fields and evidence requested in your actual case.
When inspecting returned stock, record what you can observe separately from what a report says. An outer carton mark, an opened retail seal, and a functional product defect are different findings. Keeping those descriptions separate helps you identify whether the remedy belongs in packaging, preparation, or manufacturing.
Separate the Claim Decision From the Inventory Decision
Run two workstreams: financial investigation and physical stock disposition. They can share evidence without being the same decision.
Workstream A: establish the financial outcome
Check the current reimbursement policy applicable to the marketplace and incident. Match the inventory event to any related reimbursement or case record before opening another request. Then establish what evidence remains missing.
Do not infer eligibility, a filing deadline, or a reimbursement amount from the inventory category alone. The API model used for this guide describes quantities and dispositions, not those policy terms. Record the policy you actually use with its retrieval date in the case folder.
Give each investigation a clear next step: locate the transaction, ask for a missing event reference, submit the requested evidence, or close the case with a recorded outcome. An open case without an owner is not an inventory strategy.
Workstream B: decide what happens to the units
Evaluate the options actually available for those units in your account. If return is available, compare the recoverable value after inspection with the costs and work involved. If another disposition is offered, review its terms rather than assuming every category has identical options.
For the mechanics, continue to creating and tracking a removal order. Before confirming anything, check the current settings, any applicable notices, and the charges shown for your inventory. This guide does not establish an automatic-removal deadline, a default setting, or a universal fee.
Receiving stock back does not establish that it can be sold again. Inspect it, document the condition, and decide whether a legitimate recovery route exists. For date-sensitive products, also review the FBA expiration date requirements guide.
Make the final decision visible in both workstreams. A completed reimbursement investigation may still leave physical stock awaiting action; a completed removal may still leave a financial discrepancy unresolved.
Reconcile Quantities Without Counting a Unit Twice
Track physical units separately from money. Use an inventory record for quantities and movements, and a financial record for reimbursements, recoveries, and charges. Link them through case and transaction references rather than adding unlike figures together.
A practical tracking sheet needs these fields:
| Field | Purpose |
|---|---|
| Snapshot date and marketplace | Establishes when and where the quantity was observed |
| SKU and incident or lot reference | Keeps separate problems from being merged |
| Recorded disposition and affected quantity | Captures the stock problem |
| Research or case reference | Links the investigation without creating extra units |
| Physical disposition reference and status | Tracks what happened to the stock |
| Financial transaction reference and outcome | Tracks what happened to the money |
| Open action and owner | Makes the remaining work explicit |
Use a consistent snapshot date when comparing reports. A quantity observed before a movement and another observed after it describe different moments. Their difference needs an explanation, not an immediate assumption of additional loss.
For example, suppose an identified batch moves from an investigation record to a final disposition record. Your task is to link that transition to the same affected stock, not create another incident merely because a different report now shows it. Treat this as a reconciliation scenario, not a claim about how every Amazon report updates.
Close the incident only when the physical outcome and financial outcome are both documented. If either remains open, keep a follow-up action. That prevents a completed removal from hiding an unresolved claim or a payment from hiding stock that still needs attention.
Prevent the Same Disposition From Recurring
Use the category history to choose a focused prevention project. A broad goal to reduce unfulfillable inventory is less actionable than a specific investigation into leaking bottles from one supplier lot.
- Repeated customer-damaged records: compare the affected products, packaging, and available return explanations. Look for an identifiable pattern before redesigning the package.
- Repeated distributor- or carrier-damaged records: review preparation, protective packaging, handoffs, and shipment evidence with the relevant supplier or logistics partner.
- Repeated defects: connect the incidents to batch and inspection records. Ask the supplier to address the identified failure mode rather than merely replacing a shipment.
- Repeated expiry: revisit purchase quantities, lot visibility, and stock rotation. Keep expiration issues separate from simple slow sales.
- Repeated warehouse-damaged records: improve event reconciliation and evidence retention so each incident can be traced promptly.
Measure the pattern against the product’s own history and the available volume context. A larger count after a larger shipment is not enough to establish that quality has deteriorated. Preserve the comparison basis and any uncertainty about lot matching.
Give the prevention action its own owner. The person closing an inventory case may not be the person who can change supplier inspection or replenishment decisions. The case is finished when the stock is resolved; the improvement project is finished when the agreed change has been checked.
Frequently Asked Questions
Does unfulfillable mean Amazon will reimburse me?
No. Amazon’s inventory model describes unsellable condition and disposition categories. Eligibility and payment need a separate review against the applicable policy and incident records. Keep a reimbursement outcome separate from the inventory status.
Can fixing a stranded listing fix damaged units?
Treat those as separate diagnoses. An offer problem concerns whether inventory has a usable offer; a damage disposition concerns the physical stock. Resolve each identified issue rather than using a listing change as evidence that the units are sellable.
Should I remove every unfulfillable unit immediately?
First preserve the evidence and check the options and notices that apply to those units. Then assign a disposition decision and follow-up date. The right action depends on condition, recovery prospects, available options, and current account terms—not the headline total alone.
Closing Checklist
Before closing your next unfulfillable inventory incident, confirm that you have the affected identifiers, the recorded category, a dated evidence packet, an investigation owner, and a physical disposition decision. Link any financial outcome to the same incident without counting the stock again.
The most useful habit is simple: classify first, preserve evidence, then resolve stock and money separately. That turns a dashboard number into a manageable operations task.