What you will learn
- What a freight booking contains beyond a passenger ticket
- How wagon allocation, loading windows and train capacity are planned
- What shippers, railway staff and terminals each need to see
- How pricing, invoicing and demurrage are handled
- Where freight booking stops and freight tracking begins
What this project is
Freight booking is about capacity, not seats. A shipper asks to move a quantity of goods, in a wagon type, from a loading point to a destination, within a window. The railway has to answer whether wagons of that type are available, whether the train has room, and what the loading and unloading slots look like. A booking system records that answer as a commitment both sides can plan around, rather than a conversation that lives in email.
The booking itself carries the commercial and operational detail: commodity, weight, wagon count and type, loading and unloading points, requested dates, and any special handling such as hazardous goods or temperature control. Once accepted, it drives wagon allocation, terminal planning and invoicing. A booking that only records the price, without the wagon and slot detail, leaves the operational work to be redone by hand at the yard.
Core features
- Booking requests with commodity, weight, wagon type and loading window, submitted by shippers and reviewed by railway staff
- Wagon allocation against available fleet, with substitution rules when the exact wagon type is short
- Train capacity planning that shows booked, available and reserved space per service
- Loading and unloading slot scheduling at terminals, so wagons do not arrive with nowhere to go
- Pricing, invoicing and credit handling tied to the booking, including extra charges for waiting time
- Status tracking from request through acceptance, loading, departure and delivery
How it is built
- Start with the commercial rules: wagon types, commodities the railway accepts, and how prices are set for each lane and wagon type
- Build the request and acceptance workflow, with clear states so a shipper always knows whether a booking is pending, accepted or refused
- Add wagon allocation and terminal slot planning, because those are where a booking becomes an operational plan
- Connect invoicing to the booking record, then add reporting on utilisation, refusal reasons and late loadings
- Pilot with one lane and a small set of regular shippers, then widen the wagon types and terminals in stages
Technology considerations
Freight data is messier than passenger data. Weights change at loading, wagon types get substituted, and a train may leave with a different consist than planned. The system should record what was planned and what actually happened, separately, so invoicing can be based on actuals while planning learns from the difference. Integration with yard and terminal systems matters more than a polished shipper portal: if the yard does not see the booking, the booking is just a form.
Access control needs care. A shipper should see only its own bookings and prices, while railway planners see the full picture. Pricing rules, especially contracted rates versus spot rates, should live in one place and be versioned, so an old booking can always be repriced from the rules that applied when it was made.
Challenges to plan for
- Wagon shortages on a busy lane, and deciding fairly which bookings get wagons first
- Late loading that cascades into missed departures and wagons stuck at terminals
- Hazardous or oversized loads that need approvals the booking flow must not skip
- Reconciling planned versus actual weight and wagon count at invoicing time
Who it is for, and its limits
This suits a railway freight operator, a private wagon owner, or a large shipper that books regular rail capacity. It fits where freight moves on scheduled services with real wagon constraints. It does not fit a road haulier, and it does not replace a full yard management system: booking decides what moves, the yard decides how it is shunted and loaded.
A booking system does not create wagons or track capacity. It also does not handle customs, road delivery beyond the terminal, or cargo insurance. Costs vary with the number of lanes, wagon types and terminal integrations, so confirm with a quote once those are mapped.
Frequently asked questions
How is freight priced in the system?
From rate tables by lane, wagon type and commodity, with contracted rates overriding spot rates for named customers. Extra charges for waiting time or extra handling are recorded against the booking, not added as a surprise invoice later.
What happens if the requested wagon type is unavailable?
The system can offer a substitution or a later service, but it should not silently swap wagon types. The shipper accepts or declines the alternative, and that decision is recorded.
Can a shipper change a booking after acceptance?
Within limits, yes: dates and quantities can change if capacity allows, and the price is recalculated from the rules in force. Changes after loading starts need railway approval, because wagons and slots are already committed.
Does this track the goods in transit?
It tracks booking status, not live wagon position. Live tracking needs a separate feed from wagon sensors or yard scans, which can be shown alongside the booking but is a different system.
What is demurrage in this context?
A charge for wagons held beyond the agreed loading or unloading window. The system records the agreed window and the actual times, so the charge is calculated from facts both sides can see.