Skip to content
feedlab Request early access

Feed error

Warning

Missing value: brand

The "Missing value: brand" issue means a channel expects a brand name for a product and the feed did not supply one, or supplied a placeholder it treats as empty. On Shopify it usually means the vendor field is blank, or holds a supplier or internal category rather than the brand a shopper would recognise.

How this appears in your account

The exact wording the channel shows, so you can match what you are looking at.

What it affects

Channels
Google Shopping Microsoft Advertising OpenAI
Attributes
brand mpn identifier_exists
Scope
A subset of items

Why it happens on Shopify

The Shopify vendor field is empty

Vendor is optional and is frequently left blank on products created by hand or imported without a brand column, which leaves the mapped brand attribute empty.

Vendor holds a supplier rather than a brand

Many stores use vendor operationally, recording the wholesaler or distributor they buy from. That value is real but it is not the brand, so it either misidentifies the product or is rejected as meaningless.

A placeholder was submitted

Values such as "Generic", "N/A", "None", "Unbranded" or a single hyphen are treated as missing rather than as a declaration that no brand exists.

The product genuinely has no brand

Unbranded commodity goods and some handmade items have no brand in any meaningful sense, and the feed needs to say so through identifier_exists rather than inventing a value.

How to fix it

  1. Audit what the vendor field actually contains

    List the distinct vendor values across the catalogue. This is usually a short list, and it immediately shows whether vendor holds real brands, supplier names, or a mixture of both.

  2. Map vendor values to real brand names

    Where vendor holds supplier names, a lookup table translating each one to the correct consumer-facing brand is more reliable than mapping the field directly, and it keeps working as products are added.

  3. Use a metafield where the brand is recorded properly

    Stores that already track brand in a product metafield should map from there instead. It is purpose-built for the job and not subject to operational reuse the way vendor is.

  4. Use your own brand for own-brand goods

    Products you manufacture or sell under your own label should carry your store's brand name. This is correct rather than a workaround, and it makes the items eligible for brand-based matching.

  5. Declare identifier_exists as no for genuinely unbranded products

    For commodity goods with no brand and no manufacturer identifier, the honest declaration is identifier_exists set to no. Never substitute a placeholder such as "Generic", which counts as missing anyway.

How feedlab handles this

feedlab can source brand from the vendor field, a metafield, a static value, or a lookup table that translates vendor values into brand names, with a conditional fallback chain across them. The preview resolves the mapping against real products, so gaps show up before the feed is published rather than in Merchant Center afterwards.

Frequently asked questions

Can I put "Generic" in the brand field?

No. Channels treat Generic, N/A, None, Unbranded and similar placeholders as missing values, so it does not resolve the issue. For products that genuinely have no brand, declare identifier_exists as no instead.

Should brand come from the Shopify vendor field?

Only if vendor actually holds brand names in your store. It is free text with no validation and is commonly used for suppliers or internal groupings, so audit the distinct values before mapping it directly.

Which products are exempt from needing a brand?

Google exempts movies, books and musical recordings, which are identified by GTIN or ISBN. Everything else is expected to carry a brand where one exists.

Primary sources

Channel specifications change. These are the official documents this page is based on.

Last reviewed View as markdown