E-commerce
July 1, 2026
"The bot is suggesting a cartridge that is incompatible with my machine." "The AI is pushing for a repurchase even though I still have three filters left." "Chatbot confuses subscription skip #145 with a simple one-time refill." Three failures where a poorly calibrated consumable bot invents a reference, over-sells, or mixes up spare part #343 and consumable map.
An e-commerce AI chatbot for consumables does not replace CONSUM agents (#665). It reads CONSUM-MAP, cites parent product order API, references the correct refill replacement_frequency_days, and performs a handoff for wrong_ref oos subscribe exception to humans.
This guide #666 covers intents bot_consum_*, flow CONSUMbot, and KPI consum_bot. Companion bot of the playbook CONSUM (#665). AI use case: suggest the correct refill at the right time without aggressive pressure.
Summary
Why automate consumables with a bot?
"Which refill for my model?", "when to replace the filter?" and "where to reorder the right cartridge?" are common questions post-device purchase and on reorder CTA emails. A calibrated bot cites CONSUM-MAP consumable_skus replacement_frequency_days reorder_url without pushing immediate purchase or invented references.
What the bot solves tier 1 post-purchase
Which ref: consumable_skus parent product map
Frequency remind: replacement_frequency_days cite map
Compat check: compat_rules generic_consumable_allowed map
Reorder guide: reorder_url repurchase link map
Subscribe link: subscribe_url if subscription_available map
Gorgias estimates that 22% to 32% of post-purchase consumable tickets concern reference and replacement frequency, resolvable by a grounded bot without an agent (Gorgias, CS 2026).
CONSUMbot vs CONSUM #665, replenishment #145, repeat bot #310 and spare #343
Five contents, five distinct consumable repurchase models.
Quick matrix
#666 CONSUMbot: bot tier 1 ref freq remind reorder handoff
#665 CONSUM: agents wrong_ref oos subscribe exception CM-7
Replenishment #145: subscription skip pause frequency distinct contract which_ref
Repeat bot #310: proactive windows reorder generic distinct consum map
Spare #343: spare parts repair distinct consumable consumed
Pipeline: #666 bot ref remind reorder tier 1 u2192 #665 agents wrong_ref oos subscribe escalate.
Which bot_consum_* intents should be configured?
Eight consumable bot intents mapped to consum_* typologies #665.
Eight bot_consum intents
bot_consum_which_ref: consumable_skus parent product cite map
bot_consum_compat: compat_rules generic_consumable_allowed map
bot_consum_frequency: replacement_frequency_days cite map
bot_consum_reorder: reorder_url repurchase guide map
bot_consum_subscribe: subscribe_url if subscription_available map
bot_consum_reminder: proactive reminder replacement_frequency post device
bot_consum_oos: consumable out of stock alt policy map cite
bot_consum_handoff: wrong_ref subscribe exception → #665
Tier 1 auto: which_ref, compat, frequency, reorder, reminder if CONSUM-MAP + parent lookup.
bot_consum_handoff consum_wrong_ref consum_oos subscribe complex → agents #665 payload order_ref consum_sku.
How should CONSUM-MAP #665 be consumed?
The bot reads CONSUM-MAP #665: consum_program_id, parent_product_skus, consumable_skus, consumable_type, replacement_frequency_days, compat_rules, generic_consumable_allowed, reorder_url, subscribe_url, subscription_available, wrong_ref_return_policy, customer_communication_copy, forbidden_reorder_phrases.
Lookup grounded
PARENT-API-CITE-BOT: parent product order API before consum ref
NO-PRESSURE-REORDER-BOT: no urgent phrasing forbidden_reorder_phrases map
CONSUM-SKU-CITE-BOT: consumable_skus cite map only
FREQ-CITE-BOT: replacement_frequency_days cite map no invented date
REORDER-GUIDE-BOT: reorder_url repurchase link no forced bot checkout
REPLEN145-REROUTE-BOT: skip contract pause → #145 replenishment subscription
SPARE343-REROUTE-BOT: repair part → #343 spare distinct consumable
CONSUM665-HANDOFF-BOT: wrong_ref oos exception → #665 CM-7 agents
Alignment anti-hallucination (#123): SKU freq compat = CONSUM-MAP whitelist only.
CONSUMBOT-SUP policy in six rules
Six bot consumable rules without pressure.
CONSUM-MAP-GROUNDED-BOT: SKU freq compat reorder from map only
PARENT-API-CITE-BOT: parent product order API before consum ref respond
NO-PRESSURE-REORDER-BOT: forbidden_reorder_phrases blacklist never used
CONSUM-SKU-CITE-BOT: consumable_skus cite map only reorder
REORDER-GUIDE-BOT: reorder_url repurchase link not bot forced order
EXCEPTION-HANDOFF-BOT: wrong_ref oos subscribe exception → #665 CM-7
Flow CONSUMbot CRB-1 to CRB-8
Eight-step flow for post-purchase device consumable bot.
CRB-1 Classify: bot_consum_* intent detect post-purchase email reorder
CRB-2 Collect: order_ref email parent device consum question
CRB-3 CONSUM-MAP: consumable_skus freq compat reorder subscribe
CRB-4 Parent lookup: parent product order API line SKUs map
CRB-5 Guardrail: PARENT-CITE NO-PRESSURE CONSUM-SKU FREQ REORDER-GUIDE
CRB-6 Respond: TPL-CONSUMbot grounded map API
CRB-7 Handoff: wrong_ref oos subscribe exception → #665
CRB-8 Log: intent consum_program_id tag consum_bot reorder_click Y/N
Example TPL-CONSUMbot-REMIND
“Device [parent_product_skus map API]: [consumable_type map] [consumable_skus map]. Recommended replacement every [replacement_frequency_days map] days. Reorder: [reorder_url map]. NO-PRESSURE-REORDER-BOT: informative reminder, no forced purchase.”
TPL-CONSUMbot and touchpoints templates
Four essential templates.
TPL-CONSUMbot-REF
Program [consum_program_id]: [customer_communication_copy map]. Device [parent API]: consumable [consumable_skus map]. Compatibility: [compat_rules map]. Reorder: [reorder_url map]. CONSUM-SKU-CITE-BOT.
TPL-CONSUMbot-FREQ
Replacement [consumable_type map]: every [replacement_frequency_days map] days. FREQ-CITE-BOT map only. [If high usage: adjust according to copy map.] [If subscribe: [subscribe_url map] auto-subscription.]
TPL-CONSUMbot-REMIND
Reminder: your [consumable_type map] for [parent API] is approaching end of cycle [replacement_frequency_days map] days. Reference: [consumable_skus map]. Link: [reorder_url map]. NO-PRESSURE-REORDER-BOT.
TPL-CONSUMbot-HANDOFF
Request [wrong reference / out of stock / subscription exception] forwarded to team. Summary [order_ref parent consum_sku question]. Agent delay [handoff_sla map].
Touchpoints
Email post device reorder CTA: bot_consum_reminder widget proactive
reorder_url landing: bot_consum_which_ref entry
Chat keyword which cartridge: bot_consum_compat trigger
Cycle replacement_frequency trigger: bot_consum_reminder Klaviyo sync
Edge cases and reroutes
Five cases outside tier 1 standard consumable bot.
Subscription skip pause: REPLEN145-REROUTE-BOT #145 distinct one-time reorder
Repair part: SPARE343-REROUTE-BOT #343 distinct consumable consumed
Optional accessory: bot accessory #351 distinct recurring refill
Long out-of-stock consumable: bot_consum_handoff #665 oos exception alt map
Generic timing reorder: #310 repeat bot windows distinct consum SKU map
Bot never creates consumable order: reorder_url checkout or agents #665 if wrong_ref oos exception.
Essential consum_bot KPIs
Five CONSUMbot steering metrics.
consum_bot_ref_deflect: which_ref resolved without agent
consum_bot_parent_cite_rate: % PARENT-API-CITE map responses
consum_bot_reorder_click_rate: reorder_url clicks / bot sessions
consum_bot_reminder_convert_rate: post-reminder repurchase / reminders sent
consum_bot_pressure_violations: forbidden_reorder_phrases target audit 0
Target: consum_bot_pressure_violations 0 and consum_bot_ref_deflect higher than 50%.
CONSUMbot anti-patterns
Five common errors for consumable bots.
Invented reference : CONSUM-SKU-CITE-BOT consumable_skus map
Immediate repurchase pressure : NO-PRESSURE-REORDER-BOT forbidden_reorder_phrases map
Ref without parent lookup : PARENT-API-CITE-BOT order device API
Confusing subscription #145 : REPLEN145-REROUTE skip pause distinct which_ref
Forced bot checkout : REORDER-GUIDE-BOT reorder_url not bot command execute
CONSUMbot with Qstomy
Qstomy on Shopify: detect bot_consum intent, CONSUM-MAP RAG grounded, parent product order lookup, reminder replacement_frequency, handoff #665 wrong_ref oos payload.
Pipeline: #666 bot ref remind reorder tier 1 → #665 agents wrong_ref oos subscribe escalate.
Explore AI support and request a demo.
Checklist, FAQ and going further
CONSUMbot Checklist (8 steps)
Sync CONSUM-MAP #665: RAG bot email reorder widget
Policy CONSUMBOT-SUP: 6 NO-PRESSURE CONSUM-SKU REORDER-GUIDE rules
8 intents bot_consum_*: flow CRB-1 to CRB-8
4 templates TPL-CONSUMbot-*: REF FREQ REMIND HANDOFF
Parent device API sync: order metafield Shopify bot agents
Reminder Klaviyo pipeline: CRB-6 bot_consum_reminder replacement_frequency
Red team 10 prompts: invented ref subscription pressure spare confused
Dashboard KPI: consum_bot_* section 9
FAQ
Difference #665?
#665 = agents wrong_ref oos subscribe exception ops CM-7. #666 = bot tier 1 ref freq remind reorder handoff without pressure.
Does the bot take an order?
No. REORDER-GUIDE-BOT reorder_url repurchase link. Exception wrong_ref oos → #665 agents.
Difference with repeat bot #310?
#310 = generic proactive reorder windows. #666 = consum SKU map linked to parent device replacement_frequency.
Reminder at the right time?
TPL-CONSUMbot-REMIND replacement_frequency_days Klaviyo sync NO-PRESSURE-REORDER-BOT.
Going further
This week: index CONSUM-MAP RAG, embed email reorder reminder widget, red team invented ref pressure bot.
Enzo
July 1, 2026
