Amazon and Flipkart vs Own Store: Seller Checklist

GPTWala Business Hub · Ecommerce Strategy

Practical decisions. Verified business truth. Clear next steps.

Use this guide as an operating checklist, then verify platform rules, commercial records and customer-facing promises before implementation.

Reviewed and updated: 12 August 2026

Compare Amazon, Flipkart and an own store at the level of one delivered, retained and collected order. Include referral or commission, closing and fulfilment charges, marketplace ads, storage, forward and reverse logistics, returns, payment costs, discounts, customer service, content, technology and acquisition. Then compare discovery, account dependence, customer relationship and cash timing. Current fees vary by category and programme, so calculate from official seller tools and actual statements.

This guide owns a comparable profit-and-control worksheet; it does not recommend one marketplace or promise sales. This guide gives you an operating method, not a promise of rankings, enquiries, sales or profit. Platform policies, fees, eligibility and laws can change, so verify the linked primary sources and your own commercial records before implementation.

What this guide helps you decide
Build the source-of-truth sheet first
A practical implementation workflow
Use the decision table
Apply it to Indian product businesses
Use AI without losing business truth
Avoid the common failure patterns
Measure progress with operating evidence
A 30-day implementation plan
Frequently asked questions

What this guide helps you decide

The real question is not whether marketplace versus owned-store selling sounds useful. The question is whether it solves a defined buyer or operating problem for one product, audience and channel without breaking product truth, margin, consent or delivery capacity.

Use these diagnostic questions before spending money or assigning work:

What is the exact SKU, price band, category and fulfilment method?
Which fees appear on current official calculators and actual statements?
How do cancellation, return, damage and settlement timing affect cash?
What demand must the own store fund and what customer relationship can it retain lawfully?

Write the answers in one decision note. If a critical answer is unknown, make discovery the next task. Do not let an attractive tool, template or competitor example silently become the strategy.

Build the source-of-truth sheet first

Every execution step should pull facts from an approved record. A source-of-truth sheet prevents a copywriter, agency, AI tool or busy salesperson from filling a gap with a plausible but wrong product promise.

Truth item	Authoritative source	Owner	Stop condition
Product and offer facts	Approved SKU, catalogue and offer master	Product or merchandising owner	A buying-critical field is missing or inconsistent
Buyer need and language	Recorded enquiries, interviews and sales notes	Sales or customer owner	The audience is assumed rather than evidenced
Price, margin and fulfilment	Current finance, stock and delivery records	Finance or operations owner	The promise cannot be fulfilled profitably or reliably
Channel and permission rules	Current platform policy and consent record	Channel owner	Permission, eligibility or policy is unclear

Add a version date to the sheet. When price, stock, specification, channel rule, audience permission or fulfilment promise changes, pause affected assets until their owner approves the update.

A practical implementation workflow

Step 1: Choose one comparable SKU cohort

Use the same SKU or genuinely equivalent offer, period, geography and return-maturity window across channels.

Evidence before moving on: A cohort definition that finance and operations accept.

Step 2: Build the fee and cost ledger

Record every channel-specific fee and variable business cost from official current sources and statements. Do not copy an old blog table.

Evidence before moving on: Dated source beside each cost line.

Step 3: Reconcile failed and returned orders

Include forward/reverse freight, fees, packaging, damage, markdown and unrecovered inventory according to the actual process.

Evidence before moving on: Mature return/RTO allocation without double counting.

Step 4: Value control and dependency separately

Record listing control, customer access, account risk, policy change, review ownership, content portability and demand dependence as non-price factors.

Evidence before moving on: A risk register rather than an invented rupee value.

Step 5: Run low, base and high scenarios

Change only named variables such as return rate, ad cost, price and fee. Keep observed actuals separate.

Evidence before moving on: Scenario decisions with stop thresholds.

Do not combine all steps into one launch. A small controlled version creates evidence that can be reviewed. A large rollout creates more places for the same unnoticed error to spread.

Use the decision table

Situation	Recommended action	Avoid
Marketplace contribution is positive and operations stable	Keep the channel while building owned assets deliberately	Leaving the business fully dependent without a continuity plan
Revenue is high but settlements disappoint	Reconcile SKU-level statements and returns	Using dashboard sales as profit
Own store lacks demand	Budget content/acquisition and time honestly	Comparing marketplace traffic with free website traffic
Fee or policy changes	Refresh the ledger before pricing or ad decisions	Relying on archived percentages

Treat this table as a starting policy. Your product risk, average order value, buying cycle, staff coverage, cash cycle and after-sales burden may require stricter gates.

Apply it to Indian product businesses

Kitchen accessory seller

A standard SKU gains marketplace discovery but has return handling costs. The owner compares mature retained contribution with an owned-store cohort that includes payment, ads and support.

Proof to keep: Settlement reconciliation and return-cause ledger.

Apparel brand

Size-related returns differ by channel. It separates listing/content defects from product-fit issues before changing price or exiting a channel.

Proof to keep: Variant-level return reasons and contribution.

B2B equipment seller

Marketplace format cannot qualify application needs. It uses the marketplace only for standard accessories and its own site for application-led RFQs.

Proof to keep: Qualified opportunity and accepted-order records by channel role.

These examples are intentionally operational rather than aspirational. Replace every placeholder with current records from the actual business. Do not present a fictional example as a client result or an industry benchmark.

Use AI without losing business truth

AI can help organise approved facts, draft alternatives, summarise interviews, classify enquiries, produce controlled content variants and flag missing fields. It must not invent specifications, materials, prices, discounts, stock, delivery dates, certifications, customer consent, testimonials or commercial results.

Use a four-part control:

Bound the input: provide only permitted, current source material.
Constrain the output: state what may change and what must remain exact.
Review by role: the product or commercial owner checks buying-critical facts.
Record release evidence: keep the source version, prompt or brief, reviewer, corrections and approval date.

For customer data, use approved accounts and collect only what the workflow genuinely needs. Do not paste private buyer lists, confidential price sheets or unreleased product files into an unapproved tool. India’s data-protection requirements and implementation timelines should be checked against current official MeitY material and qualified advice for the business.

Avoid the common failure patterns

Using headline commission only: Include all applicable fees and business variable costs.
Ignoring settlement timing: Model cash and working-capital exposure by cohort.
Treating own-store traffic as free: Include content, ads, partnerships and operating labour.
Using one return percentage: Measure mature SKU, category, channel and fulfilment cohorts.

The most expensive failure is usually not weak wording. It is a mismatch between the public promise and the business that must fulfil it.

Measure progress with operating evidence

Do not use reach, clicks or message volume as proof of business value by themselves. Connect upstream activity to a verified downstream event.

Measure	Definition	Decision it supports
Retained contribution per order	Collected net revenue less all defined variable and channel costs	Whether the SKU-channel pair is viable
Settlement reconciliation gap	Difference between expected and verified channel settlement	Whether records or assumptions are wrong
Mature return cost	Full cost of returns and failed orders for a completed cohort	Whether pricing/content/fulfilment must change
Demand dependency	Share of viable orders sourced by one marketplace or owned method	Whether the business needs resilience work

Record the denominator, time window, product or offer, channel, source and owner for every rate. Keep observed results separate from forecasts. A short test can show a problem, but it may not support a broad conclusion.

A 30-day implementation plan

Days 1 to 5: define

Choose one product, audience, channel and business outcome. Complete the source-of-truth sheet, baseline and stop rules. Name the owner who can approve or stop the work.

Days 6 to 12: build

Create the smallest usable version. Test links, mobile reading, forms or message routing, exact product facts, price basis, permissions and team handoffs. Use internal testers before real buyers.

Days 13 to 20: run a bounded pilot

Release to a limited, relevant audience or product set. Log every material exception. Do not expand merely because the asset looks polished or early engagement is positive.

Days 21 to 26: reconcile

Connect platform events to enquiry, order, delivery, return and finance records as relevant. Review complaints, mismatches, duplicate handling, response delays and workload.

Days 27 to 30: decide

Choose one outcome: keep, fix, stop or expand one variable. Record why, what changes next and when the next review occurs. Expansion should preserve the same truth, consent and approval controls.

Connect this work to the GPTWala DAA framework

DAA can reduce owned-channel dependence over time, but every channel decision still needs SKU-level contribution and operational evidence. If your product business still depends mainly on walk-ins, dealer calls, exhibitions or forwarded catalogues, GPTWala’s free DAA workshop explains how digital presence, AI-assisted content and controlled WhatsApp-led demand generation can work as one system. The workshop is educational and does not guarantee traffic, leads, orders, sales, earnings or profit.

Frequently asked questions

Is it cheaper to sell on my own website than Amazon or Flipkart?

Not necessarily. An own store avoids some marketplace fees but must fund technology, payment, content, demand generation, support, fulfilment and returns. Compare one mature retained-order cohort using the same cost scope.

How do I check current Amazon or Flipkart fees?

Use the current official seller fee pages, calculators, programme terms and your actual settlement statements. Fees vary by category, price band, fulfilment method, programme and time; do not rely on an undated third-party table.

Should I leave marketplaces after launching my website?

Only if evidence supports it. Many businesses use marketplaces for discovery and standard transactions while building owned content, direct demand and assisted selling. Manage dependency, but do not abandon a profitable channel for ideological reasons.

Can a small Indian product business start marketplace versus owned-store selling without a large budget?

Yes, if it starts with one product, one audience, one owner and one measurable buyer action. A small budget does not remove the need for accurate product facts, realistic fulfilment, permission and a stop rule. Expand only after the first bounded version produces trustworthy operating evidence.

Can AI automate marketplace versus owned-store selling?

AI can assist with research organisation, drafting, classification and controlled variants. It should not invent product specifications, prices, stock, delivery promises, customer permission, testimonials or results. A named human owner must verify buying-critical facts and approve release.

How long should I test marketplace versus owned-store selling before deciding?

Use a test window long enough for the relevant outcome to mature. A product-page test may need enough qualified visits; a B2B workflow may need the full enquiry-to-decision cycle; retention work may need a repeat-purchase window. Define the event, denominator and review date before launch instead of choosing a universal number of days.