Change my booking engine: operator playbook for agencies & consolidators

What “change booking engine” means for a B2B travel portal

Treat the target as a B2B travel booking platform, not only a search UI. One order model across channels, brand under your control, and distribution rules at book time — that is the difference between a pretty front end and a system operators can trust on Friday afternoon.

If today’s setup is a mix of supplier sites, side spreadsheets and a portal you outgrew, the change aims for one desk with labelled supply (GDS, NDC, LCC and your own contracts), markup and fee rules that calculate on the order, and documents and statements that mid‑office recognises without archaeology.

Whether you call it changing or switching your booking engine, the target should be a platform, not just a new skin.

Data migration for travel agency software

• Export current agency hierarchy, users and roles with IDs that map cleanly
• Migrate live credit/deposit balances and wallets; reconcile to statements before cut‑over
• Load active markup and fee rules with effective dates, not only “current values”
• Bring open orders and receivables/payables; keep older history read‑only
• Validate traveller/profile data needed for corporate programmes

You do not need to drag ten years of history into a new engine to go live safely. What you must carry is what the business will reference next month: active users and roles, the agency tree, live credit and deposits, current markup and fee rules, traveller profiles for ongoing accounts, open orders and open receivables/payables.

Plan a rolling horizon for orders and documents (e.g. current year), freeze the rest as read‑only in the legacy system or a warehouse. Publish an exact cut‑over window and reconcile balances before you open booking. Migration is successful when finance can close the first month without rebuilding numbers from chat threads.

Sub‑agent tiers, credit and markup continuity

• Master → sub‑agency → further tiers with inheritance and clear overrides
• Markup and fee rules by supplier/product/market/currency/tier with effective dates
• Agency credit wallet and deposits enforced at book; approvals for over‑limit
• Private content visible only to accredited tiers

A consolidator’s risk sits in tiers, markups and credit that drift from policy. The new portal — a booking engine for travel agents your network can trust — must enforce inheritance with explicit overrides: branding, pricing, eligibility and payment options cascade from parent to child unless changed. Credit and deposits must be authoritative at the moment of booking — not reconciled days later.

Supplier credentials: BYO — the platform is not your inventory seller

• Use your own supplier credentials; keep contracts and accreditation in your name
• Enable/disable per market and tier; label GDS/NDC/LCC/contracted sources
• Prefer configuration over bespoke connectors for each addition

Keep commercial independence clear: you enable suppliers you contract, with your own credentials and terms. The platform aggregates and normalises through Synapse; it does not become the merchant of record for your business.

Expect a capability model per supplier, label the source in results, and keep enablement a configuration change — not a connector project every quarter.

Mid‑office continuity (Vector) for a B2B travel portal

• Post invoices/receipts from the order; no re‑typing from screenshots
• Carry ticket, contract and commission references through to statements
• Match BSP/ARC and supplier statements from the same figures

Documents, tax and reconciliation should read from the same order the agent created. Vector‑class mid‑office posting — invoices, receipts, BSP/ARC matching and supplier statements — must follow automatically so finance does not maintain a second set of truths.

Success is month‑end that closes on first pass. That requires correct references (ticket numbers, contract IDs, commission base), explicit net vs sell, and currency handling that does not surprise later.

Go‑live sequencing you can defend

• Pilot scope: 5 routes, 1 partner tier, live finance in the room
• Parallel statements for the first month; measure exceptions, not vanity metrics
• Clear cut‑over plan with rollback; widen only after clean month‑end

Run a real pilot before you widen: one market, a small partner tier, live suppliers, mid‑office wired. Score outcomes by exception rate and reconciliation effort — not by slide‑deck promises.

Communicate a freeze window, reconcile wallets, run parallel statements for the pilot month, then expand. Keep a rollback switch, and prefer visible failures over silent mismatches.

Where Nucleus, Synapse and Vector fit

Nucleus is the B2B portal: white‑label desks, multi‑tier distribution, markup rules, credit and wallets. Synapse is the unified travel API and supply layer for GDS, NDC, LCC and your own contracts in one schema. Vector posts documents, tax and reconciliation from the same order data. Pulse can sit beside them for ticketing and traveller communication after go‑live when you want a support add‑on.

Further reading & next steps