Skip to content
Commerce Fieldbook
Fieldbook/Catalog and product pages

Our feed and product page disagree

Find the field, variant, source, and timestamp behind a product-data mismatch.

stableintermediateReviewed 2026-07-25

A feed mismatch is rarely store-wide. Price may come from one transform, availability from another, and images or shipping rules from somewhere else entirely.

Typical symptoms

  • A channel rejects products that look correct in the commerce platform.
  • Price or availability differs between catalog, page, markup, and feed.
  • Search or AI tools repeat old product details.
  • Only certain variants, languages, or markets are affected.

What to capture

Collect the catalog record, rendered page, structured data, feed row or channel diagnostic, product and variant identifiers, market, currency, and timestamp.

Don't assume

The newest-looking value is not necessarily the approved value. Find the owner or system of record for the field before changing it.

Steps

  1. Put each field side by side for the affected product and variant.
  2. Trace every value to its source and transforms.
  3. Check sync delays, theme output, localization, and market rules.
  4. Fix the approved source value or the transform that changed it.
  5. Regenerate the feed or wait for the documented refresh.
  6. Check the page and channel diagnostic separately.

Done when

  • Product and variant identifiers match.
  • Price and availability agree for the same market and time.
  • Visible content matches structured data.
  • The channel has processed the corrected data.

Related pages

Keep working on this issue