Jar handling
Specify infeed condition, spacing, accumulation, line height, stability limits, guide-contact restrictions and discharge requirement.
A procurement specification should describe the required production result and the evidence for acceptance without forcing an unsuitable machine design. Use verified pack data, clear responsibilities and controlled assumptions.
Use production evidence. Final machine selection and acceptance depend on representative jars, lids, process conditions and agreed checks.

State what the completed system must achieve with the approved jars and lids. Let the supplier explain how the proposed machine achieves it, then make assumptions, options and exclusions visible.
| Specification section | Include | Avoid |
|---|---|---|
| Application | Products, jars, lids, process condition, batch pattern and current constraint. | Generic phrases such as “suitable for all jars”. |
| Performance | Good-pack output basis, staffing, run condition, quality checks and changeover requirement. | An isolated headline speed with no test basis. |
| Supply boundary | Infeed, lid supply, capper, conveyors, controls, guarding, inspection and outfeed interfaces. | Assuming that “automatic” includes every upstream and downstream function. |
| Acceptance | Samples, run duration, defects, measurement methods, FAT/SAT and sign-off responsibilities. | Approval based only on visual demonstration. |
| Site and support | Utilities, access, installation, commissioning, training, documents and spares scope. | Leaving site responsibilities until dispatch. |
List each jar and lid part number, dimensions, material, normal variation, filled weight, product condition and approved closure method. Identify the formats included in acceptance and any future formats that are for design consideration only.
State the finished-pack tests and who owns the limits. For threaded lids this may include application or removal torque, engagement, cap height, leak or tamper feature. For twist-off and vacuum packs it may include lug engagement, button state, vacuum, leak, cooling condition and visual checks. Do not publish a universal value where the pack owner has not approved one.
Specify infeed condition, spacing, accumulation, line height, stability limits, guide-contact restrictions and discharge requirement.
State manual placement, pre-placement or bulk feeding; refill method; orientation; change parts; acceptable cosmetic condition; and low-level response.
Define start permission, ready, fault, starved, blocked, reset, emergency-stop and any required data or recipe interface at a functional level.
Use the line-integration guide and site-preparation guide to complete the interface schedule.
Identify which tests occur at Lancing and which require the customer’s site, product or connected line. Define the approved samples, run duration, operator involvement, replenishment, planned stops, reject categories and sampling method.
For closure results, identify the instrument or method, units, timing, sample quantity and reaction to a marginal result. Record whether destructive tests consume samples and who supplies enough components for setup, repeat runs and teardown.
See the FAT, SAT and commissioning guide for a structured handover sequence.
Use the cost-factor guide to compare quotations on the same boundary. A lower total may simply exclude lid feeding, change parts, site work or acceptance evidence.
Request that the supplier marks each requirement as included, excluded, optional, subject to sample trial or requiring clarification. This exposes gaps before order and creates a controlled basis for later changes.
Send a procurement brief to LancingOnly when the model is already verified and there is a justified reason. A functional specification normally gives suppliers room to propose the correct configuration for the pack and process.
Define good packs over an agreed representative run, including staffing, replenishment, normal stops, reject rules and the formats to be tested.
List the approved format matrix, change parts, tool requirements, settings or recipes, first-off checks, expected operator role and the acceptance method for the changed format.
The pack owner should provide verified limits and methods from its closure and process development. Where limits are not yet established, the specification should require trials rather than inventing values.
Clear exclusions prevent assumptions about conveyors, utilities, guarding, integration, samples, installation or validation from becoming disputes later in the project.
Send your jar, lid, product and target output. Lancing will help you identify a practical machine route and the samples needed for confirmation.