跪拜 Guibai
← All articles
Frontend · AI Programming · Agent

One Sentence to Book a Truck: How Huolala Wires WeChat AI into Ordering

By 货拉拉技术 ·
Read original on juejin.cn ↗ Google Translate ↗ Alt translation

The pattern shows how to bolt AI conversation onto a transactional product without letting the model touch money: isolate business capabilities as tools, force a native confirmation for payment, and keep AI code in a subpackage so it can change without breaking the main flow. Western teams building chat or voice ordering into existing commerce can copy this split, which keeps the agent's reach shallow and the transaction deep.

Summary

Huolala replaced a multi-page form flow with a conversational entry on WeChat's XiaoWei agent. The mini program exposes seven atomic abilities, from vehicle-type lookup to order cancellation, each calling real business APIs. The model never generates prices or order status; it extracts intent, asks for missing fields, and returns results to the agent. WeChat's GUI mode, where AI clicks through the page, failed on popups, map drags, and multi-turn context, so Huolala moved to MCP and Skill-based tooling.

Before payment, the thread returns to Huolala's native mini program through a Handoff card. The confirmation page recalculates price from current business data and clears the conversational context. The company also runs a self-built assistant inside its own mini program, sharing the same business APIs and guardrails. Both routes converge on the same principle: the model understands and orchestrates, the business system handles orders and transactions.

Takeaways
— WeChat offers three mini program integration modes: GUI (AI clicks UI), MCP (business APIs as callable tools), and Handoff (return to native page for payment).
— Huolala extracted seven atomic capabilities from dozens of order flows: query vehicle types, parse address, estimate price, query order details, list orders, repeat last order, and cancel order.
— The confirmation page recalculates the price from real business data instead of trusting the conversational estimate, because city config, vehicle availability, and pricing conditions can change.
— AI code lives in an independent subpackage with its own runtime and requests; the only bridge to the main package carries login state, handoff context, and an order draft that is destroyed after use.
— Huolala wrote 59 self-test cases covering address, vehicle selection, price, order query, repeat, cancel, and refusal, plus internal crowd testing to catch cases where the model invents details.
— One tuning example: the model added "about" to a vehicle length (3.8-4.3 m vs the interface's 3.9-4.3 m), so they added a constraint to repeat only the exact interface text for dimensions.
— Huolala runs two parallel routes: WeChat AI for channel reach and a self-built assistant inside the mini program for deeper product control, both sharing the same business APIs and native transaction flow.
Conclusions

The failure of GUI mode is instructive: simulating human clicks does not carry business context, so any page change breaks the chain. The move to MCP and Skills is the same shift seen across Western agent frameworks, from instructing an operator to exposing a standardized toolset.

The Handoff mechanism treats the model as a front end for intent extraction, not as a decision maker for money. That boundary is what keeps the system safe enough to ship.

The independent subpackage is a pragmatic isolation pattern. It lets AI code iterate at its own pace without touching the main mini program, which matters when adding an experimental conversational layer to a production checkout.

The two routes, WeChat AI and self-built, are not competing; they target different parts of the funnel. WeChat AI captures intent before a user enters the app, the self-built assistant deepens the experience inside it. The architecture that separates core business from channel adapters is the long-term answer.

Concepts & terms
Handoff
A mechanism in WeChat's mini program AI where the agent collects information in conversation, then sends the user to a native page to complete confirmation and payment, carrying the collected context.
Skill
In WeChat's MCP framework, a Skill is a packaged business capability (an atomic interface or component) that tells the AI what it can do, what inputs it needs, and what it must not guess.
Atomic capability
A single, composable business operation, such as "estimate price" or "cancel order", extracted from larger flows so the AI can combine them on demand.
Independent subpackage
A separate code bundle in the mini program that contains the Skill and its runtime, isolated from the main package except for a narrow handoff bridge.
Source: juejin.cn ↗ Google Translate ↗ Backup ↗