Product Data Source of Truth and Ownership
Separate Shopify product pages, Merchant Center, Meta Catalog, on-site collections, and SEO structured data into data destinations, then assign a single owner for each source field. This lesson stands on its own and also works as the product-data handoff between Google Ads, Meta Ads, SEO, CRO, and operating reviews.
First, this lesson stands on its own
If you are facing one specific issue, such as a Merchant Center warning, a mismatched Meta product set, or a confusing collection page, you can start here. The key idea is simple: product data is not one file. It is an operating chain that distributes facts into several channels.
PetNest is the case site for this lesson. We will separate the same product across Shopify, feeds, catalogs, search, collections, and structured data so one channel fix does not break another channel during the next sync.
What this lesson solves
Separate Shopify product pages, Merchant Center, Meta Catalog, on-site collections, and SEO structured data into data destinations, then assign a single owner for each source field.
The goal is not to fill every possible field at once. The goal is to build a reusable decision order: decide whether the field is required, identify the source, then identify every destination affected by the field. When a new issue appears, the team can fix the root source instead of patching the visible warning only.
- Step one: define the single source of truth so Shopify, feed apps, Merchant Center, and catalog tools do not maintain conflicting versions.
- Step two: assign owner, validation page, and refresh timing so a sync delay is not mistaken for an ads problem.
- Step three: write the fix into the change log so the next similar issue reuses the same path.
Source-of-truth map: field priority table
This table is the working asset for the lesson. Do not only copy field names. Add the current store owner, validation page, and last updated timestamp to every row.
| Field or node | Recommended source | Owner / use | Governance decision |
|---|---|---|---|
| SKU / variant id | Shopify variant | Merchandising | Stable IDs drive channel mapping, event matching, and returns analysis |
| title | Shopify title plus channel override | Merchandising + SEO | Ads, on-site search, and structured data all consume it |
| price / availability | Shopify inventory and price | Operations owner | Price and availability must match the landing page |
| gtin / brand | Product master data or supplier file | Buying or merchandising owner | Affects Merchant Center recognition and cross-platform matching |
Public references: https://support.google.com/merchants/answer/188489?hl=en / https://help.shopify.com/en/manual/online-sales-channels/marketplaces/google/getting-setup/syncing-products. These sources confirm field, sync, diagnostic, or structured-data boundaries. Operating signals should become checklists and owner rules instead of visible source labels.
Draw five data destinations first
Do not start by editing fields. Map the product data into five destinations: Shopify admin, Merchant Center, Meta Catalog, on-site search or collections, and structured data. For each layer, answer which field it reads, who can edit it, how often it syncs, and which channel breaks if the field is wrong.
Turn this decision into the lesson asset, not just a meeting note. Any change that affects price, availability, product title, image, taxonomy, variant ID, or promotion status should trace back to one source field and one owner.
Ownership is not a department label
An owner is not a vague operations team. For PetNest, the travel bottle title belongs to merchandising, GTIN belongs to buying, collection ordering belongs to site operations, and Merchant Center errors belong to ads operations. Each owner needs the authority to make the change.
Turn this decision into the lesson asset, not just a meeting note. Any change that affects price, availability, product title, image, taxonomy, variant ID, or promotion status should trace back to one source field and one owner.
When channel overrides are allowed
If Google Shopping needs a clearer color or capacity phrase, a Merchant Center channel title can exist. The override still needs to be logged in the field priority table with the reason it should not become the Shopify master title.
Turn this decision into the lesson asset, not just a meeting note. Any change that affects price, availability, product title, image, taxonomy, variant ID, or promotion status should trace back to one source field and one owner.
PetNest operating drill
PetNest needs to review 12 SKUs this week. Sample 3 SKUs and compare the product page, Merchant Center preview, Meta Catalog item, collection page, and structured data. Check title, price, availability, image, brand, GTIN, and variant ID consistency.
Execution checks
- Log mismatched fields in the lesson asset, not in a temporary chat thread.
- Mark impact scope: ads serving, organic search, on-site search, collections, dynamic ads, or monthly review.
- Give every fix an owner, deadline, and validation method.
- After the fix, wait for one sync cycle and save the updated channel state.
Cross-series handoff
Upstream, this connects to the Merchant Center basics lesson in `google-ads-basics`; downstream, it hands off to lesson two for title, attribute, and taxonomy design.
If you arrived from ads, SEO, CRO, or operating review work, keep this boundary clear: this series makes product facts trustworthy. Later series decide budget, page design, creative scripts, or profit tradeoffs.