Compare-at prices, sale prices and rich results
The product page says £40. The collection card says £50. Checkout says £45. Which one is the real price?
That isn’t just a markup problem. It makes the whole offer hard to trust. Shopify’s compare-at price field can show a reference price next to the current one, but the store has to set the values accurately and keep them the same everywhere the product appears.
Search engines may use structured product data to read price and availability, yet valid markup doesn’t guarantee a rich result. Start with the visible offer and the business’s pricing records. Then check the theme and feed so every system shows the same current facts.
Know what the price fields mean
A product price is the amount the customer is expected to pay. A compare-at price is a reference value the theme may show as the previous or regular price when it’s higher than the current one. How it appears depends on the theme and product setup, especially when variants are priced differently.
Before publishing a discount, confirm which variants are on sale, when the offer begins and ends, whether a code is needed and whether shipping or other conditions affect the total. Never inflate the reference price just to make a discount look bigger. Pricing and promotion rules vary by market, so I’d confirm the legal requirements with the right adviser.
Check the whole customer journey
View the product page, collection card, cart and checkout on desktop and mobile. Select each relevant variant and see whether the price changes correctly. If an app handles bundles, discounts or subscriptions, test with that app switched on. Confirm the structured data shows the price the customer sees, and that the theme and an SEO app aren’t both outputting conflicting Product markup. That double-markup clash is one I check for on any client store.
If a discount is activated by a code, explain that clearly. If the product is part of a promotion with exclusions, make those easy to find. A customer should not have to reach the final checkout step to discover that the offer does not apply to the selected variant.
Understand what rich results can and cannot do
Product structured data can help search engines interpret product details such as price, availability and other attributes, depending on the feature and current guidelines. Google may choose not to display a rich result even when the markup is valid. A clean test only confirms the markup can be parsed. It doesn’t prove the offer qualifies for every display or will appear.
Use Google’s Rich Results Test for supported results and the Schema.org validator for broader structured-data checks. Inspect the rendered page after an app or theme update. If two sources provide different prices or availability, find the source of the conflict instead of adding more markup.
Keep feeds aligned
Shopping feeds introduce another copy of product data. Check that submitted price, sale price, availability and landing-page URL match the storefront. Some integrations map Shopify fields automatically; others allow rules or overrides. Document those transformations and test a sample of products after a feed or catalogue change.
When a sale ends, update the product record and feed straight away. Don’t keep advertising a discount that’s gone. Watch Merchant Center diagnostics for price mismatches, and fix them at the source rather than patching each export by hand.
Make the offer understandable
A discount is only useful if the customer understands it. Show the current price clearly, present the reference price in a way that is not misleading and explain relevant terms. Avoid countdowns that restart or claims of limited availability unless they are true. If a product is on clearance and cannot be returned under a clearly stated policy, ensure the terms are lawful and visible before purchase.
A clean product page helps the customer more than an attempt to force a search result enhancement. Accurate product details, readable policies and a working checkout are the foundation.
Check the numbers at the point of purchase
The product page is not the only place a price can change. Automatic discounts, discount codes, shipping and taxes can affect what a customer pays at checkout. If the sale is limited to certain variants or quantities, show that condition before the user commits. Check the offer in the currency and market the customer will use, especially if the store serves more than one region.
Keep a record of the approved regular price and promotion period. This gives the team a reference if the storefront, feed or support message appears inconsistent. Ask the person responsible for pricing to approve the comparison rather than letting a marketer choose a reference value. If a promotion is corrected, update all systems promptly and communicate with customers who may have seen an earlier version.
Validate after theme and app updates
A theme or app update can change how prices are displayed or which structured data is emitted. Recheck a representative product after the change, including its variants and currency. Use testing tools to identify parse errors, then compare the result with the live offer. If Google displays a different price, inspect the feed and page source before editing schema; duplicated or manually patched markup can create a second inconsistency.
Related reading
- Product comparison tables on Shopify
- Shipping and returns structured data for online stores
- Product feeds and SEO: one source of truth for your catalogue
Pick one discounted product and compare its visible price, checkout total and feed values. Where might a customer spot a mismatch?