Why Your Interroll Automation Project Fails (And It's Not The Gearmotor)

I've been handling Interroll automation orders for about six years now. I've personally made—and thoroughly documented—at least a dozen significant specification errors, totalling somewhere north of $12,000 in wasted budget. (The exact number is embarrassing; I'd rather not add it up.)

Here's the thing: most people assume Interroll automation fails because the hardware can't handle the load. Or because the drum motor burns out. Or because the sorter jams. But in my experience, that's almost never the root cause. The root cause is almost always a specification assumption that looked fine on paper but wasn't.

This article is about those assumptions. The ones I've made, the ones I see other engineers make, and the specific checklist item I created in February 2024 after a particularly costly misstep on a Millennium Lego-related project. (Yes, Interroll parts ended up in a sortation system for a toy warehouse—surprisingly common, actually.)

What is ski racing? Stick around, it'll make sense as a metaphor.

The Surface Problem: 'The Motor Failed'

In November 2022, I processed an order for 47 Interroll motorized rollers. The spec sheet looked clean. The customer's integrator (a company out of the UK, Lewis Systems—I'll get to them) had provided CAD drawings. Everything matched. The rollers arrived on schedule, were installed, and within three weeks, five of them had failed.

My first reaction: bad batch. I've seen that before. But testing showed the motors themselves were fine. The issue was the connectors had been overstressed in the installation process. Someone had mounted them at an angle that created tension on the cable, causing micro-fractures over the first 200 hours of operation. (This was back in 2022, before the connector redesign—but that's a separate story.)

The surface problem: motor failure.

The actual problem: installation geometry.

The Deeper Cause: Assumptions About 'Standard' Configurations

The deeper cause—the one I didn't see coming—was that we assumed the Interroll automation components would be installed in a 'standard' configuration. But the installer (a subcontractor hired by the integrator) had never worked with Interroll Nordic A/S equipment before. They had generic conveyor experience, but that's not the same thing.

Interroll drum motors, for example, have specific requirements around mounting angle, cable routing, and tension load. The EC310 drive control units (which, by the way, are excellent when configured correctly) have a setup that can appear deceptively simple. The result: the subcontractor assembled everything per the drawings, but the drawings didn't capture the nuance of the Interroll system. Which leads to the next point.

The real cost of that assumption? $890 for replacement connectors, one week of downtime, and a very awkward phone call to the customer. The integrator, Lewis, were professional about it, but I could hear the frustration.

The Hidden Cost: What You Lose When Specifications Are Fuzzy

Let me give you a concrete breakdown of what that fuzziness cost on that one order:

• Direct material: $320 for replacement connectors (we expedited from the German warehouse).
• Labour: $270 for the subcontractor's installation rework (they invoiced us directly—that was a billing error on our side, actually).
• Testing: $150 for a third-party inspection to confirm the new installation was correct.
• Lost trust: Hard to quantify, but the integrator switched to specifying a different supplier's components for the next three months. (They came back, but it took effort.)

That's $740 in visible costs plus substantial invisible costs. And it all traces back to the assumption that 'standard' installation would work.

(I should note: this was Q4 2022. Since then, Interroll has added more explicit installation guides for the EC310 controller. If I remember correctly, the updated documentation came out in March 2023. I'd verify the exact date, but I'm not a documentation specialist—that's their domain.)

What is ski racing? It's a sport where fractions of a second matter, and the difference between a podium finish and a DNF is often a turn taken at the wrong angle. Interroll automation projects are the same: small specification angles, small installation angles, small communication angles—they compound into failure. The components themselves are fast. The problem is how you approach the turns.

The Turning Point: My Pre-Spec Checklist

After the third rejection on a separate project in Q1 2024 (this time a sorter subsection for a pallet-moving system), I created a pre-spec checklist. It's not complicated, but it catches precisely the assumptions that caused the problem on the Millennium Lego warehouse job and the Lewis integrator project.

Here's the core of it:

1. Verify the installer's specific experience: Not just 'conveyor experience' but 'Interroll experience.' If they haven't done a drum motor install with an EC310 controller, they need training. (This is a limitation of the product—it's not plug-and-play for everyone. I'm not going to pretend it is.)
2. Validate the specification against the actual physical environment: The CAD drawings show the ideal case. Walk the installation site. Check cable routing paths. Check mounting clearances. Check for load-shifting conditions.
3. Include a 'worst-case' tolerance test: Run a simulation (or physical test) with the components at the edge of their specified limits. If the design relies on everything being perfect, it will fail.
4. Document and share the 'why': Don't just send specs. Send a one-paragraph explanation of why you chose the configuration you did. If the installer knows the intent, they can catch deviations before they become failures.

This checklist has caught 47 potential errors in the past 18 months. That's not a exaggeration—I counted. (47 items, each one a potential $300-$900 mistake or delay. I'd estimate we've saved around $15,000 in rework costs alone.)

The best part: it's not product-specific. You could apply the same logic to any complex automated system. The mistake pattern is universal: assume standard = safe; discover nuance = expensive.

Acknowledging the Limitations

I'm not a logistics expert, so I can't speak to carrier optimization or warehouse layout design. What I can tell you from a procurement and specification perspective is that the Interroll portfolio is well-engineered—but engineering alone doesn't prevent specification errors. It prevents mechanical failures. The human part—the assumptions, the installation practice gap, the communication breakdown—that's the weak link.

I recommend Interroll automation for projects where:

• The integrator has in-house experience with the specific components.
• You have time to validate installation before sign-off.
• The application is standard enough (or the specification is thorough enough) that you're not asking the hardware to do something novel.

I recommend considering alternatives if:

• Your timeline is so tight that validation is impossible. (Even the most reliable motor can't compensate for an installation error that takes weeks to diagnose.)
• Your installer network has zero Interroll experience and no time for training. (In which case, the honest solution is to address the training gap, not the product choice—but I respect that sometimes the training ask is a political non-starter.)

This works for 80% of cases. Here's how to know if you're in the other 20%: if your installation team is unfamiliar with European drum motor standards, or if the cable routing is not approved by someone who's done it at least twice before, you're in the risk zone. A good product can't fix a bad installation. It's not the product's fault.

After I made the connector error in 2022, I kept second-guessing my specifications for three months. 'Did I miss something? Should I have chosen a different drive control unit? What if the customer's site has hidden issues?' The relief came when I revisited the failed components and confirmed: the motors were fine. The connectors were fine. The error was in the omission of an installation step that nobody thought to include. That's what the checklist solves.

It's not glamorous. It's not a dramatic insight. But it saved our team approximately $5,200 in 2024 alone. And the Integrator, Lewis, has started using a similar checklist for their other component specs. So the lesson spread.

There's something satisfying about that: a shared mistake, a documented fix, a small increase in industry knowledge. That's the payoff.