The batch fulfillment day, step by step

Choosing a cadence: when batching beats shipping daily

Shipping one order at a time feels responsive, but it prices every parcel at its worst. Each order interrupts something else, restarts the same setup — find the scale, find the right box, open the tool, re-check the address — and ends before any of that setup pays for itself. Batching moves all of those fixed costs to the front of a single run, and the longer the run, the less each parcel carries. The trade-off is dispatch delay, which is why the cadence is not a preference but a calculation: take the shortest handling time you have promised on any channel, and batch as rarely as that promise allows. A shop that promises three business days everywhere can ship twice a week. A shop that promises next-day dispatch on one channel batches every morning, because the strictest promise sets the clock for the whole operation.

The signal that you are ready for batch days is not a volume milestone, it is a feeling: shipping has become the thing that fragments the rest of your work. If you touch the tape gun more than a couple of times a day, the interruptions are already costing more than the parcels. And a deliberate cadence has a second, quieter benefit — buyers get consistent dispatch behaviour instead of a lottery, which shows up in fewer where-is-my-order messages than daily-but-erratic shipping produces.

Consolidating channels into one list: synced stores and exported files

A batch day starts with a single list of every open order, and the list is only trustworthy if nothing has to be remembered onto it. Orders arrive three ways here. Synced storefronts are the easy case: Shopify, Etsy, WooCommerce, and TikTok Shop connect directly, and their open orders land in the To Ship queue on their own. Channels without a connector arrive as files — a marketplace export, a spreadsheet from a wholesale buyer — and the CSV import mechanic turns a file into validated, quotable rows with a saved column mapping. The third stream is the one every seller forgets to count: the DM sale, the market-stall follow-up, the buyer who texted an address. Those get pasted or screenshotted in, and Billy drafts them into the same queue as everything else.

The point of consolidation is not tidiness, it is that the batch is only a batch if it is complete. An order that lives outside the list does not get validated with the others, does not get quoted with the others, and surfaces at the worst possible time — after the boxes are sealed and the drop-off is done. If you run more than two or three storefronts, the channel-by-channel intake picture is its own subject, covered on the multiple-stores page; this page assumes the orders have arrived and cares about what order you do things in next.

The sequence: validate, buy, print in pick order, pack against the stack

The run sheet below is the whole argument of this page. Each step exists to catch a specific class of error at the point where it is still cheap, and the ordering is what does the work — the same five activities in a different order catch the same errors after they have already cost money.

Two orderings matter more than the rest. Validation goes before buying because an address error found before money moves costs a message to the buyer, while the same error found after purchase costs a void and a rebuy, and found after dispatch costs a returned parcel. And printing goes in pick order — the order you will physically walk your shelves or bins — because it converts the label stack into the pick list. Pack against the stack and every parcel is a self-checking pair: the label on top must match the item you just pulled, so a swap is caught by the next pair being wrong, not by two buyers a week later opening each other's orders. When the run ends, everything goes to the carrier drop-off in one trip; the day is planned around that trip, not around waiting for anyone to arrive.

Handling exceptions mid-batch without derailing the day

Every batch throws exceptions: an address the validator flags, an item that is not on the shelf where it should be, a buyer message that arrives mid-run asking to combine two orders. The rule that protects the day is simple — the batch does not stop. Exceptions get parked in a physical and digital holding lane, the run continues, and the parked items are worked as their own small batch at the end. Stopping a fifty-parcel run to chase one problem trades fifty parcels of momentum for one parcel of resolution, and the interruption is where mispacks breed: the stack and the pile lose their pairing the moment you start shuffling either one.

Caught mistakes are cheaper here than they feel. A label bought for a parcel that then changes — heavier than expected once packed, or merged with another order — can usually be voided with the credit going back to the wallet, and the void page covers how each carrier decides that. What matters operationally is the sequencing again: a mistake found at the packing bench, before sealing and before drop-off, is a two-minute fix from the same prepaid balance. The batch day exists to make sure that is where mistakes get found.