PRODUCT DATA

How to Keep Product Prices and Availability Consistent

Trace a product’s selected variant across its storefront page, feed and structured data before a price mismatch becomes customer-facing.

By Cuebase · Published · Updated

Start with one selected variant

Do not audit a product title in the abstract. Pick one real variant and record its SKU, option values, current price, compare-at price if used, and availability. Use that same variant in every check. A page price can be a range; a feed item can be one offer; structured data can describe the default offer. They are different until you prove they agree.

Use a fixture to understand the check

The downloadable fixture is a local, original example, not a live Shopify store or Google feed. Its fictional Trail Mug has two variants. Blue 350 ml is available at $24.00; Black 500 ml is unavailable at $28.00. The fixture deliberately shows $26.00 for Blue in the feed. That is training data, not evidence of a merchant problem.

SurfaceQuestionWhat to record
Visible product pageWhich option is selected and what does the shopper see?URL, options, price, availability, capture time
Variant recordDoes the SKU and option match the displayed offer?SKU, price, inventory policy, publication state
FeedDoes the feed use that variant’s price and availability?Item ID, price, availability, fetch time
Structured dataDoes the rendered offer match the page?Offer price, currency, availability URL, capture time

Fix the owner record first

Find the first controlled record that is wrong. If the Shopify variant price or stock state is wrong, fix that before editing a feed or markup. If the variant is right but the feed is stale, find that feed’s update path. If the feed is right but rendered markup is wrong, inspect the theme or app that generates it.

Shopify variants carry their own price and availability context. Google’s product structured-data documentation puts price and availability in offer information and says those values should match what a shopper can see. That is not an automatic catalog audit; conflicting records still need your investigation.

Check the visible page last

After the owner record and downstream data update, open the public product URL in a clean browser session. Select the exact options from your log. Confirm the displayed price, sale treatment, and availability wording. Then inspect rendered structured data and the next feed fetch. Record when each surface changed. Do not claim a fixed feed-delay window without evidence for that channel.

Use Cuebase for the separate visibility question

Cuebase records what an AI shopping answer says on a fixed prompt; it does not automatically audit prices, feeds, or structured data. In Share of Voice, keep the prompt and tracked brands fixed, choose Run probe now, and use Export CSV for recorded mention and citation metrics. If an answer states a price, save the answer, source URL, selected variant, and timestamps in a separate investigation record.

A repeatable incident log

  1. Capture the shopper-facing claim and source URL.
  2. Record the handle, selected variant, SKU, and option values.
  3. Compare page, Shopify variant, feed, and structured data at recorded times.
  4. Correct the first controlled record that is wrong.
  5. Recheck the same variant after downstream channels refresh.

Read Shopify product data for AI, what to count in an AI answer, and AI share of voice before treating a citation as proof of an offer.

Download the labeled local fixture (JSON) and the incident log (CSV). When the records are clean, start your free catalog scan.