Most conversations about traceability start in the wrong place. They start with numbering: what the batch code should look like, how many digits, whether it encodes the date. That is the part nobody struggles with. The struggle is what happens to that identity over the following six weeks, while the material is put away, moved, issued, consumed, turned into something else and sent to a customer.
What "batch" means on this page
Worth settling first, because the word gets used two ways in manufacturing and they are not the same thing.
Sometimes "batch" means a production run: the units that went through together, as in what that batch cost to make. That usage belongs to costing and is treated in work-order costing and variance. On this page, a batch or lot means something narrower: an identity carried by a quantity of material or output, which stays attached to it as inventory.
Different manufacturing contexts use terms such as batch, lot or heat. This page uses "batch or lot" throughout, without implying a technical distinction between them. None of the terminology changes the underlying question, which is whether the identity survives handling.
Every inventory movement has to carry the identity
This is the whole subject in one sentence: in exactllyERP, every inventory movement tracks the applicable batch or lot identity.
The important word is every. Traceability is not a feature that can be present in most places and absent in a few, because the gap is where the questions land. A record that holds identity at goods receipt, keeps it through storage, keeps it when stock moves between locations, keeps it when material is issued to production, and then drops it at dispatch has not given you nine tenths of a trail. It has given you a trail that stops exactly where somebody will need it.
In practice this covers the ordinary movements a manufacturing business runs on: goods received against a purchase, material moved between warehouses or locations, material issued to production, output received back, and goods dispatched. Each of those is a movement, and each carries the identity of what moved.
Following material into production
Production is where most traceability records historically break, because material stops being a stock line and becomes work.
Issue to production is an inventory movement like any other, so the identity of what was issued travels with it. That is the mechanism, and it is worth being clear that it is a recording question rather than a shop-floor one. What the job is doing, how far through it is and which stage it has reached are execution questions, covered in work-order execution and shop-floor tracking. What concerns us here is narrower: the material that went in is still identifiable after it went in.
From a finished batch back to what went into it
Continuity through production makes the more valuable question answerable.
A finished-product batch in exactllyERP can be traced back to the exact raw-material batches or lots consumed in producing it. Not the supplier in general, not the month's purchases, but the specific input lots.
The difference between that and a system which merely stores batch numbers is the difference between an investigation and an argument. When a problem surfaces in a finished batch, the first question is always what went into it. If the answer has to be assembled from issue notes and somebody's recollection of which drums were open that week, the investigation takes days and ends in a probability rather than a fact.
Movement does not stop at the factory
Two movements outside the production area are worth naming, because both are places where records tend to thin out.
The first is ordinary warehouse movement. Stock gets transferred between locations for reasons that have nothing to do with traceability, and the identity travels with it. This matters alongside the practice of keeping different resulting quantities in different places, described in scrap, by-product and yield tracking: putting a quantity somewhere else must not cost you the knowledge of what it is.
The second is material that leaves the premises altogether. Batch and lot identity is retained when material moves to a job worker or subcontractor and when it returns. That is a genuinely useful thing to be able to say, because an external processing step is the classic point at which a traceability record becomes a piece of paper in a file. The job-work process itself, including reconciling what went out against what came back, is covered in job work and subcontracting.
From a finished batch to the customer who received it
The outward half of the picture is the half most often missing, and the half most often needed at short notice.
Dispatch retains the batch or lot identity against the customer and the document. The practical consequence is direct: for a given batch or lot, the manufacturer can identify which customers received it.
Systems that keep careful records up to the warehouse door and then dispatch by item code alone are common. They look complete during an implementation and fail at the only moment the question is ever asked, which is when somebody outside the business raises a problem and wants to know the extent of it.
Seeing the movements in one place
Recording identity on every movement is necessary but not sufficient. The movements also have to be readable together.
For a selected batch or lot, exactllyERP provides a consolidated movement history in one place, without anybody compiling the trail by hand. That is a meaningful distinction. Traceability that exists only as scattered entries across separate records is technically present and practically unusable, because assembling it takes a person a day, and a day is usually longer than the situation allows.
What this is for, and what it is not
The reason to care about any of this becomes obvious the moment something goes wrong with one batch.
Between the three capabilities above, a manufacturer investigating an affected batch can establish the raw-material lots behind it, the sequence of movements it went through, and the customers who received it. That is the substance of an investigation, and having it in the system rather than in a filing cabinet is the difference between answering within the hour and answering within the week.
It is worth being precise about the boundary, though. That information is what a manufacturer needs when investigating an affected batch; the traceability capability should not be confused with a separate recall-management workflow. Formal recall handling, with its notifications, approvals and regulatory steps, is a different requirement. If your business needs one, ask any vendor to demonstrate it in its own right rather than assuming it arrives with batch tracking.
Following one lot through
An illustration, deliberately ordinary, to show the shape rather than any particular system's screens.
A raw-material lot is received and put away. Part of it is later transferred to a second warehouse, and part is issued to production. A finished-product batch comes back from that production. Some of the finished batch is moved again for storage reasons, and some is dispatched to a customer.
Six movements, three of them routine enough that nobody would think to document them separately. The batch or lot identity is associated with each one. So the finished batch can be traced back to the exact input lots consumed, the movements can be reviewed in sequence rather than reconstructed, and the customer who received part of that finished batch can be identified. If the material had gone out to a job worker and come back partway through, its identity would have survived that too.
What to make an ERP vendor demonstrate
Traceability demonstrates well, provided you insist on movements rather than a prepared record. The wider evaluation method is set out in the ERP selection and evaluation guide; this sequence is the one specific to identity.
- Receive a batch or lot, then move it between two warehouses, and check the identity is on both movements.
- Issue it to production and show it is still identifiable after the issue.
- Show which raw-material lots went into a specific finished-product batch.
- Send material out to a job worker and bring it back, and show the identity survived the round trip.
- Dispatch part of the finished batch and show which customer received it.
- Then ask for that batch's movement history in one place, without anyone assembling it.
Then ask what the system does not do, because that is where assumptions hide. Does it manage a recall process itself, or only supply the facts? Are expiry or manufacturing dates held against the batch? Is any capture technology involved, or is identity recorded as part of the transaction? What happens to identity on a return? Is serial-number tracking a separate thing entirely? These are good questions precisely because the answers differ between systems.
How exactllyERP handles batch and lot traceability
exactllyERP supports batch and lot traceability as part of inventory and warehouse capability rather than as an industry-specific addition, and every inventory movement tracks the applicable batch or lot identity.
The identity stays associated with goods receipt, material movement between warehouses and locations, issue to production, output received back from production, and dispatch. A finished-product batch can be traced back to the exact raw-material batches or lots consumed in producing it. Identity is retained when material moves to a job worker or subcontractor and when it returns.
Dispatch retains the identity against the customer and the document, so the customers who received a particular batch or lot can be identified. For a selected batch or lot, a consolidated movement history is available in one place. The functional scope this sits inside, across procurement, inventory, production and finance, is described on the features page.
This page describes capability, not configuration. Which materials warrant a batch or lot identity at all, how the identity is structured, and who is responsible for recording it at each point are implementation choices that depend on the operation. They are worth settling before go-live, because identity that was never captured at a movement cannot be added to that movement afterwards.
Common questions
What does batch or lot traceability mean in a manufacturing ERP?
It means a quantity of material carries an identity that survives being moved. Giving material a batch or lot number is the easy part; almost any system can do that. Traceability is whether that identity is still attached after the material has been put away, transferred, issued to production, turned into something else and sent out. If the identity is recorded once and then dropped at the first movement, what remains is a numbering scheme rather than a traceable record.
Does exactllyERP retain batch or lot identity through every inventory movement?
Yes. In exactllyERP, every inventory movement tracks the applicable batch or lot identity. That covers the ordinary run of them: goods received, material moved between warehouses or locations, material issued to production, output received back from production, and dispatch. The word that matters is every. A trail with one uncontrolled step in it is not a trail, because the question you eventually want to ask will be the one that crosses exactly that step.
Can a finished-product batch be traced back to the raw-material lots used to make it?
Yes. A finished-product batch in exactllyERP can be traced back to the exact raw-material batches or lots consumed in producing it. This is the part that separates real traceability from stock records that merely mention batch numbers. Knowing that a batch exists tells you nothing about what went into it; being able to name the specific input lots is what lets a manufacturer investigate a problem rather than speculate about it.
Can exactllyERP identify which customers received a particular batch or lot?
Yes. Dispatch retains the batch or lot identity against the customer and the document, so the manufacturer can identify which customers received a particular batch or lot. That is the outward half of the picture, and it is the half most often missing. Plenty of systems keep good records up to the warehouse door and then lose the thread at dispatch, which is precisely where the question becomes urgent.
Is batch or lot identity retained through job work or subcontracting?
Yes. Batch and lot identity is retained when material moves to a job worker or subcontractor and when it comes back. This matters more than it sounds. Material leaving the premises is the point at which most traceability records quietly stop, and any gap there has to be reconstructed later from delivery paperwork. How the job-work process itself is handled, including reconciling what was sent against what returned, is a separate subject.
Does batch traceability mean the ERP also has a recall-management workflow?
Not necessarily. Batch traceability and recall management are separate capabilities. Traceability provides the information an investigation needs: the input lots behind a finished batch, the sequence of movements it went through, and which customers received it. A recall-management workflow is a different thing again, with its own notifications, approvals and regulatory steps. Whether an ERP also provides a dedicated one should be demonstrated separately rather than assumed to come with batch tracking.
Where to start
Pick the batch your plant has already had to investigate once, and write down how long it took to answer three questions: what went into it, where it went, and who received it. That number is the honest measure of your current traceability, and it is usually larger than anyone expects.
If exactllyERP is on your shortlist, bring that batch to the demonstration and ask for those three answers in front of you.