Noon Clone Development Company: How to Choose One
Anyone can demo a storefront. The question that separates providers is what happens when the same order has to carry a second currency, a different VAT rate, a serviceability rule and a cash settlement that closes three days later. Here is how the options compare, what to ask before you sign, and what we have not done yet.
Talk to Our Team →See PricingAgency vs Freelancer vs Miracuves
Three routes to a multi-market marketplace, and the trade-off each one actually asks you to accept.
| What you care about | Custom agency | Freelance team | Miracuves ready-made |
|---|---|---|---|
| Time to a working platform | Quarters, and multi-market work lands last | Unpredictable, often optimistic | Six working days, markets configured with you |
| Cost shape | A programme budget that moves | Low quote, high variance | $2,499 fixed, one-time, add-ons named up front |
| Multi-currency | Built if you specified it correctly | Usually a display conversion | A currency catalog with operator-set rates in the schema from day one |
| Tax across zones | Built if you specified it correctly | Frequently one rate | Tax classes bound per zone with per-product overrides |
| Cash settlement | Often descoped when the budget tightens | Rarely modelled at all | Verified handover, per-agent cash balance, operator settlement |
| Who owns the code | Usually you, check the contract | Usually you, if it is documented | You - complete Laravel 12 source, no encrypted files, no callback |
| What happens if they leave | Handover is a project of its own | The single largest risk | Ordinary Laravel and Flutter; any competent team can pick it up |
| Domain knowledge included | Depends entirely on the team | Depends entirely on the individual | Already in the schema - 131 tables of it |
| Proof it works | Their portfolio | Their portfolio | A live demo you can place a real order through |
The row worth dwelling on is the last-but-one. A custom build's real cost is not the invoice, it is that the only people who understand the tax binding are the ones you are paying by the month.
Questions Worth Asking Any Provider
Ask these of us, and of everyone else you are talking to. The answers separate a marketplace that can add a market from one that can only serve the first.
If a provider answers all nine confidently, ask to see three of them in a live console rather than a slide.
The Six-Step Development Process
What actually happens between signing and taking your first order, and who is responsible for each part of it.
Market discovery
Which states you sell into, which currencies you quote in, which VAT treatments apply, where delivery genuinely reaches, which languages the catalog reads in, and how much of your volume closes in cash. This shapes everything after it, so it is a conversation rather than a form.
Infrastructure and deployment
Provisioning on your provider under your account, the Laravel 12 application deployed, MySQL and Redis running, queue worker and scheduler configured, storage wired, domain pointed and TLS in place. Your infrastructure from the first day, not ours with a migration promised later.
Market configuration
Currencies created with operator-set rates and a default per market, tax classes bound per zone with per-product overrides, delivery country codes and zip allowlists opened, shipping methods with per-category cost overrides, and languages enabled with the translation store ready.
Branding across six surfaces
App name, logo, splash screen and colour theme applied to all three Android builds and both web surfaces, transactional email templates branded, and the custom domain configured. Six surfaces that have to look like one company.
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, loyalty ratio and coupon rules in place, and seller subscription tiers defined if you are using them.
Walkthrough, handover and support
One order traced end to end across buyer, seller, agent and operator, the repository transferred to you, staff accounts created with their permissions, and the configuration checklist handed over. Then 60 days of launch guidance, 6 months of priority bug fixes and 12 months of updates.
Six days is our side of it. Seller recruitment, catalog data, translated copy and gateway merchant approvals run on their own clocks and are yours to drive - we will tell you that before you buy, not after.
Red Flags That Mean Walk Away
Six things that should end the conversation, whoever you are talking to, including us.
If you hear any of these, stop
- "Multi-currency is just a display setting"It is not. If the order, the commission split, the refund and the settlement record do not each know their currency, your books stop agreeing the week your second market opens.
- "We will add the second country later"Later means a rebuild. Currency, tax zone, serviceability and translation are schema decisions. Retrofitting them into a live marketplace with real orders in it is the most expensive version of this project.
- "Cash on delivery is just another payment method"A cash order is a promise that closes days later, at a door, with stock and commission already committed. Anyone who calls it a checkbox has not run one.
- "Some files are encrypted for licensing"Then you do not own the platform, you rent it with extra steps. Ask this question early because the answer rarely improves.
- "We take a small percentage of orders"A percentage on a thin-margin marketplace is a permanent tax on the part of the business you worked hardest for. Fixed price or walk.
- "Everything is ready, nothing is missing"No platform is finished. A provider who will not name a single gap is either not looking or not telling, and both cost you the same amount eventually.
The last one is the reason the section below exists on our own page.
What a Multi-Market Marketplace Has to Get Right
Five things that are invisible in a demo and decisive in production. Any provider you are considering should be able to show you all five.
Every one of these ships in the base build and is demonstrable in the live demo. Ask us to open any of them with data in it.
What We Have Not Done Yet
Stated plainly, because you will find it out anyway and it is better you hear it from us first.
No named client on this platform
We have not yet deployed this multi-vendor commerce platform for a named client. Nothing on this page is presented as a Noon Clone reference. The testimonials on the hub are approved quotes from operators who launched other Miracuves marketplaces built on the same foundations - vendor onboarding, a merchant console, dispatch to a fleet, and commission and payouts on one ledger.
The reference deployments are modelled
The two deployments described below are illustrative configurations built only from capabilities that ship in the base build. They are not client engagements, they carry no reported revenue or growth figures, and the numbers in them are properties of the platform rather than results a customer reported.
Right-to-left layout is scoped work
Not included, and not implied anywhere. For a Gulf-market deployment this is the caveat most worth pricing at the start of the conversation rather than the end of it. Multi-language content itself does ship - the translation store and per-locale listing content are in the base build.
Android only in the base price
Three Flutter Android builds ship. The projects compile for iOS, but the developer account, signing, store submission and review cycle are separate work and quoted as an add-on rather than assumed.
Neither ISO 27001 nor SOC 2 is held
Neither certificate is held and neither is claimed. The platform is built so the evidence gathering is possible - permissions per module, append-only histories, field-level edit records - but certification is a separate programme with its own auditor and its own cost.
Your accounts stay yours
Gateway merchant credentials, SMS and email providers, the Firebase project and the OpenAI key are all integration-required. We configure them with you; we do not supply them, and we do not resell them to you at a markup.
A provider willing to publish this list is easier to verify than one who is not. Hold us to it.
Modelled Reference Deployments
Two illustrative configurations showing how the same platform is set up for two very different commerce markets. Neither is a client engagement. Both are built only from capabilities that ship in the base build and are demonstrable in the live demo.
India: COD-Led Multi-Vendor Marketplace
How the platform is configured for a marketplace where cash still closes a large share of orders and growth runs outward from the metros into smaller towns.
What the market makes hard: cash closing the order at the door days after it was placed with stock and commission already committed; tax rates differing by category and by state, needing a line on every invoice; buyers who do not shop in English; and delivery that reaches some pin codes reliably and others not at all.
What ships in the base build: cash on delivery with a server-verified code at handover, a cash balance carried per agent and settled to the operator wallet, an operator-set handling fee, zip allowlists deciding where checkout is offered, tax classes bound per zone with per-product rules, and languages configured across web and all three Android apps.
The figures above are properties of the platform, not results reported by a customer. Named client deployments, with their own reported figures, are published separately on the Miracuves portfolio.
Thailand: Provincial and Cross-Border Marketplace
How the same platform is configured where one catalog has to serve a capital, the provinces and a neighbouring market, each with different delivery economics and a different currency.
What the market makes hard: delivery economics differing sharply between a dense capital route and a provincial or island one; buyers who expect to pay on arrival; selling into neighbouring markets that quote in a different currency; and a second market usually meaning a second deployment to keep in step.
What ships in the base build: zones with per-category shipping cost overrides, a currency catalog whose default drives checkout display, cash on delivery with per-agent reconciliation, a delivery fleet with pickup and delivery checkpoints, multi-language storefront across every surface, nine order statuses with a full history per order, and one REST API serving the storefront, the seller panel and all three apps.
The figures above are properties of the platform, not results reported by a customer. Named client deployments, with their own reported figures, are published separately on the Miracuves portfolio.
We label these as modelled rather than dressing them as case studies because we have not yet deployed this platform for a named client, and a reference deployment presented as client proof is the fastest way to lose the trust this page is trying to earn.
Frequently Asked Questions
Have you deployed this platform for a real client?
Why would I buy a platform with no client reference?
Do I own the code, genuinely?
What if I need something the base build does not have?
Can our own developers maintain this after handover?
What support comes after go-live?
Ask us the hard questions first
Bring the nine questions above. We will answer all of them in a live console, including the ones where the answer is that we have not done it yet.
Explore the Noon Clone
A partner who tells you what has not happened yet
No named client on this platform, two modelled reference deployments labelled as modelled, and a live demo you can place a real order through. Deploy in six days with full Laravel 12 source on infrastructure you own.
Talk to Us →Miracuves is an independent software development company. We are not affiliated with, connected to, sponsored by, or endorsed by Noon.
“Noon Clone” is used descriptively. It is how the software industry refers to building a platform with functionality similar to Noon, and how clients search for it.
The entire design and codebase is built by our own team. The product contains no code, design, graphics, or content originating from the Noon website or applications.
Noon 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.
