RELEASE NOTES

Changelog

What shipped, in the order it shipped. Grouped by what it changes for you rather than by the commits behind it.

RSS feed

Fleet schedule, and a map-first vehicle picker

A fleet calendar for every truck, vehicle picking on the map, and faster map pages.

TOVR
  • The fleet calendar lands: absences, maintenance windows and committed legs for every truck on one timeline.
  • Picking a vehicle now happens on the map — you see where a truck actually is before you commit it, not after.
  • Map surfaces load on demand, so the fleet and dispatch pages open noticeably faster on a cold visit.

Billing you can read before you are charged

Invoices announce themselves, statements summarise the month, and every usage line traces to one leg.

TOVR
  • An invoice announces itself by email the moment it is ready, and a monthly statement summarises the period.
  • Usage is keyed per committed leg, so every line traces back to one leg of one chain instead of a monthly total.
  • Own-fleet work is told apart from procured capacity in the usage breakdown.

One identity per shipment, and honest platform names

The same load on two exchanges is one shipment, and every freight platform is named.

TOVR
  • The same load seen on two exchanges resolves to one shipment, so duplicates stop competing with each other.
  • Every freight platform is named in the interface, and a load can say it appears on more than one.
  • Visibility is a property of each sighting and is derived per organization, so what you can see is yours alone.

An audit trail worth reading

Specific activity verbs, written in the same transaction as the change, including refused actions.

TOVR
  • Thirty-three activity verbs across seven namespaces replace the generic entries the activity log used to record.
  • Activity is written on the same transaction as the change it describes, so a change can no longer commit without its record.
  • Refused actions are recorded too — who tried, on what, and which rule stopped them.

Freight chains, rebuilt around the map

Workspace, timeline and map share one filter set, and creating a chain is a single flow.

TOVR
  • The chain workspace, the timeline and the map share one filter set, so narrowing one narrows all three.
  • Creating a chain is a single flow whether you start from a shipment, from a vehicle, or from nothing.
  • Chain cost breakdowns are shown in place rather than behind a separate sheet.
Changelog | TOVR