Cartoning Systems: Scope, Line Capacity & Acceptance

What should a cartoning system include?

A cartoner is the machine that handles the folding carton and loads the product in its configured sequence. A cartoning system includes the supporting functions needed to deliver an agreed finished pack. Some functions may be inside the cartoner; others may be separate machines, operator tasks or equipment supplied by another vendor.

Draw two boundaries on the layout: the point where product enters your purchased scope and the point where an accepted pack leaves it. “Automatic” is not a sufficiently precise boundary. For example, receiving pre-grouped products on a conveyor is a different obligation from counting individual sachets arriving from several lanes.

For model configurations, use the HIJ cartoning machine range. If the contract ends at a closed retail carton, downstream case packing remains a separate function unless it is explicitly included. Do not count it as part of the cartoner simply because it appears on the same layout. If you are deciding which packaging level to automate, compare cartoners and case packers by their finished package before defining the supply boundary.

Specify the product at every physical handoff

Prepare an interface sheet for each connection. Identify the outgoing equipment, receiving equipment, transfer height, direction, support surface, product pitch and the condition in which the product arrives. Record the smallest and largest approved formats, not just the nominal sample used during the sales demonstration.

Describe variability as well as dimensions. A soft sachet may arrive with changing thickness or a projecting seal; a cylindrical pack may roll unless controlled; a group may need to stay together while it changes direction. These are sample-review questions, not reasons to assume one feeder works for every product.

Keep a consistent vocabulary in the drawings. “Product” might mean one sachet upstream and one group of six at the cartoner. Label those as individual packs and groups of six. A conveyor sensor that detects one group does not automatically prove the group contains the correct number of items.

The cartoner infeed guide covers feeder choices in more detail. Bottle-specific transfer and filling-line questions belong in the bottle cartoning integration guide. Here, the deliverable is a documented connection that both equipment suppliers have accepted.

Put every machine rate into the same units

A line containing several machines cannot be compared by placing their headline numbers side by side. Products per minute, cartons per minute and cases per minute describe different quantities. Convert them to a common unit for each SKU before discussing a bottleneck.

These figures describe a simplified flow balance, not accepted production. Define accepted output separately: conforming finished cartons counted at the agreed endpoint, divided by the agreed elapsed test time. Specify whether replenishment, small stops and recovery are inside that period. A short peak-speed demonstration and a sustained accepted-output test answer different questions.

Do not multiply unrelated vendor “efficiency” percentages unless their definitions, time boundaries and populations match. Ask for the actual test conditions and a line-level result. Product mix, changeovers and the available production schedule still determine whether the system can complete your orders.

A buffer needs both capacity and a recovery plan

A buffer temporarily separates the operation of adjacent machines. Its useful capacity is the amount that can be added or removed from its normal operating level while preserving product condition and the intended flow. The total conveyor length or nominal number of pockets is not automatically usable spare capacity.

For a preliminary accumulation estimate, use additional items = net inflow × interruption time. If the downstream machine stops completely, net inflow equals the continuing upstream inflow. If it keeps running more slowly, subtract its outgoing rate in the same units.

Specify what happens when the buffer approaches full or empty. Agree the normal operating level, stop-request thresholds, product protection and restart permissions. Confirm these against the actual layout, sensor response and safe stopping behaviour. A buffer must not be used to justify uncontrolled pressure, untracked product or bypassed guarding.

Repeated interruptions can fill a buffer even when it absorbs one isolated stop. Test realistic sequences and the time needed to recover between them. If the real receiving rate does not exceed incoming flow during recovery, address the rate balance or scheduling rather than merely installing more storage.

Agree machine states, permissions and product recovery

Write the sequence of events before choosing a communications protocol. The interface should answer practical questions: can the receiving station accept another item, when must the sending station pause, which machine reports a blocked transfer, and who authorizes a restart after a fault?

OMAC's PackML resources describe a common approach to machine behaviour and consistent machine data. Such conventions can help structure an interface discussion. They do not prove that two particular machines are compatible, that the required tags are implemented, or that a safety function is covered. Confirm the actual implementation and keep safety-related controls within the project's competent engineering review.

• Product starvation: define whether the cartoner waits, skips a carton or completes products already inside the machine.
• Downstream blockage: define the stop request, remaining product movement and the available discharge space.
• Reject or inspection fault: define the affected product range, rejection confirmation, segregation and restart conditions.
• Communication loss: agree the permitted machine response and how product positions are re-established before automatic operation resumes.
• Recipe change: verify that the pack count, carton format, inspection settings and downstream grouping belong to the same approved SKU.

A common brand of PLC is not evidence that these behaviours have been engineered. Nor does one shared HMI establish a single, complete batch record. Document which device owns each command, which signals are acknowledged and which production records the customer actually receives.

Name an owner for each interface, not just each machine

For every connection, record who designs it, who supplies the hardware and software, who tests it and who resolves a failure at the joint. A two-vendor boundary needs a named lead even when both machines pass their separate factory tests.

As an industry example, PROPACK's integration overview distinguishes standalone installation from complete-line integration and identifies layout, conveyors and controls interfaces as project inputs. That is a useful scope distinction, not evidence of what any HIJ quotation includes.

Put exclusions next to inclusions. Identify responsibility for connecting conveyors, change parts, sensors, reject collection, electrical connections, layout access, training, documents and site commissioning. Separate an optional future expansion from equipment supplied now. A reserved space or spare control connection is not proof that a later feeder will fit or achieve the required rate.

For a phased project, define what the first phase can deliver independently and what must change when the second phase arrives. Recheck guarding, line control and acceptance responsibilities when the boundary changes. A general statement that the line is “upgradeable” is not a substitute for this scope.

Test the connected system at its boundaries

Machine-level FAT and line-level acceptance should complement each other. When adjacent equipment is unavailable at a factory test, record what was simulated and what remains to be demonstrated at site. Do not report a simulated interface as a completed full-line test.

1. Start with approved samples. Identify product, carton and insert revisions. Include the formats that challenge grouping, transfer, closure or inspection.
2. Run the specified mix and output conditions. Record elapsed time, accepted cartons, rejected cartons and interruptions. Confirm the counter location and treatment of work in progress.
3. Challenge the handoffs. Use an approved test procedure to demonstrate starvation, blockage, buffer high/low conditions and recovery. Never defeat safety devices to create a test.
4. Reconcile product. Account for incoming items, finished packs, rejects and material left between machines. Explain intentional test samples separately.
5. Change the format. Verify the complete connected recipe and tooling sequence, then show that the first accepted cartons belong to the new SKU.
6. Close the open items. Identify the owner and evidence needed for any unresolved factory or site acceptance condition.

The cartoning machine FAT checklist covers detailed machine tests. The additional system-level question is whether product and information remain controlled across every purchased boundary. Agree acceptance criteria in the URS and contract; no universal test duration or fault allowance fits every application.

Turn the line concept into a specific equipment request

Start the discussion with your finished-pack samples, SKU/count matrix, required accepted output and a layout showing incoming and outgoing equipment. Add the existing machine details and identify tasks that will remain manual. Ask the supplier to return a proposed scope and interface list alongside the machine configuration.

The HIJ automatic cartoning machine provides a platform reference for that discussion. Its suitability and integration scope must be checked against the product and project; the buffer and rate examples in this guide are not specifications for that machine.

If your immediate decision is whether to operate equipment internally or outsource the packing work, use the in-house versus contract retail cartoning guide first. If the business case is settled, the next useful document is a scope drawing with measurable acceptance criteria, not another list of nominal machine speeds.