A landed cost dashboard earns its place when it shows the few numbers that trigger decisions: cost per unit by lane, duty rate accuracy, freight variance, and clearance time. Vanity totals that never change a decision do not belong on it.
The headline KPI is landed cost per unit, shown by product family and by lane, with the trend, not just the current value. A single company wide average hides exactly the movement that matters: one lane repricing, one category duty change, one supplier drifting.
Split the unit cost into its components on drill down: goods, freight, duty, and fees. When the headline moves, the first question is always which component moved, and a dashboard that cannot answer it in one click sends the team back to spreadsheets.
Estimate to actual variance belongs on the dashboard beside the costs themselves, by category. It tells leadership whether the numbers underneath pricing can be trusted this month, and it gives the reconciliation process a visible scoreboard.
Duty rate accuracy and classification exception counts belong in the same block: entries amended, rates corrected, and exams or holds per period. These are leading indicators. A rising exception rate today is next quarters duty surprise, visible early enough to fix.
Clearance time by lane, hold rate, and time from arrival to available stock all convert directly into inventory cost and stockout risk. A lane that is cheap on paper and slow in practice is not cheap, and the dashboard should show both numbers in the same row so the trade off cannot be missed.
Demurrage, storage, and exam fee totals deserve a line of their own. They are the purest waste in the system, nobody budgets them as strategy, and a visible monthly total has a way of funding the broker and data fixes that reduce it.
On time shipment rate, documentation error rate, and packing compliance by supplier predict landed cost problems before they invoice. Adding two or three supplier indicators turns the dashboard from a finance report into an operations tool purchasing actually opens.
Keep the supplier view factual and shared. The goal is a joint fix list, not a scoreboard for arguments, and suppliers respond better to a documented error rate trend than to anecdotes from the last bad shipment.
One screen, one owner, one weekly review where each KPI has a named decision attached: reprice, reclassify, renegotiate, reroute, or fix data. A KPI with no decision attached gets removed at the quarterly tidy, however interesting it is.
Freshness is part of honesty. Show the data date on the dashboard itself, and let stale data look stale. A dashboard the team trusts, checks weekly, and acts on beats a beautiful one that quietly stopped updating in March.
Keep reading: How do you reconcile estimated landed cost against what shipments actually cost?, How can sales teams quote confidently when landed cost is a range, not a number?, and How do finance teams forecast landed cost variance by trade lane? cover the nearby cases in this series.
Landed cost per unit by product family and lane, with its trend and a component split into goods, freight, duty, and fees. Averages hide movement. The split shows which component moved when the headline changes.
Because decisions are only as good as the cost file under them. Estimate to actual variance by category tells leadership whether pricing can trust the numbers this month, and scores the reconciliation process visibly.
Clearance time by lane, customs hold rate, and arrival to available stock time. Slow lanes carry inventory and stockout costs that offset cheap freight, so cost and speed belong in the same view.
Give every KPI a named decision and an owner, review weekly, and remove any metric that drives no decision at a quarterly tidy. Show the data date on screen so stale numbers cannot pose as current.