
A practical system for recording customer measurements in a boutique — what to capture per garment, how to avoid the common errors, and how to keep measurement history useful over years.
Measurements are the part of a tailoring business where a small error is expensive. A wrong number does not surface at the cutting table; it surfaces at the trial, after fabric has been cut, with a customer who has somewhere to be.
This is about building a measurement system that does not lose numbers and does not record wrong ones.
The paper diary works beautifully until one of four things happens: it is not in the shop when you need it, two customers share a name, the handwriting is ambiguous between 36 and 38, or the diary is simply gone. Every boutique has a story about the fourth.
There is a subtler failure too. In a book, measurements get overwritten. The old number is scratched out and replaced. You lose the ability to see that a customer has changed, and you lose the ability to check what you actually stitched to last time when she says the previous blouse fitted better.
The discipline that prevents most problems: take measurements once, write them down immediately, and read them back to the customer. Reading back catches transposition errors — the 34 that should have been 43 — while the customer is still standing there, which is the only moment the fix is free.
Record the date. A measurement without a date is of unknown value within a year.
Generic "size" fields are useless here. Each garment type needs its own set. A reasonable starting point:
Shoulder, bust, waist, front neck depth, back neck depth, sleeve length, armhole, sleeve round, blouse length, dart point.
Shoulder, bust, waist, hip, kurti length, sleeve length, sleeve round, neck depth; plus bottom length, waist and thigh round for the salwar.
Waist, hip, lehenga length, and the blouse set separately.
Shoulder, bust, waist, hip, full length, sleeve length, neck depth.
Adjust to your own practice. The point is not this exact list — it is that each garment has a defined list you capture every time, so nothing is missed because the shop was busy.
Numbers do not capture everything that affects fit. Keep a free-text note per customer for the things that recur:
These notes are the difference between a customer who returns and one who does not, and they are exactly what gets lost when the person who knew them is not in that day.
Once measurements are stored digitally, the value compounds — provided you keep history rather than overwriting. Three things become possible:
The tailor needs the numbers. They do not need the customer's phone number or outstanding balance. This is the practical argument for role-based access: without it you either keep measurements to yourself, which defeats the purpose, or expose everything.
Do not type in five years of diary. Enter customers as they return, plus anyone with an active order. Within a season the active base is in, and the dormant records were never going to be used.
Keep the old diary in a drawer for a year. It costs nothing and it ends the anxiety that stops people committing to the new system.
Measurement records are defined as named templates per garment type, so the blouse set and the lehenga set are separate and each is captured completely. Records attach to the customer and to the specific order, so the garment being stitched carries the numbers it was created with. Tailors reach them through the assignment view without being given access to financial data.
For the wider picture, see what digital tools change in a tailoring business.
Whichever your tailors already use. Consistency matters far more than the choice. Record the unit explicitly.
For anything closely fitted, every time. For loose garments, a year is a reasonable interval.
Either works if everyone does the same thing. Write the convention down — this is a common source of disagreement between staff.
Ask them to measure an existing well-fitting garment rather than their body. It is more reliable than a self-measurement over the phone, though a trial is still wise for anything structured.
The core habit: capture completely, read back before the customer leaves, date everything, and never overwrite history.
Manage orders, measurements, billing, and customers in one place with Boutique Manager.
Everything you need — orders, customers, measurements, billing — in one powerful platform.