A product catalog is the source of truth that connects product pages, inventory, orders, advertising feeds, support, and reporting. Build it around stable product and variant identifiers, then make every public channel derive price, availability, and descriptive facts from governed records rather than separate manual copies.
Separate products from variants and offers
A product is the shared concept; a variant is a purchasable difference such as size, color, material, capacity, or pack count; an offer describes commercial terms such as price, currency, condition, and availability. Give each sellable variant a unique stock-keeping identifier and retain supplier or global identifiers when they are valid. Do not reuse an identifier for a materially different item.
Google's product-variant documentation describes grouping variants with ProductGroup and giving each variant and group a unique identifier. It also recommends that a directly addressable variant show the matching image, price, availability, and add-to-cart state. Even when search markup is not used, that consistency is a good catalog acceptance test.
Define required fields and ownership
For each product and variant, identify the owner and required fields: title, description, brand, category, attributes, identifiers, images, active price, currency, tax treatment, weight and dimensions, fulfillment rules, availability, return restrictions, and lifecycle state. Record where each value originates and which system may edit it. Keep marketing language separate from regulated, compatibility, safety, or warranty claims that need stronger evidence.
Google's Product structured-data guide explains that product information can include price, availability, shipping, returns, ratings, and variant relationships. Search enhancements are discretionary, so markup should reflect the visible page and business records rather than promises about how a search result will appear.
Control changes and channel synchronization
Use a staging or draft state for new records. Validate identifiers, required attributes, image rights, price, and availability before activation. For bulk edits, export the affected records, test a small sample, and compare the public page, cart, feed, and order record after the change. Retire discontinued items without silently assigning their URLs or identifiers to replacements.
Track synchronization time and failures for storefronts, marketplaces, feeds, and advertising channels. A correct database value is not enough if a stale feed still presents an old price or available quantity. Reconcile exceptions by variant and channel rather than overwriting the catalog from whichever system was checked last.
The catalog is reliable when one variant can be traced from source record to public page, cart, order, inventory movement, support history, and external feed; material facts agree; and every bulk change has a reviewable before-state and verification result.
Sources
- Product Variant Structured Data — Google Search Central
- Introduction to Product structured data — Google Search Central