E-commerce
July 1, 2026
"Should I buy v1 on sale or wait for v2?" "What is the concrete difference between my 2023 model and the 2026 model?" "I bought the old version yesterday, can I exchange it for the new one?" Three tickets where a poorly framed comparison of old vs new version blocks conversion, generates returns and disputes when the agent confuses changelog #671 and launch #114.
The e-commerce old-to-new version differences support covers comparative table, pre-purchase choice assistance, install base migration and transition exchange policy. Complements #671 updates: here, side-by-side comparison and range migration decision.
This guide #687 covers policy OLDVSNEW-SUP, flow OVN-1 to OVN-8 and matrix OLDVSNEW-MAP. Future customer service pair bot OLDVSNEW (#688).
Summary
Why does the old vs. new version generate customer service tickets?
The brand launches v2 or the 2026 revision while v1 remains in stock or at the end of its lifecycle. The visitor hesitates between the promo for the old version and the new arrivals. The existing customer wonders if the upgrade is worth the cost. Without a comparative SOP, the agent improvises differences, under-sells the new one, or over-promises a free exchange.
Five typical version comparison friction points
Blurry diff: customer cannot see the compare_table map
Which to buy: old vs new pre-purchase indecision map
Upgrade worth: v1 owner upgrading to v2 map
Different accessories: case cartridge v1 vs v2 map
Transition exchange: bought old wants new swap policy map
Baymard points out that a clear comparison table on PDPs reduces abandonment for multi-revision products (Baymard, PDP 2025).
OLDVSNEW #687 vs PRODUPD #671, launch #114, UPGRBND #663 and bot #688
Five pieces of content, five distinct product evolution angles.
Quick Matrix
#687 OLDVSNEW: side-by-side comparison choice old new migration upgrade worth
PRODUPD #671: changelog compat breaking firmware discontinued
Launch #114: after-sales service plan first launch new SKU D-day
UPGRBND #663: scalable pack tier sequence distinct version comparison
#688 OLDVSNEWbot: migration comparison bot tier 1 range
#671 = official compat changelog. #687 = comparison table and decision aid old vs new.
Which oldvsnew_* typologies should be classified?
Eight ticket scenarios comparing the old and new versions.
Eight oldvsnew typologies
oldvsnew_compare: differences compare_table_copy map
oldvsnew_which_buy: buy old or new pre-purchase map
oldvsnew_upgrade_worth: upgrade v1 v2 owner map
oldvsnew_accessory_diff: accessories diff accessory_compat_diff map
oldvsnew_price_diff: price difference promo old vs new map
oldvsnew_old_stock: old version still available old_stock_policy map
oldvsnew_migration: migration steps migration_steps_copy map
oldvsnew_swap: exchange old new transition upgrade_trade_in_policy map
Tags: oldvsnew, version_compare, migration. COMPARE-CITE: compare_table_copy map only.
How should the OLDVSNEW-MAP matrix be structured?
The OLDVSNEW-MAP matrix documents each version transition for agents and future bot #688.
OLDVSNEW-MAP Columns
oldvsnew_program_id : version transition map identifier
product_line_id : map product family
old_version_skus : map old version SKUs
new_version_sku : map new version SKU
compare_table_copy : map side-by-side diff table
upgrade_benefits_copy : map upgrade benefits v1 v2
accessory_compat_diff_copy : map old new diff accessories
price_diff_copy : map transition promo price difference
old_stock_policy : map end-of-life old version stock
migration_steps_copy : map installed base migration steps
upgrade_trade_in_policy : map transition trade-in exchange
produpd671_reroute_policy : map firmware changelog → #671
customer_communication_copy : map version comparison phrase
Sync PDP compare widget, range migration page, helpdesk macros and MULTIMDL #685 revisions if fitment.
OLDVSNEW-SUP policy in six rules
Six rules support old versus new version comparison.
OLDVSNEW-MAP-GROUNDED: compare upgrade diff from map only
COMPARE-CITE: compare_table_copy cites map only not invented
NO-DOWNGRADE-PROMISE: no downgrade from new to old without old_stock_policy map
SWAP-POLICY-CITE: upgrade_trade_in_policy cites map before swap promise
PRODUPD671-REROUTE: changelog breaking firmware → #671 PRODUPD distinct comparison
VERSION-API-CITE: order version SKU API before swap respond
Flow OLDVSNEW OVN-1 to OVN-8
Flow agent eight steps version comparison.
OVN-1 Intake: oldvsnew_* intent + old new SKU order_ref context
OVN-2 OLDVSNEW-MAP: compare upgrade accessory price stock migration swap
OVN-3 Context classify: pre-buy owner upgrade swap stock migration
OVN-4 Version lookup: order API version SKU if swap owner
OVN-5 Policy triage: COMPARE SWAP PRODUPD671 reroute VERSION-CITE
OVN-6 Respond: macro OLDVSNEW grounded compare_table_copy
OVN-7 Execute: swap trade-in exception ops escalate
OVN-8 Close: tag oldvsnew_resolved upgrade_converted swap Y/N
SLA: oldvsnew_compare answered with compare_table_copy COMPARE-CITE in one interaction.
Essential OLDVSNEW macros
Four macro comparison agents version.
OLDVSNEW-COMPARE-01
"Line [product_line_id]: old [old_version_skus map] vs new [new_version_sku map]. Differences: [compare_table_copy map]. [upgrade_benefits_copy map if oldvsnew_upgrade_worth.] [accessory_compat_diff_copy map if applicable.] COMPARE-CITE map only."
OLDVSNEW-WHICH-01
"Pre-purchase: [old_stock_policy map]. [price_diff_copy map.] If budget priority and old stock: [old_version_skus]. If [upgrade_benefits_copy summary]: [new_version_sku map]. PDP Link: [url]."
OLDVSNEW-MIGRATE-01
"Owner [old_version_skus]: migration dynamically to [new_version_sku]: [migration_steps_copy map]. [upgrade_trade_in_policy map if applicable.] Accessories: [accessory_compat_diff_copy map]."
OLDVSNEW-SWAP-01
"Order [order_ref] version [API SKU]: [upgrade_trade_in_policy map]. SWAP-POLICY-CITE only. [If eligible: swap steps map.] [If not: [old_stock_policy] alternative.]"
Edge cases: PRODUPD, refurbished, UPGRBND and MULTIMDL
Five cases outside macro comparison standard version.
Changelog breaking firmware: PRODUPD671-REROUTE #671 backward_compat firmware distinct compare
Refurbished old version: refurbished SKU old_version policy distinct new
Scalable tier pack: #663 UPGRBND sequence distinct swap version
Model revision fitment: #685 MULTIMDL generation_year distinct compare range
Old stock depleted: old_stock_policy new only redirect PDP
Compare side-by-side = #687. Official post-release compat changelog = #671 PRODUPD.
Essential old vs new KPIs
Five OLDVSNEW steering metrics.
oldvsnew_compare_clarity_rate: compare COMPARE-CITE / total oldvsnew_compare
oldvsnew_which_buy_convert_rate: purchase post OLDVSNEW-WHICH-01
oldvsnew_upgrade_convert_rate: upgrade v2 / oldvsnew_upgrade_worth tickets
oldvsnew_swap_request_rate: swap / transition window orders
oldvsnew_compare_invent_violations: invented difference target 0 audit
Target: oldvsnew_compare_clarity_rate greater than 95% and oldvsnew_compare_invent_violations 0.
Anti-patterns OLDVSNEW
Five common mistakes in version comparison support.
Invented diff: COMPARE-CITE compare_table_copy map only
Swap promised without policy: SWAP-POLICY-CITE upgrade_trade_in_policy map
Confusing PRODUPD #671: changelog firmware distinct side-by-side comparison
Downgrade promised: NO-DOWNGRADE-PROMISE old_stock_policy map
Version swap without order lookup: VERSION-API-CITE order SKU API
OLDVSNEW with Qstomy
Qstomy on Shopify: detect oldvsnew intent, OLDVSNEW-MAP RAG grounded, compare_table lookup, which buy recommend, handoff #688 bot compare tier 1.
Pipeline: #688 bot compare which buy tier 1 → #687 agents swap migration escalate.
Explore AI support and request a demo.
Checklist, FAQ and going further
OLDVSNEW Checklist (8 steps)
OLDVSNEW-MAP v1: compare upgrade accessory price stock migration swap
OLDVSNEW-SUP Policy: 6 rules COMPARE SWAP PRODUPD671 reroute
8 oldvsnew_* typologies: tags helpdesk version_compare
4 OLDVSNEW-* macros: COMPARE WHICH MIGRATE SWAP
PDP widget compare: compare_table_copy sync old new
Range migration page: migration_steps upgrade_benefits CTA
Agent training 30 min: OLDVSNEW vs #671 vs #114 vs #663
KPI Dashboard: oldvsnew_* section 9 compare_clarity
FAQ
PRODUPD #671 difference?
#671 = changelog compat breaking firmware discontinued. #687 = side-by-side comparison migration choice.
Launch #114 difference?
#114 = after-sales plan first launch. #687 = side-by-side transition old new existing range.
Buy old or new?
OLDVSNEW-WHICH-01 price_diff old_stock upgrade_benefits map.
Relation with #688 bot?
#688 = bot compare which buy tier 1. #687 = agents swap migration exception escalate.
Going further
This week: index OLDVSNEW-MAP active transitions, audit PDP compare widget, agents test macro OLDVSNEW-COMPARE-01.
Enzo
July 1, 2026
