UK-registered +44 7367 067226
WhatsApp FOLLOW f in X
  1. Home
  2. Blog
  3. What Should I Do With Unfulfillable FBA Stock Before the Fees and Disposals Pile Up?
Problems We Solve

What Should I Do With Unfulfillable FBA Stock Before the Fees and Disposals Pile Up?

Unfulfillable FBA units build up from returns and warehouse damage until a removal deadline forces a rushed decision. We build a tracker that decides earlier.

Updated 3 min readBy SpiderHunts Technologies

Free estimateNo obligation

Get a free estimate

Tell us what you need. A senior engineer reads every enquiry.

Takes under a minute. We never share your details.

  • Free consultation
  • No commitment
  • NDA on request

Prefer to talk? Book a free 30-minute call →

Quick answer: TL;DR

Unfulfillable units accumulate quietly from customer returns and warehouse damage, and the decision about them is usually made in a hurry. We build a tracker that records why each unit became unfulfillable, applies your rules for return, dispose or liquidate, drafts the removal orders and follows them through to what actually arrived back.

A report nobody wants to open

Somewhere in your FBA inventory there is a column of unfulfillable units. Customer damaged returns, carrier damaged, defective, expired. It creeps up by a few units a week, then a busy season adds a lot at once. Every so often someone creates a removal order for everything, the boxes arrive at your warehouse in a jumble, and a person spends two days opening them to decide what can be resold.

Meanwhile nobody has checked whether any of those units were damaged in Amazon's warehouse and should have been reimbursed rather than removed at your cost.

Why the pile keeps growing

Unfulfillable stock has no natural owner. The person who handles returns sees customer messages, not warehouse dispositions. The person who handles inbound is focused on getting stock in, not out. And the decision about each unit depends on information held in different reports: the disposition code, the reason for return, the unit cost and whether the product can be refurbished.

  • Disposition codes explain why a unit is unfulfillable but are spread across returns and inventory reports.
  • Warehouse damage and customer damage look the same unless you read the reason.
  • Whether a unit is worth returning depends on its cost, its size and your ability to repackage it.
  • Removal orders arrive back mixed, without a clear link to the original reason.

What the delay costs

Unfulfillable units count against your storage and can attract fees while they sit. Stock that could have been repackaged and sold again ages until it is no longer worth handling. Warehouse-damaged units that should have been claimed pass the point where a claim can be made. And the eventual bulk removal lands on your warehouse team at the worst possible moment, usually right after a peak.

There is also the decision quality problem. When everything is decided at once in a rush, expensive units get disposed of because nobody had time to look.

Take a typical example. A kitchen appliance comes back as customer damaged because the outer box was opened and taped. The unit itself is fine. Returned and repackaged, it is sellable stock. Left in the unfulfillable pile for months and then swept into a bulk disposal, it is a write-off plus a disposal fee. Multiply that by every product line with decent unit value and the case for deciding early is clear.

The unfulfillable tracker we build

  1. A daily pull of unfulfillable inventory, customer returns data and inventory adjustments through the Selling Partner API.
  2. For each unit, the disposition and reason recorded together, with warehouse damage separated from customer damage.
  3. Your rules applied per SKU or product line: return to your warehouse, dispose, or send to a liquidation option you use, based on unit cost, size and whether you can resell after checking.
  4. Warehouse-damaged units flagged for a possible claim, with the dates and references a person needs to check eligibility.
  5. Removal orders drafted in batches you choose, for a person to approve and submit.
  6. A receiving screen for when removals arrive, where your team records the condition of each unit and whether it goes back into sellable stock.
Unit typeTypical ruleWho decides
High value, customer damagedReturn for inspectionRule, then warehouse check
Low value, bulkyDispose or liquidateRule, person approves batch
Warehouse damagedCheck claim eligibility firstPerson
Expired or date-codedDisposeRule, person approves batch
Defective per customerReturn and inspectRule, feeds product quality log

The thresholds are yours. The system does not decide what a unit is worth to you; it applies the rules you set and shows its reasoning.

How the week looks afterwards

Unfulfillable units are handled in small, regular batches instead of an annual clear-out. Your warehouse receives removals it expected, with a list of what should be in the boxes and why each unit was sent back. Units that pass inspection go back into stock the same week.

The defective reasons also build into something useful: a running list of products customers say are faulty, with their comments attached, which is exactly what you need when talking to a supplier.

Recognise any of these?

  • Unfulfillable units are removed in one large batch once or twice a year.
  • Nobody checks whether damaged units were damaged by Amazon before removing them.
  • Removal boxes arrive and nobody knows what should be in them.
  • Stock that could be resold ends up disposed of because there was no time to check.
  • Defect complaints never make it back to the supplier conversation.

FAQ

Frequently asked questions

The questions readers ask us after this guide.

Still have a question?

Ask us directly. A senior engineer reads every question.

Ask about your project

Can removal orders be created automatically?

They can be drafted automatically. Submitting them stays with a person, since removal and disposal have costs and are hard to undo.

Does this help with reimbursement claims?

It flags warehouse-damaged units and gathers the details. Whether a claim is valid and raising it is a person's job, following Amazon's current policy.

What if we use a returns processing company?

The tracker can send removals to them instead of your warehouse and read back their inspection results if they provide an export or API.

What do you need from us?

Seller Central access through Amazon's authorisation, unit costs, and the rules you use today, even if they are informal.

Keep reading

More on Problems We Solve

Start here

Tell us where your Amazon back office slows you down

Describe how your Amazon account runs today: which marketplaces, FBA or FBM or both, the Seller Central reports you download by hand and the spreadsheets and tools sitting around them. We will tell you what we would build and what we would leave alone, and if an existing tool already does the job well, we will say so.

  1. You tell us what you needTwo minutes on the form, or a message on WhatsApp.
  2. A senior engineer reviews itAnd comes back with questions, a realistic range and an honest view on fit.
  3. Free 30-minute scoping callWe talk through scope, options and a realistic estimate, with no obligation.
Free estimateNo obligation

Talk to someone who builds this

Send a short brief and we will come back with an honest view and a realistic range.

Takes under a minute. We never share your details.

  • Free consultation
  • No commitment
  • NDA on request

Prefer to talk? Book a free 30-minute call →