How the Work Runs
Built Around a Boutique’s Real Order Flow
A boutique order is rarely one garment on one date. Most systems assume it is.
Saree blouses and falls. The commonest order in an Indian boutique is also the fiddliest to record: a blouse taken from a saree the customer brought, with a fall and pico to match, and a fit note that only makes sense next to last time’s. Juvee keeps the blouse measurements as their own template — ten points rather than a generic chest and length — with the customer’s previous set still dated and readable underneath.
Lehengas and heavy work. A lehenga is not one job. It is a skirt, a blouse, a dupatta, embroidery that may go out to a karigar, and a wedding date that cannot move. Each piece is tracked separately so “nearly ready” becomes a list of what is actually finished, and the whole order still carries one delivery date so nobody loses sight of it.
Trials and alterations. High-value orders come back two or three times before they leave for good. Every fitting is recorded against the same order with what was agreed, so the person who alters it in June is not relying on the memory of the person who measured in March.
Bulk and party orders. Six bridesmaids, four sizes, one date. Each person is her own record with her own measurements, each outfit its own line with its own progress — so one piece running late cannot hide behind the group.
Fabric that belongs to the customer. Cloth brought in by a customer is not stock and should never be counted as stock. It is logged against that order, so it is not issued to somebody else and not counted in what you own.