Blog / Downtime
Downtime · Guide

Conveyor Short Stops: Jams, Tipping and Gaps

OL By OEE Lab Editorial |Updated 2 November 2026 |6 min read
Short answer

Conveyor short stops usually come from three events at transfers and merges: jams, tipped products and gaps in the flow. Tally them by location for one shift, check speed ratios and transfer height there, and fix the spot that costs the most minutes, which may differ from the one that stops most often.

Three faults, three different causes

Operators often call all of these "a jam". They have different causes and need different fixes, so give each one a name on your tally sheet.

EventWhat you seeLikely causesCheck first
JamProducts wedge at a merge, guide or infeedToo much back pressure, narrow guides, damaged packsGuide width against the product, accumulation pressure
TipBottle or pack falls and blocks the flowSudden speed change, step at the transfer, unstable productSpeed ratio, transfer height, dead plate length
GapMachine waits or trips because spacing is wrongSpeed mismatch, poor metering, slow restartSpeed settings, sensor positions, timing
Name the event first. Many stops logged as a jam turn out to be tips.

This page covers short, repeat flow stops. For belts that slip, mistrack or break, use conveyor troubleshooting.

Count them for one shift

Walk the line with a sheet that lists each transfer as a row and jam, tip and gap as columns. Then add the average clear time for each event type, using a stopwatch.

Example: a bottling line records 60 stops in one shift.

Jams: 18 x 45 s13.5 min
Tips: 28 x 20 s9.3 min
Gap trips: 14 x 15 s3.5 min
Hypothetical shift, 26.3 minutes in total. Tips are the most frequent, but jams cost the most.

The count points at tips, while the minutes point at jams. Then split the same sheet by location, because that is what turns a loss into a project.

LocationJams (45 s)Tips (20 s)Gaps (15 s)StopsLost
Depalletizer to filler43815360 s
Filler to labeller merge104115545 s
Labeller to packer219324515 s
Packer infeed2226160 s
Total182814601,580 s = 26.3 min
Same hypothetical shift. The busiest spot for stops is not the one that loses the most time.

Here the merge has 10 of the 18 jams and the largest loss, while the labeller transfer has 19 of the 28 tips. Those are two small projects with two different fixes, and neither needs a line-wide program.

Clear time is only part of it. A line that takes a long time to get back to speed after each stop loses more, so include the restart in your stopwatch time.

Check your spacing with a formula

Many gaps and tips start with speeds that were set by feel. The number that links them is pitch: the distance from the front of one product to the front of the next.

Pitch = conveyor speed / product rate
30,000 mm/min / 300 bottles/min = 100 mm
Gap = 100 mm - 60 mm bottle = 40 mm
Hypothetical single-file conveyor. Run this for each section, using measured speed and rate.

Each step in speed changes the pitch, and a big step at a transfer is a common reason for bottles to tip. If the next section is 20% faster, at 36 metres a minute, pitch grows to 120 mm with the same 300 bottles a minute.

Moving from a faster section to a slower one closes the gaps and raises pressure, so check this where jams repeat. Measure real belt speed with a tachometer, since drive settings do not always match it.

What usually fixes each one

Jams

  • Set guides to the product width plus a small, agreed clearance, and mark settings for each size.
  • Reduce pressure in accumulation by slowing or stopping sections earlier.
  • Check merges for a narrowing that is too sharp for the rate.
  • Look for damaged packs arriving from upstream, as the fix might be at the source.

Tips

  • Check the height of each transfer and each dead plate with a straight edge.
  • Ramp speeds gently from section to section, instead of one big step.
  • Check for wet, worn or over-lubricated patches on the belt.
  • Soften starts and stops, because hard starts tip tall, light products.

Gaps

  • Check that the accumulation sensors control speed in the right order.
  • Give the infeed a steady supply, and let buffers fill before the machine restarts.
  • Look upstream, as gaps often come from false sensor trips or repeated stops on a previous machine.

How buffers change the math

A buffer between machines keeps short stops from spreading along the line. A quick calculation shows how much cover you have.

Example: 18 metres of single-file conveyor holds 300 bottles of 60 mm diameter, and the line runs 300 bottles a minute. When full, that is one minute of cover for the machine after it, if the machine before it stops.

The other direction is usually much shorter. At the 100 mm pitch above, the same conveyor holds 180 bottles while running, so it has room for 120 more, which is 24 seconds of cover if the machine after it stops.

A buffer only works if it has room or stock when needed. After a stop, the machines need spare speed to refill or empty it, and the V graph shows how speeds are usually set around the key machine.

Start with stops around the bottleneck, since those cost line output directly. Bottleneck analysis helps you find it, and upstream and downstream stops shows who owns the minutes.

Availability or performance?

Whether a short stop lands in availability or performance depends on your threshold. Pick one with stop threshold in OEE, then keep it fixed so that trends remain valid.

Unlogged stops are not lost from OEE, because they still lower the output count. They just fall into performance as unexplained loss, as minor stops vs breakdowns explains.

Where conveyor projects go wrong

  • Running faster to make up time. Higher speed can bring more jams and tips, and output may fall as a result.
  • Fixing the first thing an operator mentions. Tally a full shift first, as the worst spot is often not the loudest one.
  • Logging everything as "conveyor". Use the transfer name and event type, as in your reason codes.
  • Treating all sizes as equal. One bottle size may cause most of the tips, so split the tally by product.
  • Leaving out the guide settings at changeover. A guide left set for the last product can cause a shift of jams.

Run the tally twice

Run one tally shift, then repeat it on another shift to check the pattern holds. Pick one transfer, change one thing, and run the tally again.

For wider work on short stops across all machines, read how to reduce micro-stops. If packaging machines at the end of the line add to the problem, packaging line troubleshooting covers them.

See it live in Fabrico

Jams, tips and gaps clear in seconds, so a hand tally can only ever sample them. Where cameras are fitted, Fabrico shows video of each stop, streamed on request next to its machine data, and OEE per line and shift shows the cost. See how Fabrico uses cameras for OEE.

What people ask next

Why do bottles tip at conveyor transfers?

The usual causes are a sudden speed change, a height step at the transfer, a long dead plate, or wet patches on the belt. Check the transfer with a straight edge, and measure both belt speeds. Tall and light products are the most sensitive.

How do I calculate spacing on a conveyor?

Divide conveyor speed by product rate to get pitch, then subtract the product length for the gap. At 30 metres a minute and 300 bottles a minute, pitch is 100 mm. Use measured speeds, not drive settings.

Should conveyor short stops count as availability or performance?

It depends on your stop threshold. Stops above it go to availability, and those below it go to performance. Stop threshold in OEE shows how to set it.

Are conveyor jams a maintenance problem or an operations problem?

Often both. Settings like guide width and speed sit with operations, and wear, height and drives sit with maintenance. Tally by location first, then assign an owner per transfer.

How much buffer do I need between machines?

Enough to ride through your common short stops, with spare speed to recover afterward. Compare your buffer minutes with your stop lengths. Mean time between stops gives you the data to judge it.

See OEE per line and shift on your own machines

Fabrico is a light MES for OEE. It takes stops, speed and counts from PLCs or IoT sensors, with add-on AI cameras counting output where a machine has no usable signal, and operators tag the cause at the line.

Book a Fabrico demo

← More OEE Lab guides · How to reduce micro-stops →

OEE essentials: OEE calculator · What is OEE · Six big losses · Availability · TEEP · Cost of downtime · OEE benchmark · Free OEE tracker · Free OEE software · How to track downtime · How to implement OEE · Light MES vs full MES