Product Data Change Log, QA, and RACI
Turn product data edits from personal habit into a traceable workflow: who requested it, who changed it, who verified it, and which channels need to refresh. 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.
TrekCup 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
Turn product data edits from personal habit into a traceable workflow: who requested it, who changed it, who verified it, and which channels need to refresh.
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.
Change-log and QA checklist: change QA
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 |
|---|---|---|---|
| Requested | Why the edit exists | Ads diagnostics, SEO, inventory, promotion, or support feedback | |
| Responsible | Who edits the source field | Must be able to change Shopify or the source sheet | |
| Consulted | Who judges impact | Ads, SEO, site operations, or support depending on the field | |
| Informed | Who needs to know | Every channel owner that reads the field |
Public references: https://help.shopify.com/en/manual/online-sales-channels/marketplaces/google/getting-setup/syncing-products / https://support.google.com/merchants/answer/13693497?hl=en. These sources confirm field, sync, diagnostic, or structured-data boundaries. Operating signals should become checklists and owner rules instead of visible source labels.
The change log records the reason, not only the action
When TrekCup changes 12oz to 350ml, that is not just a title edit. The log should say whether the reason is Canadian unit language or a Merchant Center unit requirement.
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.
QA covers page, feed, and events
One field change should check product page display, Merchant Center preview, structured data, catalog item, and purchase event ID. Looking only at Shopify admin is not enough.
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.
RACI prevents everyone from editing everything
Merchandising may change titles, ads may request a feed fix, SEO may flag schema mismatch, but the source field owner should be singular.
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.
TrekCup operating drill
TrekCup 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
This is the recurrence-prevention layer for lessons three and four, and it gives lesson seven a QA template for promotions.
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.