{"id":10794,"date":"2026-10-21T17:21:48","date_gmt":"2026-10-21T09:21:48","guid":{"rendered":"https:\/\/www.weswoo.com\/?p=10794"},"modified":"2026-10-21T17:21:48","modified_gmt":"2026-10-21T09:21:48","slug":"shopify-compare-at-list-price-ai-shopping-price-history","status":"publish","type":"post","link":"https:\/\/www.weswoo.com\/en\/shopify-compare-at-list-price-ai-shopping-price-history\/","title":{"rendered":"AI Can Read Product Discounts. What Does Your Compare-at Price Really Mean?"},"content":{"rendered":"

A crossed-out price should never be inflated simply to make an offer look better. It deserves another look now because it can travel beyond your product page and reach a shopping assistant as evidence that an item is on sale.<\/p>\n

Imagine selling a small desk lamp for EUR 60, with EUR 80 crossed out beside it. A customer reads that as a EUR 20 saving. But what is the EUR 80: your previous selling price, the manufacturer’s suggested retail price, or a number left behind when the page was designed? Those meanings are different.<\/p>\n

The immediate job is to make that comparison understandable. For the same lamp, variant and sales region, what prices reach your admin, a shopping assistant, the product page and checkout? What supports the reference price? All amounts below are hypothetical teaching examples using the same Matte black \/ USB-C<\/strong> variant.<\/p>\n

\"Distinguish
Distinguish the merchant\u2019s previous selling price from an MSRP comparison before choosing the reference-price display. The lamp, amounts and variant are teaching examples. Main illustration labels are Chinese.<\/figcaption><\/figure>\n

The change: a crossed-out price can become shopping-assistant data<\/h2>\n

On October 9, 2026, Shopify announced that Catalog API returns eligible variant Compare-at prices as list_price<\/code>, without changing price<\/code>. Shopify changelog<\/a><\/p>\n

A variant is the combination a customer actually buys: a particular color, size or configuration. The white lamp’s reference price cannot explain the matte black lamp’s discount. Global Catalog supports buyer context including country, region and currency, so record the variant and buyer region together when checking prices. Global Catalog documentation<\/a><\/p>\n

Returning list_price<\/code> requires Catalog Mapping sharing, a reference price above the buyer’s contextual price, and regional display. Most stores default on; MSRP\/reference-price uses default off. Absence means no displayable reference price for that configuration and context, not proof of no historical reductions. Return conditions<\/a><\/p>\n

Themes control storefront presentation; each AI channel decides whether to display a received reference price. Sale prices and channel display<\/a><\/p>\n

\"This
This setting shares Compare-at reference prices; it does not control overall product discoverability. Check sharing, price and regional conditions, then inspect channel display. Both price and optional list_price use a Price object with amount and currency. A field-relationship diagram, not an account screenshot or price-history audit. Main labels are Chinese.<\/figcaption><\/figure>\n

Establish what EUR 80 means before choosing the display<\/h2>\n

If EUR 80 is only the manufacturer’s suggested retail price, or MSRP, it expresses the manufacturer’s recommendation. It does not establish that your store previously charged EUR 80. Calling the offer \u201cWas EUR 80, now EUR 60\u201d turns an external benchmark into a story about your own price reduction.<\/p>\n

The European Commission’s guidance on unfair commercial practices says recommended retail price comparisons should be explained; unrealistically high references and misleading presentation may mislead consumers. Assessment depends on the circumstances. Adding an \u201cMSRP\u201d label does not automatically make a comparison compliant. European Commission price-comparison guidance, section 2.8.2<\/a><\/p>\n

Even if you previously charged EUR 80, ask where, for which variant and when. An admin screenshot shows what is entered now. It does not establish the product’s selling history.<\/p>\n

A practical coordination problem arises when operations calls EUR 80 the \u201cregular price,\u201d design labels it \u201cwas,\u201d and development treats it as a discount baseline for every channel. Everyone reuses the same number, but the claim made to customers changes. Before changing the page, write one clear sentence defining the field’s business meaning. That matters more than choosing the crossed-out style first.<\/p>\n

A real product page makes the presentation question easier to see. On October 21, 2026, we viewed Taylor Stitch\u2019s The California Shirt in Breaker Gingham page with M\/40 selected. The price area showed USD 94.50 beside a crossed-out USD 135 and a \u201c30% off\u201d message. Near the add-to-cart button, the page also stated that Last Call items were final sale and ineligible for returns or promotional discounts. The useful presentation detail is that price, selected size and purchase restrictions sit in the same decision area, instead of making the customer infer how the offer applies. Taylor Stitch product page<\/a><\/p>\n

\"Actual
Actual Taylor Stitch product page captured October 21, 2026. M\/40 is selected; USD 94.50, a crossed-out USD 135 and 30% off appear with Last Call restrictions near the button. Public storefront observation only; page and brand rights belong to their owners.<\/figcaption><\/figure>\n

That screenshot establishes only what the page displayed at the time. It does not establish whether USD 135 was this variant\u2019s actual previous selling price, MSRP or lowest price over the preceding 30 days, nor does it establish whether the store\u2019s pricing complies with applicable law. This is neither a WESWOO client project nor a test of an AI shopping channel. A merchant can learn from the clarity of the layout while separately verifying the reference price\u2019s meaning and supporting history; those facts cannot be inferred from a polished product page.<\/p>\n

For European sales, the distinction matters directly. For physical goods sold to EU consumers with a price-reduction announcement, Article 6a’s general rule requires the trader’s lowest price during at least the preceding 30 days. Member States have regulatory choices for new arrivals, perishable goods and progressively increased reductions; check the applicable national rules. This is not a universal rule for every price comparison worldwide. European Commission Article 6a guidance<\/a><\/p>\n

Continue with the lamp in Germany. Assume the general rule applies: its regular price was EUR 80, but it was offered for EUR 70 during the 30 days before the reduction. It now costs EUR 60. Advertising \u201c25% off\u201d against EUR 80 overlooks that prior low. The reduction from EUR 70 to EUR 60 is approximately 14.3%. In its 2024 Aldi S\u00fcd ruling, the Court of Justice confirmed that percentage reductions and promotional statements emphasizing a price advantage must use the lowest price during at least the preceding 30 days. Court of Justice case explanation<\/a><\/p>\n

The list_price<\/code> field therefore does not automatically become a \u201clowest price in the past 30 days\u201d field. It carries merchant-supplied pricing data, rather than a conclusion from an audit of price history. The operating team needs records for the relevant region, variant, dates and promotions before choosing the reference price and wording. Developers cannot reconstruct that history from today’s two numbers.<\/p>\n

Check the admin data, then the actual display<\/h2>\n

Start with one variant currently on sale instead of changing the entire catalog. Assemble its SKU, target region, currency, current price, reference-price meaning and applicable historical evidence. Then work through the dependencies.<\/p>\n