Color is the product feed attribute that names the color of an item, submitted as g:color in an XML feed or as a color column in a CSV/TSV upload to Google Shopping, Meta Catalog, and most marketplaces. It's one of a short list of attributes these platforms recognize specifically for building product variants, so when a jacket comes in five colorways, color is what tells the feed — and the shopper — which entry is which underneath a shared item group. The value is a plain, human-readable color name rather than a hex code, a swatch ID, or internal merchandising shorthand.

Why it matters

Google Merchant Center requires color on any item that belongs to a variant group defined by item_group_id when color is one of the dimensions that differs across those variants — skip it, or use inconsistent values like "Navy" on one row and "Navy Blue" on its sibling, and Google can reject the items, fail to merge them into a single variant listing, or show a color swatch that doesn't match the product photo. Meta Catalog applies the same logic for dynamic ads and shop grids: without a clean color value, the catalog can't generate the color-filter chips shoppers use to narrow a search, and dynamic remarketing ads may show the wrong colorway to someone who viewed a different one. Because color is also a customer-facing merchandising signal, sloppy values here erode trust in the listing itself, not just the feed's technical health.

How it works

The color field takes free text, not a controlled vocabulary, though Google's guidance is to use common, recognizable names ("Red," "Charcoal") rather than proprietary or seasonal collection names a shopper wouldn't search for. When a single item genuinely combines colors, Google allows up to three values in one field separated by a slash, such as "Black/White," with the dominant color listed first. Color is required for the Apparel & Accessories category whenever variants exist, and it's one of the attributes — alongside size, pattern, material, gender, and age group — that Google explicitly permits as a basis for grouping rows under one item_group_id. If color is the only thing distinguishing two otherwise identical listings, it must be present and different on each row, or the platform has no way to justify treating them as separate variants of the same product.

Example

<item>
  <g:id>JKT-4471-BLK</g:id>
  <title>Waxed Cotton Field Jacket - Black, M</title>
  <link>https://example-shop.com/products/waxed-field-jacket-black-m</link>
  <g:item_group_id>JKT-4471</g:item_group_id>
  <g:color>Black</g:color>
  <g:size>M</g:size>
  <g:price>168.00 USD</g:price>
  <g:availability>in stock</g:availability>
</item>
<item>
  <g:id>JKT-4471-OLV</g:id>
  <title>Waxed Cotton Field Jacket - Olive, M</title>
  <link>https://example-shop.com/products/waxed-field-jacket-olive-m</link>
  <g:item_group_id>JKT-4471</g:item_group_id>
  <g:color>Olive</g:color>
  <g:size>M</g:size>
  <g:price>168.00 USD</g:price>
  <g:availability>in stock</g:availability>
</item>

Both rows share the same item_group_id, so Google and Meta treat them as color variants of one product rather than two unrelated listings — the color field is the only thing telling either platform which is which.

Related Concepts

Color rarely does its job alone: it's almost always paired with size on apparel items, and both depend on a correctly shared item group ID to actually form a variant set instead of a pile of duplicate-looking rows. Retailers restructuring a catalog around this pattern for the first time can walk through the mechanics in The Complete Guide to Product Variant Feeds.