E-commerce
July 1, 2026
“I bought step 1, how do I add step 2 at the same pack price?” “My upgrade window has expired, can I still complete it?” “The site says complete my pack, but I don't see the link.” Three tickets where a poorly framed upgradeable pack blocks post-purchase upsell and frustrates when the agent confuses fixed bundle #97 and trial starter kit #308.
The e-commerce upgradeable pack support covers completion after partial purchase, delta upgrade pricing, original order eligibility, and upgrade window. Distinct pack choice PDP #97: here, completable bundle upgradeable after purchase step-by-step.
This guide #663 covers policy UPGRBND-SUP, flow UB-1 to UB-8, and matrix UPGRBND-MAP. Pair of support of the future UPGRBND bot (#664).
Summary
Why do scalable packages generate support tickets?
The customer purchases step 1 of a modular bundle: skincare routine phase 1, coffee machine only kit, or training program module 1. They want to complete it without paying for the full pack again, understand the price delta, or link the upgrade to their original order. Without a SOP, the agent sells the entire pack or improvises an upgrade discount.
Five typical modular bundle upgrade frictions
Vague next step: customer does not know what to add
Opaque upgrade price: delta vs full pack is misunderstood
Order eligibility: link upgrade to original order map
Expired window: upgrade_window_days exceeded map
Partial return: step 1 before upgrade return policy map
GoPrecision notes that progressive bundles increase LTV when the upgrade path is documented (GoPrecision, bundling 2026). Without UPGRBND-MAP, support and merchandising diverge on upgrade pricing and eligibility.
UPGRBND #663 vs bundle #97, starter #308, LE #221 and bot #664
Five contents, five distinct bundle models.
Quick Matrix
#663 UPGRBND: modular post-purchase upgrade completion milestone pack
Bundle #97: help choosing pack vs single pre-purchase PDP
Starter #308: credit-based discovery kit trial-to-full-size trial
LE coffret #221: distinct modular limited edition fixed set
#664 UPGRBNDbot: low-pressure tier 1 next step handoff bot
#97 = choose before purchase. #663 = complete or upgrade after stage N partial purchase.
Which upgr_bnd_* typologies should be classified?
Eight upgradeable pack ticket scenarios.
Eight upgr_bnd typologies
upgr_bnd_how_it_works: customer does not understand modular journey map
upgr_bnd_whats_next: what step to add after tier N map
upgr_bnd_pricing: upgrade delta price vs complete pack map
upgr_bnd_eligibility: eligible for upgrade order order_ref map
upgr_bnd_complete: complete whole pack savings map
upgr_bnd_order_link: link upgrade to original order map
upgr_bnd_window_expired: upgrade window expired policy map
upgr_bnd_return_tier: return to step before upgrade map
Tags: upgr_bnd, upgradeable_bundle, modular_pack. ORDER-API-CITE: tier_owned API order lookup.
How to structure the UPGRBND-MAP matrix?
The UPGRBND-MAP matrix documents each evolutionary pack program for agents and future bot #664.
UPGRBND-MAP Columns
upgrbnd_program_id: modular map pack identifier
bundle_tiers: tier1 tier2 tier3 SKU map sequence
upgrade_path_skus: upgrade SKUs by owned tier map
upgrade_window_days: days post tier1 for map upgrade
upgrade_pricing_policy: price delta vs full map pack
complete_bundle_savings_copy: map completion savings
order_link_required: Y/N original map order link
eligibility_rules: must own tier N for N+1 map
return_policy_per_tier: return by steps before map upgrade
upgrade_portal_url: customer map completion link
customer_communication_copy: modular map journey phrase
Sync metafield tier_owned order, post-tier1 upgrade CTA email, helpdesk macros, and upsell dashboard.
UPGRBND-SUP policy in six rules
Six rules for the scalable support pack.
UPGRBND-MAP-GROUNDED: price tier window from map only
ORDER-API-CITE: tier_owned order API before eligibility
UPGRADE-PRICE-CITE: upgrade_pricing_policy delta cite map
WINDOW-CITE: upgrade_window_days cite map expired policy
STARTER308-REROUTE: trial kit credit → #308 STARTER distinct modular
RETURN185-LINK: partial return → #185 prorated if multi-tier return
UB-1 to UB-8 UPGRBND Flow
Flow agent eight-step scalable pack.
UB-1 Intake: upgr_bnd_* intent + order_ref tier_owned
UB-2 UPGRBND-MAP: tiers upgrade price window eligibility portal
UB-3 Order lookup: tier_owned API order line SKUs map
UB-4 Classify: next price eligibility complete window return
UB-5 Policy triage: ORDER-CITE UPGRADE-PRICE WINDOW eligibility
UB-6 Respond: macro UPGRBND grounded map portal url
UB-7 Execute: ops upgrade link discount code exception window
UB-8 Close: tag upgr_bnd_resolved upgrade_converted Y/N tier_added
SLA: upgr_bnd_whats_next answered with next tier SKU upgrade_portal_url map in one interaction.
Essential UPGRBND macros
Four upgradeable bundle macro agents.
UPGRBND-EXPLAIN-01
"Upgradeable bundle [upgrbnd_program_id]: [customer_communication_copy map]. Steps [bundle_tiers map]. You own tier [N API]. Next step: [upgrade_path_skus map tier N+1]. Link: [upgrade_portal_url map]."
UPGRBND-PRICE-01
"Upgrade tier [N+1]: [upgrade_pricing_policy map price delta]. Full bundle: [complete_bundle_savings_copy map]. Window: [upgrade_window_days map] days post purchase tier 1. [If expired: policy map.]"
UPGRBND-ELIGIBILITY-01
"Order [order_ref]: tiers owned [tier_owned API map]. Eligible for upgrade tier [N+1]: [Y/N eligibility_rules map]. [If order_link_required Y: use [upgrade_portal_url map] linked to order.]"
UPGRBND-RETURN-01
"Return tier [N] before upgrade: [return_policy_per_tier map]. Upgrade canceled if tier returned. Multi-tier partial return: policy #185 pro-rata if applicable."
Edge cases: fixed bundle #97, return #185, tiered #603, and mixed cart
Five cases outside the standard scalable macro pack.
Fixed PDP bundle: #97 distinct modular pack choice post-purchase
Multi-tier partial return: #185 pro-rata calculation return_policy_per_tier
Volume qty tier: #603 TIERPR qty distinct modular pack
Loyalty tier upgrade: #583 MEMSALE distinct tier SKU pack
Tier 1 order outside program: non-map SKU ineligible explain alt full pack
Scalable pack = owned tier sequence. Fixed bundle #97 = upfront multi-SKU single purchase.
Essential upgr_bnd KPIs
Five UPGRBND steering metrics.
upgr_bnd_upgrade_convert_rate: purchased tier N+1 / eligible tier N owners
upgr_bnd_complete_bundle_rate: complete pack / modular programs
upgr_bnd_window_convert_rate: upgrade in window / total upgrades
upgr_bnd_eligibility_response_sla: eligibility answered ORDER-CITE / total
upgr_bnd_window_expired_ticket_rate: expired window / upgr_bnd tickets
Target: upgr_bnd_upgrade_convert_rate greater than 25% and upgr_bnd_eligibility_response_sla greater than 95%.
UPGRBND anti-patterns
Five common mistakes with upgrade support packs.
Invented upgrade price: UPGRADE-PRICE-CITE upgrade_pricing_policy map
Eligibility without order lookup: ORDER-API-CITE tier_owned API
Confusing starter #308: STARTER308-REROUTE distinct modular trial credit
Ignored window: WINDOW-CITE upgrade_window_days expired policy
Selling full pack without explain: UPGRBND-EXPLAIN next tier portal first
UPGRBND with Qstomy
Qstomy on Shopify: detect upgr_bnd intent, UPGRBND-MAP RAG grounded, tier_owned order lookup, UPGRADE-PRICE cite, handoff #664 bot tier 1 next step.
Pipeline: #664 bot explain next tier tier 1 → #663 agents window expired return escalate ops.
Explore AI support and book a demo.
Checklist, FAQ and going further
UPGRBND Checklist (8 steps)
UPGRBND-MAP v1: tier upgrade price window portal eligibility
Policy UPGRBND-SUP: 6 ORDER-CITE UPGRADE-PRICE WINDOW rules
8 upgr_bnd_* typologies: tags helpdesk modular_pack
4 UPGRBND-* macros: EXPLAIN PRICE ELIGIBILITY RETURN
Email post tier1: upgrade_portal_url CTA upgrade_window
Order metafield tier_owned: sync API agents macros
Agent training 30 min: UPGRBND vs #97 vs #308 vs #185
Dashboard KPI: upgr_bnd_* section 9 upgrade_convert
FAQ
Difference with bundle #97?
#97 = pack choice vs single pre-purchase PDP. #663 = upgrade completion after partial tier purchase.
Difference with starter #308?
#308 = trial credit discovery kit trial-to-full-size. #663 = modular pack completable steps.
Upgrade window expired?
UPGRBND-PRICE-01 WINDOW-CITE policy map exception ops if applicable.
Relation with #664 bot?
#664 = tier 1 next step bot without pressure. #663 = agents window return pricing escalate.
Going further
This week: index UPGRBND-MAP programs, audit upgrade_portal_url emails, test macro UPGRBND-ELIGIBILITY-01 agents.
Enzo
July 1, 2026
