A successful scan produces an identifier you can use correctly. For inventory, that means more than a beep: the app must support the code, capture the intended item, preserve its value, and put the result into the right record. Test that complete path before scanning a shelf of products.
Decoding a code and looking up a product are separate
A barcode represents data in a visual format. UPC/EAN codes commonly carry product identifiers; Code 128 can carry other strings; QR codes may contain a web address or other structured data. A scanner can decode a value without knowing the product name, price, or owner. Those details require an appropriate database or application.
Google's ML Kit barcode documentation describes on-device decoding of supported linear and two-dimensional formats. That capability does not guarantee that every camera app exposes every format or that a particular inventory app works offline. Product lookup, account sign-in, and cloud export may still require a connection.
Choose the app around the task: a browser link opener for an ordinary QR link, an identifier capture/export tool for a collection, or an inventory system that associates scans with products and quantities. Check the app's data handling and supported exports before giving it private stock records.
Build a repeatable capture routine
- Choose a representative label, including a small, glossy, or slightly worn example you expect to encounter. Confirm the format is supported.
- Clean the camera lens and use even light. Fit the entire code and its surrounding clear area into the frame. Move the phone until the bars or cells are in focus.
- Avoid glare on reflective packaging by changing the light or viewing angle. Check that a neighboring label is not the one being captured.
- Compare the decoded value with the printed identifier or trusted record. Record the format as well as the raw value when the workflow needs it.
- Scan the same item again deliberately. Observe whether the app adds a row, increments quantity, or ignores the repeat. Choose the intended rule before continuing.
Google's scanning implementation guidance explains why image resolution and a supported format matter. A scanner can also normalize certain formats. Document any conversion instead of silently treating every different-length output as an error.
If the code opens a website, preview the destination before proceeding. A physical label or successful decode does not authenticate a payment page. For a sensitive transaction, verify the organization through an independently known route.
Preserve the identifier as text
Identifiers are labels, even when they contain only digits. Save a raw value unchanged and make any normalized lookup field separate. The GS1 General Specifications describe GTIN lengths and leading-zero handling. A spreadsheet or import tool that treats the value as a number may discard those zeros.
Import identifier columns as text before loading a CSV or other table. Quotation marks in a CSV file alone may not stop a spreadsheet from inferring a numeric type. Verify the reopened result, including the first character, full length, and any long values. If a system expects a normalized 14-digit GTIN, use its documented conversion while retaining the original scan.
A GS1 check digit checks the composition of the identifier. It does not prove that the label is attached to the right product, that the product is genuine, or that your quantity is correct. Those need separate controls.
Try a small inventory exercise before a large count
Invented identifiers, real verification questions
The sample inventory JSON uses internal labels 000123 and 000124 for fictional items. They are not assigned GTINs and are not intended for retail labeling. Values are JSON strings so their leading zeros remain explicit.
Assume a count of three units of Demo Cable and two of Demo Adapter. Scan or enter one identifier per product, then enter the counted quantity: two records, five units in total. If a repeat scan creates another row with three cables, it must be reviewed rather than automatically added to the stock total.
Open the export, confirm both exact identifiers, check that there are two records, and verify the quantity total of five. Compare each record with the physical count. This tests record handling; it is not an optical scanner benchmark.
For a real count, include location and counting session so the same product in two bins can be handled deliberately. Distinguish a repeated scan from another legitimate unit. Keep an unchanged raw export while you clean data, and verify a few records after importing into the final system.
Use the phone-lighting guide when glare or dim conditions cause poor captures. If exports seem to vanish between devices, check the actual storage location with phone-data management.