Locate orders and understand their progress

Purpose

Staff find previous sales and explain their lines, payment progress and outstanding balance. Lists and detail views serve different parts of that investigation.

How It Works

A reader opens Orders and narrows the list using the customer or sale details they know. The result supplies enough financial context to choose an order for inspection. Opening the number leads to Order 360, where lines and transaction links provide the fuller account. The reader can distinguish an unavailable money summary from a reported zero balance. Reconciliation exceptions identify gaps between the sale and Accounting’s position. Customer-specific lists serve a narrower scope than workspace search.

Relationships

Placement establishes the order, billing and payment connect its money, and record protection constrains which reader can inspect it.

Show evidence (sources, provenance, origins, pinned commits)

The Formal Contract

The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.

Outcomes: Staff can identify a customer’s order without its number.Displayed money reflects the latest Accounting position held by the order.
Surfaces: consoleapijob
Intent sources: services-commerce:docs/milestones/plans/COMM-M2-plan.md#D1services-commerce:docs/milestones/plans/COMM-M2-plan.md#2. Scope

Controls

32 controls apply, from the corpus control catalogue.

TC-IAM-006 TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-AZ-006 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-TEN-004 TC-CRY-001 TC-DAT-001 TC-DAT-002 TC-DAT-003 TC-DAT-004 TC-DAT-005 TC-LOG-001 TC-LOG-002 TC-LOG-003 TC-LOG-004 TC-LOG-005 TC-AVL-004 TC-MON-001 TC-MON-002 TC-MON-004 TC-PI-001 TC-PI-002 TC-PI-003 TC-PI-004 TC-PI-005 TC-PRV-001 TC-PRV-002

Permissions

Key	Checked at	Scope
`commerce.orders.read`	api	tenant
`commerce.orders.read`	console	tenant

Business Rules

10 rules, 8 to be proved before approval. A rule's product intent is derived from its origin: 10 confirmed by a product decision, the rest inheriting this capability's confirmed.

Id	Rule	Kind	Enforced at	Provenance
`01`must prove Confirmed	The workspace list returns orders in descending placement order with buyer names from CRM when available, default pages of fifty, a maximum of two hundred and a continuation cursor. origin: services-commerce:docs/milestones/plans/COMM-M2-plan.md#D1 no proof recorded yet	policy	api, service	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
`02`must prove Confirmed	Literal case-insensitive search matches displayed or partial order numbers and buyer names, with search text limited to one hundred characters. origin: services-commerce:docs/milestones/plans/COMM-M2-plan.md#D1 no proof recorded yet	policy	api, service	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`must prove Confirmed	Status, payment, kind and inclusive placement dates filter together, with paid based on an invoiced zero balance and unpaid excluding voided and cancelled orders. origin: services-commerce:docs/milestones/plans/COMM-M2-plan.md#D1 no proof recorded yet	policy	api, service	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
`04`must prove Confirmed	Buyer lists require both buyer kind and identifier and allow only kind and policy narrowing; incompatible workspace filters are refused, and portal callers can list their own buyer scope only. origin: services-commerce:docs/milestones/plans/COMM-M2-plan.md#D1 no proof recorded yet	validation	api, service	test services-commerce:modules/orders/tests/unit/orders/orders-list-query.spec.js#refuses a search beside a buyer
`05`must prove Confirmed	Reading an order returns its lines and frozen purchases, price explanations, sequenced payment attempts, invoices, delivery obligations and events. no proof recorded yet	policy	service	test services-commerce:modules/orders/tests/integration/services/persistence/orders.queries.integration.spec.js#answers the order whole: every column mapped, the system properties, the mirror absent until derived
`06`must prove Confirmed	The order mirrors Accounting’s invoiced, paid, credited and balance figures after payments and acceptance and during sweeps, while raising reconciliation exceptions without suppressing the available figures. origin: services-commerce:docs/milestones/plans/COMM-M2-plan.md#2. Scope no proof recorded yet	calculation	service	test services-commerce:modules/orders/tests/integration/services/mirror/refresh-money-mirror.integration.spec.js#raises accepted_without_invoice_line on the billed line the view lacks, one open row counting both findings, and still writes the mirror it could derive
`07`must prove Confirmed	The Orders table displays order number, customer, placement date, status, total and balance, links to detail, handles voided balances and foreign currencies, explains missing names and requires order-read authority. origin: services-commerce:docs/milestones/plans/COMM-M2-plan.md#D1 no proof recorded yet	policy	console	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
`08`must prove Confirmed	Order 360 presents promotion names, money and invoice links, line discounts, tax and delivery errors, payment-attempt states and a message when Accounting has not yet supplied money figures. origin: services-commerce:docs/milestones/plans/COMM-M2-plan.md#2. Scope no proof recorded yet	policy	console	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
`09` Confirmed	The workspace order-detail page uses the order’s buyer when opened without a contact in the route.	policy	console	observed react-console:app/(console)/console/[tenantId]/orders/[orderId]/page.tsx:OrderPage
`10` Confirmed	Order records, events and after-sale documents are available as datasets for workspace queries and exports.	policy	service	observed services-commerce:modules/orders/export/orders.dataset.ts

Scenarios

Id	Given	When	Then	Provenance
`01`	Pat asks about an order from last Tuesday but cannot give its number.	Staff use a partial surname search and the placement date.	The result provides the matching order and balance with a link to its detail.	documented services-commerce:docs/milestones/plans/COMM-M2-plan.md#D1

Edge Cases

Id	Given	When	Then	Provenance
`02`	An accepted sale is cancelled and its refunded balance reaches zero.	A manager applies the Paid filter.	The recorded list behavior includes it based on money rather than cancellation status.	documented services-commerce:docs/milestones/plans/COMM-M2-W1-report.md#Things to know / for Andrew

Planning

Locate orders and understand their progress ​

Purpose ​

How It Works ​

Relationships ​