Apparel Billing Software with Size & Colour Stock Control

The Problem With Selling Clothes Is the Combinations

A grocery shop sells one SKU of Maggi noodles. You sell one kurta in four colours and six sizes. That's 24 SKUs before you've added the next style. Multiply that across 50 designs and you're managing over a thousand product variants, all in one modest-sized store.

Most generic billing software wasn't built for this. It handles items, not variants. So you either create a separate product entry for every size-colour combination (and lose your mind maintaining it), or you bill loosely and hope the stock count sorts itself out at the end of the month (it won't).

Good apparel billing software solves this at the structure level. Here's what that actually looks like in practice.

Size-Colour Grids: The Thing Most Software Gets Wrong

Imagine you stock a floral printed shirt in red, blue, and yellow, across sizes S, M, L, XL, and XXL. You want to know: how many red XLs do you have left? How many blues sold this week?

If your billing software makes you scroll through a flat product list to find "Floral Shirt - Red - XL" as a separate entry, you're doing more work than you should. A variant grid lets you create one parent product, attach the colour and size attributes, and see stock across all combinations on one screen. When a bill is raised for two blue Ls, those two units drop from the right cell automatically.

This is not a luxury feature. Without it, you either stop tracking by variant (and lose accuracy) or you spend an hour a day maintaining a spreadsheet on the side. Neither is sustainable when your catalog grows.

Barcodes Across Variants

Every size-colour combination needs its own barcode. A red M and a blue M are different products at the point of sale. If they share a barcode, your cashier has to manually select the variant at billing, which slows things down and introduces errors.

A proper system generates unique barcodes per variant. You print the label, attach it at receiving, and at billing the scan pulls up the exact variant, no guesswork. When you receive a fresh shipment of 60 pieces across 12 variants, you scan each group, the quantities update, and you're done in under five minutes.

For stores with high footfall, this matters especially on weekends. A queue of six customers and a slow billing process is a different kind of loss.

How GST Works for Apparel (and Why It Trips People Up)

Garments in India carry different GST rates depending on the sale price. Most readymade garments under Rs. 1,000 per piece are taxed at 5%. Above Rs. 1,000, the rate goes to 12%. Footwear has its own slab structure.

This sounds simple until you're selling a mix. A customer buys one kurti at Rs. 850 and one at Rs. 1,200 in the same bill. The software needs to apply 5% to the first and 12% to the second. If you're managing this manually or using a generic billing tool that applies one fixed tax rate across all products, your GST returns will be wrong.

Billing software built for apparel handles this with a tax rate field per product, so the right slab is applied automatically. When you file your GSTR-1, the data is already split by rate. No recalculation, no scrambling before the due date.

Tracking What's Actually Moving

Most fashion retail losses aren't from theft. They come from buying the wrong mix. You ordered 30 units of a kurta: 10 in black, 10 in mustard, 10 in pink. The mustard sold out in two weeks. The pink ones are still sitting in the back three months later.

Good stock reports tell you this by variant, not just by style. You want to see: mustard moved fastest, black was steady, pink needs a discount or a return to the supplier. Without variant-level sales data, you're ordering next season's stock based on gut feel.

Picture a standalone women's boutique in Jaipur with around 200 active styles. If they're only seeing total sales by style, they'll reorder the same colour mix and end up with the same dead stock. Variant-wise reports fix this, and they're only useful if the billing software was capturing variant data from the start.

Managing Seasons and Clearance Stock

Apparel has a shelf life that grocery doesn't. A salwar suit that doesn't sell before the season changes becomes a clearance item. You need to be able to identify that stock quickly: what's been sitting longest, what's low on units but high on dead variants, where to apply discounts.

Some stores handle this with a separate rack and a rough mental tally. That works until you have three racks and can't remember what came in when. A billing system that timestamps stock receipt and flags slow-moving variants by age gives you that picture without a physical audit every week.

The goal is to catch these items when you still have time to move them at a slight discount, not when you're writing them off at 60% off because the season's already gone.

Returns and Exchanges Without Confusion

A customer brings back a blue L because they want a blue XL instead. That's not a refund, it's an exchange. Your billing software should be able to handle this cleanly: return the blue L to stock, issue the blue XL, and if there's a price difference, charge or refund the delta.

If your system doesn't have a clean exchange flow, what typically happens is a manual workaround: delete the original bill, create a new one, update stock by hand. Every manual workaround is an error waiting to happen, and at month-end your stock count will be off by exactly as many exchanges as you fudged through.

What to Actually Check Before Buying Software

If you're evaluating apparel billing tools, the questions worth asking before you commit:

• Can I create products with size and colour variants under one parent SKU?
• Does it generate unique barcodes per variant?
• Does it apply GST by slab based on unit price, or just one flat rate?
• Can I see stock and sales reports broken down by variant, not just by style?
• How does it handle exchanges (not just returns)?
• Can multiple staff log in, and does it track who billed what?

If the answer to any of the first three is no, you'll be working around the software rather than with it.

Unsold combinations become dead stock fast — the mechanics are the same as in our electronics dead stock guide. And if you're still on spreadsheets, FEFO without an ERP shows the lightweight way to rotate stock.

Where software fits for apparel

Whatever software you choose, the test is variant-level stock truth: every size-colour combination has to be its own stock line, or the system is just a prettier version of the notebook. Apparel is one of ShelfLifePro's verticals, and every plan has a 14-day free trial, no credit card required — enough to load one rack's worth of stock and see whether it fits how you actually sell.

For stores with more complex needs, like multi-outlet tracking or supplier-wise purchase history, the paid tiers cover that. But if you want to see whether variant-level billing actually works for your catalog before spending anything, the free tier is a reasonable place to start.

Your stock is already complicated enough. Your billing software shouldn't add to it.