E-commerce
July 1, 2026
"The bot says compatible without asking for my 2022 generation." "The AI recommends variant A when my device requires variant B." "Chatbot validates the purchase even though my model is in incompatible_models." Three failures where a miscalibrated multi-model bot over-promises compat, improvises identification, or ignores the generation_year_ranges map.
An e-commerce multi-model compatibility AI chatbot does not replace MULTIMDL agents (#685). It reads MULTIMDL-MAP, guides wizard model_lookup_wizard_steps, gates compat before recommend, and handoffs wrong variant exchange to humans.
This guide #686 covers intents bot_multimdl_*, flow MULTIMDLbot, and KPI multimdl_bot. Companion bot of the MULTIMDL playbook (#685). AI use case: identify model generation version before confirming compat.
Summary
Why automate multi-model compatibility using a bot?
"Does this filter fit my device?", "how do I find my model number?", and "which variant should I buy?" recurring PDP cart FAQ. A calibrated wizard identification bot, cites compatible_models_list generation_year_ranges variant_by_model_group without "compatible with everything" or invented variant.
What the bot solves tier 1 multi-models
Model wizard: model_lookup_wizard_steps identification
Compat gate: compatible_models_list match before yes
Generation year: generation_year_ranges cite map
Variant recommend: variant_by_model_group COMPAT-GATE
Cart filter: block wrong variant checkout
Aculogi points out that structured fitment data reduces wrong accessory returns when model identification is guided before purchase (Aculogi, fitment data).
MULTIMDLbot vs MULTIMDL #685, accessory #351, CHRGCBLbot #616 and ADDONbot #670
Five contents, five distinct compatibility angles.
Quick matrix
#686 MULTIMDLbot: tier 1 bot wizard identify compat gate recommend handoff
#685 MULTIMDL: agents wrong exchange recommend MM-7 escalate
Accessory bot #351: case filter a single parent model_id distinct long list
CHRGCBLbot #616: wattage port cable distinct standards fitment model
ADDONbot #670: extension module base stack distinct multi-model list
Pipeline: #686 bot wizard identify recommend tier 1 → #685 agents wrong exchange escalate post-purchase.
Which bot_multimdl_* intents should be configured?
Eight multi-model bot intents mapped to multimdl_* typologies #685.
Eight bot_multimdl intents
bot_multimdl_identify: wizard model_id_fields identification guide
bot_multimdl_compat_check: compatible_models_list match map
bot_multimdl_list_models: compatible_models summary map
bot_multimdl_generation: generation_year_ranges distinction map
bot_multimdl_which_variant: variant_by_model_group A vs B map
bot_multimdl_recommend: SKU recommend COMPAT-GATE map
bot_multimdl_cart_filter: block wrong variant cart checkout
bot_multimdl_handoff: wrong purchase exchange u2192 #685
Tier 1 auto: identify, compat, generation, which_variant, recommend, cart_filter if MULTIMDL-MAP + guardrails.
bot_multimdl_handoff wrong variant complex return u2192 agents #685 payload model_id order_ref variant.
How should MULTIMDL-MAP #685 be consumed?
The bot reads MULTIMDL-MAP #685: multimdl_program_id, product_sku, compatible_models_list, incompatible_models, generation_year_ranges, variant_by_model_group, model_id_fields, model_lookup_wizard_steps, identification_guide_url, customer_identify_copy, wrong_variant_return_policy, customer_communication_copy.
Lookup grounded
WIZARD-GROUNDED-BOT: model_lookup_wizard_steps map only, not invented
MODEL-ID-CITE-BOT: model_id confirmed before compat respond
COMPAT-GATE-BOT: do not recommend without compatible_models_list match
GEN-YEAR-CITE-BOT: generation_year_ranges cite map revision
VARIANT-CITE-BOT: variant_by_model_group cite map only
NO-UNIVERSAL-BOT: not compatible with everything without compatible_models_list
NO-EXCHANGE-BOT: wrong variant exchange handoff #685 only
ACC350-REROUTE-BOT: accessory a parent → #351 ACCbot distinct list
MULTIMDL685-HANDOFF-BOT: wrong exchange → #685 agents MM-7
Alignment anti-hallucination (#123): compat variant = MULTIMDL-MAP whitelist only.
MULTIMDLBOT-SUP Policy in six rules
Six bot rules for secure multi-model compatibility.
MULTIMDL-MAP-GROUNDED-BOT: variant compat from map only
MODEL-ID-CITE-BOT: wizard complete before compat recommend
COMPAT-GATE-BOT: lookup before recommend cart add
NO-UNIVERSAL-BOT: not compatible with any model without list map
GEN-YEAR-CITE-BOT: generation_year_ranges before yes ambiguous generation
NO-EXCHANGE-BOT: wrong purchase exchange agents #685 never bot alone
Flow MULTIMDLbot MMB-1 to MMB-8
Eight-step multi-model compatibility bot flow.
MMB-1 Classify: bot_multimdl_* intent detect PDP cart FAQ
MMB-2 Collect: product SKU context model hint photo label
MMB-3 Wizard: model_lookup_wizard_steps identification_guide_url
MMB-4 MULTIMDL-MAP: compatible generation variant exclusions
MMB-5 Guardrail: MODEL-ID COMPAT-GATE GEN-YEAR VARIANT NO-UNIVERSAL
MMB-6 Respond: TPL-MULTIMDLbot grounded customer_communication_copy
MMB-7 Recommend or block: variant SKU or cart_filter warn
MMB-8 Log handoff: intent model_id variant tag multimdl_bot handoff Y/N
Example TPL-MULTIMDLbot-COMPAT
"Model [confirmed model_id] generation [generation_year_ranges map]: [compatible / incompatible according to compatible_models_list map]. Variant: [variant_by_model_group map]. [customer_communication_copy map.] MODEL-ID-CITE-BOT map only."
TPL-MULTIMDLbot and touchpoint templates
Four essential templates.
TPL-MULTIMDLbot-IDENTIFY
For [product SKU]: indicate [model_id_fields map]. Steps: [model_lookup_wizard_steps map]. Guide: [identification_guide_url map]. [customer_identify_copy map.] Label photo if in doubt.
TPL-MULTIMDLbot-COMPAT
Model [model_id] generation [generation_year_ranges]: [compatible / incompatible map]. [incompatible_models if applicable.] Recommended variant: [variant_by_model_group map]. COMPAT-GATE-BOT.
TPL-MULTIMDLbot-RECOMMEND
For model [model_id confirmed]: SKU [variant_by_model_group map]. [customer_communication_copy map.] PDP Link: [url]. VARIANT-CITE-BOT map only.
TPL-MULTIMDLbot-BLOCK
Variant [cart SKU] incompatible with model [model_id]: [incompatible_models map]. Remove from cart or choose [correct variant_by_model_group map]. Active cart_filter.
Touchpoints
Model lookup PDP widget: bot_multimdl_identify proactive
Long PDP compatibility table: bot_multimdl_list_models assist
Cart variant check: bot_multimdl_cart_filter gate
Model compatible chat keyword: bot_multimdl_compat_check trigger
Edge cases and reroutes
Five non-tier 1 standard multi-model bot cases.
Wrong purchase return: NO-EXCHANGE-BOT MULTIMDL685-HANDOFF-BOT #685 MM-7
Accessory single parent: ACC350-REROUTE-BOT #351 distinct fit single model
Charger cable standards: CHRGCBL616-REROUTE-BOT #616 wattage port distinct
Base extension module: ADDON670-REROUTE-BOT #670 stack install distinct
Ambiguous generation photo required: wizard pause GEN-YEAR-CITE-BOT before yes
Bot never executes exchange return: wrong variant → agents #685 MULTIMDL-WRONG-01.
Essential multimodal bot KPIs
Five MULTIMDLbot steering metrics.
multimdl_bot_identify_deflect : wizard identify resolved without agent
multimdl_bot_model_id_cite_rate : MODEL-ID-CITE-BOT / bot_multimdl_compat
multimdl_bot_universal_violations : compatible all promised audit target 0
multimdl_bot_wrong_variant_block_rate : cart_filter blocked / checkout multi SKU
multimdl_bot_exchange_execute_violations : exchange bot alone audit target 0
Target: multimdl_bot_universal_violations 0 and multimdl_bot_identify_deflect greater than 55%.
MULTIMDLbot anti-patterns
Five common multi-model bot errors.
Compatible without identification: MODEL-ID-CITE-BOT wizard before yes
Compatible with all promised: NO-UNIVERSAL-BOT compatible_models_list map
Invented variant: VARIANT-CITE-BOT variant_by_model_group map
Generation ignored: GEN-YEAR-CITE-BOT generation_year_ranges map
Confusing accessory #351: ACC350-REROUTE a distinct parent long list
MULTIMDLbot with Qstomy
Qstomy on Shopify: detect bot_multimdl intent, MULTIMDL-MAP RAG grounded, wizard model identification, COMPAT-GATE variant recommend, cart filter, handoff #685 wrong exchange.
Pipeline: #686 bot wizard identify recommend tier 1 → #685 agents wrong exchange escalate.
Explore AI support and request a demo.
Checklist, FAQ and going further
MULTIMDLbot Checklist (8 steps)
Sync MULTIMDL-MAP #685: RAG bot PDP widget lookup
Policy MULTIMDLBOT-SUP: 6 rules MODEL-ID COMPAT-GATE NO-UNIVERSAL
8 intents bot_multimdl_*: flow MMB-1 to MMB-8
4 templates TPL-MULTIMDLbot-*: IDENTIFY COMPAT RECOMMEND BLOCK
PDP widget wizard embed: model_lookup_wizard_steps sync
variant_by_model_group index: RAG grounded variants audit
Red team 10 prompts: compat without model_id universal promised invented variant
Dashboard KPI: multimdl_bot_* section 9
FAQ
Difference #685?
#685 = agents wrong exchange MM-7 escalate. #686 = bot tier 1 wizard identify recommend handoff.
Difference accessory bot #351?
#351 = accessory fits a parent model. #686 = multi-model product wizard identification long list.
Bot exchanges wrong variant?
No. NO-EXCHANGE-BOT TPL-MULTIMDLbot handoff #685 wrong_variant_return_policy.
Customer doesn't know the model?
TPL-MULTIMDLbot-IDENTIFY wizard model_id_fields identification_guide_url label photo.
Going further
This week: index MULTIMDL-MAP RAG wizard steps, embed PDP lookup widget, red team universal promised bot violations.
Enzo
July 1, 2026
