What are you filling?
Include product name, free-flowing or dusty behaviour, particle size, density if known, and whether samples are available.
Use this checklist to send the product, target weight, pack style and output details needed for a useful weigh filling machine recommendation.
The more complete your brief, the easier it is to compare the right machine options. Product behaviour, target weight, pack type, output and line constraints are the details that usually make the biggest difference.
These prompts reduce back-and-forth and make the first recommendation more useful.
Include product name, free-flowing or dusty behaviour, particle size, density if known, and whether samples are available.
Give minimum and maximum fills, tolerance expectations, giveaway sensitivity and pack-count range.
Explain whether the filled pack is sealed, capped, labelled, coded, checkweighed, conveyed or packed into cases.
Answers for buyers preparing a weigh filler enquiry.
No. Send what you know. Product, target weight, pack type and desired output are enough to start a useful conversation.
Samples are often helpful when product flow, dust, fragility or dosing behaviour may affect the machine route.
Early planning is useful because line layout, utilities, pack format and future SKU range can affect the machinery decision.
That gives Lancing enough information to compare a linear weigher, multihead weigher, auger filler or integrated bagging line.
A complete enquiry reduces assumptions and allows the same basis to follow the project from initial shortlist to factory acceptance.
| Information | What to send | Why Lancing needs it |
|---|---|---|
| Product | Name, composition, representative samples, bulk density, particle size, dust, static, fragility, moisture and batch variation. | Chooses the feeder, hopper, contact path and cleaning route. |
| Weights | Smallest, normal and largest target; declared quantity; tolerance; current giveaway or underweight problem. | Sizes the weighing path and defines the acceptance statistics. |
| Packs | Actual pouch, bag, jar, tub or bottle with dimensions, opening, film, seal or closure. | Defines product drop, support, clamp, former and downstream handling. |
| Output | Accepted finished packs per minute, hours per shift, batch size and operator plan. | Separates filler cycle from the real production-line requirement. |
| Line and controls | Layout, upstream feed, downstream machines, utilities, controls standard, coding and inspection. | Defines interfaces, buffers, conveyors, guarding and commissioning scope. |
| Cleaning | Product sequence, allergen/cross-contamination standard, cleaning method and changeover target. | Checks access, removable parts, tooling, drains or dust containment. |
| Acceptance | Sample size, mean, standard deviation, min/max, under-target rules, product damage, seal quality and output duration. | Prevents a vague “accuracy” or “speed” claim becoming the only test. |
Sample quantity is not a fixed website specification. It should be sufficient to tune the machine, challenge the required weights, include refills and changeovers, and complete the agreed consecutive-fill run without substituting a different product lot.
| Trial input | Project-specific basis | What to record before dispatch | Why it matters |
|---|---|---|---|
| Product quantity | One supplied LU-3000C quotation requested 10–15 kg of representative product. Other projects may need more or less. | Batch or lot, date, moisture or conditioning, bulk density where known, fines, particle range and normal production variation. | The same sample must cover tuning, all targets, refill behaviour and the acceptance run. |
| Pouch quantity | The same quotation requested 25–50 empty pouches of each size. | Size reference, dimensions, laminate, zipper or closure, maximum usable opening and print/code position. | Allows outlet review, repeated filling, sealing trials, rejects and changeover without relying on one ideal pack. |
| Target matrix | Smallest, normal and largest production weights rather than one convenient test point. | Declared quantity, internal tolerance, current set-point, expected batch size and finished-pack output. | Feeder trim, weigh-hopper capacity, bulk volume and cycle time can change across the range. |
| Line interfaces | Manual pouch presentation, bag clamp, conveyor, premade-pouch machine, VFFS or rigid-container handling. | Layout, heights, line direction, ready/busy signals, coding, inspection and downstream stop behaviour. | Prevents a successful standalone dose from failing when connected to the real pack route. |
| Acceptance method | Agreed before the trial and tied to the intended product, pack and output. | Reference scale, tare method, consecutive sample size, mean, standard deviation, min/max, rejects, product loss and elapsed time. | Keeps the decision evidence-led and avoids selecting one favourable fill or short burst. |
Do not sieve out normal fines, dry a moisture-sensitive product unusually, use laboratory-perfect packs or omit the most difficult target unless that condition is excluded from the final specification. Record any difference between trial material and intended production.
Prototype pouches can support an early feasibility test, but production-quality laminate and dimensions are normally needed before outlet, sealing and sustained finished-pack acceptance are closed.
No. That was the requested basis for one supplied LU-3000C project. The required quantity depends on product, number of targets, hopper volume, line configuration, changeovers and the agreed acceptance run.
It should reflect normal production particle size, fines, moisture, bulk density, fragility and batch variation. Any conditioning or difference from production should be declared.
They can support early feasibility work, but final outlet, pouch handling, sealing and finished-pack acceptance normally need production-quality packs with the intended dimensions and laminate.
Agree product and pack references, targets, settings, hopper range, operator tasks, reference scale, consecutive sample size, statistics, reject rules, product-quality checks and finished-pack output.