Master-Sub Order Model Design for an E-commerce Platform
The article explains the master‑sub order model used in e‑commerce, defines master orders as collections of sub‑orders and sub‑orders as single‑SKU transactions, evaluates design options for goods, services, and fees, reviews the current “得物” single‑SKU system, and proposes a scalable multi‑sub‑order, multi‑master‑order architecture to support combined payments, multi‑warehouse fulfillment, and complex purchase scenarios.
This article analyzes the master‑sub order model commonly used in e‑commerce systems and explains how it is applied in the "得物" platform.
Definition of Master Order : A master order aggregates all user actions and flows for a specific logical dimension (e.g., all related SKUs). It is essentially a collection of one or more sub‑orders.
Definition of Sub Order : A sub‑order represents the actions and flow of a single SKU. It contains exactly one sellable item and any number of non‑sellable items (e.g., delivery fees).
The article discusses three possible design schemes for handling entity goods, customized services, and shipping fees, concluding that two sub‑orders best express the business logic.
Current "得物" transaction model features a single master order with one sub‑order per SKU, limited to one item per order, platform‑mediated logistics, and a single fulfillment warehouse.
Future trends include stronger platform involvement, the need for combined payments/cart, and multi‑warehouse fulfillment, which will require extending the existing model.
Finally, the article proposes a scalable abstraction where multiple sub‑orders aggregate into multiple master orders, supporting complex scenarios such as multi‑item purchases and multi‑warehouse logistics.
DeWu Technology
A platform for sharing and discussing tech knowledge, guiding you toward the cloud of technology.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.