The order grid is where a Magento store’s promises meet reality. A well-run order workflow - statuses that mean something, fulfilment steps in the right order, exceptions surfaced daily - is the difference between an operations team that scales and one that drowns at 100 orders a day. Here is the model and the practice.
States vs Statuses
Magento separates state (the machine: new, processing, complete, closed, canceled) from status (the label: “Pending”, “Shipped”, “Awaiting Stock”). Custom statuses attach to states - “Picking”, “Awaiting Courier”, “Fraud Review” all hang off processing. This distinction matters: reports and integrations key off state; humans read statuses. Add custom statuses for your real workflow steps rather than stretching “Processing” to cover everything.
The Standard Fulfilment Flow
- Order placed - state
new; payment authorised (or captured, per gateway config) - Invoice - capture payment; order moves to
processing. Auto-invoice on capture is the norm for instant-dispatch goods - Ship - shipment created with tracking; customer emailed; state stays
processinguntil all items ship - Complete - all invoiced and shipped; the order is done
Deviations: backorders (ship when stock lands), partial shipments (multiple shipments per order), split fulfilment across warehouses under MSI. The model handles all of them - the discipline is using the steps, not bypassing them with status edits.
Grid Operations That Scale
- Mass actions: invoice, ship, cancel, hold in bulk - but build the habit of checking order detail before mass actions on exceptions
- Saved views/filters: “today’s unfulfilled”, “on hold”, “payment review” - the grid’s filters are the ops team’s dashboard
- Columns that matter: add the fields your workflow triages by (shipping method, payment method, custom status) instead of opening every order
Exception Handling: Where Teams Win or Drown
Define the exception queues explicitly: payment review, address validation failures, out-of-stock holds, fraud flags. Each needs an owner and a daily sweep. Orders rotting in “Payment Review” for a week are how one-star reviews begin.
Automation That Pays
- Auto-invoice on capture: remove the manual step for standard orders
- ERP/OMS push on placement (queued, immediate) with status flowing back (see the ERP integration post)
- Notifications on stuck states: any order in
processingolder than your dispatch SLA should ping someone
Order management is a system, not a screen: statuses that map to reality, fulfilment steps used properly, exceptions with owners, and automation for the volume. Get the system right and the grid becomes quiet - the best possible sign.