Shopify order statuses vs your own workflow statuses
Payment and fulfillment statuses answer essential questions, but they do not tell the whole production story. Add useful working stages while keeping Shopify’s records tied to real events.
The OrderPilot team·
For eleven weeks, the Madison sofa order reads “Partially paid · Unfulfilled.” During that time, the vendor accepts it, starts production, changes the expected ship date, sends it, and delivers it to the store for inspection. The Shopify labels can be correct throughout that illustrative journey.
Use payment and fulfillment statuses for the facts they describe. Use working stages for the jobs your team must complete between the sale and the handover. In OrderPilot, those stages can connect to purchasing, receiving, signing, and delivery while the customer sees a simpler account of progress.
Keep payment, fulfillment, and production separate
Shopify tracks several kinds of order state, including payment, fulfillment, returns, and whether an order is open, archived, or canceled. Its order-status reference explains what those labels mean.
A payment status answers a money question. A fulfillment status answers a fulfillment question. Neither is a reliable substitute for “the vendor acknowledged the specified fabric” or “the warehouse inspected the table.”
Do not mark a piece fulfilled merely to make the screen look more advanced. Equally, a production delay does not undo a payment already received.
The customer’s sofa can be paid for and still unmade. That is normal for the sale type. The working record needs enough detail to explain what happens next without changing the meaning of the financial or fulfillment record.
Give each working stage an owner and evidence
A useful stage names a state of the work that somebody can verify. “In production” should mean more than “we sent an email last week.”
For each stage, define the evidence, the responsible role, and the next action. A vendor acknowledgment belongs with the purchase. An inspection result belongs with the arrival. A delivery appointment belongs with the delivery arrangement.
Avoid creating stages solely because the name sounds reassuring. If nobody knows what qualifies an order to enter or leave a stage, the label will eventually become a matter of personal preference.
A concise process is easier to maintain than a long list of almost-identical labels. “Nearly ready,” “almost ready,” and “ready soon” are not three different warehouse tasks.
Start with a working list the team can explain
The following is a suggested starter set, not a claim that these are all built-in names. Use OrderPilot’s existing system statuses where they fit and add store-defined steps for the rest.
| Staff stage | Evidence or work completed | Owner | Customer-facing group |
|---|---|---|---|
| Sent to Vendor | Required vendor purchase instructions sent | Purchasing | Confirmed |
| Vendor acknowledged | Correct specification acknowledged | Purchasing | In production |
| In Production | Vendor confirms the build stage | Purchasing | In production |
| Vendor dispatched | Shipment information received | Purchasing | In production |
| Received for inspection | Goods arrived; inspection pending | Receiving | In production |
| Quality Check | Inspection work underway | Receiving/service | In production |
| Delivery scheduled | Usable goods and appointment agreed | Delivery team | Ready |
| Delivered | Actual customer handover recorded | Delivery team | Complete |
Keep “Vendor dispatched” separate from the customer’s delivery journey. The piece leaving the maker is not the same event as the piece leaving your store for the customer.
The status map guide expands this planning exercise. Choose the stages that answer real questions in your own business.
Show customers a smaller, clearer set of stages
Customers need to understand progress and their next action. They usually do not need the team’s internal purchasing or inspection labels.
OrderPilot groups staff statuses under customer-facing groups. Several detailed steps can therefore appear as “In production” to the customer while the team distinguishes acknowledgment, manufacture, and vendor dispatch. Decide which steps are visible and what the group means. Avoid publishing a “Ready” message while the furniture is waiting for inspection or a required accessory.
Built-in system statuses keep their names; stores can rename their own statuses, the non-system defaults, and the customer-facing groups. That gives you useful wording control without duplicating Sent to Vendor simply to change its capitalization.
The public and private statuses guide helps decide what belongs in each view.
Build connections around events the record can prove
OrderPilot’s status map uses connections expressed as When, Only if, and Then. A connection can move automatically after a supported event or wait for staff to make the move.
Start with a small set:
| Connection | When | Only if | Then |
|---|---|---|---|
| Purchasing progress | PO-send event | The required purchasing condition is met | Move to the appropriate vendor-sent stage |
| Arrival progress | Goods-received event | The required receipt condition is met | Move to the next receiving stage |
| Customer handover | Delivery event | The required delivery condition is met | Move to the completed stage |
These are planning examples. Choose the actual events and conditions available in the editor, then test them against your order. A multi-vendor sale may be only partly sent; a dining set may be only partly received. Keep signing and payment requirements in the process where the store needs them. A convenient automatic move should not bypass an unresolved approval or customer decision.
Let staff see why a move is waiting
The Next status control shows moves that are ready and the reasons other moves are waiting. That gives the associate an answer more useful than an unavailable button. For the sample Madison order, purchasing may be complete while receiving is still pending. The team should see which part is missing and who owns it.
When the situation does not fit an automatic event, use a deliberate staff step. A person deciding that a visible mark has passed inspection is a different kind of evidence from a system recording a quantity received.
Keep exceptions explicit. If someone has authority to override a requirement, the resulting record should explain the decision rather than making the normal process appear to have happened.
Send an update when the change matters
A status change can trigger an OrderPilot email when the store configures that notification. Write the message around what changed and what the customer should expect next.
For the sofa, an arrival message might explain that the piece is at the store and being inspected. A later readiness message can invite the customer to settle the delivery arrangement.
Status texts use fixed templates and require SMS to be enabled for the store. Use email for the tailored wording and richer explanation the customer needs.
The order-update message examples provide a starting point. Preview the customer-facing result and avoid sending several nearly identical messages as staff complete neighboring internal steps.
Keep Shopify Flow automation coordinated with these notifications. The Flow recipes guide explains where another trigger might be useful and where it can duplicate the same message.
Test before publishing the process
OrderPilot lets you draft the status map, test it against an order, and publish the reviewed version. Use a sample order that contains the complications your store actually sees.
Test a partial vendor send, a partial receipt, and a customer-facing change after signing. Ask whether each event produces the intended stage and notification, and whether a blocked move explains the missing condition. Read the timeline afterward. Another colleague should be able to explain the sequence without having watched the test.
This is also the moment to inspect any older customer-status-page customization. Shopify’s checkout customization guidance describes the move away from legacy scripts. A decorative progress label on a page should not become the only record of the store’s actual work.
Keep both records true through delivery
OrderPilot fulfills a line in Shopify when the goods leave the store. Its production stages can explain the earlier work while the fulfillment record continues to describe the physical handoff.
For an order containing a lamp taken home immediately and a sofa delivered later, the line-level records matter. The lamp’s progress should not imply that the sofa has also left.
When the team can answer “what happened, what is waiting, and who acts next,” the status system is doing its job. Continue with selling made-to-order furniture on Shopify to connect the stages to the full customer order.
Sources
- Understanding your order statuses — Shopify Help Center.
- checkout.liquid — Shopify developer documentation.
A useful stage names work that somebody can verify.
