E-commerce
July 1, 2026
"You were at €49, now €59, why?" "Can I buy at the old price?" "Raw material costs, ok, but what has changed in the product?" Three tickets where a poorly explained price increase loses shopping carts, fuels negative reviews, and prompts ad hoc requests when the agent promises the old rate or denies the increase.
The e-commerce price increase support covers catalog communication, value explanation, cheaper alternatives, grandfathering policy, and cart grace period. Distinct from post-purchase change #387 PRICE-ADJ: here, it is a general PDP increase and value explanation before or after purchase.
This guide #711 covers policy PRICEINC-SUP, flow PI-1 to PI-8, and matrix PRICEINC-MAP. Customer service pair of the future PRICEINC bot (#712).
Summary
Why does a price increase generate tickets?
The brand is revising prices: raw material inflation, logistical costs, premium repositioning, or the end of permanent promotions. The loyal customer sees a more expensive PDP, a recalculated cart, or an announcement email. They want to understand why, get the old price, or find an alternative. Without a SOP, the agent denies the increase, promises an ad hoc discount, or confuses it with price error #247.
Five typical price increase frictions
Why more expensive: misunderstanding the reason for the increase map
Value justified: what changes for this price map
Old price requested: grandfather policy map
Recalculated cart: cart price before effective_date map
Cheaper alternative: other SKU for the same need map
Baymard points out that price transparency and value justification strongly influence pre-purchase trust (Baymard, pricing UX 2026). Without PRICEINC-MAP, support and merchandising diverge on the price increase message.
PRICEINC #711 vs PRICE-ADJ #387, objections #174, tiered #603 and bot #712
Five contents, five distinct pricing moments.
Quick Matrix
#711 PRICEINC: catalog increase value explanation alternatives grandfathering
PRICE-ADJ #387: price delta after paid order partial refund
Objections #174: too expensive pre-purchase distinct from announced increase
TIERPR #603: qty volume tiers distinct from unit catalog increase
#712 PRICEINCbot: bot explain value alternatives old rate tier 1
#387 = customer has already paid, post-purchase delta. #711 = catalog price goes up, explain value and guide.
Which priceinc_* typologies should be classified?
Eight scenarios for catalog price increase tickets.
Eight priceinc typologies
priceinc_why_increased: why increase map
priceinc_value_explain: what changes in product value map
priceinc_old_price_request: wants old rate map
priceinc_cart_reprice: cart recalculated effective_date map
priceinc_grandfather: eligible for old loyal price map
priceinc_alternative: cheaper SKU same need map
priceinc_subscription: recurring sub new rate map
priceinc_post_purchase_delta: paid before increase wants adjustment map
Tags: priceinc, price_increase, catalog_price. VALUE-CITE: value_explanation_copy map only. priceinc_post_purchase_delta → reroute #387.
How should the PRICEINC-MAP matrix be structured?
The PRICEINC-MAP matrix documents each price increase program for agents and future bot #712.
PRICEINC-MAP Columns
priceinc_program_id: map price increase program identifier
sku_affected: affected SKUs or catalog_wide map
old_price_summary: old displayed price map
new_price_summary: new price map
effective_date: map increase effective date
increase_reason_copy: why cost increase repositioning map
value_explanation_copy: what changes product value map
grandfather_policy: legacy price grandfathered Y/N terms map
cart_grace_period: cart honored X hrs before effective_date map
alternative_sku_ids: validated cheaper alternatives map
customer_communication_copy: email banner PDP macro map
bot_intent_map: bot_priceinc_* #712 mapping
Sync Shopify price list, increase announcement email, and helpdesk macros. Legal audit if grandfather_policy exception.
PRICEINC-SUP policy in six rules
Six rules support list price hikes.
PRICEINC-MAP-GROUNDED: reason value prices from map only
REASON-CITE: increase_reason_copy cites map verbatim
VALUE-CITE: value_explanation_copy cites map if applicable
NO-OLD-PRICE-PROMISE: grandfather_policy cites map only
NO-AD-HOC-DISCOUNT: no improvised discounts outside of grandfather map
PRICEADJ387-LINK: post-purchase delta → #387 PRICE-ADJ distinct from list increase
Flow PRICEINC PI-1 to PI-8
Flow agent eight steps price increase.
PI-1 Intake : priceinc_* intent + order_ref sku cart screenshot
PI-2 PRICEINC-MAP : old new reason value grandfather cart grace alternatives
PI-3 Price lookup : Shopify API current price effective_date verify
PI-4 Classify : why value old_price cart grandfather alternative post_purchase
PI-5 Triage : REASON VALUE NO-OLD-PRICE NO-AD-HOC PRICEADJ387
PI-6 Respond : macro PRICEINC grounded customer_communication_copy
PI-7 Execute : grandfather exception alternative redirect partial #387
PI-8 Close : tag priceinc_resolved value_cited grandfather Y/N
SLA : priceinc_why_increased answered with REASON-CITE increase_reason_copy in one interaction.
Essential PRICEINC macros
Four macro agents price increase.
PRICEINC-REASON-01
"Increase [priceinc_program_id map] [sku]: [increase_reason_copy map verbatim.] New price [new_price_summary map] since [effective_date map.] REASON-CITE."
PRICEINC-VALUE-01
"[sku map]: [value_explanation_copy map.] [If packaging reformulation: product change link.] VALUE-CITE."
PRICEINC-OLD-01
"Old price [old_price_summary map]: [grandfather_policy map: loyal eligible / not available / conditions.] NO-OLD-PRICE-PROMISE."
PRICEINC-ALT-01
"Alternative for same need: [alternative_sku_ids map PDP links.] [If cart_grace_period: cart honored until effective_date map.]"
Edge cases: PRICE-ADJ, errors #247, price match and tiered
Five cases outside of the macro standard catalog increase.
Delta after order paid: PRICEADJ387-LINK #387 partial refund window
Display bug price error: #247 pricing error distinct from legitimate increase
Competitor matching: #388 price match reroute distinct from catalog increase
Quantity volume tiers: #603 TIERPR tiers distinct from unit increase
Strikethrough compare-at price: #248 compare-at distinct from base rate increase
Announced catalog increase = priceinc_why_increased. Customer paid before increase = reroute #387 PRICE-ADJ.
Essential price inc KPIs
Five PRICEINC steering metrics.
priceinc_value_cite_rate: VALUE-CITE / total priceinc_value_explain why
priceinc_reason_cite_rate: REASON-CITE / priceinc_why_increased
priceinc_old_price_promise_violations: old promised rate agent audit target 0
priceinc_ad_hoc_discount_rate: non-grandfathered discount / total priceinc tickets
priceinc_alternative_click_rate: proposed alternative_sku accepted / priceinc_alternative
Target: priceinc_value_cite_rate greater than 95% and priceinc_old_price_promise_violations 0.
PRICEINC anti-patterns
Five common mistakes when supporting a price increase.
Denying the increase: REASON-CITE new_price_summary map
Promising the old rate: NO-OLD-PRICE-PROMISE grandfather_policy map
Improvised ad hoc discount: NO-AD-HOC-DISCOUNT policy map
Invented value: VALUE-CITE value_explanation_copy map only
Confusing PRICE-ADJ #387: post-purchase delta distinct from catalog increase
PRICEINC with Qstomy
Qstomy on Shopify: detect priceinc intent, PRICEINC-MAP RAG grounded, reason value cite, alternative suggest, handoff #712 bot tier 1.
Pipeline: #712 bot explain value tier 1 → #711 agents grandfather exception redirect #387.
Explore AI support and request a demo.
Checklist, FAQ and going further
PRICEINC Checklist (8 steps)
PRICEINC-MAP v1: old new reason value grandfather cart grace alternatives
Policy PRICEINC-SUP: 6 rules REASON VALUE NO-OLD-PRICE NO-AD-HOC
8 typologies priceinc_*: tags helpdesk price_increase catalog
4 macros PRICEINC-*: REASON VALUE OLD ALT
PDP banner hike: customer_communication_copy visible pre-buy
Loyal customers announcement email: increase_reason value_explanation proactive
Agent training 45 min: PRICEINC vs #387 vs #174 vs #603
Dashboard KPI: priceinc_* section 9 value_cite old_price_violations
FAQ
Difference with PRICE-ADJ #387?
#387 = customer paid, post-purchase delta partial refund. #711 = catalog hike explaining value guidance.
Old price available?
PRICEINC-OLD-01 grandfather_policy NO-OLD-PRICE-PROMISE map.
Cart recalculated?
PRICEINC-ALT-01 cart_grace_period effective_date map.
Relation to #712 bot?
#712 = bot explain value alternatives tier 1. #711 = agents grandfather exception redirect #387.
Going further
This week: index PRICEINC-MAP SKUs hike, sync PDP banner effective_date, test macro PRICEINC-VALUE-01 agents why hike.
Enzo
July 1, 2026
