Orders flagship · round 2 (quiet pass) — Orders index + Order detail

Frank spends 65–80% of his admin time here. Every status, column, action, step, factory code and product type below is the real one (TRUTH-ORDERS, 3.0_Backend origin/main 6787e7873, prod dump, OpenAPI 0577c24). Order numbers are bare 4-digit ids. Anything without real backing is drawn as a tagged ghost. People are placeholders; dotted = example value.

Orders index · 11 boards

  • O01 Orders · default view (Active) ★
  • O02 Customise tabs (choose + reorder)
  • O03 Saved views (menu + save as new)
  • O04 Column chooser
  • O05 Peek sheet (Space)
  • O06 Bulk: Delivered → Complete in batches of 100
  • O07 Empty: On Hold (0 today)
  • O08 Filtered empty: search finds nothing
  • O09 Long strings + CJK
  • O10 Phone · /m/orders (order lookup)
  • O11 How you’d use it (daily flows)

Order detail · 19 boards

  • D01 Order 4521 · Overview tab ★
  • D02 Action model · one header in every status
  • D03 Matrix · status × visible actions
  • D04 Garments tab (Order Summary)
  • D05 Designs tab
  • D06 Measurements tab
  • D07 Production tab
  • D08 Pricing tab
  • D09 Notes tab
  • D10 Photos tab
  • D11 Issues tab
  • D12 Activity tab
  • D13 State · loading skeleton
  • D14 State · permission denied (support role)
  • D15 State · “someone else changed this” (measurements)
  • D16 Raise Issue with “Put Order On Hold”
  • D17 Cloud print + job progress (Jobs list)
  • D18 Settle · confirmation ladder
  • D19 Phone · /m/orders/4521

The action model in one line

One dark next-step button by status (Edit · Assembly ▾ · Build ▾ · Resolve hold) + a Cloud print ▾ split (cloud: Order bill / Shirt code · PDF: Mark-Up / Order / Shirt Tag / QC Tag) + Edit + Raise issue (holds live here) + ⋯ grouped by intent. 4–5 controls instead of 8–10.

Tags

proposalneeds backendAPI onlydotted = example value

Open questions

see ORDERS-R1.md §Open questions · 1a/1b …