Own serial allocation, aggregation and each client file from the lines
- Each serial counted from its record
- Leaks traced to the physical action
- Files sent only after two signatures
Serialization and aggregation reconciliation that accounts for each serial in a packaging run before the client's file leaves the plant.
See one packaging run's serials reconciled ↓On a serialized line each saleable unit gets a serial when its label prints, and each one must end the run in a single place: in a case that ships, or decommissioned as a reject, a sample or a destroyed unit. The serialization system reports what was scanned. The reject log, the batch record's packaging pages and the warehouse hold what physically happened.
Checking the line report against a glance at the batch record misses the actions the data never saw. A bottle is pulled by hand after its case was scanned and replaced from the rework tray; start-up print checks are destroyed in line clearance without a decommission scan. The file goes to the client, and the mismatch surfaces downstream at a trading partner as product without matching data.
Built forSerialization leadsPackaging QA specialistsPackaging line operatorsPackaging line managers
A run is checked against the line system's own count, while the physical record sits in three other places.
Where a run's serial books live
Built-in controls
The client receives a file that matches its pallets, with the reconciliation behind each serial.
A bottle line's run closes with three serials unaccounted for; the agents hold the client's file, trace each one to the line, and two people sign the corrections before it goes.
demoThe line, the run, its people and its serials are sample data.
The lead runs each reconciliation and releases the file, packaging QA approves corrections first, and the line answers for what happened on the floor.
Own serial allocation, aggregation and each client file from the lines
Approve each correction to serial data against the packaging record
Run the line, answer the agents' line questions and re-scan cases
Own line practice and agree the checks learned from each run
Four findings the line's own count passed, each traced to its source record.
The case data listed the pulled bottle while the reject log sent it to the reject bin, so the data shipped a bottle that did not.
A bottle sent to the rework tray at a jam belonged to no case, and was most likely the one put back in the pulled bottle's place.
Two print checks destroyed at line clearance stayed commissioned until the eBR start-up page was read.
The draft called those start-up serials samples; the eBR page says destroyed, and the sample log would have read two more.
demoSample data, from the working solution.
Agents read and draft; people re-scan, approve and countersign.
Reads the allocation, the serialization system's counts, the reject log and the eBR packaging pages.
Matches serial by serial from commission to decommission, case and pallet, and finds conflicts.
Computes the leak, holds the file, traces each leaked serial with a confidence and asks the line in fixed fields.
Drafts exact corrections as a versioned set, each with its evidence.
Plays the client's serialization auditor, the agents' own draft included.
Builds the EPCIS file after both signatures, sends it to the client's portal and reads back the client's receipt.
Beyond the run itself: the sign-off order, the queue across plants and clients, another market's run, and the trail and settings behind them.
demoSample data, from the working solution.
Serialization and aggregation give each saleable pack a unique serial number and record which packs sit in which case, and which cases on which pallet. Here agents reconcile both for each packaging run, so each commissioned serial ends in a shipped case or a decommission before the client's file leaves the plant.
That the serials commissioned on a run equal those aggregated into cases plus those decommissioned as rejects, samples or destroyed units. Anything left over is a leak, which the agents trace to the physical action behind it through the reject log, line events and batch record pages.
The DSCSA asks for a product identifier on each package and homogeneous case. Aggregation to the pallet is industry practice agreed with the client, and the aggregated data sent downstream must match what was serialized, which is what this reconciliation checks.
Under EU FMD, the manufacturer keeps a record of each operation on the unique identifier, and reference and retention samples are not uploaded to the repositories system. A client market that follows those rules gets its own rule set, which keeps those samples out of the upload while aggregation stays voluntary by agreement.
The commission, decommission and aggregation events for the run, built only after packaging QA approves the corrections and the serialization lead countersigns. The client's reply comes back in fixed fields, stating what its repository accepted.
No. Reconciliation closes the serial books for the run; the QA head dispositions the lot, and the client, as brand owner, makes its own market release decision.
One plant's root cause becomes every plant's check within days, each answered with evidence.
1-min demoMulti-Site Manufacturing BenchmarkingThe best plant's way becomes every plant's way, with the records that prove it.
1-min demoManufacturing KPI StandardizationEvery plant, report and agent answers from one signed number, so meetings argue causes, not definitions.
1-min demoShare one run's serialization report with its reject log and the batch record's packaging pages, and we can account for each serial it commissioned.