Skip to main content
TroubleshootingAugust 25, 2026

Amazon FBA Shipment Stuck in Transit: What to Do, Day by Day

FBA tracking says In Transit for weeks? The real timelines behind every inbound status, plus a day 3, 7, 15, 30 action plan and how to get reimbursed.

Forbes Business Council E-Commerce LeaderAmazon SPN Certified ProviderAmazon SP-API Authorized PartnerE-Commerce Entrepreneur & AdvisorFounder of PrepVia
Amazon FBA Shipment Stuck in Transit: What to Do, Day by Day

By Bernardo Campelo, Forbes Business Council E-Commerce Leader, Amazon SPN Certified provider, Amazon SP-API authorized partner, and Founder of PrepVia.

Last month a seller forwarded me his Seller Central screen with one line highlighted: In Transit, 19 days. Fourteen pallets of wholesale replenishment, the Q4 buy already committed against it. He wanted to know who to sue.

The shipment was fine. It had spent eleven of those nineteen days in a delivery appointment queue at a California fulfillment center, which the In Transit label does not distinguish from a truck in a ditch. He burned two weeks of stress on a status that compresses five different physical situations into two words.

I run PrepVia, a prep center in Miami, Florida. We hand shipments to Amazon every business day, small parcel and LTL both, and we watch what the tracking actually does after the truck leaves our dock. This is the troubleshooting page I wish I could send every seller who messages me on day 19: what each status really means, how long each one takes before it means trouble, and exactly what to do on day 3, day 7, day 15, and day 30.

The 60-second version

The statuses: In Transit, Delivered, Checked-In, Receiving, Closed. Only two of them are Amazon's responsibility. In Transit belongs to the carrier, Delivered is the handoff, and everything after Checked-In happens inside the fulfillment center.

When stuck is normal: LTL freight showing In Transit for 2 weeks during appointment backlogs, Delivered without Checked-In for up to 7 to 10 days, and Receiving that runs 2 to 3 weeks on multi-FC placements. All routine, all survivable.

The playbook: day 3 verify with the carrier directly, day 7 pull the signed proof of delivery, day 15 open a Seller Support case with documents attached, day 30 file the reimbursement claim.

The money: as of 2026 Amazon reimburses lost inbound inventory at your sourcing cost, not your sale price, and only when you can prove ownership and delivery. The claim window is finite, so the evidence file you start on day 3 is what gets you paid on day 30.

The Five Statuses, and How Long Each One Really Takes

Seller Central gives you status labels without durations, which is why every seller eventually types some version of "fba shipment stuck in transit" into Google at 11pm. Here is what each label physically means and the honest timeline behind it, based on watching thousands of shipments cross this pipeline.

StatusWhat is physically happeningNormal durationStops being normal
In TransitThe carrier has your freight. Amazon has nothing yet.SPD: 1-5 business days. LTL: 3-8 business days, plus dock appointment waitNo new carrier scan for 7 straight days
DeliveredCarrier obtained a signed proof of delivery. Freight is in the FC yard or dock, not yet in Amazon's system1-3 days before check-in, 7-10 days in Q414 days with no Checked-In
Checked-InThe FC logged the shipment's arrival at the dockHours to 2 days before the first unit scan5+ days with no move to Receiving
ReceivingUnits are being scanned, counted, and often transferred to other FCs2-14 days, longer on multi-FC placementReceived count frozen for 14 days
ClosedFinal counts posted, discrepancies visibleEnd stateShortage shown with no reconcile option

Two structural notes on that table.

First, the transit ranges differ by shipment type for a mechanical reason. A small parcel shipment rides UPS ground and gets a scan at every sort facility. An LTL shipment moves on a bill of lading through terminals that may scan the pallet twice in total, and then waits for a delivery appointment because trucks cannot simply show up at an Amazon dock. If you are choosing between the two modes, the tracking behavior itself is part of the trade, and I broke that comparison down in SPD vs LTL shipments.

Second, the gap between Delivered and Checked-In is where most panic lives, and most of that panic is misplaced. The signed POD means Amazon has legal possession. The trailer can then sit in the yard for days before a dock team works it. I wrote a full breakdown of what drives that gap in Amazon FBA check-in time in 2026, and the end-to-end view of every tracking surface lives in the inbound shipment tracking guide.

The LTL appointment queue is invisible in Seller Central. Your carrier requests a delivery appointment and the FC assigns one based on dock capacity. In peak weeks that assignment can land 5 to 10 days out, and the whole wait displays as In Transit. Before assuming a shipment is lost, pull the PRO number and ask the carrier for the appointment date. The step-by-step is in how to track an FBA LTL shipment.

When Stuck Is Normal, and When It Is a Problem

Most stuck shipments are not lost. They are queued. The skill is telling the two apart early, because the queued ones resolve themselves and the lost ones reward speed.

Normal, even when it feels wrong:
  1. LTL freight showing In Transit for 2+ weeks between October and December. Appointment backlog, not loss.
  2. Delivered with no Checked-In for up to a week, or 10 days in peak. Yard time.
  3. Receiving open for 2 to 3 weeks while units transfer across multiple FCs. The received count creeps up in bursts, not daily.
  4. SPD boxes from one shipment arriving on different days. Parcel networks split multi-box shipments constantly.
Actual problem signals, act on these:
  1. Zero carrier scans for 7 consecutive days on SPD. The label may never have been inducted, which means the box is sitting somewhere with no custody record.
  2. A signed POD exists and 14 days pass with no Checked-In. Possession happened, the record did not. This is a dock search request, not a waiting game.
  3. Receiving frozen at a partial count for 14+ days. The remaining units are on a lost transfer or a miscounted pallet.
  4. Shipment Closed with a shortage. The clock on your claim window is already running.

The Day by Day Playbook

Count day zero as the later of the carrier's estimated delivery date or the last physical scan. Everything below assumes you are past it.

Day 3: Verify, do not escalate

Three days of silence is noise, not signal. Use it to establish facts.

  1. Pull tracking on the carrier's own site with the tracking or PRO number, not the Seller Central widget. The widget lags and truncates events.
  2. For LTL, ask the carrier for the delivery appointment status. If an appointment is scheduled, your mystery is solved and your shipment is fine.
  3. For multi-box SPD, check every tracking number individually. A shipment shows In Transit until the last box lands.
  4. Screenshot every status with a visible date. You are starting an evidence file, and the file is worth more than any phone call you could make today.

Day 7: Get the paper

A week without movement is when you collect the documents that decide everything later.

  1. Request the signed proof of delivery from the carrier: date, time, receiver signature, and piece count. For partnered carrier shipments the carrier will still produce this against the PRO number.
  2. If SPD shows no scans at all, open a tracer with the parcel carrier now. Tracers take days to run and you want the result in hand before you talk to Amazon.
  3. Compare the piece count on your bill of lading against the piece count on the POD. A 26-pallet BOL signed against 24 pallets received is a short delivery, and you just found your missing units without Amazon's help.
  4. Do not open a Seller Support case yet. A case filed this early gets a templated answer telling you to wait, and you have spent your cleanest escalation on nothing.

Day 15: Open the case, with evidence attached

Two weeks past due is where Amazon's own guidance stops asking for patience. Open a case from the shipment's page in Seller Central and make it easy to say yes to.

  1. Attach the BOL, the signed POD, your supplier invoice, and the box-level packing list in the first message. Cases that open with documents skip a full round of back-and-forth.
  2. Ask for a specific action: a dock search at the named FC, citing the POD signature date and the trailer or PRO number. Vague cases get vague answers.
  3. State the delta in units, not boxes: 480 units of X, 240 units of Y, per the attached packing list. Amazon reconciles at the FNSKU level.
  4. If the shipment shows Delivered but not Checked-In, say exactly that and include the number of days elapsed. It is a known failure pattern and support teams recognize it.

Day 30: File the claim

A month past due, the shipment either surfaces or becomes a reimbursement case. When the shipment closes short, or the reconcile option becomes available, file for the missing units with the same evidence file. If a non-partnered LTL carrier lost the freight before delivery, you also file a freight claim with the carrier under the bill of lading terms. Standard BOL terms give you nine months. Payouts run against declared value, not retail value. The full mechanics, including what to write in the claim itself, are in the lost inbound shipment reimbursement guide.

The Case File: What Evidence Actually Moves a Claim

Every reimbursement I have watched succeed rested on the same short stack of paper. Every one I have watched fail was a seller arguing with a screenshot of Seller Central.

DocumentWhere it comes fromWhat it proves
Bill of lading (BOL)Created at booking, signed by the driver at pickupThe shipment existed and a counted number of pieces left your dock
Proof of delivery (POD)The carrier, after deliveryAmazon took possession: date, time, signature, piece count
Supplier invoice or receiptYour supplierOwnership, and the unit cost that sets your reimbursement value
Box-level packing listYour warehouse or prep centerWhich FNSKUs, in what quantities, were inside each box
Photos at handoffWhoever loaded the truckCondition and count at the moment custody changed

The packing list is the one sellers skip, and it is the one that converts a vague shortage into a specific claim. If your box content data is sloppy, fix that habit before you ever need a claim, and the box content guide covers how to get it right at shipment creation.

Reimbursement: What Amazon Actually Pays

Three things about the money, all as of 2026, all worth confirming against the current policy text in Seller Central because Amazon revises it.

First, the basis. Amazon reimburses lost or damaged inbound inventory at your sourcing cost, the price you paid to manufacture or acquire the product, not your Amazon sale price. Amazon estimates that cost from its own data unless you provide documentation, which is exactly what your supplier invoice is for. If your true cost is higher than Amazon's estimate, the invoice raises your payout.

Second, the cap. Reimbursement is capped per unit, 5,000 dollars as of 2026, which matters only for high-value goods but matters a lot then. Anything near that line deserves declared-value freight coverage on top.

Third, the timing. Amazon rejects claims filed before a shipment becomes eligible for reconciliation. It also rejects claims filed after the window closes. For inbound shipment claims, as of 2026, the window generally opens 15 days after the delivery date and shuts at 60. That pincer is why the day-by-day structure above exists: too early wastes the claim, too late forfeits it, and the eligible window in between is narrower than most sellers assume.

Where a Prep Center Sits in This

Half of the evidence table above is generated before Amazon ever touches your freight, which means your prep partner is either building your case file by default or leaving you exposed by default. At PrepVia every outbound shipment leaves Miami with box-level content data recorded and a signed BOL on file, because we have sat on the seller's side of enough of these cases to know which documents end them. Our turnaround is written down as an actual guarantee rather than a brochure average, 35 hours end to end or the prep is free, and the terms are public on the SLA guarantee page.

None of that prevents Amazon from misplacing a trailer. What it does is turn a misplaced trailer from a two-month argument into a two-week claim.

Frequently Asked Questions

How long can an FBA shipment stay in transit before I should worry?

Small parcel shipments normally deliver in 1 to 5 business days and LTL freight in 3 to 8 business days plus a dock appointment wait that can add another week. The real warning sign is not total elapsed time but scan silence: 7 consecutive days without a new carrier scan means it is time to pull the proof of delivery and open a tracer. During Q4, LTL shipments sitting In Transit for two weeks are usually queued for an appointment, not lost.

What does Delivered but not Checked-in mean at Amazon?

It means the carrier holds a signed proof of delivery, so Amazon has legal possession, but the fulfillment center has not yet logged the shipment into its system. Trailers routinely sit in the yard for several days before a dock team works them, and in peak season that gap can stretch to 10 days. If 14 days pass with no check-in, open a case and request a dock search, citing the POD signature and date. Possession is already established, so the burden at that point is on Amazon.

Can I get reimbursed for a lost inbound FBA shipment?

Yes, when you can prove the units existed, you owned them, and Amazon or its partnered carrier took possession. As of 2026 Amazon reimburses at your sourcing cost rather than your sale price, capped per unit, and only within a finite claim window. The documents that decide the outcome are the bill of lading, the signed proof of delivery, your supplier invoice, and a box-level packing list. Claims filed before the shipment is eligible for reconciliation get rejected, so timing matters as much as evidence.

Why is my FBA shipment stuck in Receiving?

Receiving covers counting your units at the first fulfillment center and often transferring part of the inventory to other FCs before the shipment closes. Multi-destination placements and peak season backlogs can legitimately hold a shipment in Receiving for two to four weeks, with the received count rising in bursts rather than daily. The status is only a problem when the count freezes at a partial number for more than 14 days. At that point treat the unreceived remainder as missing and open a case with your packing list attached.

Stuck shipments start at handoff. Clean handoffs start at the dock.

Talk to PrepVia about your inbound flow →

24-36h prep · Box-level content data on every shipment · No minimums · Amazon SPN Certified · Miami, FL

Related Reading

Bernardo Campelo

Bernardo Campelo

Forbes Business Council E-Commerce Leader, PrepVia Founder

Founder of PrepVia and Member Leader at Forbes Business Council. Building automation-first logistics infrastructure for e-commerce sellers.

Tags

fba-trackinginbound-shipmentsamazon-fbashipment-troubleshootingfba-reimbursementprep-center3plfba-prep-services

Common Questions