When a product fact is wrong in several places, fix the earliest confirmed source that publishes the wrong value.
A merchant may correct the price in Merchant Center, then watch it return after the next catalog sync. Another merchant may edit the product page while an app keeps generating old structured information behind it. Both fixes address a symptom, not the publishing source.
Trace one representative product from its source record to the customer-facing result. Keep the product option, market, currency, promotion, and observation time constant so valid differences do not become false mismatches.
Choose one fact and one offer
Do not begin with the whole catalog. Pick one product with a reproducible symptom and one fact, such as base price, sale price, stock, product code, colour, or image. Identify the exact option and market.
Capture the value, source, URL or record ID, and observation time at every step. A sale ending between two checks or a market switch can explain a real difference.
- Product and option ID
- Market, locale, and currency
- Base price, sale, or purchase plan
- Stock state
- Observation and source update times
Draw the publishing chain
A common chain is source catalog, integration or app, product export, selected feed, storefront template, structured product information, and checkout. Your store may skip or add steps. Name the system that owns each change.
At every boundary, ask whether the incoming fact was correct and whether the outgoing fact stayed correct. The first supported break is the likely correction point.
Separate contradictions from legitimate differences
A red option and a blue option may have different stock. Canada and the United States may have different prices. A subscription and a one-time purchase may have different terms. A current page and an older export may reflect different moments.
Record those dimensions before escalating a mismatch. If the mapping cannot be verified, label it unverified and run an interaction check or inspect a directly addressable option.
Option, market, promotion, currency, purchase-plan, and timing differences need context. They are not defects merely because the values differ.
Fix the owner, then validate downstream
If the source catalog is wrong, correct it there and republish. If an integration maps the field incorrectly, repair the mapping. If the feed is right and the page template publishes an old value, fix the template. Avoid manual downstream edits that the next sync will overwrite.
After the staged fix, repeat the same trace. Preserve before-and-after evidence and confirm that the correction did not alter unrelated options, markets, or product facts. Production publication stays under merchant control.
Know when a deeper audit is justified
A public check can confirm the visible symptom. A catalog scan can inspect a merchant-owned file. When neither one can identify the first break, a cross-channel root-cause audit can compare the store, a private source export, and one selected feed or market.
That deeper work should follow evidence, not precede it. The result should identify the correction owner and affected scope without promising a platform or commercial outcome.