Should a Label Rewinder Reject and Splice Defects Automatically? Define the Defect Rules First

Start with the accept-or-reject decision, not the camera speed

List the defect classes that require removal for the actual job: missing print, text or barcode failure, register movement, colour or density outside the approved limit, contamination, die-cut fault, missing label, matrix remaining on the web or a customer-specified critical mark. Separate defects that require rejection from cosmetic variations that are still saleable. The decision must come from the approved artwork, product specification and risk of the application.

Flexographic Technical Association guidance explains that 100% inspection commonly compares the running web with a master image. It also warns that sensitivity set too high creates unnecessary alerts, while sensitivity set too low can let print faults pass. An automatic rejection workflow will act on the classification it receives, so a weak defect master can create automatic waste just as easily as it can miss a fault.

Create a defect table for each product family. Record the region of interest, defect type, size or tolerance method, severity, action and who may approve an exception. Use retained accepted and rejected samples when setting the inspection master. Do not rely on one generic recipe for pharmaceutical text, a cosmetic highlight, a logistics barcode and a blank label.

Prove that the defect position survives the complete web path

A camera can find a defect only at its inspection position. The rewinder must then locate the same defect after the web travels through rollers, accumulators, slitting and tension zones. Record the direction of travel, encoder reference, distance from inspection to rejection, roll and job identity and any change in the web path. A wrong scale, slip or incorrect reference point can make the cut land on good labels while leaving the failed label in the roll.

Run a validation roll with known, clearly identified defects at the web centre and near both edges. Include isolated defects, two defects close together and one defect near the intended splice. Compare the inspection record with the physical label position before enabling automatic cutting. If the machine is fed by defect data from an upstream press, confirm roll direction, roll identity, length reference and how removed or inserted material changes the coordinate.

FTA reporting on inspection workflows notes that captured run data can support defect removal and that linked systems can use defect positions to stop a rewinder. The same principle applies when the next action is automatic. The position record must remain correct through every process step; the automation should not be accepted only because the camera displayed the defect on screen.

Specify the removal and splice, including what happens around the defect

Define whether the system removes one label, a fixed length or material up to safe boundaries before and after the defect. State what should happen when defects are adjacent, when a fault crosses a slit lane or when the defect lies close to the core, roll change, existing splice or finished-roll length. These rules determine waste, splice count and whether the finished roll remains usable in the customer's applicator or next process.

Specify the approved splice construction: tape, width, position, overlap or butt arrangement, maximum thickness, alignment, marker requirement and the number of splices permitted in one finished roll. Confirm whether the end use accepts a splice at all. Food, pharmaceutical, security, high-speed dispensing and automatic application jobs may have different customer rules; the machine capability does not replace those rules.

PRATI reports that SATURN Next has been demonstrated with automated quality control, defect rejection and splicing, together with defect positioning, web cutting, waste editing, counting, automatic slitting and rewinding. Treat that as a workflow to qualify with your material and acceptance criteria. A demonstration on one self-adhesive construction does not prove the same cut, tape or splice result on every paper, PET liner, unsupported film or multilayer material.

Build the factory-acceptance trial around failed and released rolls

Prepare a trial matrix before the machine test. Include the intended substrates, minimum and maximum web or slit widths, roll diameters, normal production speed range, clear or low-contrast material where relevant, expected defect classes and the approved splice materials. Add restart, acceleration, deceleration and roll-end conditions, because defect positioning and web control must remain stable away from steady running.

For every seeded defect, record whether it was detected, classified, located, removed and replaced or spliced as intended. Also record false rejects and any good labels removed around the fault. Inspect the splice for alignment, adhesion, thickness and passage through the next process. Rewind the finished roll to its required direction and verify count, roll build, sidewall, core position and label sequence.

Challenge the exception paths. Confirm what the machine does if the camera loses the master, the defect position is unavailable, the splice tape is missing, the waste-removal action is incomplete or an operator pauses the cycle. The safe response should be documented and understood by production and quality staff. Automatic continuation is useful only when the system can stop and hold the job when evidence is missing.

Release the workflow only after the inspection report, physical roll and downstream test agree. Save the approved master, tolerance set, defect-action table, material and splice specification, machine recipe, software version and signed trial results. For a Royal Coat review, send the artwork and critical areas, substrate and liner, web and slit widths, speed, finished-roll specification, defect classes, customer splice rule and accepted and rejected samples.