Skip to content

Public preview · Free feed checks are available. Paid reports and downloads are not available yet.

How to review missing brand in a Google Shopping feed

Brand requirements depend on product identifiers and category. Submit the actual product brand when it exists; do not substitute a reseller name merely to remove a warning.

Reviewed October 4, 2026 · Independent guidance · Static feed check with contextual limitations

What does this issue mean?

The brand attribute describes the product’s brand, not necessarily the company that sells it. A merchant offering several manufacturers should not map every row to its own store name. Identifier matching can become inconsistent when a real GTIN is paired with the wrong brand, even if every field is syntactically populated.

Why this happens

Common causes include a supplier manufacturer column that was not mapped, a platform vendor field that actually describes your wholesaler, or a parent product’s brand failing to reach variant rows. Custom products can require a different treatment, so inspect the offer rather than applying the same placeholder to the entire catalog.

How to diagnose and fix it

  1. Identify whether the item has a real manufacturer brand and confirm it against packaging or supplier documentation.
  2. Inspect the source column used by your feed integration; a vendor, seller or supplier column may not mean brand.
  3. Populate the actual brand consistently across the relevant variants and review its relationship with GTIN and MPN.
  4. For your own manufactured or genuinely unbranded products, follow Google’s identifier guidance instead of inserting Generic or N/A.

Before and after example

The examples are illustrative. Replace them with verified information for your own offer; copying an example identifier, amount or URL would introduce incorrect data.

Before

id,brand,gtin
SHIRT-M,,4006381333931

After review

id,brand,gtin
SHIRT-M,Northline,4006381333931

The example is fictional. Feed Doctor reports missing brand as a contextual warning; it cannot determine the true manufacturer from a file or certify that a supplied brand matches a barcode.

Shopify fix

Find the affected product and exact variant in your Shopify catalog, then identify which product field or Google & YouTube channel setting supplies brand. If a separate feed app generates your export, inspect its mapping instead of assuming the channel settings control that file. Change verified source data, save it, and obtain a fresh export.

Compare one affected variant and one previously correct offer before making a bulk change. Do not change stable IDs just to improve a report score. If the issue involves identifiers, verify whether the connector reads barcode, brand or manufacturer reference data. If it concerns a live page or shipping account setting, a feed-column edit alone may not resolve it.

WooCommerce fix

Open the relevant product or variation and inspect the attribute consumed by your Google feed integration. Google for WooCommerce can map product attributes into feed attributes; third-party feed generators may use different mappings. Check both the stored value and the exported result, especially when parent attributes are inherited by variations.

Update the source value or mapping deliberately and regenerate the feed. Keep product identity, currency and variant relationships consistent. Avoid editing only a downloaded snapshot if a scheduled exporter will replace that change. For an account or website issue, repair the effective configuration and public offer as well as reviewing the file.

Verify the repair before submitting

Keep the original feed as a backup and compare the same affected product IDs in the regenerated file. Confirm that the expected product count remains unchanged and that no unrelated fields disappeared. If you applied a bulk rule, inspect offers outside the original affected set as a control; an overly broad mapping can fix one problem while creating another.

Run a new static scan, then separately check live product information and your Merchant Center diagnostics. File format validation cannot determine every policy, account, image or website condition. Processing and recrawling take place in Google’s systems, so a corrected file is not an immediate promise of approval. Use the actual updated diagnostics to decide whether additional investigation is required.

Scan your feed for this issue

Check all parsed products in an XML, CSV or TSV feed. Preview the score and issue samples free; unlock affected-product details and downloadable reports with a one-time payment. Conditional findings remain marked for review.

Check My Feed

Frequently asked questions

Does this finding always mean my product is disapproved?

The example is fictional. Feed Doctor reports missing brand as a contextual warning; it cannot determine the true manufacturer from a file or certify that a supplied brand matches a barcode.

Can Feed Doctor fix brand automatically?

Only deterministic formatting changes are available in Fix & Export. Missing identifiers, prices, business facts and ambiguous values require manual action. Review every change and remaining finding before submitting a repaired feed.

Should I fix the exported file or my store?

Correct the source product or feed integration whenever possible. A downloaded file edit may be overwritten by the next scheduled export. Keep a backup and compare the exact affected IDs in a fresh feed snapshot.

Do I need to connect Google to scan a feed?

No. Feed Doctor accepts a Google-format XML, CSV or TSV file, or a public HTTPS feed URL. It checks the feed without accessing your Merchant Center account. Reports are private to your browser and expire after 7 days.

Related feed issues

Official references: Google product data specification, Shopify Google & YouTube requirements, WooCommerce attribute mapping. Requirements can vary by product, country and account setup.