The Same Batch Number Twice
A batch is identified by your organisation, the item and the batch number — nothing else. Receive that combination twice and the second receipt joins the first, filling in what was blank and rewriting exactly three fields that were not.
Two deliveries, four months apart, both labelled batch 2413. To the system that is one batch, and the second delivery has an opinion about when it expires.
Batch tracking is one of those features that looks like bookkeeping until the day somebody has to answer a recall. Then it becomes the only thing that matters: which units, from which delivery, went to which customers. The mechanism underneath is simpler than most people assume, and the simplicity is where the sharp edge lives.
What identifies a batch
Three things together: your organisation, the item, and the batch number as written. That is the whole key. A batch number is not unique across your catalogue — the same number on two different items is two separate batches, correctly, because a supplier's numbering is theirs and two suppliers may both use 001. What it is unique within is the item.
So when goods arrive carrying a batch number, the system looks for that combination. If it finds nothing, a batch record is created with everything the receipt supplied. If it finds one, the receipt is folded into the batch that already exists.
A blank batch number creates nothing
Receiving without a batch number is not an error and does not produce an empty batch. The stock arrives, the traceability record simply has no batch to hang on it. That is worth knowing because it is the honest description of most receipts in most organisations — batch tracking is a discipline you apply where it matters, not a field the system fills in for you.
What happens on the second receipt
This is the part to know. When a second receipt lands on an existing batch, its fields are merged, and there are two different rules depending on the field.
| Field | Rule on a second receipt |
|---|---|
| Expiry date | Overwritten. The newer receipt's date replaces whatever was there. |
| Quality status | Overwritten. A later assessment supersedes an earlier one. |
| Recall status | Overwritten. A batch marked for recall can be cleared, and a clean batch can be marked. |
| Supplier, purchase order, lot number | Filled in only if currently empty. First write wins. |
| Received and manufactured dates | Filled in only if currently empty. |
| Unit cost, landed cost allocation, total unit cost | Filled in only if currently empty. |
The three overwriting fields are the ones whose whole purpose is to change. A quality status that could never be revised would be useless — the point of it is that somebody inspects, and inspects again. A recall status has to be settable and clearable or a recall can never be closed. And an expiry date, in the ordinary case, is being corrected rather than contradicted: the first receipt did not carry one, the second does, and the batch ends up right.
Three fields change their mind on purpose. Everything else remembers the first answer.
The case where this bites
Now the case it is worth being deliberate about. A supplier reuses batch numbering on a cycle — many do, particularly where the number encodes a production line and a week rather than a unique run. Two genuinely different productions arrive four months apart carrying the same number on the same item.
The system treats them as one batch, because by its definition they are. The second receipt's expiry date replaces the first's. Stock from the earlier production is now sitting on the shelf under a batch record that says it expires four months later than it does, and every rotation rule that reads that date will agree.
Your supplier's batch numbers are genuinely unique
Nothing to do
This is most pharmaceutical, most food manufacturing and most regulated supply. The merge behaviour is doing exactly what you want: a second delivery of the same batch is the same batch.
Your supplier recycles batch numbers
Qualify the number on receipt
Prefix it with the receipt date or the purchase order — 2413-2026-03 rather than 2413. It is a receiving convention rather than a system change, and it makes two productions two batches, which is what they are.
You are not sure
Check the expiry dates on your oldest batches
A batch whose recorded expiry is later than its neighbours from the same period is the tell. It takes one report and it is worth running before you rely on rotation.
You do not track batches at all yet
Start where a recall would hurt
Batch tracking is a discipline with a cost at the receiving door. Apply it to the items where you would need to answer "which units" under pressure, and leave the rest.
The serial number has a sharper version of the same rule
Serial numbers work the same way — identified by organisation, item and serial — with one difference worth flagging. Two of a serial's fields carry defaults rather than being left alone: an update that says nothing about the unit's status sets it back to available, and one that says nothing about its last movement stamps it as now.
In the ordinary flow that is correct: a serial being received is available, and it did just move. Where it matters is any path that touches a serial for another reason — correcting a warranty date, attaching a supplier, fixing a typo. If that path does not carry the current status forward, a unit that was marked damaged, reserved or issued comes back as available, and nothing announces it.
What is genuinely immutable here
The batch and serial records are current state and they move. What does not move is the trail beside them. Every receipt, issue, transfer and allocation writes a trace event carrying a direction, an event type, a quantity, the document and line it came from, who did it and when. Those are inserted and never updated.
So even where a batch's expiry date has been rewritten by a later receipt, the history of what arrived when, in what quantity, against which purchase order, is intact. Reconstructing the truth about a reused batch number is a report rather than an excavation — which is the difference between an inconvenience and an incident.
Our take
Identifying a batch by the number on the box is the only definition that survives contact with a warehouse, and it is right. It does mean the system inherits your suppliers' numbering discipline, including where they have none — and the three fields that overwrite are exactly the three you would want to be able to correct, which is why they overwrite. The honest summary is that batch tracking here records what you were told, faithfully, and does not attempt to detect that you were told two different things under one label. Where your suppliers recycle numbers, qualify them at the receiving door; it costs a convention and it removes the entire problem. Where they do not, this behaves the way you would want without you thinking about it, which is the most anyone should ask of a traceability layer.
What AWRA OpsHub does today
- Batches identified by organisation, item and batch number, so a supplier's numbering can be used as written and the same number on two items stays two batches.
- A batch record carrying lot number, expiry date, supplier, purchase order, received and manufactured dates, quality status and notes, recall status, unit cost, landed cost allocation and total unit cost.
- A merge on a second receipt that fills in every field currently empty, so a later delivery completes a batch record rather than replacing it.
- Expiry date, quality status and recall status treated as revisable, so an inspection or a recall decision made later supersedes an earlier one.
- Serial numbers identified the same way, carrying their own warehouse, location, status, supplier, purchase order, received date and warranty expiry.
- An append-only trace event on every movement, recording direction, event type, quantity, the source document and line, a reference, the user and the moment — never updated in place.
- Batch allocations recorded per movement, so an issue against several batches is traceable to each of them.
- A daily batch expiry reminder, so a date recorded on a batch is a date somebody hears about.
More we can add to your workspace
- A warning when a batch number arrives with a different expiry date than the one on record, raised at the receiving door where the person can still check the box.
- Batch numbers qualified automatically by receipt or purchase order, for suppliers whose numbering repeats on a cycle.
- A revision history on the three overwriting fields, showing what an expiry date, quality status or recall status was before it changed and which receipt changed it.
- A status carried forward automatically when a serial record is edited for an unrelated reason, so a damaged or reserved unit stays as it was found.
- A report of batches whose expiry dates were rewritten, which is the fastest way to audit for recycled numbering after the fact.
- A warranty reminder on serial numbers, matching the batch expiry reminder that already runs.
Where we point you to a specialist
- We will not invent a batch identity your supplier did not give you. Deriving a synthetic batch number from a receipt would make your records disagree with the label on the box and with the paperwork your supplier holds, which is the one property batch tracking exists to preserve.
- Where a regulator prescribes how batches must be identified, retained and reported for your sector, that prescription governs and your compliance adviser owns it. We will hold the fields and produce the reports; the standard is theirs to interpret.
- A recall decision is a judgement with legal weight and stays with the people qualified to make it. We will mark a batch, trace every movement of it and produce the list of where it went. Deciding that a batch should be recalled is not something we will infer from a quality status.
The mismatch warning at the receiving door is the smallest item here and removes the whole failure this article describes — one comparison at the moment the goods are being booked in.
Catching a reused number at the door
Everything needed is already on the batch record. The work is in noticing a disagreement at the one moment somebody can still walk over and look at the carton.
An expiry mismatch warning
Receiving a known batch number with a different expiry date raises a prompt before the receipt is confirmed, naming both dates.
A revision history
What the expiry, quality and recall fields held before each change, and which receipt or assessment changed them.
Qualified batch numbering
An optional receiving convention that appends the purchase order or the receipt date, for suppliers whose numbering repeats.
We publish scope, not dates.
Scope batch traceabilityFive questions to ask about batch tracking
What makes two receipts the same batch?
A good answer sounds like
A named key.
What ours actually is
The organisation, the item and the batch number as written. Nothing else.
What happens when a batch is received twice?
A good answer sounds like
A stated merge rule.
What ours actually is
Empty fields fill in; expiry date, quality status and recall status are replaced; everything else keeps its first value.
Can an expiry date be corrected?
A good answer sounds like
Yes.
What ours actually is
Yes — it is one of the three revisable fields, which is what makes a later, better-informed receipt able to fix an earlier one.
Is the movement history editable?
A good answer sounds like
No.
What ours actually is
No. Trace events are inserted and never updated, so the record of what arrived when survives any change to the batch record itself.
What if my supplier reuses batch numbers?
A good answer sounds like
An honest answer and a workaround.
What ours actually is
Two productions become one batch. Qualify the number at receipt — the convention costs nothing and it makes them two batches, which is what they are.
Ask your supplier one question
Whether their batch numbers repeat is a five-minute email and it decides whether any of this applies to you. If the answer is yes, the receiving convention that fixes it takes an afternoon to agree.
Talk through traceabilityFrequently asked questions
Why is a batch identified by its number rather than by the receipt?
Because the number is what is printed on the carton, on the supplier's paperwork and on any recall notice you will ever receive. A batch keyed on the receipt would be internally tidy and externally useless — when a supplier tells you batch 2413 is affected, you need to be able to look up 2413 and find every unit of it, including the units that arrived on three different days.
What actually happens to my costs when a batch is received twice?
They are kept from the first receipt that supplied them. Unit cost, landed cost allocation and total unit cost all fill in only when currently empty, so a later delivery at a different price does not silently restate the cost of stock already on the shelf. Whether that is what you want depends on your costing policy, and it is worth knowing which way it falls.
Can I see that an expiry date changed?
Not on the batch record itself, which holds current state. What survives is the trace history — every receipt against that batch, with its quantity, document and date — so the sequence can be reconstructed. A revision history on the three overwriting fields is the item that would make this visible rather than reconstructable.
Does the same rule apply to serial numbers?
Nearly. Serials are identified the same way and supplied fields fill in the same way, with one difference: status and last movement carry defaults rather than being left alone, so an update that omits a status writes "available". In receiving that is correct; on any other path that touches a serial, it is worth passing the current status through deliberately.
What is the fastest way to find out if this has happened to us?
Look for batches on the same item, from the same period, whose recorded expiry dates are further apart than the productions could be. A supplier delivering monthly with a twelve-month shelf life produces a predictable ladder of dates; a batch that sits off that ladder has usually been rewritten by a later receipt carrying the same number.
Do I have to use batch tracking on everything?
No, and you should not. A blank batch number creates no batch and is not an error — the stock arrives normally. Batch tracking earns its cost at the receiving door on items where you would one day need to answer "which units, and where did they go". Applying it everywhere turns a useful discipline into a data-entry tax.
