Why One Quantity-per-SKU Sheet Beats 40 Packing Slips
Batch fulfillment has a hidden tax, and it gets worse as you grow. The more orders you ship, the more times you walk to the same shelf, because per-order paperwork makes you pick the same SKU again and again. A quantity-per-SKU pick list removes that tax: one line, one count, one trip per SKU, no matter how many orders that SKU appears in. This is the core idea behind Picksort, and it's the single biggest lever for picking speed in a small warehouse.
Let's make the problem concrete, then show what merging actually changes.
The per-order model punishes growth
When you print packing slips, you get one document per order. That's correct for the customer, who wants to see their items and address on their slip. But it's the wrong shape for the picker.
Here's why. A packing slip organizes items by order. So the same SKU is scattered across dozens of separate documents. To fulfill the batch, you either:
- Walk the shelves order by order, revisiting the same bin every time that SKU shows up, or
- Try to hold the running totals in your head, which invites miscounts and short-picks.
The math gets ugly fast. Double your order volume and you don't just double the slips; you roughly double the number of redundant trips to your popular shelves. The picking effort scales with orders times repeated SKUs, not with the actual number of items. That's the growth penalty.
A before/after example: 66 orders
Imagine a Friday batch of 66 unfulfilled orders. Your bestselling scented candle sells well, so it appears in 9 different orders — a couple of orders want one, a few want two, one wants five. Across all 66 orders, the candle's total demand adds up to 23 units.
The packing-slip way
You print 66 packing slips. As you work through them, you hit that candle on 9 separate slips. That's up to 9 trips to the candle shelf (or 9 mental additions), for a single SKU. Now multiply that pattern across every popular product in the batch. A 66-order day becomes hundreds of little redundant walks and running-total calculations. It works, but it's slow and error-prone.
The quantity-per-SKU way
You open a merged pick sheet. The candle appears once, with a big number next to it: 23. You walk to the shelf a single time, count out 23, tick the box, and move on. Every other SKU in the batch works the same way — one line, one count, one trip. You pull the entire 66-order batch in a fraction of the walking. Packing happens afterward, when everything is staged at the bench.
Same orders. Same items. Radically less movement. That's the whole thesis: merge first, pick once.
What a merged pick sheet gives you
A good quantity-per-SKU sheet isn't just a deduplicated list. The details make it usable on a real floor. Here's what Picksort produces from your open, unfulfilled orders:
- One line per SKU with the total quantity across all orders, plus a checkoff box. Big, glanceable numbers you can read at arm's length.
- Group by vendor, bin location, or SKU. Switch the grouping and quantities re-tally instantly. Group by bin location and the sheet becomes a walking route, so you move through the warehouse in order instead of crisscrossing it.
- Zero setup. No imports, no field mapping, no templates to build. Install and open, and your live orders are already merged.
- Read-only by design. Picksort only reads orders and products. It can't edit, fulfill, delete, or create anything, so it's safe to run on a live store.
- Pick on your phone, print for packing. The sheet is single-column on mobile so you can pick straight from your phone, then print it with checkoff boxes when it's time to pack.
Bin location comes from an optional product metafield; vendor comes from the product's vendor field. Neither is required to get value — even a plain SKU-grouped sheet immediately collapses your redundant trips.
Where a merged sheet fits (and where it doesn't)
Be honest about scope. A quantity-per-SKU sheet is the fastest way to pick a batch. It is not a full warehouse system.
- Use a merged sheet if you do in-house batch fulfillment and repeatedly pick the same SKUs across many orders. This is most small-to-mid Shopify merchants.
- You'll still fulfill in Shopify. The sheet gets items off the shelves; you mark orders fulfilled in your admin as usual.
- If you need barcode scanning, kits, or shipping labels, Picksort doesn't do those — it deliberately stays simple. Tools like iPacky add scanning and bins; if that's your requirement, use one of them. See our iPacky alternative comparison for an even-handed look.
The trade is intentional. Picksort's whole value is doing one thing cleanly and cheaply: turning your open orders into a merged pick sheet with no configuration.
How this connects to your printing workflow
Most merchants arrive here from a printing question. If you've been bulk-printing slips, the natural next step is to separate picking from packing paperwork:
- Pick from the merged quantity-per-SKU sheet (grouped by bin) in one pass.
- Print packing slips natively in Shopify for the customer-facing documents.
- Pack and fulfill each order in your admin.
For the printing mechanics, see how to print a pick list in Shopify. And if you want the strategic view on batching, our piece on batch picking vs single-order picking explains when each approach wins.
Frequently Asked Questions
What is a quantity-per-SKU pick list?
It's a pick sheet that merges every open order and lists each SKU once, with the total quantity to pull across all orders. Instead of one document per order, you get one line per product. It means one count and one trip per SKU, which is why it's dramatically faster for batch picking than per-order packing slips.
Why is one merged sheet faster than 40 packing slips?
Packing slips are organized by order, so a popular SKU appears on many separate slips and you revisit its shelf repeatedly. A merged sheet lists that SKU once with a combined total, so you visit the shelf a single time. As order volume grows, the merged sheet saves more and more redundant trips.
Do I need bin locations to use Picksort?
No. Bin location is optional and comes from a product metafield. Without it, you can still group by SKU or vendor and get a fully merged quantity-per-SKU sheet. Adding bin locations lets you group the sheet into a walking route, which speeds picking further.
Is Picksort safe to run on my live store?
Yes. Picksort is read-only by design — it only reads orders and products to build the sheet and cannot edit, fulfill, delete, or create anything. It's one plan at $9/month with a 30-day free trial, cancel anytime.
If your popular SKUs show up in half your orders, you're paying the per-order tax every single day. Install Picksort and start a free 30-day trial to turn your open orders into one merged quantity-per-SKU sheet — one line, one count, one trip per SKU. Zero setup, read-only, works on your phone. Prefer to see it first? Watch the tutorial.