Identifiers — GTIN, brand, MPN
identifier_exists
feed attribute: identifier_exists
A flag that must match what you actually submit: true or false, never 'no', '0' or 'N/A'.
Google Merchant Center
Optional attribute, but the value has to be true or false and has to agree with the identifiers you submit.
Meta
Meta builds identifiers from the GTIN, brand and MPN columns it is given; it has no equivalent flag.
What the requirement says
- identifier_exists indicates whether the unique product identifiers (GTIN, MPN and brand) are available for your product. Accepted values are true and false.
- Submit false only for products that genuinely have no GTIN, no brand and no MPN — custom or made-to-order goods.
- If you submit a GTIN, brand or MPN for the item, identifier_exists has to be true (or omitted, which means the same thing).
Why products lose visibility when it fails
- Submitting identifiers while claiming identifier_exists = "false" contradicts itself, and that inconsistency is what gets flagged.
- Values like "no", "0", "N/A" or "FALSE " (with a space or different case) are not one of the two accepted values.
- A false flag on a product that does have a barcode hides the identifiers the platform could have used to match it.
The checks we run on it
Straight from the audit engine, with the basis each one is judged on. “Commonly suppresses” means the failure is the kind that stops a product serving, so it is weighted more heavily in your score.
| Check | Basis | Requirement | What to do |
|---|---|---|---|
identifier_exists conflicts with the identifiers importantidentifier_exists_invalid | required in some cases | Identifier_exists must be true or false and must match the identifiers you submit. | Set identifier_exists to "false" only for products that genuinely have no GTIN, brand or MPN. |
Want to know which of your own products fail this requirement?
Audit my identifier exists free →How to fix it in Shopify
- Shopify's public catalogue does not publish identifier_exists, so a store scan cannot judge it — this check runs on a feed URL or an uploaded CSV.
- In a Google Shopping feed app, identifier_exists is usually a per-product or per-collection mapping; set it to false only for custom goods.
- If you build your own feed, include the column and leave it blank for products that have identifiers.
How to fix it in WooCommerce
- Feed plugins (Product Feed PRO, CTX Feed and similar) expose identifier_exists as a column you can set per product, per category or with a rule.
- Default it to true, then override it to false for the categories that genuinely have no barcodes or brands.
Worth knowing
- The value is case-sensitive in practice at some destinations: use lowercase true / false.
How FeedGuard checks it
- We look at what the item actually submits: a GTIN, brand or MPN alongside identifier_exists = false is a contradiction, and any value other than true or false is reported as an unrecognised value.
- A store scan cannot see this attribute at all, so the check only runs on a feed URL or an uploaded CSV.
Every failure names the field and shows the value at fault, counted over up to 250 products per scan. A requirement that does not apply to an item is left out of both sides of the score rather than counted as a pass, and a requirement our source cannot see at all is excluded from the score and listed as “not checked from this source” with the reason. Where a value can be corrected without inventing anything, the row is fixed in the corrected CSV you can download; anything we would have to make up (a real barcode, a brand, a price, a category) is listed for you to supply instead.
What each kind of scan can see
A store scan reads the public catalogue the store itself publishes (Shopify's /products.json). A pasted feed URL or an uploaded CSV is the file the shopping platform reads, so every attribute can be judged against it. This is the difference that decides whether a check can run at all.
| Attribute | Store scan (Shopify) | Your feed URL or CSV upload |
|---|---|---|
| identifier_exists | not published — check skipped Shopify's public catalogue does not publish identifier_exists, so we cannot tell whether your feed submits it. | read from your file read from your file |
A store scan cannot see identifier_exists — this check is skipped there and excluded from the score.
Shopify's public catalogue does not publish identifier_exists, so we cannot tell whether your feed submits it.
Paste your feed URL or upload your CSV to have it checked.
Read the engine's own rules for this requirement on the results page: every failing row links back to this guide. All 49 checks are listed on what we check.
Run the free audit on your store
Paste your store domain, paste your product feed URL, or upload a product CSV. You get a scored report of every requirement above, the products failing each one, the exact fields at fault, and a corrected CSV to download. No account, no card.
Run the free audit on your storeA store scan reads the public catalogue and skips the attributes it cannot see (listed above); a feed URL or CSV gets the full audit.
Other identifiers — gtin, brand, mpn requirements
- GTIN / barcode
If your product has a manufacturer barcode, submit it — correctly, digits only, and only once per product.
- Brand
Required for new products: the brand shoppers recognise, not your own storefront name.
- MPN (manufacturer part number)
Required when the product has no manufacturer-assigned GTIN — a SKU is usually not a part number.