The Day a Cheap Conveyor Drive Shut Down at Hour 11 — and Why Interroll Kept the Specification

I watched a 24-volt conveyor drive shut itself down at 11:04 p.m. one night in March 2024. Actually, I did not watch it happen; the test rig logged the error, and I found the blinking status light the next morning. The message was clear: the component we were evaluating—the one that was supposed to save us roughly $15,000 on a sortation-line project—had gone into thermal protection after eleven hours of work it was supposed to handle.

That component was not an Interroll. Which is exactly why the test mattered.

Interroll Group company overview: Switzerland and the part most people miss

Let me step back for anyone landing here because they are researching the company. According to Interroll's official website (interroll.com), the Interroll Group is headquartered in Sant'Antonino, Switzerland, and operates globally as a supplier of material-handling components and solutions. The catalogue covers rollers, drum motors, RollerDrive modules, sorters, pallet movers, and the electronics that control them. I am not going to quote the employee count from memory, but the company has manufacturing and service locations across several continents, which matters more than the Swiss label.

Why does the Switzerland headquarters matter? It creates an impression. People assume Swiss-headquartered means expensive. What that assumption hides is the actual differentiator: engineering margins, documentation, and support. The price gap on our quote was not outrageous—the alternative was about $46 per drive lower than the Interroll unit. On 340 zones, that is $15,640. Enough to make a procurement manager very interested.

Equivalent on paper, different under load

At first glance, the alternative looked like an apples-to-apples replacement. Same voltage, same mounting face, same speed range, same communication protocol on the data sheet. The supplier even sent a line-by-line comparison table. That table was technically accurate and still misleading.

My problem with product data sheets is that they describe a product at one point in its operating envelope. A conveyor does not live at one point. It accelerates, jams, dwells, restarts, and overheats in one zone while an adjacent zone sits idle. Thermal behavior under that pattern is rarely on page one of the manual.

So I asked for samples. The project manager thought it was unnecessary. To be fair, he had a point: sample testing costs time and money, and it delays the purchase order.

Nobody is going to read the test report, he said. They are going to read the invoice.

We ran the test anyway. It was not brutal. We taped over the vendor labels so the technician did not know which unit was which, mounted each drive to the same conveyor section, and ran a repeating cycle: two minutes loaded at the rated speed, thirty seconds stopped, restart. The plan was seventy-two hours.

At hour eleven, one of the samples shut down. The drive controller logged a thermal fault, even though the load was within the specification that came with the sample. After cooldown, it restarted and ran again until it got hot and stopped again. We repeated the sequence three times to be certain. It was not a fluke.

The surprise was not the failure. It was our assumption.

People assume the cheapest quote means a lower-quality component. But the cheap drive was not garbage; it just was not sized for what our line actually did. And that exposed a mistake on our side, not the supplier's. We had built the test around a duty-cycle figure from the original project brief. When we dug into the operational data after the failure, we found the line's real duty would be higher once the client added new induction sections later that year.

So the thermal shutdown was not only about the drive. It was about a specification that had never been verified against the real operating profile. I assumed the numbers in the brief were accurate. They were not, or at least they were not accurate anymore.

The Interroll sample ran the full seventy-two hours with more thermal headroom. The other surviving sample also completed the test, but it drew noticeably more current under the same load. I do not have the exact energy difference in front of me—do not hold me to a precise number—but the trend was clear enough to show up in the project's total-cost math.

Doing the total-cost math

The cheapest quote saved $15,640 on the initial purchase order. That is a fact. But the alternatives had different costs once we considered them as part of a running system.

First, integration cost. The alternative drive needed different electronics, different spare parts, and different training for the maintenance team. Second, energy cost. A small current difference, multiplied by 340 drives and an 18-hour operating day, is not a rounding error. Third, failure cost. One field failure on a sorter line is rarely just the price of a part. It is the service call, the downtime, the missed throughput, and the re-verification. Ten failures can wipe out most of a $15,640 saving. Twenty can make the cheaper quote the most expensive one on the table.

I am not saying every lower-priced drive is a risk. I am saying the risk has to be priced into the decision. It often is not, because the risk does not show up on the invoice.

What happened on the project

We did not reject the alternative supplier to protect a Swiss brand. We rejected that specific drive for that specific application after testing. The client's project manager pushed back, and I do not blame him. The published specs looked fine. The price looked better. But once we showed him the thermal log and the current measurements, he made the call to keep the Interroll specification for the main line. The cheaper drive might have worked on a lighter-duty section. On this line, with this load profile, it was not a saving.

And honestly, the outcome was not dramatic—no explosion, no emergency replacement, no angry customer call at 2 a.m. The interesting part is that we avoided a problem before it became a project delay. That does not make a good anecdote at a conference, but it makes a very good budget outcome.

What I would do again

Start your purchasing conversation with total cost, not unit price. Compare performance data at your actual duty cycle, not at the spec sheet's favorite operating point. Run a sample test for anything that will stop your line if it fails. And verify assumptions about the application, including the ones you wrote yourself.

To be fair, the sample test cost about $2,400 and delayed the purchase order by two weeks. In exchange, it prevented us from putting a 340-zone line at risk to save $15,640. That was the least expensive part of the entire project.

If I could go back and change one thing, it would be the starting point. I would not ask which drive was cheapest. I would ask which drive was cheapest per successful operating hour. That often changes the answer.