Yatra Clone · Development Company

Yatra Clone Development Company: What to Check Before You Hire

Most travel developers have built a booking app. Far fewer have built a ledger that partners trust with their money. Ask a vendor what stops two agents' parallel bookings pushing a balance below its credit ceiling. Ask who can raise a ceiling and whether that is recorded. Ask whether agents can set their own markup, and whether the answer changes after you sign. Below is how we work, what we state plainly and nine questions worth asking.

Talk to Our Team →See Pricing
Since 2010 building platforms
Full source ledger included
6 days to deploy
A credit change
Who, when and why
What Handover Actually Means
01Balance and credit logic
02Commission and settlement rules
03Supplier KYC and GST handling
04Four business portals
05Security handbook and VAPT
06The gap list, in writing
2010
Building Platforms Since
9,000+
Projects Delivered
6 days
Deployment Window
100%
Source Code Transferred
Compare

Agency vs Freelancer vs Miracuves

Three routes to the same trade platform, and where each tends to fail at the first month end.

What mattersFreelance teamMiracuves ready-made
Time to liveMany months, most of them on finance logicSix working days
Parallel bookings against one balanceWhichever request lands last winsProcessed once, ceiling checked before confirming
Who can raise an agent's creditAnyone with admin accessA specific permission, logged with a reason
Commission after a partial refundRecalculated by handAdjusted on the booking record automatically
A supplier with no GST certificateListed anywayCannot sell until verified
Vendor tax paperworkSomebody's monthly taskGenerated with each payout
What is not builtFound during user acceptance testingPublished before purchase
Price behaviourHourly, and it moves$3,999 fixed, quoted before work starts

Good agencies exist and some understand travel well. What the table measures is time, price certainty, and whether the money side was engineered as a ledger or added as screens on top of a booking app.

Due Diligence

Questions Worth Asking Any Provider

Put all nine to us and to anyone else bidding. Five of them are about money, because that is where trade platforms fail.

01

Can two bookings beat a credit ceiling?

Ask what happens if an agent submits two bookings in the same second with room for only one. If the answer is not "one is refused", your credit policy is decorative.

02

Who can change an agent's credit?

A named permission with an audit entry, or anyone in the back office. Credit is the fastest way for a keen sales executive to create a bad debt.

03

Where is commission calculated?

On the server, stored with the booking, or worked out in a report afterwards. Only the first gives the agent and your accounts team the same number.

04

What does a monthly statement include?

Ask to see one with a refund and an adjustment in it. Statements that ignore either are the ones agents dispute, and disputed statements are why agents leave.

05

What happens to a failed supplier confirmation?

The amount should return to the agent balance automatically. If it needs a ticket to your finance team, expect a lot of tickets.

06

How are suppliers verified?

Which documents, stored where, visible to whom. KYC uploads sitting in a public folder are a data breach waiting for somebody to guess a filename.

07

Can agents set their own markup?

Ask directly, and ask about sub-agents and agency-branded sites in the same breath. Ours: no, no and no, each available as a quoted add-on.

08

Does corporate sign-in support SAML?

Larger clients' IT teams will ask. Ours ships email, one-time codes and Google sign-in; SAML is custom work, and it is better to know before a client asks.

09

What is on your list of gaps?

A provider with no list has not looked or is not telling you. Ours is on this page, before any contract.

All nine get answered on the first call, and most of them on the live demo with the agent, settlements and owner logins, where you check the answer instead of taking it.

Process

The Six-Step Development Process

What we do, in the order we do it.

Step 1 · Day 0

Map your partner agreements to the platform

How agents earn, whether they need to set markup or run sub-agents, what credit terms you offer, how companies are billed and what suppliers pay. Anything your agreements need that the base build does not do is scoped today, and gateway, messaging, store and supplier approvals start today.

Step 2 · Days 1 - 2

Brand every portal

Your name, logo, colors and domain on the agent, corporate, supplier and settlement portals, the website and both apps, so a partner signing in and a traveler booking directly both see one business.

Step 3 · Days 3 - 4

Deploy and connect

Your cloud, TLS, PostgreSQL and Redis, object storage for supplier documents outside the public web root, Razorpay and Stripe for payments and top-ups, messaging configured, and approved supplier accounts connected with demo inventory for the rest.

Step 4 · Day 5

Set terms and permissions

Commission, vendor share, margins and corporate plans entered, and the permissions to grant credit, adjust balances and release payouts given only to the people who should hold them, with sales, operations, support and accounts each scoped to their own work.

Step 5 · Day 6

Walkthrough and back office training

We approve a supplier, grant an agent credit, book for a client from the balance and then try to book past the ceiling so you see it refused. A corporate booking waits for approval, and the settlements desk closes a statement with a refund in it.

Step 6 · Post-launch

The support window

60 days of guidance, 6 months of priority bug fixes and 12 months of updates, with the deployment sized to your first partner network and the volumes at which each scaling step is worth taking written down for your team.

Day zero decides more on a trade build than on any other. A platform that does not match your agent agreements is a platform your agents will not use, and it is far cheaper to find that out before the portals are branded.

Warning Signs

Red Flags That Mean Walk Away

Five answers that should end the conversation

"Agents just get an admin login." Then every agent can see every other agent's clients and commission. A trade platform needs partners fenced into their own data on every request, not a shared console with good intentions.

"We'll handle credit in a later phase." Credit is how agents choose a supplier. Launching a trade channel without it means agents pay by card per ticket, and most of them simply will not.

"Settlements are an Excel export." An export is where reconciliation starts, not where it ends. Ask how refunds and adjustments reach the statement, and who fixes the figures when they do not.

"Sub-agents and markup are easy to add." They change commission, statements and reporting throughout. Easy to promise is not the same as scoped and quoted, and it should be the second before you sign.

No answer on supplier documents. Onboarding suppliers without checking PAN, GST and bank details invites fraud and tax trouble. A vendor with no view on it has not run a supplier network.

The fourth is the one we apply to ourselves. Sub-agents, agent markup and agency white-label sites are not in our base build, and we say so on every page rather than after a contract.

Domain

What a B2B Travel Platform Has to Get Right

The parts that decide whether agents, companies and suppliers trust you with their business.

A balance that cannot be beatenEach balance operation processed exactly once, the credit ceiling checked before confirmation, and an agent unable to book beyond their limit however many requests arrive together. The amount returns automatically when a supplier cannot confirm.
Money that moves only with permissionCredit changes, balance adjustments, refunds and payouts each require a specific permission and each is written to the audit log with the person and the reason, so the finance team, not whoever is closest to the partner, controls exposure.
Commission everyone reads the same wayAgent commission, vendor share and category margin calculated on the server and stored with the booking, adjusted on cancellation and refund, and rolled into monthly statements the agent can reconcile against their own records.
Suppliers verified before tradingPAN, GST certificate, bank statement, property deed and trade licence checked by type, stored outside the public web root and visible only to verification staff, with GST tax documents generated for every payout once the supplier sells.
Company rules applied before paymentEmployees with roles and hierarchy, travel policies evaluated on each booking, approvals routed before payment or ticketing, and expense claims filed against the trip, with employee data belonging to the company account and exportable or deletable on request.
Partners fenced into their own dataAn agent sees their clients and bookings, a company its employees and a supplier its inventory, enforced on every request, with rate limits per partner so one runaway script cannot slow the portal for everyone else.

All six ship in the base build. On the call we will open each one in the demo, starting with a booking that tries to exceed an agent's credit ceiling.

Platform Trust

What We Have Not Done Yet

Six items, stated before a purchase rather than after one.

01

No agent-set markup

Agents earn the commission percentage you configure and cannot add their own margin above your trade price. Where your market expects agents to price their own retail fares, agent-set markup is scoped and quoted before launch.

02

No sub-agent or distributor tier

Every agent is your direct partner. A master-distributor model where agents recruit and manage sub-agents, with commission split across tiers, is custom work that touches commission, statements and reporting throughout.

03

No agency white-label sites

Agents book through your branded partner portal. A booking website under each agency's own brand and domain, drawing on your inventory, is not in the base build and is quoted against the number of agencies involved.

04

SAML and multi-tenant are custom

Sign-in is email, one-time code or Google. SAML or a corporate identity provider for large clients is scoped per client, and a separate isolated platform for each reseller or regional partner is a multi-tenant add-on.

05

No certificates, and credit is still your risk

Built to the controls ISO 27001 and SOC 2 reviewers examine, but not certified, and no uptime figure. The platform enforces the credit you grant; it cannot decide whom to trust or recover a debt for you.

06

What is built is real

Agent balances and credit ceilings, commission on every booking, monthly statements, corporate policies and approvals, supplier KYC, GST documents, CRM, finance-only money permissions, two-factor for operators and a VAPT reference mapped to the OWASP Top 10.

Clone names the functional target rather than the provenance of the code: this is an original implementation on NestJS, React and React Native, with no affiliation to Yatra, TBO or Riya, none of whom is a supplier or partner to it.

Modelled

Modelled Reference Deployment

An illustrative configuration rather than a client engagement, showing how the platform would be set up for a travel consolidator. Every figure is a property of the build, not a reported result.

Illustrative Scenario

A Travel Consolidator in Pune Serving Agents and Companies

A consolidator supplying independent travel agents across Maharashtra and running business travel for mid-sized companies, from one deployment.

Illustrative scenarioNot a client engagementMarket modelled: India
5Supplier document checks
3Corporate plans
6 daysDeployment window

What the situation makes hard: agent credit tracked in spreadsheets and chased by phone, commission calculated by hand at the end of every month, and company bookings arriving by email with no policy or approval trail.

What the configuration addresses: a branded portal where agencies book for their clients, credit ceilings and prepaid balances controlled by the accounts team, corporate travel under policies, approvals and plans, and supplier KYC with automatic GST documents.

What ships, and what would be scoped: monthly statements, supplier payouts, company accounts with employee roles and expense claims, and finance-only permissions with an audit log. If this consolidator's agents expected to set their own markup or run sub-agents, those would be quoted as add-ons.

Named client work is published separately. The founders quoted on the hub built B2B platforms with credit, multi-tenant clients, settlements or invoicing at their core, in retail commerce, delivery, utility billing and logistics; none of them runs a travel agency, and the hub says so rather than implying otherwise.

FAQ

Frequently Asked Questions

Have you built B2B platforms like this before?
Miracuves has been building platforms since 2010 with over nine thousand projects delivered, and founders have published attributed reviews of B2B platforms built with us where the hard part was credit, multi-tenant clients, reconciliation or invoicing, in retail commerce, delivery, utility billing and logistics. None of them is a travel agency, and we say so. The case study on this page is labelled as a modelled deployment because we would rather describe an illustration honestly than borrow proof from a different kind of engagement.
What exactly do I own at handover?
The complete TypeScript source for the agent, corporate, supplier and settlement portals, the consumer website, the React Native apps and the NestJS services, including the balance, credit, commission and settlement logic and the KYC and GST handling. No licence fee, no per-agent charge, no share of bookings and no restriction on use, with product, API and security documentation and a VAPT compliance reference alongside.
Can you add sub-agents or agent markup for us?
Yes, as scoped custom work rather than as something already in the box. A sub-agent hierarchy with commission split across tiers, agent-set markup above your trade price and white-label agency sites all change how commission, statements and reporting work, so we quote each in writing against your agreements before you commit. Custom work typically takes two to eight weeks.
Is partner money safe on the platform?
Money actions are the most tightly controlled part of the build. Credit changes, balance adjustments, refunds and payouts each need a specific permission and are logged with who acted and why. Balance operations are processed once, amounts are fixed on the server and gateway signatures are verified, and admin and finance users sign in with two-factor authentication. We do not claim a certificate, and if your lenders or auditors expect particular controls, we map them before launch.
Who holds the supplier and payment accounts?
You do. Supplier agreements and Razorpay and Stripe accounts are yours, with their keys encrypted with AES-256, masked in the back office and covered by a credential audit log. Supplier KYC documents live in your own object storage outside the public web root. We connect everything during deployment and do not hold access afterwards.
What if my model needs something the base build does not do?
We scope and quote it in writing before it starts, and we tell you if the honest answer is that the ready-made route is wrong for you. On trade builds the requests that come up most are sub-agents, agent markup, agency white-label sites, SAML sign-in and accounting exports, and all five are named on this page rather than discovered after a contract.

Ask us the hard questions first

Bring the nine questions from this page and your agent agreement. Start with the one about two bookings and one credit ceiling.

Explore

Explore the Yatra Clone

Five pages on this product. You are on Development Company.

Hire on the answers, not the deck

Grant an agent credit, book past the ceiling and watch it refused, then close a statement with a refund in it. An afternoon on the demo, and the claims on this page are checked.

Talk to Us →
Miracuves · Yatra Clone Solution Process, gaps and modelled deployment cross-verified against the hub, 2026-09-15
Disclaimer

Miracuves is an independent software development company. We are not affiliated with, connected to, sponsored by, or endorsed by Yatra.

Why this name

“Yatra Clone” is used descriptively. It is how the software industry refers to building a platform with functionality similar to Yatra, and how clients search for it.

Who built this

The entire design and codebase is built by our own team. The product contains no code, design, graphics, or content originating from the Yatra website or applications.

Trademarks

Yatra and all other third-party names and marks are the property of their respective owners, referenced here solely to describe the category of software offered.