Back to all posts
FBA Replenishment & Inbound Compliance

The FBA Delivery Window from China: How to Set Your Send to Amazon Window, Book Delivery, and Decide When a Late Supplier Carton Should Trigger a Split (2026)

By Alice Zhou2026-09-129 min read
WooliiPorterThe FBA Delivery Window from China: How to Set Your Send to Amazon Window, Book Delivery, and Decide When a Late Supplier Carton Should Trigger a Split (2026)

If you replenish FBA from China using a non-Amazon carrier — ocean or air freight to the destination port, then LTL or small parcel into the fulfillment center — Send to Amazon will ask you for a delivery window: the date range in which you expect the shipment to arrive at the fulfillment center. Getting it wrong usually does not get the shipment rejected at the gate. It shows up as an alert in the Seller Central shipment workflow and Shipping Queue, and the fulfillment center plans receiving and dock appointments around the window you declared. The real fix is not a better guess. It is reverse-planning the window from data, and deciding in advance what happens when one supplier's carton is clearly going to land late: wait, extend the window, or split the shipment.

What the Send to Amazon delivery window actually is, and when you have to fill it in

  • What it is: your estimated arrival date range for the shipment at the fulfillment center, provided when the shipment is created in Send to Amazon.
  • When you must provide it: when you ship with a carrier that is not an Amazon partnered carrier — for example commercial air or ocean plus LTL or small parcel arranged by you or your freight forwarder.
  • When you do not: with an Amazon partnered carrier or Amazon Global Logistics, the estimated arrival is transmitted by the carrier and is not something you enter manually.
  • What happens outside the window: the shipment is flagged in the Seller Central shipment workflow and Shipping Queue, and receiving-side planning is built around the window you declared.

Window lengths, which marketplaces apply them, and how the rules change are all site-specific and evolve over time. Treat the Seller Central help pages and your marketplace's announcements as the source of truth — not a day count someone posted in a forum last quarter.

Why China-origin shipments miss windows more often — and why arriving early is not a free pass

The chain from factory to fulfillment center carries far more variables than a domestic transfer: factory lead times and holiday shutdowns, port cut-offs and rolled bookings, vessel or flight changes, port congestion, customs inspection, and pickup or trucking capacity. A slip in any one link propagates down the chain and lands on the date range you entered. The more optimistic the window, the higher the odds it slips.

The second common misconception is that early is always better than late. In practice, arriving before the window opens is also an out-of-window arrival. It triggers the same category of shipment alert and disrupts dock appointment and receiving capacity planning just as a late arrival does. Arriving early shifts the risk rather than removing it. The better mental model: the delivery window is a commitment you should be able to justify afterwards with records, not a target you push forward to look good.

The core scenario: waiting for one supplier's last carton pushes the whole shipment's window

The classic multi-supplier case: four suppliers, three cartons already at your China warehouse, the fourth still at the factory. As long as everything ships as one consignment, the entire shipment's window is determined by the last component to reach the warehouse. One carton can delay the whole lot.

A practical decision order:

  1. Identify the latest-to-warehouse component. Name the supplier, the carton, and the expected arrival at your consolidation warehouse — not a vague “sometime this week.”
  2. Compare it against the date the main lot must leave. Reverse-plan the latest departure date from a window you can defend, then put that date next to the tail carton's expected arrival.
  3. If the tail will not make it, pick one of three paths: split — ship the ready portion on the original window and create a separate shipment for the tail; extend — hold the whole shipment if the delay is short and holding cost is acceptable; upgrade — move only the tail onto a faster first leg.

A split is not free. It creates an additional shipment, an additional set of carton labels, another delivery appointment, and may affect how inbound placement and related fees are handled. But a shipment that repeatedly arrives late has costs too. The question is not “split or not” in the abstract — it is which option is cheaper for this specific tail. A usable rule of thumb: if the tail cannot be confirmed before the point where the main lot must depart, it is usually time to split rather than keep waiting.

Reverse-planning checklist: the fields that make a window defensible

Do not fill in dates by feel. Record these fields and the window stops being a guess.

StageFields to recordSource
Factory handoverHandover date, carton count, carton dimensions and per-carton weightSupplier + China warehouse receiving record
Cut-offPort or carrier cut-off time, vessel or flight referenceFreight forwarder
ETD / ETA portDeparture date, estimated arrival at destination portCarrier
Customs releaseRelease date, whether inspection was triggeredCustoms broker
Pickup and truckingPickup date, trucking appointment timeForwarder / drayage provider
Delivery windowWindow open and close datesSeller Central shipment
FC appointmentAppointment ID and scheduled timeCarrier / fulfillment center
Receiving check-inSigned-in and put-away progressSeller Central shipment

Base your timing on your own historical data plus carrier commitments — never on fixed day counts copied from an article. Keep a slip table by lane and by season, and update it after every shipment with the gap between estimate and actual. After a few cycles, the numbers you enter become defensible by default.

The window is one layer of inbound compliance — fixing it does not fix everything

A correct delivery window only covers the time dimension. These need to be planned alongside it, or you will get the window right and stall somewhere else:

  • FNSKU labeling and prep: missing, wrong, or non-compliant packaging causes holds at receiving regardless of when the truck arrives.
  • Inbound placement and split decisions: shipping as one consolidated lot versus splitting affects placement routing and related fees, and should be weighed together with a carton-level split decision.
  • Carton and pallet specs, carton labels: non-compliant cartons get stopped at receiving too.
  • Eligibility thresholds for programs such as AWD: dimension and weight thresholds should be checked against Seller Central documentation, not assumed from experience.

In short: the delivery window is time-dimension compliance; the items above are physical-dimension compliance. Plan both on the same calendar so your replenishment does not die at the least valuable step.

Where WooliiPorter fits: you buy, we fulfill

The boundary first: you purchase from your own suppliers and pay them directly. Title to the goods stays with you. We do not sell products, we never handle payment for goods, and we are not a purchasing or dropship agent. What we do is receive parcels at our China warehouse with inbound photo evidence, offer QC on request, consolidate and repack multiple suppliers' cartons, arrange first-leg and international transport with tracking, and route by order line (hold-and-fulfill versus supplier direct ship). Applied to this article's scenario, that means turning “the latest-to-warehouse component” and “the day the main lot must leave” into records you can check, instead of inferences from a chat thread.

To see the full flow, start with China inventory fulfillment. Consolidation and split mechanics are covered under consolidation and repacking, and the overall working model is on how it works. If you want your current replenishment cadence and split rules reviewed, submit a workflow review request.

On channel integrations, current status is whatever is published as verified on /integrations — we state only what is verified, not what is planned. Teams that want inbound, consolidation, and outbound data flowing into their own systems or AI workflows can start at the developer page for the Merchant API and MCP.

If you are ready to tighten your replenishment process end to end, create an account and choose Merchant at /auth/signup. For the carton data referenced above, the volumetric weight calculator and the China warehouse address template are useful starting points.