A dyeing and printing process house in Surat, Ahmedabad or Tirupur looks like a factory: jets, jiggers, stenters, printing tables and an ETP. Commercially, it is a service business. The grey fabric belongs to the trader who sent it, and the house charges a processing rate for adding shade, print and finish.
That is why accounting software fits a process house so badly. Tally sees dyes, chemicals, wages, power and processing invoices. It does not see the customer lots moving across the floor, which machine each one is waiting for, whether its shade passed, or whether it has been billed. This guide is for owners, dye masters and office managers of dyeing and printing process houses. It explains where process house margins leak and how ERPDrive's Process House Edition closes each gap.
Why Process House Margins Leak
A process house earns its money in a narrow band. The processing rate is agreed with the trader in advance, often under pressure from other houses in the same cluster. The costs are dyes, chemicals, steam, power, water treatment, labour and machine time, and most of those are spent whether a batch comes out right or not.
So margin depends on three things the rate card cannot control. First, how many batches have to be run twice, because every re-dye spends the full cost of a batch again for no extra revenue. Second, how much machine time sits idle while lots wait for the wrong machine, because the fixed cost of a jet runs every hour. Third, whether every completed lot is actually billed at the agreed rate, because an unbilled lot is pure loss of revenue already earned.
None of these show up in the books. A re-dye looks like normal chemical consumption, an idle machine like a normal power bill, and an unbilled lot is simply absent. The fix has to sit at the lot and batch level, not in the ledger.
Key Takeaway: In a process house, the expensive mistakes are not in the chemistry. They are in identity, approval, scheduling and billing: knowing whose lot it is, whether its shade passed, which machine can run it, and whether it has been invoiced.
8 Problems Process Houses Face, and How ERPDrive Solves Them
Problem 1: Lot Mixups Between Customers
The Problem: Dozens of traders send grey fabric, and many of them send similar qualities in the same week. When a lot's identity is a handwritten slip tied to a bale, lots get dyed against the wrong programme or billed to the wrong party. Sorting it out costs days of searching and some of the customer's trust.
How ERPDrive Solves It: Grey inward receipts record every fabric on the customer's challan, each with its own quality, quantity and panna, tagged to that customer. Fabric names are free entry, so any quality a trader sends is recorded as it is. When a batch is created, the batch card links back to the grey lot it consumes.
The Result: Every lot carries its owner and its challan from inward to dispatch. For the wider principle, see our guide to batch tracking and traceability.
Problem 2: Shade Rejections Found After Delivery
The Problem: Shade is often approved by eye against a swatch, under whatever light the floor has. A lot that looked right leaves the house, the trader's buyer rejects it, and the process house pays for re-processing: dyes, chemicals, steam and machine hours, plus a delay on the next lot.
How ERPDrive Solves It: The shade library holds a standard and a Delta E tolerance for each shade. At the shade-approval stage the measured Delta E against the standard is recorded, and the batch clears the gate only within tolerance.
The Result: Out-of-tolerance batches are caught at the machine, where a correction is cheapest, instead of at the trader's godown. See our guide to rejection analysis and rework.
Problem 3: Recipes That Live in One Person's Head
The Problem: The dye master knows which recipe gave the approved shade last time, on which quality. When that knowledge sits in memory or a personal notebook, repeat orders drift, a new shift gets it wrong, and the house's most valuable know-how walks out of the gate every evening.
How ERPDrive Solves It: Dye recipes are stored per shade and quality. A new batch card carries the recipe, the customer, the grey lot and the target shade, so the floor works from the card. Because the Process House Edition runs as a dedicated deployment with its own database, the recipes stay with your house.
The Result: A repeat order starts from the recipe that was approved last time, whoever is on shift.
Problem 4: The Right Fabric, the Wrong Design
The Problem: In printing, two traders can send near-identical qualities for different designs in the same week. If the link between lot and design lives on paper, the right fabric gets printed with the wrong screens, and the whole lot is a loss.
How ERPDrive Solves It: Screen printing designs are managed alongside customer orders, so the printing team sees exactly which design runs on which lot before the table is set up.
The Result: Design errors are prevented at the planning stage rather than discovered on the finished fabric.
See Your Lots Move From Grey Inward to Invoice
See how ERPDrive's Process House Edition handles grey receipts, batch cards, Delta E shade approval, machine scheduling and rate-card billing, using your own fabrics and stages.
Book a Free DemoProblem 5: Machines Idle While Lots Wait
The Problem: Planning often happens on a whiteboard or in the master's head. Nobody can see at a glance which machine can take which fabric width, so a wide lot queues behind a narrow machine while a suitable jet sits empty. Every idle machine-hour is fixed cost with no revenue against it.
How ERPDrive Solves It: Each machine is defined by the panna it can take, in inches, and its throughput. The production schedule matches waiting orders to machines that can actually run them, and the production board shows each lot at its current stage.
The Result: Idle capacity becomes visible and lots stop queueing behind the wrong machine. See our guides to capacity planning for job shops and machine maintenance.
Problem 6: The Status-Call Treadmill
The Problem: Traders call all day asking where their lot is. Office staff walk the floor or flip registers to answer, and by evening the answer is out of date. The calls take hours that should go into billing and dispatch.
How ERPDrive Solves It: Every customer order gets a public tracking link, with no login needed, showing the lot's current stage. WhatsApp notifications go out as the lot moves through your stages.
The Result: Traders check their phones instead of calling, and your office gets its day back.
Problem 7: Completed Lots Billed Late, Wrong or Not at All
The Problem: Grey inward goes into a register, processing takes days or weeks, and billing happens at month end from registers and memory. Some lots are missed. Rates get disputed because nobody can quickly show the agreed rate for that quality, and volume discounts are worked out by hand. Late invoices mean late collections.
How ERPDrive Solves It: When a batch is marked complete, ERPDrive creates a draft proforma invoice from that customer's rate card. Monthly volume discount schemes on grey inward apply the agreed slab automatically. You review the draft and raise the GST invoice for the processing service.
The Result: Nothing completed goes unbilled, rates are on record, and invoices go out when the work is done. See our guides to GST invoicing and accounts receivable.
Problem 8: ETP Records in a Paper Register
The Problem: Effluent treatment is a licence-to-operate matter for every wet processing unit. When ETP readings live in a paper register, gaps tend to surface exactly when an inspection happens, and rebuilding months of records is stressful and unconvincing.
How ERPDrive Solves It: ETP tracking keeps effluent treatment records in the system alongside production, so they are maintained as the work happens.
The Result: Records are ready when the pollution control board asks, without a scramble.
Challan Register and Tally vs ERPDrive Process House Edition
| Area | Challan Register, Whiteboard and Tally | ERPDrive Process House Edition |
|---|---|---|
| Grey inward | Register entry and a slip on the bale | Multi-fabric receipt per challan, tagged to the customer |
| Recipes | Dye master's memory or notebook | Stored per shade and quality, carried on the batch card |
| Process stages | Fixed in nobody's system | Your own editable stage master and board |
| Shade approval | By eye against a swatch | Delta E against the standard, gated by tolerance |
| Machine planning | Whiteboard or the master's head | Scheduling by panna and throughput |
| Customer status | Phone calls to the office | WhatsApp updates and a public tracking link |
| Billing | Month-end from registers | Draft proforma on completion from the rate card |
| ETP records | Paper register | Tracked in the system |
Process House KPIs Worth Tracking
Review these weekly by customer, quality and machine. Set your targets from your own baseline once the data is reliable, not from cluster rumours.
| KPI | How It Is Calculated | What It Tells You |
|---|---|---|
| First-time shade approval rate | Batches cleared at the first shade check divided by batches checked | How often recipes and processes hit the shade first time |
| Re-dye batches | Batches re-processed after a failed shade check or a customer rejection | Chemicals, steam and machine hours spent twice |
| Lot turnaround time | Days from grey inward to dispatch, per lot | Whether traders will keep sending you work |
| Machine idle hours | Available hours minus hours with a batch running, per machine | Capacity lost to poor matching of lots and machines |
| Completed but unbilled lots | Lots marked complete with no confirmed invoice | Revenue already earned but not yet claimed |
| Completion to invoice days | Days between batch completion and GST invoice | How quickly work turns into collections |
How ERPDrive Runs a Lot From Grey Inward to Invoice
Step 1: Record Grey Inward Against the Customer Challan
Each inward receipt captures every fabric on the trader's challan with its quality, quantity and panna, tagged to that customer, so the lot has an identity from the first minute.
Step 2: Create the Batch Card From the Approved Recipe
The batch card pulls the stored recipe for the shade and quality, links the grey lot it consumes and carries the customer and target shade to the floor.
Step 3: Schedule the Lot on a Machine That Can Run It
Machines are defined by panna and throughput, so the production schedule matches waiting lots to machines that can actually take them, and the lot moves through your own process stages on the board.
Step 4: Approve the Shade Against the Delta E Standard
At the shade-approval stage the measured Delta E is recorded against the shade standard, and the batch clears only within tolerance, so re-dye decisions are made at the machine.
Step 5: Complete, Notify and Bill From the Rate Card
Customers see stage changes on WhatsApp and a public tracking link, and a completed batch creates a draft proforma from the customer's rate card and volume slab, ready to confirm as a GST invoice.
How to Get Started: A Practical Rollout Sequence
- Define your process stages. Set up the stage master in the order your house actually runs, with the names your floor already uses.
- Set up machines. Enter each machine with the panna it can take and its throughput so the schedule only proposes machines that fit.
- Load your shade library and recipes. Start with the shades and qualities you run most often, each with its standard and Delta E tolerance.
- Enter customer rate cards and volume slabs. Record the agreed rates per customer and quality before the first lot is billed from the system.
- Register open lots. Enter the grey lots already on the floor so the board shows the real position from day one.
- Switch on customer tracking. Share tracking links with your most active traders first and let WhatsApp updates replace the status calls.
- Review weekly. Shade approvals, re-dyes, idle machines and unbilled lots, with the dye master, floor in-charge and office in one meeting.
Process houses work on the customer's fabric, so the trader who sent it remains responsible for tracking goods sent for job work under GST, and depends on your receipts and returns being accurate. For the rules on both sides, read our job work GST compliance guide and our guide to subcontracting and job work management. If you also stitch or trade fabric, see our textile and garment ERP guide.
Frequently Asked Questions
What is a process house ERP?
It is software that runs the job-work flow of a dyeing and printing unit: grey fabric inward against the customer's challan, recipes and batch cards, process stages, shade approval, machine scheduling, customer tracking and billing. Unlike accounting software, it follows each customer's lot through the floor, so nothing is mixed up, delayed without notice or left unbilled.
Can I define my own process stages in ERPDrive?
Yes. The process-stage master is editable. The stages your house actually runs, for example grey inspection, scouring, dyeing, shade approval, printing, finishing, folding and dispatch, become the batch card steps, the production board columns and the tracker your customers see. You can add, rename or reorder stages without custom development.
How does shade approval with Delta E work?
Each shade in the shade library has a standard and a Delta E tolerance. At the shade-approval stage the measured Delta E against the standard is recorded, and the batch moves ahead only if it is within tolerance. Out-of-tolerance lots are flagged at the machine, when a correction is cheaper than a rejection at the trader's end.
How does ERPDrive bill job-work processing?
When a dye batch is marked complete, ERPDrive creates a draft proforma invoice from that customer's rate card. Monthly volume discount slabs on grey inward are applied by the system. You review the draft and convert it into a GST invoice, so completed lots are not missed and rates are not argued from memory.
Are our dye recipes and rates kept private?
Yes. The Process House Edition runs as a dedicated deployment with its own instance and its own database, separate from other companies. Your recipes, per-customer rate cards and discount slabs stay in an environment that belongs to your house alone.
Conclusion: Make Every Lot Count
A process house rarely loses money on one bad batch. It loses it on small failures around the chemistry: a lot nobody can identify, a shade that passed by eye and failed at the buyer, a jet waiting for work, a finished lot never invoiced.
ERPDrive's Process House Edition puts every lot, batch and bill on one system, from grey inward to the GST invoice. Book a free demo to see it on your own fabrics, stages and rate structure, or message us on WhatsApp to talk through how your house runs today.