Blog · Reliability engineering

When your conveyor stops being the forgiving part of the system

Conveyors usually give you options — reroute, buffer, work around a jam. Tighten the layout enough to remove that redundancy, and a single jam starts behaving exactly like a stalled shuttle.

19 September 2026 6 min read

Most conveyor and sortation systems are, by design, forgiving. A jam on one branch gets rerouted around, a stopped zone gets bypassed, and the rest of the line keeps moving while someone clears the fault. That forgiveness is a property of the layout, not the equipment — and it's the first thing that disappears when a facility tightens its footprint to fit more automation into the same building.

Remove the alternate paths and a single jam stops behaving like an inconvenience and starts behaving exactly like a stalled shuttle: everything behind it is stranded until someone physically intervenes.

Where the redundancy actually lives — or does not

A conveyor network with multiple paths can automatically route around an inoperable section, which is the entire reason multi-path sortation architectures spread the way they have — the system absorbs a local failure without anyone noticing downstream. A single-line layout has no such option: it fails the way it was drawn, along its one path, for as long as it takes to clear.

STIQ's 2026 goods-to-person research tracks the industry pushing toward denser fulfilment layouts — more automated assets and more SKUs per square metre than five years ago. Density and redundancy pull in opposite directions: the more tightly a layout is packed, the fewer alternate paths there's physical room for, and the more a single-line design becomes the default rather than a deliberate choice.

Merge points are where it actually goes wrong

Per the Material Handling Institute's breakdown of conveyor jam causes, three failure patterns account for most stoppages, and merge points — where outlet conveyors feed into the main line — fail specifically on timing: when the control system sends packages into the merge at the same moment as packages already on the main line, they collide, at exactly the point where the most traffic converges.

  • Overloading — package volume exceeding what the line was sized for, building up until something jams.
  • Out-of-spec products — oversized items get stuck, undersized ones fall through gaps sized for a different profile.
  • Merge-point timing failures — outlet conveyors feeding into the main line at the same moment as existing traffic, colliding at the point where the most paths converge.
3the jam causes that account for most conveyor stoppages, per the Material Handling Institute — overloading, out-of-spec products and merge-point timing failures

Designing for it, and catching it before it happens

MHI's guidance treats this as a layout decision made before startup, not a fix applied after: jam-clearing procedures, empty zones and restart sequences defined in the design, and — where the footprint allows it — zero-pressure accumulation, spacing product at predictable time and distance intervals rather than letting it pack tight against itself. None of that is available to bolt on once a tight single-line layout is already built.

Where the physical redundancy isn't there, the only remaining lever is catching the jam before it happens rather than after. Motor current draw and temperature climb before a jam fully forms — the same signal that flags a bearing wearing out flags a merge point about to back up — which turns a stoppage nobody saw coming into a work order raised while the line is still running.

How we approach it

Condition monitoring doesn't distinguish between a bearing failure and an approaching jam — both show up as the same kind of drift in motor current and temperature, read off the PLC and SCADA telemetry the conveyor system already produces. We watch for that drift and raise a work order before the merge point locks up, which matters more, not less, on a single-line layout with nowhere for the fault to reroute to.

That sits alongside a PM schedule built from the actual OEM manual for that specific line. The redundancy a layout doesn't have has to be made up for somewhere, and a preventive schedule that genuinely matches the manufacturer's spec, checked against real telemetry, is the only place left to find it.

Ready to put this into practice?

Upload an OEM manual and see the PM schedule it builds — or open the live demo, no signup required.

We use essential cookies to run this site. With your consent, we also load Google Analytics to measure site usage, and Calendly's own cookies if you open our booking widget. See our Cookie Policy for details.