Sleeper Rail Booking Software — Built for Overnight Trains, Cabins, and Departures
Above the fold: Run your entire overnight sleeper-rail operation on one platform. Compartment-by-compartment selection at booking, berth-by-berth inventory across the carriage layout, departure-board scheduling built for multi-night services, channel control across direct sales and specialist rail-holiday agents, QR boarding at the platform, live manifest. Built by operators who got tired of running their systems instead of running their service.
The real problem with most sleeper-rail booking platforms
A guest books a two-night journey on the website. The twin-sleeper compartment they wanted is listed as available, but the channel manager hasn't synced since lunch, so the berth is actually gone — sold an hour earlier through a rail-holiday agent. Meanwhile, the manifest the train manager is using at the platform is out of date because the boarding system hasn't synced with reservations since yesterday. An agent calls asking whether the premium compartment is still being held back for direct bookings; nobody can confirm without opening three tabs.
Peak season is on. A section of track has closed for emergency engineering work, the route has been replanned, and every guest booked on the affected departure needs to be told what's changing. The reservations team finds out about the oversold compartment only when the guest emails asking why their confirmation never arrived.
Overnight sleeper-rail is not a day-train ticket. A sleeper compartment is not a hotel room. A multi-night service is not a flat seat count. Compartment categories, berth counts within each compartment, single-supplement rules, carriage layouts the guest can browse at booking, themed multi-day journeys, maintenance windows that take rolling stock out of service, charter switches that lift entire departures out of the public catalogue, intermediate-station boardings where a passenger joins mid-route — none of that fits into a calendar widget with a "book now" button.
A sleeper-rail booking platform that can't model that is just a payment form attached to a spreadsheet. It works until the second compartment category sells out. (The hidden economics of accommodated transport operations →)
What JetSetGo does for sleeper-rail operators
Compartment-by-compartment selection that closes the booking
Guests pick the specific compartment they want, on a real carriage layout, with available compartments highlighted by category, carriage, accessibility, and adjoining-compartment rules. Single supplements, twin-share rules, family-compartment combinations, and travel-companion linking are configurable per departure. Accessible-compartment holds, premium-category holds, and direct-channel exclusivity rules apply automatically. The booking flow converts because it shows the guest what they're actually buying — not a category and a hope.
Scheduling built for how overnight rail actually runs
Each departure is a real product, not a date entry on a calendar widget. Departures carry their own season, route, compartment allocation, crew roster, and pricing band. Maintenance windows take individual carriages or whole rakes out of service without breaking forward bookings. Themed multi-day journeys price independently from regular weekly services on the same route. Charter switches lift entire departures out of the public catalogue without disturbing the rest of the season. Multi-route operators run parallel services on shared rolling stock without inventory leaking between them.
The departure-board view is one screen. The 12-month rotation is one table. Adjustments update across direct, agent, and online-distribution channels in the same second.
The travel-agent network, managed properly
Overnight sleeper-rail depends on specialist agents and rail-holiday packagers. JetSetGo was built knowing that. Agents log in to their own portal, see only the compartments and price tiers you have exposed to them, book with their commission rules already applied, and their bookings flow into your manifest the moment they confirm.
Cap each agent's allocation per departure. Hold premium compartments for direct bookings until a set window. Release unsold allocations back to general inventory at a configurable date. Reconcile and pay commissions in one run, not a spreadsheet exercise. The relationships with rail-specialty agents and the consortium distribution network stay — the operational friction does not.
Compartment inventory the platform actually understands
A rake is modelled the way it actually sells. Compartment categories — premium compartment, twin sleeper, single sleeper, family compartment, accessible compartment — each with the individual compartments inside them, each compartment with its berth count, single-supplement rate, accessibility attributes, and adjoining relationships. Public spaces with their own capacity caps for dining seatings, lounge-car bookings, and on-board activities. Each level allocates independently when a booking comes in. A premium category sells before a twin-sleeper category at the same price tier. A family compartment sells as a triple plus a single, or as two adjoining twins, depending on how the operator has set the rules. An accessible compartment holds its allocation until 30 days out, then opens to general inventory.
Boarding, manifest, and on-board operations
The manifest is live to the train manager, the on-board crew, and the shoreside office at the same time. QR ticket scanning at the platform with cryptographic validation — no screenshot reuse, no clipboard reconciliation at end of boarding. Mid-route boardings handled correctly: a passenger joining at an intermediate station is on the manifest, their compartment is held empty until they arrive, and the crew sees who is expected at each stop down the line. Late-arrival check-in updates the compartment assignment in the same second. Dietary requirements, travel-companion groupings, and accessibility needs flow from booking to platform to dining service to the crew member responsible for the compartment.
On-board POS for incidentals — the lounge car, the bar, the dining service, optional onward-transfer add-ons booked en route. Charges post to the guest's compartment account; settlement at the end of the journey is a single transaction, not a stack of paper receipts.
Disruption you can manage in minutes
Track closures, weather, mechanical, signal failures, planned engineering works — when something disrupts a departure, mass-comms go out to every affected guest in seconds. SMS and email with the revised schedule, the new arrangements, and a rebook-or-refund link in the same message. Onward-connection bookings tied to a cancelled service refund or transfer in the same workflow. The manifest updates as guests confirm new arrangements. The reservations team stops being the disruption call centre.
Reporting, compliance, and customer ownership
Passenger manifests for rail regulators and safety authorities. Financial reports that match the accounting system. Agent-commission statements per period, per agent, per departure. Audit trails for insurance claims and probity reviews. Every booking, payment, modification, refund, compartment assignment, and on-board transaction logged with timestamp, departure, route sector, and payment trail — generated from one underlying dataset, not stitched together from three.
The customer database is yours. It builds with every booking — direct, agent, online channel — and every on-board transaction. Repeat-guest journeys (return overnight services, themed multi-day journeys, annual signature departures) earn their next-season bookings from that data, not by paying a third-party platform to reach your own past guests.
Flexible pricing — priced the way you actually sell
Sleeper-rail pricing rarely fits a single model. JetSetGo lets you price per compartment, per person, per berth, per route sector if your operation prices that way, as a fixed rate per departure, or as any combination — set per departure, per route, per season, or per compartment category. The same rules support single supplements, share-with-stranger berth rates, premium-compartment surcharges, dining-service add-ons, and lounge-car or beverage packages bundled into the headline price.
Versioned price lists switch automatically by date — peak season, shoulder, off-peak, themed journeys, charter periods. Set them once; the platform applies the right one on the right day.
A visual business rules engine handles everything that does not fit a flat tariff:
- "10% off when booking more than 90 days ahead"
- "Single supplement waived on selected shoulder-season departures"
- "Loyalty discount for return guests — second journey of the year at the early-bird rate"
- "Family rate when booking two compartments together"
- "Hold the premium compartments for direct bookings until 60 days out, then release to agents"
- "Promo code applies to selected routes only"
Rules apply automatically at the point of booking. The agent or the direct customer sees the right price; the operator sees it first.
One inventory, every channel
Website. Agent portal. Mobile POS at the platform and the ticket office. API integrations with downstream systems. Online-distribution connectors for the major rail-holiday channels. Phone bookings logged by the reservations team.
All of them drawing from one inventory pool. All of them respecting the channel rules the operator sets. All of them updated in the same second when a sale closes anywhere.
This is the part that "just a booking widget" cannot do. Compartment inventory is one thing, but compartment inventory managed across six different channels with different rules and different price tiers, across multiple services that share rolling stock, is what makes peak season survivable. (Peak season capacity management: mathematical models that actually work →)
What this looks like for real sleeper-rail operators
A named overnight service operator running a fixed route weekly, two nights end-to-end. Compartment categories sell at different rates by carriage, with single supplements configurable per departure. The booking flow shows the carriage layout so guests pick their specific compartment, not just a category. Specialist rail-holiday agents take a meaningful share of bookings; the direct channel holds the premium category until 90 days out. The platform models each departure independently — a peak-season service and a shoulder-season service on the same route get their own price bands and their own cancellation policies.
A luxury themed-journey operator running multi-day signature departures with curated on-board programmes. Compartments sold as cabins — single occupancy and twin occupancy priced separately, with strong direct-channel emphasis. Themed seasonal journeys — heritage routes, culinary itineraries, signature winter departures — share the rolling stock across the year, each with their own pricing band, their own included on-board programme, and their own deposit-then-balance payment schedule that the long-lead bookings demand.
A multi-route operator running several overnight services on shared rolling stock. The platform tracks which rake is allocated to which service in which season, so a carriage taken out for refurbishment removes the right number of compartments from the right departures, in the right order, without anyone manually patching a spreadsheet. Charter requests for whole rakes or individual carriages can be quoted, accepted, and lifted out of the public catalogue in minutes.
A sleeper-rail operator with strong agent distribution taking a majority of bookings through specialist rail-holiday packagers and consortium networks. Each agent group has its own allocation, its own commission rate, its own price tier, and its own release rules. Reconciliation runs in one pass at month end, not as a spreadsheet exercise across multiple inboxes. The direct channel still owns its slice — premium compartments held back, loyalty rates protected — and the agent network sees only what the operator has chosen to expose.
Frequently asked
Can guests choose their specific compartment at booking? Yes. The booking flow shows the carriage layout, with available compartments highlighted by category, accessibility, and adjoining-compartment rules. Guests book the compartment, not just the category. Operator-defined rules govern things like holding accessible compartments until 30 days out, blocking single bookings on family-compartment categories, and reserving premium compartments for direct bookings.
How does it handle mid-route boardings at intermediate stations? Properly. A passenger booked to join the service at an intermediate station is on the manifest from the moment they confirm. Their compartment is held empty until they arrive, the crew sees who is expected at each stop, and the QR scan at the boarding platform validates the ticket the same way it would at the origin. Late-arrival handling, dietary requirements, and accessibility needs travel with the booking record.
Can I keep selling through specialist rail-holiday agents and consortium networks? Yes. The platform connects to agent portals and the major rail-distribution channels. The difference is that you set the rules — cap how much capacity each channel can sell, hold premium compartment categories for direct bookings, decide which price tiers each channel sees. Most operators keep agents and consortium networks as distribution channels and use the channel rules to shift more revenue toward direct bookings over time.
What happens if the route is closed by engineering works or a track incident? The disruption notice goes out to every guest booked on the affected departure — SMS and email, with the revised schedule and a rebook-or-refund link in the same message. Onward-connection bookings tied to the cancelled service refund or transfer in the same workflow. The manifest updates automatically when guests confirm new arrangements.
Can I run multiple overnight services on shared rolling stock? Yes. The platform models which rake is allocated to which service in which season. When a carriage comes out for maintenance, the right compartments are removed from the right departures. When a charter is accepted, the relevant rake is lifted out of the public catalogue for the relevant dates only. Multi-route operators run parallel services without inventory leaking between them.
What if I outgrow you? Your data is yours — exportable at any time, in full, no lockout.
Run your sleeper-rail service the way it actually runs
The rake, the carriage, the compartment, the route, the departure, the manifest, the advance booking, the agent channel, the on-board POS for incidentals, the engineering-works call — all on one platform. With one inventory pool. With pricing rules that respect what your operation actually does.
Cancel anytime. You own your data.
See also: cruise booking platform (the sister pillar for accommodated multi-night cruise operations) — multi-modal booking platform (when you run sleeper-rail + onward transfers + accommodation as one operation) — bus & coach booking software (for the surface-transport side of the business).