Why Route4Green, and how it works
Route4Green is a route optimisation core called over an API. Your system stays the source of data and the place decisions are issued. The core takes the whole order book and the whole vehicle list for a date and returns a plan per vehicle.
New to route optimisation? Read the explainer.Why Route4Green
It assigns orders across the whole fleet
Most software only reorders the stops of a vehicle that already has its orders. Route4Green first decides how many vehicles run and which vehicle takes which order, because that is where the cost is decided.
It is measured against your own plan
Compared with the plan you ran that same day, not an industry average, and stating whether both sides carried the same volume.
It fits inside the system you already run
The core is called over an API, so it can sit inside your own TMS or the one your TMS vendor supplies. The same core runs inside SmartWay TMS.
How it works
You bring one day or one shift
Orders, vehicles, constraints, and the plan you ran that day as the baseline.
Route4Green plans the whole fleet
The whole fleet in one run, up to 300 orders, for one date and one transport mode. Orders or vehicles it cannot place are returned, not hidden.
You get routes with the difference
Plan against plan: trips, kilometres and cargo per route, always with a row showing how much cargo each side carried.
A direct difference shows only when both plans carry the same volume within 1%. Beyond 1%, if the smaller still reaches 90% of the larger, the difference is per tonne of cargo. Below 90%, no difference, only the reason.
For developers: four integration steps
1. Get an API key
Request a trial; we get in touch and send a test key over a private channel, never on this site.
2. Push your data in
Declare vehicles and vehicle plans, then push orders and drop points. The input is your whole order book and every available vehicle for the date, not one route. With a TMS, this is usually a background sync job.
3. Run an optimisation job
Create a job with pickup and delivery windows, payload and dimensions, and vehicle working hours. It runs asynchronously because the problem is large.
4. Read the result
Poll the job, or register a webhook to be called back when it finishes. You get the orders per vehicle, the stop order, the plan metrics, and any orders or vehicles not placed.
How long integration really takes
It depends on how clean your order data is. With normalised drop points and coordinates, the API work is a few days. The longer part, and the most underestimated, is usually address normalisation and reconciling the vehicle list.
What does not exist yet
- No self-service sandbox yet. Test keys are issued by hand after a conversation, not on signup.
- The one-day measurement runs with the SmartWay team, not yet by yourself on the demo site. The team states which of your constraints were not applied.
- No per-language SDKs yet, only REST and the public documentation on this site.
- No official price list yet. Volume and rate are discussed with you directly.
Measure first, decide after
A one-day measurement on your data is free. The partner endpoint docs are public, no signup needed.