How Leading O2O Platforms Engineer Scalable, Low‑Cost Architecture – Insights from Meituan, 58 Daojia & Didi

O2O Supply‑Chain System Architecture – Meituan

Meituan has evolved from a traditional group‑buying site into a large local‑life service platform that connects merchants and users across hotels, breakfast, travel and other categories. To support this diverse supply chain, Meituan built a flexible attribute center that allows new product categories to be configured without code changes, reducing development time to about five minutes. An event‑driven, decoupled workflow enables dynamic, minute‑level approval processes, and the entire order‑creation and dispatch pipeline is fully automated, eliminating manual intervention.

Order Dispatch & Data Analysis – 58 Daojia

58 Daojia launched its home‑service platform in June of the previous year and released it publicly on November 20. Within four months, its self‑operated categories (housekeeping, beauty, express delivery) achieved the highest order volume nationwide, covering 30 cities. The system manages workers' status, wages, performance, and dispatch logic. It uses an offline‑grid cache and multiple distance‑measurement APIs to filter nearby workers, and leverages business‑district and community‑level order analytics to optimize field promotion and improve user experience.

Meituan CRM Overview

Meituan’s CRM system connects the platform with merchants through five stages: lead discovery, opportunity conversion, onboarding, order creation, and settlement. It introduces a “lead sea” model and a public‑private sea transfer mechanism to streamline lead management. By automating BD tasks, the system boosts productivity, provides real‑time merchant insights, and issues early warnings to keep operations on track. Challenges include diverse lead types, rapid business expansion, and vertical O2O segmentation, which the CRM addresses through platform‑wide, modular design.

Low‑Cost Architecture Evolution – Didi

Didi’s infrastructure director explained that technology must serve business growth, not dictate it. With limited resources, architects prioritize cost‑effective solutions that maintain consistency across rapidly scaling services—Didi’s monthly traffic can grow eightfold within a week. The company adopts a simple codebase, pushes complex logic into the architecture layer, and relies on cluster‑centric designs to keep iteration fast and cost low. The key is to expose complexity through well‑designed architecture, allowing a small elite team to solve the hardest problems efficiently.