Size charts for boutiques that end "will M fit?"

Picture the same message arriving four times in one day, from four different people, about four different kurtis: "Hi, will M fit me? I'm usually M in Zara but L in local brands." Each one is a real buyer, tape measure nowhere in sight, asking you to guess her body from a brand name. You answer the first two carefully. The third gets a shorter reply. The fourth message sits on "seen" until tomorrow — and by tomorrow she's bought elsewhere.

The frustrating part is that every one of those conversations is the same conversation, and it has a written answer.

"M" is not a measurement

Letters mean nothing across brands. An M kurti from one supplier is a 38 bust; from another it's a 40 with a looser cut. Your customer knows this — that's exactly why she asks. When a product page shows only S/M/L/XL with no numbers behind them, you haven't given her sizing information; you've given her a riddle, and the DM is her asking for the answer key.

The cost isn't only your time. Every doubt is a pause, and online, pauses kill purchases. Worse, a customer who guesses wrong and receives a kurti that doesn't close won't always ask for an exchange — often she just never orders again.

What a boutique size chart actually needs

You don't need a fashion-brand fit team. One honest table does it:

• Sizes down the side, measurements across — bust, waist, hip at minimum; add length and shoulder if your cuts vary.
• Inches, stated clearly. Your customers measure in inches; don't make them convert.
• Garment or body — say which. "Fits bust up to 38″" reads differently from "garment measures 38″". Flat garment measurements are easiest to produce: lay the piece flat, measure, double where needed.
• A line about stretch and fit. "Cotton, no stretch — take your usual size" or "relaxed fit — size down if between sizes" resolves the between-sizes doubt that causes half the DMs.

Make the chart once, carefully, on a slow afternoon. Measure your actual pieces rather than copying a supplier's chart — suppliers are optimistic, and their "M" is the reason you get these DMs in the first place. If your kurtis and your lehengas run differently, note it on the chart itself rather than pretending one letter covers both.

Put the answer where the doubt happens

A size chart buried in an Instagram highlight might as well not exist. The doubt happens on the product page, at the moment she's choosing between M and L — so that's where the chart must be, one tap from the size picker. When the answer sits next to the question, the DM never gets sent, and the order comes in with a size she chose herself, with numbers in front of her.

Every sizing DM you receive is a question your product page failed to answer. The chart doesn't just save you typing — it lets the sale happen at 11 p.m. when you're asleep.

For the customers who still aren't sure — genuinely between sizes, or ordering something stitched to fit — the next step up is collecting their actual numbers, which is why we let customers fill in their own measurements at home through a private link.

Where Studio OS fits

Studio OS treats the size chart as shop infrastructure, not a per-post afterthought:

• Upload your size chart once, in Settings — a photo or a clean image of your table.
• It automatically appears on every product page in your shop, right where customers pick a size before requesting an order.
• Sizes on an order are chosen by the customer and confirmed server-side, so what she picked is exactly what lands in your orders list.
• Update the chart in one place and every product reflects it — no re-uploading across fifty listings.

We'd eventually like charts to go per-product for shops whose cuts differ wildly between categories; for most boutiques, one honest shop-wide chart already ends the daily "will M fit?" queue.

Browse the demo shop to see a chart in place on a product page, or set up your own on Studio OS — a guest account works, no signup needed.