Parent Lot Child Lot

Parent–child lots represent a hierarchical relationship where a single source lot (parent) spawns one or more derived lots (children) due to splitting, repackaging, rework, blending/segregation, sterilization cycles, or other process steps. Each child lot remains traceably linked to its parent(s) for genealogy, mass balance, and status propagation. In regulated MES, parent–child lots underpin backward and forward traceability, enabling precise recall scope with minimal overreach.

While regulations rarely use the phrase “parent/child lot,” they require robust identification and batch/lot documentation. FDA 21 CFR 211.188 mandates batch production and control records, 21 CFR 111.260 requires dietary supplement batch records to list component lots and yields, and 21 CFR 820.65 requires device traceability where necessary. EU GMP Volume 4 expects documentation and electronic controls (Annex 11) consistent with data integrity principles.

• Parent lot: Original lot identifier for received or created material.
• Child lot: Derived lot created by split, processing step, or disposition.
• Merge: A new lot with multiple parents; genealogy must capture many-to-one.
• Mass balance: Quantitative reconciliation across parents and children.
• Status propagation: Holds and recalls cascade across the hierarchy.

Regulators focus on traceable identification, complete batch/lot documentation, and effective recall execution rather than a specific data model. For pharmaceuticals, 21 CFR 211.188 requires batch production and control records that clearly identify components, processing, and yields sufficient to reconstruct manufacturing history. For dietary supplements, 21 CFR 111.260 details batch production record content, including component lot identifiers and actual yields. For medical devices, 21 CFR 820.65 requires traceability for devices where necessary to assure conformance, often extending to component lots for critical-to-quality assemblies.

Electronic realization of parent–child lots must meet 21 CFR Part 11 and EU GMP Annex 11 principles: validated systems (GAMP 5-aligned), secure and contemporaneous audit trails, and trustworthy e-signatures for creation, split/merge, usage, disposition, and status changes. ISA‑95 provides a neutral model for Level 3 (MES) vs. Level 4 (ERP) role partitioning so that lot genealogy remains authoritative at Level 3 while ERP remains authoritative for commercial order and financial views.

A robust parent–child model separates the immutable identity of a lot from its mutable attributes (quantity, status, location, testing). Parentage is maintained via directed edges: split (one-to-many), merge (many-to-one), and transform (one-to-one with changed attributes). Inheritance rules apply to material definition, specification set, retest/expiry logic, and critical attributes (e.g., allergen flag), with the ability to override based on processing steps. Transactions must be granular: dispense, sample, rework, quarantine, destruction, and release events each leave an auditable footprint.

Mass balance and tolerances

Mass balance should reconcile parent outputs with child quantities plus losses and waste. MES should enforce tolerance bands and trigger deviation workflows when reconciliation fails. Children created by sampling and QC usage must be accounted against parent quantities to avoid phantom inventory. For merges, the new lot should store the parent contributions and potency factors to support label claim, assay-adjusted charges, and potency-corrected consumption in downstream steps.

• Identity: Lot ID is immutable and unique; no reuse.
• Inheritance: Material and specs roll down unless a process creates a new material definition (e.g., blend).
• Quantities: Tracked in base UoM with conversions; retain lot potency for actives.
• Status: Each lot has an independent status; holds may propagate per rules.
• Attribution: Child stores parent ID(s), contribution %, and context (split, merge, rework).

ISA‑95 partitions responsibilities: ERP (Level 4) manages item masters and financial inventory; MES (Level 3) manages production genealogy, equipment, and WIP; Control (Levels 0–2) executes phases. Parent–child lots live primarily at Level 3 with references from Level 4 for item, customer order, and cost. When batch processes are involved, ISA‑88 concepts apply: material lots flow through unit procedures and phases; split/merge events correlate with transfer and phase completion events, and genealogy ties to batch records.

Interfaces and master data alignment

Interfaces must guarantee idempotency and referential integrity. Lot creation, split, and merge should be initiated in MES with event-driven updates to ERP and WMS. Master data harmonization ensures the same GTIN/Item, UoM, and shelf-life rules exist across systems, while MES remains the source of truth for genealogy and batch record.

Parent–child constructs appear in many operations: splitting a received API lot into dispensary containers; repacking excipient into smaller drums; reworking an intermediate; blending multiple parent lots into a new lot; subjecting sub-lots to different sterilization cycles; or segregating suspect quantities under quarantine. Each action should be explicitly modeled to preserve traceability, mass balance, and independent status control.

• Dispense split: Parent bulk material split into child containers; inherit COA and specs; container-IDs link to child lots.
• Blend/merge: New lot derived from multiple parents with contribution percentages and assay data for potency-adjusted usage.
• Sterilization sub-lots: Pre-sterile parent split into loads, each child linked to cycle parameters and results.
• Rework: Nonconforming lot transformed into a new child; route via CAPA/deviation and document impact on expiry/retest.
• Sampling/retain: Child lots for QC retains and stability samples to maintain auditable quantity flows.
• Kitting/assembly (devices): Component lots become children of a subassembly lot, enabling forward traceability to finished devices.

Where serialization applies (e.g., device UDI/DI+PI, pharma markets with serials), serial numbers and packaging aggregations must reference the correct lot node in the genealogy. Child lots resulting from split or processing must update the label PI (lot/expiry) and, if applicable, aggregation hierarchies. GS1 standards (GTIN, lot, serial, SSCC, and EPCIS events) provide identifiers and event semantics to publish transformations across the chain.

• Aggregation: Case→pallet SSCCs link to child lots created by the packaging order.
• UDI/PI: Lot/expiry imprint must correspond to the specific child lot and processing date.
• EPCIS events: Transform and aggregation events mirror MES split/merge for downstream partners.
• Relabeling/Repack: Create new child lots when label PI changes; maintain parent link for recall scope.

All parent–child operations are GxP-significant and must be captured as Part 11/Annex 11-compliant records with audit trails: who, what, when, why (reason codes), original and new values, and affected quantities. eBMR/eDHR entries should reference the lot node(s), equipment, and critical process parameters (CPPs) that justify splits (e.g., different cycle parameters). Review by exception relies on precise, atomic transactions and clear system checks (double witness, barcode scanning validation, tolerance bands).

• Electronic signatures: Applied to create/split/merge, hold/release, and destruction transactions.
• Audit trail review: Periodic and event-driven per data integrity guidance; exceptions trigger CAPA/deviation.
• Retrospective edits: Disallowed; corrections performed via controlled reversal/adjustment with reasons.
• Record linkage: Each lot node links to BPR sections, QC results, and equipment logs for complete review.

WMS must reflect the same lot nodes and statuses as MES. Child lots often map to discrete containers/SSCCs, enabling FEFO, allergen/temperature routing, and putaway rules based on lot attributes (expiry, hazard). During a recall, MES provides the authoritative set of affected parents and children; WMS executes the physical segregation and pick-blocks. Idempotent interfaces ensure that reversing a split/merge in MES cascades to WMS without duplicated inventory.

• Lot-controlled locations: Reserve, quarantine, and released locations tied to lot status.
• Containerization: Child lot per SSCC/container, with barcode/GS1-128 labels.
• Pick enforcement: FEFO/expiry, allergen segregation, and temperature zones.
• Recall simulation: Periodic mock recalls validate that genealogy and location data converge in <2 hours for high-risk products.

Splits and processing steps may change the effective expiry or retest date. For example, sterilization or rework may reduce shelf-life or require additional testing gates. Child lots should compute expiry/retest using rule sets that consider processing date, environmental exposure, container closure, and validated stability data. BPR/eBMR should record any changes to shelf-life logic, with QA approval and rationale.

• Expiry adjustments: Child expiry may be shorter than parent due to processing or repackaging.
• Retest logic: New retest interval for reworked lots; LIMS auto-schedules tests on child nodes.
• Co-mingling risk: Blends must not dilute out-of-spec lots; genealogy retains parent OOS flags and lineage.
• Propagation rules: Holds, deviations, and recalls propagate per validated business rules with QA override controls.

V5 models parent–child lots as first-class MES objects with governed split/merge/rework transactions, potency-aware quantities, and mass-balance checks. Event-driven interfaces publish immutable genealogy to ERP/WMS and to labeling/serialization services. eBMR/eDHR entries embed lot nodes, equipment, and CPPs; LIMS test orders are spawned per child expiry/retest rules; QMS workflows (deviation, CAPA, change control) can block specific nodes or entire branches. Holds and recalls propagate deterministically and are visible in WMS for physical segregation.

Frequent pitfalls

• Lot number reuse across years or sites causing ambiguous parentage.
• Creating container IDs without distinct child lots when label PI (lot/expiry) changes.
• Missing mass-balance accounting for sampling, rejects, and evaporation losses.
• Failure to propagate holds across parents/children; partial containment during recalls.
• ERP-first lot creation causing out-of-sync genealogy when MES performs splits.
• Audit trails that capture quantities but not reasons or witnesses for critical actions.

Remediation strategies

1. Enforce MES authority for lot creation and genealogy; make ERP/WMS subscribers.
2. Implement tolerance-based mass balance with exception workflows (deviation/CAPA).
3. Codify propagation rules (upstream, downstream, or both) and test in recall drills.
4. Harden Part 11/Annex 11 controls: unique IDs, e-signatures, and secured audit trails.
5. Use GS1-128/SSCC and EPCIS transform events to align physical and digital flows.
6. Define expiry/retest rule sets per operation; verify in eBMR review by exception.