What a Textile Mill ERP Must Track: From Greige to Dispatch

Most ERP software is built around a simple idea: an item comes in, it sits in a warehouse, it goes out. A textile processing mill does not work like that. The same fabric changes length, changes form and passes through many hands before it leaves. Software that ignores this ends up being worked around with paper.

I plan production in a textile processing mill and I built the ERP it runs on. This is what I learned such a system must track.

1. Greige receipt: the starting point of every number

Everything begins when grey (greige) fabric arrives at the gate. The system must record who sent it, the quality, the width, the quantity received, the quantity rejected and what was returned.

Every later number depends on this one. If receipt is wrong, every report after it is wrong.

2. The lot is the thread through everything

A mill talks in lots. So the system must tie every entry to a lot: issue, printing, dyeing, finishing, packing and dispatch.

When each entry carries its lot, questions answer themselves:

• Where is this lot now?
• How much of it is finished?
• How much was rejected, and at which stage?
• How much has shipped?

A report such as "grey issued but no production recorded" then becomes one query, not an afternoon of phone calls.

3. Stages are real, and they are different

Processing is a route, not a single step. In the mill I work in, fabric can pass through pre-process stages such as singeing, kier, mercerizing and drying, then printing or dyeing, then ageing, washing, finishing and calendering, then packing.

Two lessons from modelling this:

• Printing and dyeing need their own records. One order often has a printed part and a dyed part. Put them in one table and the quantities are added together wrongly.
• Quantities do not stay the same. Fabric is lost, rejected and reprocessed. In some pre-process steps it even gains length. A system that assumes "what goes in must come out" is wrong on its first day.

4. The floor does not follow the plan exactly

A plan says where fabric should go next. The floor decides where it really goes. So the system should record what each operator actually processed and where they sent it. A lot's route is then a true record of what happened, and the plan can be compared against it.

Each stage should also refuse to receive more than the stage before it delivered. That single check catches most typing mistakes at the moment they are made.

5. Machine and operator on every entry

Production is entered against a machine and an operator. This gives you output per machine, output per shift and a name beside every figure. It is also what makes later questions about quality possible to answer.

6. Packing, gate pass and dispatch

The last stage is where money is made or lost. The system should track packing, gate passes with each line item, shortages between what was ordered and what was shipped, and when a dispatch is closed.

7. The daily floor status report

Management needs one page every day: a lot-by-lot position of work in progress, grouped by stage, with a total for each stage and a grand total. If the system holds live data, this report is printed in seconds instead of being compiled by hand.

8. Tablets on the production floor

The people who enter production are standing at a machine, not sitting at a desk. The busiest entry screens need layouts made for a tablet, with large buttons and few fields.

What this means when you choose software

Before you buy or build a textile ERP, ask to see these things working:

1. One lot followed from receipt to dispatch on a single screen
2. Rejection and reprocessing entered without breaking the totals
3. Several departments entering data at the same moment
4. The daily floor status report produced from live data

You can see how I built these in the textile mill ERP case study, including a short walkthrough video.

If you run a dyeing, printing or processing unit and your records are still on paper, Excel or Access, tell me how your floor works and I will show you what a system built for it would look like.