E-commerce
July 1, 2026
A Shopify store can use custom statuses to describe the reality of its operations: in production, in quality control, waiting for supplier, ready to ship, or blocked for verification.
These statuses are useful internally, but they can be incomprehensible to the customer if they are not translated. The chatbot can explain what the status means, what happens next, and when support needs to step in.
This guide explains how to make custom Shopify statuses clearer with an AI chatbot.
Summary
Why do custom statuses need to be explained?
A status like “awaiting fulfillment” or “quality check” may be clear to the team, but not to the customer. They primarily want to know if their order is progressing, if any action is expected from them, and when it will be shipped.
The chatbot must therefore translate the status into customer-friendly language and provide a realistic next step.
An order status is only useful if the customer understands what it means for them.
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
Which statuses to cover?
Frequent statuses are order received, payment confirmed, in preparation, in production, awaiting supplier, quality control, partially shipped, ready to ship, shipped, blocked, or canceled.
Each status must have a short explanation and an associated action: wait, provide information, track a package, or contact support.
How do you translate an internal status?
The translation must explain what is happening now. For example, “quality control” can become: “Your order is checked before shipping to ensure that the product conforms to standards.”
The bot must avoid internal terms, codes, and abbreviations. The customer does not need to know the exact workflow to be reassured.
This translation reduces repetitive tickets. A well-explained status already answers the two main questions: where is my order, and what happens next?
How to manage deadlines?
If a status implies a wait, the bot must provide an estimate if one exists and specify if it is indicative. For manufacturing or a supplier, the delay may vary.
The response must explain what will trigger the next step: completion of manufacturing, supplier receipt, quality validation, or handover to the carrier.
What should I do if the status does not change?
A frozen status worries the customer. The bot must check how long it has been since it changed and compare it with the normal delay of this step.
If the delay has been exceeded, it must transfer with the status, the last update date, and the order.
Which flow to follow?
The flow must start from the actual status.
Identify the order and the Shopify or custom status.
Translate the status into a comprehensible phrase.
Indicate the next expected step.
Compare the time spent in this status with the normal timeframe.
Transfer if the status is stuck or requires human action.
Which messages should be used?
For a preparation: "Your order is being prepared. It will be handed over to the carrier once the package is ready."
For a manufacturing: "Your product is currently being manufactured. The delay may depend on the model and the options chosen."
For a blockage: "The status has not changed for longer than expected. I am forwarding the request for verification."
When to transfer?
Transfer is necessary if the status is blocked, if an internal action is required, if the customer disputes the delay, or if the status implies a manual verification.
The bot must transmit the order, the status, the update date, the expected delay, and the customer's question.
Which KPIs should be monitored?
Follow issues by status, blocked statuses, transfers, average delays per stage, and conversations where the customer says they do not understand the follow-up.
This data shows which statuses need to be renamed or better explained.
Which mistakes should be avoided?
Avoid displaying untranslated internal statuses, promising shipping before validation, or responding "in progress" without a next step.
The chatbot should give meaning to the order tracking, not repeat a technical label.
How can Qstomy help?
Qstomy can use the customer, cart, and order context to answer clearly, then hand over sensitive cases with an actionable summary.
The chatbot simplifies complex questions without creating promises that the brand cannot keep.
Explore AI support, the AI sales agent, or request a demo.
STAT-BOT Checklist (12 steps)
Document STATUS-MAP #407 + custom_status codes
Create order_status.* metafields section 5 Shopify
Configure WMS/Flow sync → metafields
Publish /pages/order-status custom status glossary
Export Notion glossary JSON → bot
Configure 12 bot_cust_stat_* intents section 3
Implement flows SB-1 to SB-8 + upstream router section 2
Enable guardrails no shipped unfulfilled + stale detect
Integrate STAT-FLOW #407 handoff fields SB-7
Staging tests 10 scenarios MTO, partial, stuck, fulfilled reroute
Align Klaviyo emails custom_status change labels
Weekly custom_stat KPI dashboard + transcripts audit
In brief
#408 = custom status bot, executes PREP-STATUS #407
Grounded metafields: zero status hallucination
STAT-BOT: lookup → glossary → explain → handoff
Router: fulfilled WISMO, custom STAT-BOT, else PREP-BOT
KPI false_status_promise: absolute zero target
FAQ
Difference with #407 agents?
#407 policy labels + macros. #408 bot explains metafields 24/7 in chat.
Are custom status needed for everyone?
No. Standard unfulfilled → PREP-BOT #396 is enough. Custom if MTO, multi-step, enriched portal.
Does the bot modify metafields?
No, read-only. Ops/WMS/Flow write. Bot reads API each session.
Relation to PREP-BOT #396?
Complementary. Upstream router. STAT-BOT if custom metafield present.
Shopify Plus required?
No. Order metafields on all plans. Flow optional. Compatible status apps.
Go further
This week: define custom_status codes, create Shopify metafields, sync Notion STATUS-MAP, test STAT-BOT staging on 5 MTO orders.
Share this #408 guide with ops and e-com: a custom status has value only if the bot reads it, not if it invents it.
How many custom status max?
Recommended 4-8 timeline steps. More = confusion. Group internal ops steps.
Enzo
July 1, 2026
