The scanner beeps. A number appears. But the billing screen says "Product not found".
Before ordering new labels, check whether your software knows which product that number belongs to. A readable barcode and a complete billing record are two separate parts of the checkout process.
Why does a barcode scan but show no product?
If the scanner sends the correct number but the software cannot find an item, check the product record, barcode field and catalogue synchronisation first. The identifier may be missing, linked to the wrong variant, or unavailable in the store or application you are using.
A normal EAN-13 product barcode carries an identifier. Product descriptions and prices are generally retrieved from the receiving system's database. Buying or printing the barcode does not automatically create that record in every retailer's billing software.
First, identify which part is failing
| What happens | What to check first |
|---|---|
| No number reaches the application | Scanner connection, input settings and physical label readability |
| The correct number appears, but no item is found | Product records and the field used for barcode lookup |
| A different product appears | Wrong label, incorrect assignment or duplicate product mapping |
| The right item appears with the wrong price | The price record and applicable store or promotion settings |
A beep alone does not prove that the billing application received the intended value. Check the actual output. If the symbol itself cannot be read reliably, use our separate guide to barcode printing and packaging mistakes.
1. Compare the scanned value with the approved number
Take one affected product and its approved barcode record. Use your software's scan-test function, if available, to capture what the scanner sends. A scanner configured to act as a keyboard can also be tested in an empty text field.
Compare the captured value with the assigned identifier, digit by digit. Check for missing digits, extra characters or unexpected formatting. Do not add or remove zeros simply to make a lookup work; ask your software provider how identifiers should be stored and matched.
If the captured value differs from the approved number, investigate the label and scanner configuration before editing catalogue records.
2. Find the exact product variant in your catalogue
Search by the product name or your internal stock code. Open the record for the exact item in your hand.
Suppose your shop sells lemon handwash in 250 ml and 500 ml bottles. Finding the general "Lemon Handwash" listing is not enough. Check that the scanned identifier is assigned to the correct bottle size.
Ask the colleague managing the catalogue to confirm:
- The product record exists in the system being used at checkout.
- The correct variant is selected.
- The identifier is saved in the field that the application searches.
- The record is active and available for the relevant sales channel or location, where the software requires this.
Field names and availability settings vary by software. Follow your provider's instructions rather than assuming every billing system uses the same setup.
3. Check the import and save process
A spreadsheet can look complete even when some rows were rejected during import. Review the import report and open an affected record in the application itself.
Keep identifier columns as text in your working sheet. Check that the import mapped the barcode column to the intended destination field, rather than to a description or internal reference field.
Then export or inspect a sample of saved records. This helps catch a problem that might otherwise be repeated across the entire catalogue. Keep a backup before making bulk changes.
4. Look for incorrect or duplicate assignments
If scanning opens the wrong product, search the catalogue for that exact identifier. Check whether somebody attached it to another record or printed the wrong artwork on a batch of labels.
For example, a packing team may apply the 250 ml handwash label to the 500 ml bottle. The scanner can read the label perfectly while the transaction still identifies the wrong item.
Do not fix this by changing a correct record to match an incorrectly labelled pack. Establish which assignment was approved, separate the affected stock, and correct the source of the mismatch.
5. Check whether the checkout has the latest catalogue
Was the product added this morning? Is the checkout using a different store account? Does the application keep an offline catalogue?
These are useful questions for your software team. Confirm that the latest records have reached the affected device through the system's supported update process. Avoid deleting and recreating products as a first response; that can complicate stock and transaction history.
Try a known working product on the same device. Then test the affected item on another configured checkout, if available. Record what changes. This gives support a much clearer starting point than "the barcode is broken".
6. Complete a small checkout test
After correcting the record, test one item before updating a whole range. Confirm that the scan retrieves the correct name, size or colour, selling price and unit of sale.
Use a test mode where available. Follow your store's process for handling any test transaction so it does not leave an unintended sale or stock adjustment.
Keep a short approval record: product, assigned identifier, test device, result, date and person checking it. That small habit makes future label changes easier to trace.
Does an online barcode lookup fix the billing record?
No. A public product lookup and your retailer's catalogue are separate systems unless an integration connects them. Seeing a product in an online database does not prove that a specific checkout has imported it.
Equally, an item missing from one lookup service does not by itself establish that the printed number is invalid. Check the identifier's source and the requirements of your intended retailer separately.
Prepare a useful handover for your retailer
Send an approved product list containing the product name, variant, internal reference, assigned retail identifier and matching artwork filename. Add commercial fields in the retailer's requested format.
If you are preparing a new range and your sales channels accept the selected identifier route, review YesBarcode's EAN-13 packages. The current packages include JPG and SVG artwork plus an Excel number list. Use that list as an input to your product records; the receiving billing system still needs its own setup.
For an existing "product not found" problem, investigate the mapping before purchasing replacement numbers. A missing catalogue entry may only need a record correction.
Frequently asked questions
Why does my scanner beep but show no product?
Check whether the application received the correct identifier. If it did, review the matching product record, barcode field and catalogue availability. A beep alone does not confirm a successful lookup.
Does buying a barcode add my product to every shop's system?
No. Each retailer needs the relevant product data in its own system or through a supported integration.
Should I buy a new barcode when a product is not found?
Not automatically. First check the existing assignment and software record. A missing or incorrectly imported entry does not by itself mean the product needs a new identifier.
What if the barcode shows the wrong product?
Compare the physical item, printed label and approved catalogue mapping. Check for a wrong label or duplicate assignment before changing records.
Can a phone scan confirm that my billing setup works?
No. A phone may read the symbol or search a different database. Test the actual checkout application and confirm the returned product details.