E-commerce
July 1, 2026
“You sold me the product, why are you sending me to the manufacturer?” “The brand says 5 years, your site says 2 years, who is right?” “I registered my manufacturer warranty, does the shop still need to intervene?” Three messages where customer service mixes up legal warranty, commercial shop warranty, and manufacturer warranty without clear routing.
The manufacturer warranty vs. e-commerce shop warranty customer support playbook covers who is responsible, who to contact first, and which procedure to apply when the customer purchased from the DTC store, distinct from marketplace channel confusion or checkout extensions.
This guide #455 covers policy MFGW-SUP, flow MFGW-FLOW, and KPI mfgw. It complements marketplace warranty (#355) from the manufacturer vs. shop counterparty angle on DTC purchases. Distinct from warranty automation (#62) and extensions (#348): here, we focus on the customer service routing playbook for manufacturer, seller legal warranty, and brand commercial warranty.
Summary
Why does the manufacturer-store confusion generate customer service tickets?
A manufacturer warranty vs store ticket happens when the customer does not know whether the online store, the manufacturer, or both are responsible after a breakdown.
Five typical customer confusions
Legally responsible entity: store seller vs manufacturer mentioned on packaging
Different duration: 2 years on site vs 5 years in manufacturer manual
Procedure: manufacturer RMA vs store after-sales portal
Intermediary: does the store collect or send back directly?
Registration: manufacturer warranty activated, is the store still involved?
Service-Public points out that the 2-year legal warranty of conformity is the responsibility of the seller from whom the purchase was made, separate from any manufacturer commercial warranty (Service-Public, legal warranty 2026). Your Europe confirms that the consumer can contact the seller first for any lack of conformity (Your Europe, EU warranty 2026).
Angle #455 vs related content
Marketplace channel #355: Amazon vs purchase store. #455 = DTC purchase, contact person confusion.
Automation #62: store claim portal. #455 = manufacturer routing prior to claim.
Extension #348: EXT-WAR checkout. #455 = legal, store, and manufacturer plans.
Bot #349: AI coverage. #455 = agent routing playbook.
Repair #341: workshop flow. #455 precedes REPAIR: who takes responsibility.
DTC Electronics Example
Authorized reseller brand, 74 mfgw tickets/month, 52% referral to manufacturer without legal explanation. Without MFGW-SUP: mfgw_fcr 61%, "store washing its hands" disputes 18/month. After MFGW-MAP + flow: mfgw_route_accuracy 92%, mfgw_fcr 84%, mfgw_csat 4.3/5.
Contact person ≠ purchase channel
Customer buys from DTC store but breakdown is sometimes covered by direct manufacturer warranty. MFGW-FLOW distinguishes legal scheme from routing ops.
Post-holiday seasonality
Peak mfgw_ticket_rate in January-February post-gifts: pre-load MFGW-REGIME capacity and supervisor escalation manufacturer_refusal.
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
How does MFGW-SUP differ from MP-WAR #355 and EXT-WAR #348?
Three warranty regimes, three guides: marketplace channel, checkout extension, manufacturer-shop interlocutor.
Intention → process matrix
#455 MFGW-FLOW: manufacturer vs shop, routing, intermediary
#355 MP-WAR: Amazon marketplace vs DTC purchasing channel
#348 EXT-WAR: extension sold at shop checkout
#62 WAR-AUTO: eligible shop claim automation
#341 REPAIR: workshop after confirmed routing
Three MFGW-REGIME regimes
legal_conformity: 2 years, EU responsible shop seller
store_commercial: shop commercial warranty beyond or in addition
manufacturer_warranty: manufacturer warranty, own conditions
Four MFGW-TYPE pathways
mfgw_store_first: shop processes then transfers to manufacturer if needed
mfgw_manufacturer_direct: customer routes to manufacturer RMA portal
mfgw_dual_parallel: two regimes coexist, clarify which one applies
mfgw_brand_own_product: brand = manufacturer = seller, single interlocutor
Promise #455
Policy MFGW-SUP, MFGW-MAP matrix by SKU, 12 mfgw_* typologies, MFGW-FLOW flow, MFGW-* macros, mfgw_* KPI.
Seller is always the legal entry point
MFGW-SUP rule 1: 2-year legal warranty, DTC shop remains responsible even if the manufacturer's manual states 5 years commercial.
Which mfgw_* typologies should be mapped?
Twelve store manufacturer warranty typologies for consistent helpdesk routing.
Twelve mfgw scenarios
mfgw_who_responsible: who to contact first post-breakdown
mfgw_duration_conflict: 2 years on site vs 5 years manufacturer manual
mfgw_store_intermediary: store collects and transfers to manufacturer
mfgw_manufacturer_rma: direct manufacturer RMA portal routing
mfgw_registration_required: mandatory manufacturer warranty registration
mfgw_unauthorized_dealer: manufacturer refuses unauthorized reseller
mfgw_grey_import: parallel import product, EU manufacturer warranty refused
mfgw_legal_vs_commercial: confusion between seller legal vs brand commercial warranty
mfgw_pre_purchase_question: who guarantees if I buy here?
mfgw_serial_proof: serial number, invoice for manufacturer claim
mfgw_manufacturer_refusal: manufacturer rejects, store must take back
mfgw_brand_dtc_single: brand owns product, no third-party manufacturer
Helpdesk tags
mfgw, mfgw_manufacturer, mfgw_store, mfgw_legal, mfgw_routed, mfgw_intermediary, mfgw_resolved. Distinct warranty_channel (#355), ext_warranty (#348).
Prioritization
P1: mfgw_manufacturer_refusal store must legally take back. P2: mfgw_who_responsible, mfgw_duration_conflict. P3: mfgw_pre_purchase FAQ.
Mining verbatims mfgw
90-day export "manufacturer", "builder", "5-year warranty", "sent back to", "warranty registration", "RMA". Distinct "Amazon" → #355.
Which MFGW-MAP matrix should be documented?
The MFGW-MAP shop manufacturer warranty matrix lists terms, routing, and contacts by SKU or product range.
MFGW-MAP Columns
sku_or_range: reference or product family
legal_warranty_months: 24 EU standard seller
store_commercial_months: shop commercial warranty if applicable
manufacturer_warranty_months: duration from manufacturer manual
routing_type: store_first, manufacturer_direct, dual, brand_dtc
manufacturer_portal_url: manufacturer RMA link
registration_required: Y/N manufacturer registration
store_intermediary: Y/N shop collects product
proof_required[]: invoice, serial number, photo, form
macro_primary: MFGW-STORE vs MFGW-MFG-ROUTE
Authorized Electronics Dealer Example
legal 24 months shop, manufacturer 60 months manufacturer parts, routing store_first: shop opens legal file, transfers to manufacturer if outside 24 months and eligible for manufacturer commercial warranty.
Proprietary DTC Brand Example
routing brand_dtc: single contact point, legal + commercial merged, no external MFGW-MFG-ROUTE.
Publishing to /pages/warranty-coverage
MFGW-MAP FAQ: who warrants, durations, procedure, manufacturer link, difference with #355 marketplace channel.
Sync PDP warranty block
Product detail page warranty block cites the same MFGW-MAP durations. Agent and customer see alignment between site and packaging manual.
Authorized dealer flag
MFGW-MAP authorized_dealer Y/N by range. Agents never promise commercial manufacturer warranty if N and grey import is suspected.
How to write the MFGW-SUP policy in eight rules?
The MFGW-SUP manufacturer warranty policy governs routing without abusive redirection, nor unfounded manufacturer promises.
Eight MFGW-SUP rules
Legal seller first: legal warranty of 2 years, DTC store is responsible, never send directly to the manufacturer only
MFGW-MAP grounded: durations and routing from the JSON, not invented by the agent
Explain three regimes: legal, store commercial, manufacturer commercial
Intermediary clarity: if store_intermediary is Y, explain collection and timeframes
Manufacturer route when map says: MFGW-MFG-ROUTE with portal URL and proofs
Manufacturer refusal takeover: in case of manufacturer rejection, the store resumes its legal obligation if applicable
No unauthorized promise: do not promise a manufacturer warranty if it is a grey import or from an unauthorized reseller
Cross-link channel #355: marketplace purchase outside of MFGW-FLOW DTC, use MP-WAR route
Direct redirection to manufacturer prohibited
Rule 1: "contact the manufacturer" without opening a store case = potential DGCCRF dispute pattern. The store must qualify legal eligibility first.
Duration conflict resolution
2 years on site = minimum seller legal warranty. 5 years in manual = manufacturer commercial warranty with separate conditions. Use MFGW-DURATION-01 macro to explain both.
Grey import gate
mfgw_grey_import: MFGW-MAP flag, store legal remains if legal DTC purchase, manufacturer commercial is often excluded. No false promises of 5-year manufacturer warranty.
How to apply the MFGW-FLOW in eight steps?
The MFGW-FLOW framework structures the regime qualification and contact routing grounded in MFGW-MAP.
Eight steps MF-1 to MF-8
MF-1 Intake: order_id, SKU, purchase date, nature of breakdown, confirmed DTC purchase channel
MF-2 Canal gate: marketplace purchase? route MP-WAR #355, stop MFGW
MF-3 Classifier mfgw_*: section 3 typology
MF-4 Match MFGW-MAP: regimes, routing_type, durations, proof_required
MF-5 Regime explain: MFGW-REGIME-01 three customer regimes
MF-6 Branch routing: store claim | intermediary collect | manufacturer RMA | brand_dtc single
MF-7 Execute: open claim #62 | MFGW-MFG-ROUTE link | REPAIR #341 handoff
MF-8 Document: mfgw_regime, routing_chosen, manufacturer_refusal Y/N, claim_id
MF-6 store_first branch
Store opens warranty claim #62, collects proof. If eligible for manufacturer commercial post-24 months: transfer file to MFGW-INTERMEDIARY-01 with RMA number.
MF-6 manufacturer_direct branch
MFGW-MFG-ROUTE-01: portal URL, proof checklist, manufacturer lead time. Store remains the contact if refused or if manufacturer SLA is exceeded.
MF-6 manufacturer_refusal
Manufacturer rejects: MF-8 flag, store resumes 24-month legal analysis or store commercial analysis according to MFGW-MAP. Escalate to supervisor in case of dispute.
MF-2 marketplace redirect
Customer mentions Amazon Fnac purchase: handoff MP-WAR #355 even if "manufacturer" question. Channel takes precedence over contact.
MF-7 extension overlap
Customer mentions checkout extension: route EXT-WAR #348 in parallel, MFGW-FLOW does not replace extension policy.
MF-5 brand_dtc shortcut
routing brand_dtc: skip MFGW-MFG-ROUTE, MF-6 direct store claim #62 single contact. Simplify using MFGW-STORE-01 macros only.
Which MFGW-* macros and touchpoints should be configured?
Eight manufacturer's warranty store agent macros and post-purchase PDP touchpoints.
MFGW-REGIME-01 (three arrangements)
"Three distinct warranties: (1) legal 2-year store seller, (2) commercial store [X months if applicable], (3) commercial manufacturer [Y months terms of manual]. Your purchase: [date], applicable arrangement: [arrangement]."
MFGW-STORE-01 (responsible store)
"As the seller, we process your legal warranty claim. Opening file: [proofs list]. Processing time: [SLA]."
MFGW-MFG-ROUTE-01 (manufacturer routing)
"Manufacturer's commercial warranty [Y months]: direct manufacturer procedure [URL portal]. Proofs: [proof_required]. We remain available in case of blockage."
MFGW-INTERMEDIARY-01 (store intermediary)
"We collect your product, transfer it to the authorized manufacturer service. Estimated total time: [X days]. File number: [claim_id]."
MFGW-DURATION-01 (duration conflict)
"2 years site = mandatory EU seller legal warranty. 5 years manual = manufacturer commercial warranty, packaging terms. Both coexist, contact person depending on period and defect."
MFGW-REGISTRATION-01 (manufacturer registration)
"Manufacturer warranty registration required: [URL]. Complete within [X days] post-purchase. Store legal warranty of 2 years is independent of registration."
MFGW-REFUSAL-01 (manufacturer rejection takeover)
"Manufacturer refused: [reason]. We will re-analyze under the store legal warranty if eligible. Additional documents: [list]."
Touchpoints
PDP warranty block MFGW-MAP durations
/pages/warranty-coverage FAQ three arrangements
Claim portal #62 intake MF-1 fields SKU serial
Helpdesk snippet MFGW-REGIME on keyword manufacturer
Post-purchase email D+7 registration link if registration_required
Which intermediate cases, RMAs, and manufacturer rejections should be processed?
Special manufacturer warranty cases require MFGW-MAP extensions and supervisor escalation.
Authorized intermediary shop
Official reseller: store_intermediary Y, shop return label, manufacturer service transfer. Client does not manage RMA directly. Total SLA = shop + manufacturer.
Direct manufacturer portal RMA
manufacturer_direct routing: client creates portal ticket, RMA number. Shop provides PDF invoice if requested. Client status tracking + optional shop copy.
Mandatory warranty registration
mfgw_registration_required: outside registration period, commercial manufacturer warranty refused. 24-month legal shop warranty remains unchanged in case of non-conformity.
Unauthorized dealer
mfgw_unauthorized_dealer: manufacturer refuses claim. MFGW-MAP authorized_dealer Y required. Seller's legal shop warranty remains responsible for 2 years in the EU.
Grey parallel import
mfgw_grey_import: non-EU manufacturer notice. Commercial manufacturer warranty often N. Legal shop warranty applies if sale complies with the FR market.
Overlap repair #341
Manufacturer offers repair vs replacement: REPAIR handoff #341 if shop workshop or authorized partner. Distinct from warranty replacement #62.
Spare parts #343
Out of warranty failure, part under manufacturer warranty only: route spare parts (#343) or MFGW-MFG-ROUTE according to MFGW-MAP.
Pre-purchase warranty objection
mfgw_pre_purchase: MFGW-REGIME-01 + conversion link for warranty objections (#227).
Which mfgw KPIs should be measured?
The shop manufacturer warranty KPIs link routing accuracy, FCR, and abusive return disputes.
Eight key metrics
mfgw_ticket_rate: mfgw tickets / 100 mapped DTC SKU sales
mfgw_route_accuracy: compliant MFGW-MAP routing / total mfgw
mfgw_fcr: first contact resolution without recontact within 7 days
mfgw_store_claim_rate: open shop cases #62 / mfgw
mfgw_mfg_route_rate: routed manufacturer / map eligible
mfgw_manufacturer_refusal_rate: manufacturer refusals / routed mfg
mfgw_abusive_redirect_rate: manufacturer-only redirect without shop case / mfgw (target 0)
mfgw_csat: satisfaction tag mfgw_resolved
DTC authorized reseller benchmark
mfgw_route_accuracy > 90%, mfgw_fcr > 80%, mfgw_abusive_redirect_rate < 2%, mfgw_csat > 4.2/5.
Monthly dashboard
Breakdown mfgw_* typology, routing branch, manufacturer_refusal reason, SKU top confusion duration_conflict.
A/B MFGW-REGIME-01
50% mfgw tickets macro three regimes vs ad hoc 8 weeks. Measure mfgw_fcr lift and mfgw_abusive_redirect_rate drop.
mfgw_abusive_redirect audit
Weekly transcript scan manufacturer redirect without shop claim_id. Target mfgw_abusive_redirect_rate under 2%.
What anti-patterns should be avoided regarding the manufacturer's warranty?
Twelve shop manufacturer warranty anti-patterns to banish from the helpdesk.
1. Dry manufacturer referral
Rule 1 legal seller first. "Call the manufacturer" without a case file = dispute.
2. Confusing 2 years and 5 years
MFGW-DURATION-01 mandatory. Two terms, no contradiction.
3. Promising manufacturer warranty on grey imports
Rule 7 unauthorized grey. Legal shop warranty only.
4. Skipping MF-2 channel gate
Marketplace purchase: MP-WAR #355, not MFGW DTC.
5. Inventing warranty periods
Rule 2 MFGW-MAP grounded only.
6. Ignoring manufacturer refusal
Rule 6 shop return mandatory if legal warranty is applicable.
7. Routing extension without #348
Checkout extension: EXT-WAR parallel, not merged with MFGW.
8. Confusing REPAIR and warranty
Routing #341 after MF-6 confirmed status.
9. Registration block legal
Manufacturer registration does not affect the seller's legal 24-month warranty.
10. Bot overpromising #349
Bot explains, agent routes MFGW-FLOW. No guaranteed replacement by bot alone.
11. Stale PDP warranty block
MFGW-MAP update without PDP sync = agent contradicts site.
12. Mix wholesale #144
Active B2B reseller: wholesale route, not consumer mfgw.
How does Qstomy help with manufacturer vs. store warranties?
Qstomy on Shopify runs tier 1 mfgw: MF-2 channel gate, MF-3 classifier, MFGW-MAP lookup SKU order, MFGW-REGIME-01 auto, routing store vs manufacturer guardrail no abusive redirect, handoff claim #62 or MFGW-MFG-ROUTE portal link.
Qstomy mfgw capabilities
mfgw_map_rag: routing SKU durations regimes
mfgw_regime_template: MFGW-REGIME-01 three regimes
mfgw_no_redirect_guard: block manufacturer-only redirection
mfgw_mfg_portal_link: MFGW-MFG-ROUTE URL prefill
mfgw_mp_war_handoff: #355 if marketplace channel detected
mfgw_claim_prefill: #62 SKU series date file
Pipeline #455 #355 #62 #456
#455 MFGW routing agents. #355 MP-WAR channel. #62 claim execute. Future #456 manufacturer routing bot. Shared MFGW-MAP corpus.
Encrypted DTC scenario
Authorized reseller electronics, 74 mfgw tickets/month, mfgw_abusive_redirect_rate 38% baseline.
After MFGW-SUP + Qstomy PDP warranty block: mfgw_route_accuracy 93%, mfgw_fcr 85%, mfgw_abusive_redirect_rate 1.5%, mfgw_csat 4.4/5.
Explore customer support and request a demo.
Continuity warranty ops
MF-8 mfgw logs feed merch MFGW-MAP quarterly review alongside product lifecycle (#345) warranty messaging.
What is the checklist for deploying MFGW-SUP?
Checklist MFGW-SUP (12 steps)
Document MFGW-MAP by SKU: regimes, routing, portal, proofs
Align PDP warranty block with MFGW-MAP durations
Draft MFGW-SUP policy 8 rules legal seller first
Publish /pages/warranty-coverage FAQ three regimes
Create MFGW-* macros for dedicated helpdesk MP-WAR #355
Train agents on MFGW-FLOW 45 min MF-5 regime explain
Tags mfgw_* + KPI dashboard section 9
Route MF-2 channel gate to #355 if marketplace
Integrate portal claim #62 intake MF-1 fields
Test 8 scenarios: who responsible, duration conflict, intermediary, RMA direct, registration, refusal return, grey import, brand DTC single
Procedure manufacturer_refusal return supervisor
Sync MFGW-MAP → bot #349 #456 corpus
In brief
#455 = interlocutor, not channel #355
Legal 2 years seller: DTC store responsible first
Three regimes: legal, store, manufacturer
MFGW-MAP routing: store_first, direct, intermediary, brand_dtc
KPI mfgw_route_accuracy: target > 90%
FAQ
Customer wants to contact manufacturer directly?
MF-4 MFGW-MAP: if manufacturer_direct and outside legal store obligation, MFGW-MFG-ROUTE. Otherwise, store opens case first.
2 years site vs 5 years instructions manual?
Two regimes. MFGW-DURATION-01: legal seller vs commercial manufacturer.
Difference from #355?
#355 marketplace purchase channel. #455 manufacturer interlocutor vs DTC purchase store.
Manufacturer refuses?
MFGW-REFUSAL-01: store resumes 24-month legal analysis if applicable.
Is registration mandatory?
Affects manufacturer commercial, not seller 2-year legal warranty.
Going further
This week: document MFGW-MAP top 20 SKU, publish /pages/warranty-coverage, deploy MFGW-REGIME helpdesk snippet, train agents on MF-5 before MF-6 routing, connect MF-2 gate #355, launch dashboard mfgw_route_accuracy.
Share this guide #455 with customer service and merchandising: explaining three warranty regimes is worth ten direct manufacturer redirects which generate "brand is backing out" reviews, an up-to-date MFGW-MAP is worth hours of agent time reconciling contradictory packaging instructions and website information.
Enzo
July 1, 2026
