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

DEV Community: Kanak Kapoor

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