The Eid war story
On the night before Eid, the lane outside a master tailor’s shop in Lahore’s Ichhra Bazaar is still crowded at 1 a.m. Inside, three karigars are finishing the last suits under tube lights, the masterji is handing over parcels across the counter, and a queue of customers is arguing — politely at first, then not so politely — about whose suit is actually ready.
Eid is the tailor’s harvest season — and his hardest test. In the last ten days of Ramadan, a shop that stitches eight or ten suits a day in normal weeks suddenly takes fifty or sixty bookings a day: an order surge of 500–600%. Every customer wants his suit before Chand Raat, and every customer is convinced his order was promised first.
The last Ashra runs on eighteen-hour days. The shop opens after sehri and stays open past midnight; the cutting master works through the afternoon, the karigars stitch through the night, and the masterji snatches sleep on a charpai in the back room. By the 25th of Ramadan, most good tailors stop taking new Eid orders altogether — the handwritten “Booking Closed” sign goes up after the first Ashra, because every booking taken after that is a promise the shop cannot keep.
The order surge a tailor faces in the last ten days of Ramadan — from about 10 suits a day to 50 or 60.
The length of a workday in the last Ashra — open after sehri, closed long past midnight, every day until Eid.
And all of this — hundreds of Eid suits, advances, balances, promised dates — lives in a paper register and a drawer full of naap slips. A slip goes missing and a customer’s naap is gone. A name is misread and the wrong suit goes home on Chand Raat. A balance is forgotten in the rush and never collected. The war story repeats every Eid, in every bazaar, because the system running it was designed for ten suits a day — not sixty.
The language of naap
Before anything is cut or stitched, a tailor shop runs on language. Every customer who walks in is translated into nine measurements — the naap — written on a paper slip in the tailor’s own shorthand. Lose the slip, and the customer effectively does not exist. Here is the vocabulary every Pakistani tailor shop lives by:
Qameez length (lambai)
The full length of the shirt, from shoulder to hem. The first number the tailor calls out, and the most argued-over — half an inch too long and the qameez looks borrowed; half an inch too short and the customer will not accept it.
Bazu
Sleeve length, from the shoulder tip to the wrist. A bazu that runs long swallows the hand; one cut short shows the wrist bone and ruins an otherwise perfect suit.
Tairum
The shoulder-seam measurement. This is the skeleton of the suit — get the tairum half an inch wrong and the shoulders sit crooked no matter how fine the stitching is.
Gala
The neck and collar. Too tight and the customer cannot breathe through a wedding dinner; too loose and the collar stands away from the neck like a badly fitted uniform.
Chest (seenah)
The chest circumference — the foundation of the whole fit. Every other shaping decision on the qameez is judged against this number.
Kamar
The waist, where the qameez is shaped to the body. The difference between a boxy shirt and a tailored one lives in this single measurement.
Ghera
The hem flare — the circumference of the qameez at its bottom edge. A wide ghera for formal and traditional wear, a narrow one for the slim modern cut; customers are surprisingly passionate about it.
Shalwar length
The full length of the shalwar, waist to ankle. It must break exactly at the shoe — pooling fabric at the ankle marks an amateur, a floating hem marks a disaster.
Panchah (mohri)
The ankle opening of the shalwar. Narrow for the modern tapered look, wide for the traditional cut. Young customers will debate the panchah longer than any other measurement.
Nine numbers, scribbled on a slip of paper, rubber-banded to a bundle of cloth. That slip travels from the counter to the cutting table to the karigar’s machine — and if it falls behind a drawer, or the ink smudges in the monsoon humidity, years of a customer’s loyalty can end in a single badly cut suit. The naap is the most valuable data a tailor owns, and paper is the worst place to keep it. For the full routine of saving those nine numbers safely, see our guide to the darzi naap measurement app.
The order lifecycle, step by step
Every suit — whether booked in the calm of October or the madness of the last Ashra — travels the same six stages. When the shop is quiet, the masterji carries the sequence in his head. When sixty suits are moving at once, nobody can. Here is the lifecycle:
Booking
The customer is measured, the naap is recorded, an advance is taken, and a delivery date is promised. Nothing moves without this step.
Cutting
The cutting master cuts the cloth to the naap. The most skilled step — and the only one that cannot be undone.
Stitching
The karigar sews the suit. This is where the Eid queue forms, and where knowing the true order of work matters most.
Finishing
Buttons, loops, pressing, and a final check. The step most often skipped under pressure — and the first thing the customer notices.
Delivery
The suit is handed over, tried on, and minor alterations are noted on the spot instead of becoming a second visit.
Payment
The balance is collected, a receipt is issued, and the account is closed. No balance is left to be “remembered later”.
On paper, every stage is a chance to lose something: the booking slip with the naap, the cutting sequence, the karigar’s pile order, the finishing check, the right parcel at delivery, the pending balance. Software enforces the sequence instead — a suit cannot be marked delivered before it is stitched, and a balance cannot be forgotten because it sits on the order until it is paid.
You can watch the whole lifecycle in the live demo — on real screens, with sample tailor data.
The Eid readiness checklist
Eid cannot be survived on talent alone. The shops that come through the rush with their reputation intact all do the same seven things:
1. Close bookings before you drown
Set the Eid cutoff right after the first Ashra and hold it. The shops that suffer most are not the ones with too few karigars — they are the ones that kept saying “ho jayega” until Chand Raat. A system shows your true queue length, so the cutoff is a number, not a guess.
2. Take an advance on every Eid booking
No advance, no booking. The advance is your cancellation insurance: when a customer does not return, the cloth and the cutting time are already paid for. Recorded advances also end the annual argument about “how much did I already pay?”
3. Give every order a serial number
On Chand Raat there are seventeen Ahmeds waiting at the counter. A serial number on the booking, the cloth bundle, and the finished parcel ends the “which Ahmed?” problem forever.
4. Sequence the stitching queue
First booked, first stitched — with urgent orders flagged, not shouted. When the karigar asks “what’s next?”, the answer comes from the queue, not from whoever is shouting loudest at the counter.
5. Confirm delivery dates in writing
Send every customer their promised date on WhatsApp at booking time. A date in writing ends ninety percent of counter arguments before they start.
6. Reconcile cash every night
Eid-week cash piles up fast — advances in, balances out, karigar payments going out. Count it every night against the day’s bookings. A ten-minute routine beats a post-Eid mystery.
7. Keep a waiting list
Cancelled and no-show slots are gold in the last Ashra. A waiting list turns every cancellation into a filled slot within the hour — instead of an empty machine and a lost suit’s worth of income.
Paper register vs Excel vs Rahnivo
Most tailors who leave paper land on Excel first — a spreadsheet of orders that one person updates, usually at night, usually from memory. It is a half-step: better than nothing, but one wrong sort scrambles every row, and it still cannot remind anyone of anything. Here is how the three options compare on the jobs that actually matter.
| What you need to do | Paper register | Excel sheet | Rahnivo system |
|---|---|---|---|
| Naap records | Paper slips in a drawer — lost exactly when you need them | A row in a sheet, if someone typed it in | Every naap saved to the customer profile, forever |
| Order stage tracking | Memory, and shouting across the shop | A status column, updated when someone remembers | Booking → Cutting → Stitching → Finishing → Delivery, one click per stage |
| Eid booking cutoff | A handwritten sign on the door | Not managed | Cutoff by queue capacity — bookings stop when the shop is full |
| Pickup reminders | None — customers crowd the counter asking | None | Automatic WhatsApp message when the suit is ready |
| Advance & balance | Ticked in the register margin | A column, updated by hand | Advance and balance on every order, settled at delivery |
| Karigar workload | Whoever shouts loudest gets the next suit | Not tracked | Orders assigned per karigar, output visible at month end |
| Monthly earnings | Counted by hand at month end | Formulas that break when rows move | Ready in one click — orders, advances, pending balances |
| Backup if records are lost | Fire, water, or a lost drawer ends it | Only if you saved copies somewhere else | Cloud backup — every naap is safe |
Running a tailor shop like this? See the system free on WhatsApp →
See it in action
Watch a one-minute walkthrough of the Rahnivo tailor system — a suit booked, stitched, and delivered.
Want the full tour? Explore the tailor system.
Frequently asked questions
Eid ke season mein itne saare orders kaise manage karein?+
System mein har order ki booking date aur promised delivery date record hoti hai. Eid se pehle aap ek screen par dekh sakte hain ke kaun se suit stitching mein hain, kaun se ready hain, aur kaun se late ho rahe hain. Booking cutoff lagayen — jab queue full ho jaye to naye Eid orders band kar dein, taake liye gaye waade poore hon.
Naap slip gum ho jaye to kya hoga?+
Kuch nahi — kyunke naap ka asal record system mein mehfooz hota hai. Customer ka naam search karein aur uska poora naap foran screen par aa jayega: qameez length, bazu, gala, kamar, sab kuch. Kagaz ki slip sirf backup hai; asal record digital hai.
Can the system handle urgent or Eid-rush orders separately?+
Yes. Any order can be flagged as urgent or Eid-rush, which pushes it to the top of the stitching queue and highlights it until it is delivered. The regular queue keeps moving in booking order, so urgent orders never silently swallow the normal ones.
Can I track which karigar is stitching which suit?+
Yes. Every order can be assigned to a karigar at the stitching stage, so you always know who is working on what. At month end you can see each karigar's completed suits — useful for wages, bonuses, and settling the eternal question of who is actually the fastest.
Do customers get pickup reminders?+
Yes. When a suit moves to the ready stage, the customer gets a WhatsApp message that the suit is ready for pickup or trial. During the Eid rush, this alone clears the daily crowd asking 'suit tayyar hua?' — because the system already told them.
Is my customers' naap data safe?+
Yes. Every naap is stored with encrypted cloud backup. If a register is lost or a drawer of slips goes missing, every customer's measurements are still one search away and can be restored on any device in minutes. Only your shop's login can see your records.
