Order detail
Route: /org/ecom/orders · Permission: View customer orders for the e-Commerce store
1. What the detail view is
An order expands in place on the workbench rather than opening a separate page — so the list stays visible and a fulfilment run is not a sequence of back-navigations.
2. What it contains
3. The expanded card
Each item carries its own requested section and date, shown inline — which is what lets one order span two fulfilment sections. See operations board.
4. Field reference
| Element | Notes |
|---|---|
| Order reference | Prefixed per project |
| Status badge | One of six |
| Payment chip | Independent of status |
| Items | With per-item schedule |
| Money | Product, tax, total |
| Customer | Name and contact — masked in these figures |
| Actions | Gated per permission |
What edit actually covers
Edit order details (notes, internal flags) after placement is "Edit order details (notes, internal flags) after placement" — not
status, price or items. Those are review and refund permissions.
5. The admin contract
| Prerequisite | Without it |
|---|---|
| View customer orders for the e-Commerce store | No access |
| Review and act on customer orders (status transitions) | No status changes |
| Edit order details (notes, internal flags) after placement | No notes or internal flags |
6. Downstream
Every action taken here surfaces to the shopper in my orders.
7. Don't confuse this with…
| Thing | Why it differs |
|---|---|
| Order detail (this page) | The admin's expanded card |
| Shopper order detail | The customer's own view |
| Job order | A print for the bench |
8. Troubleshooting
| Symptom | Cause |
|---|---|
| Actions missing | The matching permission is absent |
| Items in two sections | Correct — items schedule independently |
| Cannot change a price | Not editable post-placement; refund instead |