First-off approval
Confirm the format after setup, material change or an adjustment that can affect bottle control or tightening.
Pack quality
Capping quality control plan
Define the accepted capped pack, the test method and evidence required before settings are approved.
Quality plan
Define an accepted capped pack before setting the machine.
A torque value alone does not describe every closure. The plan should state the checks that matter for the bottle, cap, liner, tamper feature and product, together with the method and decision rule.
The pack owner's specification remains the authority. Lancing can help establish trial evidence, but product compatibility, seal performance and release criteria must be confirmed for the buyer's materials and process.
Minimum plan inputs
- Approved bottle, closure and liner references.
- Defined first-off and in-process checks.
- Named test method and equipment.
- Response to a failed or borderline result.
- Record retention and change-control responsibility.
Control points
Build checks around the failure modes that matter.
| Check | What it can reveal | Condition to record |
|---|---|---|
| Visual seating | High, tilted or damaged caps, tamper-band faults, scuffing or incomplete engagement. | Cap and bottle reference, line state and observation standard. |
| Thread engagement | Cross-threading, false starts or tightening without reaching the seated position. | Sample source and inspection method. |
| Removal or application torque | Variation measured with a defined instrument and technique. | Instrument, units, direction, delay and sample temperature. |
| Liner or seal condition | Uneven compression or damage that torque alone may not show. | Inspection method and pack-owner criteria. |
| Leak or integrity test | Whether the pack meets the product owner's containment requirement. | Test medium, orientation, time and other defined condition. |
| Restart samples | Quality drift after a feeder fault, jam clearance, stop or changeover. | Stop cause, restart sequence and first accepted sample. |
Sampling logic
Check at moments most likely to introduce change.
In-process verification
Choose frequency from pack risk, run duration, material variation and the site's quality system.
Event-based checks
Take samples after jams, restarts, feeder faults, unusual noise, damage or intervention in the capping zone.
Connected guidance
Link quality evidence to setup and troubleshooting.
Quality evidence
Share acceptance criteria before the machinery trial.
That allows the test to address the closure characteristics and failure modes important to the project.
Inspection and rejection
Questions for turning pack acceptance into a workable line control
Define the faults that matter, decide which can be detected inline and retain offline checks for properties that sensors do not prove directly.
Which capping faults can reasonably be checked inline?
Depending on the pack and inspection system, inline checks can identify cap presence, gross cap height, obvious tilt, missing or mispositioned closures and some visible damage. Detection capability must be proven with real good and bad samples. The capping reject-system guide starts with failure modes rather than a sensor list.
Which closure checks still need offline sampling?
Removal torque, leak performance, liner seating, opening experience and subtle thread or tamper-feature faults often require a controlled offline method. Inline inspection can reduce risk but does not automatically prove every closure property. Define the sampling method, timing and escalation rule alongside the automatic checks so both parts support the same accepted-pack standard.
How should reject logic respond to repeated faults?
A single verified reject may be removed while the line continues, but repeated or clustered faults should trigger an agreed warning, controlled stop or escalation because they can indicate a feeder, setup or packaging problem. The response must suit the risk assessment and prevent suspect packs bypassing inspection. Test the sequence using representative fault samples before production handover.
How can a reject system avoid masking an upstream problem?
Log reject reason and frequency by time, format and batch, and make recurring patterns visible to operators and supervisors. A reject station should not become a substitute for correcting poor cap presentation, bottle handling or component quality. Define a threshold for investigation and retain the affected samples so the upstream cause can be examined instead of discarded unseen.