E-commerce
July 1, 2026
A customer may have a product in hand without knowing its exact name. They see a barcode, an EAN, a printed reference, or a photo of a label, and then ask support to find the product sheet, stock, or compatibility information.
The chatbot can speed up this search if the catalog is correctly linked to the product codes. However, it must handle scanning errors, old codes, variants, and products that are no longer sold.
This guide explains how to use an AI chatbot to find a product by barcode and guide the customer to the right information.
Summary
Why is barcode search useful?
A product's trade name can change, be difficult to spell, or exist in several variations. The barcode, however, is often more precise. It allows a reference to be found without relying on the customer's memory.
This search is useful for repeat purchases, compatible parts, consumables, food products, cosmetics, accessories, and items purchased in-store.
When the customer does not know how to name the product, the barcode can become the most reliable shortcut.
Convert over 2,000 customers on average per month with Qstomy.
The world’s 1st Shopify AI dedicated to customer conversion
Empowering 200+ e-commerce merchants
Which data needs to be connected?
The chatbot must be able to link barcode, EAN, SKU, variant, product sheet, stock, sales status, image, and equivalences. It must also know if a product has been replaced by a new version.
Without this connection, the bot risks finding a close but incorrect sheet. For variants, a difference in size, scent, color, or dosage can completely change the response.
How to handle an incorrectly entered code?
A barcode can be poorly scanned, cut off in a photo, or entered with a missing digit. The bot must check the length, format, and close matches before concluding that it cannot find anything.
It can ask for a photo of the label or offer to check a printed reference next to the code. This help prevents the customer from having to retype a long series of numbers multiple times.
What to answer if the product is no longer sold?
The bot must clearly explain that the product is no longer available, then offer a helpful next step: a new version, an equivalent product, a back-in-stock alert, support contact, or an information sheet if it still exists.
It should avoid redirecting to a dead page or simply saying "product not found." The customer is often looking for a solution, not just a product sheet.
How do I use the result?
Once the product is found, the bot can provide the name, variant, stock, link to the product sheet, compatibility information, and useful instructions.
It must also ask what the customer wants to do next: repurchase, verify a part, find an alternative, or ask a question about usage.
Which flow to follow?
The flow must go from the code to the useful action.
Ask for the barcode, EAN, SKU, or a readable photo.
Check the format and search for an exact match.
Check for variants and replaced products.
Present the found product with the important information.
Propose the next action: purchase, alternative, compatibility, or support.
Which messages should be used?
For a found product: “I found this product: [nom], variant [variante]. It is currently [stock]. Here is the corresponding sheet.”
For an incomplete code: “The code seems incomplete. Can you send a photo of the label or check the last digits?”
For a replaced product: “This reference is no longer sold, but it has been replaced by [nouveau produit], which corresponds to the same use.”
When to transfer?
The transfer is necessary if multiple products match the same code, if the customer is looking for technical compatibility, if the reference is old, or if the product comes from another channel.
The bot must transmit the code, the photo if any, the matches found, and the exact question from the customer.
This summary prevents the agent from starting from scratch. They can confirm the correct reference, check compatibility, or explain why an old version is no longer available.
Which KPIs should be monitored?
Track barcode searches, exact matches, unfound codes, old products, compatibility transfers, and conversions after a product sheet is retrieved.
If many codes are unfound, the catalog may be missing EANs, SKUs, or links between old and new references.
Which mistakes should be avoided?
Avoid proposing a similar product without checking the variant. Also, avoid concluding too quickly that the product does not exist when a code is incomplete or old.
The bot must be precise, especially if the customer is looking for a compatible part, a consumable, or a sensitive product.
How can Qstomy help?
Qstomy can link barcodes, SKUs, and product sheets to help the customer find the right reference faster.
The bot can also handle replaced products, variants, and cases where a human check is needed.
Explore the AI sales agent, the AI support, or request a demo.
BARSCANBOT Checklist (8 steps)
Sync BARSCAN-MAP #973: RAG bot barcode EAN index
Policy BARSCANBOT-SUP: 6 rules REGISTRY-GATE PDP-GROUNDED NO-SKU-GUESS
8 bot_barscan_* intents: flow BSB-1 to BSB-8
4 templates TPL-BARSCAN-*: PDP OLD PRICE HANDOFF
Product scanner widget: ean_detect entry mobile store
Shopify variant barcode sync: verify admin live test scan
Red team 10 EAN: invent SKU dead end test
KPI Dashboard: barscan_bot_* section 9 + delta barscan_
FAQ
Difference #973?
#973 = agents verify ops mapping staff execute. #974 = bot tier 1 lookup widget.
Bot invents a product?
No, outside BARSCAN-MAP. NO-SKU-GUESS-BOT. Handoff if unknown.
Difference PRINTCATbot #962?
#962 = catalogue text reference. #974 = shelf label EAN scan.
Difference PRINTCOUPBOT #970?
#970 = coupon print checkout. #974 = physical product barcode.
Store web price dispute?
Bot quotes price_policy map. Dispute confirmed → PRXDIFFbot #748 handoff #973.
Going further
This week: sync BARSCAN-MAP #973, product scanner widget, PDP OLD templates, measure barscan_bot_deflect.
Enzo
July 1, 2026
