Surviving the festive rush: stock planning for Eid, Diwali & the wedding season

For a clothing or fabric shop in India, the calendar isn’t twelve even months — it’s a few intense peaks with long flat stretches in between. Eid, Diwali, Karva Chauth, Navratri and the long wedding season pull forward months of demand into a handful of frantic weeks. Get the stock right and you clear a year’s profit in six weeks. Get it wrong and you spend January staring at unsold lehengas, money that should have been in the bank sitting on a shelf instead.

The shops that do this well are almost never the ones with the best instinct. They are the ones with the best record of what happened last time. This guide is the full playbook we walk new shops through: what to do ninety days out, thirty days out, during the rush itself, and — the part everyone skips — in the fortnight after it ends. Everything here maps to something you can actually do in Kapda Stock, and every step links to the exact page in the documentation that explains it.

The festive calendar a textile shop actually runs on

Before any of the software matters, get the shape of the season straight in your head. Most Indian textile and clothing shops see four demand shapes in a year, and they behave very differently:

The mistake is treating all four the same way. A wedding season is won on a handful of ₹40,000 bills that start as a quotation and take three visits to close. Eid is won on three hundred ₹1,200 bills rung up in four days, where the only thing that matters is that the counter never stalls. The stock plan, the staffing plan and even the billing setup should look different for each.

Count backwards from the peak, not forwards from today

Write the festival date on a piece of paper and count backwards. Your supplier needs lead time. Your karigars need longer. Labels and barcodes need to exist before the goods hit the floor. Here is the countdown that works for most shops:

1. 90 days out — read last season’s numbers and decide the shape of the buy.
2. 75 days out — raise purchase orders with your main suppliers, before their books fill up.
3. 60 days out — issue job work to karigars for anything stitched, dyed or embroidered.
4. 30 days out — catalogue and label everything; fix broken size sets; set credit limits.
5. 14 days out — brief staff, test the printer, build your offers.
6. The rush — bill fast, watch reorder suggestions daily, keep udhaar under control.
7. +14 days — clear dead stock while the mood is still festive, then close the season properly.

Start from last year’s numbers, not a gut feeling

The single biggest mistake in festive buying is buying by memory. Memory is flattering — it remembers the design that sold out in two days and quietly forgets the forty pieces that went out at 40% off in January. Your sales history has no such loyalty. It knows exactly which colours, fabrics and price points moved last Diwali, and which sat untouched from the first day to the last.

Set the Reports hub to a custom range covering the same festive window last year — say the six weeks ending on the festival date — and spend an hour with four reports. One hour, once a year, is the highest-return hour in a textile shop’s calendar.

Three patterns show up in almost every shop’s history, and all three are worth acting on:

• The top twenty SKUs did a disproportionate share of the revenue. They are the backbone of this year’s order.
• The slow movers you eventually marked down are almost always in the same two or three categories every year. Stop repeating them.
• The daily curve is back-loaded. For most shops the majority of festive demand lands in the final ten days — which means a top-up order that arrives on day eleven is worth far more than a bigger order placed on day one.

Build the purchase list from velocity, not from feel

Once you know the shape of the buy, the quantity question becomes arithmetic. Kapda Stock watches stock two ways, and the difference between them matters enormously in a festive month.

Minimum stock is a safety net you set

Every variant has a Min stock level. When stock falls to or below it, the variant gets a red Low stock badge, appears under the *Low stock only* filter in Inventory, and counts on the dashboard tile. Every morning at 9:00 AM IST the owner also gets an email listing each low item as *product (colour, size): X left (min Y)*, plus a WhatsApp alert with the count. Nothing is sent on days when nothing is low, so the alert stays meaningful. The full behaviour is in Low stock & reorder.

Reorder suggestions follow the season

Suggestions are calculated from the last 30 days of actual movement, so they rise on their own as the festive curve steepens. The arithmetic is deliberately simple enough to check by hand:

1. Average daily sales = units that left stock in the last 30 days ÷ 30.
2. Suggested quantity = (lead time × average daily sales) − current stock, rounded up.
3. A variant is only suggested when that number is above zero, and the list is sorted by quantity, largest first.

Lead time defaults to 7 days. So a saree that sold 60 pieces in the last 30 days is selling 2 a day; with 5 pieces left, the suggestion is 7 × 2 − 5 = 9. Everything that removed stock counts as movement — sales, stock-outs, job-work issues and cuts — which is what makes the number honest for a fabric shop that also sends material to karigars.

Turn the list into orders, not notes on a phone

Raise a purchase order against the supplier rather than sending a WhatsApp and hoping. The Purchases section of the Reports hub then shows open POs with Ordered, Received, Pending, Pending value and the expected date — which, in the middle of a rush, is the difference between chasing a supplier on the right day and discovering on the wrong one. For anything going out to a karigar, use Job work: material leaves stock when the job is issued and finished pieces come back in when it is received, so fabric sitting at a tailor’s workshop is never mistaken for fabric you have sold.

Get the catalogue ready before the crowd arrives

Nothing slows a festive counter like a product that isn’t in the system. If a design has no SKU, no barcode and no price, it becomes a manual line, an argument, and a stock count that never reconciles. Do the catalogue work in the quiet fortnight before the rush.

• Arriving stock with a supplier spreadsheet? Use Bulk import rather than typing — one row per product, with `hsn_code`, `gst_rate`, `selling_price`, `opening_stock` and `min_stock` filled in. Valid rows import and invalid rows are listed with the reason, so one bad row never blocks the rest.
• Add variants — colour, size, design — rather than creating a separate product per shade. Variant-level stock is what makes the broken-size-set report work.
• Print barcodes and labels for everything before it goes on the floor. Scanning is the single largest speed gain at a festive counter.
• Set Min stock on the fast movers now. A minimum you set in a calm week is the alert that saves you in a busy one.

Fix the broken size sets

The 📏 Broken size sets table on the Reports hub lists products where some sizes are out of stock while others still hold stock. This is quietly one of the most profitable reports in the app during a festive month: a customer who wants a large in a design you only have in small does not buy the small. They leave. Two weeks before the peak, work that list and fill the gaps.

Speed at the counter is the whole game

Festive footfall punishes slow billing more than it punishes anything else. A queue that stalls is not a delay — it is a walkout. POS billing creates a full tax invoice in one step: stock is deducted, payments are recorded, any unpaid amount lands on the customer’s ledger, and the receipt is ready to print. The job in the week before the rush is to make sure your staff can drive it without looking at the screen.

The shortcuts to teach staff this week

Park bill deserves special attention in a festive week. A customer steps away to consult a relative; the cart, the customer, the bill discount, the GST setting and the coupon are all saved under a label such as *3 items · ₹1,250 · Asif*, the screen clears, and you serve the next person. Held bills belong to the member who parked them, so two people on two counters never see each other’s list. The only thing to re-apply on resume is the coupon.

Payments the way festive customers actually pay

Very few large festive bills are settled with a single tap. + Split payment lets you take ₹1,000 in cash and the rest by UPI on the same invoice; collect less than the total and the remainder automatically appears as On credit against the customer’s ledger. Set a UPI ID in Invoicing settings and every receipt and invoice PDF carries a *Scan to pay via UPI* QR for the exact amount — which, on a busy evening, removes the entire "what’s your number" conversation.

Test the printer before the season, not during it. Print thermal drives a USB or serial ESC/POS printer through the browser’s Web Serial feature on desktop Chrome or Edge, and the first print asks you to pick the port. If the browser doesn’t support it you fall back to the PDF receipt. The full setup, including the 80 mm layout, is in Printing & PDF.

Staff, roles and the money that shouldn’t walk out

Festive season is when shops hire extra hands, and when access control stops being theoretical. Two things are worth an hour of setup:

• Roles decide who can bill. POS needs the Manager role or above. Cashier and Salesman are read-only roles and cannot complete a sale — so anyone standing at a counter this season needs Manager. See Roles.
• Module access narrows what they see. A salesman does not need the profit report. The module access matrix tightens each person individually, and it only ever narrows what their role already allows.

There are also two safety limits worth knowing before a peak day so they never surprise you: a single sale can carry up to 200 lines, and a member can create at most 30 invoices per minute. Neither is reachable in normal trade, but it is better to have read it here than to discover it at 8 PM on the busiest evening of the year.

Extend udhaar carefully — and track every rupee

Festivals are when regulars ask for credit, and saying no to the right person at the wrong moment costs you a relationship. Say yes deliberately instead of reluctantly. Set a credit limit on the customers who need one *before* the season starts. When a sale would push a customer past their limit, POS shows the projected balance and the amount over; a Manager cannot complete it, while an Admin or the Owner can confirm an override, and the override is recorded on the invoice. That is a much better conversation than the one you have in February.

Everything unpaid lands on the customer’s ledger as a credit entry the moment the sale completes, so the khata is right without anyone writing in a book. When the season ends, the automatic udhaar recovery ladder starts collecting on your behalf — we pulled that apart step by step in Never chase udhaar again.

Plan for the line going down

Broadband fails on exactly the evenings you can least afford it. The POS is built to keep billing through an outage: a sale that cannot reach the server is parked on the device, the cart clears, and it becomes a real invoice with a real number when the connection returns. The important preparation is one habit — open POS on the counter device at the start of the day and leave it open, because a screen you have not loaded yet cannot load without a connection. The full rules, including what happens when a sale is rejected on sync, are in Offline mode & sync and in The internet goes down. Your counter doesn’t.

Market the rush without annoying anyone

Offers work in a festive month, but only if they reach people. Build discounts and coupon codes in Offers & promotions so the counter applies them consistently instead of each salesman negotiating separately. Then be realistic about reach.

Two other limits shape a festive campaign: a business can send 1,000 automated messages a day (extras are queued for the next 9:00 AM IST run), and each member can trigger 3 bulk sends an hour. Plan a broadcast in batches rather than one enormous blast on the evening before the festival.

The fortnight after: clear what didn’t sell

This is the part almost every shop postpones, and postponing it is what turns leftover festive stock into next year’s dead stock. The 🐌 Dead stock table lists items with stock and no sale in 90+ days, with the Value locked, Idle days and a Suggested off — a clearance discount that deepens with time: 20% from 90 days, 30% from 180 days, 40% from 365 days. Right after a festival, customers are still in a buying mood and the discount you need is at the shallow end of that scale. Six months later it will not be.

Close the season properly

When the shutters come down on the last festive night, the numbers are the most valuable thing in the shop. Spend an evening on four things while the season is still fresh:

1. Check the Day book for the peak days. It assembles itself from cash movements and closes automatically at 11:55 PM IST, so the only job is to look at it and make sure the till agrees.
2. Run the aging report and see how much of the season’s revenue is still sitting on other people’s khatas. Anything in the 61–90 and 90+ buckets gets a call this week, not next month.
3. Take the month to your CA with the GST filing pack — the pre-filing checks catch a malformed GSTIN or a missing HSN code before the return is rejected. We walk through the whole compliance flow in What Kapda Stock really does about GST.
4. Write down what ran out and what didn’t, and save the ABC ranking as a PDF. Next year this hour becomes ten minutes.

“Last Eid we knew exactly what to stock because the app showed us the previous year, colour by colour. We sold out of the right things and barely marked anything down.”

The 90-day festive checklist

If you read nothing else, work this list. Each line is a job, not a principle:

1. Read last year’s festive window in the Reports hub — ABC, category performance, sales by time, returns.
2. List the top twenty SKUs to reorder and the categories to cut.
3. Raise purchase orders 75 days out; issue job work 60 days out.
4. Catalogue and label arriving stock; use bulk import for supplier spreadsheets.
5. Set Min stock on every fast mover and fill the broken size sets.
6. Give counter staff the Manager role and tighten module access.
7. Set credit limits on udhaar customers before the season, not during it.
8. Test the thermal printer and confirm the UPI QR prints correctly.
9. Open POS on the counter device each morning and leave it open.
10. Check reorder suggestions daily through the rush.
11. Clear dead stock in the fortnight after, at the shallow end of the discount scale.
12. Close the season: day book, aging report, CA pack, notes for next year.

None of this is glamorous, and none of it is difficult. It is simply the difference between a season you survive and a season you profit from. The shops that treat the festive rush as a planning exercise rather than an endurance test end up with the same footfall, the same staff and dramatically more money in the bank on the other side. If you want to see how the whole loop fits together in your own shop, you can set up a workspace in under a minute, or compare the plans first.