Ecommerce Website Development in Pune: How to Build Product Variants, Size Charts and Fit Guides That Help Customers Choose the Right Size
A good size chart on an online store does three jobs: it helps the customer pick the right size before paying, it reduces avoidable "wrong size" returns, and it gives search engines clear, structured product information. For an apparel, footwear or accessories store, the work sits in three places: how your variants are modelled in the catalogue, how the size and fit information is presented on the product page, and how the variants are described in your product data for search and shopping feeds. This guide, written from the point of view of an ecommerce website development team in Pune, explains each layer for Shopify, WooCommerce and custom stores, with a worked example and a test checklist.
We keep one boundary clear. This is about building the product page and catalogue properly. It is not about courier choice, return logistics or tax, which are separate topics. The aim is simply that a customer standing on your product page on a phone can answer the question "which size should I buy?" without guessing.
Why size and variant design deserves its own project
Sizing is the main uncertainty in buying clothing and footwear online, because the customer cannot try the item on. When uncertainty is high, customers either abandon the page, order two sizes intending to return one, or buy and return. A page that answers the question clearly lowers all three. It does not eliminate them, since fit is personal, but it reduces the cases where the page itself caused the confusion.
Variants are also a data problem. If a T-shirt in four sizes and three colours is stored as twelve unrelated products, stock is hard to manage, reviews are split, search engines see duplicate pages and customers cannot compare options. If the same shirt is stored as one product with variants, you get a single page, shared reviews, correct stock per option and cleaner data for Google. Getting this structure right at the start saves months of repair later. Our guide to product catalogue data preparation covers the broader catalogue groundwork.
Step 1: Model variants correctly
What a variant is
A product is the thing a customer thinks they are buying, such as "Cotton Kurta, Indigo". A variant is a specific purchasable combination of options, such as "Indigo, size M". Each variant has its own SKU, price (if different), stock count and ideally its own image. Options are the dimensions along which variants differ, such as size, colour or length.
Keep one product per design
Use one product page for one design and put colours and sizes inside it. Create separate products only when the item is genuinely different: a different fabric, cut or price positioning. If you create a separate product for each colour so that each can rank or show its own photo, do it deliberately, link the colour siblings to each other, and keep the data consistent.
Platform notes
| Platform | How variants work | Watch out for |
|---|---|---|
| Shopify | A product has up to three options, and every combination becomes a variant with its own SKU, price, inventory and optional image | Platform limits on options and variant counts have changed over time; check the current limits before planning a large size run. Some themes show colour as text rather than swatches until configured |
| WooCommerce | A "variable product" uses attributes, and you generate variations from them; each variation can carry its own SKU, price, stock and image | Plugins that add swatches or size charts vary in quality; large numbers of variations can slow the admin and the page, so keep attributes lean |
| Custom store | You design the schema: product, option, variant, inventory | You must handle stock per variant, variant selection logic and feed output yourself, so decide these before building |
TODO: confirm the current Shopify limits on options and variants per product against Shopify's documentation before quoting numbers to a client.
Use sensible option names and order
Size labels should match what customers know. For adult clothing, use S, M, L, XL or numeric sizes consistently, in logical order, not alphabetically ("L, M, S, XL" is a common bug). For footwear, state the sizing system (UK/India, EU or US) in the option name or helper text so that "8" is never ambiguous. Keep colour names descriptive ("Indigo", not "Colour 2") and match them to the photographs.
Handle stock per variant, and show it honestly
Each size should have its own stock. Disable or clearly mark sold-out sizes instead of hiding them, so customers can see that the size exists. If a popular size is out of stock, a notify-me option helps; our guide to back-in-stock alerts and out-of-stock pages explains how to build it with proper consent.
Give variants their own images where it matters
When a customer picks a colour, the main image should change to that colour. This sounds obvious, but a mismatch between the chosen colour and the displayed photograph is one of the most common causes of "not as shown" complaints. Our article on WooCommerce variation galleries covers how to link images to variations.
Step 2: Design the size chart
Start from real measurements
A size chart should list garment or body measurements in centimetres (and optionally inches), not just letter sizes. Letter sizes differ between brands; measurements do not. Decide whether the table shows body measurements (what the customer measures on themselves) or garment measurements (the finished item), and say which. Mixing them is a frequent source of confusion.
Measure samples from your actual production batch, not a supplier's generic chart. If a manufacturer changes a pattern, update the chart. TODO: record the measuring method your team uses (for example, flat garment measurements taken in a stated way) so staff measure consistently.
A basic chart for a shirt might have columns for size, chest, shoulder, length and sleeve. For trousers, waist, hip, inseam and rise. For footwear, foot length in centimetres against your size labels. Keep the number of columns small enough to read on a phone.
Be careful with India-specific sizing
India has no single sizing convention that all brands follow. Customers move between brand sizes, international sizes and their own tailor's measurements, and a size M from one label can differ from another by several centimetres. A national sizing initiative (the SizeIndia project by the National Institute of Fashion Technology with the Ministry of Textiles) has studied Indian body measurements, but brands still use their own charts. TODO: confirm the current status of SizeIndia and any adopted national standard before referring to it in client-facing copy. In practice, this means your own chart is the authority, and it should say so plainly.
Show how to measure
Add a short "How to measure" helper with a simple illustration or a few lines of text: measure chest around the fullest part, waist at the narrowest, hip at the widest, and foot from heel to longest toe. Include a note that measurements should be taken over light clothing and that if a customer is between sizes they should choose by their preferred fit, with guidance such as "if you prefer a loose fit, size up". A short instructional video can help, but keep it optional and light, because heavy media slows mobile pages.
Describe the fit in words
Numbers alone do not describe fit. Add a plain line for each product such as "Regular fit, true to size", "Relaxed fit, size down if you prefer a fitted look" or "Runs small; we suggest ordering one size up". State what the model is wearing, with the model's height and the size shown, if you use models. If you do not have evidence that a product runs true to size, do not claim it; use your return reasons and customer feedback to judge. TODO: define a rule for who writes and approves the fit notes (for example, product team after a fit session), so they stay accurate.
Make the chart easy to open and read on mobile
Most Indian shoppers browse on phones, so the size chart must work in a small viewport:
- Place a visible "Size guide" link next to the size selector, not buried in a tab below the fold.
- Open it in a modal or a drawer that can be closed easily, and keep the table scrollable horizontally if it is wide.
- Use a readable font size and enough contrast; do not shrink text to fit more columns.
- Make sure the chart can be reached with a keyboard and read by assistive software, with a proper table structure and header cells. See our guide to website accessibility for why this matters.
- Do not make the chart a flat image if you can avoid it. Images cannot be searched, translated or read aloud, and they are often blurry on a phone. If you must use an image, add a text alternative and a text table beside it.
Keep one chart per type of product, not per product
Maintaining a separate chart on each product page invites errors. Create a small number of reusable charts (men's tops, women's tops, kids' wear, footwear, trousers) and attach each to the products it fits. When a chart changes, update it once.
On Shopify, this is commonly done with a metafield or a page referenced by the product template, or with an app. On WooCommerce, plugins can attach charts by category or product. On a custom store, store charts as data and render them from a template.
Step 3: Build a fit helper that does not mislead
Simple helpers beat clever ones
Some stores add a "find my size" calculator that asks for height and weight and recommends a size. These can help, but they can also produce confident wrong answers, especially if the logic is based on assumptions rather than your own garment data. If you build one, do the following:
- Base the recommendation on your own measured charts, not on generic formulas.
- State clearly that it is guidance.
- Offer a way to see the full chart.
- Test it against real customers' known sizes before launch, and review it after a few weeks using return reasons.
Collecting body measurements counts as personal data, and the way you handle it should be explained in your privacy notice. If the helper stores customer measurements for later use, make that explicit and ask for consent. See our guide to DPDP Act compliance for websites for how to treat personal data collected through a form.
Use customer feedback honestly
A short "How did it fit?" question in the review form (small, true to size, large) is a helpful input for future customers and for you. It must be honest: do not edit or invent fit feedback. Our guide to building an honest product review system covers moderation and trust.
Step 4: Describe variants correctly for Google
Customers are not the only audience for variant data. Search engines and shopping feeds read it too, and mistakes here cause disapproved products or missing rich results.
Structured data on the product page
Google supports Product structured data and, for products with variants, a product group that links the variants to a parent. The main ideas, which you should confirm against Google's current documentation, are:
- Each variant is described with its own price, availability and identifiers such as SKU.
- Variants are linked to a parent so that Google understands they are options of one product.
- The properties that vary, such as size and colour, are stated.
- The data in the markup matches what the customer sees on the page.
Many Shopify themes and WooCommerce plugins output some of this automatically, which is a double-edged sword: duplicate or conflicting markup from a theme and an SEO plugin is common. Our article on product schema for Shopify and WooCommerce explains how to audit it.
Merchant Center and shopping feeds
If you advertise in Google Shopping or show free listings, your product feed must describe variants properly. For apparel, Google asks for attributes such as colour, size, gender and age group, and variants should share a group identifier so that they are treated as one product with options. The required attributes and the allowed values for size systems change over time, so check the current Merchant Center specification before building the feed. Our guide to Google Merchant Center covers the setup and common disapprovals. TODO: confirm the current Merchant Center requirements for apparel attributes, size type and size system for India.
Variant URLs and SEO
A single product page with a URL parameter or a selected variant is usually enough. Avoid creating a crawlable URL for every size and colour combination unless each has genuinely distinct content, as this creates thin, near-duplicate pages. Make sure the canonical URL points to the main product page, and that selecting a variant does not break the page's title or heading. If you do use colour-specific pages, give each a distinct title and images and cross-link them.
Step 5: Speed and usability on the product page
Variant selectors, charts and image galleries add JavaScript and images. Keep them light:
- Load the size chart content only when opened, if it is long.
- Compress and size images properly; our guide to image optimization explains modern formats.
- Avoid loading three apps that each add a size chart, a reviews widget and a fit tool. Audit third-party scripts regularly; see our third-party scripts audit.
- Make the size selector large enough to tap, show unavailable sizes clearly and keep the add-to-cart button visible after selection.
- Remember the whole product page: our product page conversion checklist puts size information in context.
A worked example: a Pune ethnic-wear label
Consider a hypothetical small label in Pune that sells kurtas online, with sizes XS to XXL in four colours. This example is illustrative only and does not describe a real client.
Catalogue. Each kurta design is one product. Size and colour are options, which give 24 variants per design. Each variant has its own SKU and stock. Colour swatches change the main photograph, and sold-out sizes are shown as unavailable, with a notify-me link.
Size chart. The label measures one sample of each size from its production batch: chest, waist, hip, shoulder, sleeve and length, in centimetres. It creates two reusable charts, one for straight kurtas and one for A-line kurtas, and attaches each to the right products. A "Size guide" link sits beside the size selector and opens a scrollable table on mobile.
Fit notes. Each product has a one-line fit note based on a fit session with the production team. The model's height and the size she wears are shown. The review form asks "How did it fit?" with three options.
Search data. The product page outputs product markup with variants linked to a parent, and the product feed uses consistent group identifiers and size values.
Review. After eight weeks, the team checks the return reasons for "size" and "not as expected" and compares them with the earlier eight weeks. It adjusts two fit notes and one chart. It does not claim a percentage improvement unless the figures support it.
None of these steps is exotic. The value comes from doing all of them consistently.
Test checklist before you launch
- Pick every size and colour on a phone and a laptop; confirm the price, image, stock message and add-to-cart behave correctly.
- Add each variant to the cart and check the cart, checkout, order email and invoice show the right size and colour.
- Place a test order for a sold-out size and confirm it is blocked.
- Open the size chart on small and large screens; confirm it is readable, scrollable and closable.
- Check that the chart's numbers match the garments by measuring three random samples.
- Run the product page through Google's Rich Results Test and check that markup shows the right price, availability and variants without duplicates.
- Review the product feed for missing size and colour values before submission.
- Run a keyboard-only pass through the size selector and chart.
- Test page speed on a mid-range phone with a normal connection; compare before and after adding any size or fit app.
- Record where each chart is stored and who is responsible for updating it.
Common mistakes
- Creating separate products for each size or colour without a reason.
- Using only letter sizes without measurements.
- Showing an image of a chart that cannot be read on a phone.
- Mixing body and garment measurements in one table without saying so.
- Claiming "true to size" with no evidence.
- Letting colour changes leave the photograph unchanged.
- Installing several apps that each add size or review features.
- Forgetting to update the chart after a pattern change.
- Collecting height and weight in a helper without a privacy explanation.
When to ask a developer for help
You can fill in a chart and write fit notes yourself. Ask a developer when you need to restructure existing products into variants, attach reusable charts by category, output correct variant markup, build a feed with consistent group identifiers or make the size selector accessible and fast. If you are choosing a platform, our comparison of Shopify and WooCommerce for an Indian store explains the trade-offs.
Related reading: How well variants work depends on the platform underneath; see how to choose between Shopify and WooCommerce.
Frequently Asked Questions
Should each colour of a product have its own product page?
Usually no. One page with colour and size options keeps reviews together and avoids duplicate content. Separate pages for each colour can make sense when the colours differ strongly in demand or imagery, but then each page needs its own title and images, and the pages should link to each other.
How many measurements should a size chart show?
Enough to let customers choose without guessing, and few enough to read on a phone. For tops, chest, shoulder, length and sleeve are typical; for trousers, waist, hip and inseam; for footwear, foot length. State whether the numbers are body or garment measurements.
Can a size chart reduce returns?
It can reduce returns caused by unclear sizing, but fit is personal and some returns will remain. Compare your return reasons before and after the change over a similar period instead of expecting a fixed percentage.
Is a size chart image or a table better?
A table, because it can be read on a phone, translated, searched and used with assistive software. If you must use an image, add the same information as text beside it.
Does Google need my variants described in a special way?
Google reads product structured data and, for shopping listings, a product feed. Both should describe each variant's size, colour, price and availability and link variants to a parent product. Requirements change, so check Google's current documentation or ask your developer to validate your markup and feed.
Sources: Google Search Central: Product structured data, Google Search Central: Product variants structured data, Google Merchant Center Help: Apparel size attributes, Shopify Help Center: Add variants, WooCommerce Docs: Variable products, W3C WAI: Tables tutorial. Platform limits and feed requirements change; confirm them in current documentation before relying on this guide.
Working with Govindani Infotech on variants and product pages
Govindani Infotech is a Pune-based website design and development company at 2nd Floor, Landmark Plaza, 206 Satara Road, Parvati Paytha, Pune 411009. We build e-commerce stores on Shopify, WooCommerce and custom platforms, and the catalogue structure described here is part of how we set a store up.
If your store has variants that are messy, charts that are images or product data that Google keeps rejecting, message us on WhatsApp at wa.me/919201958278 or use the contact page. If you are planning a new store, our website creation page explains how a project runs.
About the author: written by the Govindani Infotech e-commerce development team in Pune, drawing on our experience building and maintaining online stores.