Merchant Center Product Identifiers in 2026: GTIN, MPN, Brand and Exemptions

A product gets disapproved for “Incorrect GTIN value” even though the number was copied straight off the box. Or the opposite: everything is approved, yet a third of your catalog quietly gets a fraction of the impressions that comparable items get. Both symptoms usually trace back to the same place — the Merchant Center product identifiers. They never appear in the ad, they do not change a single word of your copy, and they decide whether Google can match your listing to the product it already knows.

This is a working guide to gtin, mpn and brand in 2026: what Google validates, how to check a check digit in under a minute, when a GTIN genuinely does not exist, and how to fix identifiers across a whole feed without waiting on a developer. A one-hour audit checklist and a FAQ close the piece.

Why Google wants identifiers and what you lose without them

Google does not sell your products — it matches them. When a listing arrives saying “Running shoes, size 11, blue,” the system has to decide whether this is the same shoe two hundred other merchants are selling, and then build one entity around it: reviews, a price range, specifications, offer history. The only reliable key for that is the global number the manufacturer printed on the package.

That has four consequences you can see in your own reports:

• Catalog matching. Without a valid GTIN a listing stays an orphan. It still enters the auction, but it never inherits the catalog data that makes a product predictable.
• Price and demand reporting. Price competitiveness and best seller data are built on matched products, which is exactly why the price competitiveness and best sellers reports in Merchant Center go blank for unmatched items.
• Visibility. Google’s own wording is that products missing recommended identifiers get limited visibility. That is not a disapproval — it is a silent demotion, which is harder to notice and easier to ignore.
• AI surfaces. The more unambiguously a product is described, the easier it is for a model to surface it. Same logic as the conversational attributes in Merchant Center: completeness wins placements that bidding alone will not buy.

An identifier does not sell anything. It decides whether Google understands what you are selling — and everything else in the feed is built on top of that understanding.

Three attributes, three different jobs

Identification is handled by three fields. They are not interchangeable, and most catalog damage comes from treating them as if they were.

Attribute	What it is	Who assigns it	Example
gtin	Global Trade Item Number (UPC, EAN, JAN, ISBN)	GS1, through the manufacturer	4006381333931
mpn	Manufacturer Part Number	The manufacturer, free format	GO-7742-BLU-11
brand	The trademark the product is sold under	The brand owner	Nike

The rule in one line: a GTIN is globally unique and identical across every merchant selling that item; an MPN is unique only inside a brand; brand is the name on the package, not the name of your store — unless you are the manufacturer.

What to submit, by product type

• Branded product with an assigned GTIN: submit gtin, brand and mpn when you have it. Maximum data, maximum visibility.
• Product without a GTIN (private label, custom build, replacement part): submit brand and mpn. Do not invent a number — check-digit and prefix validation will catch it.
• Products you manufacture: put your own brand name in brand and a stable internal part number in mpn.
• Genuinely unidentifiable items: set identifier_exists to no. That is an honest statement, not a workaround.

One trap deserves its own line: an internal SKU is not an MPN. If “ITM-00128” exists only in your ERP, it carries no meaning for Google. For your own products it is acceptable as an MPN; for someone else’s brand, pushing your SKU into mpn actively breaks matching.

GTIN formats and the validation rules

A GTIN is not “any number on the barcode.” The format is fixed and machine-checked.

Format	Digits	Used in	Watch out for
UPC (GTIN-12)	12	North America	8-digit UPC-E must be expanded to 12
EAN (GTIN-13)	13	Rest of world	8- and 14-digit variants exist
JAN (GTIN-13)	8 or 13	Japan	Prefixes 45 and 49
ISBN-13	13	Books	Starts with 978 or 979; the recommended form
ISBN-10	10	Older books	Retired in 2007; final character may be X
ITF-14 (GTIN-14)	14	Cases and multipacks	A retail unit normally needs its own GTIN-13

The five rules that break feeds most often:

1. Digits only. No spaces, hyphens, letters or symbols. “4006381-333931” fails.
2. Valid check digit. The last digit is computed from the rest, not chosen.
3. Restricted ranges are not GTINs. Prefixes 2, 02 and 04 are reserved for in-store use; 99 and 981–984 are coupon ranges. None belong in a feed.
4. Leading zeros matter. Spreadsheets love to turn 0012345678905 into 12345678905, which is a different and invalid number. Store the column as text.
5. One GTIN, one variant. Sizes and colors usually carry distinct GTINs. Copying one number across a product line guarantees wrong matches.

Checking a check digit by hand

The algorithm is the same for GTIN-8, 12, 13 and 14:

1. Right-align the number to 14 characters, padding with zeros.
2. Remove the last digit — that is the check digit you are verifying.
3. Working right to left from the digit before it, multiply alternately by 3 and 1.
4. Sum the results.
5. Subtract that sum from the next multiple of ten. The remainder is the check digit.

If it does not match, the number has a typo and no appeal will fix it — the data has to change. On a large catalog, run this as a script across the whole export: identifier errors cluster by supplier and by import batch, which also tells you where to fix the process, not just the rows.

When no GTIN exists: exemptions and identifier_exists

Google lists the categories that never receive a global number:

• store and private-label brands;
• replacement and OEM parts;
• custom-made and made-to-order goods;
• books published before 1970, when ISBN did not exist;
• vintage, antique and one-of-a-kind items;
• pre-orders the manufacturer has not numbered yet.

For these, set identifier_exists: no and keep brand and mpn as complete as reality allows. A missing flag plus a missing GTIN is the single most common source of soft warnings in feed diagnostics — the kind that never disapprove anything and quietly cap your reach. If you work through these systematically, keep the guide to Merchant Center product disapprovals and feed diagnostics next to this one.

The reverse mistake is worse: flagging the entire catalog as identifier-free to clear warnings. The report turns green and every branded product loses its match. You traded a dashboard color for real impressions.

Common failures and what they cost

Failure	How it shows up	Fix
Case GTIN used instead of retail unit	Incorrect GTIN / no catalog match	Use the retail unit number
Leading zeros stripped on export	Invalid GTIN length	Force the column to text in the export
Internal SKU placed in gtin	Invalid check digit	Move to mpn, clear gtin, set identifier_exists
Store name in brand for a third-party product	Limited visibility, catalog mismatch	Restore the manufacturer’s brand
One GTIN across all sizes	Duplicate or conflicting offers	Split variants, group with item_group_id
identifier_exists: no on branded items	No errors — and no matching	Restore the GTIN, remove the flag

Most of those fixes never touch your storefront code. They are handled by feed rules and supplemental feeds in Merchant Center, the same layer you use to rewrite product titles.

Fixing identifiers without a developer

1. Export the broken rows. Filter feed diagnostics by identifier-related issues and pull the item IDs.
2. Sort into three buckets: formatting typos; products that truly have no identifier; products whose identifier exists at the supplier but never reaches your feed.
3. Bucket one goes to feed rules. Trim whitespace, strip hyphens, restore leading zeros — all standard transformations.
4. Bucket two goes to a supplemental feed. A two-column sheet of id and identifier_exists flags only the rows that deserve it.
5. Bucket three goes to procurement. Ask suppliers for the retail-unit GTIN as text, not “the barcode from the price list.”
6. Write the rule down. No new SKU enters the catalog without an identifier or an explicit statement that none exists.

If you recently moved your pipeline, re-check the mapping: during a Merchant API migration, identifier fields are the ones that most often shift types and lose formatting.

A one-hour Merchant Center product identifiers audit

1. Export the full feed and measure what share of items carry a non-empty gtin. Under 70% for a branded assortment is a red flag.
2. Script-validate every GTIN for length (8/12/13/14) and check digit.
3. Find numbers beginning with 2, 02, 04, 99 or 981–984. Those are not GTINs.
4. Count duplicates: how many distinct item IDs share one GTIN.
5. Diff brand against your real brand list to catch store names and category words sitting in the brand field.
6. Count identifier_exists: no rows and spot-check ten of them by hand.
7. Cross the unmatched items against impression share. A consistent gap is the volume you are leaving on the table.
8. Turn the findings into a standing rule for whoever adds products.

Fold this into the rest of your feed hygiene — alongside custom labels for Shopping and Performance Max segmentation and the product image requirements. A feed is one object, and it performs at the level of its weakest field.

What identifiers change in your campaigns

Shopping and Performance Max. Budget flows toward products the system can forecast. An unmatched listing carries fewer external signals and therefore less confident predictions, which shows up as “this product never scales even with headroom in the budget.” It is the same mechanism described in Product Value Optimization in PMax and Shopping, viewed from the data side.

Pricing decisions. Price competitiveness is computed against matched offers. No identifier, no comparison, no pricing input — you end up guessing where competitors sit.

AI product surfaces. Through 2026, feed completeness has become a selection factor on AI-driven surfaces rather than a nice-to-have. Models prefer items they can describe unambiguously, and brand plus model plus global number is the cleanest possible description.

Two companion pieces published alongside this one: Merchant Center shipping settings, the second data block that decides which products get surfaced, and AI campaign localization for Search if you are taking the catalog into new markets.

Variants: sizes, colors and item_group_id

The most expensive identifier mistake is not a typo — it is mishandled variants. The model is simple: anything a shopper can buy on its own is a separate product with its own id and its own gtin. The item_group_id attribute does not merge them into one product; it only tells the system these are variants of one model so the listing can offer a color or size choice.

What follows from that:

• One GTIN copied across a line turns twelve different shoes into twelve conflicting offers of one item. Google picks one and suppresses the rest.
• If the manufacturer genuinely assigned one number to several variants — common with one-size accessories — duplication is fine, because it really is one product.
• item_group_id must be stable. If it changes every time the catalog is re-indexed, grouping collapses and the accumulated statistics go with it.
• Variants need differentiating attributes — color, size, material. Without them the system cannot tell variants from duplicates.

The check is a single query against your export: group the feed by gtin and find numbers shared by more than one id with different size or color values. That list is your fix queue.

Getting identifiers out of suppliers

In most catalogs this is a procurement problem rather than a technical one: the numbers are simply not in the price list you receive. What works:

1. Ask precisely. “Send the retail-unit GTIN as text, 13 digits, per SKU” produces a usable file. “Send us the barcodes” produces a PDF of barcode images.
2. Ask for a file, not an email body. A CSV with supplier SKU, product name and GTIN removes the manual retyping step where typos are born.
3. Spot-check what arrives. Validate ten check digits and compare prefixes — a single manufacturer’s numbers normally share leading digits. Wildly mixed prefixes inside one brand deserve a second look.
4. Put it in the intake rule. No new SKU enters the catalog without an identifier or an explicit “none exists.” That is cheaper than cleaning the feed twice a year.
5. If the supplier will not provide numbers for a branded product, you have two options: get them from the manufacturer directly, or list with brand and mpn while accepting the visibility you lose.

How to confirm a product is matched

There is no “matched / unmatched” column in the interface, but three indirect signals are reliable:

• the product appears in price competitiveness reporting — only matched items can;
• impressions are steady rather than erratic at an unchanged bid;
• searching its GTIN surfaces the same model, not a lookalike.

If none of those hold while the identifier passes validation, the number most likely belongs to a different product — the case where “valid” and “correct” part ways.

When the feed is not the problem

Sometimes identifiers are clean and impressions still do not come. At that point the bottleneck is usually account structure, policy history or destination quality, and more feed work changes nothing. That is the moment to look at the account as a whole — PPC Rebels works through feed, structure and access as part of its Google Ads services, and new markets are usually opened on agency Google Ads accounts with existing serving history.

FAQ: product identifiers in Merchant Center

Is a GTIN mandatory for every product?

No. It is required for products the manufacturer assigned one to. Private label, custom goods, parts, vintage items and pre-orders are exempt; those use brand, mpn and the identifier_exists flag instead.

Can I generate my own GTIN?

No. Numbers come from GS1 and are validated by check digit and prefix range. An invented number either fails validation or collides with somebody else’s product — and the collision is the worse outcome, because it corrupts matching and can trigger disapprovals.

How is an MPN different from my SKU?

The manufacturer assigns the MPN, and it is identical for every merchant selling that model. Your SKU exists only in your systems. Using your SKU as the MPN of a third-party brand breaks matching; using it for products you make yourself is fine if it is stable.

What goes in brand for an unbranded item?

If you sell it under your own name, use your store or label name. If there is genuinely no brand and the item is unique, set identifier_exists to no rather than typing a category word like “Mug” into the brand field.

Why is a product disapproved when the number came off the package?

Usually it is the case or multipack GTIN instead of the retail unit, stripped leading zeros, or stray hyphens and spaces. Validate length and check digit first — that finds the typo in a minute.

Do variants need separate GTINs?

Yes, whenever the manufacturer assigned different numbers to different sizes or colors, which is almost always. Group the variants with item_group_id, but keep each identifier distinct.

Do identifiers affect CPC?

Not directly — bids are not calculated from them. Indirectly they do: a matched product is better predicted and wins more auctions at the same bid. Judge the outcome on profit, as laid out in POAS vs ROAS bidding.

What happens if I flag the whole catalog as identifier-free?

Warnings disappear and branded products lose their catalog connection: no price comparison, weaker visibility on product surfaces. You fixed the report, not the business.

How fast do identifier changes take effect?

Processing after a successful feed upload typically takes hours to a day; recovering visibility takes several days more, because the item has to rebuild statistics. Schedule this work before peak season, not during it.

Can everything be fixed inside Merchant Center alone?

Mostly, yes. Feed rules repair format and strip characters; a supplemental feed sets flags and fills values for a list of IDs. You only need engineering when the identifier is missing from the source system itself.

Will Google’s automatic improvements fix this for me?

Partially. The system can correct and enrich some attributes, but it cannot invent a GTIN that does not exist. What Google changes on its own is covered in Merchant Center automatic improvements.

Where do I start with a huge catalog and no time?

Start with the top 200 products by revenue: length, check digit, brand. Those items carry the business, and on those items a lost match is the most expensive.

Identifiers are not feed bureaucracy. They are the language your catalog uses to talk to Google’s catalog — and while that language has typos, every conversation about bids and creative is premature.