Noon Clone App: One Marketplace, Several Gulf Markets
A launch-ready multi-vendor marketplace for operators selling into more than one Gulf state from a single deployment. Each market gets its own currency, its own VAT treatment and its own delivery promise, while the catalog, the sellers and the ledger stay in one place.
Six surfaces, one REST API. A customer storefront and Android app, a seller panel and seller app, a delivery agent app, and an operator console spanning catalog, orders, finance, marketing and configuration.
Go Live in 6 Days with Multi-Vendor CatalogVendor PayoutsDelivery FleetCOD ReconciliationAI Catalog CopyWhite-Label
⚡ Platform at a Glance
A Currency per Market
Currencies carry operator-set exchange rates rather than a live feed, so a dirham price and a riyal price are both deliberate. The default drives what each buyer is quoted at checkout.
VAT Where VAT Differs
Tax classes bind per zone with per-product rules through a polymorphic binding. Five percent in one state and fifteen in another is configuration, not two deployments.
Cross-Border Serviceability
Delivery country codes and zip allowlists decide where checkout is offered at all, with per-category shipping overrides so a cross-border route can price differently from a city one.
Cash Is Still the Habit
COD carries a code verified at handover, a cash-collected balance per agent, an operator-set handling fee and reconciliation into the operator wallet.
Four Separate Wallets
Customer, seller, delivery agent and operator balances kept apart, each with an append-only history so any balance can be re-derived rather than trusted.
Owned, Not Rented
Full source, your branding, your commission rate, your gateways, deployed on your infrastructure in six working days.
🚀 Ready to launch your own Gulf-market multi-vendor marketplace?
Live in Action
Noon Clone Demo: Six Live Surfaces, One Database
Four live surfaces sharing one database. Sign in below and trace a single order end to end: a buyer places it in their own currency, a seller accepts and packs it, an agent collects it and verifies the code at the door, and the operator watches every state change and every movement between wallets.
USER WEB
Browse, Cart and Checkout in the Browser
The buyer experience on the web: category tree, brand directory, search with filters and autocomplete, a product page with the variant matrix and reviews, a multi-vendor cart, and checkout with coupon, wallet and loyalty applied together.
-
Open the storefront and set the market
-
Sign in as a buyer using the details below
-
Trace: Search, Product, Cart, Tax, Checkout, Orders
-
Try: user@demo.com | User_321
USER APP
The Same Storefront on Android
The Flutter customer build against the same REST API: home rails and category browse, search, product detail with variants, cart and checkout, order tracking with live status, wallet and loyalty, plus push notifications and in-app support chat.
-
Install the Android buyer build
-
Use the buyer details below to sign in
-
Trace: Home, Search, Cart, Order Tracking, Wallet
-
Try: user@demo.com | User_321
SELLER WEB
Shop, Products, Orders and Payouts
The seller panel on the web: shop profile and KYC, product CRUD with the variant matrix and stock, bulk import and export, AI-assisted descriptions, an order queue with accept and reject, refund responses, sales analytics, and a wallet showing commission with a withdrawal request flow.
-
Open the seller panel in a second tab
-
Sign in with the seller details below
-
Explore: Products, Orders, Refunds, Wallet, Analytics
-
Try: vendor4@demo.com | Vendor_$321
SELLER APP
Run the Shop from a Phone
The Flutter vendor build for sellers who work away from a desk: the live order queue with accept and reject, product and stock edits, refund responses, customer chat, wallet balance with commission visible, and withdrawal requests.
-
Install the Android seller build
-
Use the seller details below to sign in
-
Explore: Orders, Products, Stock, Chat, Wallet
-
Try: vendor4@demo.com | Vendor_$321
DELIVERY APP
Assignments, Proof of Delivery and Cash
The last mile: an assignment feed with accept and reject, navigation to the vendor for pickup and then to the customer, status checkpoints from picked up to delivered, one-time-code verification at the door, and a wallet separating earnings from cash collected on COD orders.
-
Install the Android agent build
-
Use the agent details below to sign in
-
Explore: Assignments, Pickup, OTP Handover, Earnings
-
Try: delivery@demo.com or +91 9876543212 | Delivery_$321
ADMIN DASHBOARD
Catalog, People, Finance and Configuration
The operator cockpit: product moderation, cross-vendor orders with a full status timeline, refund and withdrawal queues, vendor and deliveryman approval, commission and tax setup, marketing, reports, and every business rule held as configuration rather than code.
-
Open the operator console in a third tab
-
Sign in with the operator details below
-
Explore: Moderation, Orders, Payouts, Settings, Reports
-
Try: admin@demo.com | Admin_$321
Video Walkthrough
Noon Clone Video Demo: Storefront, Vendor Flow and Operator Console
A walkthrough of the platform as an operator sees it, rather than a feature reel. It walks one order from a buyer searching, through the seller queue, out to the handover at the door, then shows that same order in the console with its status history, its tax lines and the wallet entries it produced on both sides. Catalog and moderation come next, then seller plans and commission, then the settings where gateways, currencies, languages and delivery zones actually get configured. If a specific flow matters more than the tour, ask and we will open it live with data in it.
App Flows
Noon Clone App Screens: Customer, Vendor, Delivery and Operator
The interface across the surfaces that matter: home and category browse, search with filters, the product page with its variant matrix and reviews, the multi-vendor cart and checkout, the vendor order queue and wallet, the deliveryman assignment feed with OTP handover, and the operator console.
Want a guided walkthrough of a specific flow? Book a call and we will walk whichever surface you care about, with data already in it.
Client Reviews
Marketplace Builds We Have Shipped
We have not yet deployed this multi-vendor commerce platform for a named client, so nothing below is presented as a Noon Clone reference. These are approved quotes from operators who launched other Miracuves marketplaces built on the same foundations: vendor onboarding and approval, a merchant console, dispatch to a delivery fleet, and commission and payouts on one ledger.
Proof in Production
Marketplace Reference Deployments: India and Thailand
Two modelled reference deployments showing how this platform is configured for two very different commerce markets. Both are illustrative scenarios rather than client engagements, built only from capabilities that ship in the base build. Real client deployments, with their own reported figures, are published on the Miracuves portfolio.
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 tier-2 and tier-3 towns.
- Cash closing the order at the door, days after it was placed, with stock and commission already committed
- Tax rates that differ by product category and by state, needing a line on every invoice
- Buyers who do not shop in English and convert badly against an English storefront
- Delivery that reaches some pin codes reliably and others not at all
- Take cash without inventing the accounting for it in a spreadsheet
- Open a new town only once a delivery route genuinely exists
- Set commission per category rather than one flat rate across electronics and apparel
- Run the storefront in the language the market actually reads
- Cash on delivery with a server-verified code at handover
- A cash-collected balance carried per agent, settled to the operator wallet
- Operator-set handling fee on cash orders
- Zip allowlists deciding where checkout is offered at all
- Tax classes bound per zone with per-product rules
- Languages and currencies configured across web and three Android apps
- Seller onboarding with KYC and per-seller commission
This is a modelled reference deployment, not a client engagement. Every capability listed above ships in the base build and is demonstrable in the live demo. The figures are properties of the platform, not results reported by a customer.
Thailand
Provincial and Cross-Border Marketplace
How the same platform is configured where one catalog has to serve Bangkok, the provinces and neighbouring markets, each with different delivery economics and a different currency.
- Delivery economics that differ sharply between a dense Bangkok route and a provincial or island one
- Buyers who expect to pay on arrival rather than in advance
- Selling into neighbouring markets that quote in a different currency
- A second market usually meaning a second deployment to keep in step
- Serve provinces and capital from one catalog without one subsidising the other
- Quote every buyer in the currency they recognise
- Add a neighbouring market as configuration rather than a second platform
- Keep the last mile, and the cash, under the operator brand
- Zones with per-category shipping cost overrides
- A currency catalog whose default drives checkout display
- Cash on delivery with per-agent reconciliation
- Delivery fleet with pickup and delivery checkpoints
- Multi-language storefront across every surface
- Nine order statuses with a full status history per order
- One REST API serving storefront, seller panel and all three apps
This is a modelled reference deployment, not a client engagement. Every capability listed above ships in the base build and is demonstrable in the live demo. The figures are properties of the platform, not results reported by a customer.
The Basics
What Is a Noon Clone App?
A Noon Clone is a ready-made multi-vendor marketplace built to run several markets from one deployment. Customers browse and buy, independent sellers list their own products and get paid, your own delivery agents complete the last mile and collect the cash, and you take commission on every transaction. The backend is Laravel 12 across 131 normalized MySQL tables, with one REST API serving the storefront, the seller panel, the operator console and three Flutter Android apps.
Markets
Currencies with operator-set rates, tax classes bound per zone, delivery country codes and zip allowlists, and entity-level translation, so one catalog can be sold four different ways.
Logistics
A delivery agent identity with KYC and approval, an assignment feed, live location, a code verified at handover, and cash on delivery reconciled through its own ledger.
Money
Four wallets with an append-only history per actor, commission split on completion, refund reversal, withdrawal queues, and settlement records held per gateway and per currency.
Built for Web, Android, Vendor & Delivery
What Is a Noon Clone Script?
Selling across borders multiplies the things that must agree. The same product needs a price in two currencies, a VAT treatment that differs by state, a delivery promise that only holds for some destinations, and a settlement path when the buyer pays cash at the door days after ordering. Get one of those wrong and the order still completes while the books quietly stop reconciling. All four are modelled here rather than left as operator discipline.
-
Currencies with operator-set rates, not a live feed
-
Tax classes bound per zone, overridden per product
-
Delivery country codes and zip allowlists per market
-
Entity-level translation across catalog and pages
-
Cash on delivery with per-agent reconciliation
Everything here is in the base build unless labelled configuration-required or integration-required. Gateway credentials, SMS, push and AI keys are yours to supply because they are your accounts. Right-to-left layout is named as a scoped customization rather than implied anywhere on this page.
Features
Noon Clone Features: Catalog, Checkout, Fulfilment and Payouts
Everything below is in the base build and demonstrable in the live demo. The order runs from the parts that decide whether one deployment can serve several states, outward to the catalog. Anything not relevant to your markets switches off from the console.
Currency per Market
Currencies carrying operator-set exchange rates, with the default deciding what each buyer is quoted at checkout. Rates are deliberate rather than pulled from a feed that can move overnight.
- Currencies with operator-set exchange rates
- A default currency driving checkout display per market
- Tax classes bound per zone
- Per-product tax rules through a polymorphic binding
Tax by Zone
Tax classes bound per zone with per-product overrides through a polymorphic binding, shown inclusive or exclusive, and itemized on every order. Different VAT rates across states are configuration.
- Delivery country codes controlling where you ship
- Zip allowlists deciding where checkout is offered
- Shipping methods with per-category cost overrides
- Inclusive or exclusive tax display per market
Cross-Border Serviceability
Delivery country codes and zip allowlists deciding where checkout is offered at all, with per-category shipping overrides so a cross-border route prices differently from a city one.
- Cash on delivery as a full settlement path
- A code verified at the door before handover
- Cash collected tracked per agent and reconciled
- Operator-set handling fee on cash orders
Cash on Delivery, Accounted
A code verified at handover, a cash-collected balance per agent, an operator-set handling fee, and reconciliation into the operator wallet when the agent settles.
- Entity-level translation across catalog and pages
- Operator-configured languages per deployment
- Products with multi-image galleries and video
- Self-referencing category tree of unlimited depth
Catalog and Translation
Multi-image galleries and a category tree of unlimited depth, with entity-level translation so a listing carries its own content per locale rather than one shared description.
- One cart spanning several vendors at once
- Guest cart tracked by session and merged on login
- Save for later and move to wishlist
- Shipping estimated per vendor before checkout
Checkout and Coupons
Coupon, wallet credit and loyalty points stacking on one order, shipping picked per seller, tax applied from the zone rules, and placement guarded against a double submit.
- Coupon, wallet and loyalty applied together
- Flat or percentage, scoped to product, category or cart
- Free-shipping coupons and per-user usage limits
- Order placement guarded by an idempotency check
Order State Machine
Nine statuses carrying an order from pending payment through to delivered, with cancelled, returned and failed ending it, and every move stamped into a status history.
- Nine order statuses from pending payment to delivered
- Per-line delivery status allowing partial fulfilment
- Status history with actor, note and timestamp
- Field-level edit history on any operator change
Refunds and Returns
A return opens with a reason and evidence, walks its own status machine, and settles as immediate wallet credit or back down the rail that took the payment.
- Refund request with reason and evidence
- Its own status machine preventing double-spend
- Instant wallet credit or gateway settlement
- Loyalty points reversed on cancellation
Four Wallets
Buyer, seller, agent and operator balances held apart, each debit and credit paired with a history row written inside the same database transaction.
- Customer, vendor, deliveryman and operator wallets
- Append-only history row per balance movement
- Top-up through any configured gateway
- Add-fund bonus tiers set by the operator
Loyalty and Referral
Points earned on order value or per category, redeemed at checkout, convertible to wallet balance, plus referral codes rewarding both sides.
- Points earned on order value or per category
- Redeemed at checkout against the order total
- Converted to wallet balance on request
- Referral codes rewarding both sides
Delivery and Cash
Assignment feed with accept and reject, pickup and delivery checkpoints, live location, a code verified at the door, and a cash-collected balance carried per agent.
- Assignment feed with accept and reject
- Live location broadcast while in transit
- One-time code verified at the door
- Cash collected tracked per agent and reconciled
Reviews and Chat
Ratings and reviews with photo upload, seller replies, buyer-to-seller chat with attachments, and a threaded support ticket queue.
- Ratings and reviews with image upload
- Vendor replies on any review
- Customer to vendor chat with attachments
- Support tickets with threaded conversations
Note for buyers: every feature above is white-label and can be enabled or disabled per deployment from the admin console. Nothing in this list requires a code change to turn off.
Monetization
Noon Clone Revenue Models: Commission, Subscriptions, Delivery and Placement
Six revenue lines run on one ledger and combine against a single order. What changes across the Gulf is which of them carries the weight: commission holds up in a high-basket market, delivery margin and the cash handling fee matter more on a cross-border route, and seller plans keep paying in a slow month.
Commission on Sales
A percentage set globally, per category, per seller or per product, taken from the seller wallet when the order completes and reversed automatically on refund. Per-category bands matter where margins differ sharply by vertical.
Seller Subscriptions
Tiered packages carrying product-count limits, reduced commission, featured placement and priority support, billed on a cycle with a trial and a grace period on failure. Revenue that does not move with basket size.
Delivery and Cash Handling
A mark-up on the shipping charge, a handling fee on cash orders, and a settlement fee when an agent withdraws. On a cross-border route these cover what a single commission rate never does.
Featured Placement
Paid banner slots, sponsored positions on search and category pages, and a participation fee for sellers joining a time-boxed flash deal. Sold as position rather than as a share of a sale.
Wallet Float
Buyer top-ups and seller balances rest with the platform between payout runs, and add-fund bonus tiers give you a lever to encourage larger top-ups.
White-Label Deployment
The platform is itself sellable. Agencies and networks stand up a branded marketplace per client or per state from one codebase they already know.
Want a revenue model that fits your market? commission bands, subscription tiers and delivery margin are all operator-set. Book a call and we will map the levers against the volumes you actually expect.
Control Center
Noon Clone Admin Dashboard: Catalog, Orders, Payouts and Configuration
Running several markets from one console means the configuration surface matters as much as the daily queues. Currencies, tax zones, delivery countries and languages all live here, and every module sits behind its own permission, so a finance clerk settles payouts without reaching catalog and a moderator approves products without touching market settings.
Operator Control
Market Configuration
Currencies with their rates and defaults, tax classes bound per zone, delivery countries and zip allowlists, and languages. This is the tab a new state is opened from, and it is where most of the work of a second market actually happens.
Catalog Moderation
A queue of seller-submitted products with approve, reject and bulk actions, full editing rights over any listing, and control of the category, brand and attribute libraries.
Cross-Seller Orders
Every order across every seller with a status timeline, field-level edit history, expected-delivery changes, manual override with a reason, and invoice generation carrying the right tax line.
Refund Queue
Requests with reason and evidence, approve or reject with a note, and settlement issued either to the customer wallet or back through the gateway that took the payment.
Payouts and Cash Settlement
Seller and agent payout requests with approve, deny and mark-processed, alongside each agent collected cash settled against the operator wallet. On a cash-heavy book this is the first screen of the day.
People and Approval
Customer directory, seller approval and suspension with subscription management, and agent approval, suspension and zone assignment per market.
Marketing Surface
Banners, flash deals, featured deals, the daily deal, platform and per-seller coupons, and composers for push, email and SMS campaigns.
Tax Configuration
Tax classes and rates bound per zone, per-product tax rules through a polymorphic binding, inclusive or exclusive display, and a per-order tax line breakdown.
Business Settings
Commission, loyalty ratio, the lifetime of the code used at handover, shipping methods and per-category cost overrides, all configuration rather than code.
- Currencies with operator-set rates and a default per market
- Tax classes and rates bound per zone
- Delivery countries and zip allowlists
- Languages and entity-level translation
Reports and Exports
Sales, seller, product, customer, wallet, refund, withdrawal and tax reports over any date range, exported to Excel, CSV or PDF, which is what a VAT period is assembled from.
- Cash carried per agent and settled to the operator
- Refund and withdrawal queues with counts
- Gross merchandise value and orders by market
- Per-route SEO metadata and an auto-generated sitemap
Need deeper governance? age-gated categories, country-specific catalog rules, per-vendor document expiry or a four-eyes approval on payouts can all be added as custom modules. Ask and we will scope it.
Pricing
How Much Does It Cost to Build a Noon Clone App in 2026?
The white-label platform is $2,499 as a one-time purchase, deployed in six working days. That covers the 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. Built from scratch this is an eighteen to thirty month programme with a senior team, and assembled from separate commerce, logistics and payout products it becomes three subscriptions, three security reviews, and a cash and currency gap that nobody’s roadmap owns. What the fixed price does not include is anything properly yours: gateway merchant credentials, an SMS and email provider, a Firebase project, an OpenAI key, catalog data, translated product copy, and the VAT rates you configure per state. Anything beyond the base, extra markets, right-to-left layout, VAT export or processor-side verification, is scoped and quoted separately, typically two to eight weeks.
Not sure which option
is right for you?
Talk to us - we'll understand your goals, timeline, and budget, and point you to exactly what you need. No upselling, just honest advice.
Deliverables
What's Included: Noon Clone Source Code, Apps and Deployment
What transfers is the whole system, configured for the markets you actually sell into, not a licence to operate somebody else’s platform.
Market Configuration
Currencies with their rates, tax classes per zone, delivery countries and zip allowlists, and languages, all set up with you at deployment rather than left as a first-week discovery.
- Currencies, tax zones and delivery countries configured with you
- Languages enabled and the translation store ready
- Fully branded Android app for your customers
- Browse, search, cart, checkout and order tracking
Seller App
The seller surface on mobile: products, stock, the order queue, refund responses, customer chat, wallet and withdrawal requests.
- Branded Android app for your vendors
- Product CRUD, stock and order queue on mobile
- Refund responses and customer chat
- Wallet balance and withdrawal requests
Delivery App
The agent surface, and the one that decides whether cash works: assignments, navigation, status checkpoints, verified handover, collected cash and earnings with a payout flow.
- Branded Android app for your delivery agents
- Assignment feed with accept and reject
- Live location and OTP proof of delivery
- Earnings, cash collected and payout requests
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.
- Customer web storefront with full search
- Vendor web panel for shop and catalog management
- SEO-friendly product and category pages
- Responsive across desktop, tablet and mobile
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 rather than a phone.
- Operator console with role-scoped staff accounts
- Granular permission system per module
- Vendor approval and product moderation
- Commission, coupons and payout processing
Operator Console
Moderation, cross-seller orders, refunds, agent settlement, payouts, people, marketing, tax zones and market configuration, with role-scoped staff access from day one.
- Complete Laravel 12 source, no encrypted files
- REST API v1, v2 and v3 serving every client
- 131-table schema with reversible migrations
- Modular structure for AI, Blog and Tax
Full Source Code
The Laravel 12 backend and all three Flutter projects transferred into your repository, unobfuscated, with no licence callback of any kind.
- App name, logo, splash screen and colour theme
- Branded transactional email templates
- Custom domain configuration
- Full white-label across every surface
Deployment and Handover
Installed on your infrastructure with queue, scheduler and storage running and your markets configured, then an admin walkthrough and the configuration checklist.
- Server setup on your preferred provider
- Queue worker, scheduler and storage configured
- 60 days of launch guidance
- 6 months of priority bug fixes, 12 months of updates
Want to see exactly what you get? book a walkthrough and we will open the storefront, the vendor panel, the delivery app and the operator console with live data, then show you the repository structure you would be taking ownership of.
Explore Every Angle of the Noon Clone
Four deeper guides covering the feature set, the fixed price, how to judge a builder, and how the model earns across more than one currency.
Features
The full role map across buyer, seller, rider and operator, with tax classes bound per zone and operator-set exchange rates built into the schema instead of bolted on later.
See the full breakdown →Development Cost
One fixed $2,499 rather than a per-country quote, set against agency and custom ranges, plus the six working days to live and the gateway approvals each market needs.
See exact pricing →Development Company
How to judge a builder for a multi-country launch: source ownership, how currency and tax are modelled, and the audit trail behind every converted order.
Compare options →Business Model
Six revenue lines running across several markets at once: commission, seller plans, fulfilment fees, placement, wallet float and white-label licensing.
See the playbook →Built For
Who Is Our Noon Clone App Built For?
These operators share one shape: more than one market, each with its own currency, tax treatment and delivery reality, and no appetite for running a separate platform per state.
Regional Retail Groups
Vertical Marketplace Founders
COD-Heavy Markets
Distributors Going Direct
Franchise and Multi-Location Networks
Agencies and White-Label Resellers
If your business depends on catalog, vendors, fulfilment or repeat purchase, this platform is the substrate. Book a call and we will tell you honestly whether it fits your model or whether one of our adjacent solutions is the better start.
Where It Fits
Noon Clone Use Cases: Retail, Grocery, Fashion & Cross-Border
The platform is identical in every case below. What differs is how many markets it is configured for, and which of currency, tax, delivery or cash is the awkward one.
General Retail Marketplace
A regional marketplace with sellers across many categories, an unlimited category tree, brand pages and a moderation queue holding quality. Commission and seller plans carry the revenue, and your own fleet keeps the last mile, and the cash, under your brand rather than an aggregator.
Grocery and Daily Essentials
Grocery leans on what other commerce platforms treat as edge cases: stock that turns over in hours, restock subscriptions telling buyers when an item returns, a clearance storefront for short-dated goods, and cash collected at the door on a daily delivery rhythm.
Fashion and Lifestyle
Fashion is a variant problem before it is anything else. Colour and size collapse into SKU rows with their own price and stock, galleries carry the range, and photo reviews do work that description copy never manages.
Electronics and High-Value Goods
High-value electronics need the audit surface most. Every order carries a status history and a field-level edit log, the verified handover proves delivery happened, and the refund pipeline holds a defensible record when a dispute lands weeks later.
Digital Goods and Media
Digital goods need no courier and no serviceability rule. Downloadable products carry their own variants and a single-use access check, with authors and publishing houses modelled for book and media catalogs.
Cross-Border Commerce
A regional rollout leans on all four at once: the currency table quoting each buyer in their own money, per-zone tax profiles carrying different VAT rates, delivery country codes and zip allowlists bounding the promise, and the translation store holding catalog content per locale, all under one operator console.
Not sure which of these you are? most operators are a blend of two. Book a call and we will map your catalog, your vendor mix and your fulfilment model against what the platform already does.
Why Now
Why Launch a Multi-Vendor Marketplace in 2026?
The opening in this region is not that people have started shopping online. It is that a buyer in one state and a buyer two hours away across a border are treated as one market by platforms that price, tax and deliver as though they were, and as two by anyone willing to configure for both.
You Keep the Commission
Every order pays your rate rather than an incumbent one. On a business already moving meaningful volume through somebody else, the rate difference alone usually funds the build several times over.
You Own the Buyer
Phone numbers, order history, wallet balances and repeat-purchase behaviour sit in your database in every market you run, which is what makes direct marketing and a loyalty programme possible at all.
Supply You Already Control
Retailers holding stock, distributors with supplier relationships and networks with outlets start with the expensive half already solved. The platform is the missing piece rather than the business.
Cash Is Not an Edge Case
Where a large share of buyers still pay at the door, a platform that treats cash as an unpaid order leaves the reconciliation to you. Here it is a settlement path with its own ledger, fee and audit trail.
One Deployment, Several States
A currency, a VAT rate and a delivery rule per market from a single install. Competitors either run one blunt configuration across the region or maintain a separate platform per state, and both cost more than this does.
One Substrate, Not Five
Commerce, logistics, content, AI and payouts in one codebase means one contract, one data model and one security review rather than five of each, all needing to agree about what an order is.
Why Launch
131
Database Tables
114
Eloquent Models
13
Payment Gateways
3
Android Apps
The numbers below are platform facts, not market projections: they describe what ships in the build rather than what the sector is forecast to do. Market sizing varies by source and we would rather quote our own schema than someone else forecast.
Tech Stack
Noon Clone Tech Stack: Laravel 12, Flutter, MySQL and Redis
A deliberately ordinary stack, chosen so you can staff it locally. Laravel and Flutter developers are readily available across this region, which matters far more than novelty when you are hiring the person who maintains it after us.
Backend and Business Logic
PHP 8.2 · Laravel 12 · nWidart Modules
- Controller to service to repository to model, with transactions at the service boundary
- 114 Eloquent models over 131 normalized MySQL tables
- Modules for AI, Blog and Tax that enable and disable without touching core
- Observers, events and listeners driving notifications and ledger writes
Mobile Applications
Flutter · Dio · Provider with GetIt
- Customer, vendor and deliveryman builds from one shared architecture
- Sanctum bearer tokens with role claims for seller and delivery agents
- Firebase Cloud Messaging per app, with topic subscriptions
- Google Maps in the deliveryman build for pickup and drop-off routing
Data and Caching
MySQL 8.x · Redis 7.x · InnoDB
- utf8mb4 throughout, soft deletes on customer, vendor, agent and product rows
- Composite indexes on the hot paths, including vendor with status and created date
- Redis for cache, queue and session, with a database queue as fallback
- Append-only wallet histories so any balance can be re-derived
Payments and Settlement
Eleven gateways · Offline · COD
- Stripe, PayPal, Razorpay, Mercado Pago, Iyzico, PhonePe, Paytm, PayUZ, SSLCommerz, Flutterwave and PayTabs
- Signature verification at the webhook boundary, idempotent by gateway transaction id
- Operator-defined offline methods with manual verification
- Cash on delivery reconciled through a dedicated agent transaction table
Communications and AI
FCM · Twilio · Vonage · OpenAI
- Push through Firebase Cloud Messaging to all three apps
- SMS through Twilio or Vonage, email through SMTP or Amazon SES
- OpenAI for product descriptions, SEO copy and image alt text
- Per-feature token quotas with tokens and cost logged per call
Storage and Delivery
S3-compatible · Intervention · CDN
- AWS S3, DigitalOcean Spaces, Wasabi or MinIO through Flysystem
- Image optimization and responsive variants generated on a queue
- WebP conversion where the client supports it
- CDN recommended at the edge for static and media assets
Note for tech buyers: the Noon Clone is structured so your own team can take it over. Ordinary Laravel conventions, a documented schema, migrations that roll back, and clean module boundaries around anything custom.
How It Works
How the Noon Clone Works: Browse, Buy, Fulfil and Settle
One cross-border cash order, followed end to end. It is the version worth understanding because it touches the currency table, the tax zone, the serviceability rules and both ledgers on the way through.
How It Works
Discover and Add to Cart
The buyer is quoted in their own currency and shown only what can actually reach them.
- Currency default and locale resolved before the first price renders
- Serviceability checked against delivery country and zip allowlist
- Category tree, brand directory or keyword search with autocomplete
- A cart that can hold items from several sellers at once
Checkout and Pay
The cart splits by seller and every total resolves, in the right currency and at the right rate, before anything is dispatched.
- Tax applied from the zone rules for that destination
- Shipping chosen per seller, with per-category cost overrides
- Cash on delivery, an offline method, or one of eleven gateways
- Placement guarded by an idempotency check so a double submit cannot duplicate
Vendor Accepts and Packs
Each seller sees only their own portion of the order.
- Order lands in the seller queue with buyer and item detail
- Accepted or rejected with a reason, then marked packed and ready
- Stock decremented automatically at the SKU level
- Packing slip and invoice generated as PDF with the tax line
Assign and Collect
The operator or the auto-assignment job puts the order in front of an agent on that route.
- Assignment appears in the agent feed, accepted or rejected
- Navigation to the seller for pickup, then on to the buyer
- Live location broadcast while the order is in transit
- Status checkpoints written with a timestamp and a geo position
Verify and Hand Over
The step a card-first platform does not have, and the one that has to be provable weeks later.
- One-time code verified server side against a time-boxed record
- Cash counted and written to that agent own collected balance
- Order moves to delivered and the customer is notified on push, email and SMS
- Delivery trail retained for the SLA and dispute record
Settle and Reconcile
The money resolves across four wallets, and the agent still owes the operator until it does.
- Commission split between operator, seller and delivery agent
- Seller balance credited and the platform commission debited
- Collected cash reconciled off the agent balance into the operator wallet
- Every movement paired with an append-only history row and a reference id
Visual Flow Diagram
Browse → Cart → Checkout → Vendor Accepts → Assign Agent → Pickup → OTP Handover → Settle
Architecture
Noon Clone Platform Architecture and Backend Flow
Market Rules Resolved Once
Currency, tax zone and serviceability are decided in the service layer at request time, not assumed by whichever client is asking. That is why a price quoted in the app and a price quoted on the web never disagree.
Tax as a Module
Tax ships as an nWidart module with its own routes, migrations and providers, alongside AI and Blog. A state with an unusual treatment is extended there rather than in the core application.
Event-Driven Side Effects
Order placed, status changed, seller approved, payout requested and refund processed each emit an event, with listeners fanning out to notifications, ledger writes and analytics.
Queues and Scheduler
Redis-backed workers under Supervisor handle images, PDFs, mail, push and AI calls, while a cron scheduler runs commission recalculation, plan renewals, abandoned-cart reminders and backups.
Append-Only Ledgers
Wallet histories, order status histories, edit histories and refund transitions are written and never updated, so any balance, in any currency, can be replayed rather than trusted.
Horizontal Scale
A stateless application tier behind a load balancer, MySQL with read replicas carrying reporting, Redis for cache and queue, and S3 behind a CDN for media.
Build to Scale
Built to Scale: Catalog Depth, Order Volume and Fleet Load
Load in this region is seasonal in a way that punishes a thin architecture: Ramadan and the shopping festivals around it concentrate a disproportionate share of the year into a few weeks, and a cross-border order stays open longer than a domestic one. Both are answered in the build.
Seasonal Peaks
A festival fortnight can carry a quarter of the annual volume, which is a caching and queueing problem rather than a hardware one. The category tree, banners, settings and popular-product rails are served from Redis instead of being rebuilt per request, every list endpoint paginates rather than returning an unbounded set, and related models are eager loaded so the busiest views never fall onto the N+1 path.
Orders That Cross a Border Stay Open
A cross-border or cash order keeps receiving writes long after checkout, through dispatch, customs handling and settlement. Composite indexes sit on the access patterns that matter, seller with status and date, and agent with status, and closed orders older than twelve months move to an archive table on the same schema without breaking joins or reporting.
Queued Background Work
Images, invoices, reports, mail, push fan-out and AI enrichment all run as queued jobs under Supervisor, with failed jobs captured and retried on a backoff. A festival-week surge cannot stall a page render, and an SMS provider having a bad afternoon degrades notifications rather than checkout.
Fleet Write Volume
A fleet writes continuously while it is working, and a dense city route generates far more location traffic per order than a long cross-border one. Location updates run on their own queue rather than synchronously inside a request, and delivery histories become candidates for time-based partitioning once the fleet justifies it.
Built for Seasonal Spikes
A festival fortnight can carry a quarter of the year. Cached rails, paginated lists and queued side effects are what keep that from becoming an outage on the day it matters most.
Hot Tables Indexed
Orders, order details, notifications, chat and delivery histories carry composite indexes on the patterns that matter, including seller with status and date, and agent with status.
Async by Default
Image processing, invoice generation, email, push fan-out, AI enrichment and report building all run on queues, so none of them sit inside a customer request.
Fleet Write Load
Location updates go to their own queue rather than being written synchronously, and delivery histories are candidates for time-based partitioning as the fleet grows.
Search Headroom
MySQL full-text is enough to launch on. A dedicated engine slots in behind the same service interface when the catalog, or the locale count, outgrows it.
Archive Path
Closed orders past twelve months move to an archive table on the same schema, keeping the working set small without breaking joins or the reports a tax period is built from.
Search Across Languages
MySQL full-text and indexed columns carry the baseline and are enough for most catalogs. Where listings carry content in more than one locale the index gets harder, and Elasticsearch or Meilisearch drops in behind the same search service interface with sync on a queue, making it an infrastructure change rather than a rewrite.
Note for founders and CTOs: a new market does not need new architecture. What changes as states accumulate is process count behind the proxy, a CDN nearer those buyers, and read capacity on the database. The drivers change, the code does not.
Security
Noon Clone Security: OWASP-Mapped, GDPR-Ready and VAPT-Ready
Operating across several states raises the stakes on two of these. Customer data crosses a border with the order, and an agent carries cash that has to reconcile in whichever currency it was collected. The platform answers each with a mechanism rather than a claim: append-only ledgers written in the same transaction as the balance they move, so any wallet including an agent’s float can be re-derived rather than trusted; repository-level tenant scoping so no seller reads another’s orders; gateway-hosted payment fields so no card number reaches your server in any market; and location and contact data visible only to the agent and the operator.
Security headers are yours after handover
Rate limits ship at sane defaults, not tuned ones
Captcha is available and off by default
A WAF is recommended and not included
Two-factor is configurable, not mandatory
Dependency audits are a standing task
The Cash Trail Reconciles
Every movement of an agent collected balance writes a history row inside the same transaction as the balance change, so what a courier owes the operator is always derivable rather than merely recorded.
Privacy Across Borders
Soft deletes on customer, seller and agent rows, a per-user JSON export, deletion with a grace period before personal data is purged, and marketing requiring explicit opt-in, applied the same way in every market you operate.
Tenant Isolation
Seller and agent scoping enforced in the repository layer, model policies on read and write, and API token abilities mapped to permission slugs rather than one blanket scope.
Payment Integrity
No card number is ever stored. Webhook signatures verified at the boundary, transactions made idempotent by gateway id, and refunds guarded by a status machine against double-spend.
Injection and XSS
Eloquent parameterization throughout, form-request validation on every write endpoint, Blade output escaping, and Mews Purifier over rich-text fields such as descriptions and support replies.
Built to the Controls
Argon2id password hashing, encrypted session cookies with HttpOnly and SameSite, CSRF tokens on every state-changing route, and mass-assignment protection across models.
The honest position on certification: the controls below are built, and the platform is ready for a penetration test and for the evidence-gathering that ISO 27001 or SOC 2 require. Neither certificate is held, and neither is claimed. Several items are also deployment-layer responsibilities that we configure but you own after handover, and they are named as such below rather than folded into a compliance claim.
Advance Add-Ons
Noon Clone Add-Ons: Search, Analytics, Integrations and Automation
The base build covers the marketplace. These are the extensions operators ask for once volume arrives, quoted after scoping rather than bundled.
Right-to-Left Layout
The platform ships entity-level translation, so Arabic content is supported, but it does not ship a right-to-left interface. Mirroring the storefront, seller panel, console and the three apps is a scoped customization rather than a toggle, and we quote it rather than implying it is already there.
VAT and Accounting Export
Scheduled export of orders, tax lines, commission and payouts per state into your finance system, so a return period stops being a manual reconciliation across markets.
External Search
Elasticsearch or Meilisearch behind the existing search service with index sync on a queue, for catalogs, or language counts, where MySQL full-text has stopped being enough.
Loyalty and Membership Tiers
A paid membership carrying free delivery and member pricing, layered over the existing loyalty points and wallet, in the style buyers across this region now expect as standard.
B2B and Wholesale
Tiered pricing per buyer group, minimum order quantities, quote requests and credit terms, for operators serving trade buyers alongside retail.
Sponsored Placement Engine
A self-serve advertising surface where sellers bid for position on search and category pages, with budget control and delivery reporting.
Observability Stack
Prometheus and Grafana or an equivalent, log aggregation and OpenTelemetry tracing, for operators who need more than the built-in error log during a peak week.
iOS Builds
The three Flutter projects compiled, signed and submitted for the App Store, with the review cycle and the store assets handled alongside.
Building in Commerce and Logistics? We Have the Whole Market Covered.
The same foundations carry several adjacent products, and one sibling worth naming outright. If your model sits closer to any of these, start there rather than here.
Amazon Clone
The same marketplace platform positioned for general multi-vendor commerce rather than a multi-market Gulf rollout, leading on catalog, checkout, fulfilment and payouts.
Instacart Clone
Grocery marketplace with store partners, personal shoppers, substitution rules and weight-based pricing.
UberEats Clone
Food ordering with restaurant onboarding, menu management, order routing and a courier dispatch fleet.
Gojek Clone
Multi-service super app running ride-hailing, delivery, courier and a marketplace from one shared account.
Marketability
Marketability, Revenue Potential and Business Prospects
Adding a state is where this model earns. The catalog, the sellers, the apps and the ledger are already paid for, so the second market costs a currency, a tax zone and a delivery rule rather than another platform. The scenarios below are illustrative arithmetic on operator-set inputs, not a forecast and not a promise.
The Second Market Is Nearly Free
Catalog, sellers, apps and ledger are already paid for. Opening another state costs a currency, a tax zone and a delivery rule, which is why the economics improve with each market rather than each product.
Sellers Are Recurring Revenue
Subscription tiers turn a one-time onboarding into a monthly line, and the tier becomes the upsell path as a seller grows across your markets.
Delivery Is Margin, Not Cost
Your own fleet turns the shipping charge from a pass-through into a controllable margin, and the cash handling fee covers what it genuinely costs to collect money by hand.
The Asset Is the Footprint
A seller roster, a buyer database and a set of proven cross-border routes are worth more than the software. The platform is what lets you own all three rather than rent access to them.
- Commission on every order, set globally, per category or per vendor
- Vendor subscription plans with product limits and reduced rates
- Delivery margin on the shipping charge and a COD handling fee
- Featured placement and sponsored positions sold to vendors
- Settlement fee applied when a vendor or agent withdraws
- Wallet float held between payout runs, with add-fund bonus tiers
- An owned sales channel rather than a rented listing on another platform
- A customer database you can market to directly, with order history attached
- A vendor network that is an asset in its own right
- A commission rate you set rather than one set for you
- Last-mile delivery under your brand rather than an aggregator
- Source code that can be extended, licensed or resold
Example Revenue Scenarios
On these numbers: each scenario is arithmetic on inputs an operator chooses, shown to make the levers concrete. They are not projections, and Miracuves does not guarantee any commercial outcome. The six days is our deployment window for the base platform, not your route to market.
First state, then the second
Markets from one deployment
An operator proves the model at home, then opens a neighbouring state by adding a currency, a tax zone and a delivery rule rather than another platform.
Commission, delivery margin and the cash handling fee are all operator-set. The platform cost is one-time; what recurs is hosting, gateway fees and the team running it.
Cross-border seller
Working days to deployment
A distributor already shipping between states puts a branded storefront in front of it, pricing each market in its own currency and taxing each at its own rate.
Six days is our build time on the base. Catalog loading, seller recruitment and customs arrangements are operator work and set the real timeline.
Agency running white-label deployments
Codebase, many branded marketplaces
A studio deploys the same platform per client or per territory, each fully branded, from one codebase it already knows.
Per-deployment licensing is a commercial conversation rather than a page price. What the platform provides is the branding depth and module toggles that make repeat deployment practical.
Why Miracuves
Miracuves vs Other Noon Clone Developers
There are many ways to get a marketplace: generic commerce scripts, freelancers, agencies, or owning the platform outright.
Why Founders Choose Miracuves
One Deployment, Several States
Currency, tax zone, serviceability and language are per-market configuration on one install. Most scripts assume a single market and the workarounds start the day you open the second.
Cash Is in the Codebase
Most scripts stop at checkout and treat a cash order as unpaid, leaving the reconciliation to you. The fleet, the verified handover and the cash ledger are all in this codebase rather than behind an integration.
Source Code on Handover
Backend and all three Flutter projects land in your repository. Nothing obfuscated, no licence server phoning home, no dependency on us afterwards.
Six Working Days
Installed on your servers with queue, scheduler and storage running, and your markets configured. Nothing is being invented, so the week is setup rather than build.
Fixed Price, Not a Range
The number is $2,499 rather than starting at. Scope is written down before anything is built, and changes are quoted rather than absorbed silently.
Honest Readiness Labels
Configuration-required and integration-required items are marked throughout. Right-to-left layout is named as a scoped customization rather than implied, and VAT is modelled rather than filed.
Compare & Discover Why Operators Choose Us for Multi-Vendor Commerce
| Criteria | Miracuves Noon Clone | Generic Clone Script | Custom Dev Agency |
|---|---|---|---|
| Time to Launch | 6 days (Production) | Unknown / DIY | 6-9+ months |
| Source-Code Ownership | ✔ Full | Often limited / encrypted | Usually yes |
| Feature Depth (Noon-like) | High (catalog, payouts, fleet) | Basic (single-vendor storefront) | Depends on budget |
| Security & Compliance | Strong (built to the controls, GDPR-ready) | Minimal | Varies widely |
| Scalability & Performance | Cloud & CDN-optimized | Rarely considered | Depends on architecture |
| Monetization Options | Multiple (commission, plans, delivery) | Usually commission only | Custom (more time & cost) |
| Admin & Analytics | Full-fledged dashboard | Very basic or missing | Custom build (extra cost) |
| Cost vs Speed vs Quality | Balanced | Cheap but risky | High cost, slow |
| Ongoing Support & Updates | Available with clear plans | Usually none | Depends on contract |
The comparison that decides this one is not feature count, it is what happens when you open the second state. Most scripts assume one currency, one tax rate and one delivery promise, and the workarounds start immediately.
Industries
Industries We Serve
The Noon Clone suits operators whose buyers sit in more than one market. Regional retail groups price per currency and tax per zone. Cross-border distributors bound the promise with delivery countries and zip allowlists. Grocery leans on fast stock movement, restock alerts and clearance. Fashion uses the SKU-level variant matrix and photo reviews. Electronics needs the audit trail and verified handover on high-value orders. Pharmacy uses moderation and controlled catalog access. Franchise networks run per-location inventory under one console, and agencies deploy the whole thing per client or per state.
- 🛒 General Retail
- 🥬 Grocery & Essentials
- 👗 Fashion & Apparel
- 📱 Electronics
- 💊 Pharmacy & Wellness
- 📚 Books & Media
- 🏭 Distribution & Wholesale
- 🏪 Franchise Networks
- 🎨 Handmade & Artisan
- 🌍 Cross-Border Retail
Miracuves Noon Clone is built as a marketplace-first commerce platform for operators selling across several markets at once: priced per currency, taxed per zone, delivered by your own fleet, and white-labelled entirely under your brand.
Version History
Release Log
| Version | Date | What's New |
|---|---|---|
| v4.0 | Aug 2026 | Laravel 12 upgrade. AI module for catalog copy and SEO. Clearance storefront and restock subscriptions added. |
| v3.6 | 2025 | Deliveryman app with OTP proof of delivery, live location and a cash-collected ledger. |
| v3.4 | 2025 | Vendor subscription packages with trials, grace periods and per-tier commission rates. |
| v3.0 | 2024 | Tax module with per-zone rates, wallet ledgers per actor and the refund status machine. |
Blog & Resources
Noon Clone App: Latest Insights and Guides
Guides on marketplace economics, vendor onboarding, delivery operations and the decisions that matter before you launch.
How Safe is a White-Label Noon App? Security Guide 2025
Last Updated on April 29, 2026 by sakshi You’ve heard the horror stories — eCommerce…
Business Model of Noon: How This Platform Makes Its Revenue
Last Updated on April 28, 2026 by Rutuja Gaikwad Business Model of Noon has rapidly…
Noon vs Amazon Business Models for Startups
Last Updated on May 5, 2026 by sakshi In the rapidly evolving world of e-commerce,…
Understanding the Revenue Model of Noon and Its Growth Engine
Last Updated on June 16, 2026 by Yash Narayan Key Takeaways Noon’s revenue model is…
How to Build Your Own Noon Clone – A Fullstack Developer’s Blueprint
Last Updated on April 27, 2026 by sakshi If you’re looking to build an eCommerce…
FAQ
Noon Clone FAQ: Pricing, Features, Payments and Deployment
Everything you need to know about the Miracuves Noon Clone App.
A ready-made multi-vendor marketplace built to serve several markets from one deployment. Buyers browse and purchase in their own currency, independent sellers list products and receive payouts, your own delivery agents close the last mile and collect cash where that is the habit, and you take commission on every transaction. It ships with a web storefront, a seller panel, an operator console of role-scoped modules, and three Flutter Android apps, all against one versioned REST API.
Same platform, different operating model on the page. The Amazon Clone is written for the general multi-vendor marketplace. This page is written for operators running several Gulf markets from one deployment, so it leads on currency per market, VAT bound per zone, cross-border serviceability and cash on delivery. Same product, same price. Choose by which description matches your footprint.
The white-label platform is $2,499 as a one-time purchase, deployed in six working days on your infrastructure with your branding. Custom modules and deeper changes are scoped and quoted separately, typically two to eight weeks depending on what you need.
Source yes: backend and all three Flutter projects land in your repository at handover, nothing obfuscated, no licence server checking in, and no reason to keep us on retainer. iOS no: the base price covers the three Android builds. The Flutter projects do compile for iOS, and App Store builds, signing and submission are quoted separately because the developer account and the review cycle are their own piece of work.
Eleven ship pre-integrated, including PayTabs which is the one most relevant to this region, alongside Stripe, PayPal, Razorpay, Mercado Pago, Iyzico, PhonePe, Paytm, PayUZ, SSLCommerz and Flutterwave. Operator-defined offline methods and cash on delivery are built in too. Every gateway needs your own merchant credentials, which is why they are labelled integration-required rather than included.
Agents are a first-class identity with KYC and operator approval rather than a flag on a customer account, with an assignment feed, navigation to seller and buyer, live location, status checkpoints and a wallet carrying earnings and collected cash. Cash is the part worth understanding: the code is verified server side at the door, the money writes to that agent own balance, and it settles into the operator wallet through a dedicated transaction table rather than sitting as an order that simply never got paid.
Yes. Sellers register with KYC, are approved by an operator, then run their own shop: product CRUD with variants and stock, bulk import and export, AI-assisted descriptions, per-locale content on a listing, an order queue, refund responses, analytics and a withdrawal flow, from the web panel or the Android app.
A percentage set globally, per category, per seller or per product, deducted from the seller wallet when the order completes and reversed automatically on refund. Per-category bands matter across this region, because electronics and apparel rarely tolerate the same rate. Seller subscription tiers can carry reduced rates as a paid benefit.
Arabic content yes, right-to-left layout no, and the distinction matters. A polymorphic translation store holds interface and content strings per locale, so listings, categories and pages can all carry Arabic. What does not ship is a mirrored interface across the storefront, seller panel, console and three apps. That is a scoped customization we quote, and we would rather tell you now than let a demo suggest otherwise.
Both are per-market configuration. Each currency carries an operator-set exchange rate rather than a live feed, and the default decides what a buyer is quoted at checkout, so a dirham price and a riyal price are each a decision you make rather than a number that moves overnight. VAT runs through the tax-class system: classes bind per zone, per-product rules attach through a polymorphic binding, display is inclusive or exclusive per market, and every order carries a tax line. Five percent in one state and fifteen in another is configuration. Filing is not included.
It drafts product descriptions, SEO titles and descriptions, tag suggestions and image alt text through OpenAI, with per-feature token quotas and a log recording tokens and cost per call. It runs on your own OpenAI key, so it is integration-required. Note it drafts in the language you prompt it in; it is not a translation service for your catalog.
The controls are built: Argon2id hashing, CSRF protection, parameterized queries, HTML sanitization, tenant scoping, webhook signature verification, and append-only ledgers covering the cash trail. It will stand up to a penetration test and to ISO 27001 or SOC 2 evidence gathering. We hold neither certificate and claim neither.
Anything properly yours: gateway merchant approval, an SMS and email provider, a Firebase project, an OpenAI key, catalog data, translated product copy, seller recruitment, the VAT rates you configure per state, and app store review. Six days is our deployment window for the base platform, not your route to market.
Let's turn your idea into
a live platform.
Get a free consultation, a clear timeline, and honest answers. We'd rather earn your trust than rush a sale.
