How Meituan Scaled Its O2O Supply Chain: From Manual Chaos to 90% Cost Reduction

Meituan has expanded beyond traditional group‑buying into O2O sub‑domains such as hotels, travel, food delivery, and breakfast, each with varying levels of standardization. Supporting project production across these domains efficiently and reliably became a critical challenge for its supply‑chain system.

What Is a Supply Chain

According to supply‑chain expert Martin Christopher, "21st‑century competition is between supply chains, not companies." In Meituan's O2O battlefield, the supply chain (SCP) links merchants and users. Merchants sign contracts, which are digitized into detailed, searchable project proposals that include descriptions, pricing, and purchase restrictions. After verification, these proposals appear on Meituan's consumer‑facing apps for purchase and consumption.

Supply Chain System Challenges

Fine‑grained data structuring – Different O2O categories (e.g., restaurant vs. hotel) require vastly different attribute sets, sometimes approaching 100 fields for a single offering. This granularity is needed both for high‑speed merchant‑side entry and for rich consumer search.

Flexible selling modes – Hotels, for example, combine room type, breakfast inclusion, and seasonal pricing, creating combinatorial SKUs that must be recorded once yet sold in many variations.

Dynamic category and attribute adjustments – New sub‑categories (e.g., Wi‑Fi‑enabled buffets) demand rapid UI and storage changes, requiring a zero‑code approach for the supply‑chain system.

Configurable audit workflows – Different business channels need distinct approval steps, and these steps must be reconfigurable as policies evolve.

Facing the Challenges

Meituan moved from ad‑hoc development to a structured architecture centered on a "product center". Services (e.g., big‑bed room, breakfast, Wi‑Fi) are modeled as units that merchants assemble into sellable bundles. These bundles map to SKU attributes that drive sales, consumption, and pricing rules.

Event‑Driven Decoupling

To make audit processes dynamically configurable, Meituan introduced a workflow engine. Each channel defines its own approval nodes, responsible roles, and transition logic, all configurable without code changes. This decouples business logic from the core supply‑chain platform and enables native process data for analytics.

Automation Everywhere

Meituan split the order‑entry pipeline into multiple automated stages, introducing "no‑review" and "no‑write" shortcuts. The goal, dubbed project 908, was to cut per‑order cost by 90% and improve efficiency eightfold.

Results

For a typical discount‑order flow, development effort dropped from 30 person‑days to 5 person‑days. Order volume grew 1000% while per‑order cost fell over 90%. The audit team was dissolved, and the system now supports rapid, code‑free category and attribute changes via the attribute center.

Conclusion

Technically, the supply‑chain workflow follows an MVC pattern: the front‑end (BD) submits a request, the back‑end renders a dynamic form (DF), the Attribute Center validates input, the Product Center stores the model, Gravity schedules audit tasks, and the CMS assembles the final consumer‑facing content using dynamic templates. This architecture delivers high availability, automation, and rapid adaptability for Meituan's O2O ecosystem.