Variant resolution

The process by which a system maps an offer, link, or answer to the exact purchasable variant (specific SKU, fully-specified color/size/configuration), not just to the parent product.

StoreSteady treats variant resolution as a reference term because Parent-only URL: The link reaches the parent product, not the variant.

• Parent-only URL changes what a crawler, shopping channel, or AI assistant can safely infer about the merchant surface.
• Without a named category, operators tend to treat variant resolution as generic AI noise instead of a reproducible finding with evidence and a validation path.

• variant pre-selection on landing; variant-specific canonical URLs; structured-data offer-to-variant linkage; agent-readable variant identification.

Crawl every variant URL referenced by feeds, sitemap, and structured data. Assert (a) the URL loads; (b) the advertised variant is the pre-selected variant at landing; (c) the resolved SKU matches the feed/markup expectation.

• A parent-product URL that requires the buyer (or agent) to pick a variant before adding to cart.
• A variant URL whose pre-selection is broken on page load (variant defaults back to parent).

1. Identify the merchant-controlled source that creates the variant resolution signal.
2. Reconcile visible copy, machine-readable data, policy text, feed state, and checkout behavior where the term applies.
3. Keep the fix high-level in public docs; detailed remediation belongs inside paid scan workflows.

Rerun the same evidence capture used for detection. The finding is validated only when the original variant resolution signal no longer reproduces and adjacent source surfaces still agree.

• Google Merchant Center - variant URL and pre-selection requirements →
• Schema.org `ProductGroup` and variant linkage →

• Product truth →
• Offer interpretability →
• Offer drift →

• StoreSteady public methodology →
• Google Merchant Center - variant URL and pre-selection requirements →
• Schema.org `ProductGroup` and variant linkage →