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 Receive order
- 2 Verify payment
- 3 Reserve inventory
- Payment clears before stock moves
- 4 Pick & pack
- 5 Dispatch shipment
- Only warehouse dispatches
- 6 Confirm delivery
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.
- 1Receive orderIngest the order, validate line items, and confirm the SKUs are sellable.
- 2Verify paymentConfirm authorization; hold or decline anything the processor flags.
- 3Reserve inventoryHold stock at the fulfilling location and trigger replenishment if it goes short.
- 4Pick & packRetrieve the items, verify quantities, and package for the carrier.
- 5Dispatch shipmentGenerate the label, hand off to the carrier, and publish tracking to the order.
- 6Confirm deliveryVerify carrier confirmation, close the order, and open the post-purchase follow-up.
Owned end to end by Operations Director.
SOP / runbook
The same process as a numbered operating procedure.
- 1. Receive orderIngest the order, validate line items, and confirm the SKUs are sellable.Performed by Order Manager
- 2. Verify paymentConfirm authorization; hold or decline anything the processor flags.Performed by Order Manager
- 3. Reserve inventoryHold stock at the fulfilling location and trigger replenishment if it goes short.Performed by Warehouse Lead
- 4. Pick & packRetrieve the items, verify quantities, and package for the carrier.Performed by Warehouse Lead
- 5. Dispatch shipmentGenerate the label, hand off to the carrier, and publish tracking to the order.Performed by Warehouse Lead
- 6. Confirm deliveryVerify 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 DirectorOwns end-to-end fulfillment performance, carrier relationships, and SLA commitments.
- Order ManagerProcesses incoming orders, validates payments, and sets warehouse priority.Receive orderVerify payment
- Warehouse LeadDirects pick-and-pack, owns inventory accuracy, and oversees outbound shipments.Reserve inventoryPick & packDispatch shipment
- Customer Support LeadHandles delivery inquiries, manages returns, and resolves post-shipment exceptions.Confirm delivery
- Merchandising ManagerOwns 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.
| Step | Operations Director | Order Manager | Warehouse Lead | Customer Support Lead | Merchandising Manager |
|---|---|---|---|---|---|
| Receive order | A | R | |||
| Verify payment | A | R | C | ||
| Reserve inventory | A | R | C | ||
| Pick & pack | A | R | |||
| Dispatch shipment | A | C | R | ||
| Confirm delivery | A | R |
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.
- Only warehouse dispatches access
Dispatch is the warehouse’s call. Support can ask; it cannot ship.
- Returns are supports to approve access
Only support authorizes returns, so refund exposure has one owner.
- Catalog goes live through merchandising access
Nothing reaches the storefront without merchandising publishing it.
Product
What gets built on top of it — the data, the screens, the API.
Data model
The entities, their fields, and how they relate.
ReceiveVerifyPaymentConfirmA 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
PublishA sellable product with its merchandising copy, pricing, and variants.
- gtin string required
- sku string required
- title string required
- price number required
- published boolean
ReserveStock of one SKU at one location, with the quantity currently reservable.
- gtin string required
- gln string required
- onHand number required
- reserved number
PackDispatchA packed parcel handed to a carrier against one or more order lines.
- sscc string
- trackingNumber string
- carrier enum UPS · FedEx · USPS · DHL
- dispatchedAt datetime
AuthorizeA 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/orders/:id/inventory/catalogExample UI
A working admin table and detail form, built from the fields.
| Order | Customer | Placed | Status | Total |
|---|---|---|---|---|
| BB-10482 | A. Okafor | 2026-08-14 09:12 | shipped | 128.4 |
| BB-10483 | M. Lindqvist | 2026-08-14 09:26 | picking | 64 |
| BB-10484 | R. Patel | 2026-08-14 10:03 | paid | 219.95 |
| BB-10485 | J. Moreau | 2026-08-14 10:41 | placed | 42.5 |
API surface
The endpoints, grouped by namespace, with their operations.
/api/commerceOrder, catalog, inventory, and shipment operations.
- GET
/api/commerce/ordersOrder.List The operator order queue. - GET
/api/commerce/orders/{id}Order.Read One order in full. - POST
/api/commerce/orders/{id}/verify-paymentOrder.VerifyPayment Confirm authorization for an order. - GET
/api/commerce/inventoryInventoryItem.List Stock by location. - POST
/api/commerce/inventory/reserveInventoryItem.Reserve Hold stock against a paid order. - POST
/api/commerce/shipments/{id}/dispatchShipment.Dispatch Hand a packed parcel to the carrier. - GET
/api/commerce/shipments/{id}Shipment.Track Carrier tracking state. - POST
/api/commerce/catalog/{id}/publishCatalogProduct.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.
BrightBoxCommerce.Product.WebBrightBoxCommerce.Product.ApiBrightBoxCommerce.Product.ApiBrightBoxCommerce.OperationalBrightBoxCommerce.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.
Access-control matrix
Which role may perform which operation, derived not declared.
| Operation | Operations Director | Order Manager | Warehouse Lead | Customer Support Lead | Merchandising Manager |
|---|---|---|---|---|---|
Shipment.DispatchOnly warehouse dispatches | ✓ | ✓ | |||
CatalogProduct.PublishCatalog goes live through merchandising | ✓ | ||||
Return.AuthorizeReturns are supports to approve | ✓ | ✓ |
Order.ReceiveOrder.VerifyPaymentOrder.ConfirmOrder.ListOrder.ReadInventoryItem.ReserveInventoryItem.ListShipment.PackShipment.TrackDerived, 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. Download the template
The compiled genome as JSON: every role, step, rule, resource, screen and system on this page.
Download BrightBox Commerce as JSON2. 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. Join the waitlist
The hosted product runs your model for your team and your agents.