Clothing Store Software: Size, Colour and the Stock You Thought You Had

The matrix is the product

“We have forty shirts” is not useful. Forty shirts in which sizes, which colours, and how many of the one that actually sells? A clothing shop lives or dies on the mix, and the mix is the product record.

If the system stores a shirt as one item with a quantity, the size and colour have to live in a note, a separate code, or someone's memory. None of those survive a staff change.

Set up variants once

Choose the axes the shop actually uses — size and colour are common; sleeve length, fit or fabric may matter for some lines. Each combination becomes a sellable unit with its own barcode, price and stock. The parent item holds the shared name, category, tax and supplier.

That structure gives three things a flat item cannot:

• Scan the exact piece. The barcode identifies M / Navy, not just “shirt”.
• Reorder the gap. The size that sold out is visible without opening every stock line.
• Move stock intelligently. A transfer or return knows which variant is moving.

Markdowns and season end

Clothing has a clock. A full-price rack in November is a discount rack in February. The software should let the shop change a price without rewriting history: old invoices keep the old price, new sales use the new one, and the margin report shows when the discount started.

Bulk price changes by category or season are useful, but they must be deliberate. A single “update all prices” button with no preview is how last season's cost gets applied to this season's stock.

Returns are normal, not fraud

A customer buys two sizes and returns one. That is a healthy sale, not a loss. The return note has to bring back the exact variant, at the price actually paid, into the right outlet. If the system only returns a generic “shirt”, the size that comes back may never be sellable again.

Exchange is the same operation with a second line: return one, sell another, settle the difference. Staff should not have to cancel the original invoice to do it.

Wholesale and retail in one shop

Many clothing shops sell a single piece to a walk-in customer and a dozen to a reseller from the same rack. Price tiers per customer or per quantity handle that without a second price list. The rule should be visible on the invoice so the discount is explainable later.

Bangladesh specifics

Seasonal demand around Eid and winter is compressed into a few weeks. Purchase orders and goods receipts have to be quick, and stock has to arrive at the right outlet, not just the warehouse. Cash, bKash and card are all normal; printed invoices matter for corporate orders and for resellers who need a VAT document.

What Zuviq Book covers

Variant axes with per-variant barcode and stock, price tiers, returns and exchanges, multiple outlets, purchase orders and goods receipts, and the same catalogue for quotations and invoices. The public bill link is useful for resellers who lose the paper.

The shop walkthrough is in the clothing brochure; for mixed general retail, see general retail.

Audit one style before you commit

Pick the style with the most size-colour combinations. Enter every combination, receive a real purchase, sell three pieces, return one, and run the stock report by variant. If that report is clean, the rest of the catalogue will be clean too.

Start the trial with every module open for seven days. Pricing is here.