Route4Green Sandbox
Watch the route optimization core work, right here
One delivery day per industry, prebuilt on the map: the Route4Green dispatch plan beside a simple routing rule. No account, no install.
From a Pilot (trial run) with a national postal operator: -21% km per tonne of cargo, plan versus plan over 5 operating days. The Route4Green dispatch plan covered about 62% of the tonnage actually moved. See the figures and how they were normalised
From a scenario to a contract
The first three steps take a few hours, on your own or with us. The Pilot (trial run) is where both sides commit.
- 1
Watch a scenario
Industry scenarios on simulated data, no account needed.
See the sample scenarios - 2
Compare one day of your data
Pick a day in the file you already use; the page sets the Route4Green dispatch plan beside your current one.
Compare dispatch plans - 3
Guided demo
We run one day of your data and read the result with you.
Book a demo - 4
Pilot (trial run)
Eight weeks: two weeks of data preparation, then six weeks running alongside your current operation.
- 5
Contract
Go or stop, decided on the Pilot acceptance report.
Prebuilt scenarios on the map
Each scenario is a typical operating setup on synthetic data: orders, vehicles and depots go in, in the same format as an order import file, and optimized routes come out on the map.
By industry
01
Dealer distribution: 100 dealers in Ho Chi Minh City
One central warehouse in Binh Tan, 20 trucks of 2.5 t and 100 dealers in the outer wards to restock in a day. Unloading takes about 20 minutes a stop, so which orders share a trip decides both the distance and the hours on the road.
What point-to-point routing tools do not do
Says which orders could not be routed
When the fleet is short, the optimizer does not force more orders onto an overloaded route. It returns the list of unassigned orders with the reason (they exceed the fleet's remaining capacity) so you can plan the next wave, the way real operations work.
Several operating modes in one plan
First-mile collection, mid-mile line-haul, last-mile delivery and pick & drop are different problems. One plan can carry several kinds of leg at once.
Several depots in one solve
Which depot serves which order is not a human decision made before optimizing. The optimization core picks the depot and the stop order in the same solve.
Figures from a Pilot with a national postal operator
Plan versus plan over 5 operating days: the Route4Green route plan next to the route plan the operator was running, for the same post office network.
-26%
trips per tonne of cargo
0.86 -> 0.64 trips per tonne, volume-normalised because the plan covered only about 62% of the tonnage
-21%
km per tonne of cargo
26.8 -> 21.1 km per tonne, volume-normalised because the plan covered only about 62% of the tonnage
+35%
kg per route
1,156 -> 1,564 kg per route, a raw ratio that needs no normalising
Why normalise: over those 5 days the Route4Green dispatch plan covered only 62% of the tonnage moved (186 tonnes against 300). The two plans carried different volumes, so the raw -54% trips and -51% km are never quoted alone; per tonne figures correct for it.
This is plan against plan, not odometer readings, and it is one Pilot.
See the evaluation processCompare plans on one day of your own data
Use an Excel or CSV export from your system. The page checks it against the published thresholds, then sets the Route4Green dispatch plan beside your current dispatch plan for one day. Your browser reads the file; only address text and that day's figures are sent.
Where your data goes
The file is read here, in this browser. Name, phone and note columns, every unused column and the data of other days never leave the browser.
When addresses are looked up
Only the address text of points without coordinates, including a depot address you type, goes through the Route4Green server to Goong, the address lookup provider, to find coordinates. Before sending, digit runs shaped like phone numbers are filtered out of the address cell by pattern.
Lookup results are cached on the server in encrypted form for at most 90 days, so the same address is not looked up twice.
When you send a comparison
The Route4Green server receives the chosen day's data to build the Route4Green dispatch plan and set it beside the current dispatch plan:
- order codes, weights, delivery windows, and loading and unloading minutes per order
- delivery point codes with coordinates, without the address text
- the depot coordinates, the vehicle working hours and the fleet you declare
- the vehicles or routes of the current dispatch plan, the order sequence on each, and route km when the file has them
Not sent with the comparison: address text, names, phone numbers, notes, other columns and other days.
How long it is kept
- Comparison results are kept on the Route4Green server for the number of days the trial key allows, counted from sending.
- Creating a share link stores an encrypted summary of the result on this site, kept no longer than the link. A share link opens until it expires, at most 30 days, or until you revoke it.
- The trial key is stored in a cookie in this browser for at most 30 days, and never beyond the key's expiry.
On the engineering side? The API docs and the integration guide live on route4green.com. Open the API docs