A commerce lifecycle, told through one customer.

Experience. Emma controls profile data, saved addresses, order-history entry points, and loyalty tier visibility from one account surface.

Rules. Customer owns profile data; order details keep immutable snapshots; checkout only changes defaults when Emma opts in.

Proof. Customer profile, loyalty, order-history ownership, and order-address snapshot scenarios cover the behavior.

Experience. Published products appear in the storefront with commercial facts, variants, media, reviews, campaign visibility, and category navigation.

Rules. Archived products leave normal discovery, discontinued products cannot be newly ordered, and promotion pricing only appears when active and applicable.

Proof. Product lifecycle, campaign pricing, category browsing, and storefront product journey tests cover the path.

Experience. Emma narrows a large catalog with text search, category levels 1 to 3, brand filters, typed attributes, numeric bounds, and reload-safe URL state.

Rules. Catalog remains the source of truth; Elasticsearch is the read model; backend computes facets, counts, pagination, and category-aware filter semantics.

Proof. Search BDD covers relevance, zero results, configurable facets, publish indexing, stale-document removal, and category-aware facet counts.

Experience. Emma compares products, chooses variants, checks trust signals, and sees the best applicable customer value before adding to cart.

Rules. Variant products require a variant, variant prices stay within bounds, bundles need real value, and high discounts require approval.

Proof. Variant lifecycle, comparison, campaign approval, and best-customer-value scenarios protect the behavior.

Experience. Checkout reuses saved addresses, validates the cart, applies customer rewards, and shows the accepted commercial summary before order placement.

Rules. Delivery and billing selections are mandatory; cart pricing is the single quote source; checkout snapshots commercial, address, and reward facts.

Proof. Address-book checkout, cart validation, commercial snapshot, and reward snapshot scenarios cover the flow.

Experience. Emma sees stable order history while operations receive the fulfillment facts required to progress delivery.

Rules. Accepted sale price, address, variant, cost, margin, and reward snapshots do not mutate after checkout.

Proof. Order snapshot, variant-line, profitability, and logistics handoff scenarios keep the record immutable.

Experience. Operators receive shipment work from paid orders, pick items, deliver shipments, and publish order-state changes.

Rules. Logistics stores fulfillment facts without commercial totals; picked shipments cannot be cancelled from logistics.

Proof. Shipment lifecycle BDD covers intake, cancellation boundaries, picking, delivery, and emitted order-state events.

Experience. Managers create reward campaigns while customers receive eligible cart-visible rewards during checkout.

Rules. First-order rewards are single-use, paused campaigns are excluded, and profitability depends on delivered order margin snapshots.

Proof. First-order acquisition, loyalty reward, profitability, and segmentation scenarios cover the current slice.

Experience. Delivered orders unlock review submission, images, edit windows, moderation, and merchant replies.

Rules. Duplicate reviews are rejected; image count and resolution are constrained; merchant replies require approval first.

Proof. Review submission, image, editing, moderation, and merchant reply scenarios prove the behavior.

Experience. Customers and agents manage account-linked tickets, order disputes, customer-visible replies, internal notes, and template-assisted responses.

Rules. SLA risk includes unassigned open tickets, backend-derived warning/due/escalated states, internal notes stay private, and response templates cannot send unresolved placeholders.

Proof. Ticket management, communication, response-template, SLA management, and delivered-order dispute scenarios cover the support scope.

Experience. Stock owns availability authoritatively: the storefront reflects out-of-stock in real time over SSE, checkout holds units with a 15-minute reservation, and stock managers run a filterable availability dashboard.

Rules. availableToSell = onHand − reserved; a reservation cannot drive stock below zero; physical deduction happens at shipment, not order placement; availability reads are public and read-only.

Proof. Wave 1 delivered (24 acceptance criteria verified); stock management, reservation lifecycle, and backoffice dashboard scenarios cover it. Later waves (purchase orders, transfers, backorders, multi-warehouse) stay pending, not skipped.