What you will learn
- How wagon scans and yard events become a consignment story
- What shippers, terminals and railway staff each see
- How delays and exceptions are shown without hiding them
- What tracking can and cannot promise about arrival times
- Where tracking ends and freight booking begins
What this project is
A consignment moves through a chain of events: loaded, departed, arrived at a yard, shunted, departed again, arrived at destination, unloaded. A tracking portal collects those events from yard scans, wagon reports and terminal systems, and presents them in the order a shipper understands: what has happened, where the consignment is now, and what is due next. Without that chain, a shipper's only source of truth is a phone call to someone who may not know either.
The portal's value is in exceptions. A consignment moving normally needs little attention; a consignment stuck at a yard for two days, or diverted onto another route, needs attention immediately. The portal should surface stuck and delayed consignments first, with the last known event and the time since it happened, so a shipper or railway planner can act before the customer asks why nothing has moved.
Core features
- Consignment tracking by booking reference, wagon number or container number
- Event timelines showing loading, departures, yard arrivals and unloading in order
- Exception views for consignments that have not moved within the expected window
- Estimated arrival based on the current position and the remaining route, with uncertainty shown
- Notifications for key events: departure, arrival at destination, unloading and delay
- Document access for the consignment, such as loading notes and delivery confirmation
How it is built
- Identify the event sources first: yard scans, wagon feeds and terminal systems, and check how complete they are on real routes
- Build the event timeline and consignment lookup, then the exception views that surface stuck consignments
- Add estimated arrival and notifications, with controls so shippers choose which events they hear about
- Give terminals a view of consignments due to arrive, so tracking helps the yard as well as the shipper
- Pilot on one lane, checking tracked events against what actually happened at each yard
Technology considerations
Event data is rarely clean. Scans are missed, wagon numbers are misread, and a consignment may be split across wagons. The system should handle partial data gracefully: show the events it has, mark the gaps, and never invent a position. Consignment identity needs care too: a booking, a wagon and a container are three different things, and the portal must link them correctly or it will show a shipper someone else's goods.
Access control is straightforward but important: a shipper sees its own consignments, not its competitors'. Estimated arrival should be based on the remaining route and recent performance on that route, and it should widen when the consignment is stuck, rather than holding a precise date that the data no longer supports.
For the first version, focus on the event timeline and the exception view, and leave advanced analytics for later. Shippers judge the portal on two things: whether the timeline matches what the terminal tells them on the phone, and whether a stuck consignment is flagged before they ask about it. A portal that does those two things well, on one lane, is more useful than a portal that promises full network visibility and shows unreliable data on every lane.
Challenges to plan for
- Missed yard scans that leave a consignment apparently frozen for days
- Consignments split across wagons, where part of the load arrives and part does not
- Yard events that arrive out of order, making the timeline read backwards
- Shippers who check once and never return, because the portal only shows the past and not what happens next
Who it is for, and its limits
This suits a railway freight operator, a terminal operator or a logistics provider that moves goods by rail. It fits where consignments pass through several yards and where shippers need visibility without calling. It does not fit a shipper moving a single wagon on a single direct service, and it is not a booking system: it tracks consignments already booked, it does not create bookings.
A tracking portal does not move freight faster, and it cannot show events that no system records. Where yard scanning is patchy, the portal should say so rather than presenting gaps as smooth movement. Costs vary with the number of yards and event sources, so confirm with a quote after the event sources are mapped.
Frequently asked questions
How do I find my consignment?
By booking reference, wagon number or container number. The portal shows the consignment's event timeline, current location and what is due next, in that order.
Why has my consignment not moved?
The timeline shows the last recorded event and how long ago it was. If the gap exceeds the expected window for that leg, the consignment appears in the exception view for railway staff to investigate.
How accurate is the estimated arrival?
It is based on the current position and the remaining route. When the consignment is moving normally it is reasonably firm; when it is stuck, the estimate widens and says so.
Can I see documents for my consignment?
Yes, where the terminal or railway supplies them: loading notes, delivery confirmation and related paperwork are attached to the consignment record.
Does tracking cover road delivery beyond the terminal?
Only if the road leg is recorded in the same system. Otherwise the rail journey ends at terminal unloading, and the portal says so plainly.