Merchant stories

Nobody's first month looks like this.

Three sellers, three different things that went wrong, told with the dates and the numbers attached — including the parts that did not work. If you only want the highlight reel, the internet has plenty.

About these three storiesThey are composites — representative journeys assembled from what actually happens to sellers on Dukaan, not interviews with three named customers. The mechanics, the failure modes, the settings and the sequencing are all real and all reproducible on the platform today. The names are not. We would rather tell you that than dress up a stock photo and a made-up quote as a case study.

Story one · the notebook

The seller who was already selling

A hand-poured candle business in Mumbai doing about ₹40,000 a month entirely on WhatsApp. Not a beginner — a working business with no system underneath it. This is the most common shape of seller who arrives on Dukaan, and the one where the first month is least dramatic and most important.

₹40k
Month 0
₹3.1L
Month 9
BEFORE

A business run out of a notebook

Orders arrived as WhatsApp messages and got written into a ruled notebook. Payment was a UPI screenshot the buyer sent, which she cross-checked against her bank SMS. Stock was whatever she remembered pouring that week.

It worked at fifteen orders a month. At sixty it started failing in specific ways: two customers charged the wrong amount, one order shipped twice, one never shipped at all. Nothing catastrophic. Just a slow tax on every day.

The actual reason she moved was not any of that. A corporate buyer asked for a GST invoice and a link to order from. She had neither.

DAY 1 · SETUP

Ninety minutes, not thirty seconds

The store itself existed in under a minute — sign in with the WhatsApp number, name the brand, pick a theme. That part is genuinely as fast as advertised.

The ninety minutes went where they always go: photographs. Eleven products, each needing a shot that did not have her kitchen counter in the background. The AI-drafted descriptions took two minutes to write and twenty to edit into her own voice.

What she did right on day one: turned on all six WhatsApp automations before the first order, so she never built the habit of answering status questions by hand.

WEEK 1

Six orders and one problem

She posted the link once to her WhatsApp status and once on Instagram. Six orders in the first week — all from people who were already customers. Nobody new found her. That is normal and it is worth saying out loud: a store link does not generate demand, it captures demand you already have.

The problem was COD. Four of the six chose cash on delivery because it was there and it was default. One of those four refused the parcel. She had shipped ₹1,200 of candles and paid both legs of the courier for nothing.

MONTH 1–3

Fixing COD before scaling it

Three settings changed, in this order. Phone verification on COD orders — the buyer confirms via OTP before the order is accepted, which removes the accidental and the fake ones outright. A ₹40 COD handling fee, visible at checkout, which quietly pushed about a third of buyers to prepaid. A ₹2,500 cap above which COD is simply not offered.

Refusals went from one in four COD orders to roughly one in fourteen over the next two months. Revenue reached ₹94,000 in month three — most of it the same customers ordering more often, because the store made reordering a two-tap operation.

MONTH 9

₹3.1 lakh, and a different job

Nine months in: about ₹3.1 lakh a month, roughly 60% prepaid, one part-time helper for packing, and the corporate account that started the whole thing now ordering gift sets four times a year.

The number she cares about is not the revenue. It is that she stopped answering "where is my order" entirely. That was an hour a day. Nine months of that is about 270 hours — a full working month and a half returned to her.

WHAT DIDN'T WORK

The honest column

Instagram ads. She spent ₹18,000 over six weeks and made back about ₹11,000. Candles are a considered, gifting-led purchase and cold traffic does not convert on the first visit. She stopped.

The first theme. She picked a dense grid theme built for a 200-SKU catalogue and put eleven products in it. It looked empty and cheap. Switching to an editorial theme took one click and measurably improved conversion — the fix was free, the two months of looking wrong were not.

A second cart-recovery message. She added one manually. Three people blocked the number, which also cost her their order confirmations. She removed it.

Story two · the leak

The store that was busy and broke

An organic grocery brand in Pune shipping 400 orders a month and losing money on the growth. Everything looked healthy from the outside. The problem was entirely inside the return-to-origin number — and it is the single most common way a growing Indian D2C store quietly bleeds out.

28%
RTO before
9%
RTO after
THE SYMPTOM

Revenue up, bank balance down

400 orders a month, ₹4.6 lakh in gross sales, and less cash at the end of the month than the month before. He assumed it was courier rates. It was not.

Of those 400 orders, 310 were cash on delivery — normal for groceries. Of the 310, 87 came back undelivered. Each one cost him forward shipping, return shipping, and in about a fifth of cases a product too damaged to resell.

28% RTO on a category with thin margins is not a leak. It is the business.

DIAGNOSIS

Reading the returns properly

Sorting the 87 refusals by reason changed the plan completely:

31 — buyer unreachable on the delivery call.
24 — "I didn't order this" (impulse orders at 1am, forgotten by Tuesday).
18 — address incomplete or wrong pincode.
9 — genuinely changed their mind.
5 — courier never actually attempted.

Only nine of eighty-seven were real customer decisions. The other seventy-eight were preventable at checkout.

THE FIX · 4 SETTINGS

Nothing clever, just switched on

1 · COD phone verification. An OTP before the order is accepted. Killed most of the 31 unreachable and a good share of the 24 denials — a fake number cannot confirm.

2 · Pincode serviceability at checkout. Unserviceable pincodes are blocked before payment instead of failing at the doorstep. Most of the 18 address failures.

3 · A ₹49 COD fee, waived on prepaid. Prepaid share went from 22% to 41% in six weeks. Prepaid orders essentially do not RTO.

4 · WhatsApp shipping updates. A buyer who has read three messages about a parcel is dramatically more likely to answer the delivery call.

MONTH 2 · THE COST

Order volume fell. That was correct.

Orders dropped from 400 to 341 in the first full month. The COD fee and the OTP step turned some people away — and this is the part sellers panic about and reverse too early.

But RTO fell to 12%, then to 9%. 341 orders at 9% RTO delivers 310 parcels. 400 orders at 28% delivers 288. Fewer orders, more delivered revenue, materially less courier spend, and a warehouse no longer full of returned rice.

Net cash improved by roughly ₹61,000 a month on lower topline. Topline is not the score.

WHAT DIDN'T WORK

Two things he'd undo

Turning COD off entirely for a fortnight. He tried it. Orders fell 54% and did not recover until he brought it back. COD is not optional in Indian grocery; it needs to be priced and gated, not removed.

Blaming the courier first. He spent three weeks switching couriers before looking at his own refusal reasons. The new courier had almost exactly the same RTO rate, because RTO was never a courier problem.

Story three · the operator

Three stores, one person, until it broke

A Bengaluru seller running a silk saree label, a wholesale account and a seasonal wedding-gifting store. Everything worked until it did not, and what broke was not the software — it was that every decision still routed through one person's phone.

3
Stores
5
Staff seats
WHY THREE STORES

Different buyers, different prices

One catalogue could not serve all three audiences. Retail buyers must not see wholesale rates. The wedding store needs to appear in October and disappear in February without dragging the main brand's SEO with it.

Three separate stores under one login: separate catalogues, separate themes, separate payouts, separate analytics — one store picker at the top-left of the dashboard. Not three accounts, three logins and three sets of everything.

WHAT BROKE

One phone, every decision

During the first Diwali, the three stores did about 900 orders in eleven days. Everything technical held. She did not.

Every refund approval, every stock question, every "can we ship this to Coimbatore" came to her, because she was the only login. Two staff were packing at full speed and stopping every ten minutes to ask her something.

She missed 40 orders' worth of stock going negative on one SKU, because nobody else could see inventory.

THE FIX

Staff seats with real boundaries

Five seats, scoped by role. The packing team can see orders and mark them shipped, and cannot see revenue, edit prices or issue refunds. The catalogue person can edit products in one store only. The accountant sees payouts and nothing else.

Two warehouses were split by region so the Bengaluru team stopped picking stock that physically sat in Surat. Inventory became a fact everyone could read instead of an answer only she could give.

NEXT DIWALI

1,400 orders, and she slept

The following season did roughly 1,400 orders across the three stores with the same five people. Nothing about the platform changed. What changed was that four other people could answer the questions that used to queue behind her.

Her measure of the year: she approved 11 refunds instead of 300.

WHAT DIDN'T WORK

The wholesale store, twice

Running wholesale as a hidden category inside the retail store. Retail customers found it through search and asked why they were being charged more. It had to become a separate store, which is what she should have done first.

Opening the wedding store in August. Too early. It sat empty for two months collecting nothing but a slightly worse conversion rate on the group. Now it opens in late September and closes in January.

The ledger

What the platform did, and didn't

Across all three, the same split shows up. Software is very good at removing mechanical work and completely useless at the parts that make a business a business.

Dukaan handled this

  • Order status conversations, entirely — the single biggest time recovery in every story
  • Money arriving correctly: server-priced totals, so a coupon can't be stacked or replayed against you
  • COD risk controls that turned an unprofitable channel into a manageable one
  • Inventory as shared truth instead of one person's memory
  • Courier booking, labels and tracking without a separate aggregator account
  • A checkout that works on a slow phone in a weak-signal town

You still own this

  • Demand. A store link captures interest; it does not create it. All three brought their own first customers.
  • Photography. The single biggest conversion lever on every store, and nothing automates it well yet.
  • Pricing and margin. The platform will happily help you sell at a loss, quickly and at scale.
  • Ads. Nobody's ad spend worked without a real offer behind it, and one of the three should never have started.
  • The hard customer conversations. Automation covers the mechanical questions; the rest are still yours.
  • Deciding what to sell. No dashboard has ever fixed a product nobody wants.
The pattern

Five things all three did in week one

Not advice from us — the overlap between three sellers who each figured it out separately and each wished they had done it on day one.

01

Automations before orders

Switched on all six WhatsApp automations before the first sale, so the habit of hand-answering status questions never formed.

02

Gated COD immediately

A handling fee and a COD minimum from day one. Every one of them learned this by losing money first.

03

Matched theme to catalogue

Few products want an editorial theme; big catalogues want a dense grid. Getting this wrong looks like a cheap store.

04

Sold to existing customers first

The link went to the WhatsApp list before it went anywhere near an ad. Warm traffic pays for the store; cold traffic tests it.

05

Read one number weekly

Not a dashboard tour — one metric that mattered that month. RTO rate, prepaid share, repeat rate. One at a time.

Disqualifiers

Don't start a store if

A store you abandon in month two is worse than no store. These are the cases where we would tell you to wait.

Nobody has ever bought from you

If you have not sold this product to a single human — in person, on Instagram, to a cousin — a storefront will not be the thing that starts it. Sell ten by hand first. You will learn more from those ten than from any dashboard.

You expect the platform to bring traffic

Dukaan is not a marketplace. There is no Dukaan homepage where shoppers browse and find you. You get a store, the tools to run it and the plumbing to keep it honest. The customers are yours to bring.

Your margin is under about 15%

Between the gateway fee, shipping and the returns any Indian seller eventually eats, a thin-margin product does not survive contact with e-commerce economics. Fix pricing first; the store will still be here.

You need deep ERP or marketplace sync today

If your business already runs on an ERP with multi-warehouse allocation and live marketplace inventory sync as a hard requirement, talk to us about Enterprise rather than starting on the free plan and discovering the gap in month three.

You cannot ship reliably yet

Automation makes a well-run operation faster and a badly-run one louder. If parcels currently go out whenever you get around to it, an automated "shipped!" message will simply broadcast that to every customer at once.

You want a website, not a store

If what you actually need is a brochure site with a contact form, this is heavy machinery for the job. Dukaan is built around orders, payments and delivery — if none of those are in play, use something simpler.

By the numbers

What you're joining

0
Stores live
0
Storefront themes
0
Plugins included
₹200
Service fee cap / order
Free forever plan

Your store, live in 30 seconds.

No card. No code. Cancel nothing — there's nothing to cancel.

Start free