End-to-end visibility with intermodal: What good really looks like

If you manage intermodal freight in the UK, you already know visibility is harder to achieve than on a simple road move. Multiple modes, handoffs, and systems can quickly turn a clear plan into a blurred picture.

This article is for shippers who want to move beyond “good enough” tracking and understand what strong end-to-end freight visibility really looks like in intermodal, and how it can help them make better decisions every day.

An intermodal move naturally involves more players than a straightforward full-truckload run . A typical intermodal journey might include an origin warehouse, a local road leg to a rail terminal, the terminal in-gate, a rail operator, one or more inland depots, and a final delivery leg by road to your distribution centre or customer.

Each of those handoffs is a point where data can be delayed, translated, or lost. Data from each part of the move can sit in different systems (terminals, rail operators, and local carriers all using their own tools) which makes integration harder and leaves you piecing together the journey instead of seeing one clear, end-to-end view. Without that joined-up view, it becomes difficult to answer simple questions where your loads are and whether they’re on track.

When you don’t have a clear view of departures and arrivals, those blind spots quickly become operational challenges. They make it harder to plan labour and shifts with confidence, and leave customer service teams without clear, up-to-date information when customers ask where their shipment is.

Many shippers have built processes around “good enough” visibility – an approach that can work when volumes are low and networks are not under pressure. But as volumes grow and networks run closer to capacity, that approach becomes harder to sustain.

It often results in a more reactive operation. Teams find out about delays when they have already created a bottleneck, not when you could still reroute, rebook, or adjust. Over time, this can erode service levels and confidence, both internally and with your own customers.

To move beyond “good enough” tracking, it helps to be clear on the data you really need. There are a few core elements that should be in place before you can rely on your intermodal visibility day to day.

Strong intermodal freight visibility starts with well-defined shipment milestones. This might mean capturing events from pickup at your warehouse, through terminal in‑gate and rail departure, to arrival, out‑gate at the destination terminal, and final delivery at your site or customer.

Though it will vary by route and partner, what matters is that you have a consistent, door-to-door picture. This means having standardised event definitions across road and rail partners, where milestones are clearly defined and reliably captured. Then teams can see at a glance the status of shipments.

Milestones tell you what has happened; ETAs tell you what is likely to happen next. For logistics teams, accurate ETAs help shape decisions and are the basis for labour and dock planning, inventory moves, and customer promises. However, in intermodal, the difference between a static planned date and a dynamic ETA is critical.

Static dates are fixed once at booking. Dynamic ETAs adjust as new location data and event milestones come in, reflecting actual departures, dwell times, and progress. Good ETA performance does not mean perfection, but ETAs that stay close to reality, improve as shipments progress, and are reliable enough for your teams to plan around.

With hundreds or thousands of shipments on the move, nobody has time to manually check each one. That is where exception-based visibility comes in. Rather than asking your team to log into multiple portals each day, a good visibility setup will surface the loads that are late, at risk, or stuck at a particular milestone.

When exception alerts are set up well, they give your team the confidence to step in, and the freedom to focus on planning instead of constant monitoring

Once you know which events and ETAs you need, the next step is getting that data into the tools your teams already use.

To achieve the required level of intermodal visibility, you need more than a login to a portal. Freight visibility APIs allow providers to send shipment events, locations, and ETAs directly into your transport management system (TMS) or multimodal control tower. Data can update near real time, without manual file uploads or repeated copy-paste from different systems.

Portal access remains useful for occasional checks and deeper investigation, but an API-first approach gives intermodal visibility the speed and consistency it needs to support day-to-day decisions.

Connecting systems is only half the job. The data flowing through those connections needs to be consistent. If spelling is inconsistent, your systems may treat entries as separate locations. If timestamps arrive in different formats or time zones, your teams may see sequences that appear out of order.

Harmonising location names, time zones, event codes, and shipment identifiers across road, rail, and terminals is essential for providing a consistent journey view.

It is tempting to treat an integration as “done” once it is live. In reality, intermodal visibility improves when you and your providers commit to data quality over time. That means agreeing expectations on update frequency, understanding which events are mandatory, and having clear processes for handling errors and missing data.

The real value of end-to-end freight visibility comes when you use it to shape decisions.

With reliable intermodal shipment tracking, shippers can decide to pull forward replenishment to a particular Distribution Centre when a train is running ahead of schedule, or to rebalance stock between locations when a container is delayed at a terminal. You can also use visibility data to inform future network design, guide your routes and how you allocate volumes between modes.

Better visibility also changes how you communicate. When ETAs are credible and exceptions are surfaced early, you can update your own customers sooner and with more confidence. Internally, transport, warehousing, and customer service teams can work from the same view of the journey, rather than debating which spreadsheet or portal is most up to date.

Small improvements in visibility can make a noticeable difference. Knowing when shipments are due, and having confidence in those times, allows you to plan shifts, yard space, and equipment more accurately and efficiently. In practice, this can mean smoother days for teams on the ground, better use of people’s time, and less reliance on overtime or emergency cover.

The questions you ask at this stage can quickly reveal how robust a provider’s visibility really is.

When speaking to providers, dig into how their tracking actually works. Ask how often they update shipment data, and which parts of the journey they cover. Explore how they generate and measure ETA accuracy for intermodal moves, and how they share that performance with you over time.

It’s worth asking how they approach TMS or control tower integrations in practice. Discuss which systems they support, typical implementation timelines, and who does what on both sides. Good providers should be able to describe a clear support model, from initial setup through to ongoing maintenance and troubleshooting.

Clarify what data you will be able to access, in which formats, and how easily you can export or combine it with other sources. Ask how configurable the alerts, dashboards, and reports are, so you can align them with the way your teams actually work.

For a more reliable view of your intermodal freight visibility, Amazon Freight can help. Create your free shipper account today to get started.

Create free account