E-commerce
July 1, 2026
"I bought 10, why am I paying the unit price?" "How much more for the -15% tier?" "The site displays €8 per unit from 5, my cart says €9.50." Three tickets where a poorly explained volume discount blocks high-volume purchases and creates distrust.
The e-commerce volume discount support covers quantity tiers, applied unit price, gap to next tier, promo stacking, and wholesale-retail confusion. Distinct from MOQ (#476): here, volume discount by qty tier, not minimum order threshold.
This guide #603 covers policy TIERPR-SUP, flows TP-1 to TP-8, and matrix TIERPR-MAP. New volume pricing vertical. Future customer service pair bot TIERPR (#604).
Summary
Why do volume-based prices generate support tickets?
"The more you buy, the cheaper it gets" seems obvious. In practice, the customer does not know if the tier applies to all units or just the last one, if the variants are counted separately, or why the cart does not reflect the PDP price.
Five typical volume pricing frictions
Tier not reached: qty 4, 10% discount tier starting from 5
Unclear unit price: all units or incremental?
PDP vs cart: different checkout tier table
Mixed SKUs: tiers per product or global cart
Promo stacking: volume tier vs sale code
Shopify Quantity Price Breaks and volume pricing apps apply tiers per line or collection (Shopify, quantity pricing 2026). Without TIERPR-MAP, agents improvise tiers or promise prices outside the rules.
TIERPR #603 vs MOQ #476, promo #111, AUTODISC #601 and bot #604
Five contents, five distinct price-volume mechanics.
Quick matrix
#603 TIERPR: unit price qty tiers volume savings
Promo #111: tiered mentioned general promo conditions
AUTODISC #601: automatic cart discount without qty tier
#604 TIERPRbot: bot tier gap qty savings tier 1
#476 = minimum to order. #603 = price drops when qty increases in map tiers.
Which tierpr_* typologies should be classified?
Eight tiered pricing ticket scenarios.
Eight tierpr typologies
tierpr_how_it_works: customer does not understand tier mechanics
tierpr_wrong_price: expected unit price not applied to cart
tierpr_qty_gap: how many more to add to reach the next tier
tierpr_mixed_cart: multiple SKUs with different tier rules
tierpr_wholesale_retail: confusion between pro and individual tiers
tierpr_stack_promo: volume tier vs promo code stack
tierpr_pdp_cart_mismatch: PDP table ≠ checkout
tierpr_post_order: order placed, tier not applied to invoice
Tags: tierpr, volume_pricing, qty_break. TIERPR-MAP-GROUNDED: tier_breaks from map only.
How to structure the TIERPR-MAP matrix?
The TIERPR-MAP matrix documents each volume pricing program for agents and future bot #604.
TIERPR-MAP Columns
tier_program_id: volume pricing program identifier
sku_or_collection: product collection tier scope
tier_breaks: qty threshold unit price or discount_pct
tier_apply_rule: all_units incremental highest_tier_only
eligible_skus: variants counted towards tier
exclusions: sales outlet excluded from tier
stack_with_promo: stack code yes no better_deal
customer_segment: retail wholesale all
customer_copy: customer phrasing PDP tier table
Sync Shopify quantity breaks, app volume pricing, PDP tier table, and helpdesk macros. Pre-launch audit: test qty 1 5 10 visible tier cart mobile desktop.
TIERPR-SUP Policy in six rules
Six rules support volume pricing.
TIERPR-MAP-GROUNDED: tier_breaks apply_rule from map only
CART-VERIFY-FIRST: lookup cart qty price before explain
NO-TIER-PROMISE: no tier price outside tier_breaks map
EXPLAIN-TIER-BY-QTY: detail current qty active tier next gap
STACK-PROMO-CITE: stack promo cites stack_with_promo map
MOQ-WHOLESALE-REROUTE: min order threshold → #476 MOQ-FLOW
Flow TIERPR TP-1 to TP-8
Flow agent eight steps volume-based pricing.
TP-1 Intake: tierpr_* intent + email cart_id SKU qty
TP-2 Program lookup: TIERPR-MAP tier_program breaks rules
TP-3 Cart verify: Shopify cart API qty unit price lines
TP-4 Classify: how wrong_price gap mixed stack post_order
TP-5 Calculate: active tier next tier gap savings EXPLAIN-TIER
TP-6 Respond: macro TIERPR grounded map customer_copy
TP-7 Execute: draft order partial refund escalate pricing ops
TP-8 Close: tag tierpr_resolved tier_program_id
SLA: tierpr_qty_gap answered with exact gap and next tier savings in one interaction.
Essential TIERPR macros
Four macro agents volume pricing.
TIERPR-EXPLAIN-01
« Program [tier_program_id]: [customer_copy map]. Current tier: [qty] units = [prix unitaire] € ([tier_apply_rule map]). Next tier: [next_qty] units = [next_price] €. Saving: [savings] €/unit. »
TIERPR-GAP-01
« SKU [SKU] qty [actuel]: tier [tier actif]. Missing [gap_qty] units for [next_tier price]. [If mix: tier per distinct SKU line.] Add: [lien PDP cart]. »
TIERPR-CART-01
« Cart [cart_id]: [lignes qty SKU prix unitaire API]. [If wrong_price: cause [qty gap / exclusion / apply_rule / stack].] Total [total] €. [If stack promo: TIERPR-STACK-01.] »
TIERPR-POST-01
« Order [order_ref]: tier [attendu / appliqué / absent]. [If absent: cause [qty / bug / exclusion].] [If eligible gesture: partial refund [montant] diff tier.] Delay: [policy geste map]. »
Edge cases: wholesale, MOQ, BOGO, and bundles
Five cases outside the macro standard volume tier.
Minimum checkout order: MOQ-WHOLESALE-REROUTE #476 distinct MOV
Pro wholesale account: B2B pricing segment customer_segment map
BOGO quantity: BOGO1 #591 distinct free item tier
Fixed price bundle pack: bundle #97 pack price ≠ qty tier
Automatic cart discount: AUTODISC #601 distinct tier
Volume tier unit price ≠ MOQ blocking checkout threshold. Reroute #476 if customer mentions minimum order.
Essential third-party KPIs
Five TIERPR steering metrics.
tierpr_ticket_rate: tierpr_* tickets / volume pricing orders
tierpr_tier_explain_rate: resolved how_it_works macro only
tierpr_gap_conversion: resolved qty_gap customer adds tier
tierpr_wrong_price_rate: wrong_price / active tier orders
tierpr_post_order_rate: post_order missing tier / total tierpr
Target: tierpr_gap_conversion greater than 40% with visible customer_copy PDP tiers table.
TIERPR anti-patterns
Five common mistakes in volume pricing support.
Confusing tier and MOQ: MOQ-WHOLESALE-REROUTE #476 distinct
Promised tier price outside map: NO-TIER-PROMISE tier_breaks only
Explain without cart verification: CART-VERIFY-FIRST qty price API
Ignoring tier_apply_rule: all_units vs incremental cite map
Outdated PDP table: sync TIERPR-MAP pre-campaign audit
TIERPR with Qstomy
Qstomy on Shopify: detect tierpr intent, TIERPR-MAP RAG grounded, cart qty unit price lookup, gap next tier calculate, handoff #604 bot tier 1 volume pricing.
Pipeline: #603 agents post_order refund → #604 bot gap savings tier 1.
Explore AI support and request a demo.
Checklist, FAQ and going further
TIERPR Checklist (8 steps)
TIERPR-MAP v1: tier_breaks apply_rule stack segment
Policy TIERPR-SUP: 6 rules EXPLAIN-TIER-BY-QTY
8 typologies tierpr_*: helpdesk tags
4 macros TIERPR-*: EXPLAIN GAP CART POST
PDP tiers table: customer_copy sync map
Qty test 1 5 10: mobile desktop audit cart
Agent training 30 min: TIERPR vs MOQ vs AUTODISC
KPI Dashboard: tierpr_* section 9
FAQ
Difference MOQ #476?
#476 = minimum to place an order. #603 = price drops per tier qty purchased.
Tier on all units?
TIERPR-EXPLAIN-01 tier_apply_rule map: all_units or incremental.
Promo code stack?
TIERPR-CART-01 stack_with_promo map best deal.
Relationship #604 bot?
#604 = bot tier gap savings cart API. #603 = agents post_order refund escalate.
Going further
Auto discount (#601)
This week: index TIERPR-MAP from Shopify quantity breaks, live PDP tiers table, test gap qty 4 to tier 5.
Enzo
July 1, 2026
