Design and Core Functions of an E‑commerce Order System

The article describes the role an order system should play in traditional e‑commerce enterprises, outlines the design ideas for its main functional modules, and offers thoughts on the system's future development.

1. Role of the Order System in the Enterprise

Before building an order system, it is essential to map the relationships among overall business systems and the upstream/downstream connections of the order system; clear boundaries determine responsibilities and functions, ensuring efficient collaboration.

2. Relationship Between the Order System and Other Business Systems

(1) External systems: Front‑end platforms such as the website, C‑end user app, merchant backend, and channel integrations (e.g., bank credit‑card or WeChat collaborations) that directly face customers.

(2) Management middle‑office: Modules like the order system, promotion system, product system, and content system that manage internal business processes.

(3) Public service systems: Shared services that provide foundational capabilities to other applications, improving architectural rationality and service efficiency.

3. Upstream and Downstream Relationships

The order system receives user information, transforms it into product orders, tracks order data, and connects upward to user‑facing channels while linking downward to product, promotion, warehousing, membership, and payment systems.

4. Business Architecture of the Order System

(1) Order Service: Provides user‑facing features such as order list, details, and online placement, as well as multidimensional order data for public modules.

(2) Order Logic: Core of the system, handling creation, payment, production, confirmation, completion, cancellation, complex status rules, amount calculations, and inventory adjustments.

(3) Underlying Services: Modular public services (e.g., product system) that the order system calls to avoid scattered data retrieval and high maintenance costs.

Core Functions of the Order System

1. Content Stored in an Order

Orders store 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 entire order lifecycle from creation to completion, supporting both forward (purchase) and reverse (modification, cancellation, refund, return) flows, each triggered by system or manual actions.

Forward Flow

Typical B2C order flow: Order Creation → Payment → Production → Confirmation → Completion.

During order creation, the system gathers product information, applicable discounts, member benefits, and applies inventory deduction rules (order‑time or payment‑time deduction) with their respective advantages, disadvantages, and mitigation strategies.

Reverse Flow

Reverse processes include order modification, cancellation, refund, and return, each requiring clear interaction with inventory, promotion, and payment subsystems.

3. State Machine

A state machine manages order status transitions using three elements: current state, action, and next state. Different user perspectives (system, merchant, buyer) may have distinct status sets, and multiple state‑machine definitions are often maintained to support various order types.

Future Development of the Order System

As business volume and forms evolve, enterprises may operate multiple order systems for different scenarios, leading to fragmentation of order data, duplicated interfaces, and increased maintenance effort. A recommended direction is to split the architecture into a unified Order Center and specialized business order systems, providing a single source of truth and shared services.

Conclusion

Building an enterprise order system should balance breadth and depth, aligning with market, company, and business realities to devise a suitable design and iteration plan that harmonizes with overall corporate development.