Notes for owners · CRM, automation and RevOps
Chhath and wedding orders in the same weeks: an order register that does not break
How a Bihar shop keeps Chhath and lagan orders from going missing in the same fortnight, with a register layout, fixed status words, and a rule for when paper is enough.
The GullySales team · Updated 17 Oct 2026 · 6 min read
On this page
In the week after Diwali, a Bihar counter can hear one question all day: "Whose bundle is this?" Chhath orders and the first lagan orders have arrived together. The orders that go missing were written in three places: the counter notebook, the owner's WhatsApp and the karigar's memory. Keep one shared register instead. Each order gets one row, one named person, a promised date before the real deadline, and a status from a short fixed list. Paper or a phone sheet both work, as long as there is only one.
Why this fortnight breaks the notebook
For most of the year a notebook is enough, because the owner remembers what it leaves out. The Chhath weeks take that away. A son working in Surat sends a WhatsApp from the train: two sarees for Maa, a kurta for Papa, keep them ready, we reach on Thursday. The person who ordered is not the person who will collect. The deadline is not a date but a phrase, "Nahay Khay se pehle". It cannot be pushed back.
Then the lagan starts. One wedding family orders for the tilak, the haldi and the wedding itself, which is three deadlines for one family, with a trial somewhere in between. A helper joins the counter for the rush and writes orders in a personal style. By the second week nobody can say which bundles are ready and which are still with the karigar.
The register, column by column
Keep one row per order, not per customer. A family ordering for three functions gets three rows, because each function has its own date.
| Column | What goes in it | Why it matters in these weeks |
|---|---|---|
| Order number | A running number, also on the bill and on a tag pinned to the cloth | Ties the row to the bundle |
| Placed by, and phone | The person who ordered, with the number they used | Often a son or daughter in another city |
| Collects, and phone | The person who will come to the counter | Not always the same person as above |
| Item and detail | Saree, blouse with measurements, sherwani size | One line, not a paragraph |
| Event and its date | Chhath, tilak or wedding, with the calendar date | The deadline the customer cares about |
| Promised date | The date you said, at least a day before the event | Leaves a day to fix a mistake |
| Owner | One name from your staff | The person who answers if it slips |
| Advance | Amount, and whether cash or UPI | Settles the balance at handover |
| Status | One word from the list below | Read in a second |
| Last message sent | Date, and what was said | Stops two people sending the same reminder |
Write the event as a calendar date on the day you take the order. "Before Chhath" means different days to different people.
Pick the status words once, and ban the rest
Free text in the status column is how a register stops being read: "almost done", "ask Raju" and "ok" mean something only to whoever wrote them. Fix the words before the rush and write them at the top of the page:
- Booked: order taken, advance recorded, work not started.
- With karigar: the cloth or item has gone for work.
- Trial due: the customer must come in before it can be finished.
- Ready: on the shelf, tagged, and a message sent to whoever collects.
- Handed over: collected and balance paid.
- Stuck: something is wrong, and the owner column says who is fixing it.
At opening and again before closing, the register's owner reads every row due in the next two days that is not yet Ready. Anything marked Stuck goes straight to the shop owner.
A worked example: the blouse that went to the wrong Sunita
This is an invented case. A saree and tailoring shop in Patna takes two blouse orders in the week before Chhath. Both are for women named Sunita, on the same afternoon. One is at the counter. The other is a WhatsApp from a son in Pune ordering for his mother, to be collected by his father. The helper writes both as "Sunita ji, blouse, Thursday".
On Thursday the father arrives, gives his wife's name, and is handed the counter customer's blouse. An hour later the counter customer comes in. Her blouse has gone. The son in Pune hears about it from his mother, not from the shop. Remaking the blouse in two days costs ₹900 in karigar overtime, and the Pune order does not come back the next Chhath.
Nothing that put it right needed software, though a slip still happens once more that season. The order number now goes on the bill, the register and a paper tag pinned to the cloth. The Ready message goes to the number in the "collects" column, with the order number in it. The helper hands over against that number, never against a name. And "Thursday" became a date.
Paper, a phone sheet or a CRM?
Use the simplest tool the whole team can see.
If one counter takes every order and the owner is always there, a bound register with the columns ruled in advance is enough. Once two people take orders, or the workshop is in another building, move to a shared sheet on phones, so the karigar can see what is due without calling. A CRM earns its place when you want to message these families before the next Chhath and the next lagan. See CRM implementation and customisation for the related service.
Skip the CRM if the festival is days away. Changing systems in the rush invites lost orders, so run the season on paper or a sheet, and move the rows across when the shop is quiet.
After the rush, the register is your customer list
Once the last wedding order is handed over, the register holds names, numbers, what each family bought, and for which event. The son in Pune will order again before the next Chhath if somebody reminds him in time.
Keep every row. Mark the ones with a complaint or a late delivery, and ring those customers before the next season.
Before the first Chhath order
Rule the columns, write the status words at the top of the page, and name the one person who owns the register. Our Bihar page describes how the state's buying seasons run, and pipeline management is the related service if you want it built as a sheet or a CRM. Then tell us what you need.
