Inspecting sortation shoes before they fail: the failure nobody actually inspects for
Here's the thing most shoe-inspection advice gets wrong: sortation shoes rarely fail on their own. They get destroyed by something else — a jam, a crash — happening nearby. So the real question isn't "are my shoes worn?" It's "what's about to take a row of them out?"
Watch a routine jam take out a row of shoes
Overhead view of a sliding-shoe sorter — flow runs left to right. Every slat carries its own shoe, riding the home rail continuously; at the divert point a group of them slides across the slats as a diagonal wall and pushes the package into the spur. Step through the four stages of the failure the controls never see.
Stage 1 — Normal divert
Package reaches the divert point, a diagonal line of shoes slides across the bed, and the package peels cleanly into the spur. This happens thousands of times an hour.The shoes are built for the pushing. What they're not built for is what comes next.
Illustration of the failure sequence — not to scale. Follow your facility's energy-control (LOTO) policy before any hands-on work.
Get the free PM checklistIf you went looking for a shoe inspection checklist, you'd find plenty of "look for cracks and wear" lists. They're not wrong, but they miss the point. In real high-volume operation, shoes don't quietly wear to the end of their life and retire. They're collateral damage. Catch the events that damage them, and you've solved the shoe problem at its source.
01The premise shift: shoes are collateral damage
A sliding-shoe sorter moves shoes across slats to divert product into chutes and spurs. The shoes themselves are robust — they're built to push thousands of cartons an hour. What kills them isn't the pushing. It's impact: a shoe meeting something it was never meant to hit. A package stuck where it shouldn't be. A crash. That's the failure mode worth inspecting for, because it's the one that takes out shoes by the dozen, not one at a time.
02Two failure modes — and only one warns you
Across the shoe-sorter platforms I've worked on, shoe damage shows up two different ways — and the critical difference is whether the machine tells you it happened.
🔇 The silent one: cracked shoe bodies
A package jams in a chute. Shoes that have diverted keep coming down the line and slam into the stuck package or jam area. They crack or break — and there's no machine alarm for it. The damage accumulates quietly until someone inspects and finds the count.
🔔 The announced one: damaged pin
On other shoe designs, a crash bends the pin underneath the shoe. The sorter detects the out-of-place pin — a "missing pin" condition — and stops itself. The machine refuses to keep running, so the damage is contained.
That split is the whole article. One failure mode hands you a stopped sorter and a clear signal; the other gives you nothing but a slowly climbing pile of cracked shoes you won't see until you look. Industry maintenance writing draws the same line: a fault that stops the machine generates a work order and gets fixed, while a failure that doesn't announce itself degrades quietly until someone connects the dots.
03The "missing pin" alarm that keeps coming back
The announced failure mode has a tell worth knowing, because it confuses people. When a bent or displaced pin trips the detection and stops the sorter, the natural move is to restart. But the sorter stops again — and gives another missing-pin alarm.
That's not a broken detector. The displaced pin has advanced to the next detection point and re-alarmed there. The repeating, marching alarm is itself the diagnosis: it's telling you a damaged pin is moving through the system. Follow the alarm to the pin, rather than assuming the detection is faulty and trying to override it.
04The blind spot that creates the silent damage
Here's why the silent failure mode exists at all — and it's the most useful thing in this article. A sorter has a chute-full photo eye that's supposed to stop diverts when a chute backs up. The problem: if boxes jam before they reach that photo eye, the eye never trips. The sorter thinks the chute is clear and keeps diverting into a jam that, as far as the controls are concerned, doesn't exist.
Those boxes hang out past the chute opening, and oncoming shoes hammer them. That's the exact scenario that cracks shoes by the dozen — and the machine never said a word.
05The real prevention is a person, not a sensor
For the silent failure mode, the entire early-warning system is a human walking the sorters. That's not a backup to the photo eye — it's coverage for the gap the photo eye structurally can't see. A green operator assumes "the photo eye handles jams." Someone who knows the machine understands the eye handles one kind of jam, and puts eyes on the other kind.
What that walker is watching for: boxes diverting into a chute that has no room, product hanging out past the chute opening, and a jam forming upstream of the chute-full eye. The same walk also keeps packages from recirculating unnecessarily, so it pays for itself twice.
06The response hierarchy when a jam is forming
When the walker spots a jam starting, the response follows the same downtime-vs-cost logic that runs through every good maintenance call:
- Clear it fast with a jam pole. Operations doesn't want an unnecessary stop, so the first move is to clear the jam without stopping the sorter — if it can be done safely from the pole.
- LOTO If the pole can't reach it, stop the system and clear it safely. When you can't clear it clean, the stop is worth it — a shoe-cracking event costs far more than the downtime. De-energize and follow your facility's energy-control policy before anyone reaches into the equipment.
- Inspect the area after a real event. If shoes took impact, that's when you find and replace the cracked ones — before they cause missorts or secondary jams.
The scale is the reason this matters
A routine event might damage a handful of shoes — three to five. A genuine crash is a different universe: dozens of shoes at once, and on a bad one, into the hundreds. That's the line between a quick fix and a half-day rebuild. It's also why catching a jam before it escalates isn't fussiness — it's the difference between replacing five shoes and replacing sixty.
07By the book vs. on the floor
By the book
Inspect shoes on a schedule for cracks, chips, wear, and free movement; verify shoes nest properly and don't bind; check pin tracks and confirm detection systems (missing-pin, missing-shoe-top) are functioning. Follow the manufacturer's inspection points and replacement intervals.
On the floor
Scheduled shoe inspection still matters — but the bigger payoff is event-driven: inspect hard after any jam or crash, because that's when damage actually happens. Staff a walker to catch the jams the controls can't see. Prevent the event and you prevent most of the shoe failures.
Neither replaces the other. The scheduled inspection catches the occasional shoe that's genuinely worn or was missed after an event. The event-driven mindset catches the dozens that fail all at once. If you only do the calendar inspection and skip the walker, you'll keep finding cracked shoes by the hundred and wondering why your "PM program" didn't catch them — because they didn't fail on a schedule; they failed in an instant.
08The takeaway for your floor
Inspect for the event, not just the shoe:
Shoes don't wear out on a schedule — they get cracked and bent by events the machine sometimes can't even see. Inspect after every jam and crash, staff the line so jams get caught before they escalate, and follow the alarm when the machine does talk to you. That's how you keep a five-shoe problem from becoming a sixty-shoe rebuild.
Build an inspection routine that catches damage early
Grab the free conveyor PM checklist — daily, monthly, and annual inspections.
Almost there — check your inbox
Click the confirmation link we just sent, and the checklist is yours. If it isn't there in a minute, check your junk folder.