A rewinder can stop at the programmed count and still leave production, quality and dispatch with different quantities. The difference may come from setup waste, labels removed around a defect, splice allowances, a counter that reads the wrong feature, or a roll that was restarted without a controlled reset. Treat the counter as one production record, not the final proof of quantity. Before releasing the job, reconcile what entered the finishing process, what was removed and what was packed.
Define exactly what the counter is measuring
Write the counting basis on the job sheet: labels, repeats, impressions, metres or sheets. A counter that reads a registration mark can give a different result from one that reads the die-cut gap, especially when the web includes missing labels, long repeats, clear constructions or multiple labels across. The setpoint must use the same unit as the finished-roll requirement.
PRATI describes finishing configurations that combine counting, cutting and rewinding, while its equipment configurator refers to label and length counting and an automatic slow-down and stop at the counting end. These functions are useful only when the sensor input, repeat definition and output unit agree with the job. Save those settings with the job instead of rebuilding them from memory at every repeat run.
Prove the setup with a short known sample. Mark a start point, count a manageable number manually and compare it with the displayed result. For clear labels or low-contrast marks, test at normal operating speed as well as crawl speed. A counter that appears stable during setup can miss or double-read when web speed, reflection or web flutter changes.
Keep good quantity separate from processed quantity
The machine may count every label or repeat that passes the sensor, including material later removed at the inspection table. Good finished quantity should therefore be calculated from accepted output, not from gross processed count. Record rejected labels or length against the reason: print defect, die-cut defect, splice removal, damaged core, setup or operator hold.
PRATI's published SATURN Next demonstration combined 100% inspection, defect positioning, waste editing, automatic splicing, counting, slitting and rewinding. That sequence shows why inspection and counting records must be linked. When a defect is removed and the web is rejoined, the finishing record should show what was rejected and whether the counter continued, paused or restarted.
Do not hide the difference by changing the final count after the roll is complete. Keep gross count, rejected quantity and accepted quantity as separate fields. The arithmetic should be visible to quality and dispatch, and the accepted result should match the roll label and packing record.
Control every stop, splice and counter reset
A controlled stop needs a reason code and a counter status. If the operator backs the web up to remove a defect, confirm whether the same labels will pass the sensing point again. If the counter is not direction-aware, reverse movement or a second forward pass can create a false quantity. The correct response depends on the machine and sensor arrangement, so document the actual sequence during commissioning and training.
For manual splices, define how many labels or how much web must be removed on each side of the joint. Record that allowance instead of estimating it at the end. For automatic rejection and splicing, verify the machine's job report and the physical splice location during the first production trial. Automation reduces repeated handling, but the release procedure still needs evidence that accepted labels were not removed or defective labels retained.
Restrict counter resets to named job stages. A practical rule is to record the old value, reason, time and new value whenever a reset is necessary after setup. If power loss, emergency stop or job recall can change the counter state, include that case in the restart checklist.
Reconcile each roll before the core leaves the machine
For every finished roll, record the roll number, target quantity, gross count, rejects, splice allowance, accepted quantity, unwind direction and operator. Where practical, add an independent physical cross-check such as roll diameter trend, web length or weight, but use it as a reasonableness check rather than a substitute for the approved counting method.
Inspect the tail and core before applying the final roll label. Confirm that the start and end positions are secure, the correct orientation is maintained and any splice is identified according to the customer's rule. If the accepted count does not reconcile, place the roll on hold. Reopening a record after dispatch is more costly than checking the difference while the web path and job settings are still available.
At job close, total all finished rolls and compare them with the order quantity, approved overs and unders, setup waste and recorded rejects. The total input length may help expose an unexplained loss, but it should not be converted to label quantity without using the actual repeat and lane arrangement.
Build the acceptance test into the equipment discussion
When evaluating an inspection rewinder or finishing line, bring a real job that is difficult to count: a clear label, a long repeat, a multi-lane layout or a roll with known defects. Define the required output unit and how defect removal, reverse movement, splicing and roll changes should affect the count. Test the complete workflow, not only sensor detection on a clean sample.
Ask what job data can be saved, exported or printed and how operator changes are logged. Confirm how the machine slows and stops at the target, whether the sensor can be positioned on the correct lane, and how the system handles a missed mark. PRATI's modular equipment covers counting within wider inspection, slitting and rewinding workflows, so the configuration should be matched to the material, quality requirement and release procedure rather than selected from speed alone.
For an application review, provide the substrate, label construction, repeat, number of lanes, web width, roll quantity, core and maximum diameter, inspection requirement, splice rule, unwind direction, accepted overrun and the customer's counting basis. Include both accepted and failed samples. Those details make it possible to discuss a verifiable release method instead of only a nominal counter feature.
Questions from production and purchasing teams
What to ask about finished-roll counting and reconciliation
Why can the machine counter and packed quantity differ?
The machine may count setup material, defects later removed, splice allowances or repeated web movement. A sensor can also miss or double-read marks. Reconcile gross count, rejects and accepted quantity separately.
Should the counter measure labels or web length?
Use the same unit as the customer's finished-roll requirement. Record whether the sensor counts labels, repeats, impressions, metres or sheets, and prove the setting with a known sample.
What should be recorded when a counter is reset?
Record the previous value, reason, time, operator and new value. Limit resets to defined job stages so that the final reconciliation remains auditable.
Can roll diameter or weight prove the label count?
They can provide a useful reasonableness check, but material thickness, tension, adhesive and core variation affect them. Use the approved counting method for release.
What information is needed to review a counting application?
Provide substrate and label construction, repeat, lanes, web width, target quantity, core and roll diameter, inspection and splice rules, unwind direction, accepted overrun and representative samples.