# Missing GTIN: when to use identifier_exists in Google feeds

> Decide whether a missing GTIN is unknown or genuinely unassigned. Use six worked cases and an evidence worksheet before changing identifier_exists.

By George Kelly · Published 2026-10-17 · Updated 2026-10-17

Publication: iamgeorgekelly (https://www.iamgeorgekelly.com)

Canonical: https://www.iamgeorgekelly.com/field-guide/missing-gtin-identifier-exists

## Short answer

A blank GTIN does not establish that a product has no identifiers. Investigate the exact item first. For Google feeds, use identifier_exists=no or false only when you are certain that no unique product identifiers are assigned. If assignment is unresolved, hold the decision instead of inventing a code or an exemption.

## Put this guide to work

[Choose the next action](https://www.iamgeorgekelly.com/field-guide/missing-gtin-identifier-exists#decision-table)

[Get the evidence worksheet](https://www.iamgeorgekelly.com/field-guide/missing-gtin-identifier-exists#evidence-worksheet)

## What does a missing GTIN actually tell you?

An empty supplier field records a gap in that file. It does not tell you whether the manufacturer assigned an identifier elsewhere. A useful review separates unknown assignment, documented absence, a confirmed assignment, and conflicting evidence.

Google says to provide a GTIN only when you are sure it is correct. Do not guess a value. Check the exact variant; a code for another color, size, or pack does not resolve your record. The existing identifier guide explains SKU, GTIN, and parent-group differences.

Next step: [Understand SKU, GTIN, and variant identity](https://www.iamgeorgekelly.com/field-guide/product-identifiers-sku-gtin-variants) — Resolve what each field identifies before deciding how to handle a missing value.

Sources: [Google Merchant Center: GTIN](https://support.google.com/merchants/answer/6324461?hl=en)

## Choose the next action from the evidence

This is an original internal review method, not a Google approval algorithm. “Hold” pauses an unsupported mapping decision; it is not a Merchant Center status or an instruction to remove an existing listing. Every path still needs the applicable destination checks.

| Evidence state | Next action | Keep unresolved |
| --- | --- | --- |
| Only a blank export or a failed lookup | Hold; ask the source owner for exact-item evidence | Whether an identifier was assigned |
| Confirmed assignment for this selection | Retrieve and review that identifier | Any remaining format or destination issues |
| Confirmed no GTIN; documented brand and MPN | Review the brand/MPN route | Do not equate no GTIN with no identifiers |
| Confirmed no assigned unique identifiers | Review identifier_exists=no or false | Other product and destination requirements |
| Two sources disagree or identify different variants | Hold; reconcile the disagreement | Do not select whichever value passes a checksum |

Sources: [Google Merchant Center: Identifier exists](https://support.google.com/merchants/answer/6324478?hl=en); [Google Merchant Center: MPN](https://support.google.com/merchants/answer/6324482?hl=en)

## When is identifier_exists=no appropriate?

Google reserves no or false for products that have no assigned unique product identifiers. Missing data in your system is not enough. Text and XML sources accept yes, true, no, or false; Merchant API sources use Boolean true or false. Confirm the format at the destination adapter.

Google’s MPN guidance requires an MPN for products without a manufacturer-assigned GTIN, with exceptions such as custom-made products or products without a clearly associated MPN. Use the manufacturer’s part number when established; a reseller should not invent one. Review known brand and MPN evidence before declaring all identifiers absent.

Sources: [Google Merchant Center: Identifier exists](https://support.google.com/merchants/answer/6324478?hl=en); [Google Merchant Center: MPN](https://support.google.com/merchants/answer/6324482?hl=en)

## Six cases for a reviewer or an agent

All cases below are fictional teaching examples. The decisions describe the next review step, not upload readiness. Numeric GTINs are deliberately omitted so that a teaching identifier cannot be mistaken for a product assignment.

| Case | Evidence | Next review step |
| --- | --- | --- |
| G1 · Supplier export has a blank GTIN | Only the export was checked. The manufacturer has not answered. | Request evidence for the exact item; leave identifier_exists unresolved. |
| G2 · No assigned GTIN; manufacturer part is documented | Fictional manufacturer confirms no GTIN for DEMO-MUG-BLUE and documents brand Example Workshop and MPN DEMO-350-B. | Map the documented brand and MPN under applicable destination rules. Do not classify all identifiers as absent. |
| G3 · One-off object with no assigned identifiers | Fictional maker confirms this new, one-off object has no assigned GTIN, MPN, or brand. | Review no/false for identifier_exists, retain evidence, and check all remaining destination requirements. |
| G4 · Candidate code belongs to a different variant | Supplier identifies the candidate as the white mug; the target is the blue mug. No actual GTIN is included in this example. | Resolve the conflicting selection; do not borrow the sibling code or declare identifiers absent. |
| G5 · Exact item assignment is documented | Fictional manufacturer assignment record matches the item, variant, and pack. Numeric GTIN intentionally omitted from this teaching case. | Retrieve the documented string and validate formatting before mapping; this fixture contains no submittable GTIN. |
| G6 · Personalization is mistaken for absence | A fictional engraved standard mug retains a documented base-product GTIN assignment. Numeric code omitted. | Review Google customization guidance and the underlying assignment; handmade or personalized wording alone does not establish absence. |

[Download the evidence template and six fictional cases (JSON)](https://www.iamgeorgekelly.com/downloads/missing-gtin-review.json)

Sources: [Google Merchant Center: GTIN](https://support.google.com/merchants/answer/6324461?hl=en); [Google Merchant Center: Identifier exists](https://support.google.com/merchants/answer/6324478?hl=en); [Google Merchant Center: MPN](https://support.google.com/merchants/answer/6324482?hl=en)

## Keep the decision attached to its evidence

Create one review record for one sellable selection. Keep the original export beside the record, with its extraction time. Save a source URL or document reference, the relevant passage, the item it describes, and who reviewed it. A supplier statement about an entire range may not settle a particular variant.

The worksheet has a blank template and a filled fictional example. Its null values mean unresolved or not recorded, never false. These internal records are not Google feed rows, Merchant API requests, or inputs for the site’s product-record checker. Review them manually or adapt them to your own authorized workflow.

- Identify the merchant item, manufacturer, variant options, and pack quantity.
- Record GTIN assignment and MPN assignment separately; retain brand evidence.
- Preserve conflicting observations instead of overwriting one with the other.
- Name the next action, owner, reviewer, and the evidence needed to close the hold.
- Record the approved mapping separately from the destination response and its timestamp.

[Download the editable review worksheet (Markdown)](https://www.iamgeorgekelly.com/downloads/missing-gtin-worksheet.md)

## What can an agent prepare safely?

Give the agent a bounded task: inventory the supplied evidence, identify gaps, and propose a review decision with source references. Require it to preserve unknowns. It should not infer absence from an empty field, generate a plausible identifier, or silently rewrite a disputed assignment.

A reviewer resolves the evidence and approves the destination mapping. After an authorized submission, retain the actual response and inspect the exact product. Separate evidence quality, mapping approval, and provider acceptance in the record; completing one stage does not complete the others.

Next step: [Assign ownership of the missing evidence](https://www.iamgeorgekelly.com/field-guide/product-data-ownership) — The hold needs a source owner and a concrete resolution task.

Next step: [Check the exact variant after mapping](https://www.iamgeorgekelly.com/field-guide/product-variant-acceptance-test) — A resolved identity still needs to match the destination offer.

## Avoid category shortcuts

Personalizing a standard product is not proof that its original identifier disappears. Google documents using the manufacturer-assigned GTIN for customization and has separate rules for bundles and multipacks. Review those cases directly rather than applying a blanket “custom product” exemption.

This guide covers an evidence review for Google product feeds. It does not grant exemptions in another marketplace, assign identifiers, or certify eligibility. The worksheet is useful because it makes the unanswered question and next owner visible.

Sources: [Google Merchant Center: GTIN](https://support.google.com/merchants/answer/6324461?hl=en)

## Sources and scope

- [Google Merchant Center: GTIN](https://support.google.com/merchants/answer/6324461?hl=en) — Supports using the correct assigned GTIN, withholding uncertain values, and treating variants and customization carefully. Checked 2026-10-17.

- [Google Merchant Center: Identifier exists](https://support.google.com/merchants/answer/6324478?hl=en) — Supports using no or false only when the product has no assigned unique product identifiers; documents source-specific Boolean formats. Checked 2026-10-17.

- [Google Merchant Center: MPN](https://support.google.com/merchants/answer/6324482?hl=en) — Supports manufacturer-assigned part numbers, the no-GTIN requirement and its exceptions, and not inventing an MPN. Checked 2026-10-17.

## Related reading

- [SKU vs GTIN: differences, barcodes, and variant IDs](https://www.iamgeorgekelly.com/field-guide/product-identifiers-sku-gtin-variants/index.md)

- [Product data ownership: resolve a price conflict](https://www.iamgeorgekelly.com/field-guide/product-data-ownership/index.md)

- [Why a product feed check can pass while the records disagree](https://www.iamgeorgekelly.com/field-guide/product-data-conflict-casebook/index.md)

- [Does the product page match the variant you submitted?](https://www.iamgeorgekelly.com/field-guide/product-variant-acceptance-test/index.md)

## Cite this guide

George Kelly. Missing GTIN: when to use identifier_exists in Google feeds iamgeorgekelly. Updated 2026-10-17. https://www.iamgeorgekelly.com/field-guide/missing-gtin-identifier-exists

Library navigation: [Choose a task](https://www.iamgeorgekelly.com/field-guide/start-here) · [Source directory](https://www.iamgeorgekelly.com/field-guide/sources) · [Editorial policy](https://www.iamgeorgekelly.com/for-agents#editorial-policy)

## Editorial note

AI-assisted research and drafting. Provider-specific claims link to primary sources. Frameworks are editorial proposals; worked examples are illustrative and are not employer performance results.