.webp)
A UK Supply Chain Director we spoke to last week was fielding the same board question every Monday: where is the Rotterdam-inbound container? Her answer, from EDI 214 events plus vessel schedules plus her carrier account manager's email chain, took 40 to 60 minutes to assemble. Her CEO asked when she would automate it. Her CFO wanted a project44 quote.
That gap between what the operations team knows and what leadership can query in real time is where supply chain visibility platforms earn their keep in 2026. This article is a candid buyer's guide. What visibility actually means. The vendor landscape. Where data feed complexity really lives. Real cost bands. And when custom pays back over off-the-shelf.
What Supply Chain Visibility Actually Means in 2026
Four capability layers.
Real-time location and ETA. GPS location, vessel position, aircraft tracking. Predicted arrival time based on real conditions (traffic, weather, port congestion). Refreshed at 5 to 15 minute intervals for surface transport, per-segment for ocean and air.
Exception detection and alerting. Late departure, off-route detection, dwell time exceeded, temperature excursion for cold chain, missed handoff. Configurable rules per shipment class and per client.
Multi-modal event matching. A container arrives at Rotterdam, transfers to truck, delivers to warehouse. Three events, three data sources, one physical journey. Matching these into a coherent shipment lifecycle is where most visibility programmes actually spend engineering time.
Historical analytics. Carrier performance, lane reliability, dwell benchmarks, exception patterns. Feeds procurement, planning, and continuous improvement.
Vendor demos show layer 1 and 2 beautifully. Layer 3 (multi-modal matching) is where the money goes. Layer 4 (analytics) is what proves the programme worked.
The 2026 Vendor Landscape: project44, FourKites, Custom
Real-time transportation visibility. project44, FourKites, Shipwell, Descartes MacroPoint. Best for over-the-road (truckload and LTL) visibility with carrier telematics ingestion. Priced $150k to $800k annually for mid-market shippers depending on shipment volume.
Multi-modal. project44 (bolstered by Ocean Insights acquisition), CargoWise, FreightWaves. Best for shippers moving across truck, ocean, air, and rail with unified visibility needed. Priced $500k to $2m+ annually for larger enterprises.
Manufacturing and inventory visibility. SAP IBP, Oracle SCM, Blue Yonder Luminate. Best for organisations already deep in the parent ERP or supply chain platform. Bundled pricing into broader contracts.
Custom builds. Direct integration to carrier APIs and data sources with your own event matching and analytics layer. Defensible in specific scenarios covered below.
According to Gartner's supply chain research, the RTV market has matured meaningfully. The gap between vendor demos and production reality has narrowed. Custom is no longer the default for enterprise shippers; it is a considered choice.
Data Feed Complexity: The Real Killer
Where the cost actually lives.
Carrier ELD and telematics feeds. US carriers standardised on ELD mandate. Hundreds of ELD providers, most with API access, subtly different data models. UK carriers on FORS or similar. Integration effort: 2 to 6 weeks per major carrier, less for those already on RTV networks.
Ocean carrier feeds. 20+ major ocean carriers, each with their own API and event model. Standardisation via UN/CEFACT and DCSA has helped but not eliminated variability. Integration effort: 4 to 8 weeks per major carrier.
Air freight tracking. Primarily EDI (Cargo-IMP) with real-time exceptions via API for major carriers. Airport ground-handling systems add complexity. Integration effort: 6 to 10 weeks per major carrier.
Yard and warehouse integration. Dock scheduling, yard management, WMS event feeds. Each customer's system different. Integration effort: 2 to 5 weeks per site.
For a shipper with 15 carrier integrations spanning all four categories, expect 30 to 60 percent of programme effort on data ingestion. Vendor demos rarely reflect this. Custom builds under-quote it by 40 to 60 percent when scoped by anyone who has not shipped one before.
Real 2026 Cost Bands: Buy vs Build
Buy off-the-shelf.
project44 and FourKites: $150k to $800k annually for mid-market shippers
Multi-modal enterprise (project44 Ocean, CargoWise): $500k to $2m annually
Setup and onboarding: 3 to 6 months for RTV; 6 to 12 months for multi-modal enterprise
Custom build.
Proof of concept: £40k to £90k over 8 weeks (one carrier integration, basic ETA, single mode)
Pilot: £100k to £220k over 4 to 6 months (3 to 5 carriers, exception detection, basic dashboard)
Production: £250k to £600k over 8 to 14 months (multi-carrier, multi-modal, exception workflow, analytics)
Add £30k to £150k per year in ongoing platform run cost and maintenance. Add £2k to £10k monthly in data ingestion costs (carrier API subscriptions, cloud data processing) at scale.
Break-even for custom against SaaS lands at year two for shippers with high annual RTV spend. Below $500k annual SaaS spend, buy almost always wins on maths. Our earlier post on custom TMS development covers the adjacent transport management build.
When Custom Visibility Actually Pays Back
Four scenarios where custom earns its money.
15+ carrier integrations with unusual mapping. SaaS platforms cover the top 30 to 50 carriers well. Beyond that, custom mappings mount up. Above 15 unusual carriers, custom becomes attractive.
Above $500k annual SaaS spend. At this scale, 3-year TCO for a custom build ($800k to $1.5m all-in) becomes competitive with SaaS renewal cycles.
Unusual multi-modal complexity. Shippers moving across truck, ocean, air, and rail with proprietary event models, unusual documentation requirements, or specific regulatory needs. Custom builds this once and owns it.
Visibility as customer-facing product. Some shippers or 3PLs want to sell visibility data to their own customers as a differentiator. That requires owning the software.
Below any of these, off-the-shelf almost always wins. The World Economic Forum publications on supply chain resilience make clear that visibility is now table stakes rather than differentiation for most operations.
What We Learned Building TrackVid's Reconciliation Engine
TrackVid is our video proof and claim management platform. Two lessons from its reconciliation engine transfer directly to supply chain visibility builds.
Multi-source event matching is 40 percent of the code and 60 percent of the pain. In TrackVid we match marketplace events, carrier events, and seller-dispatched events into a single canonical order lifecycle. Same problem shape as a visibility platform matching carrier events, port events, yard events, and warehouse events into one shipment lifecycle. Underestimate this at your peril.
API contracts break at the worst time. Carrier tracking endpoints and port data APIs each fail at least twice a year. In TrackVid we built proper monitoring, alerting, and automated fallback around every external integration. Visibility platforms need the same discipline. This is what determines whether your board's Monday question can be answered on Monday.
You can see TrackVid at our portfolio. If you want to talk about a visibility build for your specific operation, book a visibility platform call with WhiteStone.
Common Failure Modes
Three failure modes we see repeatedly.
Buying visibility SaaS without carrier commitments. Platform bought. Half your carriers do not integrate cleanly. Coverage gaps everywhere. Programme fails.
Under-scoping data ingestion effort. Consultant quotes 20 percent of effort for integration. Real requirement is 50 to 60 percent. Programme runs over budget by month six.
Building dashboards before proving data quality. Ops team sees pretty maps but underlying data is unreliable. Trust collapses. Nobody uses the system.
Frequently Asked Questions
project44 or FourKites vs build custom: how do we decide?
Under $500k annual visibility spend or fewer than 15 carrier integrations: SaaS wins on maths. Above $500k and 15+ carriers with unusual mapping: run 3-year TCO comparison. Multi-modal enterprise (ocean, air, rail plus truck) often tips toward custom due to per-mode integration cost.
What data feeds are the biggest headache?
Ocean carrier feeds (20+ carriers each with different APIs) and air freight EDI (CargoIMP with exceptions). Both take 6 to 10 weeks per major carrier to integrate cleanly. Yard management integrations often surprise on complexity because they involve customer sites with legacy systems.
How do we prove ROI on visibility investment?
Track dwell time reduction (typically 15 to 30 percent achievable), exception resolution time (30 to 50 percent reduction), on-time delivery rate improvement (5 to 12 percentage points), and customer service cost reduction (20 to 40 percent). Baseline these before rollout. Programmes that fail ROI conversations usually never baselined.
How long does a visibility platform rollout take?
SaaS: 3 to 6 months for RTV, 6 to 12 months for multi-modal enterprise, plus 3 to 6 months to fully embed with ops. Custom: 8 to 14 months from kickoff to production, plus 3 to 6 months for optimisation and analytics maturity.
Should visibility be a customer-facing feature?
For 3PLs and shippers-to-shippers relationships, increasingly yes. Customers now expect real-time shipment visibility via portal or API. If you differentiate on service, exposing your visibility platform to customers is a strong retention lever. Design for this from the start if it fits your business model.
The One Thing to Remember
Supply chain visibility platforms live or die on data feed integration quality. The dashboard is 20 percent of the work. Multi-source event matching, carrier API reliability, and exception logic are the other 80 percent. Programmes that scope this correctly ship on time. Programmes that budget as if it were a dashboard project run 40 to 80 percent over budget by month eight.
If you want a candid conversation about visibility for your specific operation, browse our custom software development services or come to the scoping call.
