Noon Clone Features: One Catalog, Several Markets
Selling into a second state multiplies the things that have to agree. The same product needs a price in another currency, a tax treatment that differs, a delivery promise that only holds for some destinations, and a settlement path for a buyer who pays cash at the door days later. The recorded scope models all four in the schema rather than leaving them to operator discipline. Here is what the recorded base build states, grouped by who touches it - confirm each item in writing and in your own acceptance testing.
The original page's deployment-day schedule, delivery-day claims and fixed price are excluded as unverified here: timeline, support scope and price are set in the written terms. Figures below are recorded properties of the platform, not measured results. Demo availability is confirmed in writing, not asserted.
What Opening a State Actually Touches
Six configuration moves, recorded scope - a new market is opened from a settings tab, not from a migration.
01
Currency added, operator sets the rate
02
Tax class bound to the new zone
03
Country code and zip allowlist opened
04
Shipping cost overridden per category
05
Locale enabled, translations filled
06
Agents approved and zoned
Feature Set by Role
Six surfaces run against one REST API, so the grouping that matters is not web against mobile - it is who is holding the screen. Four identities, four sets of permissions, four wallets. Every line below is recorded scope from the original listing, to confirm in writing and on the demo.
Customer
- Prices quoted in the currency of their own market - recorded scope
- Category tree of unlimited depth, brand directory, autocomplete search - recorded scope
- Product pages carrying the variant matrix and photo reviews - recorded scope
- One cart spanning several sellers at once - recorded scope
- Guest cart tracked by session and merged on login - recorded scope
- Coupon, wallet credit and loyalty points stacked on one order - recorded scope
- Tax shown inclusive or exclusive per market, itemized on the invoice - recorded scope
- Return opened with a reason and evidence, refunded to wallet or gateway - recorded scope
Seller
- Registers with KYC, approved and suspendable by an operator - recorded scope
- Product CRUD with the variant matrix, stock and bulk import - recorded scope
- Per-locale content on a listing, not one shared description - recorded scope
- AI-assisted descriptions, SEO titles and image alt text - recorded scope
- Order queue with accept and reject, plus refund responses - recorded scope
- Commission visible on the wallet, not reconciled after the fact - recorded scope
- Sales analytics and a withdrawal request flow - recorded scope
- Web panel or Android app against the same API - recorded scope
Delivery Agent
- First-class identity with KYC, approval and zone assignment - recorded scope
- Assignment feed with accept and reject - recorded scope
- Navigation to the seller for pickup, then to the buyer - recorded scope
- Live location broadcast while in transit - recorded scope
- One-time code verified at the door before handover - recorded scope
- Earnings held separately from cash collected - recorded scope
- Cash balance carried per agent, settled to the operator - recorded scope
- Payout request flow from the app - recorded scope
Operator
- Currencies, tax zones, delivery countries and languages in one tab - recorded scope
- Catalog moderation queue with approve, reject and bulk actions - recorded scope
- Cross-seller orders with a full status timeline - recorded scope
- Refund, payout and withdrawal queues - recorded scope
- Agent cash settled against the operator wallet - recorded scope
- Commission set globally, per category, per seller or per product - recorded scope
- Every module behind its own permission - recorded scope
- Reports over any date range, exported to Excel, CSV or PDF - recorded scope
The operator console is treated as a role rather than an afterthought because running several markets from one deployment makes the configuration surface as busy as the daily queues. A new state is opened from a settings tab, not from a migration.
Noon vs Omnistu Clone vs Building From Scratch
The same capability, three different paths. The rows that separate them are all multi-market rows - the places where a single-country commerce script quietly assumes there is only one answer. The original asserted what the original Noon does internally; a real company's mechanisms are not verifiable from this page, so that column is now what to verify against Noon's own published materials, and the generic-script column is what to ask any bidder. The Omnistu column is recorded scope to confirm against the signed terms.
| Capability | Original Noon - what to verify | Omnistu Clone - recorded scope | Single-market script - what to ask |
|---|---|---|---|
| Currency per market | Ask how many currencies it prices in natively, and who sets the rate | A currency catalog with operator-set rates; the default drives what each buyer is quoted at checkout | Ask whether it is one base currency with display conversion at best |
| Tax that differs by state | Ask how differing state rates are modelled, and who maintains them | Tax classes bound per zone with per-product rules through a polymorphic binding, inclusive or exclusive per market | Ask whether it is one tax rate, or a plugin bolted on later |
| Where you can actually ship | Ask how serviceability is gated before checkout | Delivery country codes and zip allowlists deciding whether checkout is offered at all, plus per-category shipping overrides | Ask whether it is flat shipping zones with no serviceability gate |
| Catalog in more than one language | Ask whether listings carry their own content per locale | Entity-level translation, so a listing carries its own content per locale rather than one shared description | Ask whether only interface strings are translated, catalog not |
| Cash on delivery | Ask whether COD is a settlement path with its own ledger or a payment-method flag | A settlement path: code verified at handover, cash balance per agent, operator-set handling fee, reconciliation to the operator wallet | Ask whether there is any accounting behind the flag |
| Money held per actor | Ask how many wallets exist and whether movements are re-derivable | Four wallets - buyer, seller, agent, operator - each with an append-only history written inside the same transaction as the balance move | Ask whether it is one balance field updated in place |
| Delivery fleet | Ask how delivery agents are identified, zoned and verified | Agent identity with KYC, approval, zone assignment, assignment feed, live location and verified handover | Ask whether a fleet exists at all, or only a courier webhook |
| Source code | Ask whether source is available at all | Recorded as the complete Laravel 12 backend and all three Flutter projects, unobfuscated, no licence callback - confirm each term in the signed agreement | Ask whether files are encrypted or a licence check phones home |
| Time to live | Ask for a committed timeline and acceptance criteria in writing | Timeline and milestones set in the written plan; the original published day schedule is excluded here as unverified | Ask the same - and ask what the multi-market gaps add to it |
The last four rows are the ones that decide a rebuild. A script that treats currency as a display filter and tax as a single percentage will carry your first market and then quietly fail your second - test each row rather than take the claim.
How It Works, End to End
One order, traced across four identities and two currencies, with every state change and every wallet movement written down. Every mechanism described is recorded scope; ask to watch the full trace on the demo.
01. The market decides what is possible
Before a price is shown, the buyer market sets three things: which currency the catalog is quoted in, which tax class applies to each line, and whether the destination zip is served at all. A zip outside the allowlist does not get a shipping quote and a checkout to abandon - it does not get a checkout.
02. The cart spans several sellers
One cart can hold items from several sellers at once, each with its own shipping estimated before checkout. A guest cart is tracked by session and merged into the account on login, so the basket built before signing in is not lost.
03. Checkout stacks the discounts and applies the zone
A coupon, wallet credit and loyalty points can all apply to the same order. Tax comes from the zone rules with per-product overrides, and it is displayed inclusive or exclusive according to the market. Placement is guarded by an idempotency check, so a double submit does not become two orders.
04. The seller works a queue, not an inbox
The order lands in a seller queue with accept and reject, from either the web panel or the Android app. Stock moves, commission is visible on the seller wallet from the outset, and a rejection walks its own path rather than being handled by email.
05. The agent carries the parcel and, often, the cash
An assignment appears in the agent feed with accept and reject. Navigation runs to the seller for pickup, then to the buyer. Location broadcasts while in transit, checkpoints record picked up through to delivered, and a one-time code is verified at the door before the parcel changes hands.
06. Four balances move, and each move is written down
On completion the commission splits, the seller balance credits, the agent earning credits, and on a cash order the collected amount lands on the agent cash balance rather than being mixed with earnings. Every one of those movements pairs with an append-only history row written in the same database transaction, so any balance can be re-derived rather than trusted.
07. Settlement closes the loop
The agent settles collected cash against the operator wallet. Seller and agent payout requests queue for approval, denial or mark-processed. Settlement records are held per gateway and per currency, which is what makes a second market reconcilable rather than merely functional.
Nine order statuses carry an order from pending payment through to delivered, with cancelled, returned and failed ending it. Every move is stamped into a status history with the actor, a note and a timestamp, and any operator edit leaves a field-level record - recorded scope.
Every Feature Earns Its Place
Feature lists are cheap. These are the ones that exist because a specific thing goes wrong in a multi-market marketplace without them. None of these are exotic - they are the nine places where a marketplace that was only ever going to serve one country stops being extendable.
| Capability | Why it is not optional |
|---|---|
| Operator-set exchange rates | Rates are set by the operator rather than pulled from a live feed. A feed that moves overnight reprices a whole catalog without anyone deciding to, and both sellers and buyers find out at checkout. A price in each market is meant to be deliberate. |
| Polymorphic tax binding | Tax classes bind per zone, and a per-product rule can override the class. That is what lets different rates in different states be a configuration change rather than two deployments - and what puts a defensible tax line on every invoice. |
| Zip allowlists ahead of checkout | Serviceability is decided before a checkout is offered, not after the order is taken. The alternative is an order you accept and then cancel, which costs you the customer and the seller their committed stock. |
| Per-category shipping overrides | A cross-border route and a dense city route do not cost the same to serve, and a single flat rate makes one of them subsidise the other. Shipping methods carry per-category cost overrides so both can be priced honestly. |
| Entity-level translation | A listing carries its own content per locale rather than sharing one description across markets. Interface translation is table stakes; catalog translation is what decides whether the second market converts. |
| Cash separated from earnings | An agent wallet keeps money earned apart from money collected. Merge them and the first reconciliation gap is unrecoverable, because there is no longer a record of which was which. |
| Idempotency on order placement | A guarded placement means a slow network and an impatient tap do not become two orders, two commission splits and one very awkward refund conversation. |
| Field-level edit history | When an operator changes an expected delivery date or overrides a status, the change is recorded with the actor and a reason. Weeks later, when a dispute lands, that record is the difference between a defensible position and a guess. |
| Settlement per gateway and per currency | Settlement records are held per gateway and per currency rather than pooled. Pooling works until the day a payout in one currency has to be traced against takings in another. |
The Technology Behind the Features
Deliberately ordinary choices, because the developers who maintain this after handover should already know all of it. All recorded scope.
Backend and data
- Laravel 12 on PHP 8.2, organised into nWidart modules so AI, Blog and Tax are separable rather than tangled through the core
- 131 normalized MySQL tables with reversible migrations, soft deletes on customer, seller, agent and product rows, composite indexes on the hot paths, and append-only wallet histories
- Redis 7 for cache, queue and session, with a queue worker and scheduler configured at deployment
API, mobile and payments
- One REST API in versions v1, v2 and v3 serving the storefront, the seller panel, the operator console and all three Flutter clients - six surfaces, one contract
- Three Flutter Android projects - buyer, seller and delivery agent - recorded as transferred into your repository unobfuscated; the projects compile for iOS and store builds are quoted separately
- Eleven gateways recorded as integrated, plus operator-defined offline methods and cash on delivery, with settlement records held per gateway and per currency
Why the schema size is the number that matters
A hundred and thirty-one tables is not a boast, it is a consequence. Currencies, tax classes, zone bindings, delivery country codes, zip allowlists, translation entries, four wallet histories, nine order statuses with a status history and a field-level edit log all need somewhere to live. A marketplace that models the same business in forty tables has made some of those someone else's problem.
The recorded scope states everything above transfers into your repository, with no encrypted files and no licence callback of any kind. Confirm each term in the signed agreement, because ownership is a contract term, not a page claim.
What Is Not Included in the Base Package
Everything above is recorded scope in the base build; ask for any of it to be opened on the demo, with availability confirmed in writing rather than asserted here. These are not included, and the hub labels them configuration-required or integration-required rather than implying them away.
Right-to-left layout
Named on the hub as a scoped customization, not implied anywhere as included. In a Gulf-market platform this is the caveat worth reading twice - budget it explicitly rather than discovering it after launch.
iOS applications
Three Android builds are the recorded base build. The Flutter projects compile for iOS, quoted as an add-on with signing and store submission.
Additional markets beyond the ones configured at deployment
Your markets are set up with you during deployment. Further states, VAT export and processor-side verification are scoped and quoted separately; the original quoted a typical duration band, which is excluded here - your timeline is set in the written scope.
Gateway credentials
Eleven gateways are recorded as integrated; each needs your own merchant account and its own approval in each market you take payments in.
SMS and email provider
Integration-required - your accounts, your sender reputation, your deliverability.
Firebase project
Push notifications across all three Android apps run through your own Firebase project.
OpenAI key
The recorded AI module generates descriptions, SEO copy and alt text against your key, with per-feature token quotas and a log recording tokens and cost per call.
Catalog data and translated copy
The translation store is ready and empty. Products, imagery, seller recruitment and the translated product copy are the business, and they are yours.
Tax rates per state
Tax classes bind per zone, but the rates for your jurisdictions are yours to set, and yours to keep current.
ISO 27001 and SOC 2
Neither certificate is held and neither is claimed. The recorded scope states the platform is built so the evidence gathering is possible; the certification is a separate programme and an audit of your operation, not of code.
Exchange rates being operator-set is listed here as a design decision rather than a gap. A marketplace that silently reprices a catalog against a live feed surprises sellers and buyers at the same moment, and in a multi-currency book that surprise is expensive.
Frequently Asked Questions
Can one deployment really serve several countries?
That is what the recorded scope is built around: currencies carry operator-set rates with a default per market, tax classes bind per zone with per-product overrides, delivery country codes and zip allowlists bound where you ship, and entity-level translation holds catalog content per locale. One catalog, one seller base and one ledger, sold four different ways - confirm each mechanism on the demo.
How are exchange rates handled?
Rates are operator-set rather than fetched from a live feed, and the default currency for a market drives what each buyer is quoted at checkout. This is deliberate: a feed that moves overnight reprices your entire catalog without anyone deciding to, and both sellers and buyers discover it at the same time.
How does tax work when it differs by state?
Tax classes and rates bind per zone, with per-product rules through a polymorphic binding, so different rates across states are configuration rather than two deployments. Display is inclusive or exclusive per market, every order carries a tax line breakdown, and tax reports run over any date range for the period you are filing - recorded scope.
Is cash on delivery properly accounted for?
The recorded scope states a one-time code is verified at handover, cash collected is written to the agent's own balance and kept separate from their earnings, an operator-set handling fee applies to cash orders, and the balance reconciles into the operator wallet when the agent settles. It is described as a settlement path with its own ledger, not a payment-method flag - watch it run on the demo.
Is right-to-left layout included?
No, and the hub says so plainly: RTL is named as a scoped customization rather than implied as included. For a Gulf-market deployment that matters, so it should be scoped and quoted at the start rather than assumed. Multi-language content itself is recorded in the base build - the translation store and per-locale listing content.
Are iOS apps included?
No. The three Android builds - buyer, seller and delivery agent - are the recorded base build. The Flutter projects compile for iOS, and App Store builds, signing and submission are quoted as an add-on because the developer account and the review cycle are separate work.
See a second market opened, not described
Ask in writing and we will walk the recorded scope with you: adding a currency, binding a tax zone and opening a delivery country, then placing an order through it. Demo availability is confirmed in writing rather than asserted here - no calls required, no phone numbers collected.
