Clothing Store: 6 Messages for Sizes and Colors
A clothing store differs from every other retail shop in one way: an item is not one item. A blue shirt is not a single product, it is six products because you carry six sizes. Add three colors and you have eighteen separate lines, each needing its own stock number. This is where things break. The total says forty pieces on hand, a customer asks for a blue medium and it is nowhere, while the stockroom is full of double extra large.
Most owners handle this on paper or in a spreadsheet updated by one person at the end of the day, if at all. The results are familiar: selling something you do not have, dead sizes piling up until the end of the season, and exchanges nobody can trace. The fix does not require a screen in front of every employee. It requires every movement to reach one place the moment it happens, and WhatsApp is the only place your staff already keeps open.
First: code the item properly
No tracking method survives an item called "blue shirt." The name needs three fixed parts: model, color, size. For example SHRT-102-BLU-M. If the supplier ships with a barcode, use it as is and do not invent a parallel scheme. If there is none, print a simple label. The rule: stock is never held at model level, but per color and size combination.
That coding is what makes a one-line WhatsApp message enough. The seller does not describe anything, they type the code and the count. How the coding ties into stock balances is covered in inventory management on WhatsApp.
The six messages that run the shop
Every movement in a clothing store falls into one of six cases. Cover all six with a short message and you will not need a surprise count to know where you stand.
| Case | Message | What changes |
|---|---|---|
| Receiving | receive SHRT-102-BLU-M 8 | Increases stock for that size and color only |
| Sale | sell SHRT-102-BLU-M 1 cash | Reduces stock, logs the seller |
| Size exchange | exchange SHRT-102-BLU-M for SHRT-102-BLU-L | Returns one and issues the other in a single move |
| Return | return invoice 4412 SHRT-102-BLU-M | Restores stock and raises a credit note |
| Branch transfer | transfer SHRT-102-BLU-S to Nakheel branch 3 | Deducts from one branch, adds to another |
| Damaged or lost | damaged SHRT-102-BLU-XL 1 stain | Removes it with a recorded reason |
Notice that every message carries the full code. A seller who writes "sold a shirt" gives you nothing. A seller who writes the code builds a record you can still audit three months later.
Exchanges leak the most stock
In clothing specifically, exchanges are far more common than returns. A customer takes a medium and comes back two days later wanting a large. If that movement is never recorded you lose twice: the medium shows as sold while it sits on the rack, and the large shows as available while it has already left the store.
Treat an exchange as one movement, not two disconnected ones, and always tie it to the original invoice number. At the end of the season you can then see how many exchanges each model generated. A model exchanged often has a sizing problem, not a design problem, and that fact is more useful for the next order than any sales report.
Dead sizes: catch them before the season ends
The common mistake is reading sales at model level. The model looks like a winner because seventy percent of it sold, but the remaining thirty percent is all one size that nobody will buy. A weekly review is enough: ask for every line that has not moved in twenty-one days, by size and not by model.
- Dead after three weeks on display: move it to another branch before discounting
- Dead after six weeks: bundle it with a piece that moves well
- Dead at season end: discount it, and record the note against the supplier, not the model
Handling slow stock early beats clearing it later at a loss, and the difference between the two is simply when you found out.
Invoicing and tax
Every in-store sale needs a compliant invoice, and e-invoicing requirements in Saudi Arabia are issued by the Zakat, Tax and Customs Authority. Check the current rules and deadlines at the official source, zatca.gov.sa, as obligations vary by business. The practical point is that issuing the invoice should be part of the same sale movement, not a separate step postponed to the end of the day, and it can be issued straight from a phone as described in invoicing on WhatsApp.
A checklist for the first week
- List your models and give each one a fixed code
- Open a separate stock line for every color and size combination
- Train sellers on one message format: action word, then code, then count
- Always link an exchange to the original invoice number
- Request a non-moving lines report every Saturday
- After a month, count three models physically and compare them to the system to measure accuracy
In short: the problem in a clothing store is not how many pieces you hold, it is how they are spread across sizes and colors. Code every combination separately, record the six movements with one WhatsApp message each, and review dead stock by size every week. Three habits are enough to know your real position without putting a system screen in front of every seller.