E-commerce
July 9, 2026
"My product is no longer working, can you repair it?" "How much does the out-of-warranty repair cost?" "What is the status of my repair, it's been three weeks?" These messages are neither a size return nor a simple refund request.
The product repair request follows a distinct after-sales service workflow: diagnosis, quote, workshop, spare parts, return delay. Poorly managed, it generates reminders, negative reviews and cases that drag on for months.
This guide #341 treats repair as an operational after-sales service workflow. It complements automated warranty (#62) (warranty eligibility) and returns (#returns) from the perspective of repair, workshop and repair file tracking.
Summary
Why is repair a separate after-sales service flow?
Return, warranty, troubleshooting, and repair look similar from the customer side but not from the ops side. Confounding these flows creates impossible promises.
Four different paths
Return: new product sent back, quick refund or exchange
Warranty: eligibility check, replacement, or legal refund
Troubleshooting: remote resolution without product return
Repair: product received, diagnosed, repaired, sent back to the customer
The European Commission reminds us that consumers can demand repair or replacement in case of non-conformity under the legal warranty (EU, consumer guarantees).
Angle #341
#62 automates warranty requests. Here: repair as an ops process with workshop, estimate, parts, and status tracking.
Concerned verticals
Electronics, small household appliances, outdoor, glasses, watches, premium accessories, assembled furniture. Less common for pure players.
DTC Example
Audio player brand: 95 "repair" tickets/quarter, average file processing time of 28 days without workflow. After REPAIR flow + status portal: repair_cycle_time 14 days, -40% customer follow-ups.
Cost of a missing flow
A repair file poorly routed to return = €89 refund instead of a €12 part repair. WarrantyHub estimates that a structured service portal reduces status calls by 30 to 50% (WarrantyHub, warranty management 2026).
How does it differ from the warranty and return guides?
Six neighboring contents, six angles.
Automated Warranty (#62)
Guide #62: eligibility sorting for warranty, proofs, automation. #341 covers the workshop journey when repair is the chosen solution.
Returns and Exchanges
Returns Bot: RMA, return label, refund. #341 steps in when the customer wants to keep and repair the product.
Bot Troubleshooting
Troubleshooting bot: remote resolution. #341 = physical escalation after failed troubleshooting.
Refurbished (#269)
Refurbished (#269): products put back up for sale. #341 handles the repair of the customer's product.
Warranty Glossary
Warranty Glossary: definition. #341 = operational after-sales repair workflow.
Promise #341
Repair policy, eligibility, proof collection, workshop workflow, out-of-warranty quotes, REPAIR macros, status tracking, repair KPIs.
Post-purchase automation
The repair flow is part of the automated post-purchase support but with a longer cycle and specific workshop statuses.
What questions do customers ask about the repair?
Map out product repair intents before writing macros.
Twelve verbatims to tag
Do you offer a repair service for my product?
My product is under warranty, is the repair free?
How much does an out-of-warranty repair cost?
How do I send my product in for repair?
Do you have spare parts available?
How long does the repair take?
What is the status of my repair (case number)?
Can I repair it myself using your parts?
Irreparable product: refund or store credit?
Repair refused due to normal wear and tear: what to do?
Authorized repair center near me?
Product repaired under warranty but broke down again: what recourse?
Helpdesk tags
product_repair, repair_warranty, repair_quote, repair_status, repair_parts, repair_irreparable. See taxonomy (#135).
Intake bot collection
Before workshop escalation: order number, SKU, description of the breakdown, minimum of 2 photos, serial number if electronic. Incomplete files = no REP-ID generated. Benefit: -35% back-and-forth for proof.
Initial bot sorting
Intent repair_request → troubleshooting first (troubleshooting). If failure → open repair file. Distinction between repair vs return: "defect" vs "no longer suits me".
B2B Segment
Resellers and professionals: contractual repair turnaround time, distinct from the B2C 2-year warranty. Route to B2B support if it is a wholesale account.
How do you define your repair policy?
A written product repair policy prevents each agent from promising a lead time or rate that the workshop cannot meet.
Decisions to document
Model: internal workshop, authorized partner, manufacturer return
Eligibility: legal guarantee, commercial guarantee, out-of-warranty paid repair
Exclusions: normal wear and tear, impact, water, customer modification
Quote: free or paid, validity, response time
Shipping: return label provided or at customer's expense
SLA: diagnostics, repair, and return shipping times
Repair help page
Dedicated form /pages/reparation: order number, SKU, fault description, mandatory photos, serial number if applicable. Link from footer "After-sales service".
Warranty alignment #62
If legal warranty: free repair if eligible for non-compliance. If out of warranty: quote before intervention. Same evidence base as warranty portal.
Workshop models
Internal: total control, controlled SLA, fixed cost. Authorized partner: regional repair network, contractual SLA. Manufacturer: return to manufacturer after-sales service, shop = intermediary. Choose one main model per SKU category.
How to structure the repair workflow in 7 steps?
The standard after-sales service repair workflow standardizes each case from opening to return.
Seven ops steps
Intake: form or ticket, photos, order number, warranty verified
Sorting: remote troubleshooting or physical repair
Reception: workshop package, condition check, repair_received tag
Diagnosis: technician, quote if out of warranty, SLA 5 business days
Customer validation: quote approval or refusal (return of unrepaired product)
Repair: parts ordered, intervention, quality test
Return: shipping, tracking, repair_closed case closure
Visible customer statuses
Received → Under diagnosis → Quote sent → Under repair → Shipped. Auto email at each status change. Reduces "where is my repair?" tickets.
Repair case number
Unique REP-2026-XXXXX format. Referenced in ticket, workshop, emails. Customer quotes this number, not just the order number.
Proactive communication
Email D+3 reception: "Your product is under diagnosis." D+7 if parts are delayed: "Extended timeframe, new estimate [date]." Reduces repair_status_tickets by 40 to 60 % depending on DTCs tested.
SLA per step
Intake response 24 hours, diagnosis 5 business days, repair 10 days after quote validation, return 48 hours post-repair. Display SLA on the /reparation page to ground customer expectations.
How to manage quotes, parts, and out-of-warranty cases?
Out-of-warranty repair is the most sensitive case: estimate, customer refusal, product blocked in workshop.
Estimate rules
Fee-based diagnosis: €25-49 deducted if repair is accepted
Free estimate: under warranty or covered breakdown
Estimate validity: 14 days, auto reminder at D+10
Estimate refusal: return of unrepaired product, shipping costs charged to customer or free depending on policy
Spare parts
In-stock parts vs supplier order: lead time of +7-21 days to be communicated. Macro REPAIR-PARTS if out of stock. Option to sell parts alone if customer is a DIYer (factory policy).
Beyond economic repair (BER)
Offer warranty replacement, store credit, or partial refund depending on product age. Macro REPAIR-NO with empathy. Align commercial gestures.
Online estimate payment
Shopify checkout link SKU REPAIR-QUOTE or draft order. Customer pays before intervention. No repair without payment if out of warranty.
What macros and templates for the repair?
Industrialize the REPAIR macros for recurring files.
Minimum library (8 macros)
REPAIR-INTAKE: form, photos, serial no. requiredREPAIR-ELIG: warranty vs out-of-warranty eligibilityREPAIR-LABEL: workshop return labelREPAIR-QUOTE: quote sending, validity, payment linkREPAIR-STATUS: file status REP-XXXXXREPAIR-DELAY: parts or workshop delayREPAIR-NO: irreparable, replacement optionsREPAIR-SHIP: repaired product shipped + tracking
Bot intents
repair_available, repair_cost, repair_status_lookup, repair_warranty_eligible. Bot reads file status from repair table or Shopify tag. See templates (#34).
Human escalation
Dispute over rejected quote, re-failure post-repair, product lost in workshop, delay > SLA × 2. Human SLA 24 hrs.
Repair bot tests
15 queries: "repair my product", "status REP-2026-00123", "repair quote?". Target resolution rate without agent 65% on repair_status_lookup.
How to set up Shopify and workshop tools?
The Shopify repair workflow links tickets, tags, and return fulfillment.
Technical setup
Order tag: repair_open, repair_closed
Order metafield: repair_case_id, repair_status
Quote product: SKU REPAIR-QUOTE for diagnostic payment
Return app: workshop return label with distinct address
Flow: ops notification if tag is repair_open
Workshop tools
Spreadsheet, Notion, RepairDesk, or ERP module depending on volume. Fields: REP-ID, SKU, status, technician, parts, estimated return date.
Manufacturer partner
If repair = manufacturer warranty claim: REPAIR-MFG macro with contact details, manufacturer warranty number, turnaround time for redirection 48-72 h.
Launch checklist
/reparation page live, 8 macros, workshop address tested, email statuses configured, 1 end-to-end test case.
Workshop address
Return address distinct from the shipping warehouse. Avoid mixing new packages and broken products. Repair receiving area with REP-ID log upon arrival.
Which KPIs should be measured for repair files?
Without repair KPIs, cases drag on and follow-ups skyrocket.
Six key metrics
repair_cycle_time: case open → return to customer (days)
repair_first_reply_time: ticket → first response with procedure
repair_status_tickets: "what is the status of my repair" tickets / active cases
repair_quote_accept_rate: approved quotes / submitted quotes
repair_reopen_rate: second breakdown within 30 days post-repair
CSAT intent repair: post-closure satisfaction
DTC Benchmark
Target repair_cycle_time < 21 days out of warranty, < 14 days under warranty. repair_status_tickets < 15% active cases after status portal.
Monthly review
Top 5 SKUs in repair, breakdown causes, parts lead times, SLA adjustments, or critical parts stock.
Cost per case
Track parts cost + labor + shipping by REP-ID. Compare repair_cost vs replacement_cost for future policy decisions.
Which edge cases and disputes should be prioritized?
Five repair edge cases generate the majority of disputes.
Re-breakdown after repair
6-month repair warranty on intervention per policy. Reopen folder REP-ID without doing a complete intake again.
Product lost in workshop
Immediate procedure: empathy, 48-hour internal investigation, replacement or refund according to value. Tag repair_lost.
Wear and tear vs. defect
Agent does not decide alone in case of dispute. Quality escalation with photos. Macro REPAIR-WEAR vs REPAIR-DEFECT.
Mandatory photo proof
Intake without photo = incomplete folder. Bot and form block workshop escalation if less than 2 photos (global view + breakdown detail). Reduces back-and-forth by 35%.
Customer refuses estimate, product blocked
Return within 5 business days, shipping costs per policy. Follow-up if customer does not respond at D+14 of estimate.
Dropshipping without workshop
Manufacturer redirection or direct replacement. Do not promise internal repair if impossible. See dropshipping support.
Premium or luxury product
Brand workshop repair, return packaging provided, transport insurance. Longer SLA acceptable if premium communication. Link support luxury.
How does Qstomy handle repair requests?
Qstomy routes product_repair intents from policy and case status, after remote troubleshooting if applicable.
Capabilities
Intent repair_available : policy, link form
Warranty eligibility : order date, SKU, type of breakdown
Lookup REP-ID : live case status
Photo collection : intake before workshop escalation
Escalation : quote dispute, re-breakdown, lost product
Encrypted DTC Scenario
Small domestic appliance brand, 110 repair cases/quarter, 45% status tickets without portal.
After Qstomy + REPAIR macros + status portal: 68% repair tickets self-resolved, repair_first_reply_time 8 min, repair_status_tickets -52%, CSAT intent repair 4.5/5.
The bot collects intake and reads REP-ID status; the human decides on quotes and disputes. Same separation as warranty #62, applied to the workshop cycle.
Explore AI support, Shopify, request a demo.
What is the checklist for launching the repair workflow?
Repair Checklist (10 steps)
Draft repair policy + exclusions
Publish /repair page + intake form
Define 7-step workflow in section 5
Create 8 REPAIR macros in section 7
Configure Shopify repair_* tags
Set up status portal or automated emails
Train agents: repair vs return vs warranty
Test 1 warranty case + 1 out-of-warranty case
Weekly repair_cycle_time dashboard
Monthly review of top SKUs and parts
In brief
#341 = repair ops workflow, not warranty alone (#62)
7 steps: intake → return with visible statuses
Out-of-warranty quote: clear rules before intervention
Unique REP-ID: customer and workshop tracking
KPI repair_cycle_time: target < 21 days
FAQ
Repair or return, what to offer first?
Product defect under warranty: offer repair or replacement (EU customer choice). Change of mind: standard return.
Difference with the warranty guide #62?
#62 automates warranty sorting. #341 covers the workshop journey when repair is the solution.
Is an in-house workshop required?
No. An authorized partner or return to manufacturer is sufficient. Document who does what in the policy.
Bot or human for quotes?
Bot collects intake and status. Human mandatory for quotes, wear/defect disputes, re-breakdowns.
Unavailable parts: what to do?
Communicate lead time, offer replacement if SLA is exceeded, REPAIR-PARTS + REPAIR-DELAY macro.
EU Right to Repair: e-commerce impact?
The consumer can request repair under legal warranty in case of non-conformity. Your repair workflow must be able to honor it, not just offer refunds.
Go further
Simulate an end-to-end repair case before go-live: intake, receipt, quote, test repair, return with tracking.
Share this guide #341 with the workshop and support: a documented repair workflow converts frustration into trust better than a systematic refund on repairable products.
Train agents on all three workflows: a customer saying "broken" may need troubleshooting, repair or warranty return. Wrong routing costs more than the correct procedure.
Review the top 10 repair SKUs each quarter: parts inventory, updated troubleshooting guide, repair vs replace decision if there is a recurring failure.
Workshop and support must read the same REP-ID status: Notion, ERP or Shopify order metafield, updated at each step change.
Enzo
July 9, 2026
