How Should Packaging-Line Rejects and Rework Be Managed?
A reject system must identify the affected pack, remove it at a controlled point, confirm the action and prevent unapproved return to production. Detection alone is not a complete reject strategy.
Trace the defect from its source to a confirmed disposition
A reject system must identify the affected pack, remove it at a controlled point, confirm the action and prevent unapproved return to production. Detection alone is not a complete reject strategy.
Define each reject reason, the station that detects it, how the specific pack is tracked to the reject point, how successful removal is confirmed and what the line does if confirmation fails. The design must also control the reject container, access, capacity and segregation route.
A pack can acquire several quality states as it moves through filling, closing, labelling, coding and inspection. Where practical, retain the reason and relevant process result so the final reject record explains whether the defect began upstream. This prevents the visible symptom at the last station being treated as the root cause.
Rework requires an approved product- and quality-specific procedure. Returning a pack at the wrong point can bypass an inspection, create duplicate codes, mix batches or expose the process to contamination. The line should not rely on informal operator judgement where controlled disposition is required.
| Decision | Questions to answer | Evidence to retain |
|---|---|---|
| Detection | What defect or missing condition is being detected, and at what confidence? | Challenge samples, sensor or inspection result and approved limits. |
| Pack tracking | How is the affected pack associated with the later reject action? | Distance, encoder or timing logic, queue rules and interruption tests. |
| Removal and confirmation | How is the pack removed and how is success confirmed? | Reject-device challenge, confirmation sensor and fail-safe response. |
| Segregation | Where do rejects go and who can access them? | Bin capacity, lock or access rule, full detection and reconciliation. |
| Rework or disposal | Can the pack be corrected, where may it re-enter and which checks repeat? | Approved procedure, batch and code controls, inspection route and disposition record. |
Prove the complete reject route
Use the same evidence in the project brief, supplier clarification and acceptance plan so the decision remains traceable from concept to handover.
Create controlled defects
Use safe challenge packs representing each detection and tracking condition.
Run normal and disturbed flow
Challenge gaps, queues, stops, restarts, manual removal and speed changes.
Confirm segregation
Verify that the intended pack is removed and the reject container and full condition are controlled.
Reconcile the result
Match detections, reject confirmations, physical packs and any approved rework records.
Common questions about packaging-line rejects and rework
Each answer states the practical principle first, then identifies the variables that must be confirmed for the actual product, pack, line and site.
Where should rejects leave an integrated packaging line?
Use a point where the final defect decision is available and the affected pack can be removed reliably without creating another hazard or bypass. Some early process failures may need immediate removal; others can be tracked to a common confirmed reject station. The chosen location must preserve pack identity through queues, stops and restarts.
How should a reject be confirmed rather than assumed?
Confirm that the reject device operated and that the specific pack left the accepted product flow. Depending on the risk, this may use a sensor, count reconciliation, vision, checkweigher or controlled reject bin. If confirmation is missing, the line should enter the agreed safe quality state rather than silently continue.
Can rejected packs be returned to the line?
Only under an approved rework procedure that identifies which defects can be corrected, the permitted re-entry point, required line clearance, batch and code controls, and every inspection that must repeat. Packs with uncertain identity, integrity or contamination status should not be informally reintroduced.
What records should be kept for rejected packs?
Record the time or production reference, product and format, defect reason, detecting station, reject confirmation, quantity, batch or code context where required, and final disposition. The level of traceability should match the product and site quality system; avoid collecting data that has no defined use or owner.
How should the line respond when the reject route is full?
Detect the full or unavailable condition before the system can no longer segregate affected packs. The agreed response may be a controlled stop, prevention of further product entry or diversion to a validated alternative. Access, emptying and reset should be controlled so accepted product is not mixed with rejects.
Information needed to define reject and rework control
Share verified information and representative samples where relevant. Lancing can then distinguish confirmed requirements from items that need a trial, survey or design review.
Project information
- Defect list, limits and detecting station.
- Pack tracking method and queue conditions.
- Reject device, confirmation and failure response.
- Reject-container capacity, access and segregation.
- Batch, code and data records required by the site.
- Approved rework, re-entry and repeated-inspection rules.
Application-specific confirmation
This guide explains a selection and integration framework. Final machine suitability, safety, utilities, performance and compliance depend on the actual product, pack, equipment configuration, site and agreed tests.
Related packaging-line guidance
Follow the next question that affects the same production decision.