[C10] Orders List

Cancelled orders — "Show cancelled (N)".

Orders with nothing attached — "Show orders with nothing attached (N)". These have no line item and no participant or membership behind them; production carries thousands, concentrated in one organisation, and they would otherwise be most of that list.

Clicking the button opens the order in WooCommerce admin, in a new tab. This is what staff need: the order as the store holds it.

Its menu offers Copy payment link, enabled only for an unpaid or pending order that carries a pay link. For any other order the item stays visible but disabled, saying why.

AF-1 — No orders in scope. Say so plainly, and say what the scope was, rather than rendering an empty table.

AF-2 — A historical event has no orders in its scope. Orders recorded before line items existed cannot be matched to an event. The empty state explains this and links to the organisation-wide list, where they do appear.

AF-3 — Totals unavailable. Some orders carry no recorded prices. Their total renders blank with an explanation, never as zero — a zero total asserts a free entry, which is a different fact.

AF-4 — Sold by another organisation. The row is visible and the seller is named in its own column, so the operator can see why a total or an action may not be theirs to act on.

AF-5 — Permission denied. The scope is not offered in the sidebar at all, rather than offered and refused.

Order actions. Mark paid, refund and cancel live on C06. A list row opens the order; it never mutates one.

Ledger figures. Recording a payment is transaction logging; posting it is a separate concern, and no financial statement is derived here.

Bulk operations. No multi-select, no bulk status change. Each order is opened on its own.

Creating an order. There is no "new order" affordance on this screen.

One component, several anchors (2026-09-20). Three screens sharing one component and differing only by base filter, rather than one screen with a kind selector. Two sidebar rows pointing at one route would make the active-highlight ambiguous, which is the defect the navigation rework removed; and a scope held in a query parameter is the form that rework deliberately canonicalises away.

Widening stays within the family (2026-09-20). An event’s orders widen to Event orders. Jumping straight to every order would discard the operator’s context in one click.

Scoping is by line item (2026-09-20). An order belongs to an event because a line says so. Orders predating line items stay reachable at organisation level and in the detail screen, and are excluded from event and membership scope rather than being guessed at.

Cancelled and unattached hidden by default (2026-09-20). Both are real records worth keeping and neither is what an operator came to see. The count on each toggle is what stops hiding from becoming concealment.

Blank beats zero (2026-09-20). Where no price was recorded, the total is blank with a reason. Rendering zero would assert something the data does not say.

The seller column appears only when it differs (2026-09-20). Most orders are sold by the organisation viewing them; a column that repeats the obvious on every row earns nothing.

The WooCommerce admin link is a per-store template (2026-09-22). Where WordPress is installed and how WooCommerce stores its orders vary by site, and independently of each other. Tour de Worcester is a Bedrock install, with WordPress under /wp and orders in WooCommerce’s order tables; Western Cape Schools Cycling and Helderberg are standard installs still storing orders as posts. A store can also change how it stores orders without its integration changing. A template records the answer per store instead of deriving it from the integration type. Typing it by hand is error-prone, so a guided builder is planned as later work.

The payment link is copied, not linked (2026-09-22). Staff share it with a customer who has yet to pay; they never pay on a customer’s behalf.