# Confirm completed order

**Flow key:** `order-confirmation`

## Outcome

The shopper receives one durable, accessible confirmation that matches the committed order, payment, fulfillment, and notification state.

## Actors

- Shopper
- Order service
- Payment/fulfillment systems
- Email/SMS notification provider

## Preconditions and entry points

- A synthetic order can be completed.
- Order lookup and outbound message evidence are available.

## Required test data

Use synthetic, isolated, resettable data. Never use real credentials, payment instruments, private customer records, or production notifications.

| Data | Canonical valid seed | Critical variations |
|---|---|---|
| Order | one paid physical test order | digital, zero-total, split shipment, pending payment |
| Customer | `carbon.order+001@example.test` | guest, signed in, translated locale |
| Totals | known subtotal/discount/tax/shipping/total | rounding, multi-currency display |
| Notification | email receipt enabled | disabled preference, delayed, bounced, duplicate |
| Browser state | normal checkout tab | response lost, refresh, back, copied confirmation URL |

## Canonical steps

Treat this as the ordinary successful path inferred from common product behavior. Adapt it to observed labels, business rules, APIs, and implementation evidence; do not invent a requirement.

| Step | User or system action | Expected evidence |
|---:|---|---|
| 1 | Complete checkout. | One order identifier and committed result are returned. |
| 2 | Render confirmation. | Order number, items, totals, addresses, payment state, fulfillment, and next actions match persistence. |
| 3 | Refresh, back/forward, and reopen the confirmation. | No duplicate order/payment is created and unauthorized viewers cannot access it. |
| 4 | Open order history or guest lookup. | The same order and lifecycle state are retrievable. |
| 5 | Inspect receipt/notification. | Content, locale, links, permitted PII, and totals agree with the order. |
| 6 | Inspect analytics, audit, and fulfillment event. | Each records one order and the correct correlation identity. |

## Alternate paths

- Guest confirmation
- Signed-in confirmation
- Pending/manual payment
- Digital delivery
- Multiple shipments

## Failure and recovery paths

- Order commits but page fails
- Notification duplicates or fails
- Confirmation URL leaks another order
- Payment/order state diverges
- Refresh repeats conversion analytics

## Completion oracle

- The stated outcome is true in visible UI and authoritative persisted state.
- Exactly one intended business result and no unintended side effect occurred.
- Identity, tenant, authorization, money/data, lifecycle, notifications, integrations, analytics, and audit agree where applicable.
- Refresh, retry, back/forward, and a second authorized read do not reveal a contradictory result.
- Any partial, delayed, canceled, failed, or unknown outcome is labeled truthfully and has a safe recovery path.

## Evidence to capture

- Entry context, actor, tenant, role, feature flags, locale, time zone, and initial identifiers/state.
- Step-level screenshots or DOM state plus request/response, correlation, job, event, and stable business IDs where available.
- Before/after authoritative records, versions, totals, permissions, lifecycle states, and downstream side effects.
- Notifications, audit events, integration deliveries, retries, deduplication, latency, and recovery evidence.
- Untested branches, unsafe-to-run cases, product decisions, and evidence tier.

## Product decisions to resolve

- Exact eligibility, required data, authorization, and validation rules.
- Which steps are synchronous, asynchronous, optional, skippable, reversible, or irreversible.
- Idempotency, concurrency, timeout, retry, cancellation, and compensation semantics.
- Retention, privacy, notification, audit, performance, accessibility, and localization commitments.

## Related CARBON items

- [invoice](../../items/records/invoice.md)
- [email and outbound message](../../items/content/email-and-outbound-message.md)
- [detail](../../items/views/detail.md)
- [observability and auditability](../../items/quality/observability-and-auditability.md)

[Back to Commerce and billing flows](index.md)
