Design and Core Functions of an E‑commerce Order System

Overview

The article introduces the role of an order system in a traditional e‑commerce enterprise, outlines its main functional modules, and discusses future development considerations.

1. Role of the Order System in the Enterprise

Before building an order system, it is essential to map the relationships among all business systems and define the upstream and downstream boundaries of the order system to clarify its responsibilities and functions.

2. Relationship Between the Order System and Other Business Systems

The order system interacts with three layers of external systems: (1) outward‑facing systems such as the public website, C‑end user apps, merchant back‑ends, and partner channels; (2) management middle‑back‑ends like promotion, product, and content systems; (3) shared service systems that provide common infrastructure for other applications.

3. Upstream and Downstream Relationships

Upstream, the order system receives user information and transforms it into product orders while tracking order data. Downstream, it connects to product, promotion, warehousing, membership, and payment systems, acting as a bridge between the front‑end commerce layer and internal services.

4. Business Architecture of the Order System

Order Service : Provides user‑facing features such as order list, order details, and online ordering, as well as multidimensional order data services for shared modules.

Order Logic : Core module that manages order creation, payment, production, confirmation, completion, cancellation, and related rules for status, pricing, and inventory.

Underlying Services : Integrates public service modules (e.g., product, code, database, APIs) to avoid scattered data retrieval and reduce maintenance overhead.

Core Functions of the Order System

1. Order Content Information

The system stores real‑time data about products, discounts, users, and payments to enable precise management and interaction with downstream systems such as promotion, warehousing, and logistics.

2. Process Engine

The process engine abstracts the end‑to‑end order flow into standard forward and reverse processes. Forward processes typically follow five steps: order creation → payment → production → confirmation → completion. Inventory deduction can occur either at order creation or after payment, each with its own advantages, disadvantages, and mitigation strategies.

Reverse processes handle order modification, cancellation, refund, and return, each requiring coordination with promotion, payment, and inventory services.

3. State Machine

The state machine defines the current state, actions, and next state for each order transition. It supports multiple state maps for different user roles (system, merchant, buyer) and multiple state machines for various order types, enhancing granularity and reliability.

Future Development of Order Systems

As businesses grow, multiple specialized order systems may coexist, leading to fragmented order data and duplicated integration effort. The article suggests consolidating into an Order Center that provides unified services to all business‑specific order systems, reducing maintenance overhead and improving consistency.

Conclusion

Building an order system should balance comprehensiveness with practicality, aligning with market demands, company strategy, and business realities to create a scalable and maintainable solution.