Fast mode: scanning one after another

For single units, scanning one after another is among the fastest ways to count: the code is read, the counter goes up by one and the camera moves on to the next piece. Nothing to write down, nothing to remember. But the mode does not pay off everywhere: scanning 300 identical cartons on a pallet one at a time is wasted effort. Below: when the fast mode pays off, when typing is better and how to keep your rhythm.

How consecutive scanning works

In fast mode every successful read adds one to the counted quantity of the selected item. The number is visible on screen, and a sound or vibration confirms that the code was read. The worker picks up a unit, holds the code to the camera, hears the signal and reaches for the next one. When one position is finished, the worker reads the code of another item and the counter starts again.

The real strength of this mode is that every unit passes through the hands and eyes separately. Among ten bottles that look identical, one may be of a different volume. The scanner shows another code for it at once, while counting by eye would lose it in a group of "ten identical bottles".

When to scan and when to type the quantity

The rule is simple: if there are few units and they differ, scan; if there are many and they are identical, count them and type the number. Agree the threshold before the count begins. For example:

• 1 to 12 pieces, with different sizes or flavours: scan every unit;
• more than 12 identical packs: scan one to select the item, count the rows and type the quantity;
• mixed cartons and pallets: read the carton code and enter the number of cartons, leaving the multiplication by pieces per carton to the software (if the list states the pack size);
• goods with no code or an unreadable one: find the item by name and type the quantity.

A calculation: a shelf holds 36 units of one item. At about a second per scan, that is over half a minute, against five seconds for typing the quantity. But reading all 36 one by one also catches the odd one out. For expensive goods those seconds are worth it; for cheap, bulky goods they are not.

The double-read mistake

The most common mistake in fast mode is one unit counted twice. If the camera lingers at a label, it may read the same code two times. So:

• after the signal, move the camera away from the label at once and only then take the next unit;
• if the software can pause before a repeated read, switch it on, but keep it under a second or genuine consecutive units get skipped;
• watch the counter: for every unit you pick up the number should change by one, not two.

The opposite mistake exists too: the label is creased or glaring, the code failed to read, and the worker assumes it "went through". A unit with no signal is an uncounted unit.

Another trap: the price tag on the shelf edge also carries a barcode. Read it and the software finds the item, but that is a tag, not a unit. Always read the code on the product itself and use the shelf tag only to pick the position.

Rhythm and hand habits

Speed comes from routine, not from the scanner. A tested trick: move each counted unit straight to the other side of the shelf or into a basket. Counted and uncounted goods never mix, and if you are interrupted you can see where you stopped. Goods in one hand, phone in the other; a wrist strap or neck lanyard helps a lot. If one item needs hundreds of reads, a Bluetooth scanner or a terminal with a built-in scanner beats the camera, since it does not wait for autofocus.

Before closing a position

Before closing a position, compare the number on screen with the shelf by eye. If the gap is noticeable, undo the last read or reset the counter and start again. Workers should know where the correction button is before counting starts, or the mistake is left "for later" and forgotten.

Conclusion

Consecutive scanning is a tool, not a dogma: on small, mixed batches it gives accuracy, while on large uniform ones typing the quantity is better. If you have no time to organise the count yourself, order it from StockCheck: the team arrives with scanners and hands over the result as an Excel or PDF file.