Noon Clone Development Cost: What a Second Market Really Costs
Ask any quote whether it prices the second market at all. The currency table, the per-zone tax binding, the serviceability gate and the cash settlement path are either in the schema from the start or they can become a rebuild later. Here is how the routes compare, what the recorded scope includes, what moves the number, and the costs a quote can leave out.
The original page's fixed dollar price, deployment-day schedule, from-scratch month range, regional hourly rates and support-window durations are excluded as unverified here: price, timeline and support scope are set in the written terms. Every capability below is recorded scope to confirm in writing and in your own acceptance testing.
What a Noon-Style Platform Costs Each Way
Three routes to the same capability. The differences that matter are not in the storefront - they are in whether the second market is a settings change or a project. The original asserted durations and outcomes for each route; those claims are replaced by the questions that verify them, with the Omnistu column kept as recorded scope to confirm against the signed terms.
| What you are buying | Build from scratch - what to ask | Omnistu Noon Clone - recorded scope | Assemble from separate products - what to ask |
|---|---|---|---|
| Cost | What is the itemized total in writing, and what does it exclude? | The original fixed-price listing is excluded here as unverified; request the current itemized quote in writing | What do three subscriptions cost across three years, and what gaps stay unowned? |
| Time to first order | What delivery window and acceptance criteria does the bidder commit to in writing? | Timeline and milestones set in the written plan; the original published day schedule is excluded as unverified | How long does integration take, and who owns the multi-market gaps when they appear? |
| Currency per market | Who designs the currency model, and what does getting it wrong once cost? | A currency catalog with operator-set rates, in the schema from day one - recorded scope | Ask which product's base currency wins, and what that costs the others |
| Tax that differs by state | Who designs the tax model, given it touches every invoice? | Tax classes bound per zone with per-product overrides - recorded scope | Ask whether the tax add-on knows about the other two products |
| Cash settlement | Is cash settlement scoped honestly at the start? | Verified handover, per-agent cash balance, operator settlement - recorded scope | Ask who owns the cash-and-currency gap between the products |
| Who owns the code | Do you own the source outright, with no encrypted files and no callback? | Recorded as complete Laravel 12 source, no encrypted files, no callback - confirm in the signed agreement | Ask whether you own anything, or rent all three |
| Commission on your sales | Is there any revenue share or per-order fee? | None recorded in the listing; your commission rate is yours - confirm in the signed terms | Ask whether there is a share or a per-order fee, and when it changes |
| Security review | How many codebases and reviews does the route involve? | One codebase, one review - recorded scope | Ask what three vendors, three reviews and three answers cost in elapsed time |
| Where it runs | Whose infrastructure does it run on, and whose branding? | Your infrastructure, your branding - recorded scope; confirm custody terms in writing | Ask whose infrastructure you are on, and what leaving looks like |
If three products each own a piece, the first cash order that has to reconcile against a currency the logistics product has never heard of is where the gap shows. Ask each vendor who owns that reconciliation before comparing sticker prices.
What the Scope Includes
The recorded listing covers the whole system, configured for the markets you actually sell into - not a licence to operate somebody else's platform. All seven groups are recorded scope; the original's support-window day and month counts are excluded as unverified, with support scope and duration set in the written terms.
Market configuration
Currencies with their rates and defaults, tax classes bound per zone, delivery countries and zip allowlists, and languages - all set up with you at deployment rather than left as a first-week discovery.
Customer storefront
The public marketplace with category browse, search and filters, product pages carrying variants and reviews, prices in the market currency, and a cart spanning several sellers.
Seller web panel
Shop profile and KYC, catalog management with bulk import, per-locale content on a listing, analytics, and everything a seller needs from a desk.
Operator console
Moderation, cross-seller orders, refunds, agent settlement, payouts, people, marketing, tax zones and market configuration, with role-scoped staff accounts from the start.
Three Android apps
Branded buyer, seller and delivery agent builds - the buyer app for browse through order tracking, the seller app for the order queue and wallet, the agent app for assignments, verified handover and collected cash.
Full source code
The complete Laravel 12 backend and all three Flutter projects recorded as transferred into your repository, unobfuscated, with no encrypted files and no licence callback of any kind.
Deployment and handover
Installed on your infrastructure with the queue worker, scheduler and storage running and your markets configured, then an admin walkthrough and the configuration checklist.
The market configuration line is the one worth reading twice. Currencies, tax zones, delivery countries and languages are set up with you during deployment, not handed over as an empty settings screen.
What Moves the Number
These are the things that genuinely sit outside the base scope, and roughly what each is shaped like. Anything beyond the base is scoped and quoted in writing; the original quoted a typical duration band for add-ons, which is excluded here - your timeline is set in the written scope.
How many markets, and how different they are
The markets you launch with are configured during deployment. Additional states afterwards are scoped separately, and the cost tracks how different they are rather than how many: a second state with the same tax treatment is quick, a market with a different tax regime and different delivery economics is real work.
Right-to-left layout
Named on the hub as a scoped customization rather than implied as included. For an Arabic-facing storefront, ask for it to be quoted at the start of the conversation, not discovered at the end of it.
VAT export and filing formats
Tax reports over any date range export to Excel, CSV and PDF in the base build - recorded scope. A jurisdiction-specific filing format, or a direct submission integration, is scoped work.
Processor-side purchase verification
Listed on the hub as scoped rather than included. If your risk profile requires verification on the processor side rather than in the application, budget it explicitly.
iOS builds
Three Android apps are the recorded base build. The Flutter projects compile for iOS, but the developer account, the signing setup, the store submission and the review cycle are separate work and quoted as such.
Governance beyond the base
Ask whether your category carries requirements like age-gated categories, country-specific catalog rules, per-seller document expiry, or a four-eyes approval on payouts. Each is a custom module, absent from the base build, and cheaper to scope early.
The Recorded Path to Live
What happens between signing and taking the first order, in the recorded order. The original assigned a specific day to each step; those duration claims are excluded as unverified and the sequence is preserved - confirm the timeline you are quoted in writing.
Step 1 ยท Markets and scope
Which states you sell into, which currencies you quote in, which tax treatments apply, where you can actually deliver, and which languages the catalog reads in. This is the conversation that shapes everything after it, so it happens first rather than during handover.
Step 2 ยท Infrastructure
Provisioning on your provider, the Laravel 12 application deployed, MySQL and Redis running, the queue worker and scheduler configured, storage wired and the domain pointed - recorded scope.
Step 3 ยท Market configuration
Currencies created with their operator-set rates and a default per market, tax classes bound per zone with any per-product overrides, delivery country codes and zip allowlists opened, and shipping methods with per-category cost overrides - recorded scope.
Step 4 ยท Branding and translation
App name, logo, splash screen and colour theme across all three Android builds and the web surfaces, transactional email templates branded, languages enabled and the translation store ready for your catalog copy - recorded scope.
Step 5 ยท Payments and commercial rules
Your gateway credentials installed and tested per market, cash on delivery configured with its handling fee and code lifetime, commission set globally or per category, and the loyalty ratio and coupon rules put in place - recorded scope.
Step 6 ยท Walkthrough and handover
One order traced end to end across all four identities, the repository handed to you, staff accounts created with their permissions, and an admin walkthrough with the configuration checklist. The support window then begins; its scope and duration are set in the written terms.
The deployment window is not the go-to-market window. Seller recruitment, catalog data, translated product copy and gateway merchant approvals run on their own clocks and are yours to drive.
Sizing a From-Scratch Build
The original published indicative hourly rates per region and a from-scratch month range. Neither is verifiable from this page - a real market rate and a real duration belong to a bidder's written quote, not to our documentation - so the figures are removed and the regional rows become the questions that produce a real number.
| Region | What to ask bidders there |
|---|---|
| North America | Ask bidders for their blended senior rate in writing, what it includes, and how employer costs and notice periods change it. |
| Western Europe | Ask the same - and how employer costs and notice periods compare once included. |
| Gulf and Middle East | If this is the market being sold into, ask what local hiring does to the timeline, not only the rate. |
| Eastern Europe | Ask how the bidder controls specification quality when the rate drops. |
| Latin America | Ask whether time-zone overlap is the real reason for the quote, and what else it buys. |
| South and Southeast Asia | Ask how multi-market domain knowledge varies between teams at this rate, and how it is evidenced. |
Why there is no total here
A from-scratch total depends on your team size, your region, how much of the multi-market work is scoped correctly at the start, and how many times the tax binding is rebuilt before it holds. Publishing one number would require inventing four assumptions and presenting them as a finding. The questions above plus a written quote from each bidder let you build the estimate from your own inputs, which will be more honest than any figure invented here.
For the platform side, the recorded comparison points are the 131-table schema and the six surfaces a from-scratch build would have to design and keep in step. Ask any bidder to price against those explicitly.
Why the Price Is Fixed, Not "Starting At"
The original listed a single fixed figure; that figure is excluded here as unverified and the current itemized quote comes in writing. The policy behind it - what a fixed price commits to - is preserved below as recorded terms.
The scope is the demo
The recorded terms state what you see is what deploys: there is no tier of the platform withheld for a larger invoice. Confirm the mapping in writing.
Configuration is not a change request
Setting up your currencies, tax zones, delivery countries and languages is recorded as deployment work, not billable scope creep.
Add-ons are named before you buy
Right-to-left layout, iOS builds, extra markets, VAT export and processor-side verification are listed as scoped work on the hub itself, not revealed later.
No commission recorded
The recorded listing takes no share of orders and no per-order fee; your commission rate is a lever you set for your own economics. Confirm in the signed terms.
No licence callback
The recorded scope states the code does not phone home, so there is no mechanism to switch your platform off. Confirm each term in the signed agreement.
The Enterprise tier is a different conversation
Custom, compliance-heavy and high-scale work is quoted on its own scope - priced separately rather than grown from a base figure.
The two-tier structure exists precisely so the ready-made price can stay fixed. If your requirements genuinely exceed the base build, that should be a quote, not a surcharge.
Where the money comes back from
Where the money comes back from
The source lists six proposed revenue approaches for the platform, and the Business Model page examines them against growth stage and shows which lever to switch on first.
Frequently Asked Questions
Is the listed price really the whole price?
The original listed a single fixed figure; that figure is excluded here as unverified, and the current itemized quote comes in writing. The recorded terms state it is one-time rather than a subscription and not a floor, covering the Laravel 12 source, the buyer storefront, the seller panel, the operator console and all three Android applications, installed on your infrastructure under your branding with your markets configured. Add-ons that sit outside it are named on the hub before you buy rather than after.
How many markets can I launch with?
The markets you specify are configured with you during deployment, and the platform is built to run several from one deployment - recorded scope. Adding markets later is scoped separately, and the cost tracks how different a market is rather than simply how many: a second state under the same tax treatment is quick, a different tax regime with different delivery economics is real work.
What does the from-scratch alternative cost?
No dollar figure or month range is published here, because neither is verifiable from documentation: the honest measure is a written quote from each bidder against the 131-table schema and six surfaces the platform is recorded to carry. The regional questions above are how you get a real number.
Do you take a commission on my sales?
The recorded listing states no: no revenue share and no per-order fee, with commission a lever you set for your own economics - globally, per category, per seller or per product. The code is recorded as carrying no licence callback either. Confirm each term in the signed agreement.
Is right-to-left layout included?
No. RTL is named on the hub as a scoped customization rather than implied as included. Multi-language content itself is recorded in the base build - the translation store and per-locale listing content - but RTL layout work is quoted separately. For an Arabic-facing storefront it is worth pricing at the start rather than assuming.
What happens after deployment?
Support scope and duration are set in the written terms; the original published specific day and month counts, which are excluded here as unverified. The recorded scope states the code is yours afterwards with no dependency on us: complete Laravel 12 source and all three Flutter projects in your repository, unobfuscated, with no encrypted files and no callback. Confirm each term before signing.
One recorded listing, no cut of your orders
The recorded listing is one fixed price with no commission taken and no licence callback - the figure itself is excluded here as unverified, so ask for the exact scope against your markets in writing. No calls required, no phone numbers collected.
