Private fares next to GDS content: load your own airline and hotel contracts

The real problem is not “having contracts”

You already have the contracts. The problem is that they rarely behave like inventory. A consolidator deal arrives as a PDF or ATPCO filing note. A hotel chain sends seasons, blackouts and child policies in a spreadsheet. Series fares for a tour programme sit with allotment balances that change weekly. Agents who know the deal exists still quote from public GDS or bedbank rates because the contract is slower to find than a search click.

Finance then reconstructs what was sold from chat threads and invoice exceptions. That is not a content problem; it is a loading and enforcement problem. Until the contract is structured as rules the booking engine can price and restrict, private fares management stays a tribal skill instead of a product capability.

What “beside public content” actually means

Beside means the same search, the same offer shape and the same order model. An agent requests availability once. Results include GDS, NDC, LCC and your contracted airline fares or hotel rates, each labelled by source. Eligibility, markup and commission follow rules attached to the contract and the selling tier — not a separate login, and not a promise that “we will check the deal desk and come back”.

If a private fare wins on price or product, booking creates one order with the same traveller, payment and document fields as a public fare. Mid-office and statements do not need a special path because the source was your contract. That is the difference between a travel supplier extranet that feeds the platform and a side tool that never joins the ledger.

Private fares, series fares and hotel contracts — same idea, different terms

Airline private and negotiated fares need carrier, route, booking class, travel and sales periods, fare rules, baggage, commission and validity. Series fare management adds allotments, release dates and name deadlines so tour departures do not oversell or miss penalties. Hotel, transfer and activity contracts need seasons, occupancy and meal plans, cancellation terms and stop-sales that suppliers can update without filing a ticket with engineering.

The commercial language differs; the system requirement does not. Every contract must become a tariff the engine can evaluate at shop and enforce at book. When those terms stay in email, agents invent workarounds and finance inherits the exceptions.

Why emails and side portals fail at scale

A shared drive of fare sheets does not enforce eligibility. A supplier WhatsApp group does not stop an unauthorised sub-agent from quoting a net rate. A hotel extranet that never reaches your agent UI forces double entry. And every manual reload is another chance for the wrong season or an expired blackout to reach a customer.

Supplier mapping travel API work is what keeps aggregated feeds healthy; your own contracts need the same discipline without pretending every hotel or consolidator will ship an API. Commercial partners should update fares, rates, allotments and stop-sales through a secure web interface. Your platform should map those updates into the same schema as public content so Nucleus, Nova, Orbit and Synapse all see one catalogue.

What operators should demand from a supplier extranet

• Load airline private and consolidator fares with rules the engine enforces, not free-text notes agents must remember
• Load hotel and ground contracts with seasons, supplements, occupancy, cancellation and blackouts as structured terms
• Put private and public offers in one search with a clear source label
• Restrict visibility by agency tier, market and accreditation so deals do not leak
• Apply markup and commission as configuration per channel and tier
• Capture contract and commission references on the order so statements reconcile without reconstruction
• Let suppliers manage their own stop-sales and allotments without a developer in the loop
• Expose the same contracted content through your B2B portal and your unified API, not only one UI

Treat the checklist as product requirements, not demo theatre.

Where Nexus fits in the Elkanio suite

Elkanio Nexus is the travel supplier extranet in the Elkanio suite. It turns negotiated airline private fares, consolidator deals and contracted hotel/ground rates into structured tariffs — loaded without engineering — and exposes them beside aggregated content through Synapse. Agents sell in Nucleus with clear source labels and the right eligibility, markup and commission applied automatically.

Concretely, Nexus lets you: define airline private and negotiated fares by route, booking class, travel/sales windows and fare rules; manage series fare programmes with allotments, release periods and name deadlines; load hotel, transfer and activity contracts with seasons, occupancy, supplements, stop‑sales and blackouts; restrict visibility by agency tier, market and accreditation; and publish effective‑dated changes with an audit trail.

Everything lands in one schema across up to nine travel verticals. That keeps private fares management, series fare management and public content in one flow — one search, one order, one set of documents.

Reconciliation that matches by itself

Contracts should not require archaeology at month‑end. Nexus records the contract reference, commission base and calculated earnings on the same order you already use for public content. Mid‑office posts invoice and receipt events as you sell, so BSP/ARC, supplier statements and internal ledgers match more often on first pass.

For agency‑model flows, commission receivables carry the right references. For merchant flows, net vs sell, fees and taxes are explicit on documents. The result is fewer exceptions and statements finance can trust without rebuilding each line from emails.

Loading and supplier updates without engineering

Commercial teams and suppliers make the changes; the engine enforces them. In Nexus you add or edit a fare or hotel season in a web form, preview the effect, set an effective date and publish. Suppliers can maintain their own stop‑sales, blackout periods and allotment balances under your controls. No code deploys, no spreadsheet hunts.

Where an airline or partner still needs a filing or back‑office step, Nexus produces the same structured contract terms and references so your commercial contact can submit them accurately. Either way, the booking engine and API pick up the rules immediately after publish.

A practical loading sequence

Start with the contracts that already move volume. Pick one airline deal and one hotel or ground programme you sell every week. Load them with eligibility and travel periods correct, enable them for a pilot agency tier, and watch whether agents actually select the private offer when it wins. Wire the order into mid-office so commission and net treatment post without a manual journal. Only then expand series allotments and the long tail of smaller hotel contracts.

Measure success as fewer “let me check the contract” calls, fewer quote-to-book delays on deal routes, and statements that match without a month-end archaeology project. You do not need a vanity percentage of “private mix”; you need private fares next to GDS content that agents trust enough to sell.

Closing

Own contracts are only an advantage when they appear where agents already search. Load them as structured tariffs, sell them beside public content under one order model, and keep suppliers able to update stop-sales without engineering. That is private fares management as an operating system — not as a spreadsheet with better typography.

Related glossary terms