E-commerce
July 1, 2026
“I paid €89 on Monday, today it is €59 on your site.” “You charged me €120 even though the -20% promo was announced for the whole week.” “My pre-order price increased by €15 without warning.” Three tickets where the price changed after validation, and it was not a display error at checkout.
Post-purchase price changes (sale drops, pre-order increases, promo endings) generate frustration and chargebacks if customer support improvises. A documented PRICE-ADJ policy, an eligibility window, and PADJ-* macros protect both margin and relationship.
This guide #387 covers how to respond to price changes after ordering without conflict. Distinct from price errors (#247) (display bugs, pricing errors) and the future competitor price match (#388): here, it is about the store price changing after the customer has paid.
Summary
Why do post-purchase price changes overload customer service?
A post-purchase price change ticket arises when the amount paid differs from the currently displayed price, without any disputed technical error. The customer perceives an injustice, not a misunderstanding.
Five common DTC triggers
Sales launched D+2 after a full-price purchase
Flash sale 48 hours during the customer return window
Pre-order: deposit price vs. revised final price
Auto promo end: customer thought the promo lasted all week
Shopify Markets: EUR price vs. price displayed in another market
Shop Happens points out that most brands apply 7 to 30-day windows for price adjustments, which are rarely publicized (Shop Happens, price adjustment 2026).
Angle #387 vs. related content
Price errors (#247): PDP bug, ridiculously low price, expired promo displayed. #387 = legitimate price changing.
Price match (future #388): competitor alignment. #387 = same store, different price over time.
Partial refund (#368): general PART-REF process. #387 = specific price delta reason.
Price objections (#174): too expensive pre-purchase. #387 = post-paid order.
DTC Example
Skincare brand, launching -30% sales 36 hours after a peak in full-price orders. 142 price_drop tickets D+1 without a policy. After PRICE-ADJ 14 days: price_adj_fcr 81%, average partial delta €18, price chargebacks -62%.
Risk without a policy
Agent A refunds 100% of the delta, Agent B refuses everything, Agent C offers a store credit: inconsistent CSAT and unpredictable margin.
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 pricing errors and price matching?
Four pricing contents, four types of dispute, and four distinct processes.
#247 price error (incident)
Nature: store error (bug, feed, live promo by mistake)
Issue: acquired customer right, cancellation of ridiculously low price
Action: honor, bulk cancel, partial bug fix
#387 price change (legitimate evolution)
Nature: commercial strategy (sales, end of promo, pre-order review)
Issue: commercial courtesy, no legal obligation unless specified in T&Cs
Action: PRICE-ADJ policy, partial delta if eligible
#388 price match (competitor)
Customer quotes Amazon or retailer X cheaper today. Proof qualification, margin impact, promo stacking rules. Out of scope of #387.
#368 partial refund (execution)
PART-REF-GATE executes the amount. PRICE-ADJ decides if the price delta is eligible and how much.
Workflow complementarity
Ticket arrives → classify as price_incident (#247) vs price_adj (#387) vs price_match (#388). If price_adj is eligible → partial refund via PART-REF #368.
Which price_adj_* scenarios to map?
Ten post-purchase price change typologies for consistent tags and macros.
Ten price_adj scenarios
price_drop_sale: sales launched after full-price purchase
price_drop_flash: flash promo 24-72 hours post-order
price_drop_sitewide: general -15% code while customer paid full price
price_increase_preorder: preorder, final price > announced deposit
price_increase_correction: rare ERP correction increase before shipping
price_promo_ended_perceived: customer thought promo was active longer
price_bundle_recalc: partial return, bundle promo recalculated (#247 overlap)
price_market_currency: same SKU, different price on Shopify market
price_subscription_change: recurring subscription, new price announced
price_return_rebuy: customer wants to return to repurchase cheaper
Helpdesk tags
price_adj, price_drop, price_increase, price_adj_approved, price_adj_denied, price_adj_credit. Distinct from price_incident (#247) and price_match (#388).
Ticket collection data
Order No., purchase date, SKU/variant, line price paid, current PDP price (screenshot), fulfillment status, customer LTV, remaining policy window.
Priority
price_increase_preorder + chargeback threat = P1. price_drop_sale volume = standard P2.
How should the PRICE-ADJ policy be structured?
The e-commerce PRICE-ADJ policy documents eligibility, window, amount, and exceptions before CS responds.
Five policy pillars
Window: 14 or 30 calendar days post-order date (brand choice)
SKU eligibility: same variant_id, same store, comparable stock
Exclusions: clearance, bundle, flash exclusive, wholesale, gift card
Compensation: partial refund of CC delta or optional +10% store credit
Cap: max 1 adjustment/customer/order, VIP LTV tier exception
14 vs 30 days window
Savings Roll notes that most US retailers use 7-30 days (Savings Roll, 2026). FR DTC: 14 days standard, 30 days VIP or basket > €150. Align T&C page /price-adjustment.
Delta calculation
Delta = (unit price paid − current PDP price) × quantity, excluding shipping already billed. If initial customer promo had -10% at purchase, compare net price paid vs current equivalent net price.
Price increase (price_increase)
Pre-order: final contractual price in confirmation email. If unannounced T&C increase: cancellation free of charge or honor initial price if order not shipped.
Policy publication
Footer page "Price Adjustment" + link macros PADJ-DENY if out of window. FasterCapital recommends clear communication of process and eligibility criteria (FasterCapital, price adjustment).
DEC exception
Out of policy but founding goodwill gesture: mandatory DEC form goodwill gestures (#238).
How to apply the PADJ-FLOW in seven steps?
The PADJ-FLOW framework structures the price change process in seven steps.
Seven PADJ-FLOW Steps
PA-1 Intake: order, date, SKU, price paid vs current customer price
PA-2 Classifier: price_drop vs price_increase vs price_incident (#247 redirect)
PA-3 Verify Eligibility: window, exclusions, fulfillment
PA-4 Calculate Delta: Shopify order line vs PDP live same variant
PA-5 Decide: approve partial, credit, deny, return-rebuy
PA-6 Execute: partial refund Shopify or gift card
PA-7 Document: note order, tag price_adj_approved, customer macro
PA-2 redirect #247
If reproducible display bug or ridiculously low price: transfer to price_incident (#247), not courtesy PRICE-ADJ.
PA-3 fulfillment rules
Unshipped: cancel option + reorder at lower price (if customer agrees to delay)
Shipped not delivered: standard partial delta
Delivered < 14 days: partial delta OR return-rebuy if return policy applies
Delivered > window: polite deny + Tier 2 LTV exception
PA-5 return-rebuy
Shop Happens: free return + repurchase at lower price if no policy adjustment applies. Guide the customer if return is < 30 days and return shipping is free.
PADJ SLA
Decision within 24 business hours. Partial refund executed within 48 hours. Communication on bank delay of 3-5 days.
Which PADJ-* macros for agents?
Eight standard agent macros PADJ-* standardize price change responses.
Eight PADJ macros
PADJ-APPROVE-01: approved delta, partial refund 48 h
PADJ-CREDIT-01: credit note +10% vs proposed credit card refund
PADJ-DENY-WINDOW-01: outside 14-day window, policy link
PADJ-DENY-EXCL-01: clearance/bundle not eligible
PADJ-INCREASE-01: price increase explanation based on T&C + options
PADJ-REBUY-01: return-rebuy guide with return label
PADJ-REDIRECT-247-01: display error → pricing incident
PADJ-VIP-01: LTV exception, approved delta outside policy window
Conflict-free tone
Empathy + factual policy. "We understand the frustration. Our adjustment policy covers 14 days: your order of [date] is eligible, delta of [X] € will be refunded within 48 hours." No aggressive justification of sales.
PADJ-DENY without dark patterns
Clear refusal + policy link + return alternative if eligible. No guilt-tripping like "you should have waited for the sales".
Shopify PA-6 Execution
Orders → Refund → partial amount delta. Note "PRICE-ADJ order #[id] post-purchase promo delta". See PART-REF #368.
Agent training 45 min
Classify #247 vs #387, live delta calculation, 3 cases of approve/deny/rebuy.
How to manage price decreases vs increases differently?
Post-purchase price drops and increases require an asymmetrical decision tree.
Drop (price_drop): commercial courtesy
POLICY PRICE-ADJ: partial delta if window is OK
Alternative: increased store credit if margins are tight
Return-rebuy if the customer prefers and returns are open
VIP: discretionary 7-day window extension
Increase (price_increase): contractual
Pre-order: final price announced at checkout deposit, confirmation email
Not shipped: honor price paid unless there is a revision clause in the T&C
Valid T&C revision: PADJ-INCREASE-01 + free cancellation option
Shipped: paid price acquired, no surcharge
Subscription (price_subscription_change)
30-day notice period by email under the Hamon Law / Subscription T&C. Support explains the effective date, no retro-adjust for past cycles. Link to save subscription (#373) if there is a churn threat.
Fulfilio returns reminder
Return refund = amount paid at purchase, not the current price (Fulfilio, price returns). Customer return-rebuy: initial refund, new purchase at low price.
Proactive sales communication
Day-1 VIP email "sales tomorrow" reduces price_drop tickets. Support is less overwhelmed on Day+1.
What edge cases and escalations should be anticipated?
Six price change edge cases and escalation rules.
1. Promo bundle recalculated upon return
Overlap #247 price_bundle_recalc. Explain 2+1 promo, not simple PRICE-ADJ.
2. Gift card purchased at full price, promo afterwards
Exclusion policy: no adjustment on gift card purchase. Grant goodwill gesture if high LTV.
3. Multi-quantity, sliding scale price now
Delta on current vs paid tier quantity. Calculate PA-4 line by line.
4. Customer threatens review/chargeback
PADJ-VIP tier 2 review. Document. No total surrender without policy.
5. Influencer code post-purchase
Distinct from price_match (#388). One-time courtesy if within 72h post-order window (#247 promo_forgot).
6. B2B wholesale tier
Contractual negotiated price: no B2C PRICE-ADJ. Handoff to account manager.
Tier 2 Escalation
Delta > €50, price_increase dispute, legal mention: supervisor + DEC form.
Anti-patterns
Promising adjustment without PA-3 verification
Partial refund without Shopify note (chargeback risk)
Confusing price_incident and price_adj
Blunt refusal without return-rebuy alternative
Which price_adj KPIs should be measured?
The price adjustment support KPIs drive policy and sales support load.
Eight key metrics
price_adj_ticket_rate: price_adj tickets / orders
price_adj_fcr: resolved 1st contact / price_adj tickets
price_adj_approve_rate: % of approved vs requested deltas
price_adj_delta_median: median € refunded
price_adj_cost_monthly: total partial PRICE-ADJ delta
price_adj_chargeback_rate: price-related chargebacks / tickets
price_adj_rebuy_rate: return-rebuy vs partial direct
price_adj_csat: post-PADJ satisfaction
DTC Benchmark
price_adj_fcr > 75%, approve_rate 40-60% (strict policy), chargeback price < 2% tickets, median delta €12-25 fashion/beauty.
Sales peak
Anticipate price_adj_ticket_rate x3 on D0-D3 of sales. Extra agents + pre-loaded macros. Daily dashboard during the campaign.
Policy ROI
Monthly delta cost vs avoided chargebacks + repeat rate of PADJ-APPROVE customers. Cahoot: a clear return policy increases trust and repeat purchases.
How to align marketing, ops, and customer service before the sales?
The PRICE-ADJ sale preparation reduces post-purchase conflict through upstream coordination.
Pre-sale checklist (marketing + support)
Publish sale dates on site + VIP email D-1
Verify /price-adjustment page is up to date
Brief agents on PADJ-FLOW + refresh macros
Shopify script: tag D-7 full-price orders at-risk price_adj
Cap sale delta budget (e.g., €8,000 max)
Designated tier 2 escalation during peak
Proactive at-risk email
Orders D-3 to D-1 before sales: "Sales tomorrow, your recent order is still being shipped, 14-day adjustment policy if price drops" email. Reduces hostile tickets.
Compare-at pricing
Sales = legitimate price drop. Do not confuse with stale compare-at (#247). Support verifies price field vs compare_at Shopify admin.
Fulfillment Ops
Delay mass shipping on sale D-0 by 24 hours if high volume of price_adj return-rebuy is expected. Warehouse coordination.
Sale post-mortem
Review price_adj_cost, approve_rate, tickets/host. Adjust window or exclusions for the following year.
How does Qstomy help with price change requests?
Qstomy on Shopify: price_adj intent detection, window eligibility check, order vs PDP delta calculation, PADJ agent handoff.
Qstomy price_adj capabilities
price_adj_detect: "price dropped", "cheaper now"
price_adj_lookup_order: price paid + date via API
price_adj_compare_pdp: live price variant vs line item
price_adj_eligibility: 14-day window, policy exclusions
price_adj_redirect_247: display bug → incident
price_adj_handoff: pre-filled ticket with delta + PA-3 status
Bot informs and qualifies; partial refund execution remains with the agent (PART-REF #368). Future price match bot (#389) covers competitor.
Quantified DTC Scenario
Fitness brand, 68 price_adj tickets/month during sales, price_adj_fcr 58% before bot.
After Qstomy intents: price_adj_fcr 79%, agent/ticket time -9 min, correct price_adj_redirect_247 94% (fewer incident confusions).
Explore AI support, sales agent and request a demo.
Which PRICE-ADJ checklist should be deployed this week?
PRICE-ADJ Checklist (10 steps)
Draft 1-page policy (window, exclusions, delta, cap)
Publish /price-adjustment page + footer link
Document PADJ-FLOW PA-1 to PA-7 in Notion
Create 8 PADJ-* macros + 45-min training
Classify ticket tree #247 vs #387 vs #388
Shopify admin delta calculation template
Integrate PART-REF #368 execution
Monthly price_adj KPI dashboard
Pre-sale checklist helper for marketing + support
Post-mortem after each major promotional campaign
In brief
#387 = price changes post-purchase, #247 = store error
PRICE-ADJ: 14-30 day window, partial delta
PADJ-FLOW: classify → execute in 7 steps
Drop vs increase: courtesy vs contractual
KPI price_adj_fcr: target > 75%
FAQ
Legal obligation to adjust the price?
Generally no for DTC FR, unless stated in preorder T&Cs or in case of error (#247). PRICE-ADJ is a courtesy policy.
Difference with price match #388?
#387 = same store, price changed over time. #388 = competitor is cheaper today.
Customer wants to return and repurchase cheaper?
PADJ-REBUY-01 if return is eligible. Otherwise partial delta if within PRICE-ADJ window.
Order shipped yesterday, sales starting today?
Eligible for PA-3 if within window. Partial delta PA-6, no cancellation.
Relationship with partial refund #368?
PRICE-ADJ decides delta eligibility. PART-REF executes the amount on Shopify.
Go further
Calculate the delta on 5 recent price_drop tickets: check if the 14-day policy would have covered 80% of legitimate requests.
Share this #387 guide with support and marketing: a clear PRICE-ADJ turns sale-period conflicts into a controlled, measurable gesture.
Enzo
July 1, 2026
