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

Feature scope - proposed scope

White Label Travel Portal Features: Eight Categories, Five Audiences, One Platform Underneath

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

Feature Set by Role

The Traveler

  • Searches across flights, hotels, buses, trains, cabs, activities, holidays and homestays, narrows results with filters, chooses a seat, berth or room, and settles the whole basket in one payment, with wallet balance, a promo code or a gift card taken off first. Bookings, refunds, loyalty status and support tickets share one dashboard on iOS, Android and the web.

The Travel Agent

  • A desk for people who sell travel to their own customer base. They store client records, make a booking on a client's behalf, watch commission post to each booking, spend from a wallet with a credit ceiling you decide, and read monthly statements instead of chasing your accounts team.

The Corporate Travel Manager

  • Writes the travel policy: spend caps and cabin rules per traveler. A trip over the cap waits for a manager and then finance to sign off, an expense claim is prepared once the trip ends, and spend rolls up by department. The company pays for a plan, and your margin sits on every trip regardless.

The Operations Team

  • Works the console day to day: inventory for each category, the booking and user lists, promo codes and scheduled banners, the refund queue, vendor approvals, tickets and review moderation. Each admin action is recorded in an audit log, so you can always see who changed what.

The Owner and Finance

  • The owner login is where the business itself is configured: brand, live categories, the margin per category, visible payment methods, supplier routing and team permissions. The finance login clears refunds, approves agent and vendor settlements and exports margin reports, and is walled off from everything else.
  • Nine roles and twenty-four permissions are enforced on every single request. That is why an agent only ever sees their own customers, a vendor only their own listings, and a finance user cannot touch inventory.

From First Search to the Next Trip

Seven working stages of the booking engine, described the way the code behaves rather than the way a brochure would like.

The homepage is already selling

  • Before a single query is typed, visitors see the offers, banners and featured destinations you scheduled in the console. Registration takes an email, a one-time code or a Google account, and stored traveler profiles plus recent searches shorten every booking after the first.

Every supplier is asked at once

  • A category has one main supplier, backups, and sources used for comparison only. They are queried simultaneously and blended with the stays, activities and packages you added directly. A slow connection cannot hold up the results page, and filters cut by fare, timing, stops, star rating, amenities and guest score.

Money first, confirmation second

  • The server fixes the amount, checks the signature the payment gateway returns, asks the supplier to confirm, and issues the booking only after that. Double taps cannot charge twice, since each payment is processed exactly once. When the supplier declines, the refund starts on its own and no one on your team touches it.

A single record for every booking

  • Whether the trip was a flight, a room or a cab, it lands in the same booking hub. Traveler dashboards, tickets, cancellations that show the refund before confirming, loyalty points and margin reports all read from that one place, so no one reconciles eight separate systems.

Help arrives during the journey

  • Tickets, vouchers and reminders go out by email, SMS, push and in-app messages, with each traveler choosing channels. Questions reach an AI assistant first and a human when needed, and the booking is already attached. Disputes stay open until they are resolved instead of bouncing between mailboxes.

The account pulls the traveler back

  • After the trip come reviews, points added at completion, cashback and refunds parked in the wallet, and referral codes that reward the person who shared and the person who joined. Five loyalty tiers turn a single purchase into a reason to come back for the next one.
  • A booking made by an agent for a customer, or by an employee inside a company policy, goes through this same engine. One deployment therefore serves all of them without a second backend.

Every Feature Earns Its Place

Each module is in an initial scope because a travel operator loses revenue, customers or sleep without it, and not because it pads a checklist.

Visa applications, forex orders and travel insurance are sold at the same checkout, and an AI trip planner converts a described trip into a day-by-day itinerary the traveler can book straight from the plan.

The Technology Behind the Features

One language across every layer, so a single team can maintain the sites, the apps and the engine that books trips.

Prices default to INR, with international cards accepted through Stripe. Showing prices in a traveler's own currency is custom work, quoted separately.

Boundaries we state in writing for your build

No mid-office or accounting module

  • You get bookings with payment, margin, refunds and cancellations, agent and vendor settlements with monthly statements, wallet and gift-card balances, and margin reports you can export. There is no double-entry ledger and no invoicing suite. Linking to your accounting package is custom work.

Local-currency display and extra languages

  • English is the main interface language and Hindi can be configured. More languages, prices shown in each traveler's currency, and local payment methods for new markets are add-ons. So are multi-brand setups, HR and ERP links or single sign-on beyond Google, marketing automation and a B2B package builder.

What is built is real

  • No security certification is claimed. The handbook describes controls that were built, which is different from an audit certificate. For anything past this list, see travel app development for custom scope.

Weighing up who should supply the platform?

  • Read the questions worth putting to any provider, the delivery steps, the warning signs, and a modelled reference deployment for a regional operator, all on the Provider page.

Hold the code, the contracts and the customer.

Consumer apps, an agent desk, corporate accounts, a vendor extranet and an operator console, all running on one booking engine with every margin set by you.

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.

Discuss this scope by message

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

team@omnistu.com