Multi-stop route optimisation
Submit orders, drop points, time constraints, and fleet. Get back an asynchronous optimisation job, then read the result when it finishes.
AI routing core
Route4Green takes your orders, drop points, and fleet, and returns an optimised route plan over an API. A shorter run means less fuel burned, fewer driver hours paid, and fewer vehicles pulled out of the yard.
Running in SmartWay production TMS operations, not a demo build.

Middle-mile operation in Thai Nguyen, 18 December 2024. 40 tonnes of freight, 18 drop points, 527km on the optimised plan.
40 millionVND
transport cost saved on that run
1,800 kg CO2
emissions avoided on that run
18 drop points
on a single 527km route
40 tonnes
freight carried on the run
18/12/2024
date of the run
Scope of these figures
Both figures are measured for that single run on 18 December 2024, against the route plan the customer intended to run for the same freight. They are not an average, not a typical result, not a commitment covering a company as a whole, and not a product lifecycle claim.
Previous plan against the optimised plan
Value returned scales with how many runs you dispatch per month, so the product fits multi-stop, high-frequency operations best.

Middle-mile and last-mile work with five or more stops per run. This is where every percent of distance removed multiplies across the month.
The group already being asked for shipment-level emissions figures. Route4Green returns per-run numbers you can carry into a report instead of re-estimating them by hand.
If your system already holds orders and vehicles, Route4Green plugs in over an API. No system replacement, no retraining your dispatch desk.
Public documentation, readable before you sign anything.

Submit orders, drop points, time constraints, and fleet. Get back an asynchronous optimisation job, then read the result when it finishes.
Create and adjust daily tour plans, assign vehicles and drivers, and check feasibility before dispatch.
Push orders in, pool them, and let the optimisation core decide which orders share a run.
Declare vehicles, payloads, and availability so the plan matches the fleet you actually have.
Subscribe to job completion events instead of polling for them.
Issue and revoke keys per integration, yourself.
Route optimisation algorithms are available as open source, and we are not going to pretend otherwise. The expensive part sits elsewhere: decomposing the problem at real scale, wiring in live traffic data, and recalibrating continuously against actual Vietnamese road conditions. Route4Green ships that work already done, tuned on years of live operational data. If your engineering team wants to build it in-house, we will tell you plainly which parts are worth building and which are not.
Create an account so we understand your operation and can grant test access. Keys are issued by hand today, so a person will write back to you rather than an automated system.