Scanning and labels
Barcode scanning and label printing for retail inventory
Scanning and labeling look like hardware questions. They are mostly data questions wearing hardware clothes — which is why buying a better scanner so often changes nothing.
Planned against your item file, not sold as a scanner.
Why does scanning still go wrong after we buy a good scanner?
Because the scanner is not the part that is wrong. A barcode points back to a stock item record, and everything downstream — the price at the till, the department on the report, the count on the shelf — comes from that record. If the record is missing, duplicated or wrong, a faster scanner just reaches the wrong answer sooner. Scanning is a data quality project with a device attached to it.
This is also why scanning and labeling belong in the same conversation. A label is the item file made physical: print one from a record that is wrong and you have published the mistake onto the shelf, where a customer will find it before you do.
- The barcode points at a recordPrice, department and stock all come from the item file, not the label.
- A bad record cannot be scanned betterHardware reaches the wrong answer faster.
- Labels publish whatever the record saysA price change that never reaches the shelf is an argument at the till.
- One product can need several codesVendor packs and changed UPCs are normal, not exceptions.
Which scanner and which label printer suit a store depends on the barcode types, the connection, the software version and where the work physically happens. We review that rather than publishing a compatibility list.
The workflows
Where scanning and labels actually do the work
Six jobs, and they are rarely all strong at once.
Checkout scanning
Ring items from the code rather than from a lookup, so the lane moves and the cashier stops guessing.
Product lookup
Inventory managementFind an item by code, SKU or description when the label is missing or damaged.
Alternate scan codes
Let one product scan under more than one code, which is what vendor packs and changed UPCs require.
Shelf and price-change labels
Label printingPrint after a price update so the shelf and the item file say the same thing.
Receiving labels
Purchase orders and receivingLabel goods as they arrive, before they reach a shelf and become somebody else’s problem.
Stock count scanning
Stock takeCount from the shelf instead of from a clipboard, and find the barcode problems while you are there.
What a scanning problem usually turns out to be
-
The item is not in the file at all
Staff ring it to an open department, and that sale is invisible to every report afterwards.
Log what failed to scan, correct the records, and train the counter on what to do meanwhile — in that order.
Item file setup -
The shelf price and the till price disagree
The customer is right, the cashier is embarrassed, and the store eats the difference.
Price changes and label printing are run as one process rather than two that drift apart.
Label printing -
A large label run was printed before it was tested
Thousands of labels with an unreadable barcode or the wrong field, and the work gets done twice.
Print a small test batch, scan it, read it, then run the rest. Every time.
Label printers -
Nothing gets labeled at receiving
Products reach the shelf unlabeled and the count is wrong before anybody has miscounted.
Labeling belongs in the receiving workflow, not after it.
Purchase orders and receiving -
Barcode structure was never planned
Duplicate codes and inconsistent SKUs, which a big import then multiplies.
Code and SKU structure gets decided before an import or a relabel, because afterwards is expensive.
Data conversion
Scanning and label questions
Will a better scanner fix our item lookup problems?
Rarely on its own. If the item record is missing or wrong, the scanner will find that out faster. The scanner is worth upgrading once the file behind it is right.
Can one product scan under more than one barcode?
Infinity can support alternate scan codes where they are configured. That is what you want when a vendor pack carries its own code or a UPC changes.
What should happen when an item does not scan?
Something deliberate. The right process depends on your configuration and your store policy, but "ring it to an open department and move on" is the one answer that guarantees the reports stay wrong.
Can we print shelf labels after a price change?
Yes, where it is configured — and it is worth treating as part of the price change rather than as a separate job somebody remembers.
Which label printer should we buy?
It depends on label size, how much you print, the barcode quality you need and where the printing happens. An aisle and a back office are not the same machine.
Can scanning help with stock counts?
Yes. A count is worth doing for the accurate number, and again for the barcode problems it exposes on the way.
Can you help us fix the item file itself?
Yes. Product codes, descriptions, departments and alternate codes are work we do, and it is usually where the real problem turns out to be.
How do I get a price for scanners or label printers?
Choose Hardware Pricing on the contact form, and say what fails to scan today, what needs a label and where that work happens. The workflow decides which devices fit, so it comes before the price.
Start with the item file, not the scanner
Tell us what fails to scan, what gets labeled and who does it. That is usually enough to say where the problem actually is.