First, export the affected items and their identifier fields
Open the Merchant Center diagnostics, filter to the identifier-related issues and download the item list. Add the
identifier fields for each item as the feed sends them, gtin, brand, mpn and identifier_exists, and, from the
store's own catalogue, the same fields as they are stored there along with the product's supplier and whether it is an
own-brand or custom item. Join the list to sales data so the groups can be ordered by revenue at risk; a limited
best-seller matters more than a long tail of slow lines.
Then sort. Items whose store record holds a GTIN that the feed lacks point to the export or a rule. Items whose store record has no GTIN split into two: products that have a barcode nobody captured, and products that genuinely have none. Items that carry a GTIN Google rejects as invalid, or one shared with an unrelated product, point to the supplier. Items missing only brand or MPN are a data-entry gap. Each group maps to one row of the table. The attribute definitions themselves are in the product feeds guide and the product data specification; this page sorts the items and routes each group to a fix.
Diagnosis table
Diagnosis
| Symptom | Check | Likely cause | Fix |
|---|---|---|---|
| Branded, barcoded products flagged as missing GTIN | Whether the product's barcode is recorded anywhere in the store or supplier data | GTIN exists but the feed omits it | Capture the GTIN on the product record and send it in the feed |
| Own-brand or made-to-order items flagged, with no barcode in existence | Whether the item has any manufacturer GTIN; the identifier_exists value sent | Own-brand or custom products without the correct no-identifier handling | Declare that no identifier exists for those items, and send brand and MPN where they apply |
| Items with a GTIN still flagged for incomplete identifiers | Whether brand and mpn are present and correct | Brand or MPN missing from the identifier set | Fill brand on every item and MPN where the manufacturer assigns one |
| Items flagged for invalid GTIN, or several products sharing one code | Check digits; duplicates across the catalogue; supplier source | Invalid or reused GTINs supplied by a manufacturer or supplier | Request corrected codes from the supplier; remove invented or reused numbers |
| Store holds the codes, yet the feed arrives without them | The raw export file against the processed feed; feed rules on identifier fields | Platform export or feed rule dropping identifier fields | Repair the export mapping or the rule so the fields pass through |
Fix, verify and prevent each cause
The barcode exists, the feed leaves it out
For branded products the GTIN is almost always on the packaging and in the supplier's data, but many stores never created a field for it, so the feed has nothing to send. The product feeds guide notes that the specification then treats the product as incomplete and limits where it can appear, which is precisely the warning.
Fix: add a GTIN field to the product record in the store platform if it has none, populate it from the
supplier's data file for the affected items, ordered by revenue, and map it to the feed's gtin attribute.
Verify: after the next fetch, the items move out of the missing-identifier issue, and the product report shows impressions and click-through (CTRShare of impressions that result in a click.) rising on the corrected items over the following weeks.
Prevent: make the GTIN a required field when a branded product is created, so a new line cannot go live without it.
Own-brand and custom items declared the wrong way
Products the business makes itself, made-to-order goods and some vintage or handmade items have no manufacturer GTIN. The warning appears when the feed neither supplies a code nor says that none exists. The opposite mistake also happens: a store sets the no-identifier flag across the whole catalogue, which clears the warning for branded goods while quietly suppressing their catalogue match.
Fix: set identifier_exists to false only for the items that truly have no
manufacturer code, and keep brand, and MPN where the business assigns one, on those items, following the specification's
rules for custom goods.
Verify: the warning clears on the own-brand group, while branded items still carry GTINs.
Prevent: hold the flag on the product record, set by product type, never as a feed-wide default.
Brand or MPN missing from the set
Identifiers work as a set. A product can carry a GTIN and still be flagged as incomplete when the brand is blank, and products without a GTIN often need brand and MPN together to be identified. Brand is frequently missing because the store records it as a tag or a collection rather than an attribute, and MPN because nobody knew what it was.
Fix: add a brand attribute to every product, using the manufacturer's name for resold goods and the store's own name for own-brand items, and capture the manufacturer part number where one exists from the supplier's data, as the product feeds guide describes in its section on identifiers.
Verify: the incomplete-identifier issues fall on the next processing run, and brand searches begin to show the products in the search terms data.
Prevent: include brand in the product template for every category.
Codes that are invalid or reused
Not every supplier code is a real GTIN. Some suppliers send internal stock numbers in the barcode field, some reuse one code across colours or sizes, and some stores have filled gaps with invented numbers to silence the warning. Google checks codes against its own data, so these items are flagged as invalid, or attach to the wrong product.
Fix: list the items with invalid or duplicated codes, ask the supplier for a corrected data file, remove any number the business invented, and where a product genuinely has no code, handle it as a no-identifier item instead; the Merchant Center help centre explains the issue messages for invalid values.
Verify: the invalid-code issues disappear after resubmission, and each variant carries its own distinct code.
Prevent: validate codes when supplier files are imported, rejecting duplicates and malformed values before they reach the catalogue. Where one code has been shared across colours or sizes, the product variants tutorial sets each variant up as its own item with its own id, code and shared item group.
The export or a rule drops the fields
Sometimes the store has every code and the feed still arrives without them. A platform integration may not map a custom barcode field, a third-party feed app may only export the variant's first code, or a feed rule written for titles may overwrite or blank identifier attributes. The shopping and catalogue ads guide warns that fixes made inside a platform's rules drift away from the source, and the same layering explains losses in the other direction.
Fix: compare the raw export file with the processed feed in Merchant Center for a few affected items, find the layer where the field disappears, and repair the export mapping or the rule; keep the canonical value in the store.
Verify: the processed feed shows the identifier for the sample items, and the issue count falls across the group.
Prevent: document which layer owns each identifier attribute, and test a sample of items after any change to the integration or the rules.
Prevention: identifier checks at product creation
Identifier warnings are cheapest to prevent on the day a product is created, because that is when someone has the packaging, the supplier file and the product type in front of them. Build the check into the product template: a branded product cannot be published without a GTIN and a brand; an own-brand or custom product is flagged as having no identifier by its product type and still carries the store's brand; MPN is captured whenever the supplier provides it. Supplier imports run through the same rules, with duplicate and malformed codes rejected before they enter the catalogue. When a whole feed is being connected for the first time, the Merchant Center feed setup checklist puts the identifier check beside the other setup checks.
Downstream, keep the feed a faithful copy of the store. Map every identifier field once in the export, keep feed rules away from identifier attributes unless a rule is written for that purpose, and record which layer owns each field. In the weekly Merchant Center routine the product feeds guide sets out, read the limited-item count by issue and treat a rise in identifier issues as a sign that a new supplier file or a platform change broke the chain. Because limited items lose matching and comparison placements, report identifier coverage on best-sellers beside return on ad spend (ROASRevenue generated per unit of ad spend.), so the cost of the gap is visible to whoever owns the catalogue.
A cycling retailer clears its identifier warnings
A cycling retailer's Merchant Center shows 1,140 of its 3,200 items limited for missing identifiers. Sorted by status,
620 are branded components whose barcodes sit in supplier files but were never imported; 310 are the shop's own-brand
clothing, sent with neither a code nor identifier_exists set; 140 carry GTINs but no brand, because brand was stored as a
collection; and 70 share 12 codes that a supplier reused across sizes. The team imports GTINs for the components, sets the
no-identifier flag on own-brand clothing by product type, maps the brand field in the export, and gets corrected codes from
the supplier. Within three weeks limited items fall to 45, impressions on the corrected components rise by 38%, and return
on ad spend on that segment moves from 3.2 to 4.1 with bids unchanged.
Common mistakes
Setting the no-identifier flag across the whole catalogue. Inventing or reusing codes to clear the warning. Fixing items in a feed rule while the store record stays empty. Storing brand as a tag the export ignores. Ordering fixes alphabetically instead of by revenue. Treating a limited item as healthy because it is not disapproved.
