A product feed can pass a format check while describing an offer the customer cannot buy. The title may be valid, the image may load and the identifier may be present, yet the landing page and checkout can disagree about the selected variant or its availability. Data quality requires reconciliation across the journey.
Google Merchant Center's product data specification requires submitted price and availability to match the relevant landing page, structured data and checkout. That is a platform-specific requirement. The operating process below is Aeris editorial analysis for commerce teams that want a more dependable view of their offers across channels.
Start with the same product
Pick a sample that represents the business's difficult cases, not only its simplest products. Include variants, promotional items, limited stock and products offered in more than one market. Record the exact item and destination being tested.
A parent product page may open with a default color or size that differs from the advertised variant. The review needs to follow the actual selected item rather than assume that matching the product family is enough.
Keep a stable identifier in the review record. This allows the feed owner, merchandising team and website owner to discuss the same offer even when the display title changes across channels.
Compare the commercial facts
For each sampled item, compare the feed, landing page, structured representation and checkout. Look at the selected variant, currency, product price, availability and the conditions attached to the offer.
Write down the observation time. An apparent mismatch may be caused by a legitimate change between checks, while a persistent mismatch may indicate delayed updates or inconsistent business rules. The team needs evidence to distinguish those situations.
Separate product price from shipping, taxes and other components when reviewing the total presented to the customer. The goal is a clear explanation of what is payable under the stated conditions, not a forced comparison between fields that mean different things.
Treat promotions as changes with a lifecycle
A promotion has a beginning, an end and eligibility conditions. Assign an owner for how those changes reach each system. A discount that has ended on the website should not remain active indefinitely in another representation of the offer.
Test the transition as well as the steady state. Check what happens when a promotion starts, when it expires and when an item becomes unavailable during the campaign. Those moments can expose dependencies that a normal daily check misses.
Preserve enough history to explain a discrepancy later. A current screenshot cannot establish what a shopper saw earlier, and a feed export without a timestamp may be difficult to reconcile with an order.
Decide what a mismatch should do
Not every inconsistency has the same commercial consequence. A minor wording difference may need routine cleanup. A wrong currency, unavailable variant or misleading purchase condition can require prompt action by the responsible team.
Create a small set of response categories with named owners. Decide which cases require pausing distribution through the appropriate channel controls, which require a source correction and which need further investigation. Do not change factual stock availability merely to use it as an advertising switch.
Avoid fixing only the exported copy if the underlying source remains incorrect. Otherwise, the next refresh may reintroduce the problem and make a temporary repair look like a permanent solution.
Recheck the whole path
After a correction, verify the affected offer in each relevant representation. Record whether the downstream systems have processed the change and distinguish a submitted update from an observed correction.
Keep unresolved cases visible with an owner and a next review point. A dashboard that counts closed tickets without checking the customer journey can reward administrative completion while leaving the original problem intact.
Look for recurring causes across cases. Repeated issues around the same promotion rule, market or variant mapping may justify a source-level improvement instead of a growing queue of individual edits.
Make quality part of campaign readiness
Before increasing traffic to a collection, review a representative sample of its offers and the open exceptions. The purpose is to know which products are ready for distribution and who will respond when conditions change.
Product data quality improves when it becomes a shared operational responsibility. A reconciled offer gives marketing, merchandising and support a common account of what the customer can actually buy.
Source
Google Merchant Center: Product data specification, reviewed September 18, 2026. The reconciliation workflow is Aeris editorial analysis.
