PlaygroundE-commerce

BrightBox Commerce

Fictional companyE-commerce

A direct-to-consumer retailer running its own catalog, inventory, and fulfillment from order placement through delivery confirmation.

Modeled on

  • GS1: GTIN for trade items, GLN for locations, SSCC for shipping units.
  • EDI X12: The order-to-cash triple: 850 purchase order, 856 advance ship notice, 810 invoice.
  • schema.org: Order, OrderStatus, and Offer shapes for the storefront.

The genome map

Roles in their reporting line, the process step by step with the role on each step, the rules on the steps they govern, and the resources the work acts on. Select a role to see what it reaches.

Roles Select a role to see its reach.

Order Fulfillment Operated by Operations Director

Placement through delivery confirmation, across catalog, inventory, and fulfillment.

  1. 1 Receive order Order ManagerOrder.Receive
  2. 2 Verify payment Order ManagerOrder.VerifyPayment
  3. 3 Reserve inventory Warehouse LeadInventoryItem.Reserve
    • Payment clears before stock moves
  4. 4 Pick & pack Warehouse LeadShipment.Pack
  5. 5 Dispatch shipment Warehouse LeadShipment.Dispatch
    • Only warehouse dispatches
  6. 6 Confirm delivery Customer Support LeadOrder.Confirm

Resources

  • Order
  • Catalog Product
  • Inventory Item
  • Shipment
  • Return

Rules on no step They govern operations outside the process.

  • Returns are supports to approve
  • Catalog goes live through merchandising

Three questions this genome answers

Each answer comes from the compiled genome alone. Pick another subject and the answer changes in place.

Operations Director, Customer Support Lead may perform Return.Authorize. The rule: Returns are supports to approve.

These steps wait for Warehouse Lead:

  • Reserve inventory Order Fulfillment
  • Pick & pack Order Fulfillment
  • Dispatch shipment Order Fulfillment

Order Manager, Customer Support Lead act on Order, by a process step or under an access rule.

Every artifact from one genome

The same derivations and renderers the Playground runs, here for BrightBox Commerce at build time. Open it in the Playground to pick your own set.

Operations

How the work actually runs — who owns what, in what order, under which rules.

Process flow

The end-to-end sequence, each step with its owner.

Placement through delivery confirmation, across catalog, inventory, and fulfillment.

  1. 1
    Receive order
    Ingest the order, validate line items, and confirm the SKUs are sellable.
    Order ManagerOrder.Receive
  2. 2
    Verify payment
    Confirm authorization; hold or decline anything the processor flags.
    Order ManagerOrder.VerifyPayment
  3. 3
    Reserve inventory
    Hold stock at the fulfilling location and trigger replenishment if it goes short.
    Warehouse LeadInventoryItem.Reserve
  4. 4
    Pick & pack
    Retrieve the items, verify quantities, and package for the carrier.
    Warehouse LeadShipment.Pack
  5. 5
    Dispatch shipment
    Generate the label, hand off to the carrier, and publish tracking to the order.
    Warehouse LeadShipment.Dispatch
  6. 6
    Confirm delivery
    Verify carrier confirmation, close the order, and open the post-purchase follow-up.
    Customer Support LeadOrder.Confirm

Owned end to end by Operations Director.

SOP / runbook

The same process as a numbered operating procedure.

PurposePlacement through delivery confirmation, across catalog, inventory, and fulfillment.
OwnerOperations Director
TriggerA customer completes checkout.
  1. 1. Receive order
    Ingest the order, validate line items, and confirm the SKUs are sellable.
    Performed by Order Manager
  2. 2. Verify payment
    Confirm authorization; hold or decline anything the processor flags.
    Performed by Order Manager
  3. 3. Reserve inventory
    Hold stock at the fulfilling location and trigger replenishment if it goes short.
    Performed by Warehouse Lead
  4. 4. Pick & pack
    Retrieve the items, verify quantities, and package for the carrier.
    Performed by Warehouse Lead
  5. 5. Dispatch shipment
    Generate the label, hand off to the carrier, and publish tracking to the order.
    Performed by Warehouse Lead
  6. 6. Confirm delivery
    Verify carrier confirmation, close the order, and open the post-purchase follow-up.
    Performed by Customer Support Lead

Key positions

The roles this operation needs and who reports to whom.

Fulfillment Team

  • Operations Director
    Owns end-to-end fulfillment performance, carrier relationships, and SLA commitments.
    • Order Manager
      Processes incoming orders, validates payments, and sets warehouse priority.
      Receive orderVerify payment
    • Warehouse Lead
      Directs pick-and-pack, owns inventory accuracy, and oversees outbound shipments.
      Reserve inventoryPick & packDispatch shipment
    • Customer Support Lead
      Handles delivery inquiries, manages returns, and resolves post-shipment exceptions.
      Confirm delivery
    • Merchandising Manager
      Owns the catalog — what is listed, how it is priced, and when it goes live.

Each chip is a step of the process that role owns.

RACI matrix

Every step against every role — responsible, accountable, consulted.

StepOperations DirectorOrder ManagerWarehouse LeadCustomer Support LeadMerchandising Manager
Receive orderAR
Verify paymentARC
Reserve inventoryARC
Pick & packAR
Dispatch shipmentACR
Confirm deliveryAR

R responsible · A accountable · C consulted — derived from step owners, the process operator, and access rules.

Policies & rules

The constraints that govern each operation, stated as rules.

  • Payment clears before stock moves condition

    No stock is reserved until payment authorization has cleared.

    InventoryItem.Reserve
  • Only warehouse dispatches access

    Dispatch is the warehouse’s call. Support can ask; it cannot ship.

    Shipment.Dispatch Warehouse LeadOperations Director
  • Returns are supports to approve access

    Only support authorizes returns, so refund exposure has one owner.

    Return.Authorize Customer Support LeadOperations Director
  • Catalog goes live through merchandising access

    Nothing reaches the storefront without merchandising publishing it.

    CatalogProduct.Publish Merchandising Manager

Product

What gets built on top of it — the data, the screens, the API.

Data model

The entities, their fields, and how they relate.

Order ReceiveVerifyPaymentConfirm

A customer purchase, from placement through delivery confirmation.

  • orderNumber string required
  • placedAt datetime required
  • total number required
  • status enum required placed · paid · picking · shipped · delivered · cancelled
Catalog Product Publish

A sellable product with its merchandising copy, pricing, and variants.

  • gtin string required
  • sku string required
  • title string required
  • price number required
  • published boolean
Inventory Item Reserve

Stock of one SKU at one location, with the quantity currently reservable.

  • gtin string required
  • gln string required
  • onHand number required
  • reserved number
Shipment PackDispatch

A packed parcel handed to a carrier against one or more order lines.

  • sscc string
  • trackingNumber string
  • carrier enum UPS · FedEx · USPS · DHL
  • dispatchedAt datetime
Return Authorize

A customer-initiated return against a delivered order.

  • reason enum damaged · wrong-item · no-longer-wanted · late
  • receivedAt datetime
  • refundAmount number

Screen map

Every route and the page it resolves to.

Shell: AdminShell

/orders
Order Queue 🔒
Operator order queue.
Order tablesummary
/orders/:id
Order Detail 🔒
Single order.
Order formactions
/inventory
Inventory Board 🔒
Stock positions.
Inventory Item table
/catalog
Catalog Editor 🔒
Catalog management.
Catalog Product actions

Example UI

A working admin table and detail form, built from the fields.

Order Queue VerifyPaymentConfirm
OrderCustomerPlacedStatusTotal
BB-10482A. Okafor2026-08-14 09:12shipped128.4
BB-10483M. Lindqvist2026-08-14 09:26picking64
BB-10484R. Patel2026-08-14 10:03paid219.95
BB-10485J. Moreau2026-08-14 10:41placed42.5
Order detail

API surface

The endpoints, grouped by namespace, with their operations.

Commerce/api/commerce

Order, catalog, inventory, and shipment operations.

  • GET /api/commerce/orders Order.List The operator order queue.
  • GET /api/commerce/orders/{id} Order.Read One order in full.
  • POST /api/commerce/orders/{id}/verify-payment Order.VerifyPayment Confirm authorization for an order.
  • GET /api/commerce/inventory InventoryItem.List Stock by location.
  • POST /api/commerce/inventory/reserve InventoryItem.Reserve Hold stock against a paid order.
  • POST /api/commerce/shipments/{id}/dispatch Shipment.Dispatch Hand a packed parcel to the carrier.
  • GET /api/commerce/shipments/{id} Shipment.Track Carrier tracking state.
  • POST /api/commerce/catalog/{id}/publish CatalogProduct.Publish Publish a product to the storefront.

Technology

Where it runs and who can reach it.

Architecture diagram

The cells this runs on and what talks to what.

Storefront
nextjs 15
Customer-facing catalog and checkout.
BrightBoxCommerce.Product.Web
OrderService
nestjs 10
Order lifecycle and payment verification.
BrightBoxCommerce.Product.Api
InventoryService
nestjs 10
Stock positions and reservations.
BrightBoxCommerce.Product.Api
FulfillmentWorker
express 4
Runs the pick, pack, and dispatch steps against carrier APIs.
BrightBoxCommerce.Operational
CommerceDb
postgres 16
Orders, catalog, inventory, shipments.
BrightBoxCommerce.Product.Core
  • Storefront → OrderService checkout
  • OrderService → InventoryService reserve
  • OrderService → FulfillmentWorker order.paid
  • FulfillmentWorker → InventoryService decrement
  • OrderService → CommerceDb depends-on
  • InventoryService → CommerceDb depends-on

Environment topology

Dev, staging, and production, with the providers behind each.

dev
Local and preview builds.
Providers
VercelcloudNeondatabase
Cells
none
staging
Carrier sandbox and test payments.
Providers
VercelcloudNeondatabaseStripepayments
Cells
none
prod
Live storefront.
Providers
VercelcloudNeondatabaseStripepaymentsAuth0auth
Cells
StorefrontOrderServiceInventoryServiceFulfillmentWorkerCommerceDb

Access-control matrix

Which role may perform which operation, derived not declared.

OperationOperations DirectorOrder ManagerWarehouse LeadCustomer Support LeadMerchandising Manager
Shipment.DispatchOnly warehouse dispatches✓✓
CatalogProduct.PublishCatalog goes live through merchandising✓
Return.AuthorizeReturns are supports to approve✓✓
No access rule governs
Order.ReceiveOrder.VerifyPaymentOrder.ConfirmOrder.ListOrder.ReadInventoryItem.ReserveInventoryItem.ListShipment.PackShipment.Track

Derived, not declared — this is the list an audit asks about.

Make yours

Start from BrightBox Commerce and change what differs, or pick another company as your template. Three ways in:

  1. 1. Download the template

    The compiled genome as JSON: every role, step, rule, resource, screen and system on this page.

    Download BrightBox Commerce as JSON
  2. 2. Start an agent from it

    Paste this into an agent that has the DNA MCP server connected. It drafts your model in the conversation and saves only when you ask.

    Use the DNA MCP server (https://agents.dna.codes) to help me model how my company works.
    Start from the BrightBox Commerce genome at https://dna.codes/genome/ecommerce.json. It is an example company, not mine.
    Read its roles, process steps, rules and resources, then ask me how my company differs.
    Draft my company's operating model in this conversation, as structure/v1 and behaviour/v1 documents, and use `validate` on each draft.
    Do not save anything: call `apply` only when I ask you to save.
  3. 3. Join the waitlist

    The hosted product runs your model for your team and your agents.

Which of these sounds like you? Pick as many as apply.

The most useful box on this page. Rough is fine, and “nowhere, honestly” is a real answer and a common one.

We reply by hand, usually within a day. No sequence, no drip, no spam.