Running a clothing store is one of the hardest jobs in retail, and the reason is simple: variants. A single shirt may come in 5 sizes and 4 colors, which means you are managing 20 separate items for one product. If your system cannot tell an available size from a sold-out one, you end up surrounded by dead stock nobody wants while customers walk out because their size is missing. This article covers how fashion inventory is actually managed, and how to keep your merchandise turning fast.
The variant matrix: tracking colors and sizes
In a clothing store, a size error is the fatal one. Your system has to support a variant matrix. When a customer asks for black trousers in size 40, the salesperson should know at the touch of a button whether the piece is in the stockroom. A system that treats every size as an independent item gives you a clear view of which sizes are most in demand. That stops you from ordering equal quantities of every size and lets you focus instead on what the market is actually asking for.
Fashion seasons: when to start markdowns and when to stop
Clothing has a fashion shelf life. A piece that does not sell this season can lose half its value by the next one. The answer is to watch item age in the stockroom. Snad reports show you which pieces have sat on the shelf for more than 60 days, so you can build bundle offers or step the price down to clear them. Remember: cash frozen in old merchandise is cash you cannot spend on new collections.
Returns in clothing retail and their impact on inventory
Return rates in clothing are the highest in retail. A customer buys a piece, then discovers it does not fit. The return process has to be smooth and properly documented in the books: the piece goes straight back into sellable inventory and the financial entry for the invoice is reversed. Snad POS processes these returns in seconds, which keeps your inventory numbers matching what is actually on the floor.
Best-seller analysis to steer your next buy
Historical data is your first adviser. Do your customers prefer muted colors or bold ones? Is demand concentrated in formal outfits or casual wear? Analyzing last year's sales in Snad lets you plan your buying budget precisely. It cuts the odds of buying merchandise your local audience has no taste for, and raises annual inventory turnover.
Snad POS: your partner in the fashion business
We designed Snad to handle the complexity of clothing retail simply. You can define items with their variants (color/size), issue invoices in an instant, and run periodic stock counts with a barcode scanner. More important, Snad gives you detailed financial performance reports for every item, which helps you make smart pricing decisions and stay ahead in a fast-moving Saudi fashion market.
The size curve: how to split an order across sizes
The costliest mistake in clothing retail is buying equal quantities of every size. The outcome is familiar: the middle sizes run out within weeks, and both ends hang on the rail until the season closes.
The alternative is a size curve. Work out each size's share of last season's sales within the same category, then split the new order across those shares instead of spreading it evenly.
- Build a separate curve for each category (menswear, womenswear, kidswear) and for each fit; a shirt curve does not work for trousers.
- Exclude clearance-period sales from the calculation, because discounting distorts the picture of real demand.
- Review the curve two weeks after the collection lands, and reorder the sizes that actually moved.
The table below is a worked example of splitting a 200-piece order. The percentages are illustrative; pull your own from your store's reports, not from a market average.
| Size | Share of your last season's sales | Share of a 200-piece order | Buying decision |
|---|---|---|---|
| S | 12% | 24 | Base quantity |
| M | 30% | 60 | First in line for a reorder |
| L | 32% | 64 | First in line for a reorder |
| XL | 18% | 36 | Base quantity |
| XXL | 8% | 16 | Order only once real movement is confirmed |
Item coding: a separate barcode for every color and size
Every color and size combination is a separate item, and each one needs its own code and its own barcode. If a shirt carries a single barcode across all its colors, you do not know which color sold or which size ran out, and every report after that is worthless.
Build a code your staff can read at a glance, such as SHRT-102-BLK-40: garment type, style number, color, size. That order makes sorting in the stockroom and searching in the system faster than random numbers.
- Print the price tag and barcode when the shipment is received, not when it goes on display; a piece with no tag gets rung up manually and wrecks the count.
- Standardize color names in a closed list (black, navy, beige) and block free-text entry.
- Keep the style number stable across seasons so you can compare the performance of the same fit year over year.
Generate a consistent coding structure before you load the new collection using the item code generator.
Three metrics to review weekly before any markdown decision
In fashion the decision is made weekly, not annually, and three numbers are enough to make it:
- Sell-through rate:
units sold ÷ units received × 100for each style since it arrived. It shows which styles deserve a reorder and which need early intervention. - Weeks of cover:
current inventory ÷ average weekly sales. If cover runs past what is left of the season, the overstock is certain, not likely. - Turnover:
cost of goods sold ÷ average inventory. Measure it at department level, not for a single item.
The practical rule: tie the markdown decision to weeks of cover, not to the calendar. A style with ten weeks of cover and six weeks left in the season needs action now, while it still sells above clearance pricing. Calculate the effect of the discount on your margin before you announce it, and compare departments against each other using the inventory turnover calculator.
Before you announce a seasonal sale: what the Ministry of Commerce requires
An end-of-season clearance is not an internal decision. The Ministry of Commerce requires a discount license before you advertise any discount, and attaches to that license conditions covering how the price is displayed inside the store.
| Requirement | What it means inside your store |
|---|---|
| A discount license before advertising | No sign, no post and no customer message before the license is issued |
| Displaying the license | A visible copy the consumer can verify by scanning the barcode |
| A list of discounted products with prices before and after the discount | Submitted with the application, and it must match what is on the price tag |
| Discounted products must be no less than 50% | Set the scope of the clearance before you apply, not afterwards |
| A specific discount percentage must be stated | A written, unambiguous percentage for the consumer, not vague wording |
| Disclosing the exchange and return policy during the offer period | Announced to the consumer throughout the discount period |
| Service fee | SAR 300 per store, with immediate execution |
Source: the "discount licenses" service page and the news item on commercial discount rules on the Ministry of Commerce website, both accessed on 1 August 2026. The operational impact is direct: the price tag in point of sale has to show the price before and after the discount, and the previous price has to remain retrievable from the record for the whole term of the license.
Returns and exchanges: the credit note is the correct document
In clothing, exchanges outnumber refunds, and each case has its own document. A credit note is issued by the seller when the value of a simplified tax invoice is adjusted downwards, and a debit note when it is adjusted upwards. Both must be linked to the original invoice that was previously issued.
The Zakat, Tax and Customs Authority (ZATCA) uses an example from this exact sector: a customer bought clothing, then a week later wanted to exchange one piece for a more expensive one. The treatment is for the seller to issue a credit note linked to the original invoice for the exchanged piece, then issue a new simplified tax invoice for the new product and hand it to the consumer.
- Invoices are issued in Arabic in line with the Value Added Tax (VAT) Law and its Implementing Regulations.
- Make sure the simplified invoice carries every required element, including the invoice title and the QR code, to avoid e-invoicing violations.
- The standard VAT rate of 15% is added to the final selling price, and it flows through to the value of the credit note exactly as it does on the invoice.
Sources: the simplified guideline on debit and credit notes, and the tax groups guideline (third edition, May 2026) on the Authority's website, both accessed on 1 August 2026. Review the e-invoicing requirements before you configure the returns screen at the till.
Rolling partial counts instead of closing the store once a year
A full count once a year surfaces the discrepancies far too late, after the season has already ended. The alternative is a rolling partial count that never closes the store.
- Split the sales floor and stockroom into zones, and count one zone a week with the scanner, so the whole store is covered within a clear cycle.
- Count high-value or easily lost items more often, and slow-moving items less often.
- Record every discrepancy with its cause (theft, receiving error, a piece sold under a size other than the one released). An adjustment with no stated cause hides the problem instead of ending it.
Review recurring discrepancies at style level, not store level. A repeated shortage in one specific size is usually a coding error or a barcode mix-up at receiving rather than a genuine loss, and the fix belongs in the receiving room, not in the count report.
Open-to-buy: how much can you spend next month?
Most clothing stores buy on instinct: the owner likes a collection and orders it, then finds at the end of the season that all their cash is hanging on the racks. The tool that prevents this is the open-to-buy budget: a purchasing ceiling calculated for each month separately.
Budget available = planned sales + planned markdowns + target closing inventory − opening inventory − merchandise on order and in transit
The example below is at retail price rather than cost price, because the plan is built on the same logic that sales are measured with. The numbers are illustrative; replace them with your own store's.
| Line item (at retail price, SAR) | September | October | November |
|---|---|---|---|
| Opening inventory | 400,000 | 420,000 | 450,000 |
| Planned sales | 180,000 | 200,000 | 240,000 |
| Planned markdowns | 20,000 | 25,000 | 30,000 |
| Target closing inventory | 420,000 | 450,000 | 400,000 |
| Merchandise on order and in transit | 60,000 | 80,000 | 100,000 |
| Budget available to buy | 160,000 | 175,000 | 120,000 |
Read the table this way: in November the buying budget falls even though sales rise, because opening inventory is high and there is a lot of merchandise in transit. The final figure is a ceiling for purchase orders, not a target to be spent.
- Hold back part of the budget to reorder what is actually selling; committing all of it before the season starts kills your ability to react.
- Deduct every purchase order from the budget the moment it is approved, not the moment it is received.
- Review the numbers monthly once actual sales are closed, not once at the start of the year.
Link purchase orders to the budget inside purchases so the commitment shows up before the shipment arrives.
What is left of your margin after each discount?
A discount is a financial decision before it is a marketing one. The price drops while the cost stays where it was, so profit falls by a larger percentage than the discount itself.
The example below is a piece that costs SAR 100 and sells for SAR 200, with all figures before Value Added Tax.
| Discount | Selling price after the discount | Profit left per piece | Extra units needed to recover the profit |
|---|---|---|---|
| No discount | 200 | 100 | — |
| 20% | 160 | 60 | 67% |
| 30% | 140 | 40 | 150% |
| 40% | 120 | 20 | 400% |
| 50% | 100 | 0 | Cannot be recovered |
The rule the table gives you: extra units needed = discount amount ÷ profit left per piece. At a 40% discount you need five times the volume to reach the same profit, and that does not happen in a retail store.
So build the discount decision around freeing up cash, not around raising profit. Set a floor price for each style that you never go below except in an end-of-season clearance, and calculate the impact before you announce it using the profit margin calculator.
Broken sizes: transfer between branches before you discount
A style stops selling before its quantity runs out. Once the middle sizes are gone and only both ends are left, the assortment is broken: the customer sees the piece, cannot find their size, and leaves. The quantity in the system looks healthy and sales are zero.
The first response is not a discount; it is a transfer between branches.
- Track size completeness for each style in each branch rather than total quantity. A style that has lost its two most-wanted sizes needs an immediate decision.
- Consolidate the scattered units: move the remnants from slow branches to the fastest-selling one to rebuild complete size runs instead of leftovers spread across four branches.
- Transfer mid-season, not at the end of it. Transferring after the clearance has started moves dead merchandise and saddles you with shipping costs for nothing.
- Record the movement as a documented stock transfer between two warehouses, not as a sale and a purchase; mixing the two corrupts cost of sales in both branches at once.
Monitor branch balances in inventory management, and calculate the reorder point for styles that carry across seasons using the reorder point calculator.
The receiving room: the only gateway into inventory
Every inventory error starts at the receiving door. A piece booked in under the wrong color, or in a size other than the one printed on the carton, shows up later as a shortage in the count, and people will hunt for it on the sales floor when its real home is in the receiving record.
- Do a three-way match: the purchase order, the packing list and the physical count, at color and size level. Matching on totals lets every error straight through.
- Do not book a shipment into inventory before its discrepancies are closed. A discrepancy quietly adjusted away becomes a loss with no traceable source.
- Inspect a sample from every style: actual measurement against the labelled size, color consistency between pieces, and the soundness of the stitching and the zip. A recurring defect goes back to the supplier rather than being discovered by your customer.
- Attach the barcode and the price tag in the receiving room, and let no piece reach the shelf without a tag.
Then build a running record for each supplier: shortage rate, size accuracy against the agreed size chart, and days late against the due date. That record settles which suppliers you use next season, and it is your leverage when negotiating price and terms.
Store and online: one stock balance, not two
When you sell the same piece in the store and on the online shop, the risk is not running out of stock; it is selling the same piece twice. In clothing the problem is sharper, because most styles reach the end of the season with a single piece left in each size.
- Keep one balance, updated the moment the sale completes at the point of sale, not in an overnight count.
- Reserve the quantity when the online order is confirmed rather than when it is picked, and release it back to the balance automatically if the order is not paid within a set window.
- Assign the last piece in each size to either the store or the online shop by an explicit decision, or stop showing it online; cancelling a paid order costs more than a late sale.
- Define the return path for online orders in advance: which branch receives it, which warehouse it enters, and when it becomes sellable again.
The rule is a single one: every sales channel reads from the same balance and writes to it immediately. Any delay in updating is a promise to a customer you will not be able to keep.
Frequently asked questions
Related pages on Snad
Share this article: