A B2B travel portal for your agent network, or a B2C site for travellers — both built on live GDS and supplier feeds. Real-time flight and hotel search, agent logins and wallets, markup and commission rules, payments that hold and release correctly, and an admin panel your team can actually run. Not a template: a live multi-GDS platform already runs in production. Remote, worldwide.
A travel portal is an integration problem wearing a website — the screens are the easy part. Each icon below is a real part of the system, with the hard parts done right.
A portal for your agent and sub-agent network: individual logins, credit wallets, per-agent markup and commission, roles and reporting — the exact operations layer I already run in production.
A public-facing site for travellers to search, compare, book and pay for flights and hotels — fast, mobile-first, and ready for search engines out of the box.
Live flight and hotel content pulled straight from the GDS. I connect the API, handle the SOAP/REST quirks, and normalise every supplier into one clean set of results.
One engine, many branded fronts — hand each partner or sub-brand their own themed portal while you keep a single back office and supplier connection.
Beyond the GDS — direct hotel aggregators and bed banks (Hotelbeds, TBO and similar), merged into the same search with deduping and failover.
Agent credit wallets, top-ups, markup and commission rules, multi-currency, and payment gateways wired so a booking is never charged twice or lost.
Whether you're starting fresh, switching GDS, or rescuing a half-finished portal, tell me what you've got. I'll tell you honestly what it takes — no jargon, no pressure.
The parts nobody demos are the parts that matter. Whether it's B2B or B2C, every build ships with the hard, unglamorous pieces that make a booking correct, paid for, and honoured.
Travel portals are where generic developers get expensive — they discover the edge cases live, after launch, at your cost. I've already met them:
B2B, B2C or both. Which GDS and suppliers, which markets, which currencies. We name what's in — and what isn't — so the quote is honest.
The search flow, the money flow, the agent/wallet model and the data model — agreed before a line of code, because this is where cost hides.
Connect Amadeus / Sabre / Travelport and hotel APIs, normalise their data, and build search, booking and payment with previews as we go.
Price drift, timeouts, failed payments, refunds, wallet balances and supplier outages — not just the happy path.
Deploy, monitor real bookings, and stay on to add suppliers, agents and features as you grow.
Write-ups and the related service page that show how I approach travel platforms — the architecture, and the honest cost.
How one portal talks to Amadeus, Sabre, Travelport and direct feeds at once — normalisation, fan-out search, price drift, failover and refunds.
The levers that actually set the price — suppliers, search, money movement and the edge cases — so you can size your own build.
The reservation engine underneath the portal — flight, hotel, tour and appointment booking with payments, refunds and an admin panel.
Tell me who books through it and which GDS or suppliers you need — a rough idea is enough. You'll get an honest scope and a clear quote, with no pressure.