Complete Your Shopify Catalog with Verified Product Data
Fill the Barcode (ISBN, UPC, GTIN) field and enrich titles, brands, images, and categories from 1.6B+ products.
Honest scope: CSV and API workflows today. No App Store app yet.
Shopify gives every variant a field called Barcode (ISBN, UPC, GTIN), and a lot of stores leave it empty. That empty field is what blocks Google Shopping approval, price comparison listings, and clean multichannel sync. EcomSource fills it, and the rest of your product data, from an index of more than 1.6 billion products.
TL;DR
- •Shopify has a barcode field on every variant. Google Shopping expects a GTIN in it for most products.
- •Enrich by CSV: export products, upload to the bulk lookup, reimport the completed file.
- •Or automate it: the product API returns clean JSON your app or middleware writes back to Shopify.
- •Same source fixes titles, brands, images, and categories, not just barcodes.
What is the Shopify barcode field?
On every product variant, Shopify includes a field labeled Barcode (ISBN, UPC, GTIN). It stores the universal identifier for that exact variant. Sales channels read this field: Google uses it as the GTIN in Shopping feeds, and marketplaces use it to match your product to their catalogs. If it is empty or wrong, those channels either reject the product or match it to the wrong item.
Why the empty barcode field costs you sales
Google Shopping requires a GTIN for most products that have one. Missing GTINs limit or block listings (Google Merchant Center Help). Our GTIN requirements guide covers the rules in detail.
Marketplace sync fails quietly. Channels that match by identifier cannot match a product that has none.
Duplicates creep in. Without a GTIN anchor, the same product gets recreated under new handles.
Ads get judged on data. Feeds with complete identifiers and attributes are the baseline for Shopping campaigns.
Route 1: the CSV clean-up, no code needed
Step 1. In Shopify admin, export your products to CSV.
Step 2. Upload the file to the bulk barcode lookup. We match each row by any identifier you have, or by product name and brand where you have none.
Step 3. Download the enriched file: verified GTINs in the barcode column, plus titles, brands, and categories where yours were thin.
Step 4. Reimport to Shopify. Spot-check a sample of variants, then submit your feed to Merchant Center again.
A few hundred products take minutes. If you only need to check a handful of codes first, the free GTIN lookup handles one-off checks.
Route 2: the API, for apps and always-on stores
Developers and agencies wire the product data API between their systems and Shopify. The pattern is simple: read variants with empty or suspect barcode fields, resolve each product through the API, write the verified GTIN and any missing attributes back through the Shopify Admin API. A free sandbox key with 10 calls a day lets you prove the loop before paying anything. Our guide to product database APIs for ecommerce walks through the architecture.
What you can fill, beyond the barcode
| Shopify field | What enrichment provides |
|---|---|
| Barcode (ISBN, UPC, GTIN) | Verified GTIN for the exact variant |
| Title and vendor | Clean product titles and correct brand names |
| Product category | Category mapping for better feeds and filtering |
| Images | Product photos where your listing has none |
| Weight and dimensions | Shipping-relevant measurements where available |
Honest notes before you start
Match quality depends on input quality. Rows with any real identifier match best. Name-only rows are matched carefully but deserve a spot check.
Own-brand products with GS1 prefixes you licensed yourself will not be in any external database under your new codes. Enrichment helps you verify format and avoid collisions, not invent codes.
This integration works through CSV and the API today. There is no App Store app to install yet, and this page will say so until that changes.
Variant-level details that trip stores up
Every variant needs its own GTIN. The blue medium and the blue large are different codes. Reusing the parent code across variants causes channel mismatches.
Bundles and multipacks are products in their own right. A two-pack carries its own GTIN, not the single unit code twice.
Products that genuinely have no GTIN, like handmade and custom items, should be declared that way in your feed using the identifier_exists attribute in Google Merchant Center, never given a borrowed or invented code.
Fix your feed this week
Export your Shopify products, run the file through the bulk lookup, and reimport. Free plan covers the first checks, Starter at $10 per month covers most small catalogs (pricing, August 2026). See also product data for dropshipping.
Frequently Asked Questions
Does Shopify require barcodes on products?
Shopify itself does not force you to fill the barcode field. Sales channels do. Google Shopping requires a GTIN for most products that have one, and marketplaces use the same field to match your catalog to theirs.
What goes in the Shopify Barcode (ISBN, UPC, GTIN) field?
The universal identifier for that exact variant: a 12-digit UPC, a 13-digit EAN, or an ISBN for books. All of these are GTINs, which is why Shopify labels the field that way.
How do I add barcodes to many Shopify products at once?
Export your products to CSV, run the file through a bulk barcode lookup to fill the identifiers, and reimport it. For stores that change daily, an API integration keeps new products complete automatically.
Is there an EcomSource app in the Shopify App Store?
Not yet. The integration works through CSV export and reimport, or through the REST API for automated setups. This page will be updated if an app ships.
Can I use this for a dropshipping store?
Yes. Dropshipping catalogs are usually thin because supplier feeds are thin. Enrichment fills identifiers, titles, and images so your listings can pass channel checks.
What if my product genuinely has no GTIN?
Do not invent one and never borrow another product's code. For genuinely code-less items like handmade goods, Google Merchant Center accepts the identifier_exists attribute set to false. Enrichment is for finding real codes that exist, not creating them.