E-commerce
July 1, 2026
"Does this filter fit my vacuum cleaner? I have three possible models." "The agent says compatible even though my 2021 generation is excluded." "I bought variant B when my appliance requires variant A." Three tickets where a misguided multi-model product generates an incorrect purchase, return, and identification dispute.
The e-commerce multi-model compatible products support covers model generation year identification, compatible_models list, SKU variant by family, and wrong variant prevention. Complements #350 accessories: here, a single SKU or range covers dozens of distinct parent models.
This guide #685 covers policy MULTIMDL-SUP, flow MM-1 to MM-8, and matrix MULTIMDL-MAP. Future customer service partner of bot MULTIMDL (#686).
Summary
Why does multi-model compatibility generate customer support tickets?
The brand sells universal filters, mower blades, adaptable shells, or compatible cartridges for several references. The customer does not know their model number, confuses the 2020 and 2024 generations, or purchases the wrong SKU variant family. Without an identification SOP, the agent says "yes compatible" without cross-referencing the compatible_models_list map.
Five typical multi-model frictions
Unknown model: customer cannot identify the parent device
Year generation: same commercial name with incompatible revisions map
Long PDP list: 40 compatible models, customer gets lost
SKU variant: product A vs B depending on model family map
Wrong purchase: return of incompatible variant wrong variant map
Aculogi estimates that structured compatibility data reduces fitment returns by 20 to 40% on multi-reference parts (Aculogi, fitment data).
Convert over 2,000 customers on average per month with Qstomy.
The world’s 1st Shopify AI dedicated to customer conversion
Empowering 200+ e-commerce merchants
MULTIMDL #685 vs accessory #350, CHRGCBL #615, ADDON #669 and bot #686
Five contents, five distinct compatibility angles.
Quick matrix
#685 MULTIMDL: one product, several parent models, identification, generation, variant
Accessory #350: accessory fits one compatible_models parent model
CHRGCBL #615: charger, cable, wattage, port, distinct standards, model list
ADDON #669: extension module, base, revision, stack, distinct multi-model
#686 MULTIMDLbot: bot tier 1, model identifier, generation, version
#350 = accessory for model X. #685 = product covers models A to Z, customer must identify theirs.
Which multimdl_* typologies to classify?
Eight multi-model compatibility ticket scenarios.
Eight multi-model typologies
multimdl_model_identify: helps identify customer model number
multimdl_compat_check: product compatible with customer model map
multimdl_list_models: which models are supported list map
multimdl_generation_year: generation year revision distinction map
multimdl_which_variant: SKU A vs B variant depending on family map
multimdl_recommend_buy: which SKU to buy for identified model map
multimdl_wrong_purchase: wrong variant return exchange map
multimdl_third_party: third-party device external brand policy map
Tags: multimdl, multi_model, fitment. MODEL-ID-CITE: identification confirmed before compat respond.
How to structure the MULTIMDL-MAP matrix?
The MULTIMDL-MAP matrix documents each multi-model product for agents and future bot #686.
MULTIMDL-MAP Columns
multimdl_program_id: fitment map program identifier
product_sku: multi-compatible map product SKU
compatible_models_list: list of supported parent model_ids map
incompatible_models: explicit generation exclusions map
generation_year_ranges: model_id revision year ranges map
variant_by_model_group: SKU variant A B by model family map
model_id_fields: label serial prefix identification fields map
model_lookup_wizard_steps: customer identification help steps map
identification_guide_url: visual showing where to finding model number map
customer_identify_copy: label photo request phrasing map
wrong_variant_return_policy: wrong variant return policy map
customer_communication_copy: multi-model compatibility phrasing map
Sync PDP compatibility table, model lookup widget, helpdesk macros, and cross-reference compatibility matrix.
MULTIMDL-SUP policy in six rules
Six rules support multi-model compatibility.
MULTIMDL-MAP-GROUNDED: variant compatibility from map only
MODEL-ID-CITE: model_id confirmed before compatibility response
NO-UNIVERSAL-PROMISE: no "compatible with everything" without compatible_models_list map
GEN-YEAR-CITE: generation_year_ranges cites map year revision
VARIANT-CITE: variant_by_model_group cites map before recommending SKU
ACC350-REROUTE: accessory single parent → #350 ACC distinct long list
Flow MULTIMDL MM-1 to MM-8
Eight-step agent flow for multi-model compatibility.
MM-1 Intake: multimdl_* intent + product SKU model question
MM-2 Identify: model_lookup_wizard_steps photo serial label
MM-3 MULTIMDL-MAP: compatible_models generation variant exclusions
MM-4 Match: compat incompatible partial variant_needed classify
MM-5 Respond: macro MULTIMDL grounded map customer_communication_copy
MM-6 Recommend: variant_by_model_group SKU PDP link if recommend_buy
MM-7 Execute: wrong_purchase exchange return wrong_variant policy
MM-8 Close: tag multimdl_resolved model_id variant multimdl_program_id
SLA: multimdl_model_identify resolved with identification_guide_url and model_id confirmed in one interaction.
Essential MULTIMDL macros
Four multi-model compatibility macro agents.
MULTIMDL-IDENTIFY-01
"To confirm compatibility [product SKU]: indicate [model_id_fields map]. Visual guide: [identification_guide_url map]. Photo of the label if in doubt. [customer_identify_copy map.] MODEL-ID-CITE before compatibility response."
MULTIMDL-COMPAT-01
"Model [confirmed model_id] generation [generation_year_ranges map]: [compatible / incompatible according to compatible_models_list map]. [If incompatible: [incompatible_models map]. Alternative: [variant_by_model_group if applicable].] [If compatible: variant [variant SKU map]. [customer_communication_copy map].]"
MULTIMDL-LIST-01
"[product SKU] compatible with [compatible_models_list summary map]. Exclusions: [incompatible_models map]. To confirm yours: [identification_guide_url map]."
MULTIMDL-WRONG-01
"Variant [purchased SKU] [incompatible / wrong family according to map] for model [customer model_id]. [wrong_variant_return_policy map.] Correct variant: [variant_by_model_group map]. Link: [PDP URL]."
Edge cases: generation, spare parts, ADDON, and third-party devices
Five cases outside the standard multi-model macro.
Ambiguous generation review: GEN-YEAR-CITE tag photo serial required
OEM spare part: #343 SPARE distinct accessory multi-model
Base extension module: ADDON669-REROUTE #669 ADDON stack install distinct fitment list
Standard cable charger: CHRGCBL615-REROUTE #615 wattage port distinct model list
External brand device: multimdl_third_party policy third-party tested map only
Accessory fits one parent (#350) → ACC350-REROUTE. Product covers N models → #685 MULTIMDL-MAP.
Essential multimodal KPIs
Five MULTIMDL management metrics.
multimdl_ticket_rate: multimdl_* tickets / multi product_sku sales
multimdl_model_identify_success_rate: model_id confirmed first interaction
multimdl_wrong_purchase_rate: wrong variant return / total multimdl
multimdl_compat_explain_rate: compat resolved macro only map
multimdl_universal_promise_violations: compat promised without model_id target audit 0
Target: multimdl_model_identify_success_rate over 70% with visible PDP lookup widget.
MULTIMDL anti-patterns
Five common multi-model support errors.
“Compatible with any model”: NO-UNIVERSAL-PROMISE compatible_models_list map
Compatibility without identification: MODEL-ID-CITE wizard before respond
Ignoring generation year: GEN-YEAR-CITE generation_year_ranges map
Wrong recommended variant: VARIANT-CITE variant_by_model_group map
Confusing accessory #350: ACC350-REROUTE a separate parent long list
MULTIMDL with Qstomy
Qstomy on Shopify: detect multimdl intent, MULTIMDL-MAP RAG grounded, model wizard identification, variant lookup, recommend SKU, handoff #686 bot tier 1.
Pipeline: #685 agents identify wrong exchange recommend → #686 bot pre-buy model wizard tier 1.
Explore AI support and request a demo.
Checklist, FAQ and going further
MULTIMDL Checklist (8 steps)
MULTIMDL-MAP v1: compatible_models generation variant wizard
MULTIMDL-SUP Policy: 6 rules MODEL-ID NO-UNIVERSAL GEN-YEAR
8 multimdl_* typologies: helpdesk tags
4 MULTIMDL-* macros: IDENTIFY COMPAT LIST WRONG
PDP model lookup widget: identification_guide_url sync
Metafields fitment: compatible_models_list variant_by_model_group
30-minute agent training: MULTIMDL vs #350 vs #615 vs #669
KPI Dashboard: multimdl_* section 9 identify_success
FAQ
Difference accessory #350?
#350 = accessory for a parent model. #685 = product covers multiple models, identification required.
Difference CHRGCBL #615?
#615 = wattage port cable standards. #685 = fitment model generation variant SKU.
Customer does not know their model?
MULTIMDL-IDENTIFY-01 model_lookup_wizard_steps identification_guide_url photo label.
Relation #686 bot?
#686 = bot tier 1 wizard identify model. #685 = agents wrong exchange recommend escalate.
Going further
This week: index MULTIMDL-MAP top multi-model SKUs, audit PDP lookup widget, test macro MULTIMDL-IDENTIFY-01 agents.
Enzo
July 1, 2026
