A readable code is only the beginning
A successful beep tells you the device read something. It does not prove the system selected the correct item, used the correct unit or saved the intended stock movement. Write the full chain: code, item, quantity unit, location, action and confirmation.
For a fictional supplies room, scanning a box label might mean removing one box, while the inventory balance is maintained in individual gloves. A second label on the same package may identify a shipping carton rather than its contents. Choose which code staff should scan and make the instruction visible at the point of work. Do not assume the largest label is the right one.
Map existing labels before generating new ones
List supplier codes that already work, products without usable labels and codes that appear on more than one item. Keep your internal SKU and external trade identifier separate where they serve different purposes. GS1 guidance concerns trade-item identity; an internal label is not a universal substitute for a customer's barcode requirements.
inFlow documents importing existing barcode values, including more than one value for a product, but prohibits duplicate values across its barcode setup. Test your supplier variations before replacing labels. Relabelling every item can create unnecessary work; reusing an ambiguous label can create repeated selection errors.
Test in the actual working conditions
Prepare a small collection of labels with curved packaging, glossy surfaces, small print and ordinary wear. Use the proposed phone or scanner where receiving and picking occur. Include the usual lighting, gloves and network conditions. Record whether the operator sees the expected item and quantity, rather than just whether the hardware reads the symbol.
Test an unknown barcode and a damaged code. Staff need an approved fallback such as a controlled search and supervisor review, not permission to choose the nearest-looking product. If the process requires offline use, ask the vendor to demonstrate how pending actions synchronize and how conflicts are handled; this page does not establish offline support for any product.
Choose a controlled rollout
Begin with a defined zone or product family and keep a short issue log. For each failure, record the label, device, task and result. Distinguish a bad label from a wrong product mapping and from an incorrect workflow choice. Buying a different scanner will not repair a duplicated identifier.
Assign someone to create labels, someone to approve new mappings and a place to report exceptions. Test one receipt, one issue, one return and one correction before expanding. Keep human-readable item information on labels so people can investigate when scanning fails. Finish with a sample set that operators can use safely and a written rule for the exceptions. Claims about faster fulfillment or fewer errors should come from your own measured pilot, not from the presence of barcodes.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- inFlow barcode setup — Merchant documentation · inflowinventory.com · Merchant-controlled · checked 2026-09-24
- GS1 trade-item identification — Reference · support.gs1.org · Publisher independence not verified · checked 2026-09-24