E-commerce
July 1, 2026
"My exchange has shipped but I haven't returned the old product yet." "The variant I reserved is no longer available." "Will you charge me if I don't return within 14 days?" Three tickets where a poorly managed instant exchange generates capture disputes, stockouts, and chargebacks if the original return is missing.
The e-commerce instant exchange support covers variant reservation, shipping before return receipt, mandatory return window, and stock risk. Distinct from size exchange #366: here, it's a ship-first reserve stock return window model, not fit-check sizing.
This guide #637 covers policy INSTX-SUP, flow IX-1 to IX-8, and matrix INSTX-MAP. Pairs with the futuristic CS bot INSTX (#638).
Summary
Why does the instant exchange generate support tickets?
The customer chooses instant exchange on the portal: the store reserves the new variant and ships it before receiving the return. They do not understand the return timeframe, the credit card hold, or what happens if the reserved size goes out of stock. Without a SOP, the agent promises a vague timeframe or confuses instant exchange with standard post-reception exchange.
Five typical instant exchange frictions
Vague ship-before-return : customer thinks they can keep both products
Stock reservation: variant released if the return is late
Return timeframe: 14 days vs 30 days penalty poorly explained
Hold or charge: auth hold if non-return is misunderstood
Cancellation: cancelling an instant exchange after the new item has shipped
Loop Returns and advanced exchange solutions document shipping before return with a return window and card hold to limit fraud risk (Loop Returns, advanced exchange 2026). Without INSTX-MAP, agents improvise charges and reservations.
INSTX #637 vs size exchange #366, exchange bot #367, returns #10 and bot #638
Five types of content, five distinct exchange models.
Quick matrix
#637 INSTX: ship-first stock reservation return window risk
Size exchange #366: fit-check avoid 2nd return distinct instant mechanism
Exchange bot #367: variant recommendation bot distinct ops reservation
Returns bot #10: RMA journey refund full standard exchange
#638 INSTXbot: tier 1 bot stock reserve handoff
#366 = post-purchase size advice. #637 = logistics model ship-before-return with window and stock rules.
Which instx_* typologies should be classified?
Eight instant exchange ticket scenarios.
Eight instx typologies
instx_how_it_works: client does not understand ship-before-return portal
instx_reserve_stock: how long is reserved variant map
instx_ship_timing: when is the new one shipped after instant request
instx_return_deadline: deadline to return original penalty map
instx_auth_hold: card authorization hold if non-return explain
instx_not_returned: original not returned charge invoice dispute
instx_stock_lost: reservation expired OOS variant mid-process
instx_cancel_request: cancel instant exchange after shipping new item
Tags: instx, instant_exchange, advanced_exchange. INSTX-MAP-GROUNDED: reserve_days return_deadline from map only.
How should the INSTX-MAP matrix be structured?
The INSTX-MAP matrix documents each instant exchange program for agents and future bot #638.
INSTX-MAP Columns
instx_program_id: instant exchange identifier
eligibility_rules: 1st exchange LTV market SKU map
reserve_duration_hours: variant stock hold duration map
ship_trigger_rule: on_instant_request on_label_scan map
return_deadline_days: mandatory original return deadline map
non_return_charge_rule: capture auth invoice SKU map
auth_hold_amount_rule: authorized hold cart or SKU map
cancel_after_ship_policy: new post-shipment cancellation map
stock_release_rule: reservation release if late return map
customer_copy: instant exchange portal phrase map
Loop ReturnGO portal sync, checkout ack instant exchange, helpdesk macros and return_deadline audit visible before validation.
INSTX-SUP policy in six rules
Six rules support instant exchange.
INSTX-MAP-GROUNDED: reserve ship deadline charge from map only
RETURN-DEADLINE-CITE: return_deadline_days cite verbatim map
RESERVE-STATUS-VERIFY: stock reservation API before status cite
NON-RETURN-CHARGE-CITE: non_return_charge_rule cite if instx_not_returned
SIZEXCH366-REROUTE: fit-check sizing → #366 SIZE-XCH distinct instant mechanics
CHARGE-EVIDENCE-ONLY: capture non-return proofs scan date ops only
Flow INSTX IX-1 to IX-8
Flow agent eight steps instant exchange.
IX-1 Intake: instx_* intent + order_ref instx_id variant_reserved
IX-2 Program lookup: INSTX-MAP reserve deadline charge rules
IX-3 Status verify: instx_status ship_date return_scan reservation API
IX-4 Classify: reserve ship deadline not_returned cancel stock_lost
IX-5 Policy triage: RETURN-DEADLINE-CITE NON-RETURN-CHARGE map
IX-6 Respond: macro INSTX grounded map customer_copy
IX-7 Execute: extend deadline waive charge cancel escalate finance ops
IX-8 Close: tag instx_resolved instx_program_id returned Y/N
SLA: instx_return_deadline answered with RETURN-DEADLINE-CITE and return_deadline_days map in one interaction.
Essential INSTX macros
Four instant exchange macro agents.
INSTX-EXPLAIN-01
"Instant exchange [instx_program_id]: [customer_copy map]. Variant [sku_new map] reserved for [reserve_duration_hours map] h. Shipping: [ship_trigger_rule map]. Original return within [return_deadline_days map] days mandatory."
INSTX-RESERVE-01
"Instant order [order_ref] [instx_id]: reservation [variant map] status [reserved / shipped / released API]. Expires [date reserve_duration_hours map]. [If stock_lost: [stock_release_rule map] alternatives.]"
INSTX-DEADLINE-01
"Original return [order_ref]: due [return_deadline_date map]. [If auth_hold: [auth_hold_amount_rule map] authorization hold until return scan.] [If non-return: [non_return_charge_rule map].] Return label: [return_method map]."
INSTX-NOT-RETURNED-01
"Instant [instx_id]: original not received after [return_deadline_days map] days. Status: [pending_charge / captured API]. Proof of return in transit: [scan date] → escalate CHARGE-EVIDENCE-ONLY ops. Dispute: finance [handoff_sla map]."
Edge cases: double shipping, fraud, mid-flight disruption, and standard exchange
Five cases outside the standard instant macro switch.
Customer keeps both: non_return_charge escalate finance CHARGE-EVIDENCE
Out of stock after booking: stock_release_rule alternative refund waitlist
Returned damaged: partial charge condition inspection map
Standard exchange requested: #10 retours wait-for-return distinct instant
2nd instant abuse: eligibility_rules LTV cap escalate supervisor
Instant active = instx_status shipped + return_deadline future. Do not cancel charge without CHARGE-EVIDENCE-ONLY or API return scan.
Essential instx KPIs
Five INSTX management metrics.
instx_convert_rate: instant chosen / eligible exchanges offered
instx_return_on_time_rate: original returns within deadline / instant ship
instx_non_return_charge_rate: non-return charges / instant ship
instx_stock_lost_rate: expired reservation OOS / instant requests
instx_deadline_cite_rate: % answers RETURN-DEADLINE-CITE map
Target: instx_deadline_cite_rate higher than 95% and instx_return_on_time_rate monthly monitoring by program.
INSTX Anti-patterns
Five common instant exchange support errors.
Promising to keep both products: RETURN-DEADLINE-CITE mandatory
Waiving charges without mapping: non_return_charge_rule ops finance only
Confusing fit-check #366: SIZEXCH366-REROUTE sizing distinct mechanics
Reservation without API: RESERVE-STATUS-VERIFY stock lookup
Deadline not cited: RETURN-DEADLINE-CITE map verbatim
INSTX with Qstomy
Qstomy on Shopify: detect instx intent, INSTX-MAP RAG grounded, instx_status reservation lookup, RETURN-DEADLINE-CITE, handoff #638 bot tier 1 stock reserve.
Pipeline: #638 bot explain reserve tier 1 → #637 agents not_returned charge cancel escalate finance.
Explore AI support and request a demo.
Checklist, FAQ and going further
INSTX Checklist (8 steps)
INSTX-MAP v1: eligibility reserve deadline charge
Policy INSTX-SUP: 6 RETURN-DEADLINE-CITE rules
8 instx_* typologies: helpdesk tags
4 INSTX-* macros: EXPLAIN RESERVE DEADLINE NOT-RETURNED
Instant option portal: customer_copy return_deadline visible
New ship email: INSTX-DEADLINE-01 return_deadline_date
30 min agent training: INSTX vs #366 vs standard exchange #10
KPI Dashboard: instx_* section 9 return_on_time charge_rate
FAQ
Difference with size exchange #366?
#366 = fit-check to avoid 2nd wrong size return. #637 = ship-first reservation return deadline stock risk.
Can I keep both products?
No. INSTX-DEADLINE-01 return_deadline_days map NON-RETURN-CHARGE if original is missing.
Expired reserved variant?
INSTX-RESERVE-01 stock_release_rule map alternatives or waitlist.
Connection to #638 bot?
#638 = bot tier 1 stock reserve explain. #637 = agents not_returned charge cancel escalate finance.
Going further
This week: index INSTX-MAP eligibility, audit return_deadline instant portal, test agent macro INSTX-DEADLINE-01.
Enzo
July 1, 2026
