Six ways the case–pallet relationship breaks in aggregation
Rejected packs, partial cases, sampling, manual handling, double assignment and pallet breakdown: the most common situations in which aggregation records drift from physical content, and how to prevent them on the line.
Aggregation is the parent–child record that links saleable units to a case and cases to a pallet. Set up correctly, scanning one pallet label means knowing the serial number of every pack on it; warehouse and shipping operations run without scanning packs one by one. When the record drifts from the physical content, the problem usually surfaces after shipment, as missing or extra product at the receiving end.
The situations below are where the relationship breaks most often. What they have in common is a physical event on the line that never reaches the software.
1. A rejected pack stays in the record
The camera rejects a pack and it is ejected; but if the pack had already been assigned to a case, or the reject never reached the aggregation station, it stays in the record. The reverse also happens: a pack put back on the line by hand after a reject is never assigned to any case.
What helps: record the reject decision and the physical ejection as one event, and let the aggregation station accept only serial numbers that passed verification.
2. Partial cases
At the end of a batch the last case is not full. If the partial case is not closed explicitly in the software, the system may try to add the next batch's packs to the same case, and batches get mixed.
What helps: closing the batch must close the partial case; the case record holds the actual quantity, and the label shows it.
3. Sampling
Samples taken from the line or from a case for quality control physically leave the hierarchy. If they stay in the record, the receiver expects products that are not in the case.
What helps: take samples at a station by scanning; the pack status changes to "sample" and the pack drops out of the hierarchy.
4. Manual handling
Operators moving packs by hand after a jam, a damaged pack or a line stop is the most common source of drift. Every movement made outside the system invalidates the record.
What helps: set up a rework station where opening a case, removing and adding packs is done by scanning, and every action is written to the audit trail with user and time.
5. The same pack in two cases
On fast lines, a pack read twice, or an old relationship not removed during rework, links one serial number to two parents.
What helps: the software enforces "every child has exactly one parent" at database level; a second assignment is rejected with a warning.
6. Pallet breakdown and re-palletizing
When a pallet is split in the warehouse and its cases are moved to other pallets, a pallet record that is not updated makes the shipping notice show the old content.
What helps: breaking down and building pallets is done by scanning too; a new pallet gets a new SSCC, and an old SSCC is never reused.
Print the label last
If the case label is printed before the content is final, a gap opens between label and content. In a good flow the case is filled, its content is verified, and only then is the label printed and scanned to match it with the record. You can verify SSCC check digits with the check digit calculator and review overall line readiness with the serialization readiness checklist. If you want to review the aggregation flow on your current line together, get in touch.
Let's discuss this for your plant
More notes
All notes →- 3 min readSix common mistakes on medical device UDI labelsPackaging levels, changes that require a new UDI-DI, confusing Basic UDI-DI with UDI-DI, missing production identifiers, labels that don't match the barcode and unmeasured print quality: the most common UDI mistakes for medical devices.
- 2 min readGaps and bad records in SCADA data: what to do before modellingTimestamps, gaps, frozen sensors, physically impossible values, curtailment and maintenance periods, sensor replacement: what to check in SCADA data before building a predictive maintenance or power forecasting model.
- 3 min readFive common errors in pharma serialization codes and how to catch them on the lineMissing separators, wrong check digits, date format mix-ups, duplicate serial numbers and disallowed characters: the most frequent errors in pharma DataMatrix codes and how to prevent each one on the line.