A customizable Noon-style e-commerce marketplace platform
We propose an original build that reproduces the familiar flows of this product category under your branding. It is not Noon's product, and there is no affiliation with or endorsement by Noon. Scoped and quoted in writing before any build starts.
Proposed architecture - one API behind every screen
What it typically includes
- Seller onboarding, catalog and order management
- Payments, split payouts and commission rules
- Reviews, promotions and admin tooling
The exact feature list is agreed in writing for your project - nothing on this page is a fixed bundle or a fixed price.
Scope areas for this kind of build
The areas below are condensed from our earlier product specification for this category. They describe proposed scope we can build for you, not a finished product for sale, and no live system is implied. The exact list is agreed in writing for your project before any build starts.
Overview
Every Market Gets Its Own Currency and Tax
- Prices, payouts, refunds and invoices all resolve in the local currency at the local VAT rate, so a second country is configuration rather than a parallel deployment.
Cross-Border Without Losing the Cash Habit
- Serviceability spans borders while cash on delivery stays fully ledgered, because the markets that need multi-currency are usually the same ones still paying in cash.
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
- Trace: Search, Product, Cart, Tax, Checkout, Orders
The Same Storefront on Android
- Install the Android buyer build
- Trace: Home, Search, Cart, Order Tracking, Wallet
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
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
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
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
- A written preview 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.
Marketplace illustrative scenarios: India and Thailand
How the proposed platform would be 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.
Thailand Provincial and Cross-Border Marketplace
What Is a Noon Clone App?
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
Noon Clone Features: Catalog, Checkout, Fulfilment and Payouts
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
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.
- Zip allowlists deciding where checkout is offered
- Inclusive or exclusive tax display per market
Cross-Border Serviceability
- 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
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
Checkout and Coupons
- Coupon, wallet and loyalty applied together
- Flat or percentage, scoped to product, category or cart
- 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
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
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
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.
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 - Customer Funds
- Buyer top-ups and seller balances would rest with the platform between payout runs. They remain customer funds, not platform income - whether any yield on them may be retained depends on regulation and payment-provider terms. Add-fund bonus tiers are a proposed lever to encourage larger top-ups.
White-Label Deployment
- As a scoped option, the platform could itself be sellable: agencies and networks would stand up a branded marketplace per client or per state from one codebase.
- Want a revenue model that fits your market? commission bands, subscription tiers and delivery margin are all operator-set. Message us and we will map the levers against the volumes you actually expect.
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.
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
- 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
What an engagement can include
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
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
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
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
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
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 (version confirmed in writing) source, no encrypted files
- 131-table schema with reversible migrations
- Modular structure for AI, Blog and Tax
Full Source Code
- The Laravel (version confirmed in writing) 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
Deployment and Handover
- Installed on your infrastructure with queue, scheduler and storage running and your markets configured, then written admin notes and the configuration checklist.
- Server setup on your preferred provider
- Queue worker, scheduler and storage configured
- Want to see exactly what you get? Message us and we will describe the storefront, the vendor panel, the delivery app and the operator console in writing; repository and handover terms are agreed in writing before work starts.
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.
If your business depends on catalog, vendors, fulfilment or repeat purchase, this platform is the substrate. Message us and we will tell you honestly whether it fits your model or whether one of our adjacent solutions is the better start.
Noon Clone Use Cases: Retail, Grocery, Fashion & Cross-Border
The platform is identical in every case below. What differs is how many markets the proposed build would be configured for, and which of currency, tax, delivery or cash is the awkward one.
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.
Technology options we may propose
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.
PHP 8.2 Laravel (version confirmed in writing) nWidart Modules
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
- 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
How we would approach the architecture
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.
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.
How we would design for scale
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.
Security and privacy requirements we can design for
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
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
- The proposed design stores no card numbers: webhook signature verification at the boundary, transactions 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.
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.
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.
- The three Flutter projects compiled, signed and submitted for the App Store, with the review cycle and the store assets handled alongside.
Building in eCommerce? 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.
The flagship multi-vendor marketplace: catalogue, cart, payments, reviews, seller onboarding and the commission engine.
Describe your e-commerce marketplace project
Tell us your market and audience, and we will respond with a practical read on scope.
More app categories we work on
Proposed bases we scope the same way, grouped by category - open a group to browse. The full solution catalogue lists everything.
Food delivery (13)
ChowNow, Deliveroo, Delivery Hero, DoorDash, Glovo, Goldbelly, Grubhub, HungerStation, Justeat, Swiggy, Talabat, UberEats, Zomato
Platform (13)
Agrimove, Astrosage, Astrotalk, Bet365, Bolt New, Threads, Tiktok, Twitter, Walmart, Whatsapp, Wise, X, Yatra
E-commerce (5)
Short drama (5)
Ai assistant (4)
Stays (4)
Crypto launchpad (3)
Delivery (3)
Boat charters (2)
Cloud storage (2)
Crypto marketplace (2)
File transfer (2)
Logistics (2)
Streaming (2)
Trading (2)
Travel (2)
Website builder (2)
Ai platform (1)
Ai video (1)
B2b marketplace (1)
Alcohol delivery (1)
Alcohol marketplace (1)
Boat rentals (1)
Calling (1)
Cannabis marketplace (1)
Car rentals (1)
Digital banking (1)
Email (1)
Email marketing (1)
Fashion e-commerce (1)
Food and grocery (1)
Group e-commerce (1)
Home services (1)
Investing (1)
Jobs (1)
Jobs and reviews (1)
Liquor delivery (1)
Live streaming (1)
Local services (1)
Marketing automation (1)
Marketplace (1)
Messaging (1)
Multi-service (1)
Multi-service delivery (1)
On-demand delivery (1)
Professional network (1)
Property rentals (1)
Ticketing (1)
Video (1)
Video conferencing (1)
Wine marketplace (1)
Discuss your scope by message
Tell us what you want to launch and where. We reply by email with a scoped proposal - no calls required, no phone numbers collected.