Does every product need a separate barcode label?
Label design depends on what is being tracked. Separate identifiers may be used for product/lot, work order or operation; the record represented by each code must be clear.
ERP Guides
Shop-floor data capture guide
How to Set Up Barcode Production Tracking
Barcode production tracking helps workers record shop-floor activity by scanning work-order, product or operation identifiers. A successful setup depends on more than printing labels: scan points, transaction rules, user training and error correction all matter.
Practical workflow
Set up the barcode workflow in six steps
-
01
Choose the transactions to track
Choose which events to capture: start/finish, completed quantity, scrap, downtime or operation transfer. Clarify which decision or report each scan will support.
-
02
Identify what needs a barcode
Select identifiers for work orders, products/lots, operations and, where needed, workers or equipment. Codes should be unique, with a manual verification method available if a label cannot be read.
-
03
Place scan points in the actual workflow
Locate scan points for operation start, completion and material/product transfer on the shop floor. Test scanner or mobile-device placement, network access and label handling conditions in the actual environment.
-
04
Define required fields for each transaction
Define which fields are captured automatically or entered by the user after scanning, such as transaction type, time, user, quantity, resource and scrap reason. Keep required traceability fields while avoiding unnecessary entry.
-
05
Set rules for incorrect or duplicate scans
Define how the system warns about a wrong work order, closed operation, duplicate scan, missing quantity or offline record, and who can correct it. Keep transaction history auditable.
-
06
Run a pilot before rollout
Pilot with one production area and a limited set of work orders. Review scan time, errors, worker experience and planned-versus-actual data consistency; resolve issues before expanding.
Example workflow
Recording operation start and finish
A worker scans the work-order label, then the machine code at the operation station and selects “start.” When the work is complete, a “finish” transaction is recorded for the same order and operation, with completed quantity and any scrap quantity. The system associates records with time and user.
- 1Scan work order
- 2Select operation/work center
- 3Record start
- 4Record finish and quantity
Checkpoints
Check before rollout
- Are labels easy to scan on the shop floor?
- Does each barcode map uniquely to the work order/product/operation?
- Do start and finish events match the same job/operation?
- Are quantity, scrap and user fields required where needed?
- Is there a correction process for duplicate or incorrect scans?
- Have pilot users been trained and given feedback?
Quick answers
Frequently asked questions
Can scanning record operation start and finish times?
If supported by the workflow and system configuration, a timestamp can be attached to scan events. Device clocks, user identity and correction handling should also be controlled.
What should happen during a network outage?
Decide before rollout whether offline transactions can be stored and how they will sync later. Include checks for duplicates or out-of-order events.
Does barcoding replace production tracking?
No. Barcoding is a way to speed up data entry. Scanning alone does not create reliable tracking without correct work orders, operations, ownership and transaction rules.