Rivière FreightControl tower
Concept · sample dataBuilt by Flippie Labs
Live
Rotterdam 14:06:12 CEST
SM

Operations

Wednesday 14 October 2026 · 5 hubs · 8 lanes

AI note

Network

Lane thickness is shipment volume, colour is on-time status

On track (95%+) At risk (90 to 95%) Delayed (under 90%)

LaneVol · OTD

On-time delivery

By hour, against the 95% target

Exceptions by reason

Live shipments

Departures and arrivals in the current window, refreshed from truck telematics

In transit At risk Delayed Delivered
ShipmentLaneCarrier / truckPalletsETAStatus
Rivière Freight is a fictional company. Concept dashboard with sample data. Built by Flippie Labs

Home / Examples

Logistics KPI dashboard example: a control tower for a regional freight network

This logistics KPI dashboard is a concept on sample data: a control tower for Rivière Freight, a fictional carrier running 8 lanes between hubs in Rotterdam, Antwerp, Venlo, Duisburg and Lille. It's made for an operations manager who needs to see, during the working day, which lane is slipping and why.

What this logistics KPI dashboard shows

Six KPI cards, each with a small trend line, cover shipments, on-time delivery against a 95% target, average transit time, open exceptions, cost per shipment and fleet utilisation. The range switch has three settings: today (compared with last Wednesday at the same time), the last 7 days and the last 30 days, each against the period before.

The network map is the centre of the page. Each lane is drawn between two hubs, its thickness shows shipment volume and its colour shows on-time status: on track at 95% or better, at risk between 90 and 95%, delayed below 90%. Next to the map, the lane list is sorted worst first. If you hover a lane you get volume, late shipments, average transit and cost per shipment; a hub gives shipments in and out. On the right, one chart tracks on-time delivery by hour today (or by day for the longer ranges) against the target, and another splits exceptions by reason: late pickup, capacity, address issue, customs and damaged goods, with how many are still open. At the bottom, a live shipments table lists each truck with its lane, carrier, pallets, ETA and status.

How it is built

It's a web app in HTML, CSS and JavaScript, with SVG charts and an SVG map. Every number comes from one set of generated shipment records with a fixed seed, so the KPIs, map, charts and note always agree. The Live badge and the ticking clock are part of the concept; nothing streams into this demo.

The AI note at the top is written from those computed figures. It picks the lane with the lowest on-time rate, gives its late count, names the most common exception reason and its share, counts the trucks on that lane running behind right now, and suggests an action that fits the reason, such as checking tractor availability at Duisburg when the problem is capacity.

For a real operator the data would come from the TMS and truck telematics and refresh as often as the planners need, perhaps every few minutes. Access would be set per role, so a hub lead sees their own hub and the operations manager sees the whole network.

Can it work as a warehouse KPI dashboard?

Partly. The hub view is the closest thing here to a warehouse KPI dashboard: for each hub it shows shipments in and out, late shipments and the number of lanes. This demo doesn't track what happens inside the building, such as pick accuracy, dock-to-stock time or inventory accuracy. Those would come from your WMS and fit into the same layout, and the whole design could also be built in Power BI if that's where your team already works.

If your shipment data sits in a TMS, a WMS or a set of spreadsheets, I can build a dashboard like this on your own numbers. Live dashboards · All examples