E-commerce
July 1, 2026
"Why does the bot send me back to the manufacturer without opening a ticket?" "The AI says 5 years manufacturer, your site says 2 years, who should I contact?" "I bought it here, the chatbot refuses to help me and cites an external RMA portal." Three bot failures where the AI incorrectly routes between manufacturer vs shop or promises an unfounded manufacturer warranty.
An e-commerce manufacturer warranty AI chatbot does not replace MFGW-FLOW agents (#455). It reads MFGW-MAP, explains three schemes, routes to shop claim #62 or manufacturer portal, blocks direct return to manufacturer, and hands off to an agent if manufacturer_refusal or dispute occurs.
This guide #456 covers intents bot_mfgw_*, flow MFGW-BOT, and KPI mfgw_bot. Separate from shop manufacturer after-sales service (#455) and coverage bot (#349): here, AI use case for directing internal support vs manufacturer without routing overpromise.
Summary
Why automate manufacturer warranty routing using a bot?
A bot that returns “contact the manufacturer” without specifying the seller's legal warranty reproduces the worst customer service anti-pattern and generates “brand shifts responsibility” reviews.
Volume and cost of poorly routed mfgw
On authorized electronics and appliance retailer sites, manufacturer vs. store warranty tickets rank in the top 6 post-delivery issues. Each incorrect routing costs 12 to 20 minutes of agent re-qualification time. A grounded MFGW-MAP bot filters 55% to 70% of simple routing questions.
Three risks of an unstructured mfgw bot
Abusive redirect: manufacturer RMA link without a store file
Regime confusion: 2-year legal warranty vs. 5-year instructions mixed up
Empty handoff: agent asks MF-1 intake again without payload
US Tech Automations estimates that automating warranty qualification and routing reduces processing time by approximately 70% (US Tech Automations, warranty 2026). Service-Public points out that the 2-year legal warranty is the responsibility of the seller (Service-Public, legal warranty 2026).
Angle #456 vs. neighboring content
Customer Service #455: MFGW-FLOW agents. #456 = AI routing layer.
Bot coverage #349: policy exclusions. #456 = manufacturer-store point of contact.
Marketplace #355: purchasing channel. #456 = MB-2 gate then mfgw DTC.
Claim #62: store portal. #456 = route before claim open.
Diagnosis #342: identifies malfunction. #456 = post-confirmed defect or in parallel.
DTC authorized retailer example
Electronics, 74 mfgw tickets/month, generic warranty bot achieves 41% abusive redirect rate. After MFGW-BOT + guardrails: mfgw_bot_auto_resolve 58%, mfgw_bot_route_accuracy 94%, mfgw_bot_abusive_redirect 0, CSAT mfgw bot 4.5/5.
Bot informs and routes, does not settle the claim
MFGW-BOT-SUP: probable eligibility, grounded routing, never promising “manufacturer guaranteed replacement” without an agent-validated ticket.
Post-holidays bot capacity
Peak bot_mfgw sessions January-February: scale NO-REDIRECT review capacity before the post-gift warranty confusion wave.
Electronics bot density
Highest mfgw_bot_session_rate vertical: preload duration_conflict and store_first templates for top SKUs.
How does MFGW-BOT differ from warranty bot #349 and SAV #455?
General coverage, contact routing, and agent playbook: three distinct warranty layers.
Role → content matrix
#456 MFGW-BOT: manufacturer boutique routing, portal link, no redirect guard
#349 warranty bot: legal coverage extension exclusions
#455 MFGW-FLOW: MF-1 to MF-8 agents execute
#348 EXT-WAR: parallel extension checkout
#355 MP-WAR: marketplace handoff channel
Shared MFGW-MAP corpus
#455 publishes MFGW-MAP JSON. #456 bot consumes the same source: durations, routing_type, portal_url, registration_required. Sync version mandatory.
Four BOT-MFGW-TYPE flows
bot_mfgw_regime_explain: three automatic MFGW-REGIME schemes
bot_mfgw_store_route: open claim #62 prefill
bot_mfgw_manufacturer_route: portal RMA link + proofs
bot_mfgw_escalate: refusal, hostile, grey import dispute
Promise #456
Policy MFGW-BOT-SUP, 12 intents bot_mfgw_*, flow MFGW-BOT MB-1 to MB-8, guardrails, handoff payload, KPI mfgw_bot_*.
Pipeline warranty stack
#342 diagnostic → #456 routing → #62 claim or portal → #455 agent if escalation. #349 coverage in parallel pre-purchase PDP.
Warranty billing bot stack
Shopify order context, MFGW-MAP JSON RAG, Qstomy intents bot_mfgw_*, guardrails NO-REDIRECT, claim #62 API prefill, Gorgias handoff payload, MP-WAR #355 webhook.
Which bot_mfgw_* intents should be classified?
Twelve manufacturer warranty bot intents before MFGW-BOT flows.
Twelve bot_mfgw intents
bot_mfgw_who_responsible: who to contact post-breakdown
bot_mfgw_duration_conflict: 2 years site vs manufacturer instructions
bot_mfgw_store_first: store must open file
bot_mfgw_manufacturer_portal: manufacturer RMA link
bot_mfgw_intermediary: store collects transfers
bot_mfgw_registration: manufacturer warranty registration
bot_mfgw_proof_checklist: invoice, serial number, photo required
bot_mfgw_legal_seller: 2-year legal seller warranty
bot_mfgw_manufacturer_refusal: manufacturer rejected
bot_mfgw_grey_unauthorized: parallel import unauthorized reseller
bot_mfgw_pre_purchase: who guarantees if I buy here
bot_mfgw_brand_dtc_single: brand = manufacturer = seller
Required bot session fields
order_id, sku, purchase_date, purchase_channel, serial_number, defect_summary, mfgw_regime_hypothesis, routing_type_map, registration_status, manufacturer_rma_if_any, escalation_reason.
Distinction with #349 intents
warranty_coverage_* (#349) = eligibility exclusions. bot_mfgw_* (#456) = routing interlocutor. Bot routes #349 first if regime is unknown, then #456 if who_responsible.
Bot verbatims mining
90-day chat export "manufacturer", "maker", "RMA", "sent back", "5 years", "who guarantees". Prioritize flows for 80% volume of top 20 MFGW-MAP SKUs.
Confidence threshold routing
Intent confidence below 0.75: bot asks clarifying question before MB-4 map lookup. No route on ambiguous manufacturer maker typo.
How does the bot consume MFGW-MAP #455?
The bot does not reinvent durations: it reads the MFGW-MAP matrix documented in #455.
Lookup MB-4 bot
sku → routing_type: store_first, manufacturer_direct, dual, brand_dtc
legal_warranty_months: quotes seller 24 standard
manufacturer_warranty_months: quotes grounded manual
manufacturer_portal_url: RMA link if route authorized
registration_required: triggers bot_mfgw_registration
store_intermediary: bot_mfgw_intermediary copy
authorized_dealer: blocks manufacturer commercial if N
proof_required[]: checklist bot_mfgw_proof
RAG corpus MFGW-MAP
Chunks by SKU range + FAQ /pages/warranty-coverage. Bot quotes source chunk_id. Duration hallucination = P1 incident. See anti-hallucination (#208).
Quarterly sync version
MFGW-MAP changelog: bot deployed after merch legal sign-off #455. Stale map = mfgw_bot_route_accuracy drops.
PDP warranty block ingest
Product page warranty block indexed by bot. Customer quotes PDP, bot confirms same MFGW-MAP durations.
Shopify order context
MB-3 reads order SKU date channel. Marketplace order tag → MP-WAR handoff #355, stop MFGW-BOT DTC.
Chunk_id citation audit
Weekly sample 20 bot_mfgw transcripts verify chunk_id MFGW-MAP matches cited durations. Zero tolerance for hallucination.
Shopify warranty Metafields
SKU metafields warranty_routing mirror MFGW-MAP for MB-4 fallback if RAG timeout occurs under 2 s SLA.
How to write the MFGW-BOT-SUP policy in eight rules?
The MFGW-BOT manufacturer warranty policy governs AI routing without abusive redirection or premature manufacturer promises.
Eight MFGW-BOT-SUP rules
Legal seller first bot: never manufacturer portal alone without explaining the seller's 2-year legal warranty
MFGW-MAP only: routing durations from JSON, zero invent
Regime before route: bot_mfgw_regime explain before portal link
No abusive redirect guard: block manufacturer_portal_url if store_first and legal applicable
Authorized dealer gate: no commercial manufacturer promise if authorized_dealer N
Canal gate MB-2: marketplace → MP-WAR #355 before mfgw
Escalate refusal hostile: bot_mfgw_manufacturer_refusal → agent #455 supervisor
Handoff payload complete: MF-1 fields prefill agent, no repeat intake
Anti-overpromise routing
Bot says "probable routing to commercial manufacturer, store case recommended first" not "confirmed manufacturer warranty".
Overlap #349 guardrails
Same anti-overpromise warranty family #349. MFGW-BOT adds specific manufacturer no_redirect_guard.
Grey import bot response
bot_mfgw_grey_unauthorized: 24-month store legal warranty explain, commercial manufacturer exclusion grounded. Escalate if customer disputes.
Legal review bot templates
Marketing legal approve TPL-MFGW-REGIME and TPL-MFGW-DURATION before production. DGCCRF abusive redirect pattern audit quarterly.
How to apply the MFGW-BOT flow in eight steps?
The MFGW-BOT MB-1 to MB-8 flow structures the qualification bot routing grounded MFGW-MAP.
Eight steps MB-1 to MB-8
MB-1 Intent classify: bot_mfgw_* typology section 3
MB-2 Canal gate: marketplace order ? handoff MP-WAR #355 stop
MB-3 Order context: Shopify order_id SKU date serial if known
MB-4 MFGW-MAP lookup: routing_type durations portal proof
MB-5 Regime respond: MFGW-REGIME template three regimes
MB-6 Branch route: store claim | portal link | intermediary | brand_dtc | escalate
MB-7 Execute: claim prefill #62 | portal URL | collect proof | handoff agent
MB-8 Log: intent, routing_chosen, map_version, auto_resolved, handoff Y/N
MB-6 store_first branch
Bot opens claim pathway #62 prefill order SKU. Mentions potential manufacturer transfer post-24 months if dual map. No portal link yet if legal window.
MB-6 manufacturer_direct branch
After MB-5 regime: portal URL + proof checklist. Bot remains available "if blocked reach back out to us". Log manufacturer_route Y.
MB-6 manufacturer_refusal escalate
Customer references manufacturer refusal: bot_mfgw_manufacturer_refusal → handoff agent MFGW-REFUSAL-01 payload MF-8 fields.
MB-6 brand_dtc shortcut
routing brand_dtc: skip external portal, MB-7 direct claim #62 single interlocutor.
MB-7 proof collection
Bot collects photo defect serial invoice chat upload before handoff. Payload attachments[] agent file.
MB-5 before MB-6 sequence
Compliance audit: regime template always fires before route branch. Violations = disable portal template 24 h hotfix.
SLA bot response mfgw
MB-5 regime respond under 8 s target. Handoff agent manufacturer_refusal under 60 s escalate path.
Which bot templates and guardrails should be configured?
Eight MFGW bot templates and no abusive redirect guardrails.
TPL-MFGW-REGIME (three regimes)
« Three guarantees: (1) 2-year legal seller [store], (2) store commercial [X months], (3) manufacturer commercial [Y months]. Your purchase [date]: applicable regime [regime]. »
TPL-MFGW-STORE (store first)
« As the seller we handle your legal warranty. Opening case: [link claim #62 prefill]. Proof required: [proof_required]. »
TPL-MFGW-PORTAL (manufacturer routing)
« Manufacturer commercial warranty: procedure [URL portal]. Proof required: [list]. We remain available if blocked within 48 hours. »
TPL-MFGW-INTERMEDIARY
« We collect the product and transfer to authorized manufacturer service. Estimated time [X days]. Start store case: [claim link]. »
TPL-MFGW-DURATION
« 2 years site = EU seller legal warranty. [Y] years manual = manufacturer commercial warranty under packaging conditions. Coexist, contact person depending on the period. »
Guardrail NO-REDIRECT-01
Block TPL-MFGW-PORTAL if store_first + purchase within legal_warranty_months + no agent override. Force TPL-MFGW-STORE first.
Guardrail AUTH-DEALER-01
Block commercial manufacturer template if authorized_dealer N. TPL legal + escalate grey.
Bot Touchpoints
PDP chip « Who guarantees? » bot_mfgw_pre_purchase
Post-purchase email D+7 registration_required link
Claim portal #62 bot widget MB-3 context
Help center /pages/warranty-coverage bot RAG
Portal link click tracking
UTM mfgw_bot_portal on manufacturer_portal_url. Dashboard correlate click vs handoff complaint portal broken.
Which RMA portal, refusal, and pre-purchase cases should be processed?
Special bot mfgw cases require escalation or guardrail override supervisor.
Portal RMA dead link or SSO
Customer reports portal error: bot logs incident, handoff agent with manufacturer_portal_url + screenshot. Merchant fixes MFGW-MAP URL.
Registration out of time
bot_mfgw_registration: commercial manufacturer refused. Bot quotes legal 24-month seller unchanged. No blame customer tone.
Manufacturer refusal return
bot_mfgw_manufacturer_refusal: never "contact manufacturer again" loop. Escalate agent MFGW-REFUSAL #455 P1.
Pre-purchase who guarantees
bot_mfgw_pre_purchase: TPL-MFGW-REGIME + PDP link. Conversion angle warranty objections (#227).
Overlap diagnostic #342
Unconfirmed defect: route troubleshooting #342 first. bot_mfgw routing after qualified failure.
Overlap extension #348
Customer mentions checkout extension: parallel intent warranty_coverage_ext #349, MFGW-BOT does not merge EXT-WAR policy.
Hostile review threat
Abusive review threat post redirect: escalate supervisor empathy, open store claim even if manufacturer_direct eligible.
Wholesale B2B detect
Order tag wholesale: route wholesale (#144) not bot_mfgw consumer.
Serial number validation MB-3
Bot validates serial format regex per SKU MFGW-MAP before manufacturer_direct route. Invalid serial → collect photo label escalate.
Which mfgw_bot KPIs should be measured?
The manufacturer warranty bot KPIs link routing accuracy, auto-resolve and zero abusive redirect.
Eight key metrics
mfgw_bot_session_rate: bot_mfgw sessions / 100 orders SKU mapped
mfgw_bot_auto_resolve: resolved without agent / mfgw sessions
mfgw_bot_route_accuracy: routing compliant with MFGW-MAP / routed sessions
mfgw_bot_abusive_redirect: portal without store explain / sessions (target 0)
mfgw_bot_claim_open_rate: claim #62 opened post bot store route
mfgw_bot_handoff_rate: agent escalation / sessions
mfgw_bot_map_hallucination: fictional routing duration / sessions (target 0)
mfgw_bot_csat: satisfaction post bot_mfgw session
DTC bot mfgw benchmark
mfgw_bot_auto_resolve 50-65%, mfgw_bot_route_accuracy > 92%, mfgw_bot_abusive_redirect 0, mfgw_bot_csat > 4.3/5.
Weekly bot ops dashboard
Intent breakdown, branch MB-6, handoff reason, map_version stale alerts, portal link click-through.
A/B NO-REDIRECT guardrail
4 weeks guardrail ON vs OFF: measure mfgw_bot_abusive_redirect and mfgw_bot_csat lift.
mfgw_bot_handoff quality score
Agent rates handoff payload completeness 1-5. Target average 4.2+ post MB-7 proof collection deploy.
Segmentation by routing_type bot
Dashboard mfgw_bot_auto_resolve per store_first vs manufacturer_direct vs brand_dtc optimize templates per branch.
Which mfgw bot anti-patterns should be avoided?
Twelve manufacturer warranty bot anti-patterns to ban from production.
1. Portal link first message
Rule 4 NO-REDIRECT. Legal seller explain before RMA URL.
2. Invent manufacturer months
Rule 2 MFGW-MAP only. Hallucination = P1 incident.
3. Skip MB-2 canal gate
Marketplace order → MP-WAR not mfgw bot.
4. Promise constructeur replacement
Anti-overpromise #349 family. Probable routing only.
5. Empty handoff payload
Rule 8 MF-1 fields mandatory agent.
6. Loop manufacturer refusal
bot_mfgw_manufacturer_refusal → agent not portal again.
7. Ignore registration legal split
Registration does NOT affect legal 24 months bot must cite.
8. Stale MFGW-MAP corpus
Deploy bot without map sync #455 = contradict PDP.
9. Mix warranty_coverage only
#349 exclusions without #456 routing = incomplete answer.
10. Grey import commercial promise
AUTH-DEALER-01 block manufacturer commercial template.
11. Wholesale consumer flow
B2B tag → wholesale route not bot_mfgw.
12. Skip proof collection MB-7
Handoff without attachments = agent repeat work.
13. Multi-language warranty notice
Packaging notice EN client FR: bot cites MFGW-MAP FR durations not raw notice OCR unless verified chunk.
How does Qstomy implement MFGW-BOT?
Qstomy on Shopify runs MFGW-BOT: MB-2 canal gate, MFGW-MAP RAG lookup SKU order, TPL-MFGW-REGIME auto, NO-REDIRECT-01 guardrail, claim #62 prefill handoff, MP-WAR #355 detect marketplace tag.
Qstomy mfgw bot capabilities
mfgw_map_rag_bot: SKU routing durations portal grounded
mfgw_regime_template_bot: TPL-MFGW-REGIME three regimes
mfgw_no_redirect_guard: block abusive portal
mfgw_portal_link_prefill: serial order context URL
mfgw_claim_shopify_prefill: #62 order SKU date
mfgw_handoff_payload: MF-1 fields attachments agent
Pipeline #455 #456 #349 #62
#455 MFGW-MAP source. #456 bot routing. #349 parallel coverage. #62 claim execute post bot store route. Shared guardrails anti-overpromising.
Encrypted DTC scenario
Authorized electronics reseller, 74 mfgw bot sessions/month, 41% abusive redirect baseline generic bot.
After MFGW-BOT-SUP + Qstomy: mfgw_bot_auto_resolve 61%, mfgw_bot_route_accuracy 95%, mfgw_bot_abusive_redirect 0, mfgw_bot_csat 4.6/5.
Explore customer support and request a demo.
AI warranty governance
MB-8 logs feed AI governance (#124) monthly review mfgw_bot_map_hallucination zero tolerance.
Weekly bot mfgw compliance review
Audit MB-5 before MB-6 sequence 100% sample. Zero abusive redirect transcripts tolerance.
What is the checklist for deploying MFGW-BOT?
MFGW-BOT Checklist (12 steps)
Validate complete MFGW-MAP #455 top 20 SKU
Index RAG corpus /pages/warranty-coverage + PDP blocks
Draft MFGW-BOT-SUP policy 8 rules
Configure 12 intents bot_mfgw_* classifier
Implement flow MB-1 to MB-8 + guardrails NO-REDIRECT AUTH-DEALER
Templates TPL-MFGW-* grounded map
Integrer claim #62 prefill + portal link MB-7
MB-2 channel gate handoff MP-WAR #355
Handoff payload MF-1 fields test 8 scenarios
Dashboard KPI mfgw_bot section 9
Tests: store first, portal direct, refusal escalate, grey, brand dtc, pre-purchase, marketplace gate, hostile
Sync map version bot deploy quarterly pipeline
In short
#456 = bot routing, not after-sales service execute #455
MFGW-MAP shared: same JSON #455
NO-REDIRECT guard: legal seller before portal
Handoff payload: zero repeat intake agent
KPI mfgw_bot_route_accuracy: target > 92 %
FAQ
Can the bot open a claim on its own?
MB-7 prefill #62 store route. Agent validation in case of dispute or refusal.
Difference from #349?
#349 coverage exclusions. #456 routing interlocutor manufacturer boutique.
Difference from #455?
#455 agents execute MF-FLOW. #456 bot qualify route handoff.
Portal without store file?
Forbidden if NO-REDIRECT guard store_first legal window.
Manufacturer refuses?
bot_mfgw_manufacturer_refusal escalate agent #455 P1.
Go further
This week: sync MFGW-MAP #455 into bot RAG, deploy intents bot_mfgw_*, activate NO-REDIRECT guardrail, test handoff payload 8 scenarios, connect claim #62 prefill, launch dashboard mfgw_bot_route_accuracy.
Share this guide #456 with bot ops and after-sales service: one no-redirect guardrail is worth ten RMA links sent too early, a complete handoff payload is worth twenty agent minutes spent requalifying a case that the bot should have structured.
Go-live bot test matrix
8 scenarios sign-off: store first no redirect, portal after regime, intermediary copy, refusal escalate, grey unauthorized, brand dtc shortcut, marketplace MB-2 gate, hostile supervisor.
Enzo
July 1, 2026
