An EAN lookup tells you which product a barcode belongs to. For a catalogue team the real job is bigger: turning thousands of EANs, UPCs, GTINs and part numbers into complete product records with images and attributes. SKULaunch uses those identifiers to find the right product page and images for each SKU, then extracts the data into your attributes, across thousands of products at once.
The problem
Consumer barcode lookup sites are built for one product at a time. They return inconsistent, often incomplete results, and the data comes back in their structure, not yours. For a team with 5,000 EANs to enrich, looking each one up, checking it is the right product and copying the data across is weeks of work.
The list usually arrives in poor shape too. A buyer exports it from the ERP, leading zeros have gone, half the column shows in scientific notation, and some rows carry the case barcode rather than the unit barcode. Nobody notices until a lookup returns a 24-pack instead of a single tin.
Before and after
An illustrative example from a list of EANs supplied for a new homewares range.
Before: what you have
5,000 rows: EAN, your SKU, a 20-character ERP name. Example row: 5012345678900, HW-10422, BRSH KTCHN SS 2PK. No images, no attributes.
After: in SKULaunch
- Product page identified for each EAN, preferring the manufacturer's own site over resellers
- Brand and part number confirmed against the page, not assumed from the barcode
- Images found and linked to the right SKU in the DAM
- Key attributes extracted against each product's category, such as material, pack quantity and dimensions
- EANs that could not be matched to a clear source left blank for review, not filled with a lookalike
How it works in SKULaunch
- Set the identifiers. Mark EAN, GTIN or part number fields as the ones to use for sourcing, alongside brand where you have it.
- Source in bulk. SKULaunch searches the web for product pages and images for each identifier across the whole list.
- Extract. Values are pulled into your attributes, normalised to your units and controlled value lists.
- Review. Check matches and values in the grid before anything is approved or exported.
Bulk EAN lookup: manual versus at scale
Done by hand, a single EAN lookup takes a couple of minutes: paste the number into a search engine, open three results, decide which is the real product, copy the title, save an image. Then you key the specs into the PIM. Multiply that by a range launch and it becomes a temp contract.
At scale the steps are the same, but the order matters. Clean the identifiers first, search with the barcode plus whatever else you know, extract to a fixed attribute model, and put a person at the end to check rather than at the start to type. That is the difference between a lookup tool and an enrichment process. If you only hold a code and a short name, the same approach applies, and it is covered in enriching products from a part number and a name.
Barcodes identify, they do not describe
A GTIN tells you who allocated the number, not what the product is. The prefix shows which GS1 member organisation issued it: a 50 prefix means GS1 UK and 93 means GS1 Australia. It does not mean the product was made there, which catches teams out when they try to fill country of origin from the barcode.
That is why lookups by barcode alone often return the wrong item or nothing at all. Treat the barcode as a key for finding the right page, combine it with brand or manufacturer part number where you can, and take the actual specifications from the manufacturer's source rather than a generic database.
Checks before you trust a barcode match
- Check digit. The last digit of every GTIN is calculated from the others. If it fails, the number was mistyped or truncated, and any match is a coincidence.
- Leading zeros. A 12-digit UPC becomes a 13-digit EAN with a leading zero. Spreadsheets strip it, so store barcodes as text.
- Packaging level. The unit, the inner and the outer case each carry their own GTIN. Make sure you are enriching the one you sell.
- Variant level. Each colour and size has its own barcode. A page that lists five colours is not a match for one of them until the colour is confirmed.
- Brand on the page. If the brand on the source page does not match your brand field, stop and check.
- Old or reissued numbers. Discontinued products can still appear in search results. Prefer current manufacturer pages over cached reseller listings.
Fixing bad barcodes before sourcing saves rework later. See validating and fixing GTINs and barcodes for that step.
What changes
A list of barcodes becomes a catalogue of complete products, without anyone looking them up one by one. Your team spends its time checking matches and edge cases, not copying and pasting.
Common questions
What is the difference between an EAN, a UPC and a GTIN?
GTIN is the umbrella term. An EAN-13 is a 13-digit GTIN used across most of the world, a UPC-A is the 12-digit version used in North America, and GTIN-14 is used for cases and outers. Our guide to GTIN, EAN, UPC and MPN covers the detail.
How do I do an EAN lookup for thousands of products at once?
Import the list with your SKU and barcode columns, mark the barcode as the sourcing identifier and run sourcing across the range. Results land in the review grid rather than in a separate spreadsheet.
Which identifiers can we use?
EAN, UPC, GTIN, manufacturer part number or your own code, in any combination. Barcode plus brand gives the best matches.
Where do images come from?
From the sources found for each product, linked to the SKU in the DAM. Use images you have rights to publish. For products with nothing at all, see finding images for products that have none.
What if two products share a barcode?
Conflicts are left for review so the wrong data is not applied to either product.
Can a UPC lookup find products sold only in the UK or Australia?
Yes, if the product has a public web presence. Regional ranges are found through the manufacturer or distributor page rather than a US barcode database.
More on sourcing data: AI web search for missing product data and the full guide to AI product data extraction.

.avif)