PRODUCT ENGINEERING / CONNECTED BUSINESS SYSTEMS
Omnistu Global - Everything ConnectedStart a project
Omnistu logoOmnistu

Flipkart Clone - Features

Flipkart Clone Features: Cash, Serviceability and the Last Mile

Design premise: cash is a full accounting path, serviceability is decided down to the zip, and the storefront reads in the buyer's language - this scope is designed for that, not adapted from a card-first, metro-first build. What follows is the proposed scope, grouped by who touches it - as recorded in the supplied specification. This preview does not implement or verify any of it.

Cash as a ledger - design premise4 wallets per order - specifiedOTP-verified handover - recorded
131Normalized MySQL tables - specified
13Ways to pay, including COD - specified
9Order statuses, full history - specified
3Flutter Android apps - specified
01 / By role

Feature 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. All recorded in the supplied specification.

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 recorded as an identity with its own KYC, wallet and approval state, not a flag on a customer account. On this page's proposed model, that distinction is what makes cash reconciliation possible at all.

02 / Compare

Three Routes to the Same Capability

The same capability, three different paths. The first two columns are what to verify on each route's own published terms; the third is the proposed scope as recorded in the supplied specification.

CapabilityOriginal Flipkart - what to verifyGeneric commerce script - what to verifyThis platform - proposed scope
Cash on deliveryAsk which categories offer cash on delivery, on their own published terms.Ask how a cash order is accounted for between dispatch and settlement.A settlement path with its own accounting: OTP, agent float, handling fee, reconciliation - recorded.
Serviceability controlAsk at what level serviceability is decided, on their published terms.Ask whether checkout is gated by route coverage or only priced by a shipping table.Delivery countries, zones and zip allowlists decide where checkout is offered at all - recorded.
Route economicsAsk how route economics are handled, on their published terms.Ask whether shipping can be overridden per category or route.Per-category shipping overrides so a city route and a rural one can differ - recorded.
Tax by state and categoryAsk how tax is modelled, on their published terms.Ask whether tax classes can bind per zone with per-product rates.Tax classes bound per zone with per-product rates and a line on every invoice - recorded.
Regional languageAsk what is translated, on their published terms.Ask whether translation covers catalog entities or only interface strings.Per-entity translation across storefront, apps and console - recorded.
Vendor onboardingAsk how sellers onboard, on their published terms.Ask what vendor onboarding involves beyond a registration form.KYC, admin approval, own panel and Android app, per-vendor commission - recorded.
Money modelAsk how balances are structured, on their published terms.Ask how customer, vendor, agent and operator balances are separated.Four wallets - customer, vendor, agent, operator - append-only - recorded.
Source ownershipAsk whether their platform is available for purchase at all.Full ownership is the point of building it yourself - verify the total scope you are quoting.Full Laravel 12 and all three Flutter projects recorded in the specification, with no licence callback recorded.
PriceNot applicable.Ask bidders to estimate the work implied by the specification's scope - 131 tables, three apps and the cash-reconciliation layer - and explain their assumptions.A scoped quote in writing before anything starts; commercial terms agreed in writing as part of your scoped quote.

Swipe sideways for the full table

The iOS position is stated plainly because the original page identifies it as the thing buyers most often assume: three Android builds are recorded in the base scope; 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.

03 / End to end

How It Works, End to End

One cash order, followed from a serviceability check to reconciled money - the path the original page argues a card-first platform never has to think about. Each step is recorded in the supplied specification.

01 - Is this address even serviceable?

Before anything else, the zip allowlist decides whether checkout is offered at this address at all. Delivery countries and zones sit above it, and per-category shipping overrides mean a dense city route and a town two hours out do not have to carry the same economics. The risk to test: whether offering checkout where no route exists is how a sale becomes a refund and a wasted trip.

02 - Order placed, stock and commission committed

One cart can span several vendors, so the order splits, stock decrements at SKU level and each line carries its own delivery status. Placement is recorded as guarded by an idempotency check. On a cash order, all of this is committed before any money exists - which is the model's argument for why the accounting has to be right.

03 - The agent carries the float

A delivery agent is a first-class identity with KYC and approval, not a flag on an account. They take the job from an assignment feed, navigate to the vendor and then the buyer, and broadcast location through the checkpoints. Until settlement, whatever they collect is recorded as their balance, not yours.

04 - OTP at the door, not a tap

A server-verified one-time code closes the handover. The risk to test: in a cash market, whether an unverified handover is the difference between a record and a claim - and ask which disputes a handover has to settle in your operation. The cash collected is written to that agent's balance and into a dedicated transaction table.

05 - Reconciliation closes the loop

Cash settles from the agent balance into the operator wallet, with an operator-set handling fee covering the cost of collecting by hand. Commission is recorded as deducted from the vendor wallet on completion and reversed automatically on refund. Every movement writes an append-only row, so any figure can be re-derived.

Step five is the one to interrogate in any platform you evaluate: ask whether a refund reverses the payment but not the commission, and whether cash ever fails to reconcile - and ask when and how an unexplained balance would surface in your own operation.

04 / Rationale

Every Feature Earns Its Place

The original page's argument: nothing here is on the list because it demos well - each is argued to prevent a specific failure. What each is designed to prevent.

CapabilityWhat it is designed to prevent
Cash in its own transaction tableDesigned for the fact that a cash order is not a payment that happened - it is a promise that closes later, at a door, with stock and commission already committed.
A float carried per agentUntil settlement the money is recorded as the agent's balance, not yours - without a per-agent balance, ask who is holding what.
Server-verified code at handoverDesigned so "marked delivered" is a record rather than an unverified claim - the handover the rest of the cash path depends on.
Operator-set handling feeCollecting notes by hand has a real cost - designed so recovering it does not mean quietly inflating the product price.
Zip allowlistsDesigned so checkout is not offered where no route exists - the risk to test: whether this is how a sale becomes a refund, a bad review and a wasted trip.
Per-category shipping overridesDesigned so a dense city route and a town two hours away do not have to carry the same delivery economics, with one subsidising the other.
Tax classes bound per zonePer-product rates are set per zone - designed so the invoice carries the line for the rate you have set; verify treatment with your own tax adviser.
Per-entity translationHypothesis to test: a buyer who does not shop in English may convert poorly against an English storefront, however good the catalog is.
Four separate walletsCustomer refunds, vendor payouts, agent cash and your commission are four different liabilities on one order - designed to keep them separate.

Swipe sideways for the full table

05 / The stack

The Technology Behind the Features

A conventional, hireable stack, deliberately - as recorded in the supplied specification: PHP 8.2 on Laravel 12 with nWidart modules, running controller to service to repository to model with transactions at the service boundary. Recorded as 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.

Laravel 12 - PHP 8.2, nWidart modules131 normalized MySQL tables - specified114 Eloquent models - specifiedRedis 7 - cache, queue, session

The original page's argument for the choice: nothing here is exotic, and that is the point - the developers who maintain this after handover should already know it.

06 / Honest readiness

What Is Not Included in the Base Scope

Everything above is recorded in the base scope. These are not - the original page labels them configuration-required or integration-required rather than implying them away. Yours to own, not ours to supply.

iOS applications

Three Android builds are recorded in the base scope. The Flutter projects compile for iOS; App Store builds, signing and submission are quoted as an add-on as part of your scoped quote.

Gateway credentials

Eleven gateways are recorded as integrated; each needs your own merchant account and approval.

SMS and email provider

Integration-required - your accounts, your sender reputation.

Firebase project

Push notifications run through your own Firebase project.

OpenAI key

The AI module generates descriptions, SEO copy and alt text against your key, with per-feature token quotas - recorded.

Catalog data

Products, imagery and vendor recruitment are the business, and they are yours.

Tax rates

Tax classes bind per zone, but the rates for your jurisdictions are yours to set.

ISO 27001 and SOC 2

This preview supplies no ISO 27001 or SOC 2 evidence; no certification is claimed here. The original page describes the platform as ready for the evidence gathering.

Currency exchange rates are recorded as operator-set rather than fetched automatically - the original page calls this deliberate, arguing that a marketplace which silently reprices a catalog against a live feed surprises vendors and customers at the same time.

07 / FAQ

Frequently Asked Questions

How does the delivery fleet work?

Delivery agents are recorded as a first-class identity with KYC and admin approval, not a flag on a customer account. They get an assignment feed with accept and reject, navigation to vendor and customer, live location broadcast, status checkpoints, one-time-code verification at the door, and a wallet with a withdrawal request flow - all recorded in the supplied specification. Verify each in your own testing.

Is cash on delivery properly handled?

The recorded design: cash collected is written to the delivery agent's own balance, reconciled to the operator wallet on settlement, and tracked in a dedicated transaction table rather than being treated as an ordinary payment. Verify the flow in your own testing.

Can vendors manage everything themselves?

The recorded flow: vendors register with KYC, get approved by an operator, then run their own shop - product CRUD with variants and stock, bulk import and export, AI-assisted descriptions, an order queue, refund responses, sales analytics and a withdrawal request flow, from either the web panel or the Android app.

Which payment gateways are supported?

Eleven are recorded as integrated: Stripe, PayPal, Razorpay, Mercado Pago, Iyzico, PhonePe, Paytm, PayUZ, SSLCommerz, Flutterwave and PayTabs - as recorded in the supplied specification, not as partnerships claimed here. Operator-defined offline methods and cash on delivery are also recorded. Each gateway needs your own merchant credentials, which is why they are labelled integration-required.

Are iOS apps included?

No. Three Android builds are recorded in the base scope. The Flutter projects compile for iOS, and App Store builds, signing and submission are quoted as an add-on as part of your scoped quote, because the review cycle and the developer account are separate work.

What does the AI module actually do?

It is recorded as generating 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 for every call. It needs your own OpenAI key, so it is integration-required rather than included.

Independence

Not Affiliated with Flipkart

Omnistu is an independent software development project, not affiliated with, connected to, sponsored by, or endorsed by Flipkart. "Flipkart Clone" is used descriptively - it is how the software industry refers to building a platform with similar functionality, and how buyers search for it. Flipkart and all other third-party names and marks are the property of their respective owners, referenced solely to describe the category of software offered.

Next step

See Exactly What You Are Getting - Before You Commit

Ask us to walk through the storefront, the vendor panel, the delivery app and the operator console in writing - including the cash path from zip allowlist to reconciled money. Email is fine - no calls required, no phone numbers collected.

Email team@omnistu.com