Engagement scope - proposed scope
Yatra Clone Development Company: What to Check Before You Hire
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
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.
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.
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.
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.
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.
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.
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.
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.
A proposed launch process, without time promises
Define the first service area
- Where you operate, what you charge inside it, and any limits such as cash-on-delivery ceilings. The first zone usually becomes the template for the ones that follow.
Apply your branding
- Name, logo, colour scheme and invoice layout applied across the storefront and apps. Which parts are configuration and which are build work is confirmed in the written scope.
Set the commercial rules
- Commission or subscription structure, discount responsibilities, delivery pricing per zone, tax rules and payout preferences, recorded in the written scope.
Connect your own accounts
- Payment gateways, store listings, maps and notification services stay under your own accounts, with access arranged before build work starts.
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.
What a B2B Travel Platform Has to Get Right
The parts that decide whether agents, companies and suppliers trust you with their business.
What We Have Not Done Yet
Six items, stated before a purchase rather than after one.
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.
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.
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 an initial scope and is quoted against the number of agencies involved.
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.
What is built is real
- 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 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.
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.
- 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.
- 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.
More pages on this build
Five pages describing this proposed build. You are on Development Company.
Hire on the answers, not the deck
Omnistu is an independent software development project. We are not affiliated with, connected to, sponsored by, or endorsed by Yatra .
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.
Discuss this scope by message
Tell us your market and audience, and we will respond with a practical read on scope.
team@omnistu.com