On this page
What a picker actually needs
A picking screen should be fast, physical, and hard to misunderstand. The picker should not need to think about which order an item belongs to before scanning it. If the item is in the pick batch, scanning it should reduce the quantity left.
That is especially useful for stores that use Magento for catalog data, Veeqo for order flow, and a scanner phone for stockroom work.
Why pick totals are simpler
For many small stores, a totals-only pick is easier than moving order by order. If three orders contain the same SKU, the picker can see one row with the total quantity needed instead of three repeated rows.
- Combine matching SKUs across the selected pick.
- Group items by Veeqo bin location so the pick route is easier to follow.
- Sort items within each bin by SKU so rows are predictable.
- Allow scanning any item in the batch, in any order.
- Move completed items to the bottom so the remaining work stays visible.
How Veeqo fits
The practical workflow is to use Veeqo the way the store already does: mark or send the orders for picking in Veeqo, then use M2 InstaCount as the scanner-friendly picking interface for the items in that pick.
Because Veeqo's public API may not expose the same internal picked-line behavior as Veeqo's own scanner and app combination, the safer workflow is transparent: pick in M2 InstaCount, then manually complete, finish, or cancel the pick action in Veeqo based on the store's normal process.
The goal is not to fake Veeqo's scanner app. The goal is to give the picker a better screen while keeping Veeqo as the order system.
What the picking screen should show
Strong SKU
SKU should be the easiest text to see because it is the safest identifier when products look similar.
Useful product context
Image, title, price with shipping, barcode, and short expandable description help confirm the right item.
Obvious scan feedback
Correct scans should feel immediate. Mismatches should be impossible to miss before the picker moves on.
The best version is boring in the right way: a clean list, grouped by bin, optimized for the scanner phone, and easy to use while standing in the stockroom.
FAQ
Should picking be grouped by order or by item?
For batch picking, item totals are often faster. The user can scan any item in the pick, and the screen shows what is left across the whole batch.
Why group by bin location?
Bin grouping helps the picker move through the stockroom in a cleaner sequence instead of bouncing between locations.
Can completed rows disappear?
They should usually compress or move lower on the page, not vanish completely. That gives confidence without letting completed work crowd the active list.