Skip to main content

Over an API, operated by SmartWay

The route optimisation core your TMS needs

Route4Green takes the list of orders and the list of vehicles for a date, works out how many vehicles you need and which orders each one carries, and only then sequences the stops on each route. Every run covers the whole fleet, up to 300 orders, for one date and one transport mode. The result is fewer trips and fewer kilometres per tonne of cargo.

What route optimisation is, and why optimising one vehicle at a time is not enough

SmartWay TMS runs on this same engine. If you operate a fleet, you can start with a free one-day measurement on your own data, against your own plan.

Who Route4Green is for

The route optimisation core is the engine that runs behind your software, connected over an API. TMS vendors build it into their product; fleet operators try it first on their own real data.

  1. TMS and transport software vendors

    Add route optimisation to your TMS

    Your customers assign orders across their whole fleet inside the TMS they already use. You only call the API: SmartWay operates and hosts the engine, and the product and the customer stay yours.

    See the partner programme
  2. Fleet operators

    Try it free on one day of your data

    Send one day or one shift of data: orders, the vehicle list, constraints and the plan you ran. We send back the routes Route4Green computes, set against that plan so you can compare them, free. If it fits, keep using it through SmartWay TMS or have your engineers connect over the API.

    Request a one-day measurement

    How much you gain depends on how often you plan each month and how many vehicles you schedule at once. From a few dozen vehicles up, assigning orders and building routes by hand usually becomes too much.

    • Enterprises running a large fleet of their own

      Postal, distribution and manufacturing companies with their own fleet of a few dozen vehicles or more, serving many stops a day. Every percent of trips and kilometres you cut adds up over every operating day.

    • Logistics operators and 3PLs

      Middle-mile and last-mile transport, five or more stops per trip. When shippers ask for figures per shipment, every planning run already gives you trips, kilometres and cargo for each route.

Who has worked with Route4Green

  • Vietnam Post (VNPost)
  • Gozo
  • SmartWay

One Pilot, with measured figures

A Pilot with Vietnam Post (VNPost) in Ho Chi Minh City, July 2026. Route4Green planned in parallel with VNPost's fixed routes, on the same order data.

What the API does

Public documentation, readable before you sign anything.

Open the API docs
  • Fleet-wide assignment and route optimisation

    Send your whole order book and fleet in one job, up to 300 orders for one date and one transport mode. The core decides which vehicles to use and which orders each carries, then sequences the stops, and returns what it could not place. Jobs run asynchronously.

  • Orders and request pools

    Push orders in, pool them, and the core decides which orders share a run.

  • Vehicles and vehicle plans

    Declare payload, box dimensions, working windows and a separate start point for each vehicle.

  • Webhooks

    Get notified when a job finishes, instead of polling.

  • API keys

    Issue and revoke keys per integration, yourself.

The three tiers of route optimisation, and which one this API does

Applications around the core

The core and the API are the product. SmartWay builds these applications on the same core; custom ones are quoted separately.

  • Available

    SmartWay TMS

    SmartWay's transport management system, running on the same core.

  • Coming soon

    WMS and TOS modules

    Warehouse and terminal operations, on the same order and vehicle data.

  • Built on request

    Vehicle tracking

    Position and trip status during the day, built per customer.

  • Built on request

    Adjusting routes after an incident

    Handling a breakdown, a cancelled order or a rush order mid-day, built to each customer's needs.

Why the hard part is not the algorithm

Route optimisation algorithms are available as open source, and we are not going to pretend otherwise. The expensive part sits elsewhere: describing your operation accurately enough that a solver can honour it, decomposing the problem at your fleet size, and keeping the result usable while your drop-point data is still imperfect. Route4Green ships that work as an API. If your engineering team wants to build it in-house, we will tell you plainly which parts are worth building and which are not.

Mathematics, not AI. The core solves order assignment and routing with operations-research optimisation methods; it does not learn from your data.

A worker in a high-visibility vest holds a tablet and watches a loading dock at dusk, where a forklift loads pallets into open trucks

Start with the step that fits you

TMS vendors: talk to us about embedding the core. Fleet operators: send one real operating day with the plan you ran, and get routes back with the difference, free.

Route4Green