PRODUCT ENGINEERING / CONNECTED BUSINESS SYSTEMS
Omnistu Global - Everything ConnectedStart a project
Omnistu logoOmnistu
MakeMyTrip Clone ยท Features

MakeMyTrip Clone Features: One Trip, Eight Categories, Three Kinds of Buyer

A traveler who books a flight still needs a hotel, a transfer and something to do when they land. This platform sells all of it in one checkout, and then sells it again through two further channels: travel agents booking for their own clients, and companies booking for their employees under a policy. Flights, hotels, buses, trains, cabs, activities, holidays and homestays, with the margin on each set by you.

Written answersFull source includedLive inventory on your accounts
8Travel categories
7Recorded logins
9Recorded roles
24Recorded permissions
Feature set by role

Feature Set by Role

Seven recorded logins, one for each person a travel business actually has to serve; current demo availability is confirmed in writing, not asserted here.

The Traveler

Search flights, hotels, buses, trains, cabs, activities, holidays and homestays, filter and sort, pick a seat, a berth or a room type, and pay once with a wallet, promo code or gift card applied. Every booking, refund, loyalty tier and support ticket then lives in one dashboard, on iPhone, Android and the web.

The Travel Agent

A portal for agents who sell your inventory to their own customers. Client records, booking on a client's behalf, commission calculated on every booking, an agent wallet with a credit limit, and monthly settlements they can follow without a spreadsheet or a phone call to your office.

The Corporate Travel Manager

Travel policies with spend limits and class rules, bookings above the limit routed through manager and finance approval, expense claims generated after every trip, and spend visible by department. The company pays a plan fee, and you keep the margin on every trip its employees take.

The Vendor

Hotels, homestay hosts and activity suppliers onboard with their business documents, list properties and rooms, set seasonal rates, open and close dates on an availability calendar, reply to reviews and track earnings and payouts in an extranet of their own.

The Operations Team

Inventory in every category, every booking and user, promo codes and homepage banners, the refund queue, supplier approvals, support tickets and reviews, with every change written to an audit log. A scoped sub-admin role shows exactly what an operations user can and cannot open.

The Owner and Finance

The CEO login controls the business model itself: brand, which categories are live, the margin on each, which payment methods appear, supplier connections and team permissions. The billing login processes refunds, approves agent and vendor settlements and reads the margin reports, and nothing else.

The recorded scope lists nine roles and twenty-four permissions enforced per request, so an agent sees their clients, a vendor sees their properties, and finance never touches inventory it has no reason to change. Confirm the enforcement in writing before you rely on it.

Route comparison

Clone vs Generic Script vs Selling Through a National App

Most routes to a travel business hold up until the second category, or the first agent. MakeMyTrip, Goibibo, Yatra and Cleartrip are the comparable apps people have in mind; none of them is a product you can buy, and none of them is a supplier to this platform. The script column is the question to put to that bidder; the Omnistu column is the proposed scope to confirm in the signed software terms.

What decides itA generic flight-and-hotel script - what to askOmnistu - specified scope
CategoriesAsk how many categories ship, and whether each switches on per market.Eight, switched on per market - specified.
Selling through agentsAsk whether an agent portal with wallet and commission is included, or is a separate tool bought later.Agent portal, wallet and commission built in - specified.
Selling to companiesAsk whether policies, approvals and expense claims exist at all.Policies, approvals and expense claims - specified.
Setting a marginAsk whether margins can differ per category without a developer.Percentage, flat fee and minimum per category - specified.
A supplier failing to confirmAsk what happens to the traveler's money, and who chases it.Automatic refund, no manual chase - specified.
A primary supplier going downAsk whether a fallback supplier keeps the category bookable.Fallback supplier keeps the category bookable - specified.
Repeat bookingsAsk what brings a traveler back beyond a promo code field.Wallet, gift cards and five loyalty tiers - specified.
Source codeAsk whether source is included, encrypted or revenue-shared.Yours outright, no revenue share; confirm against the signed software terms.
Booking engine

From First Search to the Next Trip

Seven stages, each one part of the recorded booking-engine scope rather than an idealised flow.

The traveler arrives to deals

The homepage shows offers, banners and popular destinations you schedule from the admin panel, before anybody searches. Sign-up is email, a one-time code or Google, and saved travelers, documents and recent searches make every later booking faster than the first.

Suppliers are searched in parallel

Each category has a primary supplier, fallbacks and compare-only sources, queried at the same time and merged with the hotels, homestays, activities and packages you list yourself. The routing is designed so one slow supplier does not slow every result, and filters narrow by price, time, stops, stars, amenities and rating.

Every price carries your margin

Supplier rates pass through the margin set for that category, as a percentage, a flat fee and a minimum, so the fare a traveler sees already includes what you chose to earn. The fare breakdown shows taxes and fees before payment, with insurance, visa help and forex offered alongside.

Pay, then book, never the other way round

The server creates the payment order with the amount locked, verifies the gateway signature, confirms with the supplier and only then issues the booking. The flow is designed so a repeated tap does not charge twice, and a failed supplier confirmation triggers an automatic refund - both behaviours recorded scope to verify on the demo before you rely on them.

One record, whatever was booked

Flights, hotels, buses, trains and every other category are recorded to feed one booking hub. That single record is designed to power the traveler dashboard, support tickets, cancellations with the refund shown upfront, loyalty points and revenue reporting, so nothing has to be reconciled across eight systems.

The trip is supported while it happens

PNR, voucher and reminders by email, SMS, push and in-app through a durable queue, with AI chat and human agents handling questions with the booking already attached. Disputes and refunds are tracked through to completion rather than handed between inboxes.

The platform works on the next booking

Reviews once they are home, loyalty points credited on every completed booking and moving travelers up five tiers, cashback and refunds sitting in the wallet ready to spend, and referral codes rewarding both sides. The next trip starts with a reason to book it here.

An agent booking for a client and an employee booking under a policy run through exactly the same engine, which is why one deployment can sell to all three kinds of buyer without three backends.

Scope rationale

Every Feature Earns Its Place

Each row is here because a travel business loses money or customers without it, not because a competitor lists it.

ModuleWhy it is in the base build
Pay-then-book checkoutTravel checkouts fail in the gap between taking money and getting a confirmation. Locking the amount, verifying the payment and refunding automatically on a failed confirmation is what stops peak weekends turning into double charges and chargebacks.
Primary and fallback suppliersSuppliers go slow and go down, usually on the busiest day. A fallback in line for each category keeps it bookable instead of showing travelers an error while they open a competitor's app.
Margin per categoryA flight and a holiday package do not carry the same economics. A percentage, a flat fee and a minimum set separately for each category is what lets pricing follow the market instead of one number applied to everything.
The agent portalA great deal of travel is still sold through local agents. Client records, commission on every booking, a credit-limited wallet and monthly settlements capture that business without building a separate B2B system.
The corporate portalCompanies will not let employees book freely. Policies, spend limits, approval routing and automatic expense claims are the minimum a travel desk needs before it will move its account to you.
The vendor extranetListed inventory earns a commission rather than a thin supplier margin. Letting hotels and hosts onboard, set rates and manage availability themselves is how that supply grows without your team keying it in.
Wallet, gift cards and loyaltyOne traveler books several times a year across several categories. Refunds to the wallet, cashback and five tiers with a recorded configurable points multiplier (recorded at up to 2.5x) are designed to turn a one-off booking into a repeat customer - a hypothesis your own retention data tests.
One booking hubEight categories with eight separate records means support, refunds and reporting that never agree. One hub behind every category is what makes a multi-category business operable by a small team.

Visa, forex and travel insurance sit inside the same checkout, and an AI trip planner turns a described trip into a day-by-day plan the traveler can book in a tap.

Stack

The Technology Behind the Features

TypeScript end to end, so the same engineers can work on the web apps, the mobile apps and the booking engine.

Web applications

React, TypeScript and Tailwind with server-side rendering, carrying the consumer website, the traveler dashboard and every partner portal in one web app, with role-gated areas for agents, corporate travel, vendors, support and admin, and maps, seat pickers and live chat built into the interface.

Mobile applications

React Native on Expo, one codebase for iOS and Android, with tab navigation for home, flights, hotels, transport, trips and wallet, secure on-device token storage, and push notifications with deep links into trips and offers. Every portal is recorded on mobile as well as the web - confirm parity in your acceptance testing.

API and booking engine

Node.js on NestJS with a module per travel category and business function, a REST API plus real-time chat over WebSockets, pay-then-book checkout with idempotent payments and signature-verified webhooks, and supplier orchestration with primary, fallback and compare routing.

Data and caching

PostgreSQL through TypeORM with versioned migrations, a relational model for bookings, payments, partners and loyalty, and Redis for caching, rate limiting and the background queues behind notifications, loyalty upgrades, reminders, settlement runs and expense generation.

Suppliers and payments

Recorded connectors for flight, hotel, bus, rail, cab and activity suppliers including Amadeus and Hotelbeds, Razorpay for India and Stripe internationally, SendGrid email, MSG91 and Twilio SMS and Google Maps, with supplier keys stored encrypted and managed from the admin panel. Each named integration is recorded scope to validate on your own accounts.

Cloud and operations

Containerized with Docker behind nginx with TLS, stateless API servers that scale out behind a load balancer for peak season, object storage and a CDN for images and documents, on AWS, Google Cloud or Azure depending on where you already run.

India and global supplier stacks run side by side, INR by default with international currencies through Stripe, so a regional brand and an outbound travel business can sit on the same codebase.

Scope boundary

What Is Not Included in the Base Package

A fixed price only means something if the boundary around it is stated, and on a travel platform the first item decides your launch date.

Live inventory runs on your supplier accounts

Connectors ship, and a demo inventory is recorded for exercising every category; confirm its current availability in writing. Live flights, hotels, buses and trains are switched on with your own GDS or consolidator, hotel wholesaler and bus and rail agreements, because those contracts and their terms belong to your business, and so do their approval timelines.

No two-way channel manager

Vendors manage rates and availability in the extranet. Syncing those in both directions with outside booking channels, so a hotel manages inventory once and sells everywhere, is a scoped add-on rather than part of the base build.

Margins are set, not optimized

A percentage, flat fee and minimum per category ship. Rules that move margins automatically by season, demand, route or booking window are the dynamic pricing add-on, worth scoping once you have enough booking history to know what the rules should be.

Enterprise corporate workflows

Policies, approvals and expense claims ship in the corporate portal. Custom approval chains, HR and ERP expense integrations, cost-center billing and single sign-on are what large corporate clients ask for next, and they are scoped against the client's own systems.

Four more add-ons

Several brands or white-label partner sites on a shared core, additional currencies and translated interfaces for other markets, marketing automation for abandoned searches and fare alerts, and a B2B builder for agents assembling their own packages. Plus any specific airline, wholesaler or local supplier your market depends on.

Recorded scope

What the Recorded Scope States

What the recorded scope states

Eight categories, pay-then-book checkout designed to refund automatically, supplier fallback, margins per category, agent and corporate portals, a vendor extranet, wallet, gift cards and five loyalty tiers, nine roles and twenty-four permissions. Security is designed around the controls ISO 27001 and SOC 2 assessments look for - which is not the same as holding either certificate, and we do not claim to - and a security handbook with a VAPT reference mapped to the OWASP Top 10 is a recorded deliverable. Confirm each item in writing before you rely on it.

Evidence

The Recorded Demo, Requested in Writing

Evidence to request in writing: the recorded demo carries seven logins - book a trip as the traveler, then open the same booking, its payment and its margin as the admin. What is currently available is confirmed in writing when you ask, not asserted here.

FAQ

Frequently Asked Questions

Which travel categories does it cover?

Eight: flights, hotels, buses, trains, cabs, activities, holiday packages and homestays, each with its own search, filters and booking flow. Flights have one-way, round-trip and multi-city search with a seat map. Buses have seat maps and boarding points, trains have classes, quotas, berth preference and PNR status, cabs cover airport transfers and hourly packages, and holidays carry day-by-day itineraries. Each category can be switched on or off per market from the admin panel.

Can travel agents book through it?

Yes, through a portal of their own. Agents keep client records, book on a client's behalf, see commission calculated on every booking, draw on an agent wallet with a credit limit you set, and follow monthly settlements without reconciling anything by hand. They book from the same inventory and the same engine as your consumer app, so an agent network is a channel you switch on rather than a second system you have to build and keep in step.

How does corporate travel work?

Companies get a portal where their travel manager sets policies with spend limits and class rules. Bookings inside the policy go straight through; bookings above the limit route through manager and finance approval first. After each trip an expense claim is generated, and the company admin sees spend by department. You can sell Starter, Business and Enterprise plans to those companies and still earn your margin on every trip their employees book.

What happens if a supplier fails to confirm?

The checkout is pay-then-book by design: the server locks the amount, verifies the payment with the gateway, asks the supplier to confirm and only then issues the booking. If that confirmation fails, the payment is designed to go back without anybody on your team chasing it. Separately, if the primary supplier for a category is down, the booking is designed to move to the next supplier in line, so the category stays bookable. Both behaviours are recorded scope - verify them on the demo before you rely on them.

Does it come with live inventory?

The connectors are recorded, and so is a demo inventory for exercising every category; confirm current availability in writing. Live inventory is activated with your own supplier accounts, such as a flight GDS or consolidator, a hotel wholesaler, and bus and rail partners, because those agreements belong to your business. We connect the accounts you hold during deployment. You can also list your own hotels, homestays, activities and packages directly, without any outside supplier at all.

Does the mobile app do everything the website does?

They are scoped to. The iOS and Android apps come from one React Native codebase, so both are scoped to carry the same features, with tab navigation for home, flights, hotels, transport, trips and wallet; parity is to be verified in your acceptance testing. Travelers search, book, pay, manage refunds, track loyalty and raise support tickets in the app, and the agent, vendor, corporate and admin portals are recorded on mobile as well. The apps publish under your own Apple and Google developer accounts.

Next step

Talk Through Your Travel Platform

Questions are answered in writing - no calls required, no phone numbers collected. The deployment process, the questions worth asking anyone bidding on a travel build, and the red flags are on the Development Company page.