E-commerce
July 1, 2026
"I ordered yesterday, why hasn't it shipped yet?" "Status 'processing' for 4 days, is this normal?" "You promised 24-hour shipping, my package doesn't even have a tracking number." Three messages where the customer confuses warehouse preparation (pick, pack, label) and delivery transit (carrier).
The e-commerce order preparation time support explains the delay between payment and carrier handoff. Without a policy, every unfulfilled ticket is treated as WISMO or delivery delay, with incorrect express promises.
This guide #395 covers the PREP-TIME policy, PREP-FLOW flow, and prep_time KPI. Delivery times are covered elsewhere; here the focus is on preparation time before shipping, warehouse cut-off, and unfulfilled status. Distinct from the future preparation bot (#396): agent processes and macros.
Summary
Why do preparation time inquiries overload customer support?
A support preparation delay ticket arrives when the order is paid but not yet fulfilled in Shopify. The customer sees "unfulfilled" or "in preparation" and panics.
Five customer confusions
Preparation = delivery: "not shipped" read as "not delivered"
24 h misunderstood: shipping within 24 hours ≠ delivered tomorrow
Weekend ignored: order on Friday night, expecting it on Monday
Invisible volume peak: Black Friday, warehouse backlog 2-3 days
Customization forgotten: engraving +2 days not reminded at checkout
ShipBob estimates that the pick-pack-label time varies from 0.5 to 2 business days depending on warehouse and volume (ShipBob, fulfillment 2026). Shopify distinguishes between fulfillment (shipping) and delivery (customer receipt) (Shopify, fulfill orders 2026).
Angle #395 vs neighboring contents
Delivery time communication: transit pre-purchase PDP. The #395 = post-order support preparation.
Express #338: express carrier cut-off. The #395 = warehouse delay before label, all methods.
Pre-order #187: product not yet launched. The #395 = standard stock in preparation.
Made-to-order #288: workshop manufacturing. The #395 = warehouse pick-pack, not production.
Delivery delay: parcel en route. The #395 = not yet shipped.
DTC Example
Beauty brand, prep SLA 1-2 business days, 67 prep_time tickets/month confused as WISMO. After PREP-TIME + PREP-FLOW: prep_time_fcr 86%, wismo_misroute -52%, prep_sla_miss_rate -31%.
Typical volume
8 to 18% of "where is my order" tickets from Day 0 to Day 3 are actually preparation questions, not transit.
Sensitive sectors
Gifts, events, B2B deadline: preparation + transit calculation before customer promise.
How does preparation differ from delivery and MTO?
Four logistical phases, four distinct support responses.
Phase matrix → customer question
Preparation (#395): order paid → label created (0-3 business days)
Transit: label → delivered (2-7 days depending on method)
MTO Production (#288): workshop manufactures before prep
Pre-order (#187): waiting for product launch
Customer total delivery time formula
Total time = prep time + transit time (+ MTO production if applicable). PDP must separate "Shipped within X days" and "Delivered within Y days". Support #395 explains X when unfulfilled.
Shopify Status
Unfulfilled = prep in progress or pending. Partially fulfilled = split shipment (#split). Fulfilled = carrier handoff, WISMO transit applicable.
Preparation cut-off vs express cut-off
Prep cut-off 2 PM: order picked same day. Express cut-off #338: next-day carrier after ship. The two are cumulative, do not confuse in macro.
Promise #395
PREP-TIME policy, PREP-FLOW flow, typologies, PREP-* macros, KPI, warehouse ops alignment.
Which prep_time_* typologies should be mapped?
Twelve preparation lead time ticket typologies for consistent routing.
Twelve prep_time scenarios
prep_time_wismo_early: Day+0/Day+1 "not shipped" within normal SLA
prep_time_sla_exceeded: prep promise exceeded
prep_time_cutoff_miss: order after cut-off, ship next day
prep_time_weekend_gap: order Fri-Sat, waiting until Monday
prep_time_peak_backlog: Black Friday, announced extended lead time
prep_time_personalization: engraving, message, +N days prep
prep_time_mixed_cart_hold: waiting for missing SKU for complete ship
prep_time_address_hold: address to verify, prep blocked
prep_time_fraud_review: order under risk review
prep_time_preorder_confusion: preorder tag, reroute #187
prep_time_mto_confusion: made-to-order tag, reroute #288
prep_time_cancel_before_ship: cancel before fulfillment
Helpdesk tags
prep_time, prep_sla_ok, prep_sla_miss, prep_peak, prep_personalization. Separate from wismo_transit and preorder.
Intake data
order_id, created_at, fulfillment_status, order tags, prep_sla_promise, personalization fields, cut-off time order vs warehouse TZ.
Ticket mining
WISMO Day+0 to Day+2: reclassify % prep_time vs transit. Feeds macros and FAQ.
How to write the PREP-TIME policy in eight rules?
The PREP-TIME preparation delay policy documents the warehouse SLA before the customer promise.
Eight PREP-TIME rules
Standard SLA prep: 1-2 business days in stock, documented /pages/expedition
Same-day cut-off: order before 2:00 PM (example) ship business day
Business days: Mon-Fri prep, no Sat-Sun except peak policy
Customization: +1-3 days prep, displayed at checkout
Peak extension: site banner + email if prep 3-5 days (Christmas, BF)
Partial hold: complete ship or split explained (#split)
SLA miss: proactive notification + gesture if > 2 days beyond promise
Pre-ship cancellation: possible if unfulfilled, within 24 hours of processing
Checkout publication
"Shipped within 1-2 business days · Delivered within 3-5 days" two distinct lines. Confirmation email repeats prep SLA.
Ops alignment
Support does not promise 24h prep if warehouse SLA is 48h. Quarterly review merch + warehouse.
Preorder/MTO distinction
Order tags route to #187/#288, not standard PREP-TIME.
SLA by SKU category
Standard stock 1-2 days, customization 3-5 days, fragile QC +1 day. Document by product tag.
How to apply the eight-step PREP-FLOW?
The PREP-FLOW framework structures the ticket response preparation.
Eight steps PR-1 to PR-8
PR-1 Intake: order_id, verbatim, prep_time_* typology
PR-2 Read order: created_at, fulfillment_status, tags, line items
PR-3 Calculate prep SLA: elapsed business days vs promise
PR-4 Classify: on SLA | cut-off miss | peak | custom | reroute
PR-5 Check ops: WMS status, hold reason if accessed
PR-6 Reply: adapted PREP-* macro + ETA ship date
PR-7 Resolve: reassurance, ops escalation if SLA miss, cancellation if requested
PR-8 Document: order note, prep_* tag, ops flag if backlog
PR-3 business days calculation
Order Monday 10 a.m., SLA 2 business days, cut-off 2 p.m.: ship Wednesday max. Order Friday 4 p.m.: ship Tuesday (cut-off miss + weekend).
PR-4 decision tree
preorder tag → #187
made-to-order tag → #288
fulfilled → WISMO transit, not PREP-FLOW
unfulfilled on SLA → PREP-OK-01
unfulfilled SLA miss → PREP-MISS-01 + ops ping
Support response SLA
Prep questions: first response 4 hours with estimated ship date. SLA miss: supervisor + client within 24 hours.
Ship date template
PR-6 always includes: "Estimated shipping: {{ship_date}} (business days)."
Which PREP-* macros for agents?
Ten PREP-* agent macros standardize preparation explanations.
Ten PREP macros
PREP-OK-01: within SLA, estimated ship date
PREP-CUTOFF-01: after cut-off, ship next business day
PREP-WEEKEND-01: weekend, prep resumes Monday
PREP-PEAK-01: peak backlog, transparent extended delay
PREP-PERSO-01: customization +N days before ship
PREP-MISS-01: SLA exceeded, apology + ship within 24 hours
PREP-HOLD-01: awaiting stock/address, customer action
PREP-SPLIT-01: planned partial ship, #split link
PREP-EDU-01: prep vs transit explanation
PREP-CANCEL-01: pre-ship cancellation procedure
PREP-EDU-01 example
"Your order is in warehouse preparation (picking and packing). Estimated shipping Wednesday. Carrier tracking will be active after shipment. Delivery time: 2-4 additional business days."
Reassuring factual tone
Concrete ship date, not "soon". If SLA missed: ownership + plan, no vague excuses.
30 min agent training
5 orders: within SLA, cut-off miss, peak, preorder tag reroute, fulfilled reroute transit.
How do you align warehouse, checkout, and communication?
The prep ticket prevention aligns the checkout promise with actual warehouse capacity.
Warehouse ops checklist
Measured prep SLA: median hours order to label
Displayed cut-off: PDP, cart, email confirmation
Peak playbook: 3-5 days prep, banner + Klaviyo
Visible WMS holds: agents read hold reason API
Personalization queue: separate documented SLA
Warehouse timezone: cut-off CET vs client UTC
Flexport notes that communicating processing time separately from transit reduces early WISMO (Flexport, fulfillment guide 2026).
D+1 unfulfilled email
Proactive: "Your order is being prepared, estimated shipping date {{ship_date}}." Reduces prep_time_wismo_early by 40-60%.
Order status page
"Preparing in warehouse" status, not just "Unfulfilled". Dynamic ETA ship date if WMS is used.
Support → ops feedback loop
prep_sla_miss > 5% per week: warehouse meeting + adjust checkout banner.
Shopify fulfillment notifications
Shipping confirmation = end of prep. Distinct order confirmation = start of prep.
Which edge cases and reroutes should be handled?
Ten lead time edge cases and policy answers.
1. Preorder confusion
Preorder tag, distant ship date. Reroute #187, not standard PREP-OK.
2. MTO confusion
Workshop production in progress. Reroute #288 with production status.
3. Fulfilled but not received
WISMO transit, not PREP-FLOW. Tracking #184.
4. Split shipment
Split #split: partial fulfilled, remainder in prep. PREP-SPLIT-01.
5. Invalid address hold
PREP-HOLD-01 + address change.
6. Fraud review 24-48 h
Prep blocked. Neutral message, no fraud details. SLA resumes post-clear.
7. Event gift deadline
Prep + transit calculation vs event date. Express #338 if still room post-ship.
8. High-volume B2B
Distinct wholesale prep SLA. Sales handoff if MOQ delay.
9. Multi-warehouse
Multi-warehouse: prep by location, maximum line item ship date.
10. Urgent pre-ship cancellation
PREP-CANCEL-01. If pick started: partial cancel policy.
Perishable prep priority
Perishables: express warehouse prep queue, communicate same day ship if cut-off OK.
Multi-warehouse prep
Split shipment: indicate prep by warehouse and latest ship date for overall promise.
Which prep_time KPIs should be monitored?
The support preparation delay KPIs link warehouse ops and customer service.
Eight key metrics
prep_time_ticket_rate: prep tickets / unfulfilled orders D+0-3
prep_time_fcr: resolved 1st contact / prep tickets
prep_sla_miss_rate: ship orders > promise / total
wismo_misroute_rate: prep treated as transit / total WISMO
prep_type_mix: ok vs cutoff vs peak vs custom
median_hours_to_fulfill: warehouse ops
prep_proactive_email_impact: drop in tickets post D+1 email
prep_cancel_pre_ship_rate: cancellations before label
DTC Benchmark
prep_time_fcr > 84%, prep_sla_miss < 5%, wismo_misroute < 10%, median_hours_to_fulfill < 36 h standard stock, prep_time_ticket -35% post PREP-EDU FAQ.
Weekly ops + support dashboard
Correlate prep_sla_miss with ticket volume. Peak: daily support + warehouse standup.
PREP-FLOW ROI
67 tickets/month × 8 min × agent cost. FCR +86% vs 62% = 16 tickets × 5 min saved/month.
Peak correlation
Black Friday: prep_sla_miss > 8% triggers warehouse staffing review within 48 h.
How to connect the WISMO bot and future bot #396?
The multichannel prep playbook routes the WISMO bot to prep or transit.
WISMO Bot #184
If unfulfilled: branch PREP-FLOW logic, no tracking number. Prep vs. transit message PREP-EDU-01 template.
Future bot #396
Prep automation: read WMS, stock, warehouse load, dynamic ETA ship. #395 sets policy and source macros.
Self-service FAQ
Article « How long before shipping? » separate from « delivery times ». Email confirmation link.
Klaviyo flow
Trigger unfulfilled D+1: prep status + ship ETA. Separate shipped flow tracking.
Express #338
Prep miss impacts express promise. Escalate if express paid + prep SLA missed.
How does Qstomy inform about the preparation time?
Qstomy on Shopify: lookup unfulfilled order, business days prep SLA calculation, PREP-* templates, reroute preorder/MTO/transit.
Qstomy PREP-TIME Capabilities
prep_order_lookup: created_at, tags, fulfillment_status
prep_sla_calculate: business days vs PREP-TIME policy
prep_edu_template: prep vs transit PREP-EDU-01
prep_reroute: preorder #187, MTO #288, fulfilled transit
prep_peak_aware: banner peak message PREP-PEAK-01
prep_handoff: ticket PR-1 to PR-5 if SLA missed
Complement #395 ops
PREP-FLOW complex dispute agents. Qstomy reduces prep_time_wismo_early. prep_time_fcr +12 pts combined Day+1 email + bot.
Quantified DTC Scenario
Decor brand, 2-day prep SLA, 67 prep tickets/month, 41% premature Day+1 WISMO.
After Qstomy PREP + proactive email: prep_time_fcr 87%, prep_bot_resolution 72%, wismo_misroute -54%, prep_time_ticket_rate -36%.
Explore customer support, AI sales agent and request a demo.
What is the checklist for deploying PREP-TIME?
PREP-TIME Checklist (12 steps)
Measure warehouse median hours order-to-label
Draft policy with 8 PREP-TIME rules + /pages/shipping
Separate checkout copy "shipped in X" vs "delivered in Y"
Document 12 prep_time_* typologies in section 3
Create 10 PREP-* Gorgias/Zendesk macros
Train agents on PREP-FLOW PR-1 to PR-8 (30 mins)
Proactive D+1 unfulfilled Klaviyo email
Order status page with "In preparation" + shipping ETA
Peak playbook banner + PREP-PEAK-01
Monthly prep_time KPI dashboard
Route unfulfilled WISMO bot → prep logic
Align future bot #396 WMS integration roadmap
Summary
#395 = prep before shipping, not shipping transit
PREP-FLOW: unfulfilled → SLA → macro → shipping date
Prep + transit: two timeframes, two messages
Reroute: preorder #187, MTO #288, fulfilled WISMO
prep_time_fcr KPI: target > 84%
FAQ
Difference between prep and shipping?
Prep = warehouse pick-pack-label. Shipping = carrier after dispatch. PREP-EDU-01.
Order placed Friday night, normal that it hasn't shipped by Monday?
Yes if cutoff missed + weekend. PREP-CUTOFF-01 + PREP-WEEKEND-01.
Relation to preorder #187?
Preorder = product not ready. #395 = standard stock undergoing warehouse prep.
Relation to bot #396?
#395 policy + agents. #396 automation of WMS prep ETA / stock.
Express paid, not shipped same day?
Check prep cutoff + express cutoff #338. Escalate if prep SLA missed.
Go further
Audit 10 WISMO D+1 tickets: how many are prep within SLA vs transit vs misrouted preorders?
Share this #395 guide with warehouse and support: clarifying preparation avoids treating every unfulfilled order as a carrier delay.
Enzo
July 1, 2026
