Barcode Scanning on the Shop Floor: What to Label and What to Scan
The cheapest adoption lever a manufacturing execution system has is not a dashboard or a report. It is a 300-thousand-rupiah keyboard-wedge scanner. When an operator scans instead of types, the terminal stops being a form to fill in and becomes a scanner with a screen, and the record stops depending on somebody remembering a part code. If adoption is the risk in your rollout (it usually is), scanning is the fix.
What to Label
You do not need to label everything on day one. Four label types cover most of the value:
- Material bags and containers: the part code on every incoming bag or drum. Scanning it at check-in ties the material to the work order without a lookup.
- Lot stickers: supplier lots and internal lots. The lot code is the unit of traceability; a scanned lot at check-in is a genealogy edge that costs nobody a keystroke.
- Machines and stations: a code on each machine. A wall-mounted terminal plus a machine QR means an operator walking up to any station just scans it and the terminal loads that station's queue. No menus.
- Travelers and work orders: the job ticket carried with the batch. Scan it to pull up the job instead of searching a list.
Print them on a cheap thermal label printer. Laminated card in a job jacket works before that.
Which Scanner to Buy
Start with a USB keyboard-wedge 2D imager. "Keyboard wedge" means the scanner types the code and presses Enter, exactly like a person, so any software that accepts typed input accepts the scan, with zero integration. Spend the money on a 2D imager (it reads QR and DataMatrix, not just bar lines) and a decent stand. Rugged handhelds can come later; a wired imager on a coiled cord survives the floor better than a bluetooth pairing.
The one technical rule: the scan must end with a terminator (Enter or Tab) so the receiving field knows the code is complete. Every scanner on the market can be configured to append one; test it on day one.
The Four Rules That Keep Scans Trusted
- One field accepts many label kinds. The operator should not choose "scan material" versus "scan lot": one box that routes by code. Fewer decisions, fewer wrong fields.
- A miss is visible, not silent. If a scan matches nothing on the step, say so on screen, immediately. A scanner that quietly does nothing trains people to stop trusting it.
- Scans record capture method. The record should know a scanner produced it, not a keyboard. When you audit a lot later, scanned entries are the ones you trust.
- Paste behaves like a scan. Offices and QC desks sometimes paste codes; the capture logic must treat a paste-with-terminator exactly like a hardware scan, or the two paths drift apart.
What Scanning Actually Buys You
Not speed: the typing was never the bottleneck. Scanning buys identity. A typed part code can be a near-miss ("40CR-04" vs "40CR-040") that quietly corrupts a WIP record; a scanned code is the code. Multiply that across every material check-in and every lot consumption, and the recall answer stops depending on everybody having typed carefully for two years.
Frequently Asked Questions
Do we need to relabel all incoming material?
No. Label what you receive into the pilot: when a bag arrives without a usable code, print one at goods-in and stick it on. The goal is that everything the operator touches at the station has a scannable code, not that your suppliers change their packaging.
QR codes or traditional barcodes?
QR where you have space and 2D content (a code plus a lot plus a date on one label); Code128 where the label is small or curved. A 2D imager reads both, so you can mix freely.
Will a scanner work with gloves and bad lighting?
A decent 2D imager reads through nitrile gloves and tolerates dim workshops; frozen and foundry environments are the exception: there, use ruggedized scanners with imager sensors rated for the temperature. Test with the actual gloves the line wears.
Scanner-First Terminals, Included
Voltrus MES terminals are built around a single scan box that understands material codes, lot codes, and machine codes, with capture method recorded on every transaction. One line to start.
See Voltrus MES