E-commerce
July 1, 2026
"I thought I was subscribed, why is there no more automatic debit?" "Redo order #4821 for me, just changing the address." "You charged me twice, cancel the subscription." Three tickets where a recurring customer without a subscription contract talks like a subscriber or requests an assisted repurchase that the customer service team does not know how to handle.
The recurring purchases support without subscription covers voluntary repurchase, Subscribe & Save confusion, modified identical order, and accidental duplicates. Distinct from the replenishment playbook #309: here, agent inbound requests, not Klaviyo marketing flows.
This guide #491 covers policy REPREQ-SUP, flow RR-1 to RR-8, and matrix DISAMBIG-SUB. Completes recurring sales (#309) with the angle of repurchase tickets without formal subscription mechanism. Customer service of the future pair reorder bot (#492).
Summary
Why do non-subscription recurring payments generate specific tickets?
About 80% of customers with 2+ orders are not subscribed. They guest repurchase on their own, but contact support when the self-service flow fails or when they confuse email reminders with recurring debits.
Five typical incoming requests
Subscription confusion: thinks they are subscribed, but has no Recharge contract
Assisted reorder: same order, change address or variant
Stop billing: requests cancellation without an active subscription
Accidental duplicate: two orders of the same SKU within 48 hours
Different price: last purchase was cheaper, disputes price during repurchase
SubSummit distinguishes Subscribe & Save from voluntary reordering (SubSummit, Replenishment Playbook 2026). An agent who applies the subscription script to a voluntary reorder loses both trust and time.
REPREQ #491 vs REORDER #309, subscription and bot #310
Four contents, four responsibilities.
Quick Matrix
#491 REPREQ: incoming repurchase requests without subscription
#309 REORDER: Klaviyo replenishment macros playbook
Subscription: pause skip contract termination
#310 bot timing: proactive AI reorder windows
#309 defines REORDER-POLICY and reminders. #491 processes the "I want to reorder" or "stop charging me" ticket when there is no contract.
Which repeat_req_* typologies should be classified?
Eight scenarios for repurchase requests without a subscription.
Eight typologies of repeat_req
repeat_req_same_order: identical to the last order
repeat_req_modify: same base, change variant qty address
repeat_req_sub_confusion: believes to be subscribed, no contract
repeat_req_stop_charge: stop charge without subscription
repeat_req_duplicate: two accidental orders of the same SKU
repeat_req_price_change: different price vs last order
repeat_req_oos_repeat: usual SKU out of stock upon reorder
repeat_req_agent_place: customer requests order to be placed by an agent
Tags: repeat_req, repeat_no_sub. Exclude subscription tag if Recharge is inactive.
How does the DISAMBIG-SUB matrix work?
Before any macro, the agent checks DISAMBIG-SUB: active subscription contract or voluntary repurchase only.
Mandatory Lookup
Shopify customer: orders_count, last order
Recharge or Shopify Subscriptions: active contract paused cancelled
Klaviyo profile: replenishment vs subscriber segment
Ticket keywords: subscription payment cancel reorder
DISAMBIG-SUB Branches
Active contract: reroute subscription macros skip pause cancel
No contract, 2+ orders: REPREQ-FLOW RR-1 to RR-8
1 order only: early repeat #206, not repeat_req
REPREQ-SUP policy in six rules
Six rules for repurchase support without a subscription.
DISAMBIG-SUB first: never script subscription without a verified contract
NO-FAKE-SUB-CANCEL: do not simulate cancellation if there is no subscription
BUY-AGAIN-LINK: prioritize self-service before agent order
MODIFY-EXPLICIT: list changes vs the last order before GO
DUPLICATE-CHECK: same SKU within 48 hours, offer to cancel one order
PRICE-GROUNDED: quote current PDP price, do not promise old rate
Flow REPREQ RR-1 to RR-8
Eight-step agent flow repurchasing request.
RR-1 Intake: intent repeat_req_* or subscription confusion
RR-2 DISAMBIG-SUB: active contract or not
RR-3 Lookup: last order SKU qty address
RR-4 Classify: same modify duplicate price oos
RR-5 Propose: buy again link or draft modifications
RR-6 Confirm: customer validates diff vs reference order
RR-7 Execute: cart link or handoff ops if agent_place
RR-8 Close: tag repeat_req_resolved, update Klaviyo if snooze
SLA: first response repeat_req < 2 h. Buy again link within 5 min if lookup OK.
REPREQ macros and key formulations
Four essential macros.
REPREQ-SAME-01
"Your last order #{order}: {sku} x {qty}. Identical cart link: {buy_again_url}. Modify variant or address at checkout."
REPREQ-MODIFY-01
"Same order #{order} with {change_list}. Pre-filled cart: {draft_url}. Confirm before payment."
REPREQ-NOSUB-01
"You do not have an active subscription. Your purchases are on an order-by-order basis. To stop receiving reminders: {snooze_url}. No automatic debit in progress."
REPREQ-DUP-01
"Two orders #{a} and #{b} for the same product within 48 hours. Would you like to cancel #{b} before shipping? Reply YES."
Edge cases: price, out of stock and agent order
Four cases outside the standard macro.
Increased price: quote current PDP, loyalty code if policy, not former price
SKU OOS: alternative #309 REORDER-008 or notify me, no dead link
Agent place order: PCI: customer cart link, do not take card via chat
Upgrade subscription request: reroute Subscribe offer if 3+ orders of the same SKU
One-time price exception granted: DEC #237 + PREC-LOG #480, no general promise.
Essential repeat_req KPIs
Five REPREQ management metrics.
repeat_req_ticket_rate: repeat_req tickets / repeat orders
repeat_req_disambig_time: DISAMBIG-SUB lookup minutes
repeat_req_wrong_sub_script: misrouted subscription tickets, target 0
repeat_req_buy_again_cvr: % buy again links converted 7 d
repeat_req_duplicate_saved: duplicate cancellations before ship
REPREQ Anti-patterns
Five common mistakes.
Cancellation script without contract: NO-FAKE-SUB-CANCEL
Ignore DISAMBIG-SUB: subscribed customer poorly served or vice versa
Order card customer chat: PCI violation
Promise old price: PRICE-GROUNDED
Duplicate entire playbook #309: #491 = incoming inquiries
REPREQ with Qstomy
Qstomy on Shopify: Auto DISAMBIG-SUB, last order lookup, buy again link, 48-hour duplicate detection, subscription handoff if contract is active.
Pipeline: #491 resolves repeat_req → #309 snooze replenishment → #492 future assisted bot reorder.
Explore AI support and request a demo.
Checklist, FAQ and going further
REPREQ Checklist (8 steps)
DISAMBIG-SUB sidebar: Recharge status visible to agent
REPREQ-SUP Policy: 6 validated lead rules
8 repeat_req_* typologies: helpdesk tags
4 REPREQ-* macros: SAME MODIFY NOSUB DUP
Flow RR-1 to RR-8: agent training 30 min
Buy again URLs test: 10 repeat sample customers
Duplicate rule 48 h: auto helpdesk alert
KPI Dashboard: repeat_req_* section 9
FAQ
Difference #309?
#309 = Klaviyo replenishment policy reminders. #491 = incoming ticket for repurchase or subscription confusion.
Customer wants subscription after 3 orders?
Macro upgrade REORDER-007 #309. REPREQ confirms DISAMBIG-SUB first.
Bot #492 replaces agents?
Tier 1 reorder link and modify. Agent for duplicate, price dispute, agent_place.
Going further
This week: filter "subscription" tickets without a Recharge contract, test DISAMBIG-SUB on 10 cases, measure repeat_req_wrong_sub_script.
Enzo
July 1, 2026
