Amazon Clone Features: Catalog, Checkout, Fulfilment and Payouts
The hard part of a marketplace is not the product page. It is everything that has to agree afterwards - stock at SKU level, one order split across several vendors, four wallets settling, cash reconciling from a doorstep, and a refund reversing all of it cleanly. Here is what ships, grouped by who touches it.
Request a Live Demo →See PricingFeature Set by Role
Every capability grouped by who actually touches it - the customer buying, the vendor selling and getting paid, and the delivery agent closing the loop at the door.
Customer
- Keyword search with autocomplete, filters and sorting
- Featured, most-demanded and best-selling rails
- Deal of the day, time-boxed flash deals, clearance storefront
- One cart spanning several vendors at once
- Guest cart tracked by session and merged on login
- Coupon, wallet and loyalty applied together at checkout
- Refund request with reason and evidence
- Restock subscriptions, wallet, loyalty and referral
Vendor
- Register with KYC, approved by an operator
- Product CRUD with variants, stock and bulk import
- SKU-level rows with their own price and quantity
- Stock thresholds with low-stock alerts
- AI-assisted descriptions, SEO titles and alt text
- Order queue and refund responses
- Sales analytics and withdrawal requests
- Web panel or Android app, same data
Delivery Agent
- First-class identity with KYC and admin approval
- Assignment feed with accept and reject
- Navigation to vendor and to customer
- Live location broadcast and status checkpoints
- One-time-code verification at the door
- Cash collected written to their own balance
- Reconciled to the operator wallet on settlement
- Earnings view and withdrawal request flow
A delivery agent is an identity with its own KYC, wallet and approval state, not a flag on a customer account. That distinction is what makes cash reconciliation possible at all.
Amazon vs Miracuves Clone vs Building From Scratch
The same capability, three different paths - and one row where a general commerce script simply has nothing to offer.
| Capability | Original Amazon | Miracuves Clone | Build From Scratch |
|---|---|---|---|
| Multi-vendor catalog | Yes - the core product | Variant matrix, SKU-level stock, unlimited category depth | The part everyone starts with |
| One cart across vendors | Yes | Yes, with shipping estimated per vendor before checkout | Splitting an order cleanly is where it gets hard |
| Your own delivery fleet | Yes - built over decades | Agent identity, assignment feed, live location, OTP handover | A second product, and usually a second team |
| Cash on delivery | Yes, in some markets | Per-agent balance, operator settlement, its own transaction table | Where general commerce scripts quietly give up |
| Four separate wallets | Internal | Customer, vendor, deliveryman and operator, append-only | Most builds have one balance column and regret it |
| Commission control | Set by Amazon | Global, per category, per vendor or per product, reversed on refund | Reversal on refund is the case that gets missed |
| Payment methods | Extensive | Eleven gateways plus offline methods and COD | One gateway, then an integration per market |
| iOS apps | Yes | Not in the base price - Android ships, iOS quoted as an add-on | Two platforms to build and submit |
| Source code ownership | N/A | Full Laravel 12 and all three Flutter projects, nothing obfuscated | Full ownership (you are building it) |
| Price | N/A | $2,499 one-time | An 18 - 30 month programme with a senior team |
The iOS row is stated plainly because it is the thing buyers most often assume. Three Android builds are in the base price; the Flutter projects compile for iOS, and App Store builds, signing and submission are quoted separately because the review cycle and developer account are separate work.
How It Works, End to End
One order, followed from browse to settled money - including the doorstep, which is where most marketplace platforms stop.
Browse and add to cart
Keyword search with autocomplete, filters on price, brand, rating, vendor and attributes, and merchandising rails for featured, best-selling, deal of the day and clearance. One cart spans several vendors at once, with shipping estimated per vendor before checkout, and a guest cart is tracked by session and merged on login.
Checkout, however they want to pay
Coupon, wallet and loyalty apply together, scoped to product, category or cart with per-user usage limits. Eleven gateways, operator-defined offline methods and cash on delivery all terminate in the same order. Placement is guarded by an idempotency check, so a double tap on a slow connection does not create a second order.
Split, assign and dispatch
The order splits across vendors, stock decrements at SKU level, and each line carries its own delivery status so a multi-vendor order can be partially fulfilled. A delivery agent picks the job off an assignment feed, navigates to the vendor and then the customer, and broadcasts live location through the checkpoints.
Handover, verified
A one-time code is verified at the door rather than the agent simply marking it delivered. On a cash order, the amount collected is written to that agent's own balance and tracked in a dedicated transaction table rather than being treated as an ordinary payment.
Settle, or reverse
Commission is deducted from the vendor wallet when the order completes and reversed automatically if it is refunded, with loyalty points reversed on cancellation. Cash held by the agent reconciles to the operator wallet on settlement, and every movement writes an append-only history row so any balance can be re-derived.
Step five is the one to interrogate in any platform you evaluate. A refund that reverses the payment but not the commission, or cash that never reconciles, leaves a balance nobody can explain - and you will find it at year end, not at launch.
Every Feature Earns Its Place
Nothing here is on the list because it demos well. Each capability exists because leaving it out breaks something specific and expensive.
| Capability | Why it is not optional |
|---|---|
| Four separate wallets | Because a customer refund, a vendor payout, an agent's cash and your commission are four different liabilities. One balance column means you cannot answer who is owed what. |
| Append-only wallet history | Because a balance you can only read is a balance you cannot defend. Every movement writes a row, so any figure can be re-derived from the ledger. |
| Cash in its own transaction table | Because treating cash as an ordinary payment hides the gap between money collected at a door and money in your account. |
| OTP at handover | Because "marked delivered" is not proof, and disputes over undelivered cash orders are the most expensive kind. |
| Idempotency on order placement | Because a double tap on a poor connection should not charge twice or reserve stock twice. |
| Per-line delivery status | Because an order split across three vendors will not arrive at once, and forcing one status on it makes the tracking page lie. |
| Commission reversed on refund | Because a refund that returns the customer's money but keeps your commission is a vendor dispute waiting to happen. |
| Field-level edit history | Because when a price or a status changes, the question is always who changed it and when. |
| Zip allowlists | Because offering checkout where you cannot actually deliver converts a sale into a refund and a bad review. |
The Technology Behind the Features
A conventional, hireable stack, deliberately: PHP 8.2 on Laravel 12 with nWidart modules, running controller to service to repository to model with transactions at the service boundary. That is 114 Eloquent models over 131 normalized MySQL tables, with modules for AI, Blog and Tax that enable and disable without touching core, and observers, events and listeners driving notifications and ledger writes. REST API v1, v2 and v3 serve every client. Mobile is Flutter with Dio and Provider over GetIt - customer, vendor and deliveryman builds from one shared architecture, Sanctum bearer tokens carrying role claims, Firebase Cloud Messaging per app and Google Maps in the deliveryman build. Data sits on MySQL 8.x and Redis 7.x with InnoDB and utf8mb4 throughout, soft deletes on customer, vendor, agent and product rows, composite indexes on the hot paths, and append-only wallet histories.
Nothing here is exotic, and that is the point: the developers who maintain this after handover should already know it.
What Is Not Included in the Base Package
Everything above is in the base build and demonstrable in the live demo. These are not - and the hub labels them configuration-required or integration-required rather than implying them away.
Yours to own, not ours to supply
- iOS applicationsThree Android builds ship. The Flutter projects compile for iOS, quoted as an add-on with signing and submission.
- Gateway credentialsEleven gateways are integrated; each needs your own merchant account and approval.
- SMS and email providerIntegration-required - your accounts, your sender reputation.
- Firebase projectPush notifications run through your own Firebase project.
- OpenAI keyThe AI module generates descriptions, SEO copy and alt text against your key, with per-feature token quotas.
- Catalog dataProducts, imagery and vendor recruitment are the business, and they are yours.
- Tax ratesTax classes bind per zone, but the rates for your jurisdictions are yours to set.
- ISO 27001 and SOC 2Neither certificate is held and neither is claimed. The platform is ready for the evidence gathering.
Currency exchange rates are operator-set rather than fetched automatically, which is deliberate - a marketplace that silently reprices a catalog against a live feed surprises vendors and customers at the same time.
See how Miracuves compares to agencies and freelancers
The deployment process, two modelled reference deployments, and what to check before you hire anyone - on the Development Company page.
Frequently Asked Questions
How does the delivery fleet work?
Is cash on delivery properly handled?
Can vendors manage everything themselves?
Which payment gateways are supported?
Are iOS apps included?
What does the AI module actually do?
See exactly what you are getting - before you commit
Request a working demo of the storefront, the vendor panel, the delivery app and the operator console, or check exact pricing.
Explore the Amazon Clone
Ready to launch a marketplace that owns its last mile?
Deploy in 6 days with the storefront, vendor panel, delivery fleet and operator console included, full Laravel 12 source on infrastructure you own.
Talk to Us →Miracuves is an independent software development company. We are not affiliated with, connected to, sponsored by, or endorsed by Amazon.
“Amazon Clone” is used descriptively. It is how the software industry refers to building a platform with functionality similar to Amazon, and how clients search for it.
The entire design and codebase is built by our own team. The product contains no code, design, graphics, or content originating from the Amazon website or applications.
Amazon and all other third-party names and marks are the property of their respective owners, referenced here solely to describe the category of software offered.
