Operations · Pricing

Departures and programmes: how many prices can one flight have

Two passengers on the same aircraft can stay in different hotels and pay different amounts. Trying to model that as one record is the setup mistake agencies make most often.

Published · 2 min read

The first thing agencies stumble on when moving to new software is usually this: is a departure the same thing as a programme? It is not, and missing the difference turns into confusion halfway through the season.

A departure is a date; a programme is a package

The departure is a date range and a flight: 10–24 March, Ramadan Umrah. The aircraft, the group structure and the overall calendar belong to it.

The programme is the package inside that departure: which hotel, how many nights, what is included. The same departure can carry a "Premium" and an "Economy" programme.

Two passengers fly out together and return together, but one stays close to the Haram and the other further away, and they pay different amounts. Same departure, different programme.

Why one record cannot hold it

Opening each package as its own departure looks simpler at first. The problem appears on departure day: the flight manifest, the coach assignment and the airport roll-call all have to be one list.

Split across separate departures, those lists break apart and have to be merged by hand — group numbers, seat allocation, roll-call, all of it.

The opposite shortcut fails too: putting everyone in one record and handling the price difference manually. Then every passenger's balance is calculated separately and a room change never updates the amount.

What the correct setup gives you

Open the departure once and hang the programmes under it: the departure-day lists stay whole while the prices stay separate.

A passenger's balance follows from the programme they chose and the room type. When the room changes, so does the amount — nobody tracks it by hand.

Occupancy becomes visible per programme too. If the premium package fills while the economy one sits empty, you can see it weeks before departure and act on price or promotion.

Copying a programme shortens the season

The same programme repeats several times a season: a monthly Umrah departure, similar hotels, a similar price structure.

Entering it from scratch each time is slow and produces mistakes — a missing accommodation line, a room price left at last year's figure.

Copying and then updating dates and prices turns season setup from days into hours.

Capacity and quota are different things

Capacity is a physical limit: how many seats on the aircraft, how many beds in the hotel. Quota is the selling limit the agency sets for itself.

Confusing them produces two failures. Treating capacity as quota leads to overselling; treating quota as capacity means stopping while you could still sell.

Closing a programme is a third concept again: a closed programme takes no new registrations, but work on existing passengers continues.

Related modules

  • Operations and placement — One shell per tour: files, passengers, rooming, transport, finance and cost in the same place.
  • Collections and accounting — Multi-currency ledgers, instalment plans, cash and bank, and per-tour profitability. Exchange rates freeze at entry.

Terms mentioned

  • Quota — The maximum number of pilgrims a departure will accept.
  • Load factor — How much of a departure's quota has been sold.
  • Room type — How many people a room sleeps: SGL, DBL, TWN, TRP, QUAD.

Let's set it up together

Tell us how your tours, pricing and team are structured; we will show the demo on a setup that resembles your own data.