PRODUCT ENGINEERING / CONNECTED BUSINESS SYSTEMS
Omnistu Global - Everything ConnectedStart a project

Engagement scope - proposed scope

Choosing a White Label Travel Portal Provider: Four Routes, Compared

This page describes proposed scope for a build in this category, agreed in writing per project. Nothing here is a finished product, a fixed bundle or a fixed price.

Scope areas for this kind of build

Typical scoping questions

Whose name is on the supplier contracts?

  • Yours. A provider that offers live flights and rooms with nothing for you to sign is lending you its own account, and the terms of that loan set your margin and your exit.

Who owns the source and the database?

  • Ask for the repository and the traveler records by name. A licence to use software is not ownership, and the gap becomes obvious the first time you want to change a checkout step.

What happens the day you stop paying?

  • With a rental, the site and often the customer list go dark with the invoice. With a platform you own, you carry on with a hosting bill and nothing else. Get the answer in writing.

Is there an accounting or mid-office module?

  • Ours has none, and we say so. What exists is bookings with margin and refunds, agent and vendor settlements, wallet balances and exportable reports. Full accounting is a quoted extra.

Can agents recruit sub-agents or set their own markup?

  • Not in an initial scope here. An agent tier with a fixed commission and a credit-limited wallet is included, and anything deeper is scoped work. Beware a provider who says yes to everything.

What if payment clears and the supplier does not confirm?

  • The traveler should be refunded automatically, with no ticket and no waiting. If the answer involves a person in your support team, picture it happening on your busiest weekend.

Where is the list of what is not included?

  • A quote with no exclusions was not costed. Our list sits on this page, and it names the channel manager sync, repricing, sub-agents and more, so nothing turns up as a surprise later.

The Six-Step Delivery Process

What happens after you say yes, day by day.

Your brand, everywhere at once

  • Logo, colors, name and domain applied to the traveler site, both mobile apps, the agent, corporate and vendor portals and the console. Categories you are not ready for stay switched off, and can be turned on from the console later without a release.

Write the commercial rules

  • Margin as a percentage, a flat fee and a minimum for each category. Agent commission, vendor commission, payment method fees, cancellation terms, loyalty tiers, cashback, corporate plans, and your team invited with the permissions each job needs.

Walk it end to end, then hand over

  • You book as a traveler and see the same booking, with its margin, in the console. An agent books for a client and the commission posts. A trip above policy waits in the corporate approval queue. Finally the finance login clears a refund, the path most demos quietly skip.

Support you can plan around

  • Day zero is the one to respect. A finished platform with no approved supplier account is still a portal that cannot sell a real ticket, and no provider can shorten a supplier's own review.

Red Flags That Mean Walk Away

Five claims that should end a sales call

  • "Live inventory is included, no contracts needed." Somebody holds those contracts, and it is not you. Your margin, your data and your continuity all belong to whoever does. Read that arrangement as the real product being sold.
  • "You get a licence, the code stays with us." Then every change you want is a favor you request. A portal you cannot alter is a rented storefront with your logo on it.
  • "Traveler data is stored on our servers." Passports, phone numbers and trip history are the asset you are building. Confirm where they live and how you would export them before you take a single booking.
  • "We guarantee the best fares." Fares come from suppliers and move by the minute. Nobody selling software controls that, so nobody honest promises it.

What a Travel Portal Has to Get Right

The unglamorous parts that never appear in a screenshot and decide whether the business survives peak season.

What We Have Not Done Yet

Six limits, put in front of you before the purchase and not after it.

There is no mid-office or accounting module

  • No ledger, no invoicing suite, no back-office accounting. What you get is bookings with payment, margin, refunds and cancellations, agent and vendor settlements with monthly statements, wallet and gift-card balances, and exportable revenue and margin reports. Accounting integration is custom work.

No certificate, no fare or uptime guarantee

  • The platform is built with role-based access, audit logging and encrypted secrets, the controls an assessor looks for. That is not a certificate, and certification audits your operation rather than our code. Fares and uptime depend on your suppliers and your hosting, so we quote neither.

Larger integrations are scoped, not assumed

  • Two-way channel manager sync, demand-based repricing, single sign-on and HR or ERP links, several brands on one core, extra currencies and languages, marketing automation, a B2B holiday package builder and further supplier connections. Each is priced against your plan before work starts.

What exists is real

  • Eight categories, pay-then-book checkout with automatic refunds, supplier fallback, per-category margins, agent, corporate and vendor portals, wallet, gift cards, five loyalty tiers, nine roles and twenty-four permissions, and two-factor sign-in for operators.
  • This is an original implementation on NestJS, React and React Native. No travel brand is a supplier, partner or reference customer of it, and none is implied anywhere on this page.

Modelled Reference Deployment

An illustration, not a client story. It shows how the platform would be configured for a tour operator that already holds its own supplier contracts. Every number describes the build and none reports a result.

A Tour Operator Selling Its Own Contracts Online

  • A regional tour operator in India with a hotel wholesaler account, bus partners and a portfolio of local homestays and activities, selling by phone today and wanting one branded channel for travelers, agents and vendors.
  • The situation: supplier relationships built over years but no online channel to sell them through, a rented portal that would cap the margin on those very contracts, and local hosts and guides who would list directly if they had somewhere to do it.
  • The configuration: the operator's own hotel and bus accounts connected as primary suppliers, its homestays, activities and packages listed directly, and agents booking for their clients with commission posted automatically. Categories it does not sell stay switched off.
  • What is already in an initial scope: pay-then-book checkout with wallet, promo codes and gift cards, the agent portal with client records and monthly settlements, the vendor extranet with rates and availability, and per-category margins with loyalty tiers managed from the console.

Choose on the answers, not the pitch

Omnistu is an independent software development project. We are not affiliated with, connected to, sponsored by, or endorsed by MakeMyTrip , or any other travel booking, online travel agency or travel portal service.

White label travel portal describes a category of product, not any one company. Brand names appear elsewhere on this site only to describe the kind of platform being built and the terms buyers search for.

Discuss this scope by message

Tell us your market and audience, and we will respond with a practical read on scope.

team@omnistu.com