Series fare
Contracted fares for a repeated group or series of departures, common in tour operations. Often managed with allotments and stricter release and name deadlines.
Series fares support repeated departures on the same routing (e.g. weekly tours). Contracts attach to a series identifier and often include an allotment of seats per departure with specific release and naming deadlines.
Compared with ad‑hoc groups, series flows emphasise templates: itinerary, rooms/seats, price rules and passenger data requirements reused across dates. Agents collect names progressively and the platform enforces deadlines and penalties.
Pricing and eligibility differ from public fares. Rules may restrict who can sell, which markets are valid, and how markups or commissions apply. Display must label series fares clearly to avoid mixing with public inventory.
Finance must track deposits, penalties and supplier statements per series and departure date. Orders should carry series and block identifiers so settlements and credit notes reconcile quickly.
In the Elkanio platform, Cluster organises series schedules and name collection, Nexus maintains the underlying contract and allotments, and Vector posts deposits, balances and penalties to the correct ledgers.
What teams often get wrong
-
Can names always be added after the deadline?
Usually not without penalties or loss of space. Enforce name and ticketing deadlines with visible clocks and alerts.
-
A sold‑out date can be oversold and fixed later.
Overselling a series departure leads to re‑accommodation and penalties. Respect allotment balance and stop‑sales at source.
Explore connected concepts
Prefer a walkthrough?
See how the products fit together and discuss your use cases in a live demo.