Why Forklift Makers Are Selling Systems, Not Just Trucks
A truck is delivered, invoiced and forgotten. A fleet management system keeps talking to the customer every day. This article explains the forklift industry trend toward software, what it changes for buyers, and how to spec a truck so it still fits your systems in five years.
1. The forklift industry trend nobody put in a brochure
Walk the stands at a Chinese trade show and the pattern is hard to miss. Heli shows a fleet management system alongside its trucks. Hangcha talks about an industrial embodied AI model. Noblelift pushes a universal dispatch platform that manages machines from several brands.
None of that is charity. Software carries higher margin than steel. A truck sale is a one-off transaction with a price your purchasing team can squeeze. A platform is a subscription, a service contract and a data relationship. Once your warehouse runs on the supplier's dispatch logic, switching brands means rewriting your own process โ so the customer stays locked in, and the lock is comfortable enough that most buyers accept it.
There is a real operational argument underneath the commercial one. A 2.5 t counterbalance truck working 2,000 hours a year generates data that a paper logbook cannot: impact events, battery cycles, idle time per shift, travel distances by aisle. Manufacturers that collect it can sell you utilisation advice, not just spare parts. That is the honest half of the story.
2. What the shift changes for buyers
The specification sheet is no longer the deciding document. A 1.5 t electric pallet truck with a 1,150 mm fork length and 200 mm load centre is easy to compare against three competitors. The question that actually decides your project is whether that truck's controller and battery management system expose data in a format your WMS can consume.
Three things to check before you sign:
| What to ask | Weak answer | Workable answer |
|---|---|---|
| Data interface | "We have an app" | Documented API, or CAN bus / RS-485 access at the controller |
| Protocol | Proprietary, closed | MQTT, Modbus TCP, or REST over your own Wi-Fi |
| Data ownership | Stays with the vendor | You export raw logs, no per-truck licence fee |
| Integration support | "Contact our software team" | Named engineer, agreed commissioning scope |
| Roadmap | Roadmap does not exist | Written statement of what the interface will support in 3 years |
A truck that cannot answer the first row is a standalone machine. That is fine if you run three of them. It is a problem at thirty, when labour planning, battery charging schedules and aisle traffic all depend on knowing where each unit is.
Talk to the supplier's engineers, not only the salesperson. Ask how they handled the last integration where the customer's WMS was older than the truck. The answer tells you whether they have done this before or are planning to learn on your project.
3. How to choose a supplier when you are buying trucks, not platforms
Not every factory can build its own platform, and not every buyer wants one. Here is the position we take, and how we suggest you evaluate anyone in this market.
- We do not develop dispatch platforms. Nine product families and 41 models across a 28,880 sqm plant in Gaogang District, Taizhou is the work we do. Writing warehouse execution software is a different business with different people.
- Instead we keep the interfaces clean. Our AGV range uses standard communication protocols, and we publish the I/O and data points a third-party integrator needs. If your integrator asks for a signal list, you get a signal list.
- We work alongside specialist integrators rather than replacing them. During commissioning, our engineers handle the machine side โ navigation, load handling, safety sensors, charging โ and the integrator handles your WMS, ERP and conveyor logic.
- Ask any supplier what happens at year three. If the platform is tied to one brand of truck, adding eight units from another maker means running two systems. A supplier that supports mixed fleets, or at least documents its interface, costs you less later.
- Allow for integration interfaces at purchase, even if you are not ready to use them. The option usually costs nothing at order stage and cannot be retrofitted cheaply. Buying a truck without a data port in 2025 to save 1,000 CNY per unit is the expensive choice.
- Match the automation level to the task. An AGV replacing one repetitive 300 m shuttle run is worth more than a fleet dashboard that nobody reads. Replacing labour on one machine beats becoming part of a process you cannot maintain.
- Check certifications against your own market. Our manufacturing licence is TS2532202-2029, quality management is ISO 9001:2015, and CE verification is held under ICR/VC/HM260171. That paperwork matters when your own customer audits you.
4. FAQ
Does every forklift maker now have a fleet management system?
No. Heli, Hangcha and Noblelift have invested in platforms because their volumes support the development cost. The majority of Chinese manufacturers, including us, supply equipment and interfaces. For buyers, the practical difference is small unless you want one vendor to run your whole warehouse process.
If a supplier has no platform, can their trucks still report data?
Usually yes, within limits. Battery management systems, controllers and telematics modules can expose state of charge, fault codes, hour meter and impact events over CAN bus or RS-485. Whether you can read them depends on the supplier documenting the protocol. Ask for the document before the order, not after.
Is a proprietary platform a bad thing?
Not automatically. If you run a single-brand fleet of 20 trucks in one building, a vendor platform can be simpler and cheaper than integrating a third-party system. The risk appears when you add another brand, change 3PL provider, or want the data inside your own ERP. Check the export path and the exit cost.
How much should integration readiness add to a truck price?
In most cases nothing at the order stage โ the controller and telematics module are already there, and the question is whether the supplier hands over documentation. Retrofitting telematics to an existing 10-truck fleet typically costs far more per unit than ordering it fitted.
We are a 12-truck operation. Do we need any of this?
Probably not a dispatch platform. You likely do need charging data and hour-meter records, because that is where your cost per hour is decided. Start with the data you can actually act on, then decide whether software earns its place.
Will AGVs replace our counterbalance trucks?
Not in mixed-traffic yards. AGVs work where routes repeat and the environment is controlled โ line-side delivery, pallet transfer between fixed points, cold store shuttles. Counterbalance and reach trucks stay in the aisles where a driver judges a load, a rack and a pedestrian at the same time.