Application-led production guidance for preserves, sauces, chutneys & picklesCall an engineer  01494 623015sales@lancinguk.com
Sauce production application

Specify a sauce filling line around the product’s real operating window.

“Sauce” can describe a thin, foaming dressing, a shear-sensitive emulsion, a sticky ketchup or a chunky cooking sauce. Machine selection starts by defining viscosity, temperature, inclusions, aeration, pack opening and sustained output.

Application guidance by Lancing Ltd Updated 1 September 2026 How this guidance is prepared
A range of sauces illustrating different sauce filling machine requirements
Thin to highly viscousSmooth, foaming or particulateBottles, jars, pots and pouches

Do not select the filler from viscosity alone

Two sauces with similar apparent thickness can behave differently when pumped. One may aerate or foam, another may thin under shear, and another may leave a long tail after the nozzle closes. Product transfer, agitation and waiting time can change the condition before filling begins.

Define the complete operating range, including the easiest and most difficult normal formulations, temperatures, ingredient loads and batch ages. The trial should reproduce how product is actually supplied to the filler and how long it remains there.

Flow and shear

Record whether mixing or pumping makes the sauce thinner, thicker, aerated or separated.

Foaming

Test transfer and filling profiles that reduce air entrainment and uncontrolled rise in the pack.

Stringing and drip

Assess nozzle cut-off after normal running and after a realistic pause.

Pieces and herbs

Measure the largest firm inclusions and long fibres, not only average particle size.

Choose the pack before finalising the filling machine

Container opening, stability, closure, sealing surface and decoration determine how the product can be presented, filled and transferred. Use commercial samples from the intended supplier and include dimensional variation in the trial.

Pack routeApplication considerations
Squeeze bottlesNeed controlled neck entry, bottle stability, fill height and recovery after gripping or conveyor pressure.
Glass jarsSuit premium or particulate sauces; wide mouths can improve piece passage and filling access.
Pots and tubsRequire positive support and a clean rim for foil, film or snap-lid sealing.
Pouches and sachetsNeed accurate presentation, seal-zone protection and controlled handling while the flexible pack changes shape.

Build the machine route from product feed to finished pack

01

Feed and holding

Set hopper size, level control, agitation and transfer method around separation, heat loss and refill frequency.

02

Filling principle

Compare gravity, pressure, piston, servo piston or pump routes only against representative sauce and packs.

03

Nozzle strategy

Select bore, anti-drip method and fill movement to control splash, foam, strings and wall coating.

04

Container handling

Check unstable bottles, shaped jars, flexible pouches and wide-mouth pots at every transfer.

05

Downstream timing

Allow product settling, closure application, surface conditioning and code or label readiness.

06

Line balance

Size the capper, sealer, labeller, coder and end-of-line equipment for sustained—not headline—output.

Closing, sealing, labelling and coding are part of the same acceptance test

The closure route depends on the pack and product condition. Screw caps, flip-tops, pumps, twist-off lids, foils, snap lids and pouch seals all need clean contact areas and measurable verification. Plan cap or lid feeding, application, torque or seal checks, reject handling and changeover from the outset.

Scale automation from weekly demand—not headline speed

Convert saleable weekly demand into available production minutes, then allow for warm-up, replenishment, cleaning, changeovers, inspection, rejects and operator tasks. Desktop, compact, two-head and multi-head systems are planning bands rather than guaranteed capacities.

Lower volume

Desktop or semi-automatic

Manual pack presentation with assisted filling, capping or labelling. Prioritise flexibility and manageable cleaning.

Growing production

Compact or two-head line

Coordinated conveyor stages, repeatable presentation and selected automatic feeding or closing.

Higher sustained output

Multi-head automatic line

Integrated container, closure, inspection and end-of-line handling with a defined acceptance run.

Representative trial checklist

Use the most difficult normal combinations—not only an ideal batch and pack.

  • Thinnest and thickest normal sauce formulations.
  • Minimum and maximum product temperature.
  • Foaming or aeration after normal transfer and mixing.
  • Largest inclusion, seed, herb or fibre loading.
  • Smallest neck and most unstable container.
  • Nozzle cut-off before and after a pause.
  • Closure or seal integrity and product-free contact surfaces.
  • Sustained run including replenishment, cleaning and changeover.

Common questions

The choice may include gravity, piston, servo piston or pump-based filling depending on viscosity, foam, pieces, temperature, dose, pack and output. Trials with representative sauce are required.

Use a nozzle and shut-off arrangement matched to the product, stable container positioning and a fill profile that controls splash and strings. Pause-and-restart testing is important.

Possibly, but guides, sensors, nozzles, closure equipment, label handling and changeover time must be reviewed for every format.

Start with saleable weekly demand and real production hours, then include warm-up, cleaning, product and cap replenishment, changeovers, inspection and expected line losses.

Related equipment and buyer guides

Continue from the application into a more specific filling, capping or line-architecture decision.

Specialist sauce filling decisions

Move from the general filling comparison to temperature, hygiene and budget-specific guides.

Continue planning the production route

Turn your product and pack into a testable production route.

Share representative product, containers, closures, labels and your required output. Define the operating window and agree what a successful trial must demonstrate.

CallStart a project