Design and Architecture of Enterprise E‑Commerce Order Systems

Order System Role in Enterprises

Before building an order system, the overall business system boundaries must be clarified to define responsibilities and ensure efficient interaction between upstream and downstream systems.

Relationship with Other Business Systems

External systems (C‑end website, merchant back‑ends, channel integrations) serve customers; management back‑ends handle order, promotion, product, and content modules; public service systems provide shared capabilities such as product, inventory, and user services.

Upstream and Downstream Relationships

The order system receives user information, creates product orders, tracks order data, and connects to product, promotion, warehouse, membership, and payment systems.

Business Architecture

Key modules include:

Order Service : order list, order details, online placement, and multi‑dimensional order data services for public modules.

Order Logic : manages order creation, payment, production, confirmation, completion, cancellation, and complex rules for order status, amount calculation, and inventory.

Underlying Services : integrates public service modules to avoid scattered data across systems.

Core Functions

Order content stores product, discount, user, and payment information to enable precise management and interaction with downstream systems such as promotion, warehouse, and logistics.

The workflow engine abstracts the order lifecycle into forward and reverse processes. Forward flow includes order creation → payment → production → confirmation → completion. Reverse flow covers modification, cancellation, refund, and return.

Two inventory deduction strategies are discussed:

Deduct on order creation – user‑friendly but may cause stale orders.

Deduct on payment – reduces invalid orders but can lead to overselling due to payment latency.

State Machine

Manages order status using three elements: current state, action, and next state. Separate state machines are maintained for different order types and user perspectives, allowing fine‑grained control.

Future Development

As business scales, multiple order systems may coexist, leading to fragmented data and duplicated integration effort. A unified order center combined with business‑specific order modules can provide consistent data, simplify maintenance, and support diverse order types.

Ultimately, the order system design should align with market, company, and business needs to create a balanced solution rather than a one‑size‑fits‑all approach.