Inspection and rejection
A practical guide to defect definition, sensing, pack tracking, reject handling and acceptance evidence for automated packaging lines.
The inspection method must match the defect, pack presentation and available contrast or measurement. The control system must then associate the decision with the correct moving pack, remove that pack reliably, confirm the reject action and define what happens when inspection or rejection cannot be completed.
System purpose
Depending on the application and chosen sensor or vision method, inspection can check presence, position, orientation, readable variable data, barcode content, closure presence, label presence, gross fill level, case condition or another observable pack feature. The system should not be described as checking a condition that its sensor cannot reliably distinguish under normal production variation.
Begin with the defect definition. State what a good pack looks like, what the unacceptable condition looks like, where the pack can be observed and how presentation, lighting, speed, reflective surfaces or product variation can change the image or signal.
Control sequence
Method selection
| Inspection need | Possible approach | Key application questions |
|---|---|---|
| Presence or position | Photoelectric, proximity, contrast or vision sensing, depending on the feature and material | Can the feature be seen consistently? Does colour, transparency or reflection vary? Is the pack position repeatable? |
| Printed code | Code presence, optical character recognition, optical character verification or barcode reading | Is the requirement only presence, or must content be compared with an authorised data source? What print and background variation occurs? |
| Label condition | Label sensor or vision inspection | Must the system detect absence, skew, position, artwork, barcode or several conditions? Can the whole label area be viewed? |
| Closure condition | Height, presence, orientation or vision inspection | Which finished-pack feature proves acceptable application? Can an incorrectly engaged closure appear present from one view? |
| Fill or contents | Level, weight or another application-specific measurement | Is the product visible? Does foam, opacity, container shape or settling affect the reading? Is legal metrology relevant to the finished pack? |
| Case or pallet identity | Barcode or label verification linked to line data | Which identifier is authoritative? How is the unit associated with the order, case or pallet before release? |
Physical rejection
A lightweight empty container, a filled glass bottle, a flexible pouch and a sealed case have different momentum, stability and acceptable handling. The reject device must have enough time and travel to move the failed pack clear without damaging adjacent good packs or creating an unsafe condition.
Review conveyor speed, pack pitch, accumulation pressure, guide position, reject direction, available space and what happens during a stop. The reject route should retain failed product securely and make removal or investigation clear to the operator.
Tracking and recovery
Reject logic is straightforward only when packs move at a fixed pitch with no stops between inspection and rejection. Real lines may slow, stop, accumulate or lose a pack. The tracking method should state what establishes movement, how queued decisions are retained, how missing triggers are handled and when the system declares tracking uncertain.
Challenge tests should include a failed pack followed closely by good packs, consecutive failures, a stop between inspection and reject, removal of a pack, blocked reject path and restart after an alarm. The required result may be reject, controlled stop, line clearance or another agreed response.
Data and ownership
A camera or reader can observe printed information, but the project must define which system supplies the correct value and how that value is associated with the pack. For variable data, identify whether the line control, coder, production system or operator entry is authoritative. Define permissions, recipe selection, change control and the response to missing or conflicting data.
The coding and marking page explains the print task, while print-and-apply guidance covers labels created during production. The controls and sensors guide helps specify line states and handshakes.
Inspection should be one layer within a controlled packing process. It cannot compensate for uncontrolled components, incorrect recipe selection or a defect definition that changes between teams. Agree ownership of standards, challenge samples, limits, review and maintenance before acceptance.
Buyer questions
Not every packaging inspection needs a vision camera; a simpler sensor or reader may be more robust when the defect is a clear presence, position or code condition. Use vision when the decision needs spatial or visual information that a simpler device cannot provide.
The choice should follow controlled samples and the real defect definition.
The line rejects the correct pack by associating the inspection decision with a tracking reference and carrying that decision to the physical reject point. The reference may use pack counts, encoder movement, controlled pockets or another method.
It must be tested through stops, gaps and abnormal conditions, not only steady running.
If a reject is not confirmed, the line should enter the predefined response that protects the good-product stream, commonly an alarm and controlled stop until the uncertain packs are contained. The exact response depends on the product, process and quality system.
Define it in the control narrative and test it during FAT or SAT.
One inspection system may check several visible features when they can be viewed reliably within the same presentation and processing time, but combining tasks can increase setup and validation complexity. List each defect independently and prove it with representative good, bad and borderline samples.
Do not assume that seeing the label automatically verifies the printed data.
