DEAP · ConceptPlanned
Understand the DEAP operating model
Learn how products, orders and explicit state transitions form the verified foundation of the DEAP domain.
- Audience
- Developer, Solution architect, Administrator
- Owner
- DEAP product architecture
- Last reviewed
- Jul 19, 2026
- Reading time
- 8 min
On this page
Current verified model
The shared DEAP domain currently defines products and orders. A product has a stable ID, SKU, name and minor-unit price. An order belongs to a customer and moves through an explicit lifecycle.
Finance, procurement, supply chain, manufacturing, workforce and continuous control are broader DEAP capabilities. Their documentation will expand as their domain contracts become available.
Order lifecycle
- 01DraftThe order can be validated and prepared before commitment.
- 02ConfirmedThe enterprise accepts the customer and operating commitment.
- 03ShippedFulfilment has handed the order into delivery.
- 04DeliveredThe order reaches its successful terminal state.
- 05CancelledThe order reaches an explicit cancelled terminal state.
Continue learning