Are Amazon case transfers normal?

Yes, transfers are common. However, repeated transfers without progress usually mean the case is not reaching the correct internal team.

Can sellers request escalation directly?

In some cases yes, but escalation only works if the case meets Amazon’s internal criteria. Otherwise it often results in further transfers.

How long should I wait before changing strategy?

If your case has been transferred multiple times or shows no progress after several business days, a different escalation approach is usually needed.

FBA Reimbursement: When to Request vs Keep Investigating (2026 Checklist)

One of the most common mistakes Amazon sellers make isn’t missing reimbursements. It’s filing too early, too late, or too vaguely.

In 2026, Amazon’s reimbursement process is more structured, more automated, and less forgiving. If your request isn’t tied to a clear, reimbursable event with clean proof, it either gets delayed or denied.

This is why experienced operators treat reimbursements as a routing decision, not a support request.

This checklist helps you decide quickly:
Should you file now, or keep investigating?

The FBA Reimbursement Checklist (2026)

Phase 1: Define the Event Clearly

Before anything else, identify the exact issue.

☐ Lost inventory (warehouse loss)
☐ Damaged in fulfillment center
☐ Customer return not received
☐ Customer refund without return
☐ Removal or disposal discrepancy
☐ FC transfer discrepancy

Rule:
If you cannot name the exact event, you’re not ready to file yet.

Phase 2: Check Inventory & Event Status

Confirm whether Amazon has already acknowledged or is still processing the issue.

☐ Inventory adjustments logged in reports
☐ Shipment status (receiving, closed, reconciled)
☐ Returns status (in transit, processing, completed)
☐ Event marked as “researching” or unresolved

2026 Reality:
If Amazon is still processing or investigating internally, filing too early often resets or delays resolution.

Phase 3: Apply the “Wait or File” Rule

Use this to decide your next move:

File now if:

☐ The event is complete and no longer changing
☐ The loss/damage is clearly recorded
☐ The reimbursement window is open and valid
☐ You have matching data across reports

Wait and monitor if:

☐ Status is still “researching”
☐ Inventory movement is ongoing
☐ Data is inconsistent or incomplete
☐ You’re missing a clear event trail

Phase 4: Write the Request Like a Routing Instruction

Amazon support responds better to clarity than explanation.

☐ Start with a one-sentence “Requested Action”
☐ Example: “Request reimbursement for 12 units lost during FC transfer for Shipment ID X”
☐ Avoid long narratives or multiple issues in one case

Key idea:
You are not asking support to investigate. You are pointing them to a specific reimbursable event.

Phase 5: Include Only Critical Identifiers (Up Front)

Make it easy for support to act immediately.

☐ ASIN
☐ SKU
☐ FNSKU
☐ Shipment ID / Order ID
☐ Relevant dates (receive date, transfer date, etc.)

Phase 6: Attach Proof That Matches the Claim

Only include evidence that directly supports your request.

☐ Inventory ledger or adjustments
☐ Shipment reconciliation data
☐ Event logs showing custody with Amazon
☐ Screenshots of discrepancies

Avoid:
Uploading everything. Irrelevant attachments slow down case handling.

Phase 7: Manage the Case Properly

After submission:

☐ If status is unclear, follow up in the same case thread
☐ Wait a defined interval before following up (don’t spam)
☐ Keep responses consistent with the original request

Important (2026):
Opening new cases for the same issue often resets progress.

Phase 8: Escalate Strategically

If resolution stalls:

☐ After 2–3 responses with no progress, request supervisor review
☐ Reference the full case thread for context
☐ Restate the requested action clearly

Real Example

Units disappear after a fulfillment center transfer.

Shipment is received
Transfer log shows movement
Units never reappear in sellable inventory

→ This is a clean reimbursement claim if the event log confirms Amazon custody.

Common Mistakes That Lead to Denials

☐ Asking support to “investigate everything”
☐ Filing without a defined reimbursable event
☐ Mixing multiple issues in one case
☐ Submitting incomplete identifiers
☐ Attaching irrelevant or excessive documentation

Want a Second Look Before You File?

If you’re unsure whether to request a reimbursement or keep investigating, that’s usually where things get tricky.

Some cases look straightforward but end up getting denied or delayed because of timing, missing data, or how the request is structured.

We’ve broken down how we approach these situations and what typically works based on recent Amazon workflows.

👉 See how Seller Candy handles FBA reimbursement cases
It’ll give you a clearer idea of what to check next and how to move forward without wasting time on back-and-forth with support.