E-commerce
July 1, 2026
"Change the flavor before shipping tomorrow." "I have been charged but not yet shipped, I want to swap product." "Too late to modify, package already in preparation." Three tickets where a misrouted pre-shipping subscription modification generates churn, a charge without the correct SKU, or a refund dispute.
The pre-shipping subscription modification support covers SKU swap, quantity, skipping a shipping cycle, add-ons, and the edit cut-off window. Distinct from renewal date (#505) and out of stock (#507): here, changing the content of the next shipment before fulfillment.
This guide #531 covers the SUBEDIT-SUP policy, flow SE-1 to SE-8, and the SUBEDIT-MAP matrix. Completes recurring subscription. Future CS pair SUBEDIT bot (#532).
Summary
Why do pre-shipment modifications generate tickets?
The customer wants to change the variant, quantity, or skip the shipment of the current cycle. Without a SOP, the agent confuses skip billing (#505) with pre-ship swap or promises an edit after the fulfillment cut-off.
Five typical friction points
Flavor swap: change variant before warehouse picking
Quantity: change from 1 to 2 units for the next cycle
Skip shipment: keep subscription, no package this cycle
Missed cut-off: order queued in WMS, edit impossible
Post-charge unfulfilled: charged but not shipped, urgent edit needed
The Recharge update subscription API allows swapping before the next order process (Recharge, update 2026). Without the SUBEDIT-MAP edit_window, agents improvise deadlines.
SUBEDIT #531 vs RENEWDATE #505, SUBSTOCK #507 and general subscription
Four elements of content, four recurring subscription layers.
Quick matrix
#531 SUBEDIT: modify shipment content before fulfillment
#505 RENEWDATE: charge date skip cut-off billing
#507 SUBSTOCK: SKU out of stock swap alt OOS
General subscription: pause cancellation global portal
#505 = charge calendar. #531 = package content before ship. #507 = SKU unavailable, alternative retain.
Which sub_edit_* typologies should be classified?
Eight scenarios for pre-shipment modification tickets.
Eight sub_edit typologies
sub_edit_swap_variant: change flavor size SKU
sub_edit_qty_change: modify quantity of next shipment
sub_edit_skip_shipment: skip cycle shipment keep subscription
sub_edit_add_line: add add-on product to cycle
sub_edit_remove_line: remove add-on before shipment
sub_edit_address: change delivery address before shipment
sub_edit_cutoff_missed: edit requested after edit_window
sub_edit_post_charge: charged unfulfilled urgent edit
Tags: sub_edit, subscription. Lookup Recharge subscription_id next_order unfulfilled status SUBEDIT-MAP.
How to structure the SUBEDIT-MAP matrix?
The SUBEDIT-MAP matrix documents the edit window and authorized actions for agents and the future bot #532.
SUBEDIT-MAP Columns
subscription_plan: monthly quarterly box selling plan ID
edit_window_hours: hours before fulfillment queue cutoff
swap_variant_allowed: Y/N variants map whitelist
qty_change_allowed: Y min max delta
skip_shipment_allowed: Y skip order not subscription
add_line_allowed: Y add-on SKUs whitelist
portal_self_serve_url: Recharge edit section link
agent_override_post_cutoff: Y/N ops WMS exception
post_charge_edit_policy: refund reorder vs WMS hold cancel
One row per plan + warehouse. Quarterly sync with ops fulfillment cut-off WMS.
SUBEDIT-SUP policy in six rules
Six rules support pre-shipment modification.
EDIT-WINDOW-GROUNDED : edit from SUBEDIT-MAP edit_window only
NO-EDIT-POST-FULFILL : fulfilled → reroute WISMO or return
CITE-CUTOFF : edit_window_hours cited if cutoff is near
RECHARGE-SOURCE : next_order status from Recharge API only
SELF-SERVE-FIRST : portal edit before agent manual
POST-CHARGE-ESCALATE : unfulfilled charged → ops WMS priority
Flow SUBEDIT SE-1 to SE-8
Flow agent eight steps pre-shipment modification.
SE-1 Intake: sub_edit_* intent + auth subscription
SE-2 Recharge lookup: next_order status charged_at fulfillment
SE-3 SUBEDIT-MAP: edit_window allowed actions
SE-4 Window gate: inside edit_window vs cutoff missed
SE-5 Self-serve: portal link if customer capable
SE-6 Execute: swap qty skip add Recharge or ops ticket
SE-7 Confirm: macro SUBEDIT grounded next ship date
SE-8 Close: tag sub_edit_resolved outcome
SLA: sub_edit_post_charge answered under 2 hours if unfulfilled and edit_window active.
Essential SUBEDIT macros
Four macro agents.
SUBEDIT-SWAP-01
"Swap completed: [old_sku] → [new_sku]. Next shipment [next_ship_date]. Edit before [edit_cutoff]: [portal_url]."
SUBEDIT-SKIP-SHIP-01
"Shipment cycle [date] skipped. Subscription active. Next delivery [next_ship_date]. For skip billing differences: see RENEWDATE #505."
SUBEDIT-CUTOFF-01
"Order in preparation at warehouse, edit_window closed. Options: receive this cycle or return after delivery according to policy."
SUBEDIT-POST-CHARGE-01
"Charge processed on [charge_date], not yet shipped. [Action] modification in progress by ops. Confirmation within [sla_hours] hours."
Out of stock swap: cross-reference SUBSTOCK #507 if SKU is OOS.
Edge cases: box, mixed, and prepaid
Five cases outside the standard macro.
Subscription box surprise: box #415 limited preferences edit
Mixed cart subscription + one-time: MIXCART #503 edit scope
SKU OOS swap: reroute SUBSTOCK #507 alt map
Address after cut-off: reroute shipping address change playbook
Fulfillment started: NO-EDIT-POST-FULFILL WISMO tracking
Do not confuse skip shipment (no package this cycle) and skip billing (#505): distinct tags sub_edit vs renew_date.
Essential sub_edit KPIs
Five SUBEDIT management metrics.
sub_edit_ticket_rate: edit tickets / subscription orders
sub_edit_success_rate: % edit inside window resolved
sub_edit_self_serve_rate: % resolved via portal without agent
sub_edit_cutoff_miss_rate: edit requested after window
sub_edit_post_charge_sla: ops response unfulfilled charged
Target: sub_edit_self_serve_rate > 60 % after portal edit section visible D-3 renewal reminder.
Anti-patterns SUBEDIT
Five common mistakes.
Confusing skip billing: #505 RENEWDATE distinct
Edit post-fulfill promise: NO-EDIT-POST-FULFILL
Swap SKU outside whitelist: SUBEDIT-MAP swap_variant
Not citing cutoff: CITE-CUTOFF mandatory
Refund without WMS check: POST-CHARGE-ESCALATE ops first
SUBEDIT with Qstomy
Qstomy on Shopify + Recharge: detect sub_edit_* intent, SUBEDIT-MAP lookup, edit window gate, portal deep link, handoff #532 bot tier 1, ops ticket post-charge.
Pipeline: #531 agents execute → #532 bot edit tier 1 self-serve → #507 SUBSTOCK if OOS swap.
Explore AI support and request a demo.
Checklist, FAQ and going further
Checklist SUBEDIT (8 steps)
SUBEDIT-MAP v1: edit_window allowed actions plans
Policy SUBEDIT-SUP: 6 EDIT-WINDOW-GROUNDED rules
8 sub_edit_* typologies: helpdesk subscription tags
4 SUBEDIT-* macros: SWAP SKIP-SHIP CUTOFF POST-CHARGE
Portal edit section: Recharge self-serve visible
D-3 reminder edit link: renewal email + edit CTA
Skip ship vs billing training 20 min: SUBEDIT vs #505
Dashboard KPI: sub_edit_* section 9
FAQ
Difference RENEWDATE #505?
#505 = skip billing charge date. #531 = content shipment before ship.
Difference SUBSTOCK #507?
#507 = OOS SKU alternative. #531 = client edit variant qty choice.
Edit after shipping?
No. NO-EDIT-POST-FULFILL, reroute return or WISMO.
Is Bot #532 enough?
Tier 1 self-serve window gate. Post-cutoff ops → agents #531.
Going further
This week: document SUBEDIT-MAP by Recharge plan, activate portal edit deep link D-3 reminder, train agents skip ship vs skip billing, measure sub_edit_self_serve_rate.
Enzo
July 1, 2026
