I build systems for travel agencies and tour operators: itinerary building and costing, vendor booking management, customer payment schedules, vendor payable reconciliation and per-trip profitability.
What is a packaged trip, operationally?
A dozen vendor bookings wearing one invoice. Hotels, transport, guides, permits, activities, flights — each with its own advance, its own balance, and its own cancellation terms on its own calendar. Currently that lives in a WhatsApp thread with the founder’s memory as the index.
Meanwhile the customer pays in instalments on a schedule that suits them, and vendors demand advances on schedules that suit them, and the gap between those two is funded out of working capital nobody is tracking. Whether the Kerala group tour actually made money is a question answered in vibes: season achha gaya — but by how much, and because of which departures?
What does the system cover?
- Itinerary and costing. Day-wise plans priced from vendor rate cards, so the quote’s margin is known before it is sent rather than after the trip returns.
- Vendor booking tracker. Every booking’s status, advance, balance and cancellation deadline. The deadline alarms alone tend to justify the system in one season.
- Customer ledger. Instalment schedules, receipts, and balance chasing that happens automatically before departure rather than awkwardly after.
- Vendor ledgers. Advances and settlements per hotel and transporter, reconciled at season end — which is when disagreements otherwise surface with no records to resolve them.
- Trip profit and loss. Quoted against actual per departure, with per-head economics on group tours.
Why per-departure economics matter more than seasonal totals
Because a season is an average of very different trips, and averages hide the two things worth knowing: which itineraries earn, and which specific costs blow up.
Almost every operator I have looked at has at least one popular package that loses money — usually a group tour where transport was quoted at last year’s rates, or a fixed-departure product where the guaranteed vehicle runs half-empty in shoulder months. It sells well, everyone likes it, and it is subsidised by something else. That is knowable within a season if each departure reports its own numbers, and unknowable forever if they do not.
The same applies to vendors: the hotel that gives the best rate but takes three follow-ups per settlement has a real cost that never appears in the rate card.
Recording that cost is not about punishing vendors; it is about knowing which relationships are actually cheap. The hotel two hundred rupees dearer that settles cleanly and holds rooms on a phone call is often the better commercial partner, and only per-trip records make that arguable rather than merely felt.
Related reading
/industries/hospitality — the properties you book into · /industries/logistics — the transport-side discipline · /products/whatsapp-automation — balance reminders and pre-travel confirmations · /services/fintech — the ledger discipline behind vendor settlement
Last season’s biggest group tour
Reconstruct its real margin — every vendor payment, every extra, every refund. If that is a shrug rather than a number, the next season is being planned on last season’s mood. /contact — safar aapka, hisaab system ka.
Questions I actually get
Do you integrate with a GDS for flights?
No, and I will say that plainly rather than implying otherwise. I build around your consolidator's output instead of pretending to be a flight distribution system. The value here is the trip's money and vendor truth, not another booking terminal.
Do you handle B2B subagents?
Yes — subagent rates, credit limits and ledgers, with statements they can read. Subagent disputes are almost always ledger disputes, and a ledger both sides can see settles them faster than any phone call.
How are cancellation deadlines handled?
As alarms against each vendor booking, because that is where real money is saved. A hotel cancellation window missed by one day is a full night's cost with no recourse, and in a busy season those get missed constantly.
Can it compute profit per departure?
Yes — quoted against actual, with per-head economics for group tours. Most operators know the season went well or badly; far fewer know which specific departures earned, which is the number that should shape next season's brochure.
Customer instalments?
Schedules with receipts and automated balance reminders before travel. Collecting the balance before departure rather than chasing it after is the single most valuable habit this system enforces.
Seasonal staff?
Trip-scoped access — assign for the season, settle, revoke. Nobody keeps standing access to your vendor rates and customer ledgers after their season ends.