Want Want Group standardizes transport across 34 bases and 76 factories on NiuX TMS
A group with 34 bases, 76 factories, and nationwide dispatch can't run on spreadsheets and phone calls. Want Want rolled out NiuX TMS to unify carrier orchestration, in-transit visibility, and settlement across the entire manufacturing footprint — and replaced silo-by-silo logistics with a single operating picture.
The operating reality before NiuInfo
Want Want’s product portfolio is famous. The logistics that moves it is less visible — and, until recently, far less standardized. Every production base handled its own carrier relationships, its own order formats, its own settlement spreadsheets. Across 34 bases and 76 factories, that fragmentation cost Want Want in three ways:
- Invisible capacity. Empty trucks leaving one base while another was paying premium spot rates — with no system-level visibility to spot it.
- Slow reconciliation. Month-end finance cycles stretched into week-long reconciliation marathons because every plant used its own rate logic and file format.
- Hard to enforce standards. Service level commitments to key accounts varied by plant — not because Want Want wanted them to, but because the tooling didn’t make it easy to standardize.
The strategic question the group had been asking for years: how do we run transportation like one company — without taking away the local flexibility each plant actually needs?
What we built together
NiuX TMS is deployed as a group-level control tower that rolls up to headquarters while respecting per-plant autonomy. Three design choices made it work:
- One carrier orchestration layer. Any of the 76 factories can dispatch to the group’s shared carrier pool with the same order format, the same rate logic, and the same in-transit tracking. Carriers see one company, not 34 independent customers.
- A shared rules engine, local policies. Want Want headquarters defines the enterprise baseline — minimum service levels, approved carriers, cost ceilings for each lane. Each plant can layer its own policies on top without forking the system.
- Settlement packaged, not spreadsheeted. Rate cards, allocations, and exception-based adjustments flow directly from execution events into monthly settlement packs. Finance no longer reconciles line-by-line.
How it runs today
The rollout is deliberately phased — priority regions first, then the long tail of smaller plants. Early phases already show what “one operating picture” means in practice: a single dashboard shows where every shipment is across every base, which carriers are meeting commitments, and where cost anomalies are emerging before they become month-end fires.
For the planners who spent years stitching plant-level data together manually, the change is dramatic: the meetings about what happened have been replaced by meetings about what to do next.
Why this story matters for operators like you
If your group runs 10+ production sites and logistics is still a federation of spreadsheets, the Want Want story is directly relevant. The blocker is almost never the will to standardize — it’s finding a TMS that can enforce group standards without crushing plant-level agility.
NiuX TMS is built for exactly this: one platform, one data core, many operating contexts. You get the group-level economics (shared carriers, consolidated billing, enterprise dashboards) without asking every plant to run their operation exactly the same way.
That’s the reason Want Want — a company that could have picked any global TMS — chose NiuInfo.
Products mentioned