Why Amazon Removal Orders Get Cancelled at SDC Warehouses
FBA sellers assume that submitting a removal order is a straightforward fix for stranded or unwanted inventory. In practice, a less-known wrinkle can derail the entire process: Amazon's Supply Chain Services network includes Storage and Distribution Centers (SDCs) that are not configured to process standard removal orders. When Amazon's placement algorithm routes your inventory to one of these facilities, every removal request you submit can be silently cancelled by the system, yet the storage clock keeps running.
That is precisely what happened in the story behind this guide. A seller's inventory for two ASINs was routed to HGR5, an SDC, without the seller's knowledge or consent. Over four months, the seller submitted nine separate removal orders covering 5,750 requested units. The system cancelled 3,607 of them, a 62.7% cancellation rate, while simultaneously charging $2,981.46 in combined monthly storage and aged inventory surcharge fees. Four support cases produced zero resolution.
This pattern is not unique. If you have found this article after facing the same cycle, you are dealing with what sellers on forums increasingly call an "SDC trap": inventory locked in a facility that cannot execute removals, fees accruing on inventory you are actively trying to leave, and support responses that sidestep the core issue. Understanding the mechanics is the first step toward building an appeal that actually moves the needle.
For a broader look at how storage-related disputes connect to account health, see our FBA inventory management and appeals.
For related step-by-step guidance, see A-to-Z guarantee claim guide.
The Financial Anatomy of an SDC Storage Fee Dispute
Before writing a single word of your escalation letter, you need to document the financial damage with precision. Vague complaints about "storage fees" rarely generate credits. Specific, itemized documentation of cancelled removal orders cross-referenced against fee charges is the type of evidence that compels a senior case owner to act.
For the seller in this story, the breakdown looked like this:
- Monthly storage fees — $984.69 charged across the period the inventory sat in HGR5 unable to be removed
- Aged inventory surcharge — $1,996.77 assessed on the same units that were aging because removal was impossible
- Total wrongful charges — $2,981.46
Every dollar of that total was traceable to a system-side failure, not a seller decision. The seller never chose HGR5. The seller never abandoned the inventory. The seller submitted removal orders repeatedly, and the system repeatedly cancelled them.
That causal chain is the backbone of your appeal. Sellers who skip this documentation step and write generic complaint letters rarely see fee credits. Sellers who map each cancelled order number, date, units requested, and units cancelled directly to the storage fee line items on their account give Amazon's team a clear audit trail to follow.
"The most effective escalation letters I've reviewed are essentially mini-spreadsheets in prose form. The seller tells Amazon exactly which removal orders failed, exactly which fees resulted, and leaves no inferential gap between the two." — Deirdre Callahan, Senior Marketplace Compliance Strategist, Northridge Seller Advisory Group
For related step-by-step guidance, see related seller case: Removing Amazon.
How Amazon's Support Failures Compound the Problem
One of the most demoralizing aspects of this scenario is watching support cases get deflected rather than resolved. In the seller's story above, four cases were opened over four months. A common deflection tactic is for an agent to pivot the conversation toward weight and dimension discrepancies or other unrelated issues, effectively closing the loop on the removal cancellation problem without addressing it.
When you are building your escalation, document each support case the same way you document each removal order: case number, date opened, subject of the response you received, and how that response failed to address the actual issue. This meta-documentation tells executive escalation teams that standard support has already been exhausted, which strengthens the urgency of your request.
For context on how Amazon's seller support escalation tiers work and when to invoke them, consult Amazon's own Seller Central contact and case tracking workflow guidance.
How to Write an FBA Storage Fee Refund Escalation Letter
The structure below reflects what works in fee dispute escalations where the cause is a system-side failure rather than a seller policy violation. Follow these steps in order, and keep every step's evidence attached or referenced by case number.
- Open with a clear, factual subject line that names the dollar amount, the number of failed removal orders, and the duration. Example: "Request for $2,981 Storage Fee Refund: 9 Removal Orders Cancelled by System Over 4 Months."
- State in the first paragraph that you are escalating after exhausting standard support, and list each case number and the date it was opened so the reader can pull the history without asking.
- Present an itemized removal order table: order ID, submission date, units requested, units cancelled, and cancellation percentage. This visual structure makes the pattern undeniable.
- Map each fee charge to the period covered by the cancelled removal orders. Use your Payments report and your Inventory Ledger report as source documents; cite them by name so the reviewer knows exactly where to verify.
- State the specific relief you are requesting: a full credit of the storage fees and aged inventory surcharges assessed during the period the removal orders were cancelled, and confirmation that the remaining inventory will be successfully removed or transferred to a standard FC where removal is supported.
- Attach or reference any Amazon communications acknowledging the SDC placement or the removal cancellations, even partial acknowledgements, as these establish that Amazon's own system flagged the issue.
- Close with a clear escalation path request: ask to be assigned to a senior case owner or executive seller relations representative who has authority to issue fee credits.
This is the letter structure that AppealsPro.ai's Appeal Letter Generator produces for FBA storage fee disputes, drawing on policy-specific templates that align with the exact language Amazon's internal teams expect to see.
Gathering the Right Evidence: Document Checklist for SDC Removal Disputes
Evidence gaps are the most common reason well-intentioned escalation letters fail. The AppealsPro.ai Document Checklists tool provides a violation-specific checklist so you never submit an escalation missing a critical attachment. For an SDC removal order dispute, the core evidence set includes:
- Removal order records: Export every removal order from the "Removal Order Detail" report in Seller Central. Include order ID, creation date, completion status, and units cancelled.
- Inventory placement records: Show which fulfillment center or SDC the inventory was routed to, and confirm you did not manually select HGR5 or any other SDC.
- Storage fee invoices: Pull the monthly storage fee report and the aged inventory surcharge report for each billing period during which removal was blocked.
- Payments ledger entries: Cross-reference fee charges against the removal order cancellation dates to establish the causal timeline.
- Support case transcripts: Export or screenshot all previous case communications, organized by case number and date.
- ASIN-level inventory ledger: The Inventory Ledger report shows unit movements (or the absence of them) and confirms that inventory was not sold, destroyed, or transferred during the dispute period.
Having this documentation assembled before you write a single word of your letter gives your appeal immediate credibility. An escalation letter that says "please see attached Removal Order Detail report dated X showing 3,607 cancelled units" is categorically stronger than one that says "Amazon kept cancelling my removal orders."
For related guidance on inventory disputes that affect account health, see our account health and suspension prevention.
How AppealsPro.ai Compares to DIY vs Consultants
| Approach | Typical Cost | Time to First Draft | Coverage | Risk |
|---|---|---|---|---|
| DIY (forums + templates) | Free | 3–10 hours | Generalized templates only | High: missing evidence gaps, wrong tone |
| Hired consultant | Typically $1,500 to $5,000+ per case, per AppealsPro.ai's review of published U.S. pricing | 2–5 business days | Case-specific but expensive | Medium: quality varies widely |
| AppealsPro.ai | Free tier (unlimited notice analysis) or $79.99/mo Starter | Minutes | 94 appeal categories covered | Low: policy-specific, evidence-mapped |
The cost difference is significant. Based on AppealsPro.ai's review of published U.S. appeals-consultant pricing, single-case fees typically run $1,500 to $5,000+ depending on case complexity and consultant experience. For a fee dispute like the one in this story, where the seller has already lost $2,981 in storage fees, paying that much to recover them can erase the entire financial benefit of winning. AppealsPro.ai at $79.99/mo gives sellers unlimited access to appeal generation across all case types for a fraction of that cost.