Orders
Read an order, and update its three independent statuses — where the order is, whether it is paid, and whether it has shipped.
Orders live under Manage → Orders. They are created when a shopper checks out on your published storefront; you do not create them by hand here, and the last section explains why.
The list searches by order number or customer name and filters by status. The columns are Order, Customer, Date, Status, Payment, Fulfillment, Total.
Three statuses, and they are independent
This is the part worth getting right early. An order does not have a status — it has three, and they do not drag each other along.
Order status — where the order is in your process.
| Pending | Just placed, nobody has touched it |
| Confirmed | You have seen it and accepted it |
| Shipped | It has left the warehouse |
| Delivered | The customer has it |
| Cancelled | Not happening |
Payment — whether the money has arrived.
| Unpaid | |
| Partial | A deposit, an instalment |
| Paid | |
| Refunded |
Fulfillment — whether the goods have gone.
| Unfulfilled | |
| Partial | Shipped in more than one parcel |
| Fulfilled |
Why three: a cash-on-delivery order that has arrived but not been collected for is Delivered + Unpaid. A prepaid order that has not shipped is Pending + Paid. Collapse all three into one field and neither of those very ordinary situations can be expressed.
Update them in the Update status block on the order's detail page. You can change one without touching the other two — which matters when several people work the same orders: a warehouse marking a parcel shipped cannot accidentally overwrite its payment state.
What is in an order
Items — each line with its unit price, quantity and SKU.
Totals — Subtotal, Discount, Shipping, Tax, Total.
Customer, Ship to, Bill to — who bought it and the two addresses.
Note — whatever note came with the order.
Line items and totals are history. They record the sale that happened, at the prices of that moment, and cannot be rewritten. If a product's price changes tomorrow, today's order keeps today's numbers — which is what you need when the books have to reconcile.
Deleting an order
Delete order removes it permanently and cannot be undone. The dialog says so.
Think twice: a deleted order disappears from every revenue report. For an order that fell through, Cancelled is usually the better answer — it keeps the record while still saying plainly that it was not fulfilled.
Why you cannot create an order by hand
There is no "New order" button, and that is a decision rather than a gap.
Creating an order is checkout: it redeems a discount code under a lock, enforces that code's usage limits, and computes the totals from a live catalogue. A plain "create order" button would either bypass all of that — minting revenue records that nothing reconciles — or quietly become a second checkout that drifts from the real one.
The same holds through the API: POST /api/v1/orders answers 405 with the
code orders_are_read_only, so an integration author knows the boundary is
deliberate. See The public API.
Updated 22/08/2026