Shopify for fashion and apparel D2C (India)

Fashion on Shopify lives or dies on three things most Indian apparel brands underbuild: size and colour variant handling, a returns and exchange flow that survives a 30–40% return rate, and COD managed so it does not bleed margin to RTO. Get those three right and the platform handles the rest. Get them wrong and a beautiful store still loses money on every single fit-return.

I am a senior Shopify developer based in Delhi/NCR, and apparel is one of the hardest D2C categories I build for — not because the store is complex, but because the post-purchase economics are brutal and most brands only design the pretty part. This is the honest build guide: what to get right, what it costs, and where fashion stores quietly lose money.

Why is apparel harder to build than other D2C categories?

Most D2C categories are forgiving. You sell a supplement, a candle, a phone case — one SKU, one size, a return rate in the low single digits. Apparel is the opposite on every axis.

• Variants explode. A single kurta in 6 sizes and 5 colours is 30 variants, each with its own stock, SKU, and photo.
• Returns are the norm, not the exception. Online apparel commonly runs 20–40% returns, and fit — not defect — drives most of it.
• COD dominates and distorts. A large share of Indian fashion orders are cash-on-delivery, which lifts conversion but also lifts returns and return-to-origin (RTO).
• The decision is emotional and visual. People buy clothes on how they look on a body like theirs, not on a spec sheet.

So the store is not really a catalogue — it is a fit-decision engine with a returns pipeline attached. Build it like that and the numbers work.

How should I handle size and colour variants?

Shopify's variant model is genuinely good for apparel if you use it deliberately. Use two options — Colour and Size — and Shopify generates a variant for every combination, each with independent inventory, SKU, barcode, and price. That is exactly what apparel needs: you want to know you have 3 units of Navy / M left, not "some kurtas."

A few rules that save you pain later:

1. Watch the variant cap. Classic Shopify allows 100 variants per product; newer stores support up to 2,000. A product with 6 colours × 8 sizes = 48 variants is fine. A "mega product" with every colour and every size across sub-styles is not — split it into separate products by style.
2. One SKU per variant, always. Your 3PL, your RTO handling, and your reconciliation all depend on it. Skipping SKUs is the single most common apparel-store mistake I inherit.
3. Show live stock per size. If Navy / S is sold out, the size button should be disabled, not add-to-cart-then-fail. This is a theme-level change and it directly protects conversion.
4. Group colours as the product, sizes as the choice. Shoppers pick a colour first (visual), then a size (functional). Order your options that way and the product page reads naturally.

For anything beyond standard size/colour — monogramming, made-to-measure, fabric choice — you move into metafields and custom options, which I cover in Shopify metafields for AI-readable products and custom product options with metafields.

What does a good sizing UX actually look like?

This is where fashion stores win or lose, because sizing UX is really returns-prevention UX. Every fit question you answer before checkout is a return you avoid after delivery. The playbook:

• A real, product-specific size chart. Not a generic S/M/L table copied across the catalogue. Garment measurements in both centimetres and inches, ideally with a how-to-measure diagram. Store it in a metafield so it renders per product or per collection.
• A fit note. "Runs small — size up if between sizes" or "true to size, relaxed fit." One line. It removes more doubt than a paragraph of copy.
• Model measurements. State the model's height and the size they are wearing. This is the single cheapest, highest-impact thing most Indian apparel stores skip.
• Photos on varied body types. People buy when they can imagine the garment on themselves. Studio-only, single-model catalogues convert worse and return more.
• A size recommender, once you have data. Apps that ask height, weight, and fit preference reduce guesswork. Add these after launch — they are an optimisation, not a foundation.

Do the free things first. A proper size chart, a fit note, and model measurements cost nothing but effort and cut fit-returns immediately. The apps come later.

How do I build lookbooks and shoppable collections?

Fashion sells on aesthetic and story, not grid pages. Shopify handles editorial content well if you build for it rather than fighting the default theme.

• Lookbook sections. A custom section that pairs full-bleed editorial imagery with hotspots or "shop the look" product links turns a mood image into a cart. This is standard theme-customisation work, not a plugin you bolt on.
• Collection storytelling. Use collection page metafields for a hero image, an intro paragraph, and a curated "styled with" row so a collection reads like a page in a magazine, not a filtered search result.
• Drops and campaigns. Fashion runs on launches. A scheduled collection, a countdown, and a clean new-in feed do more for an apparel brand than most discount mechanics.
• Editorial-grade performance. Big imagery is the point of a fashion store and the enemy of speed. Serve responsive images, lazy-load below the fold, and keep the hero light. Slow apparel stores lose mobile shoppers before the first product loads — see why your Shopify store is slow.

The trap is loading three carousel apps and a video-background plugin to fake editorial polish. That is app overhead you pay for in speed. Most of it belongs in a well-built theme instead.

How should returns and exchanges work for apparel?

This is the part brands skip and then bleed on. Shopify has native returns in the admin, but apparel needs a self-serve exchange flow, and it needs to default to exchange, not refund — because most apparel returns are fit, not regret. A size swap keeps the revenue; a refund loses it.

What a good apparel returns flow looks like:

• Customer-initiated portal. The shopper logs in, picks the item, selects a reason (too small, too big, colour, defect), and requests an exchange or return without emailing you.
• Exchange-first. Offer the same item in a different size before offering money back. Store credit is the second-best outcome; a cash refund is the last resort.
• Automated logistics. Return label or reverse-pickup booking with your courier, tied to your 3PL, so nothing is manual.
• A returns policy that is honest and visible. Window, condition, who pays shipping. Hiding it does not reduce returns; it reduces trust.

In the Indian market, apps like Return Prime and AfterShip Returns are the common choices; pricing and features change, so verify current plans before you commit. This layer integrates with your fulfilment stack — the same Shiprocket/Delhivery fulfilment setup that handles forward shipping should handle reverse pickup too.

Treat returns as a product surface, not an afterthought. A brand with a 35% return rate and a smooth exchange flow can out-earn a brand with a 25% return rate and a painful one, because the smooth brand keeps the customer and the revenue.

What about COD — should I offer it, and how do I control the damage?

For most Indian apparel brands, COD is not optional — a large share of orders still come cash-on-delivery, and switching it off costs real revenue. But COD is where returns and RTO quietly eat your margin, because there is zero payment friction at checkout, so casual and duplicate orders get placed freely.

You manage COD; you do not just toggle it. The levers:

• Nudge to prepaid. A small discount or free shipping on prepaid orders shifts a meaningful chunk of volume off COD without banning it.
• Confirm high-value COD. OTP or an order-confirmation step (WhatsApp works well in India) on orders above a threshold cuts fake and impulse COD.
• RTO prediction. Apps that score risky COD orders — bad pincodes, repeat RTO customers — let you flag or auto-confirm before dispatch.
• Cap or gate COD by cart value or region where RTO is chronically high.

COD interacts with GST, payment gateways, and reconciliation in ways specific to India — I cover that groundwork in Shopify Payments, COD, and GST in India. The mistake is treating COD as free conversion. It converts, but it also concentrates your return and RTO cost, so it needs active management.

What will a fashion Shopify build cost in India?

Two costs to separate: the platform (Shopify's own fees) and the developer build. Here is the honest picture, in INR and USD (USD ≈ INR/83).

Shopify plan pricing (India, as of 2026 — verify on shopify.com/in/pricing):

Shopify Payments carries 0% platform fee, so the third-party-gateway fee only applies if you use an external gateway. Annual billing saves roughly 25%.

Developer build cost (my pricing):

App subscriptions (returns, sizing, RTO, reviews) sit on top — budget for them deliberately, because for apparel the returns and sizing layer is not optional. For the full scope-by-scope breakdown, see what it costs to build a Shopify website in India and what you get at ₹50K vs ₹5L.

Where do fashion stores actually lose money?

After building and inheriting a lot of apparel stores, the leaks are always the same, and almost never the thing brands worry about:

1. No fit guidance → fit returns. The biggest, most avoidable cost. Every missing size chart and model measurement becomes a reverse shipment.
2. Refund-default returns → lost revenue. Defaulting to refund instead of exchange hands money back that a size swap would have kept.
3. Unmanaged COD → RTO. Zero-friction COD with no prepaid nudge or RTO scoring turns conversion into shipping cost.
4. App-heavy stores → slow mobile → lost sessions. Fashion is mobile-first in India, and a bloated store loses shoppers before they see a product. See why your store isn't converting.
5. Generic catalogue photography → low trust, high returns. Studio-only images on one body type convert worse and return more.

None of these is a Shopify limitation. Every one is a build-and-operations choice. Which is the good news — they are all fixable.

What's next

If you are launching or fixing a fashion or apparel store and want the sizing, returns, and COD layer built properly — not just a pretty theme — that is exactly the work I do. Tell me your catalogue size, your current return rate, and where orders leak, and I will give you an honest fixed number and tell you which fixes actually move margin. Start with the Shopify developer page to see how I work, or share your project on /start and I will reply within 24 hours.

Related reads

• Why your Shopify store isn't converting — the CRO leaks that hit apparel hardest.
• Shopify Payments, COD, and GST in India — the payment and COD groundwork.
• Shopify + Shiprocket/Delhivery fulfilment in India — forward and reverse logistics.

Sources

• Shopify — product variants and options
• Shopify — India pricing
• Shopify — managing returns and exchanges