Google’s dynamic dataset connecting products, pricing, inventory, merchant availability, and store reviews.
Google’s Shopping Graph connects product and seller information used in its shopping experiences. It is an underlying information system, not a merchant’s own stock ledger or a public dashboard where every relationship can be manually controlled.
Information can come from merchant submissions and material available on the web. That makes consistency important: a product page, submitted data and current business systems should describe the same item and offer. A mismatch can confuse shoppers even when each source looks plausible in isolation.
Being represented in a product information system does not guarantee that a particular offer will be displayed or selected. Availability, eligibility and presentation depend on the relevant experience and its requirements. A merchant should focus on accurate source data and monitor actual issues rather than buying a promise to manipulate an undisclosed graph.
Takeaway: Keep product identity, offer details and availability accurate across the systems you control. Separate maintaining data from claiming guaranteed placement in shopping results.
Example
A retailer changes a product’s available size range. Its team updates the product page and the connected product data source, then checks for inconsistent old variants. It does not assume that changing one public page immediately updates every shopping presentation.
What to check
Check the source of an incorrect product detail and use the supported correction process. Do not interpret a shopping result as a live inventory reservation or proof that the merchant’s entire catalog is represented.
For more detail, see Google sources of shopping information.