Order status is the business lifecycle
Processing, Fulfilled, Cancelled, Refunded, On Hold, and Failed describe the overall order outcome and operating decision.
eCommerce order operations
CMS Max Order Status Guide
Read order health across three separate tracks: lifecycle, fulfillment, and payment.
CMS Max keeps the overall order state distinct from the physical fulfillment journey and the payment result. That separation helps operations answer the right question without treating a shipped package, paid transaction, and completed order as the same event.
- Order lifecycle
- Fulfillment progress
- Payment state
- Method-specific actions
Operating model
One order can carry several valid statuses at the same time.
A paid order may still be processing. A shipped order may not be delivered. A cancelled order may have a voided or refunded payment depending on gateway state.
Fulfillment status is the handoff journey
Shipping, pickup, local delivery, DoorDash, and custom methods use different intermediate fulfillment states before completion.
Payment status is financial state
Pending, Paid, Failed, Refunded, Partial Refund, On Hold, and Voided describe what happened at the payment provider.
Current CMS Max capability
Use the intermediate state that matches the fulfillment method.
Orders begin in Processing. CMS Max then exposes a method-appropriate next fulfillment action while preserving the overall order and payment states.
Carrier shipping
Progress from Processing to Shipped and then Fulfilled. Label and carrier workflows may automate part of this path when configured and verified.
In-store pickup
Move from Processing to Ready for Pickup, notify the customer, and mark Fulfilled after the order is collected.
Curbside pickup
Use Ready for Pickup for arrival and handoff coordination, then mark the order Fulfilled after delivery to the vehicle.
Local delivery
Use Out for Delivery after the driver departs, then Fulfilled after the merchant confirms drop-off.
DoorDash delivery
Use Handed to Driver for the provider handoff and Fulfilled after confirmed delivery, subject to the active integration behavior.
Custom fulfillment
Custom methods can move directly from Processing to Fulfilled because they do not have a built-in intermediate state.
Step-by-step workflow
Update status from evidence, not assumption.
Each change should reflect a real payment response, packing milestone, pickup event, carrier event, delivery handoff, cancellation decision, or completed order outcome.
Review
Open eCommerce > Orders, filter the queue, and inspect the order, payment, fulfillment method, notes, and history.
Verify
Confirm the real event: payment captured, label created, order packed, customer notified, driver handoff, delivery, cancellation, or return.
Update
Use the available action or status control for the order and fulfillment method. Some provider-connected events may update automatically.
Communicate
Send the correct customer notification and record internal context without rewriting customer-submitted notes.
Reconcile
Compare the CMS Max state with the gateway, carrier or delivery provider, inventory, customer communication, and financial records.
Practical reference
Separate the three status vocabularies.
The same label can appear in more than one track, so read the badge heading and history before acting.
- Overall order
- Processing, Fulfilled, Cancelled, Refunded, On Hold, Failed.
- Fulfillment
- Processing, Shipped, Ready for Pickup, Out for Delivery, Handed to Driver, Fulfilled, Cancelled.
- Payment
- Pending, Paid, Failed, Refunded, Partial Refund, On Hold, Voided.
- Refund vs. void
- A void reverses an eligible unsettled transaction; a refund returns money after the provider treats the transaction as settled. Provider state is authoritative.
Current references
Use live product and provider evidence.
Interfaces, policies, plans, services, pricing, and requirements can change. Verify the current CMS Max configuration and official provider sources during implementation.
Understanding Order Statuses FAQ
Resolve the practical questions before launch.
Turn each answer into configuration, representative testing, monitoring, ownership, and a documented recovery path.
Why is a paid order still Processing?
Paid describes the payment result. Processing describes the overall order or fulfillment work that still needs to happen.
Does printing a label mean the package was delivered?
No. A purchased or printed label can support the Shipped workflow, but delivery requires a later carrier event or an intentional merchant confirmation.
What status should pickup orders use before collection?
Use Ready for Pickup after the order is prepared and the customer can collect it, then Fulfilled after the actual handoff.
Are refund and void interchangeable?
No. They represent different gateway states. CMS Max uses provider-aware actions where supported; verify the payment history and provider response before promising the customer an outcome.
Can staff edit the customer checkout note?
Customer notes represent what the shopper submitted and are read-only. Use the separate internal Order Notes field for staff context.
Build for real operations
Give every order a state the team can trust.
CMS Max brings order lifecycle, fulfillment milestones, payment state, notes, notifications, and history into one operational record.
Building Relationships with Web Developers and Marketing Agencies that want better results
The world's fastest and most SEO friendly website code.