The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.
| # | Surface | Action | Capability | Expected | Provenance |
|---|---|---|---|---|---|
| 1 | /console/{tenantId}/orders | Choose Orders within Orders and Inventory. | CAP-COM-ORD-010 | The paged table presents recent purchases first, including the customer, state, total and balance. | test services-commerce:modules/orders/tests/integration/services/persistence/orders.queries.integration.spec.js#lists every order of the tenant newest placed first, and none of another tenant’s |
| 2 | listOrders | Enter a fragment of the customer’s name. | CAP-COM-ORD-010 | Name matching finds the customer’s purchases regardless of case. | test services-commerce:modules/orders/tests/integration/services/persistence/orders.queries.integration.spec.js#finds an order by part of its buyer’s name in any case |
| 3 | listOrders | Apply the Unpaid view and the preceding week’s date range. | CAP-COM-ORD-010 | Results include owing or unbilled purchases within the dates and exclude voided ones. | test services-commerce:modules/orders/tests/integration/services/persistence/orders.queries.integration.spec.js#filters the unpaid orders: owing or not yet billed, never a voided one |
| 4 | /console/{tenantId}/orders/{orderId} | Follow the order number into its detail view. | CAP-COM-ORD-010 | The money panel presents the supplied Accounting position and a link to the associated invoice. | test react-console:components/console/order/__tests__/order-360-live-cards.test.tsx#shows the totals with the promotion's name, the money, and the invoice as a link to Accounting |
| Path | From step | Condition | Path taken | Outcome | Provenance |
|---|---|---|---|---|---|
| alternate | 2 | The manager knows the order number | Search the number with or without its display prefix | The matching purchase appears | test services-commerce:modules/orders/tests/integration/services/persistence/orders.queries.integration.spec.js#finds an order by its display number with or without the ORD- prefix |
| failure | 1 | The caller lacks permission to read orders | Refuse the order-list request | The request does not disclose order data | test services-commerce:modules/checkout/tests/e2e/checkout-security.e2e.spec.js#refuses a caller without commerce.orders.read the list, 403 permission_missing |
| Id | Statement | Provenance |
|---|---|---|
01 | Pagination presents the purchases in newest-first order without omissions or duplicate rows. | test services-commerce:modules/orders/tests/integration/services/persistence/orders.queries.integration.spec.js#pages with a limit and says whether another page follows |
02 | Search supports the display number and case-insensitive customer-name fragments. | test services-commerce:modules/orders/tests/integration/services/persistence/orders.queries.integration.spec.js#finds an order by part of its buyer’s name in any case |
03 | The balance displayed in the table is the balance provided in its order data. | test react-console:components/commerce/orders/__tests__/orders-list-screen.test.tsx#shows the number, the customer, the status, the total and the balance due |
End-to-end policy: required: A browser journey must connect the live list, filters and detail view after refresh to prove staff can find an existing purchase again.