Merge Batch
Merging batches — topping up a partial lot, blending tailings into a single batch, or folding recovered material back into production — multiplies a lot's genealogy from one parent to several, and every downstream unit of the merged batch now carries the regulatory history of everything that went into it.

On this page · 8 sections
- 1Why batches get merged in the first place
- 2What merging is not allowed to paper over
- 3Many-to-one lot genealogy
- 4Homogeneity and quality considerations when merging
- 5Mass balance across a merge
- 6Labelling and status of the merged lot
- 7Food sector: traceability expectations under Regulation 178/2002
- 8Documentation and authorisation as the common thread
How does Merge Batch apply to your shop floor?
Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.
01Why batches get merged in the first place
Batch merging is not a single operation with one name — it covers several distinct shop-floor events that all end with two or more source lots becoming one traceable unit. The most routine is topping up: a partially consumed batch of raw material is combined with a newly received or newly manufactured batch of the same material to make up a full quantity for a run, rather than opening a second container and tracking two numbers through the process. A related case is blending small or partial lots on purpose — combining tailings, the relatively small quantities of isolated material left over at the end of a production run, so that material which is individually too small to use efficiently is pooled into a batch of usable size. A third case is incorporating recovered or reworked material: all or part of an earlier batch that still conforms to the required quality is folded into a current batch at a defined stage of manufacture, rather than being discarded.
ICH Q7 gives the clearest working definition for the pharmaceutical ingredient context: blending is the process of combining materials within the same specification to produce a homogeneous intermediate or API. The guideline is careful to separate this from in-process mixing of fractions from a single batch — for example collecting several centrifuge loads from one crystallisation run — which it treats as part of the normal production process rather than as blending at all, because no second batch identity is being absorbed into the mix 1.
What all three scenarios share operationally is the same consequence: a merged batch's identity is no longer traceable to one parent lot by a simple one-to-one link. The system, and the people running it, need to know and record every batch that went into the mix, in what proportion, and on what date, because that genealogy is what the quality record and any later investigation will rely on.
02What merging is not allowed to paper over
ICH Q7 states directly that out-of-specification batches should not be blended with other batches for the purpose of meeting specifications, and that each batch incorporated into a blend should have been manufactured using an established process and individually tested and found to meet appropriate specifications before blending 1. In other words, blending is a way of combining conforming material into a usable batch size — it is not a route for diluting a failing result until the average passes. The guideline's own list of acceptable blending operations is narrow: blending small batches to increase batch size, and blending tailings from batches of the same intermediate or API into a single batch.
EU GMP Chapter 5 draws a parallel but separately worded line for recovery and reprocessing of medicinal products. The recovery of all or part of earlier batches which conform to the required quality, by incorporation into a batch of the same product at a defined stage of manufacture, should be authorised beforehand, carried out in accordance with a defined procedure after evaluation of the risks involved (including any possible effect on shelf life), and recorded 2. Reprocessing of rejected products, by contrast, is described as something that should be exceptional, permitted only if the quality of the final product is not affected, specifications are met, and it is done under a defined and authorised procedure after a risk evaluation — again with a record kept.
03Many-to-one lot genealogy
A normal production lot has a genealogy tree that fans out from a small number of consumed inputs to one output batch — one-to-one or few-to-one. A merged batch changes that shape only at the point of the merge itself: two or more parent batch numbers converge into a single child batch number, and from that point forward every unit drawn from the merged batch shares the same combined history. ICH Q7 makes the record-keeping expectation explicit: the batch record of the blending process should allow traceability back to the individual batches that make up the blend, so the identity of each contributing batch and, implicitly, the proportions blended are not lost once the physical material is mixed 1.
This matters most when something goes wrong downstream. If a complaint, an out-of-specification result, or a recall investigation points back to the merged batch, the genealogy record has to answer which of the contributing parent batches is implicated, and whether the problem could be isolated to one of them or whether it is now distributed across the whole merged lot. A genealogy record that only shows the merged batch's own number, without the parent batches and their proportions, cannot support that kind of investigation — the batch effectively becomes a traceability dead end at the point of the merge.
The practical content of a merge record, built from what the two sources opened for this review require or recommend, typically includes: the identity and quantity of each contributing batch, the date and location of the merge, the authorisation for the merge (EU GMP's recovery provision requires prior authorisation), any risk evaluation performed, and the resulting identity — whether the merged material keeps one of the parent batch numbers, takes a new number, or is assigned a blend-specific identifier that itself carries forward to the finished product record.
04Homogeneity and quality considerations when merging
Mixing two batches physically does not automatically make the result uniform, and both frameworks treat homogeneity as something to be demonstrated rather than assumed. ICH Q7 states that blending processes should be adequately controlled and documented, and the blended batch should be tested for conformance to established specifications where appropriate 1. Where physical attributes of the API are critical — the guideline gives the example of APIs intended for use in solid oral dosage forms or suspensions — blending operations should be validated to show homogeneity of the combined batch, with that validation including testing of critical attributes such as particle size distribution, bulk density, and tap density that could be affected by the blending process.
Stability is treated as a separate question from homogeneity. ICH Q7 requires that if blending could adversely affect stability, stability testing of the final blended batch should be performed, and sets a specific rule for the resulting shelf-life or retest date: the expiry or retest date of the blended batch should be based on the manufacturing date of the oldest tailings or batch in the blend — not the date of the merge itself, and not the manufacturing date of the newest contributor. This single rule has a direct operational consequence: a system that lets a merge default to today's manufacturing date, or to the newer parent's date, would be setting a retest or expiry date later than ICH Q7's stated expectation supports.
EU GMP Chapter 5's parallel provision for recovery puts the equivalent check in the hands of Quality Control rather than in a fixed rule: the need for additional testing of any finished product which has been reprocessed, or into which a recovered product has been incorporated, should be considered by the Quality Control Department 2. Neither source treats a merge as quality-neutral; both expect someone to actively decide what additional testing or evaluation the merge calls for, rather than letting the merged batch inherit its parents' release status by default.
05Mass balance across a merge
Neither ICH Q7 nor EU GMP Chapter 5, as opened for this review, sets out a standalone numeric mass-balance tolerance specific to merging batches. What they do establish is the documentation discipline that makes a mass balance possible to perform at all: EU GMP Chapter 5 requires that material and batch identity be tracked through processing, with containers and equipment labelled or identified with the product or material and its batch number at all times during processing, and that a batch number be given at receipt for incoming goods 2. ICH Q7's requirement that the blending batch record trace back to the individual contributing batches is, in effect, the input side of a mass balance: without knowing how much of each parent batch went into the blend, a reconciliation of what went in against what came out cannot be performed.
In practice, a mass balance across a merge checks that the combined quantity of the contributing batches, adjusted for any documented losses (sampling, residues, in-process waste), accounts for the quantity of the resulting merged batch within whatever tolerance the site's own procedures define for that material and process. Where the two source documents are specific is on what triggers a closer look: EU GMP's requirement that recovery decisions weigh any possible effect on shelf life, and ICH Q7's requirement that physical-attribute-critical blends be validated for homogeneity, both imply that a mass balance alone — quantity in equals quantity out — is not sufficient evidence that a merge was executed correctly. The quantity reconciliation and the quality/homogeneity evidence are complementary checks, not substitutes for each other.
06Labelling and status of the merged lot
EU GMP Chapter 5 sets a general labelling expectation that applies as much to a merged batch as to any other in-process material: at all times during processing, all materials, bulk containers, major items of equipment and, where appropriate, rooms used should be labelled or otherwise identified with an indication of the product or material being processed, its strength where applicable, and batch number, mentioning the stage of production where applicable 2. For a merged lot, that single batch number on the label now stands in for everything the genealogy record says went into it — the label itself cannot carry the full parentage, which is why Chapter 5's identification requirement has to be read together with ICH Q7's traceability requirement for the batch record rather than treated as sufficient on its own.
Status is a related but separate question from identity. Rejected materials and products should be clearly marked as such and stored separately in restricted areas under EU GMP Chapter 5, and any reprocessing or recovery action taken on them should be approved and recorded by authorised personnel before it happens. A merged batch therefore should not acquire a released or accepted status automatically from the act of merging; the authorisation, any additional testing identified by Quality Control, and the recording of the action are all described as preconditions or accompaniments to the merge, not formalities that follow it.
This has a direct implication for how a merged batch should sit in a quality or inventory system between the point of the physical merge and the point its status is confirmed: it should be distinguishable from both a freshly released batch and from its individual, unmerged parent batches, so that nobody downstream draws on it under the assumption that it carries the release status of one parent alone.
07Food sector: traceability expectations under Regulation 178/2002
Outside pharmaceuticals, food business operators merging batches — blending partial lots of an ingredient, topping up a mixing vessel, or combining recovered material — sit under a different but related traceability regime: Regulation (EC) No 178/2002, the General Food Law. Article 18 requires that the traceability of food, feed, food-producing animals, and any other substance intended to be, or expected to be, incorporated into a food or feed be established at all stages of production, processing, and distribution 3. It requires operators to be able to identify any person from whom they were supplied a food, feed, or incorporated substance (one-step-back), to identify the other businesses their products have been supplied to (one-step-forward), and to have systems and procedures in place that make that information available to the competent authorities on demand.
Article 18 does not specify how an operator must structure internal batch genealogy for a merge — it sets the traceability outcome (identify suppliers, identify customers, make that information available on demand) rather than prescribing a merge-specific record format. For a merged batch, meeting that outcome in practice means the operator's own records need to resolve the merged batch back to each of its contributing supplier batches, since the merged batch is itself now the thing that was "supplied" onward to the next stage, and a one-step-back request from an authority would otherwise have no answer for material that lost its individual batch identity at the point of merge.
Article 19 adds the operational reason this matters beyond a paperwork exercise: if a food business operator considers or has reason to believe that a food it has produced, processed, or distributed does not comply with food safety requirements, it must immediately initiate procedures to withdraw that food from the market where it has left the operator's immediate control, inform the competent authorities, and, where the product may have reached the consumer, inform consumers and recall if necessary 3. A merged batch that cannot be traced back to its contributing lots makes it impossible to scope a withdrawal correctly — the operator either over-withdraws material that was never actually affected, or under-withdraws because the affected parent batch's presence in the merge was not recorded.
Frequently asked questions
Q.Can an out-of-specification batch be merged with a good batch to bring it into specification?+
No. ICH Q7 states directly that out-of-specification batches should not be blended with other batches for the purpose of meeting specifications, and that each batch incorporated into a blend should already have been individually tested and found to meet its specification before blending.
Q.What expiry or retest date should a merged (blended) API batch carry?+
ICH Q7 states that the expiry or retest date of the blended batch should be based on the manufacturing date of the oldest tailings or batch in the blend — not the date of the merge and not the newest contributing batch's date.
Q.Does merging batches need advance authorisation under EU GMP?+
For recovery of conforming material from an earlier batch into a current batch, EU GMP Chapter 5 requires the action to be authorised beforehand, carried out under a defined procedure after a documented risk evaluation (including effect on shelf life), and recorded. Reprocessing of rejected material is described as something that should be exceptional and subject to similar prior authorisation.
Q.What does Regulation 178/2002 require for a merged food batch's traceability?+
Article 18 requires traceability at all stages of production, processing and distribution, and requires operators to identify both their suppliers (one-step-back) and the businesses they supplied (one-step-forward), making that information available to the competent authorities on demand. It does not prescribe the internal batch-genealogy method, so a merged batch's records need to resolve back to each contributing supplier batch for the operator to actually meet that obligation.
Q.Is combining fractions from one production run the same as blending under ICH Q7?+
No. ICH Q7 treats in-process mixing of fractions from a single batch — for example collecting several centrifuge loads from one crystallisation batch — as part of the normal production process, not as blending. The blending-specific controls (traceability to individual contributing batches, validation of homogeneity for critical physical attributes, the oldest-batch expiry rule) apply once material from more than one batch is combined.
Primary sources
Further reading
- Backward Genealogy TraceTracing a finished lot back through every contributing batch, including merge points.
- Bin-Level Lot GenealogyTracking lot identity at the bin/container level where merges often happen physically.
- Blend Uniformity (BUE)The homogeneity testing concept that underpins the validation ICH Q7 expects for critical blends.
- Drying Mass BalanceA worked example of mass-balance reconciliation applied to a batch process.
- Chain of CustodyThe documentation thread a merged batch has to preserve back to each parent lot.
Want to see how Merge Batch could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
