Amazon FBA Shipment Status: Delivered vs. Checked In vs. Receiving
Blog 2026-10-30
Your carrier says “delivered,” but Seller Central has not advanced—and your next promotion depends on that stock. An Amazon FBA shipment status records a processing stage, not confirmation that every unit is available. Delivered can precede check-in; Checked In precedes receiving; Receiving can continue while some units are already available for sale. A proof of delivery (POD) alone does not verify the contents of every carton. Start by matching the delivery record, Amazon shipment events, and SKU quantities. This guide shows you how to separate a delivery problem from a receiving or inventory issue, assemble evidence, and contact the right party.
Planning your next replenishment while this shipment processes? Share the cargo-ready date, destination FC code, and carton or pallet count for a quote with a clearly defined delivery scope.
Start Here: Three Checks Before You Chase an Update
Before acting on an Amazon FBA shipment status, compare three records and save the review timestamp.
| Check | What to compare | What it helps you decide |
|---|---|---|
| Delivery evidence | POD or tracking against the shipment ID, destination, carton/pallet count, and exceptions | Whether the transportation handoff is supported |
| Amazon shipment events | Latest event, its timestamp, and any displayed receiving or eligibility message | Which Amazon processing stage is recorded |
| SKU quantities | Expected units, received units, and relevant inventory availability records | Whether the issue is unreceived units, availability after receipt, or both |
Verify delivery promptly if the destination, carton count, tracking, or refusal record conflicts. Resolve transport inconsistencies before relying on the status screen.
Amazon FBA Shipment Status: What Each Stage Means
Read your Amazon FBA shipment status separately from the carrier’s tracking status. Their timestamps and definitions may differ.
| Record or status | What it indicates | What it does not prove |
|---|---|---|
| Carrier POD | A reported delivery event within the document’s stated scope | Amazon counted every unit inside the delivered cartons |
| Delivered in Seller Central | Carrier information indicates readiness for delivery or arrival in the facility yard | Check-in and unloading are complete |
| Checked In | Amazon’s trailer-delivery explanation describes movement to the dock, ready for unloading | Unit-level receiving is complete |
| Receiving | Amazon has started scanning shipment ID labels | Every planned unit was received simultaneously |
| Closed | The shipment has reached a later administrative stage | Every expected unit was found or reimbursement is owed |
Received units may become available for sale while the shipment remains Receiving. Transfers can affect immediate shipping availability, so check SKU records before allocating launch stock.
Why the Status May Stop Moving
Delivery and dock processing are separate events
Ask the carrier whether the truck completed delivery, reached the yard, was refused, or was rescheduled. Obtain the actual event record, not just the appointment.
Seasonal receiving volume and information synchronization can affect updates. Use records to establish your shipment’s last confirmed event.
Preparation or identification problems can complicate receiving
Packaging or identification problems can delay receiving. Compare dispatched labels, carton contents, and the final packing list with the submitted plan. Check readability and shipment-ID consistency.
Preserve original documents and record packing changes with dates; do not alter evidence to hide inconsistencies.
Partial receiving and inventory availability need different checks
An unchanged Amazon FBA shipment status does not establish a loss. Separate unreceived quantities from received units with availability issues. If all units were received, ask Amazon about the inventory or listing record.
Questions to Resolve With Yunxi During an FBA Shipment Review
| Customer question | Yunxi’s suggested review approach | Decision to make |
|---|---|---|
| “My first shipment is still processing. Should I send the next one?” | Compare available stock, demand, inbound quantities, and the next delivery plan | Assess replenishment separately from the unresolved shipment |
| “My invoice covers 2,000 units, but this shipment contains only 30. How do I explain that?” | Link the purchase record to the actual shipment using genuine packing and dispatch records | Distinguish ownership evidence from shipment allocation |
| “Support keeps asking for information. What should I send next?” | Organize the case history and identify the specific missing or unacceptable detail | Make a precise request rather than resending an unexplained file bundle |
FBA Shipment Review Example: 100 Cartons Delivered, 700 Units Available
Example scenario: one shipment, no other stock, and no sales, returns, or adjustments between comparisons. All quantities refer to the same review point; labels are simplified.
The packing record lists 60 cartons of SKU A and 40 of SKU B, with 10 units per carton. The POD records 100 cartons delivered to the matching destination.
| Reconciliation item | SKU A | SKU B | Total units |
|---|---|---|---|
| Planned units | 600 | 400 | 1,000 |
| Units recorded as received | 600 | 250 | 850 |
| Units currently shown as available in this example | 500 | 200 | 700 |
| Planned minus received | 0 | 150 | 150 |
The Amazon FBA shipment status is only one part of this comparison. Three conclusions follow:
- Transportation: The POD supports a recorded delivery of 100 cartons. It does not independently verify their contents.
- Receiving: 1,000 planned − 850 received = 150 units not yet reflected as received. This is a pending difference to review, not an automatic loss determination.
- Availability: 850 received − 700 available = a separate 150-unit difference requiring an inventory explanation. Do not assume its cause from the arithmetic.
The 700 available units are part of the 850 received, not additional stock. Reconcile other shipments, sales, reservations, returns, and adjustments before comparing real account balances.
What should the seller do next?
Match the POD to the packing record. Save SKU B’s 150-unit receiving difference and check investigation eligibility. Separately review the other 150 units’ inventory status. Allocate promotional stock using confirmed availability.
If the destination or shipment reference differs, resolve that mismatch first. Unrelated delivery evidence cannot confirm this shipment.
Build an Evidence File That Answers the Actual Question
For an Amazon FBA shipment status issue, group evidence by what it proves. The current Amazon workflow determines submission requirements.
| Evidence | What it helps establish | What to verify |
|---|---|---|
| Shipment ID and FC code | Intended shipment and destination | Match plan, delivery records, and support case |
| Tracking IDs, BOL or PRO | Transportation references | Map packages, cartons, or pallets to this shipment |
| Appointment record | Planned delivery arrangement | Separate booking from completed delivery |
| POD and exception notes | Recorded delivery event | Check destination, date, count, and receipt details |
| Labels and final packing record | How the shipment was identified and packed | Retain legible pre-dispatch copies |
| Inventory ownership documents | Purchase or manufacture of the units | Use documents permitted by the current Amazon workflow |
| Quantity reconciliation and account messages | Exact discrepancy and current eligibility | Record SKU counts, capture time, and case history |
BOL means bill of lading; PRO is the carrier’s shipment reference. For LTL/FTL, Amazon’s public guidance describes box count, pickup weight, and receipt confirmation. Obtain complete records.
When the purchase invoice covers more units than this shipment
For a 2,000-unit purchase and 30-unit shipment, keep the original invoice and explain allocation separately. Match the product and purchase record to genuine packing and dispatch records. Distinguish purchased, shipped, and investigated quantities; the invoice total alone does not identify this shipment’s contents.
The allocation explanation supplements, rather than replaces, required ownership evidence. Do not backdate records or claim manufacturer status when it is untrue.
Yunxi’s Amazon FBA shipping service covers transportation coordination, destination preparation, and POD-supported delivery.
Confirm the records included in your booking.
For a delivery-record review, send the Shipment ID, destination FC code, tracking number or BOL/PRO, POD, carton or pallet count, and latest shipment-event screenshot. Identify the mismatch or missing event. Yunxi can compare handover, dispatch, appointment, and final-delivery records within the agreed scope and identify carrier records to request. For shipments managed by another provider, confirm what can be reviewed using your documents. Amazon retains control of receiving and investigation decisions.
Contact the Party That Controls the Missing Step
Use this routing table to turn your Amazon FBA shipment status review into a specific request.
| What you found | Contact | Ask for |
|---|---|---|
| Wrong destination, conflicting counts, refusal, or no supported delivery | Carrier or managing forwarder | Cargo location, completed events, exceptions, and next transport action |
| Matching delivery evidence, but no later check-in event | Carrier for document verification; seller monitors Amazon | Confirmed delivery records and the current shipment instructions |
| Planned and received units differ | Seller through Amazon’s shipment workflow | Discrepancy research when eligible |
| Received units or the offer remain unavailable | Amazon Seller Support | An explanation of the affected SKU, inventory record, or account message |
Yunxi’s last-mile delivery page explains appointment coordination, delivery milestones, and POD archiving. Use these records to identify the unresolved handoff.
Prepare now; submit research when the shipment is eligible
Amazon’s public reconciliation explanation identifies Closed status and an estimated eligibility date as relevant conditions. Check the actions actually available for your shipment. Do not calculate eligibility using a universal number of days after POD.
Save any updated eligibility message, prepare evidence while processing continues, and monitor applicable submission deadlines separately. When eligible, follow the displayed research steps and retain the case ID. Eligibility does not establish that units are lost or reimbursement is due.
A concise Seller Support message
Adapt this message from the example using verified facts and the real shipment ID. Submit through the support or research process available in your account.
If support requests evidence already supplied, identify its filename and page, then ask what remains missing or unacceptable. Record the case ID, response date, requested action, and next review date. Keep claims consistent with documented quantities.
Prevent the Next Planning Error: Separate Delivery From Availability
For imports from China, maintain four separate planning stages:
| Stage | Planning record |
|---|---|
| Origin readiness and international departure | Cargo-ready date, actual departure, and route |
| U.S. release and destination handling | Import release, cargo availability, and handling completion |
| Final delivery | Appointment, completed delivery, and POD |
| Amazon processing and inventory | Shipment events, received quantities, and actual availability |
Use the China to US sailing schedule for the ocean segment, not as a sellable-inventory calendar. Use your own comparable records to estimate buffers; revisit them when the route, FC, season, or shipping method changes.
The FBA Q4 inventory planning guide covers broader replenishment timing. If reserve stock is needed, compare direct to FBA vs 3PL warehouse with storage, release processing, and every replenishment delivery included. A U.S. reserve still needs delivery and Amazon receiving.
Yunxi’s Amazon Freight Option: Coordinated West Coast Receiving
For eligible FBA plans, Yunxi’s Amazon Freight option coordinates delivery through approved West Coast receiving facilities, including confirmed plans serving Central or Eastern U.S. markets. Amazon handles subsequent internal transfers. The estimated transportation window is 25‒30 days after actual vessel departure to the designated West Coast receiving location.
Yunxi reviews the full plan, current fee status, cargo, and valid receiving instructions before confirmation. Do not independently redirect an assigned shipment. Review the West Coast FBA delivery program for shipment-specific conditions.
Yunxi’s published POC3 record lists Ningbo departure on August 7, 2026, arrival/check-in on August 27, and appointment completion on August 28. These establish recorded transport and appointment milestones, not unit-level sellable status.
FAQ
Why is my Amazon FBA shipment delivered but not checked in?
Delivered can precede dock check-in. First confirm whether the label appears in carrier tracking or Seller Central, then match the destination, shipment references, POD, and latest Amazon event. If those records conflict, verify delivery with the carrier. A matching POD still does not prove Amazon has received every unit.
What is the difference between FBA Checked In and Receiving?
Checked In refers to the dock stage before receiving in Amazon’s trailer-delivery explanation. Receiving means label scanning has begun. Some units may become available while the shipment remains Receiving; neither label confirms that all expected units have completed processing.
How long after FBA delivery does inventory become available for sale?
There is no single guaranteed interval. Amazon can make received units available for sale while processing continues, and transfers can affect immediate shipping availability. Check SKU records and current shipment messages. A carrier’s delivery estimate—including a departure-to-delivery service window—is not an inventory-availability promise.
What documents do I need for an FBA shipment investigation?
Check the current workflow for ownership and delivery evidence requirements. Prepare the supplier invoice or other permitted ownership document, matching transport records, and SKU-level quantity reconciliation. For LTL/FTL, verify the required BOL or delivery details. A signed POD alone does not establish the contents of every carton.
When can I request an FBA shipment investigation?
Check your Amazon FBA shipment status, displayed eligibility information, and available research actions. Public guidance identifies Closed status as relevant, but the actual shipment workflow determines what you can submit. Save changes to eligibility messages and monitor applicable deadlines; do not use another seller’s waiting period as your own.
Should I send more inventory while my FBA shipment is still Receiving?
Compare confirmed available stock, expected demand, inbound quantities, and the next shipment’s full path to availability. Check current plan and account constraints. More stock does not resolve the earlier discrepancy or guarantee faster receiving; waiting can also increase stockout exposure. Make the replenishment decision separately from the investigation.
About the Author
Jaina Lin is Operations Director at Yunxi Logistics, a China-to-U.S. freight forwarder supporting FBA delivery. This guide explains transportation records and receiving milestones to help sellers identify the next operational step.
Make the Next Step Match the Evidence
Reviewing an Amazon FBA shipment status should lead to a decision: verify delivery, prepare a receiving inquiry, or investigate inventory availability. Keep those tasks separate, and commit promotional stock only against the availability you can confirm.
For your next shipment, Yunxi Logistics can discuss transportation and documentation. Share product details, pickup location, dimensions, weight, cargo-ready date, destination FC, and desired inventory date. Request clear delivery scope, preparation tasks, and document responsibilities.
Official and Primary Sources
- Amazon Seller Forums — FBA Receiving Times, posted by Dominic_Amazon — Public Amazon staff explanation of delivery, check-in, receiving, partial availability, and transfers; historical timing examples are not used as current guarantees here.
- Amazon — How to track FBA shipments — Official explanation of shipment events, receiving, and discrepancy review. Published January 7, 2025; use current account instructions for the shipment.
- Amazon Seller Forums — What to do if you have a lost or delayed FBA Shipment, posted by TaylorR_Amazon — Supports ownership and delivery evidence preparation, including LTL/FTL BOL details; use the current account workflow for submission requirements.
- Amazon Seller Forums — Reconciling Shipping Discrepancies, posted by NR_Amazon — Describes shipment closure, estimated eligibility, discrepancy research, and supporting records.
