E-commerce
July 1, 2026
"The same product costs 20% less on the website." "The seller refuses to match the web price at the counter." "I paid online, the store displays a different promo." Three tickets where a poorly explained online-store price discrepancy generates frustration, dispute, and loss of omni-channel trust.
The support for different web and store e-commerce prices covers alignment policy, channel promos, price match, and post-purchase adjustment. Distinct from stock availability (#271): here, we address cross-channel price consistency and customer frustration.
This guide #747 covers policy PRXDIFF-SUP, flow PD-1 to PD-8, and matrix PRXDIFF-MAP. Future customer service pair bot PRXDIFF (#748).
Summary
Why do price differences between online and physical stores generate tickets?
The customer compares the web PDP and the shelf label, notices a discrepancy, and demands alignment at the counter or a refund of the difference. Without a SOP, the agent promises a price match outside of policy, ignores an online-only promotion, or compares two different references.
Five typical cross-channel price frictions
Perceived unfair discrepancy: customer does not understand channel map rules
Online-only promo: web code not valid in-store map
In-store only promo: shelf sales not reflected on the site map
Price match refused: sales associate vs. support divergence map
Post-purchase adjustment: customer who paid online wants the difference map
Shopify allows distinct web and POS price catalogs if not synchronized (Shopify POS, products prices 2026). Without PRXDIFF-MAP, support and stores quote contradictory rules.
PRXDIFF #747 vs AVAIL #271, omnichannel POS, web promos and bot #748
Six contents, six distinct cross-channel customer experience journeys.
Quick matrix
#747 PRXDIFF: web price vs store alignment price match adjustment
AVAIL #271: distinct cross-channel stock pricing
Omnichannel POS: unified policy distinct return playbook price
Promos online: distinct web codes store sales aisle
Omni bot #272: general pick-up stock distinct price consistency map
#748 PRXDIFFbot: bot explaining differences tier 1 conditions
Availability = stock present absent. #747 = amount displayed web vs counter and alignment policy.
Which prxdiff_* typologies should be classified?
Eight online store price ticket scenarios.
Eight prxdiff typologies
prxdiff_why_different: why different price web store map
prxdiff_policy_align: cross-channel price alignment policy map
prxdiff_same_sku: same variant reference compared map
prxdiff_promo_online_only: web promo not valid in-store map
prxdiff_promo_store_only: store promo not on site map
prxdiff_price_match_request: customer requests counter alignment map
prxdiff_post_purchase_adjust: post-purchase online adjustment map
prxdiff_denied: alignment refused why map
Tags: prxdiff, price_alignment, cross_channel, omnichannel. POLICY-CITE: price_alignment_policy_copy map only.
How should the PRXDIFF-MAP matrix be structured?
The PRXDIFF-MAP matrix documents each cross-channel pricing rule for agents and the future bot #748.
PRXDIFF-MAP Columns
prxdiff_program_id: cross-channel pricing program identifier map
price_alignment_policy_copy: verbatim alignment rules map
price_match_allowed: Y/N counter price match map
price_match_conditions_copy: proof deadline conditions map
channel_price_rules_copy: sync or distinct web POS catalogs map
promo_online_only_copy: web promos store excluded map
promo_store_only_copy: clearance department web excluded map
adjustment_policy_copy: post-purchase online adjustment map
store_locations: affected stores location_id map
exclusions_copy: final sale marketplace excluded map
customer_communication_copy: cross-channel pricing help page macro map
bot_intent_map: bot_prxdiff_* #748 mapping
Sync omnichannel pricing help page, POS seller training, and helpdesk macros.
PRXDIFF-SUP policy in six rules
Six rules support online store price.
PRXDIFF-MAP-GROUNDED : price match alignment from map only
POLICY-CITE : price_alignment_policy_copy quotes map verbatim
SKU-MATCH-VERIFY : same SKU variant before comparing map price
NO-PRICE-MATCH-PROMISE : no alignment promised if price_match_allowed is N in map
ADJUSTMENT-CITE : adjustment_policy_copy cited if post-purchase map
AVAIL271-REROUTE : stock question → AVAIL #271 distinct rate
PRXDIFF PD-1 to PD-8 Flow
Flow agent eight steps cross-channel price.
PD-1 Intake: prxdiff_* intent + sku variant channel store_location order_ref
PD-2 PRXDIFF-MAP: policy price_match promo adjustment exclusions
PD-3 Price lookup: web price POS price same variant verify SKU-MATCH
PD-4 Classify: why policy promo match adjust denied
PD-5 Triage: POLICY SKU-MATCH NO-MATCH-PROMISE ADJUSTMENT AVAIL271
PD-6 Respond: macro PRXDIFF grounded customer_communication_copy
PD-7 Execute: store ops price match adjustment finance escalate
PD-8 Close: tag prxdiff_resolved policy_cited match_granted Y/N
SLA: prxdiff_why_different answered with POLICY-CITE price_alignment_policy_copy in one interaction.
Essential PRXDIFF macros
Four macro agents price online store.
PRXDIFF-POLICY-01
« [variant map] : [price_alignment_policy_copy map.] [channel_price_rules_copy map.] [exclusions_copy map.] POLICY-CITE. »
PRXDIFF-WHY-01
« Discrepancy noted: web [web_price map] store [pos_price map] same SKU [SKU-MATCH-VERIFY map.] Reason: [promo_online_only_copy or promo_store_only_copy map.] »
PRXDIFF-MATCH-01
« Price match [price_match_allowed map] : [price_match_conditions_copy map.] [If N: NO-PRICE-MATCH-PROMISE alternative map.] [If Y: proof screenshot PDP delay map.] »
PRXDIFF-ADJUST-01
« Order [order_ref map] post-purchase: [adjustment_policy_copy map.] ADJUSTMENT-CITE. Request window [adjustment_window_days map] days map. »
Edge cases: final sale, marketplace, B2B and catalog sync
Five cases outside the standard cross-channel price macro.
Final sale: FINAL-SALE-REROUTE exclusion price match map
Marketplace tiers: exclusions_copy distinct external channel web own store map
B2B wholesale pricing: channel_price_rules_copy distinct B2C catalog map
Un-synced POS catalog: PD-7 ops escalate sync price web POS map
Stock issue only: AVAIL271-REROUTE #271 distinct pricing
Cross-channel price = documented alignment policy. Stock or return = distinct reroute playbooks.
Essential prxdiff KPIs
Five PRXDIFF steering metrics.
prxdiff_policy_cite_rate: POLICY-CITE / total prxdiff why policy
prxdiff_match_grant_rate: price match granted / eligible map requests
prxdiff_false_match_promise_rate: promised alignment out of policy target audit 0
prxdiff_sku_mismatch_rate: different variant comparison / total prxdiff_same_sku map
prxdiff_csat_post_explain: satisfaction after macro PRXDIFF-WHY grounded map
Target: prxdiff_policy_cite_rate higher than 95% and prxdiff_false_match_promise_rate at 0.
PRXDIFF anti-patterns
Five frequent mistakes regarding online vs store price support.
Price match promised outside of policy: NO-PRICE-MATCH-PROMISE price_match_allowed map
Comparing different variants: SKU-MATCH-VERIFY before PRXDIFF-WHY
Invented policy: POLICY-CITE price_alignment_policy_copy map only
Ignoring channel promo: promo_online_only_copy promo_store_only_copy cite map
Adjustment without order lookup: ADJUSTMENT-CITE adjustment_policy_copy order_ref verify
PRXDIFF with Qstomy
Qstomy on Shopify: detect prxdiff intent, PRXDIFF-MAP RAG grounded, policy cite, handoff #748 bot tier 1.
Pipeline: #748 bot explain tier 1 policy differences → #747 agents price match adjustment escalate store finance ops.
Explore AI support and request a demo.
Checklist, FAQ and going further
PRXDIFF Checklist (8 steps)
PRXDIFF-MAP v1: policy price_match promo adjustment exclusions locations
Policy PRXDIFF-SUP: 6 POLICY SKU-MATCH NO-MATCH-PROMISE ADJUSTMENT rules
8 prxdiff_* typologies: tags helpdesk price_alignment cross_channel
4 PRXDIFF-* macros: POLICY WHY MATCH ADJUST
Live omnichannel price help page: price_alignment_policy_copy visible PDP footer
45 min POS sales staff training: price match conditions PRXDIFF-FLOW
POS web catalog sync audit: channel_price_rules_copy discrepancy testing
KPI Dashboard: prxdiff_* section 9 policy_cite match_grant false_promise
FAQ
Availability difference #271?
#271 = stock present/absent store vs web. #747 = price amount and policy alignment.
Is price match always granted?
PRXDIFF-MATCH-01 price_match_allowed map. NO-PRICE-MATCH-PROMISE if N map.
Web promo at the counter?
PRXDIFF-WHY-01 promo_online_only_copy cite map.
Relation to #748 bot?
#748 = bot to explain difference in tier 1 conditions. #747 = agents price match adjustment escalate ops.
Going further
Promo support codes
This week: index PRXDIFF-MAP channel_price_rules, sync omnichannel price help page, test macro PRXDIFF-WHY-01 training POS sales staff.
Enzo
July 1, 2026
