E-commerce
June 30, 2026
"I ordered ten days ago, why hasn't my package shipped yet?" The agent opens Shopify: status unfulfilled, tag made-to-order. For you, the piece is in the workshop. For the customer, it's an oversight. Without a dedicated support framework, every made-to-order purchase becomes a WISMO ticket, a cancellation, or a chargeback.
Ecom Design Pro points out that the made-to-order buyer expects two answers before adding to cart: how long manufacturing takes, and how long shipping takes afterwards (Ecom Design Pro, lead time UX 2026). Logbase estimates that post-checkout silence is the primary cause of distrust on MTO Shopify stores (Logbase, made-to-order Shopify 2026).
This guide #288 covers customer support for made-to-order lead times: production statuses, macros, delays, cancellations. Distinct from pre-order (#187) (product not yet launched): here, production is triggered after payment, often with customized options.
Summary
Why does made-to-order support differ from stock and pre-order?
Made-to-order support manages an active production wait, not a 48-hour warehouse delivery or a product launch wait.
Three customer confusions
Unfulfilled = forgotten: Shopify displays "unfulfilled" while the workshop is working
Vague single lead time: "delivered within 3 weeks" without separating production and transport
Forgotten option: monogram or premium fabric extends the lead time without having stated so at checkout
Typical ticket volume
Custom furniture, engraved jewelry, MTO fashion, or personalized home decor stores: 35% to 55% of post-purchase tickets Day 0 to Day 21 = production status, modification before cutting, or delay vs. promised date. Kickflip notes that transparency regarding timelines and production updates is the primary driver of MTO satisfaction (Kickflip, made-to-order 2026).
Cost of a misrouted WISMO
Listybox estimates that most POD/MTO disputes stem from surprise rather than actual slowness: the customer is not informed that the item is still in production (Listybox, delivery expectations 2026).
How does it differ from the pre-order (#187) and the quote (#235)?
Five related pieces of content, five moments in the customer journey.
Pre-order (#187)
Pre-order (#187): product not yet available, far-off shipping date, charge-later. The #288: manufacturing started after ordering, lead time = production + shipping.
Custom Quote (#235)
Quote (#235): RFQ cycle u2192 validation u2192 B2B order. The #288: order placed online, workshop tracking and lead times.
Parcel Tracking (#181, #184)
Tracking (#181) and WISMO bot: parcel shipped. Here: not yet ready to ship.
Delivery Delay
Delay communication: carrier late. MTO: workshop or material delay before shipping.
Gift (#182)
Gift order (#182): anonymity, note. The #288 adds event deadline vs manufacturing lead time.
Which intents and tags should be mapped for the MTO?
Map the MTO support intents before applying generic WISMO macros.
Main intents (10)
mto_status: where is my manufacturing atmto_timeline_explain: how many days for production vs shippingmto_option_delay: does my option extend the lead timemto_modify_before_prod: change engraving, size, fabric before cuttingmto_cancel_before_prod: cancel before workshop launchmto_cancel_in_prod: cancel during manufacturingmto_delay: promised date exceededmto_rush_request: express manufacturing requestmto_mixed_cart: part stock, part MTOmto_gift_deadline: deliver before birthday/wedding date
Gorgias Tags
made_to_order, mto_in_production, mto_delay, mto_modify, mto_cancel, mto_rush, mto_mixed_ship.
What production status taxonomy should we adopt?
Adopt a production status taxonomy visible to agents and the customer, aligned with Shopify + workshop.
6 ops statuses
Order received: payment OK, workshop queue (
mto_received)Awaiting validation: specs to be confirmed with customer (
mto_pending_specs)In production: cutting, assembly, engraving (
mto_in_production)Quality control: workshop inspection (
mto_qc)Ready to ship: packaging, shipping label (
mto_ready_to_ship)Shipped: active tracking, out of MTO scope (
shipped)
Required order card fields
production_days_estimated, production_days_actual, ship_by_date, production_started_at, options_mto[], personalization_text, rush_tier, cancel_cutoff_at.
Shopify agent sidebar
Display MTO status, promised ship date, options delaying deadline, last Klaviyo "in production" update. Never let the agent guess from unfulfilled alone.
Customer display rule
Customer account: one clear status at a time ("In production", not generic "Processing"). Ecom Design Pro: avoid labels that mix manufacturing and shipping.
What macros for delay and status questions?
Twelve MTO macros cover 80% of pre- and post-purchase verbatims.
Pre-purchase
MTO-PRE-01 (PDP lead time): "Manufacturing: [X-Y] business days after order validation. Shipping: [Z] business days after. Estimated delivery: [total range]. Each piece is manufactured for you."
MTO-PRE-02 (impact option): "The [monogram/fabric X] option adds [N] business days to the standard lead time displayed."
Post-purchase status
MTO-STAT-01: "Order #[X]: status In production since [date]. Estimated manufacturing completed on [date]. Shipping scheduled within [Z] business days after. You will receive an email upon shipping with tracking."
MTO-STAT-02 (received, not yet started): "Your order is in the workshop queue. Production starts within [48-72 h]. Total lead time unchanged: [range]."
Modification and cancellation
MTO-MOD-01: "As long as status = Order received and before [cutoff], we can modify [field]. Confirm the new value by replying to this email."
MTO-CANCEL-01 (before prod): "Cancellation accepted, refund within 5-14 business days depending on bank."
MTO-CANCEL-02 (in prod, customized): "Custom manufacturing in progress: cancellation not possible (art. L221-28). We are checking if a minor modification is still possible."
Delay
MTO-DELAY-01: "Order update #[X]: [1 sentence reason]. New shipping date: [date]. Option for cancellation + full refund if you reply within 7 days."
How to proactively manage a manufacturing delay?
The manufacturing delay protocol requires proactive contact, not a defensive response to the customer ticket.
Listybox's golden rule
As soon as the delay is identified in the workshop, notify before the promised date. Message = precise new date + short reason + exit option (cancel or wait).
Agent decision tree
Delay < 3 business days vs promised: no mass notification, internal note only
Delay 3-7 days: email MTO-DELAY-01, tag
mto_delayDelay > 7 days: MTO-DELAY-01 + gesture of goodwill (see section 7)
2nd postponement of date: proactive refund offered to all affected MTOs
Chargeback threat: P1 escalation, immediate refund if production has not started
Compensation matrix
Delay 3-7 days: apologies + new date
Delay 7-14 days: free express shipping or −10% on next purchase
Delay > 14 days: 15% credit note or bonus item + refund option
Missed gift deadline: refund or voucher + personalized apologies
Documentation
Note in Shopify: delay date sent, customer response, gesture granted. XeeDevelopers: proactive contact costs less than a chargeback (XeeDevelopers, 2026 POD expectations).
How do I handle amendments, cancellations, and the right of withdrawal?
MTO modifications and cancellations depend on the workshop status and the level of customization.
Modification window (before production)
Engraving / text: modifiable until
production_started_atSize / dimensions: modifiable if the material has not been cut
Delivery address: yes, as long as
mto_ready_to_shiphas not been reachedPremium fabric option: modifiable + lead time recalculation before launch
4-step modification workflow
Check MTO status + cutoff
Confirm workshop feasibility ( Slack #production )
Update line item / Shopify note + recalculate
ship_by_dateCustomer confirmation email with new lead time if impacted
Right of withdrawal France
Clearly customized product (customer specs, engraving, tailor-made dimensions): exclusion L221-28 if informed before purchase (Economie.gouv.fr, withdrawal 2026). Standard MTO without customization: 14-day withdrawal applies. Visible mention on POP + order confirmation mandatory.
Rush production
Offer express tier (+X €, −Y business days) with hourly cutoff. Macro MTO-RUSH-01: price, new lead time, non-refundable if production has started.
How do you manage a mixed cart, gifts, and seasonal peaks?
Two MTO edge cases generate spikes in misrouted tickets.
Mixed basket stock + MTO
Shipping rule: split shipment or waiting for MTO item (written policy). Macro MTO-MIX-01: "Your order contains an in-stock item ([SKU A], shipped within 48 hours) and a made-to-order item ([SKU B], [X-Y] days). [Policy: consolidated shipping / split]." Tag mto_mixed_ship.
Gift with deadline
Collect event date at checkout or in notes. If ship_by_date > deadline: alert before payment (widget) or offer rush. Post-purchase: tag mto_gift_deadline, QC priority, escalation if probable delay at event D-7.
Premature WISMO
Intent mto_status distinct from WISMO tracking. Bot and agents: never reply "your package is on its way" if status < mto_ready_to_ship.
Seasonal peak
Kickflip: communicate extended lead times before Christmas / Valentine's Day on PDP and site banner. Buffer +20 to 40% on production_days_estimated during peak.
Where to place the bot and the human in made-to-order?
The tier 1 MTO bot answers status and lead times; humans handle disputes and complex modifications.
Auto OK
Explanation of manufacturing vs shipping, status from order metafield, impact of options on delay (help page), cancellation policy text, rush lead time if configured.
Immediate Human
Cancellation in custom production, delay > 7 days with chargeback threat, complex specification changes, missed gift deadline, request for workshop progress photo (if policy allows).
Prompt Extract
« Order MTO #[id]. Cite production_days and ship_by_date. Always separate manufacturing and shipping. If unfulfilled and mto_in_production: never say package shipped. Delay: escalate mto_delay. »
The future #486 will automate the lead time calculation by option and workshop capacity. The #288 sets up the human support and static bot protocol. For the project-based pre-purchase intake, see custom bot (#289).
Which KPIs should be tracked for the MTO vertical?
Segment the MTO support KPIs from the standard stock after-sales service.
Monthly KPIs
mto_status tickets / MTO orders: decreasing target post-macros
First response delay mto_delay: < 4 business hours
On-time ship rate: % orders shipped before
ship_by_dateMTO cancellation rate: cancellations / MTO orders
MTO chargeback rate vs stock (must remain < stock)
Modification before prod rate: quality tracking of PDP product pages
Weekly ops + support review
Workshop queue: orders > ship_by_date + 3 days. Cross-reference friction report (#281). Top verbatims without macros → enrich help or PDP.
How does Qstomy reduce manufacturing lead time tickets?
Qstomy routes MTO intents and injects production status into the bot and handoff.
Capabilities
Intent mto_*: section 3 matrix
Order lookup: MTO status, ship_by_date, options
Pre-populated MTO-* macros
Guardrail: "parcel shipped" block if < ready_to_ship
Delay escalation with workshop payload
Split mixed cart automatic explanation
Quantified DTC Scenario
MTO decoration brand (configurable furniture), 180 MTO orders/month, 94 status/delay tickets/month, on-time ship 78%. Deployment of status taxonomy + Qstomy mto intents + 12 macros. After 6 weeks: MTO tickets 94 → 38/month (−60%), on-time ship 78 → 91%, delay cancellations −34%, MTO segment CSAT 3.6 → 4.3.
See Shopify, AI support, demo.
Which playbooks should you use to deploy your made-to-order customer service?
Playbook 1: Status Taxonomy (1 d)
Define 6 statuses in section 4. Align workshop, Shopify tags, Klaviyo flows. Document transitions.
Playbook 2: MTO macros (4 h)
Import MTO-PRE to MTO-DELAY section 5. Test 15 real ticket verbatims.
Playbook 3: Delay Protocol (2 h)
Tree section 6 + compensation matrix. Simulate 3 workshop delays.
Playbook 4: PDP + checkout copy (1 d)
Separate manufacturing / shipping on PDP, cart, confirmation. Options = dynamic lead time if possible.
Playbook 5: M+1 KPI Review (45 min)
Dashboard section 10. Adjust peak buffer if on-time ship < 85 %.
Useful Linking
This week: audit 10 unfulfilled MTO orders. Does the agent know within 10 seconds if the piece is in production or in the queue? If not, deploy the status sidebar before the next seasonal peak.
Enzo
June 30, 2026
