There is one week left until Double 11 (November 11) in 2026. Most people think of "another year of record-breaking GMV," but for enterprise digitalization leaders, this is the toughest system stress test of the year—the exam is not in marketing, but in warehouses, on production lines, and in every order table reconciled in real time.
First, look at the actual scale for the same period last year. Monitoring data from the State Post Bureau show that during the 2025 Double 11 period (October 21–November 11), postal and express delivery companies nationwide collected a total of 13.938 billion express parcels, with an average daily collection of 634 million parcels (117.8% of daily business volume), and the single-day business volume peak reached 777 million parcels, setting a new single-day record. Behind these 13.9 billion parcels are billions of orders coordinating at high frequency across ERP, WMS, OMS, and TMS. The major promotion is not just a matter for the logistics department, but a real-world test of the entire digitalized chain.
2025 Singles' Day single-day parcel collection peak (State Post Bureau), corresponding to the instantaneous concurrent coordination of billions of orders
I. The systemic test behind 13.9 billion parcels: an order surge is not a logistics matter, but an ERP matter
A common misconception among many enterprises is: major-promotion support = adding a few temporary sorting lines and hiring more hourly workers. But what truly drags down a major promotion is never “not enough people,” but “incorrect numbers”—overselling, channel diversion, inventory inaccuracy, and reconciling accounts until dawn. The source of these failures almost always lies in the integration quality between ERP and surrounding systems.
A typical chain is: e-commerce platform generates orders → OMS receives orders and allocates warehouses → ERP verifies inventory and credit → WMS picks and ships → TMS/carrier returns tracking information → finance automatically reconciles accounts. Any data delay or conflict in definitions at any node will be amplified into an incident under peak multipliers. The State Post Bureau specifically noted in a notice: "The postal and express delivery industry is actively strengthening information coordination with e-commerce platforms"—the subtext of this sentence is precisely that data connectivity between systems determines whether peak season can be "stable and orderly".
A major promotion is not an exam for the logistics department; it is a real-world battle for the entire ERP–WMS–OMS chain. Ordinary small delays will turn into major incidents at a peak of 777 million packages.
II. From "Production-Driven Sales" to "Sales-Driven Procurement": Intelligent Replenishment and a Unified Omnichannel Inventory View
The first principle for handling peaks is to turn "post-event firefighting" into "pre-emptive forecasting." This is exactly the capability that modern ERP is filling in. Take Odoo 20 as an example: its 2026 inventory module added three capabilities directly related to major promotions in one go: inventory aging analysis (the Movement Analysis pivot directly shows batch storage duration), historical point-in-time inventory (you can look back at the book inventory at any historical moment, precise to the exact time), and, most critically, suggested inventory levels—based on historical demand, desired coverage days, and ordering frequency, the system automatically provides minimum/maximum inventory recommendations for the reorder point.
This means that "how much inventory to stock" no longer depends on an old purchaser's gut feeling, but is based on historical sales, in-transit, and lead-time data. At the same time, Odoo 20 continues to strengthen native logistics connectors (ShipStation, EasyPost, Sendcloud, etc.) and continues direct integrations with 15+ carriers such as DHL, FedEx, UPS, USPS, Bpost, etc.; order shipping labels can be generated with one click within the system, and tracking updates are returned in real time.
After the fact
Traditional manual/script scheduling: inventory is synchronized through end-of-day batch processing, overselling is blocked after the fact, replenishment relies on experience, abnormal orders are manually investigated one by one, and response lags by several hours at peak times.
Beforehand
Intelligent integrated scheduling: unified omni-channel inventory view, intelligent replenishment thresholds, direct carrier API connections, automatic red-flagging of abnormal orders + manual gate, and minute-level response to peak fluctuations.
Now turn the lens to the production side. Midea has deployed 13,000 Factory Agents deep into production line scheduling and quality inspection; SF Express's 40,000-square-meter smart central warehouse has achieved fully paperless human-machine collaboration; MES/WMS solutions such as VEKAN connect semiconductor processes with IoT traceability—the common prerequisite for all of them is to first align the data foundation of ERP with manufacturing and warehousing. What a major promotion needs is not just "selling more," but also "supplying enough, shipping out, and calculating clearly."
III. Three Typical Types of Major Promotion Failures
① Overselling and negative inventory: Inventory across multiple platforms is not unified in real time; when Channel A sells out, Channel B still shows stock as available, so final commitments cannot be fulfilled, resulting in both high compensation and customer complaints.
② Inventory distortion and unauthorized channel diversion: There is a time lag between the physical flow in WMS and the book flow in ERP; discrepancies between book and actual inventory are amplified at peak times, and stocktaking and reconciliation fall into "the busier, the more chaotic."
③ System avalanche and reconciliation collapse: Peak concurrency exceeds the ERP/database capacity ceiling, interfaces time out, documents pile up, and the finance side cannot complete automated reconciliation by T+1, requiring manual firefighting until dawn.
The common thread among these three types of failures is that the "data mainline" breaks under peak load. They lie dormant in normal times and erupt during major promotions; in essence, they are accumulated shortfalls in integration architecture and governance, rather than a single operational error.
| 2025 Double 11 Logistics Key Metrics | Numeric value | Implicit requirements on the system |
|---|---|---|
| Total Collection Volume (10/21–11/11) | 13.938 billion items | OMS–ERP–WMS High-Concurrency Collaboration |
| Average daily pickup | 634 million pieces | For daily 117.8%, elastic compute is required |
| single-day peak | 777 million items | Instantaneous Concurrency and Interface Stability Limits |
| Green Peak Season Requirements | Reusable containers/New energy vehicles | Performance data is traceable and verifiable |
IV. Major Promotion Assurance Checklist for CIOs
1. First conduct a full-chain stress test, rather than just looking at whether "the servers are sufficient". The focus is on stress testing the end-to-end throughput of the main chain: order → inventory validation → warehouse allocation → shipment → feedback → reconciliation, rather than a single machine.
2. Establish a unified omnichannel inventory view. Inventory across multiple platforms, multiple warehouses, and in-transit is consolidated into a single trusted data source, eliminating overselling caused by "each channel saying its own thing."
3. Get the smart replenishment thresholds up and running.Use historical sales plus lead time to set reorder points, complete safety stock recalculation before major promotions, and avoid experience-based overstocking or stockouts.
4. Direct WMS-to-carrier API connection. Reduce manual handoff steps so that shipping labels, tracking feedback, and exception alerts close the loop within the system.
5. Set up a "manual gate for exception orders." Orders that exceed thresholds (amount, quantity, remote location) are automatically flagged in red and routed to a person. Automation ≠ letting go entirely; key decision-making authority stays with people.
This matters especially for small and medium-sized manufacturers: rather than temporarily adding staff and warehouse space, it is better to first get an ERP running smoothly that "balances the books and shows real-time inventory." When system consistency is in place, combined with a small amount of automation, you can handle most peak-season surges; conversely, with a pile of systems whose data all tell different stories, even the strongest logistics team will find it hard to remedy the situation.
The 13.9 billion parcels of Double 11 are a footnote to consumer vitality and a touchstone of enterprise digital maturity. It forces every company to answer one question: is your ERP really just a "bookkeeping back office," or is it a "business main artery" that can withstand peak loads and collaborate in real time? The answer determines whether, this time next year, you will wrap up with ease or fight fires all night.
Data sources for this article: the State Post Bureau's "Express Delivery Volume Hits a New High Again During 'Double 11' 2025" (2025-11-12, spb.gov.cn); Odoo's official Odoo 20 e-commerce and logistics connector documentation (odoo.com / odooai.cn, 2026); Majorbird's "Odoo 20 Inventory Management: Inventory Aging Analysis, Historical Point-in-Time Inventory, and Smarter Replenishment" (2026); and this series' earlier reports on Midea's Factory Agent, SF Express's smart central warehouse, and VEKAN MES/WMS. Data as of 2026-11-04.
众谛信息 · Focused on Odoo and enterprise management digitalization solutions
