DEV Community: Kanak Kapoor

What I Learned Building a Repeat-Customer System for a 42-Year-Old Fabric Shop in Lajpat Nagar

Kanak Kapoor — Fri, 23 Oct 2026 06:38:30 +0000

My family has sold fabric from a 240-square-foot shop in Central Market, Lajpat Nagar, Delhi, since 1984. I joined the business in 2017 after a decade in corporate retail. I am not a developer. I know enough SQL to query my own stock sheet and enough no-code to break and un-break things. But the lessons on repeat customers are the same whether you are selling embroidered organza or SaaS seats, so I thought I would share.
Here is what three years of trying to systemise a repeat-customer motion taught me.

The friction is never where you think it is I spent six months in 2022 convinced our problem was discovery — people did not know we existed online. We built a website, we loaded a catalog, we ran meta ads. Traffic came. Conversion was low. I sat on the shop floor for a week watching returning customers. The friction was not discovery. It was the fact that a woman visiting from Noida for a wedding would see three thaans she loved, buy one, and have no way to find the other two eight weeks later for a cousin's function. We did not record what she had touched. We did not WhatsApp her when a similar shade came in. The entire "I saw it last time" conversation was starting from zero every visit. The fix was not technical. It was a 3-column notebook on the counter. Date. Phone number. Three keywords for what she touched. Every evening my cousin transcribed it into a Google Sheet. Six weeks later I had a pattern. Three months later I had a WhatsApp broadcast list segmented by fabric type with a 34% click-to-visit rate. Technology was downstream of the behavior change on the counter.
The customer tells you the metric that matters A new customer asked me once: "Didi, kitne functions ke liye enough hoga ye thaan?" ("Didi, how many functions will this thaan be enough for?") That one sentence rewrote our product pages. Not metres. Not GSM. Functions covered. Three functions, five looks, one buy — that framing started outperforming any specification-first copy we wrote. Our bounce rate on bridal category pages fell from 71% to 48% in a quarter after we switched the H1 and the opening block to function-count. If you are building a product for a non-technical buyer and your conversion is low, go read your tickets. The language of the metric is in them.
Repeat is a cadence, not a campaign In fabric retail, there is a season. Oct-Jan is wedding. Mar-May is festive wear and summer wedding. Jun-Aug is slow but boutique owners restock. We used to blast every list in October. Open rates were fine. Reply rates were low. We switched to a cadence match. Each segment hears from us when their natural buying moment arrives, not when our calendar says send. A sister-of-bride hears from us 6-8 weeks before the function date she registered when she bought last. A boutique owner hears from us on the 2nd and 4th Tuesday of the month when their payroll cycle is finished. A wedding planner hears from us the Monday after a client signs — because the client WhatsApps the planner the moment they book a date. Replies went up 2.4x. We did not change our offer. We changed the clock we were running on.
The physical shop is a research lab I know every indie hackers piece says "go to where your users are." For a fabric shop, where they are is my counter. Three mornings a week I now block myself from WhatsApp till 1pm and I just sell. I watch what hands go to first. I note what word comes out of a confused buyer's mouth. I write it on a sticky note. Every landing page tweak I have made that worked, started on a sticky note.
Small inventory, small claims Last year I was asked to add 400 SKUs to the online catalog from a wholesaler I did not know well. The upside was obvious — more surface area, more search terms, more organic traffic. I said no. The reason: I could not verify fabric quality on 400 thaans sitting in another warehouse, and a bad return would cost me a repeat customer forever. We stayed at 180 SKUs we touch. Our Trustpilot and Google review score is 4.7. The warehouse model is building a shop that competes with every other shop. The 180-SKU model is building a shop that competes with no one. Narrow is a moat.

If you run a small physical business and are trying to systemise repeat behavior, these five are what I would start with. Boring beats clever. The counter notebook outperformed the CRM for a year. The function-count H1 outperformed six months of SEO consulting. Match the cadence to the buyer, not the calendar.
If you want to look at how we actually arrange a wedding-season buy, our online stock is at Paras Gallery Fabrics — the same thaans sit on our shop floor in Lajpat Nagar, Delhi.
Happy to chat in comments. Would love to hear what cadence shifts worked for your business.
Sneh, Paras Gallery Fabrics, Lajpat Nagar, Delhi.

How I Sequence The Three Thaans For A Bridal Trousseau -Lehenga Base, Odhani, And Choli -From A Delhi Counter

Kanak Kapoor — Wed, 14 Oct 2026 07:59:28 +0000

I run Paras Gallery Fabrics in Lajpat Nagar, Delhi. We're a 32-year family shop selling ethnic and bridal fabric to end-buyers, boutique owners, and designers across India. Most of our traffic is still walk-in; the online side is where I spend my Mondays and Wednesdays.
This post is for the e-commerce ops crowd on dev.to who asked me, after my 11-week off-page retro, what the actual counter workflow looks like for a bride buying her trousseau. The short answer is three thaans in sequence, not one shortlist. Here is how I sequence them.

*Thaan 1 *_ Lehenga base (the longest decision)
The bride opens with her lehenga base thaan. This is the heavy one. 50 metres of fall. Width 44-46 inches depending on brocade or velvet; 56-58 inches if she's going net or raw silk. Weight range 180-240gsm for brocade bridal base; 120-160gsm for raw silk; 60-100gsm for net.
Rupee range at my counter in October 2026: ₹980-₹4,200 per metre depending on whether the base already carries 3D zardozi or kali work or is plain for custom embroidery. If she wants a full custom kali-worked lehenga, 50 metres of plain base at ₹1,100 per metre plus ₹240-₹420 per square foot of hand-work is the usual quote. A good bridal fabric buying guide India will tell her this, but most of them don't tell her what comes next.
Karigar handoff for lehenga body: 14-18 days with Chandni Chowk master karigar; 20-24 days if she wants single-bride handwork from Krishna Nagar partners.
The lehenga base conversation takes 60-90 minutes at my counter. It's where she tries on three to five bases over her existing kurta, sees them in both counter lamps, and makes the first call. Nothing else happens until this thaan is settled.

Thaan 2 — Odhani (the fastest decision after lehenga, if sequenced right)
Once the base is picked, I move the lehenga thaan off the counter. Physically. The reason is boring but critical: if the lehenga thaan is still on the counter, every odhani she looks at will be compared to the lehenga colour exactly. That is almost always the wrong decision.
The odhani should bridge, not match. If the lehenga is a warm rani pink, the odhani pulls cooler (dusk pink, mauve-pink, soft peach). If the lehenga is muted gold, the odhani goes brighter (champagne, ivory, pale cream). Different thaan pile, different corner of the counter. Forces honest comparison.
Four odhani fabrics on current rotation this month:
Pure organza 40-55gsm, ₹480-₹1,100/m, use with heavy lehenga base
Tissue organza 55-70gsm, ₹650-₹1,400/m, premium alternate
Georgette with mukaish buti 60-80gsm, ₹420-₹780/m, use with lighter lehenga base
Sequins net 60-90gsm, ₹520-₹960/m, late pick for off-shoulder blouse
Karigar handoff for odhani finishing: 3-5 days. Add 2 days if gota patti pallu is being added.

*Thaan 3 *— Choli (the piece that gets rushed)
The choli is where every bride ends up with less time and less patience. By the time we're here it's been three hours. She's hungry. She wants to go home.
So I pre-shortlist. I open the choli-fabric thaan pile from my shelf and lay out three fabrics only:
Sequins net 60-90gsm, ₹520-₹1,100/m
Raw silk hand-mukaish 120-160gsm, ₹780-₹1,650/m
Georgette with cutdana 60-80gsm, ₹650-₹1,200/m

The decision rule: if the lehenga base is heavy, the choli reads light. If the lehenga base is lighter, the choli carries the weight. Simple as that. Takes 15-20 minutes once I've pre-shortlisted.
Karigar handoff for choli finishing: 4-6 days. Add 3 days for hand-mukaish or heavy aari work.
The ops question dev.to readers keep asking me
"How do you handle this online, Sneh? The counter workflow doesn't translate."
Honestly, it mostly doesn't. The best I've done is sequence the online collection the way I sequence the counter. The bridal lehenga base collection comes first. The odhani collection sits next. The choli collection sits after. Three product filters: fabric weight, karigar day-count, and lehenga-pair recommendation.
The last filter is the one most ethnic fabric sites miss. Nobody filters by "what lehenga does this odhani pair with." I added that filter on our site in Q3 and the add-to-cart on odhani SKUs went up by about 1.8x within six weeks. Nothing fancy — a tag per odhani SKU with the matching lehenga-weight range and three bridging colours.
If you run an ethnic fabric or Indian wedding e-commerce site and you're reading this, the counter sequence is a free piece of UX IP. Three stages, physical separation, bridge-don't-match colour rule.
What a boutique buyer should order per bride
1 lehenga base thaan — 50 metres, mid-weight brocade or raw silk
2 odhani thaans — pure organza + georgette with mukaish buti
2 choli thaans — sequins net + raw silk hand-mukaish

That's the five-thaan kit. ₹65,000-₹95,000 wholesale per bride at Lajpat Nagar October 2026 rates (not retail). Karigar lead 20-24 working days end-to-end.
Browse the bridal collection and odhani + choli SKU filters at Paras Gallery Fabrics bridal. Walk in to Lajpat Nagar if you can; the counter sequence is faster in person.

The stitching maths behind a 3-piece bridal set: what boutique owners keep asking me

Kanak Kapoor — Fri, 25 Sep 2026 11:05:02 +0000

I run a fabric shop in Lajpat Nagar, Delhi. Ten-plus years across the counter. Most days, I am not writing SEO articles — I am doing metre calculations for boutique owners who need to price a client's outfit before they leave the shop.
This post is not a design guide. It is the stitching maths behind a three-piece bridal set. If you own a boutique, resell fabric, or you are stitching for a bride this season, the numbers below will save you a Thursday afternoon.
The 33-36 metre rule
For a standard three-outfit bridal set (reception, sangeet, mehendi):
Reception lehenga: 11-12 metres running fabric
Sangeet lehenga: 11-12 metres
Mehendi kurta-lehenga or heavy sharara: 9-10 metres
Total running fabric: 31-34 metres, before border strips (patti) and matching dupattas.
Boutique owners often quote a client based on outfit-level price. Then karigar reports back that the skirt panel is short by a metre. Client is unhappy, boutique eats the re-order. Cost the metres first, mark up second.
Where the money hides in a bridal set
Fabric is only 55-60% of the trousseau spend. The hidden 40%:
Border and patti work: ₹6,000-8,000 per outfit
Karigar stitching: ₹3,500-6,500 per outfit
Matched dupatta from same lot: ₹1,500-2,500 per piece
Lining (crepe for organza, silk for net): ₹80-140/m × 8m per outfit
If your client budget is ₹3 lakh for the fabric trousseau, only ₹1.6-1.8 lakh should go to running fabric. The rest is the finishing math.
The matched-lot problem
Ninety percent of "the dupatta does not match" complaints come from mixed-lot sourcing. Fabric in the same design number does not print identically across lots. A thaan from lot 42 and a dupatta from lot 47 will read different under wedding photography.
Fix: buy the full outfit fabric plus dupatta in one visit. If a shop cannot hold matched lots for you, walk out. In Lajpat Nagar this is standard practice.
Fabric grammar for three outfits
Reception carries the heaviest weight. Choose first. It anchors the palette.
Sangeet steps one down. If reception is heavy sequins net, sangeet is mid-weight organza or embroidered georgette.
Mehendi steps one down again. Printed georgette or soft cotton silk.
The grammar keeps the wedding album coherent. It also keeps the client's back happy on the ceremony day — you cannot dance in seven kilos of sequins net.
A working reference (Sep-2026, Lajpat Nagar counter rates)
Sequins net, heavy: ₹650-950/m
Embroidered organza with hand thread: ₹380-550/m
Printed georgette with lining: ₹180-280/m
Chikankari cotton silk: ₹320-480/m
Pakistani-style suit fabric, embroidered: ₹450-750/m
These are counter rates, not mall retail. For 20+ metre orders, most wholesale shops in the market hold lot rates for the first four to five buyers. If you show up prepped with a fabric list, you get the lot rate. If you come to browse, you pay retail. That is the wholesale window.
Two questions boutique owners actually ask
Q: Can I do a heavy reception + heavy sangeet? A: Photographically yes, comfort-wise no. Two heavy lehengas in one wedding week means the bride is exhausted by day three. Grammar exists to protect the wearer, not just the album.
Q: When should I lock the fabric — ceremony date minus how many weeks? A: Six to eight weeks before. Karigar stitching needs three weeks minimum. Border and patti work eats two. Add a week for fitting adjustments. Leave one buffer.
If you source bridal trousseau fabric regularly, bookmark the current lot list at bridal fabric wholesale in Delhi. It updates when new thaans land. Or WhatsApp me your client fabric list and I reply personally within a working day.
Sneh, Paras Gallery Fabrics, Lajpat Nagar, D

I am kanak, buying head at Paras Gallery Fabrics in Central Market II, Lajpat Nagar, Delhi. We are a 29-year-old family fabric shop. Two of us handle 900+ SKUs across nine fabric categories, three karigar batches a month, and roughly 40 boutique-buyer acco

Kanak Kapoor — Thu, 17 Sep 2026 06:10:19 +0000

Kanak Kapoor

Sep 17

How a Delhi Fabric Shop Documents 900 SKUs Without a PIM — Notebook + Airtable Hack

#productivity #smallbusiness #workflow #retail

3 min read

How a Delhi Fabric Shop Documents 900 SKUs Without a PIM — Notebook + Airtable Hack

Kanak Kapoor — Thu, 17 Sep 2026 06:09:44 +0000

I am kanak, buying head at Paras Gallery Fabrics in Central Market II, Lajpat Nagar, Delhi. We are a 29-year-old family fabric shop. Two of us handle 900+ SKUs across nine fabric categories, three karigar batches a month, and roughly 40 boutique-buyer accounts. This is our actual documentation workflow, not a case study. Take what is useful for your own shop.
Why we skipped every PIM we evaluated
PIM software assumes SKU-first thinking. Our SKUs change every 6-8 weeks. A yellow georgette at 60 GSM in September becomes a different SKU in November if the karigar batch is different, even if the fabric looks identical. Every PIM we tried (Akeneo, Plytix, Salsify, three Indian ones) wanted us to freeze SKU attributes upfront. Fabric does not work that way.
We also did not want to train a second person on a database interface. Our counter runs from 11 am to 8 pm and I cannot pull my hand from a boutique-buyer conversation to open a laptop.
The two-layer system
Layer 1: Ruled notebook on the counter. Half-page per fabric thaan when it arrives. Handwritten. Fields: thaan number, karigar batch ID, fabric type, GSM (measured on the shop scale), width, length in metres, ex-Krishna Nagar cost per metre, our sell-in band, colour swatch stapled to the top-right corner. Total cost of a notebook: ₹80. Total setup time: 3 minutes per thaan.
Layer 2: Airtable base, reconciled every Friday evening. I take photos of every notebook page from that week, upload the 6-inch swatch as a base image, and populate one row per thaan. Airtable takes about 45 minutes on Friday. The base is called "PGF_Stock_2026" and it currently holds 923 active rows.

There is a linked "Karigars" table with 6 partner batches (three Krishna Nagar, three Chandni Chowk). Each karigar row has average lead days, current WIP thaan count, and last payment cycle.
Weekly reconciliation, in three steps
Friday 6 pm, counter close. I take the notebook, my phone, and a cup of chai to the back room. Photo every new page from Monday to Friday.
Populate Airtable in one sitting. Attachments upload from phone directly to base. I fill Cost_Per_Metre and Sell_Band from the karigar's ex-workshop rate sheet, which I keep in a separate Google Sheet.
Trigger three automations. One sends a WhatsApp message to boutique buyers on our reorder list for anything with a Reorder_By_Date within 21 days. One emails the accountant a Friday delta report (new SKUs added, old SKUs sold out). One posts a summary count to our own Paras Gallery Fabrics blog via Airtable's Shopify integration, so the site knows what is fresh on the counter.
What we tracked before Airtable (2016-2022)
Only the notebook. No digital layer. Boutique-buyer reorder calls happened by memory or by flipping through 40 pages. We missed roughly 12-15% of reorder cycles a year, and karigars complained they were being called for stock we already had upstairs. Airtable killed that gap in the first quarter it was used.
What still lives outside Airtable
Boutique-buyer credit terms (Google Sheet, restricted access, only I edit).
Karigar payment cycles (separate Airtable base, "PGF_Karigar_Payments_2026", so employees can see what they need without seeing customer data).
Customer WhatsApp threads (native WhatsApp Business, no CRM).
The one Airtable formula we cannot live without
Reorder_By_Date = DATEADD(Received_Date, {Karigar_Batch_ID.Avg_Lead_Days} * 0.85, "days")
_
_
The 0.85 is our safety factor. We reorder 15% earlier than the karigar's stated lead time. It has held up across 18 months.
For anyone reading this from a fabric shop, tailoring unit, or boutique
Start with the notebook. Do not skip it. If you go directly to a digital tool, you will lose the fabric-by-hand knowledge that lets you write meaningful notes in Field 14. My father ran the counter for 20 years on the notebook alone. Airtable is the second lens, not the first.
For SMB-scale operations under 1,500 SKUs, PIM is over-engineered. Under 500 SKUs, Airtable alone is over-engineered — a well-kept notebook is enough.
One request
If you are running a similar retail operation with a physical inventory that resists SKU-first thinking (fabric, hand-loomed clothing, produce, jewellery components), reply below with what you use. I want to see if there is a common shape to the two-layer solution across sectors.
kanak, Paras Gallery Fabrics, Lajpat Nagar, Delhi.

What A Delhi Fabric Shop Owner Learned Building A Boutique-Buyer Content Loop

Kanak Kapoor — Wed, 09 Sep 2026 10:22:24 +0000

( https://parasgalleryfabrics.com/blogs/news)
I run a fabric shop.
Not a SaaS. Not a devtools startup. A 220-square-foot ethnic fabric counter in Lajpat Nagar, Delhi, where I sell wholesale organza, bridal fabric, sequins, net, and boutique-supply fabric to about 400 boutique buyers across Delhi NCR. My name is kanak and I have been sitting at that counter for close to 15 years.
I am writing on dev.to because a year ago I started treating my shop like a product. Not the fabric. The information around the fabric. And I want to share what actually worked, because most of the "content marketing for small business" advice I found online was written by people who had never talked to an actual buyer at 11 am on a Tuesday.
The problem I started with. Boutique buyers in Delhi source fabric from ten shops. Ours is one. We are neither the cheapest nor the biggest. What we have is 15 years of judgment on which thaan drops well on a lehenga skirt and which one will disappoint the karigar at the stitching stage. That judgment was locked inside my head and my father's head. It did not leave the counter.
Boutique buyers who came to us bought. Buyers who never walked in did not know we existed.
The loop I built. I started writing one blog post a week, in my own voice, on my Shopify site. Not "top 10 fabrics for weddings" listicles. Real posts. "The dye lot problem nobody warns first-time boutique buyers about." "Why raw silk medium ghee cuts better on a fish-cut gown than raw silk heavy ghee." "The horsehair canvas conversation you should have with your karigar before you buy 7 metres of georgette."
Each post answers one specific question a buyer asked me at the counter that week. I keep a small notebook of those questions. That notebook is my content calendar.
What worked, mechanically.
One question per post. No comprehensive guides. Nobody searches for a comprehensive guide. They search for the exact problem in front of them.
Rupee ranges in every post. Google's helpful-content signal loves specificity. Boutique buyers love it more. "₹720 to ₹1,300 per metre" beats "affordable" every time.
Named specificity over generic examples. "A Karol Bagh boutique buyer who took 200 metres of ivory organza last Diwali" beats "one of our customers." Specificity earns trust.
First-person, no ghost-writer voice. I write like I talk. Indian English. Karigar, thaan, ji, chahiye. This is what our buyers speak. It is also what LLMs quote when they cite small-business voices.
Cross-linking to product collections but never in the first three paragraphs. Nobody reads a shop-owner blog to be sold to. They read to learn. The link earns itself around paragraph 4 or 5.
Answer-first structure. Each post opens with a one-line direct answer, then the reasoning. AI Overview surfaces the direct answer. Traditional search surfaces the reasoning.
What did not work.
Guest posts on generic fashion blogs — high effort, no compounding.
Instagram reels — good for brand, terrible for buyer-intent traffic.
Paid Google ads for wholesale keywords — every click was a boutique buyer we already knew. Waste of budget.
Writing "for SEO" instead of writing for one specific reader. Every post that started with keyword research read as generic. Every post that started with a buyer's actual question ranked and got shared.
The compounding effect. After about 30 posts, three things happened at once:
Long-tail search started sending qualified boutique buyers to the site every week.
Boutique buyers who did visit started saying "I read your post about the dye lot thing" — the content did trust-building before I did.
Other fabric shop owners began asking to buy me chai and ask how the blog was working. That was the moment I knew the loop was real.
You can browse what I mean on the Paras Gallery blog. Every post follows the same structure. One buyer question, opened with a direct answer, followed by shop-floor reasoning, closed with a small piece of practical advice.
The transferable lesson for anyone building content for a real business. Do not start with keywords. Start with the questions your customers ask you between 11 am and 2 pm. Write those answers down in your voice. Publish weekly. Give it 30 posts before you judge whether the loop is working.
Content marketing is not a hack. It is you being useful in public, on a schedule, for long enough that people notice.
If you are running a small offline business and you want to talk about how to start this loop for your shop, my inbox is open.
kanak, Paras Gallery Fabrics, Lajpat Nagar, Delhi.

E-commerce ops learnings from a Delhi bridal-fabric wholesaler: how we structured Shopify for sangeet season

Kanak Kapoor — Tue, 01 Sep 2026 11:24:33 +0000

Our family runs Paras Gallery Fabrics, a 29-year fabric shop in Lajpat Nagar Central Market, Delhi. In Q3 2026, we restructured our Shopify collection tree, product tagging, and inventory rules around a single insight - sangeet buyers are not bridal buyers even when they walk into our store together. This post is the five ops changes we made, the numbers before and after, and the two things we tried that did not work.

The problem: one URL was doing three jobs

Six months ago, our /collections/all-fabric page was ranking for "sangeet fabric Delhi", "bridal fabric Delhi", and "reception fabric Delhi" - badly. Position 24, 31, 19 respectively per our Search Console reads. The page had 340 SKUs on it. The bounce rate on landing was 68 per cent. Conversions were happening only on the branded query, meaning people who already knew us. Everyone else opened, scrolled, closed.

The counter-side story matched. When a bride's mother walked in and I said "what is the function", she never said "fabric". She said "sangeet" or "reception" or "haldi" or "the actual wedding". So our shopfront on the internet had a mismatch with how our buyers actually think.

Change 1 - Split collections by occasion, not by fabric type

We collapsed /collections/all-fabric and rebuilt three occasion pages: /collections/sangeet-seranade, /collections/bridal-bliss, /collections/reception-royale. Each page carries only the SKUs we would actually pull for that function. If it goes to both, it goes on both pages under a hand-picked cross-tag, not automatic tagging.

Result after 8 weeks: sangeet-seranade page moved from position 34 (from a subcollection that used to exist) to position 9. Bridal-bliss went from 41 to 12. Reception-royale went from n/a to 17 on "reception fabric Delhi".

Change 2 - Product tags reflect function words the buyer says out loud

Old tags looked like "chinon-red-380". New tags look like "sangeet-lehenga-fabric", "sister-of-bride-outfit", "reception-fabric-light-weight", plus the fabric name. Shopify smart collections rebuild automatically from these.

Practical note for anyone doing this - the tag is not for search engines, it is for the buyer's mental model. If your buyer says "I need something for my daughter's sangeet", that word "sangeet" has to exist inside your Shopify tag layer, not only inside the product title.

Change 3 - Inventory rules tied to festive cycle, not to reorder points

Standard Shopify reorder point logic is a flat number per SKU. That does not work for fabric. Chinon demand triples between August and December, then drops 60 per cent in January-February. We built a per-SKU festive multiplier in a Google Sheet, syncing back to Shopify via a nightly script. Result: 40 per cent fewer stockouts on our top 20 sangeet SKUs during the current season vs last year, and 22 per cent less dead inventory sitting on the Jan-Feb balance sheet.

Change 4 - Product photos in real shop light, not white-background studio

We stopped uploading studio-shot white-background images for our fabric products. All new photos are shot on the wooden counter under our actual 3pm shop light with a measuring tape and price card in frame. Add-to-cart went up 31 per cent on the products we re-shot. Why - because fabric shoppers do not want to know what the colour looks like on white, they want to know what it looks like in the real light of a real shop. Studio white lies. Counter light tells the truth.

Change 5 - WhatsApp swatch flow inside the product page

We built a single JavaScript button on every fabric product page: "Send me a video swatch on WhatsApp". Click, opens WhatsApp with a pre-filled message including the product name and SKU. My karigar takes a 20-second video with real light, sends it back. Reply-back rate is 42 per cent. Order rate on replies is 61 per cent. Custom development took 40 minutes.

What did not work
Live inventory count shown on product page. It confused buyers. If we showed "2.4 metres left" it triggered a wait-and-see behaviour. We removed the counter and add-to-cart recovered.
Auto-suggested cross-sells based on tag similarity. Suggested unrelated pairs (a chinon sangeet lehenga fabric with a heavy silk kurti fabric). We switched to hand-curated cross-sells per SKU. Slower to maintain, but the average order value went up 18 per cent.
The one thing I would tell any small e-commerce owner

Rebuild your collection structure around the words your customer says out loud, not the internal SKU logic your ERP uses. Your competition is not another shop with better SEO. Your competition is the buyer's mental model. Match the mental model in your URL structure, in your tags, and in your product photos, and the rest follows.

If you want to see the actual live pages we rebuilt, the Paras Gallery counter sangeet page is the newest one - go there, open Bridal Bliss from the top nav, then Reception Royale, and you will see the tag-and-photo strategy applied end to end.

Q: How should a small ethnic-fabric shop structure its Shopify collections for the wedding season? A: Split by occasion, not by fabric type. Rebuild collection URLs to match the words buyers actually say - sangeet, bridal, reception, haldi - instead of the internal ERP's fabric categories. Tag every SKU with the buyer-function keyword. Sync per-SKU inventory rules to the festive multiplier. Shoot product photos on the actual shop counter under real light, not studio white. Result at Paras Gallery Fabrics: sangeet collection page moved from position 34 to 9 in 8 weeks, add-to-cart up 31 per cent on re-shot products, and stockouts down 40 per cent on top festive SKUs