Feed-to-PDP parity playbook
Bring catalog, storefront, feed, and channel owners together to resolve conflicting product data.
Who does this: Coordinates the catalog, storefront, feed, and channel owners listed below. Your job is to make sure each one is assigned.
Reviewed 2026-07-25
Choose this playbook when the contradiction crosses team or system boundaries.
Owners
- Catalog: confirms the approved product and variant values.
- Storefront: checks visible content and structured data.
- Feed: checks transforms, localization, and export timing.
- Channel: checks diagnostics and reprocessing.
Steps
- Pick a small set of affected products and variants.
- Fix the comparison time, market, and currency.
- Put every relevant field from every source in one table.
- Trace each mismatch to its source or transform.
- Correct the authoritative value or the transform that changed it.
- Regenerate dependent feeds and markup.
- Check the storefront and the channel independently.
Done when
- Identifiers, price, availability, title, and images agree for the same variant and market.
- Each transformed field has a named owner.
- The channel has processed the corrected export.
- A test or monitor now covers the failure that was missed.
Related pages
Keep working on this issue
Primary reference
Google Merchant Center product data specification
The attribute, formatting, identifier, availability, price, and landing-page requirements for Merchant Center data.
Open standard
Schema.org
The shared structured-data vocabulary used to describe products, offers, organizations, reviews, and web entities.
Open-source project
Playwright
Cross-browser automation for Chromium, Firefox, and WebKit, useful for repeatable storefront and purchase-path verification.