You've got 2,000 products to load into BigCommerce. Your supplier sent a spreadsheet with SKUs, some prices, and a column labeled "Barcode" — but half the values are blank or wrong. Your Google Merchant Center account is already throwing GTIN warnings. And BigCommerce's import wizard just rejected your CSV for the third time this morning.

This is the real BigCommerce catalog problem. Not the tutorial version where you upload 10 clean test products. The production version where your catalog data is messy, your barcodes are inconsistent, and getting it right matters because Google Shopping won't serve products with bad identifiers.

Here's how to fix it — systematically.

Why Barcodes Are the Foundation of Your BigCommerce Catalog

BigCommerce has three dedicated fields for product identifiers in every product record: UPC, EAN, and MPN (Manufacturer Part Number). Most merchants leave them blank. That's a mistake with real consequences.

When you connect BigCommerce to Google Shopping — via the native Google Shopping channel or a data feed app — Google's Merchant Center checks these fields against its product database. Products with valid GTINs (Global Trade Item Numbers, which covers UPC, EAN, and other barcode formats) get:

• Priority placement in Shopping results for matching searches
• Automatic image sourcing from Google's product graph when your images are unavailable
• Lower disapproval rates — GTIN warnings are the #1 cause of Merchant Center account health issues for mid-size BigCommerce stores

Google's official stance since 2026: GTINs are technically "optional" but products without them receive lower ad impression share and organic Shopping visibility. In practice, leaving UPC/EAN blank means you're running with a handicap.

The BigCommerce CSV Structure: What Actually Matters

BigCommerce's Modern Import/Export format uses a CSV template with required and optional fields. Here's the breakdown that matters for barcode-first catalog builds:

Required fields (import will reject without these)

Barcode/identifier fields (optional, but critical for Google Shopping)

The UPC/EAN field in BigCommerce accepts both 12-digit UPC-A and 13-digit EAN-13 formats. When Google Shopping reads your product feed, it maps this field to gtin automatically — provided your brand and identifier combination passes Google's validation.

The import file limit

BigCommerce's CSV import caps at 20 MB and 10,000 products per file. For larger catalogs, split the CSV and import in batches. Each batch runs as a background job — you get an email confirmation when it completes, and row-level errors are logged in a downloadable error report.

The Three CSV Import Failures That Waste Your Time

Before you can fix your barcode data, you need to get through the import itself. These are the three errors that kill BigCommerce imports most often:

1. Duplicate SKUs

BigCommerce treats SKU as a unique key. If your CSV has duplicate SKU values — even across variants of the same product — the import will fail or silently skip rows. Clean your SKU column first: a COUNTIF check in Excel flags duplicates before they cause problems.

2. Image URLs that aren't publicly accessible

BigCommerce fetches images from URLs during import. If your image is behind authentication, on a local server, or returning a 404, the product imports but with no image. Always host images at publicly accessible URLs before running the import — an S3 bucket or CDN path works well.

3. Variant mismatches

If you're importing products with variants (sizes, colors), every variant row must have the same Product Name and a consistent Option Name / Option Value structure. One inconsistent option value format breaks the entire variant group silently.

Populating UPC/EAN at Scale: The Barcode Lookup Pipeline

Here's where most BigCommerce catalogs fail: you have the product, you have the SKU, but you don't have the barcode. Or you have a barcode that might be correct but you haven't verified it.

The right approach is to treat your barcode as a lookup key, not just a field you fill in manually.

Step 1: Categorize what you actually have

Go through your supplier data and sort the barcode column into:

• Valid UPC (12 digits) — go straight into BigCommerce
• Valid EAN (13 digits) — same
• Truncated (8–11 digits) — likely EAN-8 or UPC-E shortcodes, need expansion
• Blank or "N/A" — need lookup via product name + brand
• Wrong format — text fields with dashes, spaces, or letters mixed in

Step 2: Validate and enrich via barcode lookup API

For each valid-looking barcode, a product data API returns the full product record: title, brand, description, images, and verified GTIN. This does two things simultaneously — it confirms your barcode is real, and it gives you enriched product data to fill out your BigCommerce catalog fields.

For blank barcodes, a reverse lookup (brand + product name → GTIN) can fill gaps, though match rates vary by category.

Step 3: Enrichment coverage rates by category

Based on typical catalog enrichment projects:

If your category falls below 60%, plan for a manual review phase. The enrichment pipeline handles the bulk; the remaining gaps need human judgment or GTIN exemptions.

Mapping BigCommerce to Google Shopping: The Field Translation

Once your BigCommerce catalog has clean barcode data, connecting to Google Shopping requires mapping BigCommerce's field structure to Google's product feed format:

The most common Google Merchant Center error for BigCommerce stores: GTIN and brand don't match Google's records. This happens when:

• Your UPC is from a different variant than what you're actually listing
• Your brand field has a typo or alternate spelling
• The GTIN is for a single unit, but you're selling a multi-pack (which needs its own GTIN or an is_bundle: true attribute)

Fix these in BigCommerce's product editor before re-syncing your Shopping channel. Trying to fix them at the Merchant Center feed level is slower and creates technical debt.

The Automation Pipeline: From Barcode Scan to BigCommerce Import

If you're stocking new product lines or onboarding supplier inventory regularly, doing this manually every time isn't sustainable. Here's the pipeline structure that scales:

Input: Supplier spreadsheet with product names and barcodes Output: BigCommerce-ready CSV, Google Shopping-compliant

1. Intake supplier data (CSV or XLSX)
2. Clean barcode column → standardize to 12/13-digit numeric strings
3. Barcode API lookup → return title, brand, description, images per UPC
4. Fill coverage gaps with brand + name reverse lookup
5. Map to BigCommerce CSV template fields
6. Flag uncovered SKUs for manual review queue
7. Import to BigCommerce (batch at 5,000 rows if catalog > 10K SKUs)
8. Verify Google Shopping sync → check Merchant Center for GTIN warnings

The time math: manually enriching 500 SKUs at 3–5 minutes each is 25–40 hours of data entry. The automated pipeline handles the same 500 SKUs in about 20–30 minutes, with the only human time being the manual review phase for the 10–20% of SKUs that didn't match.

At 5,000 SKUs, the manual approach requires a dedicated week. The pipeline completes overnight.

What to Do With Products That Have No GTIN

Not every product has a barcode — and that's legitimate. Private-label items, handmade goods, custom configurations, and some imported products genuinely don't have GTINs. For these products:

In Google Merchant Center, submit these attributes:

• identifier_exists: false — tells Google the product has no GTIN by design
• brand — your brand name (required)
• mpn — your internal SKU or part number (required when GTIN is absent)

BigCommerce doesn't have a native identifier_exists field, so you'll set this via your Shopping channel's feed rules or a data feed app. Most feed apps (DataFeedWatch, GoDataFeed, Channable) let you add custom attribute overrides for products where UPC is blank.

The worst outcome: leaving UPC blank AND not setting identifier_exists. Google will flag the product as missing an identifier — generating ongoing Merchant Center warnings and reducing Shopping impression share with no clear resolution path.

Building Your BigCommerce Catalog Right the First Time

The pattern that works for mid-size BigCommerce catalogs (500–10,000 SKUs):

1. Start with barcodes, not product names — GTINs are your catalog anchor. Everything else enriches from a valid barcode.
2. Clean before import — Fix duplicate SKUs, verify image URLs, standardize UPC format in your CSV before touching BigCommerce.
3. Read BigCommerce's error log — Every import job generates a downloadable error report. Row-level errors are specific. Read them.
4. Sync Google Shopping immediately after import — Errors are faster to fix while the import context is fresh.
5. Re-validate quarterly — Supplier UPCs change, products get relabeled, GTINs get reassigned. A quarterly validation pass keeps Merchant Center healthy.

If your catalog starts with clean GTIN data, BigCommerce import is straightforward. If it doesn't, you're doing data cleanup at every step — in the CSV, in BigCommerce's product editor, and in Merchant Center. The time invested upfront in barcode enrichment pays off every time you add products, run Shopping ads, or expand to additional sales channels.

SkuMonster provides barcode-to-product-data enrichment via API — returning title, brand, description, images, and verified GTIN for UPC and EAN lookups. If you're building a BigCommerce import pipeline and need to fill in missing product data at scale, try the API at sku.monster.

Ready to Try SKU Monster?

If you're managing product data at scale — whether you're on Amazon, Shopify, eBay, or WooCommerce — SKU Monster gives you structured titles, descriptions, images, and pricing for any EAN, UPC, or ASIN in seconds.

No manual entry. No scraping. Just clean product data via API.

Start enriching free at sku.monster →