Clothing and shoe stores
Clothing store POS for sizes, colours, seasons and branches
PointLit is a clothing store POS that keeps every size and colour of a model as its own variant, with its own stock, price and barcode. It groups the range into seasonal Collections, moves stock between branches with send-and-receive transfers, puts refunded pieces back through the stock ledger, and shows which sizes really sell.
What a clothing store POS has to handle
A clothing or shoe shop does not sell 200 products. It sells 200 models, and each one comes in sizes and colours. A linen shirt in three colours and four sizes is twelve different things on the shelf, and a customer asking for navy in L wants an answer in seconds.
PointLit was built around that kind of shop. Sizes, seasons, branches and the stock room all write to one append-only ledger, so every number on the till can be traced to the delivery, sale, transfer or count behind it.
Sizes and colours, with swatches on the till
You create a model once: in Products choose New product, pick what it varies by, such as size and colour, and fill the grid. Each combination becomes its own variant with its own stock, price and barcode, and colours carry swatches, so the cashier picks the navy shirt by its colour rather than by a code. Scanning a label adds the exact size and colour to the cart. Shoe sizes such as 38 to 45 work the same way.
Collections for seasons and end-of-season clearance
Every product belongs to one Collection, such as Summer 2026. A Collection is Planned while you build the range, Open while it sells and Closed when the season is over, and it numbers its own models. At the end of the season, Carry over… moves what did not sell into the next Collection with its stock and cost, and Markdown % takes a percentage off the price in the same step. Barcodes are kept by default, so old labels still scan.
Stock in every branch, and transfers between them
Stock is kept per branch. When a size has run out, Where else is this? on the till shows how many pieces your other shops hold, while the till is online. A transfer has two ends: the sending branch presses Send and the pieces show In transit, and nothing lands at the other branch until someone there presses Receive and enters what arrived. A short delivery shows Partly received, and every gap stays on the Differences tab.
Exchanges and refunds that keep the stock right
A refund is a new document written against the original bill, never an edit to it. You choose the lines coming back and whether to Put the stock back: a damaged piece can be refunded without returning to the shelf, and that choice is recorded. Loyalty points and account balances are settled in proportion.
An exchange, such as an M swapped for an L, is two records: a refund of the M with the stock put back, and a new sale of the L. Refunds, voids and discounts are separate permissions. The Owner and Manager roles hold them by default and the Cashier role does not.
Barcode labels for every piece that arrives
When a delivery is booked in Goods receipts, you can send the whole receipt to the Barcode Printer, so every piece gets its own label. A clothing label usually shows the model number, size and colour, price and barcode, plus a Was price during a markdown. Arabic names print correctly because PointLit turns the label into a picture before it reaches the printer, through the PointLit Windows app or the browser's print dialog.
Blind counts before the season closes
A stock count can be limited to one Collection and run as a Blind count, which hides the system quantity while staff enter what is on the shelf. Posting the count writes the differences to the ledger as one adjustment. Counting a season before you carry it over means the carry-over moves real pieces, not what the system believed.
Reports a clothing buyer actually reads
- Size curve: Units sold and On hand per size, with Share of sales next to Share of stock.
- Collection performance: one line per Collection with Pieces sold, Net, Returns, Margin, On hand and Sell-through.
- Where is this model?: one model's stock in every branch.
- Stock movements filtered to one item: its stock card, line by line.
- Refunds and voids, and Discounts: who gave money back, and why.
Worked example: a Cairo boutique with two branches
Here is how one season could run for a boutique with a branch in Nasr City and a second in Sheikh Zayed. The figures are an illustration, not a customer's.
The buyer creates Summer 2026 and a linen shirt in 3 colours and 4 sizes: 12 variants at EGP 850 each, with VAT at 14% included in the price, so each shirt is EGP 745.61 net plus EGP 104.39 VAT. A delivery of 48 pieces is booked into Nasr City, and all 48 labels go to the Barcode Printer from the goods receipt. Nasr City sends 16 pieces to Sheikh Zayed, and they show In transit until Sheikh Zayed presses Receive.
In July a customer in Sheikh Zayed asks for navy in L. Where else is this? shows 2 at Nasr City, so she is sent to the right shop instead of leaving with nothing. Another customer swaps an M for an L: the manager refunds the M with the stock put back, and the cashier rings the L as a new sale.
By September 34 of the 48 shirts have sold, a sell-through of about 71%. The Size curve shows M and L made most of the sales while S stayed on the shelf, which shapes the next order. A blind count of the Summer Collection finds 13 shirts rather than 14, and posting it records the missing one. The buyer carries the 13 into the next Collection with a Markdown % of 30, so EGP 850 becomes EGP 595, and closes Summer 2026.
How it works in PointLit
- In Collections, create the season. It starts as Planned.
- In Products, choose New product, pick what it varies by (size and colour) and fill the grid.
- Book the delivery in Goods receipts and send it to the Barcode Printer for labels.
- Open the Collection and sell. Use Transfers to send stock to another branch, where staff press Receive.
- At the end of the season, run a Blind count of the Collection, choose Carry over… with a Markdown %, and close the old Collection.
Questions and answers
- Can PointLit handle sizes and colours for a clothing store?
- Yes. You create a model once and pick what it varies by, usually size and colour. Each combination becomes its own variant with its own stock, price and barcode, colours show as swatches on the till, and stock is kept per branch. The Size curve report then shows which sizes sell and which sit on the shelf.
- Does it work for a shoe store?
- Yes. Shoe sizes are variant values like any other, so a model in sizes 38 to 45 and two colours becomes sixteen variants with their own stock. Labels can carry the size and colour, Where else is this? finds a size at another branch, and the Size curve report shows the sizes your customers actually buy.
- How do I exchange an item for a different size?
- An exchange is two records in PointLit: a refund of the piece coming back, with Put the stock back chosen so it returns to the shelf, and a new sale of the piece the customer takes. Refunding needs the refund permission, which the Owner and Manager roles hold by default. There is no single exchange screen yet.
- How do I clear last season's stock?
- Choose Carry over… on the old Collection. PointLit copies the products you pick into the next Collection, moves their stock and cost at the branches you choose, and Markdown % takes a percentage off the price. Barcodes are kept by default, so the old labels still scan, and the old Collection can then be closed.
- Can I import my product list from Excel?
- Not yet. PointLit has no self-service import today, so a range is built in the product screens, where one model with its size and colour grid is a single form. If you are moving a large catalogue, write to support@pointlit.com with roughly how many models you have and we will plan the move with you.
Bring your sizes, seasons and branches into one system
Registration is closed for now. Leave your details and we will tell you the moment it opens.
Request early access