Why boutique stock needs different habits from a regular garment shop
In a boutique, the hard part of inventory is not volume. A design may exist in a single piece, some pieces belong to a designer who is paid only after they sell, and a good share of sold outfits are still in the shop waiting for alterations. The best practice is to make every piece individually identifiable, record who owns it, and always know where it physically is: on the rack, in the trial room, with the tailor, out on approval or with the customer.
This article is for boutique owners, designer studios and ethnic wear stores where most stock is in ones and twos. It covers coding unique pieces, photos, alterations, consignment stock, seasonal collections and the counts that keep it all honest. If you run a larger garment store where each design comes in full size and colour ranges, our guide to size and colour variants in a garments POS is the better starting point.
Coding one-of-a-kind pieces so nothing is "that pink one"
Staff in small boutiques often describe pieces by memory: the pink lehenga with mirror work, the green Banarasi from the Diwali lot. That works while the owner is in the shop and stops working the day she is not. A simple code on every piece fixes it.
A practical pattern is season, category and a running number, for example FW26-LEH-014 for the fourteenth lehenga of an autumn-winter 2026 collection (an illustrative format; use whatever your staff find easy to read). The code goes on the tag, on the barcode label, on the photo file and on the invoice, so every record about that piece can be matched.
| Field | Why it matters |
|---|---|
| Piece code | Links the tag, photo, stock record and invoice to one physical item. |
| Category and season | Lets you see what is left from each collection when the season ends. |
| Fabric, work and colour | Helps staff answer customer questions and find the piece quickly. |
| Size or key measurements | Many boutique pieces do not fit a standard size chart, so measurements prevent wasted trials. |
| Cost and selling price | Needed for margin and for deciding how far a markdown can go. |
| Owner (own stock or consignor) | Decides who gets paid when the piece sells. |
Small batches are different. If a kurta set comes in three pieces, one each in S, M and L, record it as one design with three size variants rather than three unrelated items. You keep one design history and still know which size sold.
Photos as part of the stock record
Many boutiques sell as much on WhatsApp and Instagram as across the counter. Each photo is effectively a product listing, so it needs the same discipline as the stock itself. The common failure is a customer asking for a piece from a photo sent three weeks ago that was sold the following day.
- Photograph on arrival: take the photo when the piece is coded and tagged, not when someone asks for it.
- Name the file with the piece code: a shared folder where every photo is named by code makes it easy to find and easy to retire.
- Retire photos the day a piece sells: move the file to a "sold" folder at closing time so it is not shared again.
- Keep a neutral background: consistent photos make the collection look curated and help customers compare pieces.
If you plan to move from WhatsApp catalogues to a proper online store, the same codes and photos become your product data. Our guide on getting catalogue and stock ready before e-commerce explains what else you will need.
Alterations, fittings and pieces out on approval
A boutique piece can be sold and still be in the shop. Sleeves are being shortened, a blouse is being fitted, or a regular customer has taken two sarees home to show the family before choosing one. Each of these is a moment when stock can go missing or be sold twice.
Alterations and fittings
Bill the piece when the customer pays or commits, then track the alteration separately against that invoice number. A simple alteration slip with the piece code, invoice number, customer phone, the work required, the tailor's name and the promised date is enough. Keep a copy in a register or a shared sheet, and check overdue slips every week. Decide whether alteration is free or charged; if charged, bill it as a separate line so it does not distort the margin on the garment, and ask your CA how such charges should appear on the invoice.
Pieces taken home on approval
Sending pieces home on approval is a service many boutique customers value, and it is also where pieces quietly disappear. Record every approval: piece codes, customer name and phone, the date taken and the date expected back. Treat the pieces as out of stock until they return or are billed, and review the approval list every few days rather than waiting for month-end.
Designer and consignment stock: whose piece is it?
Consignment means a designer or small label leaves pieces with you and you pay them only after the pieces sell, usually keeping an agreed share. It lets a boutique offer more variety without tying up cash, but it creates three risks: consignment pieces get mixed with your own, settlements are forgotten or disputed, and unsold pieces are not returned on time.
- Agree the terms in writing: your share or margin, the selling price, who can approve discounts, the settlement date and how long unsold pieces stay.
- Create a separate supplier record for each consignor, so their pieces can be listed and their purchase history kept apart from yours.
- Give consignment pieces a tag prefix that tells staff at a glance that discounts need approval.
- Sign a handover list when pieces arrive and another when unsold pieces go back.
- Send a monthly statement to each consignor, built from your sales and stock records.
| Column | What it shows |
|---|---|
| Received | Pieces handed over by the consignor, by piece code. |
| Sold | Pieces billed this month, with invoice number and selling price. |
| Returned | Pieces handed back to the consignor, with the signed return list. |
| In hand | Pieces still in the boutique, which should match a physical count. |
| Amount due | The consignor's share of sold pieces, as per the written terms. |
Consignment stock usually is not your stock in the books until it sells. How it should be recorded and taxed depends on your arrangement, so confirm the treatment with your CA.
Seasonal collections and end-of-season decisions
Boutiques usually buy around seasons and occasions: wedding season, festive months, summer cottons. Putting the season in the piece code means that when the season ends, you can list exactly what is left from that collection instead of walking the racks.
Because each leftover piece is unique, the decision is made piece by piece rather than design by design. A classic silk saree may simply wait for the next wedding season. A trend-led print may need a markdown now. Consignment pieces should go back to the designer as agreed. If you have a second outlet, a piece that sat untouched in one may suit the other's customers. For the numbers behind these decisions, such as how long stock has aged and which labels earn their rack space, see the reports garment and footwear owners should read.
Small-quantity counts you can keep up with
With few pieces and high prices, a single missing item matters. The good news is that boutique counts are quick if they are frequent. A practical rhythm is a closing check of the trial rooms every evening, a weekly count of the highest-value pieces, and a full count once a month, compared against the stock list and the open alteration and approval records.
When a count does not match, check the alteration slips and approval list first; most gaps are pieces that left the rack legitimately but were never written down. Record any genuine loss or damage as a stock adjustment, with a reason, so the stock list stays trustworthy.
Where MATROP's software fits a boutique, and where it does not
Our garments and footwear shop software covers the core of boutique stock control: barcode labels with item-wise SKU codes for each piece, size and colour variants for small batches, supplier-wise purchase history (useful for keeping each consignor separate), stock audit and adjustments, and sales returns and exchanges against the original invoice. Optional features include customer loyalty points for repeat clients and WhatsApp invoice sharing. Staff logins can be limited so the counter bills while the owner controls prices and reports.
Alteration slips, approval tracking, consignment settlement statements and a photo catalogue are not listed as standard features. Many boutiques run these comfortably in a register or shared sheet next to the billing software. If your process depends heavily on them, we can discuss whether a custom software module makes sense, and we will tell you honestly if it does not.
You may not need software at all yet if you hold a few dozen pieces and the owner personally handles every sale. A well-kept register with piece codes and a disciplined photo folder will serve you until volume, staff or a second outlet make that hard to manage.
Questions people ask
Does every boutique piece need its own barcode?
One-of-a-kind pieces should each have their own code and tag, because each one has its own price and history. If you have three identical pieces in different sizes, treat them as size variants of one design instead.
How do I keep a designer's consignment pieces separate from my own stock?
Create a separate supplier record and a tag prefix for each consignor, keep a signed list of what was handed over, and send a monthly statement showing received, sold, returned and in-hand pieces.
Should I bill an outfit before or after the alteration is done?
Bill it when the customer pays or confirms, and keep the piece marked as pending delivery against that invoice. That way it cannot be sold again to someone else while it is with the tailor.
Can I sell the same pieces on WhatsApp and in the shop without overselling?
Yes, as long as the photo you share carries the same piece code as the stock record and the piece is billed the moment it is sold on either channel. Remove sold pieces from your shared catalogue the same day.
