E-commerce
July 1, 2026
“My status has said ‘in preparation’ for 5 days, what does that mean?” “Why ‘being processed’ when you announce shipping within 24 hours?” “The status hasn't changed, is my order lost?” Three messages where the customer reads an opaque status label without understanding what is actually happening in the warehouse.
The e-commerce in-prep status support guide explains what each visible label means (customer account, email, portal), what remains normal vs. abnormal, and how to align the Shopify status with customer expectations without confusing preparation and delivery.
This guide #407 covers policy PREP-STATUS, flow STAT-FLOW, and KPI prep_status. It complements the preparation lead time (#395) (SLA days) and precedes the custom status bot (#408): here, visible status, customer labels, and post-purchase expectations.
Summary
Why does the "in preparation" status generate tickets?
A ticket for a status in preparation occurs when the customer sees a fixed label ("in preparation", "processing", translated as "unfulfilled") without knowing if pick-pack is underway, waiting on stock, or blocked due to fraud.
Five typical customer confusions
Status = delivery: "in preparation" read as "on the way"
Frozen status: same label on Day 1 and Day 4, customer panics
Technical label: "unfulfilled" or "processing" in English
Status vs PDP promise: "24 hrs" but status unchanged for 48 hrs
No next step: customer does not know when status will change
ShipBob estimates that 34% of DTC WISMO tickets actually involve orders that are still unfulfilled, poorly routed due to an ambiguous customer status (ShipBob, fulfillment 2026). Gorgias observes that clarifying post-purchase statuses on the order portal reduces "where is my order" tickets by 28-38% before shipping (Gorgias, customer service stats 2026).
Angle #407 vs related content
Prep time #395: PREP-TIME, cut-off, SLA days. #407 = visible status label and customer meaning.
Prep bot #396: PREP-BOT automation. #407 = agents explain status, STAT-* macros.
Custom statuses bot #408: future automation Shopify labels. #407 = policy mapping and human customer service.
WISMO #184: tracking fulfilled transit. #407 = upstream unfulfilled, status before shipping label.
Self-service #28: general portal. #407 = preparation status module.
DTC Example
Decor brand, single status "In progress" for everything unfulfilled. Without PREP-STATUS: 62% of prep tickets poorly routed as WISMO. After mapping labels: prep_status_ticket_rate -41%, wismo_misroute -55%, prep_status_csat 4.2/5.
Status vs lead time
#395 answers "how many days". #407 answers "what does what I see mean". Complementary, not redundant.
How does the visible status differ from delay #395?
Two distinct customer questions, two support playbooks.
Question → guide matrix
#407 PREP-STATUS: "what does in preparation mean?"
#395 PREP-TIME: "how long before shipping?"
#396 PREP-BOT: bot explains both grounded orders
#184 WISMO: "where is my package" post-ship
Three order status layers
Shopify backend: unfulfilled, partial, fulfilled
Internal OMS/WMS: picked, packed, label_created (often invisible to the customer)
Customer Portal: FR marketing label ("Warehouse preparation")
Objective #407
Map backend → customer portal with clear labels, sub-statuses if possible, next step visible. Agents and macros aligned with mapping.
Promise #407
PREP-STATUS policy, STATUS-MAP matrix, 12 prep_status_* typologies, STAT-FLOW flow, STAT-* macros, KPI.
Which prep_status_* typologies should be mapped?
Twelve preparation status ticket typologies for consistent routing.
Twelve prep_status scenarios
prep_status_meaning: "what does in preparation mean?"
prep_status_stuck: same status for X days, concern
prep_status_vs_promise: delivery promise 24h, status unchanged 48h
prep_status_no_update: portal has not moved since order
prep_status_partial: 1 item shipped, 1 "in preparation"
prep_status_hold: fraud, address, stock hold visible or not
prep_status_personalization: engraving, message, dedicated status
prep_status_preorder: preorder tag, generic status unsuitable
prep_status_mixed_cart: global status vs heterogeneous lines
prep_status_cancel_request: cancel because status is blocked
prep_status_email_mismatch: email says X, portal says Y
prep_status_wismo_confusion: customer believes shipped, unfulfilled
Helpdesk tags
prep_status, prep_status_stuck, prep_status_hold, prep_status_partial, prep_status_misroute_wismo. Distinct prep_time_sla, wismo_transit.
Upstream router
If fulfilled + tracking → WISMO #184. If prep_sla_exceeded → PREP-FLOW #395. If meaning/stuck only → STAT-FLOW #407.
Which STATUS-MAP matrix for customer labels?
The STATUS-MAP status mapping matrix translates backend into customer language.
Eight recommended mappings
unfulfilled + sla_ok → "Warehouse preparation · dispatch within [X] business days"
unfulfilled + cut_off_miss → "In preparation queue · dispatch [date]"
unfulfilled + personalization → "Personalization in progress · +[N] d"
unfulfilled + stock_hold → "Awaiting item · combined shipping"
unfulfilled + fraud_hold → "Verification in progress · response within 24 hrs"
unfulfilled + address_hold → "Address to be confirmed · action required"
partial fulfilled → "Partially shipped · [N] item(s) remaining"
unfulfilled + prep_sla_miss → "Preparation delay · team informed · [revised ETA]"
Prohibited portal labels
Raw Shopify "unfulfilled"
English "Processing" without translation
"In progress" alone without next step
"Shipped" if not fulfilled
Visible next step
Each portal status includes: action in progress + next milestone + estimated ship date. e.g., "Warehouse preparation → Next step: estimated dispatch July 4"
Transactional email alignment
Order confirmation, shipping delay: same STATUS-MAP labels. prep_status_email_mismatch = tag if divergence detected.
Future #408 Link
Shopify custom metafields statuses feed into STATUS-MAP. Bot #408 executes in chat. #407 defines agent mapping policy.
How to write the PREP-STATUS policy in eight rules?
The PREP-STATUS preparation status policy documents labels and escalation.
Eight PREP-STATUS rules
Published STATUS-MAP: backend table → FR portal label + FAQ
Next step: each status includes milestone + ship ETA if sla_ok
Stuck threshold: same status > prep_sla_days → prep_status_stuck PREP-FLOW escalation
Hold transparency: fraud/address hold = explicit label + customer action
Partial clarity: split status line by line if partial fulfilled
Preorder distinct: preorder tag = label #187, not "warehouse preparation"
Email sync: transactional emails use identical portal STATUS-MAP
Agent script: STAT-* macro cites mapping, do not invent status
Publication /pages/order-status
FR status glossary, visual order timeline, customer account link. Bot #396 and #408 can cite URL.
Coordination #395 PREP-TIME
prep_sla_days feeds STATUS-MAP sla_ok vs miss. Two linked Notion policies: PREP-TIME (days) + PREP-STATUS (labels).
Quarterly review
Support + ops: prep_status_meaning verbatims, stuck rate, adjust labels if confusion persists.
How to apply the STAT-FLOW in eight steps?
The STAT-FLOW framework structures the ticket status preparation response.
Eight steps ST-1 to ST-8
ST-1 Lookup order: fulfillment_status, tags, holds, created_at
ST-2 Classifier: typology prep_status_* section 3
ST-3 Mapper STATUS-MAP: correct label + next step
ST-4 Evaluate normal: sla_ok vs stuck vs hold vs miss
ST-5 Explain customer: macro STAT-* grounded ST-3
ST-6 Action if needed: release hold, escalate PREP-FLOW, cancel collect
ST-7 Tag outcome: explained_ok | escalated_prep | hold_resolved
ST-8 Document: verbatim confusion, mapping gap if label is unsuitable
ST-4 stuck vs normal
D+2 unfulfilled sla 1-2 d: normal, STAT-MEAN-01. D+5 sla 1-2 d: stuck, reroute PREP-FLOW #395 PR-5+. Do not promise delivery, explain prep vs transit.
ST-5 prep_status_wismo_confusion
"Your order is in warehouse preparation, not yet shipped. No tracking number until status changes to "Shipped". Estimated shipping [date]."
ST-6 hold types
address_hold: address confirm link. fraud_hold: "24-hour verification". stock_hold: explain ship complete policy #357.
Which STAT-* macros and portal touchpoints?
Eight preparation status agent macros and customer account touchpoints.
STAT-MEAN-01 (meaning in preparation)
" "In preparation at warehouse" means that your order #[X] is paid and currently being prepared (picking, packing, labeling) before being handed over to the carrier. It has not been shipped yet. Estimated shipping: [date] (#395). "
STAT-STUCK-01 (normal unchanged status)
"The status remains "Preparation" until shipping. Your order is within the normal timeframe ([X] business days). No need to worry before [date]."
STAT-MISS-01 (delay, escalation prep)
"Timeframe exceeded. Warehouse team alerted. Revised shipping [date]. Commercial gesture if > 2 days beyond promise (#395)."
STAT-PARTIAL-01 (partially fulfilled)
"Package 1 shipped [tracking]. Item [SKU] in preparation · shipping [date]."
STAT-HOLD-01 (hold address/fraud)
"Status "Verification in progress": [reason]. Action required: [link/step]."
STAT-PREORDER-01 (reroute #187)
"Pre-order: status "Pre-order confirmed" · delivery [window]. Distinct from stock preparation (#187)."
Portal touchpoints
Customer account: STATUS-MAP labels + timeline
Page /pages/order-status glossary
Confirmation email: initial label + next step
Order status app Shopify or custom portal
FAQ chat widget glossary link
Visual account timeline
Order received → Preparation → Shipped → Delivered. Highlight current step. Reduces prep_status_meaning by 35-45%.
How do I set up the Shopify status portal?
The Shopify status portal configuration makes STATUS-MAP visible to the customer.
Four implementation options
Native account: fulfillment status + EN translation apps
Order status app: ParcelPanel, Track123, custom labels
Metafields order: prep_substatus → theme display
Custom portal: API order + STATUS-MAP frontend
Metafields prep_substatus
Values: queued, picking, packed, label_pending, hold_address, hold_fraud, hold_stock. WMS webhook update → portal refresh. Agent reads same ST-1 metafield.
Sync WMS → portal
ShipBob, Sendcloud, 3PL API: map internal status → prep_substatus metafield. Customer sees progress without ticket. Reduces prep_status_stuck.
Partial fulfilled display
Line-level status if partial: 2 lines, 2 statuses. No global status "in preparation" if 1 line shipped.
Tests before STATUS-MAP launch
10 scenarios: sla_ok, cut_off, hold, partial, preorder, peak. Verify portal + email + agent macro are consistent.
Which prep_status KPIs should be measured?
Preparation status KPIs drive labels and self-service.
Eight key metrics
prep_status_ticket_rate: prep_status tickets / unfulfilled orders
prep_status_meaning_share: prep_status_meaning / total prep_status
prep_status_stuck_rate: stuck tickets / prep_status (post SLA)
wismo_misroute_rate: unfulfilled handled WISMO / wismo tickets
prep_status_fcr: resolved STAT-FLOW without escalation / prep_status
prep_status_email_mismatch: portal ≠ email reports
portal_status_views: visits /pages/order-status vs tickets
prep_status_csat: satisfaction tags prep_status tickets
DTC Benchmark
prep_status_meaning_share < 25% post STATUS-MAP, wismo_misroute < 10%, prep_status_fcr > 70%, prep_status_csat > 4.1/5.
Weekly dashboard
Typology breakdown, stuck vs meaning ratio, portal update vs stuck tickets correlation.
Product alert
prep_status_meaning_share > 40%: review STATUS-MAP label confusion. Adjust text label or visual timeline.
Before/after STATUS-MAP
Compare 30 days pre/post portal labels launch: delta prep_status_ticket_rate ROI justification.
Which anti-patterns should be avoided on preparation statuses?
Ten "in preparation" status anti-patterns to banish.
1. "In progress" label alone
Zero information. prep_status_meaning guaranteed.
2. Displaying unfulfilled to customer
Shopify jargon. STATUS-MAP EN mandatory.
3. Premature "Shipped" status
Before fulfilled. Chargeback + wismo chaos.
4. Agent invents status
Macro STAT-* must cite mapping only. No "on its way" if unfulfilled.
5. Email ≠ portal label
prep_status_email_mismatch. Sync relationals.
6. Ignoring partial fulfilled
Wrong global status. Line-level STAT-PARTIAL-01.
7. Invisible hold for customer
"Preparation" status during fraud review for 5 days. STAT-HOLD-01 label.
8. Preorder label as warehouse prep
Confusion over month-long delay. Distinct STAT-PREORDER-01.
9. Routing stuck to WISMO
Unfulfilled ≠ transit. ST-2 classifier upstream.
10. No glossary on /pages/order-status
Agents repeat meaning 100x/day. Missing self-service.
11. WMS update without portal sync
Warehouse packed, customer sees "preparation" for 48 hours. Metafield sync.
How does Qstomy clarify statuses in preparation?
Qstomy on Shopify: lookup STATUS-MAP, explain prep vs ship, stuck detect, hold routing, partial line status, handoff PREP-FLOW #395, glossary /pages/order-status cite.
Qstomy prep_status Capabilities
prep_status_intent: 12 typologies section 3
prep_status_map_lookup: ST-3 STATUS-MAP auto
prep_status_stuck_detect: sla compare → escalate
prep_status_no_wismo: block tracking if unfulfilled
prep_status_partial_explain: line-level templates
prep_status_glossary_link: /pages/order-status in chat
Complement #395 #396 #408
PREP-TIME #395 = SLA days. PREP-BOT #396 = delay automation. PREP-STATUS #407 = labels. Bot custom #408 = Shopify metafields statuses. Consistent pipeline.
Quantified DTC Scenario
Decor 380 tickets/month prep, single status "In progress".
After PREP-STATUS + Qstomy: prep_status_ticket_rate -43%, wismo_misroute -58%, prep_status_fcr 74%, prep_status_csat 4.3/5.
Explore customer support and request a demo.
What checklist should be used to deploy PREP-STATUS?
PREP-STATUS Checklist (12 steps)
Audit current portal wordings + emails + ticket verbatim
Draft STATUS-MAP 8 mappings section 4
Document PREP-STATUS policy 8 Notion rules
Create STAT-* macros section 7 helpdesk
Publish /pages/order-status glossary + timeline
Configure portal metafields prep_substatus or app
Sync WMS → metafield if 3PL
Align transactional emails STATUS-MAP
Train agents STAT-FLOW 30 min
Route classifier ST-2 upstream WISMO/prep
Dashboard KPI prep_status weekly
Quarterly review labels vs verbatim
In brief
#407 = visible status, not delay in days (#395)
STATUS-MAP : backend → FR wording + next step
STAT-FLOW : lookup → map → explain → escalate if stuck
Prep ≠ shipped : clear distinction vs WISMO #184
KPI wismo_misroute : measures correct routing
FAQ
Difference with #395 prep delay?
#395 = how many days before shipping. #407 = what the displayed wording means.
Should status change daily?
No if sla_ok. Next step date is enough. Substatus WMS optional if sync is available.
Relation with bot #408?
#407 policy mapping agents. #408 bot executes custom Shopify statuses in chat.
Partial fulfilled how to display?
Line-level: 1 shipped tracking, 1 in preparation. No single global status.
Fraud hold: tell the client?
Yes, wording "Verification in progress". Do not hide under "preparation".
Going further
This week: audit current portal wordings, draft STATUS-MAP, publish /pages/order-status, train agents STAT-MEAN-01.
Share this guide #407 with ops and support: a clear status is worth an hour of repeated macro every day.
Should WMS sub-statuses be visible to the customer?
Recommended if sync is reliable. Otherwise, estimated shipping date + "Warehouse preparation" wording is enough.
Enzo
July 1, 2026
