Tracking data tells you where things are. The freight invoice tells you what actually happened, and it is the only logistics record that is both complete and financially authoritative.
Shipment tracking is incomplete by nature. Scans are missed, portals disagree, and a shipment that moved on a different trailer than planned may not reconcile at all. Useful for knowing where a truck is, and a poor foundation for analysis.
Logistics analytics projects usually start from tracking data because it is live and interesting. Half the questions worth asking cannot be answered from it, and the half that can is the operational half rather than the financial one.
This table is the sourcing decision, and the lag column is the reason the invoice gets ignored despite being the better source.
Fragmented transportation and distribution data
Carrier portals, a transport system, the warehouse system, order data and the invoices, each with its own shipment identifier. The join is the project.
Limited shipment and delivery visibility
Visibility is a carrier-by-carrier problem. Some provide good events, some provide a portal and no feed, and some provide a daily spreadsheet. A single view accommodates all three rather than waiting for parity.
High transportation and logistics costs
Which is a mix of rate, mode, lane, fill, service level chosen and accessorials. Attributing the cost to those components is the work, and the third position on this page is where the surprises are.
Delivery delays and inconsistent service levels
Measured against whichever date somebody picked, which is the second position on this page and the reason most service level reporting cannot be compared year on year.
Inefficient distribution network performance
Network questions need cost, volume and service together, which means the invoice joined to orders. Without that join, a network review runs on assumptions.
Limited carrier performance visibility
Carriers are usually compared on rate, which is the only dimension that is easy. Service and accessorial behaviour differ more than rates do.
Manual logistics reporting
A weekly or monthly pack assembled from carrier portals by hand. Accurate at the time, impossible to trend, and dependent on one person.
Warehouse-to-distribution coordination challenges
Where detention and redelivery charges originate. These are the clearest example of an operational problem that appears as a logistics cost.
Difficulty identifying freight cost drivers
Because the cost arrives as an invoice line with a charge code, and the charge codes are carrier-specific, inconsistent and undocumented. Normalising them is section 3.
Limited visibility into delivery exceptions and disruptions
Exceptions visible per carrier and not in aggregate, so a systemic problem looks like a series of individual ones.
The invoice gives a complete financial picture in weeks. Tracking integration gives an operational picture and takes longer, carrier by carrier. Doing them in that order means the first deliverable is a cost analysis that stands up, which funds the rest.
Step 1
Logistics and distribution process assessment
How freight is booked, by whom, against what rates, and who decides the mode and the service level. Those decisions are where the cost is set.
How freight is booked, by whom, against what rates, and who decides the mode and the service level. Those decisions are where the cost is set.
Step 2
Transportation and distribution data source discovery
Invoices, carrier feeds and portals, the transport system if there is one, order and shipment data, and proof of delivery. Per carrier, since they differ.
Invoices, carrier feeds and portals, the transport system if there is one, order and shipment data, and proof of delivery. Per carrier, since they differ.
Step 3
Logistics KPI and performance metric definition
On-time defined explicitly against a named reference date, and in full defined, before anything is built. This is the second position on this page.
On-time defined explicitly against a named reference date, and in full defined, before anything is built. This is the second position on this page.
Step 4
Shipment, carrier and delivery data integration
Joined on the shipment, which requires reconciling several identifiers, and joined to the order so that cost can be attributed to a customer and a product.
Joined on the shipment, which requires reconciling several identifiers, and joined to the order so that cost can be attributed to a customer and a product.
Step 5
Logistics analytics data modelling
With the accessorial charge codes normalised across carriers into a common taxonomy, which is the single most valuable piece of modelling on this page.
With the accessorial charge codes normalised across carriers into a common taxonomy, which is the single most valuable piece of modelling on this page.
Step 6
Transportation cost and performance analysis
Cost by lane, mode, carrier, customer and product, with the accessorial share separated from the base rate.
Cost by lane, mode, carrier, customer and product, with the accessorial share separated from the base rate.
Step 7
Distribution dashboard development
A logistics operations view, a cost view for finance and procurement, and an executive view. Three products on one model.
A logistics operations view, a cost view for finance and procurement, and an executive view. Three products on one model.
Step 8
Delivery exception and delay analysis
Attributed to a cause: carrier, dock, order timing, customer availability or a planning decision. The attribution is what makes it actionable.
Attributed to a cause: carrier, dock, order timing, customer availability or a planning decision. The attribution is what makes it actionable.
Step 9
Business validation and operational rollout
Cost figures reconciled to the ledger and to the carrier invoices before publication, since this page produces financial numbers.
Cost figures reconciled to the ledger and to the carrier invoices before publication, since this page produces financial numbers.
Step 10
Continuous logistics analytics optimisation
With the charge code taxonomy maintained, because carriers add codes and a new code quietly lands in the unclassified bucket.
With the charge code taxonomy maintained, because carriers add codes and a new code quietly lands in the unclassified bucket.
The source is named for each, from the table in section 2, because it determines both the lag and whether the capability is achievable with the data you have today.
Freight spend and cost-to-serve analysis
Cost by lane, customer, product and order. Source: invoice joined to orders. The foundation of this page and the first thing we build.
Transportation cost analytics
Base rate separated from accessorials, by mode and lane. Source: invoice, with the charge code taxonomy from section 3.
Route and lane performance analytics
Cost and service by lane, with volume and fill. Source: invoice for cost, tracking for service.
Carrier performance scorecards
Rate, service and accessorial behaviour together. Source: both. A carrier comparison on rate alone is the common and misleading version.
On-time delivery analytics
Against an explicitly named reference date. Source: tracking, verified against proof of delivery where the stakes justify it.
Shipment tracking and visibility analytics
Where shipments are and which are at risk. Source: carrier feeds, accommodating the carriers that provide less.
Delivery exception monitoring
Exceptions detected and attributed to a cause. Source: tracking, plus absence monitoring on shipments that have stopped scanning.
Distribution network performance analytics
Flow, cost and service across the network. Source: invoice joined to orders, which is why a network review needs the invoice work first.
Warehouse-to-distribution performance reporting
Dock and loading performance, including detention incurred. Source: both, and it is where logistics cost meets warehouse operations.
Logistics capacity and utilisation analytics
Fill rate by shipment and trailer utilisation. Source: invoice weight and dimensions against capacity. Frequently reveals consolidation opportunities.
Logistics executive dashboards
The management view. Built last, on a cost model that has already been reconciled, because this page produces financial figures that will be challenged.
The first three need only the invoice and can be delivered in weeks. The rest need carrier event data and arrive later. That ordering is deliberate.
Freight cost analysis by lane and customer
What each lane and each customer actually costs to serve.
Accessorial charge analysis
Charges normalised across carriers and attributed to a cause.
Logistics capacity utilisation analysis
Fill rate by shipment and consolidation opportunity.
Transportation cost-to-serve analysis
Cost per order, per customer and per product.
Carrier on-time performance comparison
Service compared across carriers on the same lanes.
Shipment delay identification
Which shipments are late or at risk now.
Delivery exception root cause analysis
Exceptions grouped by cause rather than by carrier.
Distribution centre performance reporting
Throughput, dock performance and detention incurred.
Customer delivery service-level monitoring
Performance against customer commitments.
Route and lane performance benchmarking
Cost and service by lane over time and against alternatives.
Two pieces of modelling carry this page. The shipment identity, because the invoice, the carrier feed, the transport system and the order all name a shipment differently. And the accessorial charge taxonomy, because without it a third of the cost sits in carrier-specific codes nobody can aggregate.
Logistics analytics reference architecture
Ingestion per source, a conformed shipment layer, the charge taxonomy, a governed semantic model, and views for operations, cost and executive audiences.
TMS, WMS, ERP and carrier data integration
Including the carriers that provide a portal and a spreadsheet rather than a feed, since waiting for feed parity means waiting indefinitely.
Shipment and transportation data models
Shipment, stop, leg, charge and order, modelled so that a cost can be attributed to an order line and therefore to a customer and a product.
API, EDI and batch data ingestion
EDI remains the standard route for many carriers and customers. Batch is appropriate for invoices and adequate for most of this page.
Geospatial and location-based analytics
Lane and network analysis, distance-based cost comparison and service mapping. Useful and frequently over-emphasised relative to the cost modelling.
GPS and telematics data integration where available
Where you operate your own fleet or a carrier shares it. Valuable for dwell and detention analysis specifically, which ties to the third position on this page.
Data warehousing and lakehouse platforms
Selected against your existing commitments and your team’s operating capability.
Microsoft Fabric and Power BI
Named in the brief. We work with these where the client already runs them. The choice follows the estate and the operating model, and we state no partner or certification status.
Statistical and predictive logistics analytics
Delay prediction and lane cost modelling. Modest techniques on a reconciled dataset beat sophisticated ones on an incomplete one, which is the usual trade here.
Logistics reporting and visualisation platforms
Per audience on one model, with freight cost restricted by role since it is commercially sensitive and sometimes contractually confidential.
Governance defines who may change a measure or a definition, how disputes get resolved, and how commercial and contractual confidentiality is protected. Everything below serves one of those three.
This page produces figures that leave the building: a carrier scorecard, a customer service level, a cost-to-serve figure used in a commercial conversation. Each of those will be checked against somebody else’s records, which sets a higher standard than internal reporting.
Transportation KPI definition and standardisation
On-time and in-full defined explicitly, published with every figure, and under change control. A change to the reference date changes every historical figure, so the change record is also a reporting notice.
Shipment and carrier data governance
A named owner for the shipment identity mapping and the charge taxonomy, since both decay as carriers and systems change.
Shipment event data quality
Completeness measured per carrier, so a carrier with poor event data is identified as a data issue rather than appearing as a service issue.
Freight cost data confidentiality
Rates and contract terms are frequently confidential under the carrier agreement. Restricted by role at the model layer, and checked against the agreement before any figure is shared externally.
Carrier and logistics partner data access
Scoped and expiring where carriers consume the analytics, with a carrier able to see only their own data.
Data reconciliation and reporting controls
Freight cost reconciled to the ledger and to the invoices on a stated cadence. This page makes financial claims and they will be audited.
Role-based logistics analytics access
By role and region, with customer-level cost visibility restricted since it is commercially sensitive internally as well as externally.
Data lineage and auditability
Every figure traceable to the invoice line or the carrier event behind it, which is what allows a disputed number to be resolved during the meeting rather than after it.
Exception escalation and operational ownership
Each exception type with a named owning role and a response expectation, and detention and redelivery routed to the operation that caused them rather than to logistics.
Logistics analytics platform reliability
A named owner, pipeline monitoring including carrier feeds that stop silently, and freshness visible on every view.
Either one alone can be improved by making the other worse: service improves by buying premium freight, cost improves by downgrading service. The pair, with the definitions published alongside, is the honest statement.
On-time delivery performance
Against a named reference date, with the reference stated on the report. Reported against two references where the business needs both.
On-time in-full performance
With in full defined per section 5, and partial deliveries counted as what they are.
Transportation cost per shipment
Base rate and accessorials separated, because a stable total can hide a rising accessorial share.
Freight cost per unit or weight
Normalised so that a mix change is distinguishable from a rate change, in the same spirit as the price variance decomposition on the Procurement & Supplier Analytics page.
Accessorial charge share
By category and by origin. The measure that converts a freight cost problem into an operational action list, per the third position on this page.
Carrier performance
Service, cost and accessorial behaviour together, on comparable lanes. A carrier comparison on rate alone is the misleading default.
Shipment delay frequency
With the cause attributed, and with the share where no event data exists reported separately rather than assumed on time.
Distribution centre throughput
Volume and dock performance, including detention incurred, which connects warehouse behaviour to freight cost.
Route and lane performance
Cost and service by lane over time, which is the primary input to a tender.
Logistics capacity utilisation
Fill rate by shipment, with consolidation opportunity quantified rather than described.
Delivery exception resolution time
From exception to recorded resolution, by type and owner.
Logistics reporting accuracy
Reconciliation variance against the invoices and the ledger, which is the measure that protects the credibility of everything above.
Better transportation cost control, with the accessorial analysis usually producing the first and clearest set of actions
Improved shipment and delivery visibility, limited per carrier by what each one actually provides
Stronger carrier performance management, from comparing service, cost and accessorial behaviour together rather than rate alone
Earlier identification of delivery disruptions, with absence monitoring on stalled shipments as the cheap first version
Improved distribution performance insight, including the detention and redelivery costs that warehouse operations do not currently see
Better logistics planning and network decisions, which require the invoice joined to orders and cannot be done credibly without it
If your logistics reporting runs on carrier portals, the fastest improvement available is to model twelve months of invoices. It takes weeks, it needs no carrier integration, and it usually finds avoidable charges nobody had categorised.
CaliberFocus builds logistics analytics on the freight invoice, the only logistics dataset that is complete and financially authoritative. We join it to the orders it carried, normalise accessorial charges into one taxonomy so avoidable costs have a cause, define on-time against a named reference date, and add carrier event data carrier by carrier.
- Twelve months of freight invoices joined to orders
- Accessorial charges normalised and attributed to a cause
- On-time and in-full defined before they are measured
- Cost figures reconciled to the invoices and the ledger
Security & Compliance
