Operations board
Route: /org/ecom/orders → Operations · Delivery date · Permission: View customer orders for the e-Commerce store
1. What the board is
The same orders as the ledger, pivoted onto when the customer wants them rather than when they were placed — grouped by delivery date and fulfilment section.
It is the view a kitchen or packing bench works from.
| Operations board | Financial ledger | |
|---|---|---|
| Date basis | Items' requested_date | Order's placed_at |
| Grouped by | Delivery date, then section | Order date |
| Answers | What goes out today? | What did we sell? |
| Export PDF | ❌ | ✅ |
2. Why the two views disagree
That is correct behaviour, not duplication. Reconciling "what we sold" against "what we shipped" means comparing two different questions, and the date window means something different in each.
3. The board
Mixed-section orders
An order's items each carry their own requested_section and requested_date. An order whose
items span two sections is therefore not a single-section order.
The schedule is shown inline on the card at item level. An earlier implementation bucketed a whole order under its first item's section, which put the rest of the order in the wrong place — the current behaviour shows each item where it belongs.
4. Field reference
| Element | Behaviour |
|---|---|
| Delivery date group | From the items' requested_date |
| Section group | From the items' requested_section |
| Order card | As in the ledger, plus the per-item schedule |
| Unscheduled orders | Matched by an "any open item" fallback so they are not lost |
5. The admin contract
| Prerequisite | Without it |
|---|---|
| Items with a requested date | Orders fall to the unscheduled fallback |
| Fulfilment sections | Nothing to group by |
| Review and act on customer orders (status transitions) | The board is read-only |
6. Downstream
The board is the source for the job order print — the slip the fulfilment station works from.
7. Don't confuse this with…
| Thing | Why it differs |
|---|---|
| Operations board | Delivery date |
| Financial ledger | Order date |
| Showcasing schedule | When items are offered, not when an order ships |
| Kanban in Orbit Ops | Tasks, not orders |
8. Troubleshooting
| Symptom | Cause |
|---|---|
| An order is on a different day than expected | Operations uses delivery date |
| No Export PDF | Export is Financial-only |
| An order appears with no section | Its items carry no requested section |
| Counts differ from Financial | Different date basis — both are right |