Google Product Feed Field Reference

How Default Mappings Work

The Google product feed uses a data-driven mapping system to transform B2C Commerce product data into the format required by Google. When the system can derive a value using standard B2C Commerce attributes, it creates a default mapping that specifies how the value is derived:

• Field mappings: Map directly to a single B2C Commerce product attribute, such as name, brand, or price.
• Derived mappings: Calculate values from multiple attributes or apply transformations, such as stripping HTML from descriptions or formatting prices with currency codes.
• Constant mappings: Use a fixed value for all products.
• Fallback mappings: Map to the primary attribute first, then fall back to an alternative if the primary attribute is empty for that product. For example, title uses name, falling back to masterProductName if name is blank.

You can customize fields marked as Overridable: Yes in Business Manager. Fields marked as Overridable: No are system-managed and visible in the Field Mapping table, but you can't change their mappings.

Automatic Field Formatting

The system applies automatic formatting to field values before they are written to the feed. This formatting happens regardless of whether you keep the default mapping or override it with a different attribute. When you override a default mapping, you don't need to adapt your catalog data to match Google's format—the system handles the transformation.

Formatting applies as follows:

• Dates: Date and datetime values are formatted to ISO 8601. Invalid dates are omitted from the feed.
• Booleans: Values are converted to true or false.
• Numbers: Numeric values are formatted to the required precision (for example, integers with no decimals, or two decimal places for prices). Invalid or null values are omitted.
• Prices: Positive values are formatted to two decimal places and concatenated with the currency code.
• Descriptions: HTML tags are stripped from text.
• Enums: Values such as availability and age_group are validated against predefined allowed values.

Custom Attribute Inheritance for Variants

When you map a custom attribute to a Google field, the system automatically resolves attribute values for variant products using the following inheritance chain:

1. Variant product: The system first checks the variant product for the attribute value.
2. Variation group: If the variant doesn't have the attribute value, the system checks the variation group (if applicable).
3. Master product: If the variation group doesn't have the value, the system checks the master product.

This inheritance chain ensures that custom attributes defined at the master or variation group level are automatically inherited by variants without requiring duplicate data entry.

Product Eligibility

Two layers control which products appear in the feed:

• Product filter rules: Configurable include and exclude rules that determine which products are sent to Google. By default, the rules match products that are online and searchable, but you can adjust them. See Product Filter Rules for the Google Product Feed.
• Automatic exclusions: Regardless of your filter rules, the system always excludes the following from the feed:
  • Master products (variants are exported instead)
  • Variation groups (variants are exported instead)
  • Product sets. Bundles, which have fixed components, are supported and are sent to Google as standalone products.

After a product is included in the feed, you can further control where it appears in Google by mapping the included_destination, excluded_destination, and pause fields. For example, use excluded_destination to keep a product out of Shopping ads while still submitting it to free listings. See the Optional Fields table.

List Price Derivation

The price field maps to the regular (list) price of a product. B2C Commerce doesn't have a built-in "list price" concept; storefront teams implement list pricing using different price book strategies. To accommodate this variety, the system derives the list price for the feed in two steps:

1. Selected list price book. If you select a price book in List Price Book on the General Settings tab, the system uses the price from that price book. The dropdown contains only price books that are active and contain prices in the feed currency. If you later deactivate the selected price book, reconfigure List Price Book to point at a different price book.
2. Sale price book pathway. If you don't select a list price book, the system derives the list price from the sale price book that the B2C Commerce price engine selects for the product. The price engine evaluates all applicable price books for the product, not only active ones, and returns the best (lowest) price along with its source price book. From that sale price book, the system applies one of two rules:
   • If the sale price book has a parent price book, the system walks the parent chain to the root and returns the price from the root price book. This matches the default behavior of SFRA and SiteGenesis storefronts.
   • If the sale price book has no parent, the system returns the maximum price across all applicable price books for the product. This matches the default behavior of PWA Kit storefronts.

Note If the resolved list price equals the sale price, the system populates only the price field and omits sale_price from that product's feed entry. This avoids showing a strike-through price in Google for products that aren't on sale.

Setting List Price Book on the General Settings tab is the most reliable way to ensure the list price in your feed matches what shoppers see on your storefront, particularly for storefronts with custom pricing logic, zone-based pricing, or multi-currency price books.

Sale Price Derivation

The sale_price field maps to the B2C Commerce salePrice attribute plus the configured currency. The salePrice value isn't taken from a single price book—the B2C Commerce price engine selects the best (lowest) price among all applicable price books for the product, regardless of price book hierarchy or whether a hierarchy is configured.

Because the same engine populates the price your storefront displays, the sale_price value sent to Google matches what shoppers see on your site.

If the resolved sale price equals the resolved list price (the price field), the system omits sale_price from that product's feed entry. This avoids showing a strike-through price in Google for products that aren't on sale. See List Price Derivation.

If your storefront uses custom pricing logic—such as zone-based or geo-based price book selection—the default sale price calculation may not match what shoppers see. Setting List Price Book on the General Settings tab is the most reliable way to align the feed with your storefront in these cases.

Required Fields

The following fields are required for a valid product feed entry. Products that are missing required fields are still included in the feed, but Google may reject those individual rows. Use the Product Feed Preview to identify products with missing required fields and fix them before you turn on the daily feed sync. See Preview the Google Product Feed.

Warning If more than 30% of your products are missing required fields, Google may reject the entire feed. Ensure your catalog data is complete before you turn on the daily feed sync.

Optional Fields

The following fields are optional and can enhance your product listings in Google. Optional fields are omitted from the feed when the mapped attribute or constant value is blank. Fields with a default mapping derive their value automatically; fields without a default mapping (shown as "(none)") are populated only when you map an attribute or set a constant value or pattern.

Additional Optional Fields (Product Detail)

Use the Additional Optional Fields section of the Field Mapping table to send technical specifications or other attributes to Google's product_detail field. For each entry, map a B2C Commerce attribute and, optionally, provide a section name to group related details. Click Add Attribute to add another product detail.

The product_detail field gives shoppers readable, structured information about aspects of a product that other fields don't cover, and it helps Google surface your products across search and AI-driven experiences. For the full list of accepted attributes and formatting requirements, see Product detail [product_detail] in Google Merchant Center Help.