Quick answer
Pilot 20–50 real items. Keep working manufacturer barcodes, create stable internal SKUs, label only items that need them, test readability, and perform a baseline physical count. Then define separate procedures for receiving, counting and replenishment before expanding to the full catalog.
What a barcode inventory system contains
A barcode inventory system connects physical goods to catalog records and records what happens to those goods. It needs a clean item list, identifiers, a way to scan, a quantity record, and repeatable receiving and counting procedures. Hardware alone cannot provide accurate stock. A scanner can read a perfectly printed code while the catalog points to the wrong size or unit.
Keep item identity separate from quantity. The identifier answers “which item?”; the count answers “how many, in which unit, at what time?” Scanning the same bottle does not inherently mean receiving one bottle or counting one bottle. The chosen workflow determines that action. Decide who maintains the catalog, who records movements, and who approves corrections before selecting equipment.
Barcode vs SKU vs GTIN, UPC and EAN
A SKU is your internal stock-keeping identifier. A GTIN is a GS1 identifier for a trade item. UPC commonly refers to GTIN-12 and its barcode family; EAN commonly refers to GTIN-13 and related symbols. UPC-A and EAN-13 are specific linear barcode symbologies. A barcode is the scannable carrier of data, not the product record itself. These terms describe related concepts, not interchangeable fields.
Store SKU and manufacturer barcode in separate text fields, preserving leading zeros. A barcode does not usually contain your description, price or current quantity: software retrieves those from a record. A GTIN identifies a trade item rather than each individual physical copy. If individual assets require separate tracking, define an asset or serial identifier separately. Do not treat two identical bottles as two different catalog products.
Step 1 — Clean the product catalog
Start with 20–50 real items that represent your difficult cases: similar variants, multipacks, loose supplies, damaged labels and products without codes. Walk the shelves and compare them with supplier documents. Give each record a clear name, variant, stock unit, supplier reference, SKU and existing barcode where available. Record missing values honestly rather than inventing manufacturer identifiers to complete a spreadsheet.
Remove exact duplicate records only after checking their quantities and references. Separate items that differ by size, color, flavor or package unit. “Gloves” is too vague if small and large packs are ordered independently. Assign one catalog owner and keep a dated export of the cleaned pilot. A small accurate catalog is more useful than a large import containing unresolved matches.
Step 2 — Decide which identifiers to keep
Keep manufacturer codes, supplier ordering references and your internal SKU together, but give each a defined purpose. A simple pattern such as INT-0001 can work for internal items. Choose a consistent length and character set; avoid encoding a changing shelf position, price or supplier into the permanent identity. Document how the next unused code is issued and never recycle an old SKU for another item.
Define the unit before linking a code. One carton may contain 12 individual bottles, and its barcode may differ from the bottle barcode. Decide whether you count cartons, bottles or both through an explicit conversion. If your software supports only one barcode per record, select the correct stock-unit code and keep other references in your external mapping. Do not assume barcode aliases or packaging conversions are supported.
Step 3 — Reuse manufacturer barcodes where possible
Scan the code on a real product and verify the resulting record against its name, variant and package size. Preserve a working manufacturer barcode when it correctly identifies the unit you track. Replacing every existing code adds printing work and creates competing labels. An automatic catalog match is a starting suggestion: confirm it against the physical item before accepting it.
Look for multiple symbols on packaging. A shipping label, promotional QR code and product barcode can identify different things. Select the product code deliberately. Record a changed manufacturer code when packaging changes, and check whether the product itself or only its artwork changed. Resolve that relationship before combining quantities. Retain supplier evidence so the next receiving person can explain the mapping.
Step 4 — Create internal labels only where necessary
Use internal labels for goods with no usable code, your own work materials or a clearly defined internal tracking unit. A private identifier used only inside your business does not automatically need a GS1-issued GTIN. If you manufacture products for sale through retailers or marketplaces, check their identification requirements and the applicable GS1 allocation process before choosing an external product code.
Code 128 can encode letters and numbers for internal identifiers when your chosen software and scanners support it. Ordinary Code 128 is not automatically GS1-128: GS1-128 uses specific GS1 syntax and application identifiers. Generate a real symbol with a supported label tool, not a visual imitation. Keep a master mapping from the printed value to one item and retire damaged or obsolete labels consistently.
Step 5 — Choose phone scanning or a dedicated scanner
A phone camera is a sensible pilot tool when scan volume is modest and the inventory app supports your codes. Test the actual phone in dim corners, on glossy packaging and on small curved labels. Measure the complete task: identify the item, enter quantity, confirm the action and recover from a bad scan. Camera quality alone does not determine whether the workflow is comfortable.
Consider a dedicated scanner when frequent repeated scanning, gloves, battery demands or difficult labels make the phone workflow slow. A 1D-only reader cannot read a QR code; choose a compatible 2D imager if that is required. Confirm connection method and app compatibility before buying. A Bluetooth keyboard-style scanner can type into an active field, but that does not prove every app supports its receiving or counting workflow.
Step 6 — Choose the label printer and format
Print a small test batch before buying bulk label stock. A sheet printer may be sufficient for occasional labels; a compact thermal printer can suit frequent replacements. Direct thermal media reacts to heat and needs no ribbon; thermal transfer uses a ribbon and can suit more durable labels when matched to the material. Choose adhesive and stock for moisture, friction, temperature and the product surface.
Use dark bars on a light background, preserve quiet zones and generate artwork at the intended print size. Do not stretch a barcode to fill a decorative label. Test the longest internal code, since its symbol may be wider. Add a human-readable identifier and item description to operational labels, without crowding the symbol. Follow the relevant symbology specification rather than applying one universal size to every barcode.
Step 7 — Perform the initial physical count
Choose a clear cut-off time and pause stock movements where practical. If work continues, log every receipt and issue after the cut-off and reconcile them before accepting the baseline. Count sellable or usable goods separately from damaged, returned and quarantined goods. A clean starting balance is a physical observation, not yesterday’s spreadsheet number copied into a new app.
Count in a fixed shelf order and mark completed areas. Scan to confirm identity, then enter the observed quantity in the agreed unit. Recount unexpected differences without looking at the expected balance first if possible. Approve corrections with a reason, date and responsible person. Save the final baseline export and a list of unresolved items; do not force unidentified goods into a convenient nearby record.
Step 8 — Build the receiving workflow
At receiving, compare the delivery with the purchase order or supplier document. Scan one representative item for each line, confirm variant and unit, count what actually arrived and record accepted quantity. Keep shortages, damage and substitutions explicit. Scanning a carton once must not silently add one bottle when the delivery contains 12. Check the packaging conversion before saving the receipt.
Record the supplier reference, date and document number in the system or a supporting log, according to available fields. Give a repeatable route for unknown codes: set the goods aside, check supplier evidence, create or correct the approved record, then receive them. Ensure the same delivery is not recorded twice. A barcode speeds identification; it does not confirm that an invoice quantity physically arrived.
Step 9 — Build the stock-count workflow
Separate a count observation from an incoming receipt. A stock count measures what is present; receiving adds a movement. Define whether entering 8 sets the observed balance to 8 or adds 8 to an existing balance. Test that distinction during the pilot. Repeated scans may increment a count in some tools, but do not assume that behavior without checking.
Use a fixed route through shelves and containers, and mark each completed zone so you neither skip nor repeat it. Count high-turnover or error-prone items more often between full counts. When two people work on the same physical area, assign clear boundaries and reconcile their records. Keep a reasoned adjustment trail rather than repeatedly overwriting quantities until they look plausible.
Inventory Accuracy Formula: How to Measure Stock Accuracy After a Physical Count
Step 10 — Build the reorder workflow
Choose a stock-review interval and record supplier lead time in the same time unit as usage. A practical starting reorder point is expected usage during lead time plus a chosen safety buffer. For an illustrative item using 2 units per day with a 5-day lead time and a 4-unit buffer, the trigger is 14 units. These numbers are an example, not a recommended universal setting.
Compare usable on-hand stock with the trigger, then account for confirmed incoming orders and committed demand where you track them. Check pack sizes and minimum orders before deciding the purchase quantity. Record when an order is placed to avoid buying twice. Revisit the buffer after several receiving cycles, especially if demand or delivery reliability changes. A readable barcode cannot compensate for an outdated replenishment rule.
Handling products without barcodes
Not every physical item needs an individual sticker. For loose screws, cleaning supplies or unwrapped materials, a durable bin label can identify a clearly defined item type. Keep different variants in separate bins and ensure a shelf code identifies the item rather than the shelf position. If products move, move the item label with them or update the mapping deliberately.
Define units for partially used supplies: pieces, sealed packs or measured volume, depending on what you can count consistently. Do not record half a bottle as half a liter without knowing its capacity. Keep custom bundles separate from their components and write down how you account for assembly. A bin scan identifies the record; it does not measure weight, volume or the contents automatically.
Handling duplicate or wrong barcodes
If one scanned value resolves to two different items, stop automatic matching and investigate the physical labels, supplier data and catalog imports. Do not select the first result and continue. Similar names do not prove the items are identical. If two records describe the same item and unit, reconcile their balances and references before retaining one approved record.
If genuinely different items share a supplier code in your private workflow, use an explicit internal identifier for the ambiguous item and preserve the original supplier reference. Keep an exception log with the observed value, affected products and decision. Reprint the corrected label and retest it on every relevant device. Treat a wrong lookup as a catalog problem even when the scanner decodes the symbol perfectly.
Common setup mistakes
The most expensive mistakes often happen before scanning starts: importing numbers as numeric spreadsheet cells and losing leading zeros, mixing cartons with pieces, assigning a new SKU whenever an item moves, and printing hundreds of untested labels. Another mistake is assuming scanning automatically records every sale, consumption or return. Those movements need an explicit procedure or a verified integration in the software you use.
Avoid building a workflow around unsupported features. A label printer, external scanner or spreadsheet can be part of your process without being a native feature of your inventory app. Specify who performs each external step and where the authoritative data lives. Train people to read the item name after scanning rather than trusting a success beep as proof of correct stock identity.
Small-store implementation example
Consider an illustrative neighborhood shop piloting 30 items. Most have working manufacturer barcodes; several loose supplies receive internal bin labels. The owner assigns stable SKUs, stores the manufacturer codes as text and chooses bottles as the stock unit for drinks. A supplier carton contains 12 bottles, so the receiving checklist explicitly converts cartons into bottles before the receipt is recorded.
The owner counts 18 bottles at the baseline, receives one carton and records 12 accepted bottles, bringing the recorded balance to 30. Later, a physical count finds 28. The owner checks intervening sales and issues before approving any adjustment. The barcode stays unchanged throughout; the quantity changes. Only after all pilot exceptions are resolved does the owner expand the catalog and label printing.
What to test before rollout
Run real examples end to end: a leading-zero manufacturer code, the longest internal SKU, a similar variant, an unknown code, a duplicate mapping, a damaged label and a carton-versus-piece receipt. Confirm that each scan opens the intended record and that the quantity action matches the selected workflow. Test manual entry as a fallback, and check that an accidental repeat does not create an unnoticed duplicate transaction.
Print a small batch using the actual printer, media and settings; scan labels on their final surfaces under normal lighting. Include more than one device if the business will use them. For offline work, test the app’s supported disconnected steps and its reconnect behavior with representative data. Export a sample and confirm identifiers remain intact. Write down acceptance criteria and resolve failures before migrating the full catalog.
When a spreadsheet is still enough
A spreadsheet can work for a small stable catalog, one person maintaining records and occasional physical counts. Separate catalog identity from dated movement or count rows, format identifier columns as text and protect the master file from accidental overwrites. Use consistent units and a clear correction log. Back up the file and test the export rather than assuming a saved copy contains every field correctly.
A scanner that types into cells may reduce typing, but it needs a controlled lookup and quantity process. Select the right input cell and test behavior when a code is absent. A sheet becomes harder to manage when multiple copies circulate, receiving is frequent or differences require repeated investigation. Choose based on observed work and error rates rather than the mere presence of a barcode on your products.
When an inventory app becomes useful
An app becomes useful when repeated lookups, physical counts, stock updates and supplier ordering consume time or create errors. Evaluate the full workflow with the pilot catalog, including editing a wrong match and exporting results. Check current limits, device allowances and supported offline steps. Select a product whose available features cover the task; do not treat a roadmap statement as a shipping capability.
Retail Scan & Stock offers phone-based barcode inventory and stock-count workflows and is publicly available on the App Store and Google Play. Its plan allowances are devices, not users. Use it for the supported mobile workflow and check current pricing and product pages for details. Internal label generation, dedicated-scanner compatibility and automatic packaging conversions should be validated separately rather than assumed from barcode scanning support.
Start small, then expand
Keep the pilot catalog, label mapping, baseline count and exception log together. Expand after someone else can follow the procedure without guessing units or matching the wrong product. Review the current Retail Scan & Stock device plans before choosing how many devices to use.
Sources and verification
Official standards and hardware documentation checked on October 3, 2026. Pilot sizes, procedures and the worked example are editorial guidance, not GS1 requirements. Illustrations show a general workflow, not an app interface.
- GS1: GTIN, barcode, EAN and UPC — Identifier and symbol terminology.
- GS1: Barcode standards — Linear and 2D carriers, including QR.
- GS1 US: GS1-128 — Code 128 and GS1-128 distinction.
- GS1 Canada: Barcodes — Product variants, packaging, printing and placement.
- GS1 UK: Quiet zones — Clear margins vary by symbology and size.
- Zebra: CS60 scanner — Dedicated 1D/2D scanner and connection options.
- Zebra — Direct thermal versus thermal transfer printing and ribbon requirements.
- inFlow Inventory — Internal barcode generation versus registered external retail identifiers.
Frequently asked questions
Does every internal item need a GS1 barcode?
No. A private internal identifier can serve your own inventory workflow. Products intended for external retailers or marketplaces may require a GS1 GTIN; check the trading partner’s requirements before assigning one.
Can I use the manufacturer barcode as my SKU?
You can use an existing code as a lookup key, but keeping SKU and manufacturer barcode in separate fields makes variants, packaging and changed supplier codes easier to manage. Preserve identifiers as text.
Is a QR code better than a linear barcode?
It depends on the reader and data. QR is a 2D symbol and can carry a link or structured data; UPC-A, EAN-13 and Code 128 are linear symbols. A promotional QR link does not automatically identify a stock item in your app.
Does scanning update stock automatically?
Only when the selected software workflow is configured to do that action. Identification, receiving, count observations and adjustments are different operations. Test what a scan and quantity confirmation actually save.
Do I need a dedicated scanner and label printer immediately?
Usually the pilot can begin with a compatible phone and existing product labels. Add equipment when tested scan volume, label durability or repetitive work justifies it. Confirm compatibility before purchasing.
What if a barcode scans but shows the wrong item?
Stop and correct the catalog mapping. Compare the physical variant and package unit with supplier evidence. A successful decode proves the symbol is readable, not that its associated record is correct.