How to create WMS pick lists for ecommerce orders
A WMS pick list is more than a printable sheet. For online sellers, it is the daily instruction set that decides which Shopify, WooCommerce, bol.com, Amazon, Kaufland or B2B orders are safe to release, which shelves a picker visits, which SKU is scanned, and which parcel reaches the carrier before cutoff. ChannelDock’s Pick List settings let you turn that control into a repeatable workflow.
orders by risk and cutoff
SKUs by bin and aisle
scan before pack
The best pick list tells the picker where to walk, what to scan, and when to stop.
Most ranking pick-list articles explain fields on a document. The operational gap is control: when to release work, how to group it, and how to prevent the wrong item from reaching the packing bench.
Before you create a pick list: decide what the list must control
A weak pick list is just a shopping list for the warehouse. A strong WMS pick list is a release rule, a route, an accuracy check and a feedback loop for inventory.
Only release orders that are paid, in stock, not blocked by fraud checks, and still realistic for the promised carrier cutoff.
Every pick line needs a default bin, shelf or zone. If a SKU has reserve and pick-face stock, the list must show which location the picker should use first.
Decide whether the picker scans the order, location, SKU, quantity, tote and parcel. More scan points are useful only when they prevent a real error.
Step-by-step: create a WMS pick list that works on a busy ecommerce floor
Use this procedure when moving from Shopify exports, WooCommerce plugins, printed packing slips or staff memory to a controlled ChannelDock WMS process.
Profile your orders before you group them
Pull the last two weeks of orders and separate them by line count, SKU overlap, parcel size, marketplace SLA and carrier. Single-line orders, multi-line orders, fragile products and B2B replenishment orders should not always share one picking method.
Choose the pick-list type for the shift
Use single-order picking when accuracy and training matter more than speed. Use batch picking when many orders share SKUs. Use wave picking when carrier cutoffs or marketplace SLAs drive the day. Use zone picking only when the warehouse is big enough that one person should not walk every aisle.
Set release rules in ChannelDock
In Pick List settings, define which orders can enter the list: paid status, warehouse, channel, shipping method, order tag, deadline, stock availability and manual holds. Keep blocked orders out of the walk before they waste time.
Sort the list by location, not by order number
A picker should move through the warehouse in a logical path: aisle, rack, shelf, bin. If you use walking routes, the pick list should follow that route and show quantities at each stop.
Add the minimum fields pickers actually need
Show SKU, barcode or EAN, product image, variant, bin location, quantity, order or tote reference and warning notes. Hide fields that belong at packing, such as customer message details, unless they change the pick decision.
Connect barcode checks to the list
When the picker reaches a location, scan the bin or SKU with Barcode Scanning. The scan should confirm the exact item and quantity before the product enters the tote or cart.
Send picked items into a controlled pack flow
The pick list ends only when the correct tote, order or parcel is ready for Pick & Pack. At the bench, scan the order again, verify all lines, print the label and keep exceptions visible.
Measure the list after every shift
Track picked lines per hour, walked metres where possible, mis-picks, stock exceptions, label reprints, orders missed by cutoff and orders removed from the list. Use those numbers to adjust batch size and release rules.
The decision flow behind a good pick list
Competitor guides from Picqer, Shopify apps, ShipHero, Logiwa and general WMS publishers usually stop at “create a list and start picking.” That is useful, but incomplete. The better question is: should this order be on this list, for this picker, before this cutoff?
A pick list should reduce choices on the warehouse floor, not move planning decisions from the system to the picker.
Common pick-list mistakes online sellers make
- Using one printed list for every channel, even though bol.com, Amazon, Shopify, wholesale and manual orders have different deadlines and exception rules.
- Leaving substitute SKUs, bundles and split shipments undefined, so pickers invent workarounds during the walk.
- Putting product names first when the warehouse thinks in locations, barcodes and images.
- Making batch sizes too large for the packing bench, which moves congestion from the aisle to the table.
- Failing to update stock immediately after a confirmed pick, creating oversell risk on connected marketplaces.
Manual pick list vs. ChannelDock WMS pick list
A spreadsheet can be acceptable at ten orders per day. At fifty orders, the hidden cost is not the paper; it is the decisions the paper cannot enforce.
Manual or webshop-only list
- Orders are printed even when stock, payment or support status is unclear.
- Routes follow export order, not warehouse layout.
- Wrong picks are discovered by the packer or customer.
- Stock updates lag behind the actual pick.
ChannelDock WMS list
- Only eligible orders enter the pick queue.
- Lines are sorted by warehouse route, batch, zone or cutoff.
- Barcode scans confirm products and locations before packing.
- Stock movements feed back into connected channels.
WMS pick list FAQ
Related workflows to tighten next
Pick lists work best when the surrounding WMS workflows use the same stock and order truth.
Make every pick list a controlled WMS workflow
Use ChannelDock to release the right orders, guide the route, scan the SKU and keep stock accurate across every sales channel.