E-commerce
June 28, 2026
"Your site displayed €49, I paid €79." "The -30% promo was still visible on Instagram last night." "My order was canceled without explanation even though I had the confirmation." Pricing incidents in customer support are not like a promo code refused at checkout: the customer believes they have an acquired right, sometimes with a screenshot to prove it.
GrowthSuite recommends verifying the facts (technical error, ambiguous terms, promo time zone difference) before applying the policy (GrowthSuite, discount disputes 2026). In France, an obvious pricing error can justify cancellation before shipping, but only under strict, documented conditions (Simonnet Avocat, pricing errors 2026).
This guide #247 covers customer support for pricing errors: incorrect display, disputed expired promotions, and post-order corrections. Distinct from promo terms (#111) and invalid codes (#reduce-promo): this focuses on incidents where the perceived price does not match the billed price or the displayed promise.
Summary
Why are price incidents high-stakes tickets?
A customer service pricing error ticket affects trust and margin: the customer accuses the store of bad faith, not technical misunderstanding.
Three immediate risks
Chargeback: "product does not match the advertised price"
Public review: PDP screenshot + rejected ticket on Trustpilot
Viral effect: pricing mistake shared on deal forums
Typical DTC volume
Outside of sales: 1 to 4% of tickets. Campaign peaks, ERP synchronization, Markets changes: 8 to 15%. Intellifant points out that every minute counts between error detection and cancellation before shipping (Intellifant, price errors 2026).
DTC electronics example
Price feed bug: headphones displayed at €29 instead of €129, 847 orders in 4 hours. Without a runbook: agents promise inconsistent partial refunds. With a PRICE-INCIDENT policy: bulk cancellation + email template + €10 store credit gesture: chargebacks estimated at 12 vs 89, CSAT recovery 3.1 → 3.9.
Convert over 2,000 customers on average per month with Qstomy.
The world’s 1st Shopify AI dedicated to customer conversion
Empowering 200+ e-commerce merchants
How does it differ from other pricing content?
Six pricing contents, six roles. #247 covers incidents and corrections, not promo configuration.
Promo conditions (#111)
Promo offers (#111): exclusions, mixed carts, stacking. #247: prices or promos displayed in error, not legitimate rules.
Invalid code (#reduce-promo)
Promo code (#reduce-promo): checkout diagnostics "my code does not work". #247: difference in price paid vs price seen.
Price objections (#174)
Objections (#174): "it is too expensive" pre-purchase. #247: factual dispute post-display.
Goodwill gestures (#238)
Gestures (#238): discount, credit note, gift after an incident. #247 defines when to correct the price vs offering an additional gesture.
DEC documentation (#237)
DEC (#237): tracking exceptions. Every price correction outside the grid = mandatory DEC form.
Checkout outage (#278)
Incident communication (#278): technical unavailability of the checkout. #247: difference in price displayed vs billed, not platform outage.
Strikethrough price (#248 coming soon)
The next guide will cover compare-at and customer trust. #247 includes compare-at / price mismatch differences but not the marketing explanation of the strikethrough price.
What types of pricing incidents should support distinguish between?
Eight after-sales price incident types with distinct routing and tags.
Incident Taxonomy
display_pdp_mismatch: PDP €X, checkout €Y
promo_expired_displayed: banner or social post still visible
promo_forgot_post_order: customer forgets code, order placed
merchant_glitch_bulk: feed error, incorrect low price, hundreds of orders
order_cancelled_price: store cancels due to error
double_charge_price: amount charged > confirmation
markets_currency: wrong market / currency displayed
compare_at_stale: obsolete strikethrough price vs current price
Recommended Gorgias Tags
price_incident + scenario sub-tag. Separate from promo_invalid (#111). P1 priority if bulk glitch or chargeback threatened.
Data to Collect Before Responding
Order No., SKU, timestamped customer screenshot, PDP URL at time T, admin discount applied, Shopify promo timezone, fulfillment status.
What is the legal framework and what terms and conditions (T&Cs) clauses apply in France?
The legal framework for price errors in France guides cancellation vs. fulfillment, without customer support acting as a lawyer.
Key Principles
Contract formed at the time of order with an obligation to pay (L221-14)
Manifest error / ridiculously low price (vil prix): cancellation possible before shipping if proven
T&C Clause: accessible before purchase, non-abusive
Post-shipping: reinforced customer position
Three cumulative conditions (case law)
Simonnet Avocat summarizes: documented good faith of the seller, price is objectively derisory compared to the market, cancellation before shipping. TF1 Info example: TV €1,400 vs €2,600 = plausible error; €15 for a €1,500 PC = manifest error (TF1 Info, price error 2026).
Legal escalation macro
Threat of formal notice, DGCCRF, lawyer: tag legal_price_dispute, never promise delivery at a ridiculously low price without legal validation. See anti over-promising (#209).
How to handle a discrepancy between the displayed price and the checkout price?
The PDP vs checkout mismatch scenario requires technical reproduction before customer response.
Agent diagnostic (10 min)
Open PDP in incognito mode, same customer market
Add to cart, note line price + total
Check Markets, dynamic pricing scripts, third-party apps
Compare order variant_id vs customer screenshot
Check Shopify price history (Product timeline) if available
Decision tree
Reproducible bug on shop side: honor lowest perceived price or partial refund delta. Different variant: explain with correct variant link. Customer cache / Market VPN: pedagogy + moderate goodwill gesture if LTV is high. Auto promo expired between PDP and checkout: see section 6.
Shopify ops correction
Unshipped order: Edit order → line item discount or cancel + draft order corrected price. Shipped order: partial refund delta via Orders → Refund (Shopify, refund orders).
How do you handle a disputed expired promotion after an order has been placed?
The case of a post-order expired promo differs from the courtesy forgotten code (#reduce-promo).
Four sub-cases
Expired code, customer claims to have ordered on time: verify admin vs customer timezone
Social post / email still live: marketing oversight, honor the grace window of 24-48 h
Customer forgot code, order < 24 h: courtesy partial refund policy
Promo removed but compare-at unchanged: explain, no additional discount
Courtesy policy for forgotten code
CheckoutLinks recommends a partial refund by default if the order is recent and overhead is low (CheckoutLinks, forgot coupon 2026). Parameters: 24-72 h window, 1 adjustment/customer/year, flash sale exclusion, tier 1 capped amount (gestures #238).
Shopify: no native retro-discount
Partial refund of the promo amount on the paid order. Document the reason "courtesy promo adjustment". Alternative: equivalent single-use code for next purchase if accounting blocks the partial refund.
How to correct a price on an already paid order in Shopify?
Shopify Admin price corrections follow the fulfillment status.
Unfulfilled
Orders → Edit → Add discount line item OR edit unit price if draft
Recalculate automatic taxes
Send invoice update if B2B
Tag order
price_corrected_pre_ship
Shipped, delta < €50
Partial refund: amount = price paid − price due. Attach internal DEC note. Keep refund ARN for chargeback (Shopify, partial refund evidence).
Shipped, bulk manifest error
Do not ship new glitch orders. Ops hold fulfillment. Legal validates batch cancellation. Email template PRICE-CANCEL-01 + full refund + optional €10 voucher.
Cancellation of low-priced order
Cancel order → auto refund. Transparent macro: display error, refund within 5-10 business days, no delivery at the incorrect price. Separate commercial gesture, never a substitute for the refund due.
Which agent macros for each price scenario?
Six price incident macros standardize agent tone and limits.
PRICE-BUG-HONOR-01 (confirmed bug, modest delta)
"You are correct: a discrepancy between the display price and checkout has been confirmed on [SKU]. We are crediting [X] € to your payment method within 48 hours. Ref. #[order]. We are correcting the display in parallel."
PRICE-PROMO-GRACE-01 (eligible forgotten code)
"Your order #[X] of [date] qualifies for our promotional courtesy adjustment: a partial refund of [Y] € within 3-5 days. Usage: once/year/customer."
PRICE-CANCEL-01 (cancellation for obvious error)
"Due to an entry error on [product], the displayed price did not reflect our actual rate. Your order has been canceled and fully refunded. Bank processing time: 5-10 days. As a gesture of goodwill: a credit of [Z] € should you wish to try the purchase again at the correct rate."
PRICE-EXPLAIN-VARIANT-01
"The price [X] € corresponds to variant [A]. Your screenshot shows variant [B] at [Y] €. Direct link to the desired variant: [URL]."
PRICE-REFUSE-POLICY-01 (outside framework, no bug)
"We have verified: the billed rate of [X] € corresponds to the price in effect at the time of payment. The promotion [code] expired on [date/time TZ]. Return is possible under [return policy] if the product is new."
PRICE-ESCALATE-01
"Your file has been forwarded to our manager with the screenshots and order history within 24 hours."
Which decision matrix: honor, correct, cancel, or gesture?
The after-sales price decision matrix prevents contradictory promises between agents.
Incident × Action Grid
Proven store bug, delta < 15% of cart: full partial refund of delta
Store bug, order not shipped: edit order or cancel + reorder at OK price
Critical bulk price error (> 50% margin lost): cancellation + refund, optional gesture
Marketing post-live after expiry: honor 24-48 h grace window
Forgotten promo code < 48 h, policy OK: promo partial refund
No bug, clear expired promo: explain, no refund
VIP LTV + grey area: tier 2 cap gesture #238
Agent tier thresholds
Tier 1: adjustment ≤ €25 delta. Tier 2: €25-80. Tier 3 + DEC: > €80 or bulk. GrowthSuite: system error = always honor (GrowthSuite, disputes 2026).
Mandatory documentation
Each adjustment: DEC-ID, tag price_correction, amount, root cause (bug, grace, gesture).
Which anti-patterns and chargeback risks should be avoided?
Five pricing incident support errors are costly in chargebacks and reviews.
Promising the low price without validation
Chat agent "we'll deliver to you for €29" on a glitch affecting 847 orders. Fix: bot and agents route bulk to macro PRICE-CANCEL-01 only.
Partial refund without proof
Shopify chargeback: attach ARN, confirmation email, policy screenshot. Without proof, the bank favors the customer.
Mixing invalid promo and pricing incident
Distorted analytics tags, unsuitable macros. Separate #111 / #reduce-promo / #247.
Silent cancellation
Customer discovers refund without email. Fix: immediate notification + refund processing time + support contact.
Ignoring promo timezone
Shopify expiry = admin timezone (Shopify, discount expiry). Customer UTC+2 vs admin UTC: false dispute. Verify before refusing.
How does Qstomy secure the processing of price incidents?
Qstomy detects disputed price intents and applies the matrix prior to agent response.
Price incident features
Intent price_dispute: order lookup + live catalog price
Compare capture vs order line: mismatch alert
Promo expiry check: timezone + admin discount status
Macro suggestion PRICE-* based on scenario
Tier ceiling: refund blocking > threshold without handoff
Bulk alert: spike in abnormal price SKU orders
DTC encrypted scenario
In-house brand 2,400 tickets/month, 6.2% price_incident misrouted to promo_invalid. Taxonomy of 8 scenarios + 6 macros + tier matrix + weekly bot price sync. After 8 weeks: resolution time −34%, price chargebacks −41%, 7-day repeat contacts −28%, price_correction DEC 100% traceability.
Explore Shopify integration, AI customer support, request a demo.
Which operational playbooks should be launched this week?
Playbook 1: price_incident taxonomy (3 h)
Create 8 tags in section 3 within Gorgias. Train agents: price incident ≠ invalid code.
Playbook 2: matrix + tier thresholds (4 h)
Write section 9 matrix. Validate legal + finance. Publish 1-page Notion "Price Incidents".
Playbook 3: PRICE-* macros (2 h)
Import 6 macros in section 8. Link mandatory DEC fields (#237).
Playbook 4: vil price bulk runbook (2 h)
Ops sequence: hold fulfillment, export orders, legal OK, email batch PRICE-CANCEL-01, monitor chargebacks for 30 days. Intellifant: price anomaly detection alert before pick.
Playbook 5: forgotten code policy (1 h)
48 h window, 1×/year, partial refund max €30, flash sale exclusions. Align #238 caps.
Playbook 6: promo timezone audit (1 h)
List 10 active discounts, note admin TZ, add mention in PRICE-REFUSE macros.
Useful links
A poorly handled price incident costs more than a refund: it costs trust. When support, ops, and legal share the same honor-correct-cancel matrix, each ticket becomes a first-contact resolution, not a repetitive negotiation.
Enzo
June 28, 2026
