identifier_exists With a GTIN: What to Set for brand

A common point of confusion in product feed management is what happens when a product carries a valid GTIN but lacks a brand value. Should identifier_exists be set to true or false? And does Merchant Center require the brand attribute in that scenario? This article works through the exact requirements from Google's documentation so you can set both attributes correctly.

What identifier_exists Actually Controls

The identifier_exists attribute tells Merchant Center whether any unique product identifier (UPI) exists for a product. Unique product identifiers are submitted using the gtin, mpn, and brand attributes together—they are not three independent signals but a combined set of UPIs.

According to Google documentation, identifier_exists is "Recommended for products that don't have a GTIN [gtin], MPN [mpn], or brand [brand]." The use case for setting this attribute to no or false is specifically when a product has no assigned identifiers at all—not when one of the three is missing while others are present.

If your product has a valid, manufacturer-assigned GTIN, that product has a unique product identifier. Setting identifier_exists to false in that situation is incorrect. The Google documentation is explicit: "Products for which the identifier exists [identifier_exists] attribute is incorrectly set to no [no] or false [false] and for which there is evidence that a unique product identifier exists, will receive a warning."

In plain terms: if a GTIN is present and valid, set identifier_exists to true (or omit the attribute, since true is the default assumed state when identifiers are present).

What Merchant Center Requires for the brand Attribute When a GTIN Is Present

Having a GTIN does not automatically satisfy all identifier requirements on its own. The GTIN documentation states that merchants should "Submit any other relevant unique product identifiers. You might be required to submit the brand [brand] and MPN [mpn] attributes," according to Google documentation.

This matters because Merchant Center uses the combination of gtin, brand, and mpn to understand and classify what you are selling. The documentation explains the reasoning directly: "When we understand what you're selling, we can make your ads and unpaid listings richer and help connect customers to your products."

So, when a product does have a GTIN:

• Set identifier_exists to true (or leave it at the default).
• Supply the brand attribute if the product was made by an identifiable manufacturer. This is not optional in all categories—Merchant Center may require it depending on product type.
• Supply mpn where you have it, particularly for products in categories where part numbers are standard.

Leaving brand blank while submitting a valid GTIN is not the same as having no identifiers at all. The product still has a UPI (the GTIN), so identifier_exists must remain true. The missing brand value is a separate completeness issue that may affect product classification and listing richness—it does not change the identifier_exists value.

When It Is Correct to Set identifier_exists to false

The identifier_exists = false (or no) path is reserved for a specific category of products. Per Google documentation, "If your product is new (which you submit using the condition [condition] attribute) and it doesn't have assigned product identifiers that meet the requirements below, you should submit the identifier exists [identifier_exists] attribute with a value of no [no] or false [false]."

The documentation lists examples such as custom goods, handmade products, and items produced before GTINs were introduced (such as antiques or books published before 1970). In those cases, all three UPI attributes—gtin, mpn, and brand—are unavailable or not assigned by a manufacturer.

For such products, the correct feed configuration is:

• identifier_exists: no
• gtin: leave blank
• mpn: leave blank
• brand: leave blank (or set to your own store/maker name only if genuinely applicable)

Note that the value must be submitted in English regardless of your feed's target locale.

Hypothetical Example: A Branded Electronic Accessory With a Known GTIN but Brand Field Left Empty

The following is a hypothetical example for illustration only. Values are invented.

Imagine a feed manager is uploading a batch of third-party USB hubs. Each hub has a manufacturer-assigned GTIN (e.g., a 12-digit UPC such as 012345678901), but the brand field was inadvertently left blank during the catalog import. The manager considers setting identifier_exists to false to suppress the warning about missing brand data.

This would be the wrong approach. The product has a valid GTIN, which is itself a unique product identifier. Setting identifier_exists to false would trigger a warning from Merchant Center because there is evidence that a UPI exists. The correct fix is:

1. Keep identifier_exists at true (or omit it).
2. Populate the brand attribute with the manufacturer's name (e.g., "Acme Peripherals").
3. Add mpn if the product has a part number.

Supplying the correct brand value resolves the completeness gap without misrepresenting the product's identifier status. Do not attempt to work around a missing brand value by flipping identifier_exists to false—they address different things.

Practical Checklist for Feed Operators

Before submitting or auditing a feed, run through this quick check for each product:

For feed operators managing large catalogs, attribute errors in identifier_exists and brand often originate during the import stage—particularly when source data has inconsistent manufacturer information. Magicfeedpro is designed to help merchants map, validate, and clean these fields during catalog import so that the correct values reach your destination feed.

If you are dealing with broader Merchant Center attribute issues, the merchant center errors guide covers additional diagnostic steps for common feed problems.

Key Takeaway

A product with a valid GTIN has a unique product identifier. That means identifier_exists must be true. A missing brand value is a completeness problem, not a reason to set identifier_exists to false. Fix the brand field separately, and supply mpn where available. Reserve identifier_exists = false only for products that genuinely have no manufacturer-assigned GTIN, MPN, or brand.

Related articles

merchant center

Tax Attribute in Google Shopping Feeds: Format and When to Submit

Learn when to include the tax attribute in your product feed and how to format country, region, rate, and tax_ship sub-attributes correctly.

Nov 6, 2026·6 min

merchant center

identifier_exists False: What to Submit and When It Backfires

When to set identifier_exists to false in your product feed, what companion attributes you still need, and what causes its own disapproval.

Nov 5, 2026·5 min

merchant center

MPN Attribute in Product Feeds: Rules When There Is No GTIN

Learn when the mpn attribute is required, how to format it correctly, and what to submit when a product has no GTIN.

Oct 12, 2026·6 min