Merchlint
Available now
Next, in this order
  • FrançaisFR
  • ItalianoIT
  • PortuguêsPT
  • NederlandsNL
  • SvenskaSV
  • TürkçeTR

A language shows up here once its pages are actually written. Nothing on this site is machine-translated, except a few German and Spanish pages that no native speaker has reviewed yet.

Install free Install
← All checks

WooCommerce product with no GTIN, UPC, EAN or ISBN

An empty GTIN is a common reason a product drops out of Google Shopping and other feeds, and nothing in WooCommerce warns you.

Group
Product identifiers
Confidence
F — fact read directly from your store
Name on the plugin screen
No GTIN, UPC, EAN or ISBN
Included in
the free plugin
Updated
Code
G3a

The symptom

Your feed plugin reports fewer products than your catalog holds. Or Merchant Center limits or disapproves items that look perfectly fine on the storefront. Nothing is broken in WooCommerce: the product saves, displays and sells. The identifier field is simply empty, and no screen in the admin warns you about it.

Where the GTIN field is. WooCommerce has its own field for it since version 9.2, no plugin needed. Open the product and go to Product data → Inventory: the field under SKU is GTIN, UPC, EAN, or ISBN. On a variable product every variation has the same field, on the Variations tab, under the variation’s SKU. One field takes any of the four kinds of number. The database stores it as _global_unique_id, the REST API calls it global_unique_id, and a product CSV has it in the column “GTIN, UPC, EAN, or ISBN”. If you can’t find the field, your WooCommerce is older than 9.2.

Video, 1:11 — WooCommerce GTIN: why products drop out of Google Shopping

What it costs

A GTIN is how every system outside your store knows that your product and someone else’s are the same thing. Without it:

  • The product sinks or drops out. Google says a product with a missing or wrong GTIN may get limited visibility, and one that has a GTIN but does not send it can be disapproved. Most comparison sites lean on the identifier too. None of this shows up in your store.
  • You lose the comparison. A product that does match a known product joins a listing with reviews, ratings and competing prices. One that does not stands alone, with none of that.
  • Marketplaces ask for it before you can list. Amazon requires a GTIN to create a new listing in most categories—a brand without barcodes has to apply for an exemption—and eBay asks for one on most new branded items. A listing without it either fails or ends up unmatched to the product everyone else sells, where nobody finds it.

The same field feeds Facebook and Instagram. Meta for WooCommerce, the plugin that sends a store’s products to the Meta catalog, takes the GTIN from it (version 3.7.8, 400,000 active installations on WordPress.org, code read on November 12, 2026). When the field has a code, that is the code Meta gets. When it is empty, Meta gets a GTIN only if the plugin is set to take one from somewhere else, such as a product attribute.

On a variable product the identifier belongs on each variation, because each variation is a separate item to buy. A parent with an identifier and six variations without one exports as six products with no identifier.

If a shopping feed is what brought you here, this is one of several requirements that drop products without saying so. Why products drop out of your shopping feed walks the rest the same way, with the query for each.

If Search Console’s warning “No global identifier provided” brought you here: what WooCommerce sends Google, and why a filled-in code can still go missing.

How to check it yourself

In the admin, without any plugin. Since WooCommerce 10.4 the product list has a “GTIN, UPC, EAN, or ISBN” column, hidden by default. In Products, open Screen Options (in recent versions of WooCommerce it is the gear icon at the top right), check that column and click its header: products with no number move to the top, with a dash in the column. The list shows products, not variations—a dash next to a variable product says nothing about its variations, whose numbers you only see inside the product, on the Variations tab, one by one.

From WP-CLI. WooCommerce stores the field as _global_unique_id. Without any plugin:

wp db query "SELECT p.ID, p.post_title \
  FROM wp_posts p \
  LEFT JOIN wp_postmeta g ON g.post_id = p.ID AND g.meta_key = '_global_unique_id' \
  WHERE p.post_type IN ('product','product_variation') AND p.post_status = 'publish' \
  AND (g.meta_value IS NULL OR TRIM(g.meta_value) = '') LIMIT 50"

Replace wp_ with your table prefix. To see how much of the catalog uses identifiers at all, count the filled ones:

wp db query "SELECT COUNT(*) AS filled FROM wp_postmeta \
  WHERE meta_key = '_global_unique_id' AND TRIM(meta_value) <> ''"

If that returns zero, your store does not use identifiers—see the false alarms below.

From an export, with nothing to install. Export your products to CSV (in WooCommerce: Products → Export) and open the file in the GTIN validator. It lists the rows with no code, with the product name and SKU, and flags codes with a wrong check digit on the way. In a WooCommerce export it skips variable products, because their variations carry the codes. The file never leaves your browser.

How to fix it

  1. Open the product, go to Product data → Inventory, and fill GTIN, UPC, EAN, or ISBN. The number comes from the manufacturer and is printed under the barcode on the packaging.
  2. On a variable product, fill it on each variation, not on the parent. Different sizes and colors are different trade items and carry different numbers.
  3. For a bulk catalog, map the column in a CSV import—WooCommerce’s own importer accepts GTIN, UPC, EAN, or ISBN as a column. It cleans the value and rejects a number another product already has, but it does not check the check digit or the length.
  4. If the numbers already sit in another plugin’s field, copy them across rather than typing them again. EAN for WooCommerce does it itself (checked on version 5.6.0): WooCommerce → Settings → EAN → Tools → Copy to product meta, with the meta key _global_unique_id, and its Automatic actions for new and updated products keep the field filled from then on. Both are off by default. The copy writes the field directly and skips WooCommerce’s own checks, so a repeated number goes in without objection—run the audit again afterwards, and the duplicate identifier check shows any that came across twice. If the numbers were left behind by a GTIN plugin that has since been closed, see how to move them into WooCommerce’s field.
  5. Do not invent numbers. A made-up GTIN is worse than an empty one: it collides with a real product somewhere and gets your product rejected rather than ignored.

Where the number comes from. Another brand’s product already has a number from its manufacturer or brand owner: copy it from the packaging, and don’t buy one or assign your own. If your own brand needs numbers—because a marketplace or a retailer asks for them—you get them from GS1, through the GS1 organization in your country. In the US, GS1 US licenses a single GTIN for $30 with no annual fee, or ten numbers under your own company prefix for $250 plus $50 a year (GS1 US pricing, as of October 8, 2026). Don’t buy numbers outside GS1: GS1 US warns that they may be linked to another company, and Amazon checks product UPCs against the GS1 database (GS1 US on barcodes for Amazon).

When it’s a false alarm

  • You make what you sell. Handmade goods, your own production, bespoke items and services have no manufacturer’s barcode and need none.
  • Your store does not use identifiers at all. If not one product in the catalog has the field filled, this check does not run—a list of every product would tell you nothing. You will see a note saying so instead of a thousand findings.
  • Your WooCommerce is older than 9.2. The field did not exist before that release, so there is nothing to fill in yet. The check says this explicitly rather than reporting your whole catalog.
  • The identifier lives in a plugin field. This check reads WooCommerce’s own field. Since Merchlint 0.3.3 the audit says how many products keep their number only in a field of EAN for WooCommerce, Germanized for WooCommerce, Trusted Shops Easy Integration, Google for WooCommerce, Customer Reviews for WooCommerce or Product Feed Manager for WooCommerce, and names the field. Later versions added the fields of the two closed GTIN plugins. Until the number is in WooCommerce’s field as well, findings about those products describe that field, not your data. Germanized passes its numbers through WooCommerce’s own field when that field is empty, so with Germanized this check sees them.
  • Gift cards—from version 0.3.5 Merchlint skips gift card products from gift card plugins. A voucher has no manufacturer’s barcode by nature.

How Merchlint finds it

Merchlint reads _global_unique_id for every published product and, on variable products, for every variation except the ones switched off. A variable product yields one finding with the evidence “N variations without a GTIN”, not one finding per variation—so a catalog of two hundred variable products does not turn into a thousand rows.

The check does not run at all when the field is empty across the entire catalog; instead it says which check it skipped and why. That decision is made on the whole catalog, never on one batch, so two scans of an unchanged store always agree.

Merchlint does not validate the check digit, does not look at brand or MPN, and never comments on what any regulation requires. It reports one fact: the field is empty. From version 0.3.5 a field holding nothing but invisible characters—a non-breaking space pasted from a spreadsheet, say—counts as empty too.

Confidence: F—fact from the database. No interpretation, no threshold.

This check runs in the free version, on every product, with no cap.

Run this check on your store

Doesn't match what you see in your store? Email us—we read every message. contact@merchlint.com