Waves, Zones and One Carton: How a Pick List for Order Fulfillment Gets Built

A queue of orders looks flat on a dashboard and is not flat on a floor. Order fulfillment is judged by what a picker can physically reach in a shift, and the order in which work is released decides that long before any parcel is scanned. Most sellers never see the sequencing rule behind their cut-off, so the promise they make to a customer is inherited from a print order nobody chose.

One ticket at a time is a decision, not a default

Single-ticket picking sends a person to the racks once per order. It is simple to audit — one order, one carton, one label — and it is the honest shape for a one-piece dropshipping order, because the carton already has a unique destination and a unique packing instruction. It is also the slowest shape when a hundred orders draw from the same few bins. The small-parcel dropshipping page describes the order profile we mostly run, and that profile is why our default is one ticket per carton rather than a consolidated tote of mixed orders.

Three cuts of the same queue

A wave releases a bounded batch of orders to a zone at a fixed time, so travel is amortized across the batch; the cost is that an order joining after the wave closes waits for the next one. Zone picking splits a single large order across aisles and merges it downstream, which works when the line count is high and hurts when it is not. Pick-and-pass moves an order between stations so packing, labeling and the customs paperwork each happen where they are cheapest to do well. The sequencing choice is visible in one place only: how many orders leave on the day their cut-off passes.

What repetition does to a wave

Waves reward a queue that draws on the same bins. They punish a queue that draws on a long tail, because the picker walks further per unit picked and the merge station becomes where cartons wait. A seller mixing a fast core range with a slow catalog should expect the core range to run in waves and the tail to run one-at-a-time, and should expect that split to be stated before a promise is made to a customer. Velocity banding is a counting exercise, and the inventory placement page is where we write out how it is done against our own bin map.

The clock that actually governs the queue

Platform delivery clocks and warehouse cut-offs are two different timers, and a queue built against the wrong one produces late cartons that look on time in a dashboard. Where a line runs a published cut-off we say so plainly — 16:00 China time on the lines that carry it — and where a marketplace scans its own deadline into your account, that deadline is what we sequence against, not our preference. The marketplace scan-rule page sets out one such clock in detail.

What we will not do to keep a wave tidy

We do not split one order across two days to make a batch round, and we do not release a carton whose contents have not physically been picked. If a queue is too thin to wave profitably on a given evening, the answer we send is that the work runs one-at-a-time that night, which is slower and which we will have told you about in advance rather than discovered in a late tracking scan. Choosing between throughput and per-order fidelity is your decision, not ours to make quietly.

Questions this desk gets asked

Does wave picking delay a single-unit dropshipping order?

Only if the order misses a wave that has already closed. A one-piece order can be picked outside the wave; what changes is that it waits for a free hand rather than a free trip to the racks, which is a staffing question, not a rule.

How do you decide which orders run in a wave and which run alone?

By how many orders in the queue draw on the same bins in the same window. A queue that converges on a handful of fast items waves well; a long tail of single-line orders is cheaper to run one at a time, and we would rather say that than measure it later.

Can you rebuild the sequence for one customer's deadline only?

We can hold a cut for you and route your orders against it, but we cannot give one seller's deadline the whole floor. If your clock needs priority every evening, that is a capacity conversation with a forecast behind it, not a checkbox on an order.

By Tony Zhang, FulfillDock by SBT. Written between the evening wave and the handover bench, and checked against the pick exceptions logged on the same queue this week. Published 24 October 2026, last checked 24 October 2026