Merchant Center brand errors: missing, incorrect, and inconsistent values

Brand works with GTIN and MPN to help identify a product. For a widely manufactured item, use the actual brand associated with the product—not the merchant name simply because the merchant sells it. Google's current documentation explains exceptions for products without a conventional brand and for custom-made products.

A missing-brand issue does not mean every catalog item should receive a fabricated label. The correct response depends on whether a brand genuinely exists.

Brand data is often present in a commerce platform but lost or altered during export.

• The feed mapping uses vendor, supplier, or store name instead of product brand.
• Child variants omit a value stored on the parent.
• Whitespace, abbreviations, or localization create inconsistent variants.
• A marketplace export substitutes the seller name.
• Custom products are handled as mass-manufactured products, or vice versa.
• GTIN, MPN, and brand describe different products.

Use packaging, the manufacturer's catalog, or verified internal product data. Check the exact model and every variant. Compare brand, GTIN, and MPN together, then inspect the source mapping and Merchant processed values. A landing page can provide supporting context but should not override authoritative identifier data.

Correct the catalog or feed rule that first introduces the wrong value. Make parent-to-variant inheritance explicit, keep spelling consistent, and avoid changing stable product IDs. Resynchronize and verify Google's processed product before considering the issue resolved.

CommerceVigil groups direct Merchant brand and identifier issues and tracks their lifecycle. It can show affected products and supported traffic context, but it cannot establish trademark ownership, manufacture a missing brand, or edit the source catalog.