E-commerce
June 28, 2026
"Your -40% is fake, the product was already this price last week." "Why does the strikethrough price disappear when I change the size?" "The site says -25% but my -10% code does not apply on top." Questions about strikethrough prices and displayed discounts are not technical bugs: they are demands for transparency where the customer is testing your credibility.
GoTinker points out that a permanent compare-at across the entire catalog becomes a fake promotion and erodes trust faster than any aggressive discount (GoTinker, compare-at 2026). Omnia Retail notes that brands that explain their pricing decisions maintain control of the narrative against price-comparison sites and shopping assistants (Omnia Retail, price transparency 2026).
This guide #248 covers the support management of strikethrough price questions. Distinct from the compare-at glossary (definition) and pricing errors (#247) (incidents): here, how to explain, reassure, and convert when the customer questions the displayed discount.
Summary
Why do questions about crossed-out prices reach support?
The customer support strike-through price centers mistrust and purchasing intention: the customer wants to buy, but refuses to be "ripped off".
Three common triggers
Historical comparison: "I've been watching you for 2 weeks"
Inconsistent variant: crossed out on S, not on M
Expected accumulation: -30% strike-through + influencer code
Journey stage
PDP Chat (60%), cart (25%), post-purchase review (15%). Fordeer Commerce estimates that discount visibility on product pages (not just checkout) reduces abandonment related to ghost codes (Fordeer, compare-at badge 2026).
DTC fashion example
Mid-season sales, 340 "fake discount" tickets in 10 days. Cause: compare-at = MSRP never applied. After BARRE-* scripts + "lowest price 30 days" mention on PDP: tickets −52%, assisted chat conversion +18%, "price scam" reviews −71%.
How does it differ from the glossary and neighboring pricing guides?
Five price-related topics, five angles. #248 = support conversation and trust.
Compare-at Glossary
Compare-at price (glossary): Shopify field definition, calculation, config. #248: what to say to the customer who disputes or does not understand.
Pricing Errors (#247)
Pricing incidents (#247): display bug, low-price cancellation. #248: compliant display but misunderstood or disputed.
Promo Conditions (#111)
Promo offers (#111): BOGO exclusions, mixed carts. #248: native compare-at discount, not code rules.
Price Objections (#174)
Objections (#174): "too expensive" without promo. #248: customer already sees a discount and doubts its sincerity.
Invalid Code (#reduce-promo)
Promo code (#reduce-promo): checkout technical diagnosis. #248: explaining why the compare-at price does not stack with a code.
Which customer questions about strikethrough pricing should be mapped?
Twelve strike-through price customer service verbatims to tag for analytics and macros.
Discount legitimacy questions
"Is this -40% real?"
"Did you raise the price before the sale?"
"What exactly does the strike-through price correspond to?"
Technical display questions
"Why is there no promo on the collection?" (inconsistent variations)
"The -25% badge disappeared when changing colors"
"Instagram shows one price, the website another"
Stacking and final price questions
"Can I add my -10% code on top of the sale price?"
"What is my final price including delivery?"
"Does the strike-through price include VAT?"
Helpdesk tags
compare_at_question + sub-tag: legitimacy, display, stacking, variant. Distinct from price_incident (#247).
How do you explain the strikethrough price without Shopify jargon?
The client compare-at explanation avoids Compare-at price, metafield, and variant_id.
Formulation BARRE-EXPLAIN-01
"The strikethrough price ([X] €) is the reference rate displayed before the discount. You pay [Y] €, which is a [Z] % reduction on this rate. This is the price indicated on the product sheet at the time of purchase."
Useful Analogies
Catalog rate vs. sale price in physical stores
Recently charged price, not manufacturer's suggested price
Final price at checkout = the one displayed in large font on the sheet
What not to say
"It's just marketing" (admission). "The MSRP" if never sold at that price. "I don't know how it is calculated" (refer to internal merchandising first).
Shopify agent reminder
Compare-at > Price displays the strikethrough on PDP. Discount code applies at checkout, not always combinable with already discounted prices (Shopify, sale pricing).
How to comply with the 30-day rule (Omnibus)?
In France and the EU, the Omnibus strikethrough price must correspond to the lowest price charged in the 30 days prior to the promotion (L112-1-1).
Macro BARRE-OMNIBUS-01
"In accordance with European regulations on price reduction announcements, our strikethrough price corresponds to the lowest price we charged for this product during the 30 days prior to the start of the current promotion. We keep a history of our prices and can justify it in the event of an audit."
If the customer disputes with proof
Verify price history export (ERP, Shopify timeline, Omnibus tracker app)
Compare customer screenshot/capture date vs. promotion start date
If merchandising error is confirmed: escalation + display correction (#247)
If customer confuses MSRP and actual price: educational guidance + link to up-to-date product page
Regulatory sources
DGCCRF (price reduction announcements) and PwC Avocats point out: professionals no longer freely choose their reference price (PwC, strikethrough prices 2022).
Shopify Markets EU
Toggle "Hide compare-at price" for EEA if pricing is non-compliant. Godmode AI recommends a 30-day tracker before displaying the strikethrough price in the EU (Godmode, EU compare-at 2026).
How to handle the combination of a strikethrough price and a promo code in a conversation?
Combining compare-at + promo code is the #1 question during influencer sales.
Native Shopify Rule
Sale price (compare-at + price) = current catalog price. The promo code applies to this price, unless "products on sale" are excluded in the discount rules. Shopify displays the strikethrough code at checkout, but not always on the PDP without a third-party app.
Macro BARRE-STACK-01 (combining not allowed)
"The discount displayed on the product page (-[Z] %) is already applied to the price [Y] €. Our code [CODE] cannot be combined with items already on sale, in accordance with the published terms: [link]. You are already getting the best offer available on this product."
Macro BARRE-STACK-02 (combining allowed)
"Good news: your code applies in addition to the sale price. Product page price [Y] €, code -[N] % → approximately [final] € at checkout. Verify the total before payment."
Bot and over-promising
The bot never promises a combination without looking up active discount rules. See anti over-promising (#209).
Why does the promo badge disappear and how can it be explained?
The missing sale badge on collection is often due to inconsistent variants, not a scam.
Technical causes (Shopify Help)
Empty or €0 compare-at price on some variants only
Compare-at ≤ price on a variant
Collection displays "generic" info: an unsold variant hides the badge
5-min agent diagnostic
Admin → Product → Variants: check every line compare-at > price or empty. Shopify recommends standardizing all active variants (Shopify, sale pricing variants).
BARRE-VARIANT-01 macro
"The discount is displayed on the currently selected [color/size] variant. The [X] variant is at the standard price of [Y] € with no promotion. Here is the direct link to the discounted variant: [URL]"
Merchandising escalation
If a bug is confirmed (compare-at is correct in admin, but missing on storefront): ops ticket + temporary exact price macro.
Which agent macros for each type of strikethrough price question?
Eight after-sales service crossed-out price macros cover 90% of the volume.
BARRE-LEGIT-01 (calm objector)
"We understand your vigilance. Our crossed-out price reflects the lowest price from the last 30 days before this promotion, in accordance with regulations. Price paid: [Y] €. Internally verifiable history. A dated screenshot from you would help us if you think there is an inconsistency."
BARRE-HIST-01 ("I'm watching" customer)
"The product was at [Y] € since [date]. The current promotion started on [start date] with a compare-at price of [X] €. No artificial increase before sales on this SKU."
BARRE-FINAL-01 (final cart price)
"Discounted product price: [Y] €. Shipping costs: [F] €. Estimated total: [T] €. The exact amount will be displayed before payment confirmation."
BARRE-POST-01 (post-purchase "I paid too much")
"Your order #[X]: unit price [Y] €, in line with the PDP display at time T. If a discrepancy is found, please send a screenshot + time of purchase for review (#247)."
Post-reply
Tag compare_at_question, variant PDP deep link, DEC if exceptional gesture (#238).
How to prepare your bot and product sheets for slashed price questions?
Compare-at questions prevention reduces tickets before the chat.
Recommended PDP Block
Under the price: "Strikethrough price = lowest price charged in the 30 days before this offer. Price paid: [Y] €. Offer valid until [date] or end of stock." "How do we read our prices?" link to a 200-word transparency page.
Bot Corpus
Intent
compare_at_explain: definition + current PDP linkIntent
discount_stacking: cumulative rules lookup by SKUWeekly sync: price, compare-at, promo dates by bestseller
Ads / Social Alignment
Instagram creatives: same price/compare-at as PDP. Avoid "-50%" in hero if strikethrough is non-compliant. See pre-purchase objections.
Help Center
Article "How to read our prices and promotions": 30 days, coupon stacking, variations, EU Markets.
Which response anti-patterns destroy trust?
Five strike-through price support errors turn a doubt into a 1-star review.
Minimizing the question
"Everyone does this" or "it's normal in e-commerce". Fix: acknowledge the right to verify.
Inventing a reference price
Agent quotes a compare-at price off the top of their head, off by €20. Fix: mandatory admin lookup before any numerical response.
Promising unverified stacking
"Yes, your code will work" without testing the cart. Fix: test checkout link or STACK macro after verification.
Unowned permanent compare-at
GoTinker: permanent strike-through = fake promo. Fix: merchandising removes compare-at outside of real promotions.
Ignoring Markets
DE customer sees FR price screenshot. Fix: ask for market / URL / currency before comparison.
How does Qstomy answer questions about slashed prices?
Qstomy anchors price answers on the live catalog and discount rules.
Compare-at Features
PDP Lookup: price, compare-at, calculated %, active variant
Stacking check: code + discounted product yes/no
Suggested macro BARRE-* depending on intent
Deep link discounted variant if mismatch
Escalation in case of dispute + merchandising flag
Quantified DTC Scenario
Beauty brand, -30% sales, 11% pre-purchase tickets on striked price, average agent time 14 min (improvised explanations). 8 BARRE-* macros + PDP transparency block + compare_at / stacking bot intents. After 7 weeks: compare-at tickets −46%, bot resolution without handoff 58%, chat conversion +22%, DGCCRF-style complaints 0 with documented price history.
Explore Shopify integration, sales conversations, request a demo.
Which operational playbooks should be launched this quarter?
Playbook 1: catalog compare-at audit (1 day)
Export promo SKUs: compare-at > price? 30-day history? MSRP abuse? Correct or remove non-compliant strikethroughs before the campaign.
Playbook 2: BARRE macros (3 hrs)
Import 8 macros from section 8 of Gorgias. Train agents: look up admin before giving figures.
Playbook 3: PDP transparency block (4 hrs)
Theme snippet under price + "Our prices explained" page. Mobile QA on 10 bestsellers.
Playbook 4: uniform variants (2 hrs)
Top 20 multi-variant SKUs: align compare-at or clear. Collection badge test.
Playbook 5: bot intents (1 week)
compare_at_explain + discount_stacking. Tests: stacking yes/no, variant M vs L, 30-day disputes.
Playbook 6: social alignment (2 hrs)
Review last 5 creatives: price/compare-at = PDP. Influencer brief: no implicit stacking.
Useful links
The strikethrough price is not just a Shopify field: it is a visible promise. When support can explain it with simple words, verifiable figures, and consistent macros, the displayed discount becomes a trust lever, not a source of dispute.
Enzo
June 28, 2026
