Scan Every Unit or Scan Once? Choosing a Pick Confirmation Mode
A picker is at the bin, holding three units of the right item. What happens next decides whether your paperless picking is fast, accurate, or both. Do they scan once and tap Picked? Scan once and the line is done? Or scan all three?
Each answer is a confirmation mode, and most pick apps let you choose one, usually in a settings screen nobody opens after setup. This post compares the three, explains where each fits, and covers the two settings that sit beside them.
The three modes
Scan, then tap (or type a quantity)
The scan identifies the item, and the picker confirms with a tap, or types how many they picked. It is the most common default, and the closest to how paper works.
Good: forgiving. A picker can correct a quantity before confirming. Fractional quantities (half a metre of fabric, 0.5 kg) need a typed number anyway.
Bad: two actions per line, every line. And the tap becomes the habit. Once a picker learns the tap is what completes the line, scanning becomes optional in their head, especially on a busy afternoon. It is a common enough problem that several pick apps offer a setting that hides the manual confirm button altogether (more on that below).
Scan once, confirm the line
The first matching scan confirms the full quantity. A line of three is done after one scan.
Good: fastest per line. Right when almost every line is one unit, or when the unit you scan is the unit you ship (a sealed carton of 12 scanned as one carton).
Bad: it proves the picker touched the right item, not that they took the right number. Three-unit lines picked as two are the error it can’t catch.
Scan every unit (tally scanning)
Each scan adds one. When the count reaches the line quantity, the line confirms itself and the screen moves on. A three-unit line takes three scans and no taps.
Several systems work this way. In Oracle NetSuite’s WMS, with tally scanning on, the picker scans “each item bar code”, and after tally-scanning everything “you are automatically forwarded to the next order or page”. Ordoro’s barcode pick workflow increases the picked quantity on each successful scan and removes the item from the list once the full quantity is picked. On NetSuite’s community forum, users asking for per-piece scanning gave the reason directly: typing a quantity after one scan leaves room for typos and short counts.
Good: catches quantity errors as well as item errors. For a single-unit line it is also the fastest mode there is: one scan, no tap.
Bad: a line of 24 identical units is 24 scans. For bulk lines, that is slow and tedious, and the picker will start looking for shortcuts.
Speed vs accuracy, line by line
It helps to count actions per line, because that is where the time goes:
| Line | Scan + tap | Scan once | Tally scan |
|---|---|---|---|
| 1 unit | 2 actions | 1 | 1 |
| 3 units | 2 | 1 | 3 |
| 24 units | 2 + typing | 1 | 24 |
| Catches wrong item | Only if the scan happens | Yes | Yes |
| Catches wrong count | No | No | Yes |
(Plus a bin scan on every line, if you require one.)
Two things stand out. First, for single-unit lines, tally scanning costs nothing over scan-once and is half the work of scan-and-tap. In many ecommerce catalogues single-unit lines are the majority, and if that’s true of yours, tally is the right default. Second, the only mode that catches a wrong count is the one that counts.
How to choose
Look at your last month of pick lines and ask three questions.
What share of lines are one unit? If it’s most of them, tally scanning is the default. You get the strictest check at no extra cost on the lines that matter.
Do you pick multiples of the same item often? Apparel and consumables tend to have small multiples (2–4); tally handles those fine. Wholesale and B2B orders with 24 or 48 of a SKU are better as scan-once, or picked as cartons with a carton barcode.
How expensive is a short pick? If a missing unit means a reship and a complaint, count every unit. If the customer is a store that receives against a delivery note and will tell you, scan-once may be enough.
Many warehouses end up in between: tally scanning for ecommerce lists and scan-once for a wholesale wave. If your pick app only allows one mode for the whole account, that’s worth knowing before you choose it.
The two settings beside the mode
Require bin scan. The picker must scan the bin label before the item. It proves they are at the right shelf, which matters when similar items sit in adjacent bins. If it’s off, a good app lets an item scan at the bin step count as both. Turn it off only when each SKU lives in one obvious place.
Require item scan. This hides the manual Picked button, so a line can only be confirmed by scanning. ShipHero’s Enforce All Pick Scans option, for example, “hides the manual quantity input during mobile picking”. This is the setting that fixes the scan-and-tap habit above. Keep a way out for genuine exceptions: a short pick through a skip reason, and typed entry for an item whose barcode won’t scan.
What a confirmation mode needs to feel fast
Whichever mode you choose, a few details decide whether pickers trust it:
- Feedback without looking. A short high tone for a good scan, a low double tone for a bad one, and vibration where the device supports it. Pickers scan with their eyes on the shelf, not the screen.
- A visible count. “2 of 3” in large type once tally scanning starts.
- Instant rejection of wrong items and over-scans, with no change to the count.
- A guard against duplicate scan events. Some scanners send the same code twice within milliseconds, and a tally app that counts both will overpick.
- No keyboard. If the on-screen keyboard appears after every scan, the fastest mode in the world won’t feel fast. See why the soft keyboard pops up on Android barcode scanners.
How sku.io handles it
The sku.io pick screen defaults to tally scanning: each matching scan adds one, a large “2 of 3” counter shows progress, and reaching the quantity submits the line automatically with a success tone and vibration. A single-unit line needs one item scan and no tap.
A tenant setting, Each scan counts, switches between Each unit (tally) and Whole line (first scan confirms the full quantity). Two more settings, Require bin scan and Require item scan, work as described above. With item scan required, the manual confirm buttons are hidden, and short picks go through Skip → Not enough. Fractional quantities keep a quantity stepper, because you can’t tally half a unit.
Wrong items and over-scans are rejected at scan time with an error tone, a double vibration and a message naming the expected item, and the same code arriving twice within 250 milliseconds is counted once.
For everything else that goes into a paperless pick process (hardware, exceptions, pick paths and building batches from saved views), read the practical guide to paperless picking. To see how other systems compare on these settings, see paperless picking software compared.
Sources
- Oracle NetSuite, Picking Items for Multiple Orders (tally scanning)
- NetSuite community, WMS scanner: scan each part to enter picked quantity
- Ordoro, How to Pick Orders with Barcode Scanning
- ShipHero, Overview: NEW Mobile Picking Interface and Workflows (Beta)