Design and Core Functions of an E‑commerce Order System

Overview

This article discusses the role of an order system in traditional e‑commerce enterprises, outlines its main functional modules, and reflects on future development directions.

1. Role of the Order System in the Enterprise

Before building an order system, it is essential to map the relationships between overall business systems and the upstream/downstream of the order system, define its responsibilities, and ensure efficient collaboration among systems.

2. Relationship between the Order System and Other Business Systems

(1) External Systems: Front‑end platforms such as the public website, C‑end user apps, merchant back‑ends, and channel integrations (e.g., bank credit‑card or WeChat) that directly interact with customers.

(2) Management Back‑Office: Modules that manage orders, promotions, products, and content displayed on external systems.

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

3. Upstream and Downstream Relationships of the Order System

The order system receives user information, transforms it into product orders, tracks order data, and connects downstream to product, promotion, warehousing, membership, and payment systems, acting as a bridge between front‑end and back‑end.

4. Business Architecture of the Order System

(1) Order Service – User‑facing functionalities such as order list, order details, and online ordering, as well as multidimensional order data services for common modules.

(2) Order Logic – Core processes including order creation, payment, production, confirmation, completion, cancellation, and related rules for status, amount calculation, and inventory adjustments.

(3) Underlying Services – Integration of public service modules (product, code, database, APIs) to avoid scattered data retrieval and reduce maintenance costs.

Core Functions of the Order System

1. Information Contained 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 end‑to‑end flow of an order, supporting both forward (creation → payment → production → confirmation → completion) and reverse processes (modification, cancellation, refund, return).

(1) Forward Process

Typical B2C flow: order creation → order payment → order production → order confirmation → order completion.

Inventory deduction strategies:

Deduct on Order Creation : Reduces stock when the order is placed; advantages: friendly user experience, simple logic; disadvantages: risk of malicious orders and stock lock.

Deduct on Payment : Reduces stock after payment confirmation; advantages: avoids waste from unpaid orders; disadvantages: possible over‑selling due to payment latency.

Solutions include setting order expiration, purchase limits, and risk‑control mechanisms.

Order Payment

After payment, the system records payment details and may handle order splitting based on channels or SKU attributes.

Order Production

Describes the logistics from merchant to customer, including picking, packing, and handoff to courier services.

Order Confirmation

After delivery, the system prompts users for evaluation, marking the start of after‑sale service.

Order Completion

Occurs after a defined period post‑delivery, ending the order lifecycle.

(2) Reverse Process

Includes order modification, cancellation, refund, and return, each with specific business rules and interactions with promotion, inventory, and payment systems.

(3) State Machine

Manages order status using three elements: current state, action, and next state. A fine‑grained state model improves tracking precision and supports multiple state machines for different order types.

Future Development of the Order System

As businesses grow, multiple order systems may coexist, leading to fragmented order data and duplicated integration work. A unified order center combined with business‑specific order modules can provide a single source of truth and reduce maintenance overhead.

Conclusion

Building an enterprise order system should balance comprehensiveness and focus, aligning with market, company, and business realities to devise appropriate architecture and product iteration plans.