Why Order Splitting Can Make or Break Your E‑Commerce Business
This article explains the essential purpose of order splitting in e‑commerce, outlines seven common splitting scenarios—from merchant and multi‑warehouse splits to logistics, inventory, and after‑sale cases—shows their impact on cost, fulfillment efficiency, and customer experience, and presents a three‑module system design to implement robust splitting logic.
1. The Essence of Order Splitting: Why Split Orders?
Core purpose: reduce cost and increase efficiency; failing to split leads to customer complaints, financial loss, and operational chaos.
2. Seven Common Splitting Scenarios
Scenario 1: Merchant Splitting
Trigger: order contains items from ≥ 2 merchants or promotion conflicts.
Fresh produce and cosmetics in the same box cause lipstick to melt.
Beijing warehouse stock allocated from Guangzhou incurs higher freight than the product price.
Cross‑border package exceeds customs limit, leading to a month‑long return delay.
Result: separate sub‑orders improve fulfillment efficiency by about 40 %.
Scenario 2: Multi‑Warehouse Splitting
Rule: when items reside in different warehouses, force a split; also split when a warehouse lacks sufficient stock.
JD self‑operated: appliances from central warehouse, books from regional warehouse.
SHEIN cross‑border: clothing from Guangzhou, accessories from Foshan.
Pitfalls: freight must be recalculated for each warehouse; front‑end should inform customers that the order ships from multiple locations.
Scenario 3: Product Attribute Splitting
Rule: differing product attributes (temperature, hazard) require separate packaging.
Fresh food vs. frozen meat → separate boxes.
IKEA: furniture via logistics, tableware via courier.
Guidelines: avoid double freight, display appropriate warnings.
Scenario 4: Logistics Optimization Splitting
Trigger: heavy or oversized items, cost difference between logistics tiers, or special freight spikes (e.g., promotions, holidays).
Cost formula: splitting benefit = combined freight – Σ(sub‑order freight) – extra packaging cost.
Example: 5.8 kg order (dog food + snacks) saves ¥15 after split.
Scenario 5: User Rights Splitting
Trigger: payment‑method conflicts, coupon/points limits, service restrictions.
Front‑end interaction: show conflict dialog recommending split orders, e.g., “Your selected payment method or coupon cannot be applied to some items; please split into two orders.”
Scenario 6: Inventory Rhythm Splitting
Trigger: some items are in stock while others are pre‑sale or require allocation.
Rule: generate independent sub‑orders for in‑stock items (delivery ≤ 24 h) and delayed items (delivery > 72 h).
Xiaomi Mall: phone ships immediately, custom case ships after 7 days.
Taobao clothing store: regular size ships now, embroidered custom size ships later.
Scenario 7: After‑sale Reverse Splitting
Trigger: partial returns or exchanges causing attribute conflicts.
Rule: recompute discounts for remaining items, create new sub‑orders for replacements, and handle logistics accordingly.
Example: user returns one item; system reallocates original coupon proportionally to the remaining sub‑order.
3. Core Splitting Process
4. System Design: Three Modules
1. Rule Engine
Evaluates configured rules (scenarios, inventory, user tags, promotions) to decide whether and how to split, and how to allocate freight and discounts.
2. User Interface
Displays split‑order details to customers, e.g., “Order split into 2 packages: Item A – Express, ¥10, arrives today; Items B + C – Free shipping, arrives tomorrow.”
3. After‑sale Coordination Center
Handles reverse splitting for returns/exchanges, traces original discount ratios, and generates new sub‑orders for re‑shipments.
Dual-Track Product Journal
Day-time e-commerce product manager, night-time game-mechanics analyst. I offer practical e-commerce pitfall-avoidance guides and dissect how games drain your wallet. A cross-domain perspective that reveals the other side of product design.
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.