Warehouse automation

Sortation System Specification Guide: 3 Specs That Predict Year-3 Survival

Jane Smith

Most sortation system specification guides are written for procurement committees, not for the people who have to maintain the system at 2 a.m. when a divert fails during peak. If you're choosing a system under deadline pressure, three specs predict long-term cost better than any throughput number: WCS integration depth, maintenance access design, and true landed cost per diverted parcel. Everything else in the bid packet is secondary until you've verified those three.

I say that as someone who has watched a "cheap" sorter eat an entire peak season's margin. Not because the equipment was bad—because the specification guide it was chosen from measured the wrong things.

Why take this from me

I coordinate automation projects for a third-party logistics operator. Over the past four years I've been involved in 11 sortation deployments. Six of them ran under compressed timelines—including two where the original integrator walked off site mid-commissioning and we had 10 days to get a line running before peak.

I've also been on the receiving end of three emergency retrofits where a system chosen on unit price failed under real volume. One of those cost us $47,000 in overtime labor and a $22,000 penalty clause we barely negotiated down. That's when I stopped trusting specification guides written by people who'd never touched a divert.

The three specs that actually matter

1. WCS integration depth (this is where the Vanderlande WCS programming language question comes from)

Every buyer eventually asks some version of: what programming language does the Vanderlande WCS run on, and can my team support it? It's the right instinct—wrong framing. The language itself matters less than what happens at the integration layer when something fails.

Industrial control stacks tend to sit on IEC 61131-3 for the PLC layer, often with a C# or .NET supervisory layer above it. Vanderlande's architecture follows that pattern in the deployments I've seen—their WCS and Vanderlande conveyor and sortation controls share a common stack, which is why their belt, roller, and telescopic conveyor lines commission faster than mixed-vendor setups. In one of our compressed projects, that shared control architecture cut integration testing from a planned three weeks to nine working days.

Here's the specification question that actually matters: "If your WCS field engineer is 14 hours away and a sortation divert is throwing faults, what's the remote diagnostic path?" If the answer involves a proprietary debugger only their team can run, you've just bought yourself a dependency, not a system.

2. Maintenance access design

This one never appears in a specification guide and it should. Ask to see the maintenance access plan—not the maintenance manual, the physical access plan. Can a technician reach a shoe sorter's divert mechanism without removing three guarding panels? Is there a walkway wide enough to carry a replacement motor?

We learned this the hard way. On a cross-belt sorter installed in 2023, replacing a single worn belt required two technicians and a scissor lift because the design assumed access from one side only. The belt itself cost maybe $400. The labor and downtime cost roughly $3,200 per incident. Over a year, that design choice added more to TCO than the initial equipment discount we'd negotiated.

3. True landed cost per diverted parcel

This is where the total-cost-of-ownership argument actually lands. Unit price per sorter is meaningless without four additions: installation and commissioning labor, spare parts inventory you'll need to stock (ask what they recommend, then ask why), expected maintenance hours per 100,000 parcels, and the cost of a missed divert at your facility's penalty rate.

"The $180,000 sorter that needs a $40,000 spare-parts stock and 12 maintenance hours a month is not cheaper than the $240,000 sorter that needs $8,000 in spares and 4 hours."

That's not a hypothetical. I've seen those two numbers side by side in the same bid comparison. The first bid looked 25% cheaper on the spreadsheet.

The specs buyers over-index on (and regret)

Four things eat up specification-guide space and predict almost nothing about year-three performance:

  • Nominal throughput. Anyone can hit nominal throughput in a demo with perfect parcel spacing. Ask for throughput at your actual parcel mix, with your actual gap distribution.
  • Peak speed. Peak speed is a marketing number. Sustained speed under your load profile is the operating number.
  • "99.9% sortation accuracy." Ask for the definition. 99.9% of what—parcels, reads, diverts? And under what induction quality?
  • Floor space footprint. A smaller footprint often means tighter maintenance access. You're trading maintenance labor for real estate.

Where the wholesale and OEM questions fit

A lot of buyers arrive at this search looking for sortation wholesale or a sorter OEM direct relationship. That's a legitimate strategy for replacement parts, conveyor sections, and commodity components—you can absolutely source conveyor belting or roller sections without going through a full system integrator.

For a complete sortation line, it usually breaks the TCO model. You save the integrator margin and inherit the integration risk. In my experience, the buyers who go OEM-direct on a full line end up paying an integrator later to fix the handoffs—at emergency rates. The margin comes back, plus a premium.

If you're sourcing components, by the way, verify against ANSI/ASME B20.1 for conveyor safety and EN 619 if your facility ships to or operates in the EU. These aren't optional references—they're the baseline any serious supplier should already be building to.

What I can't tell you

My experience is based on about a dozen mid-size deployments—roughly 15,000 to 60,000 parcels a day. If you're specifying a system for an airport baggage handling operation or a million-parcel-a-day fulfillment center, my frame of reference doesn't stretch that far. The principles probably hold. The specific numbers won't.

And honestly, I'm not sure why some integrators quote WCS customization as a fixed line item while others treat it as open-ended. My best guess is it comes down to how much of their control stack is genuinely productized versus project-built. Ask them which parts of the WCS are configuration and which are custom code. The ratio tells you a lot about your integration risk.

One more thing—the specification guide you're working from almost certainly has a page on "future scalability." Skip it until you've verified maintenance access and the remote diagnostic path. Scalability is a nice-to-have. Access is what determines whether your system survives year three.

Share WhatsApp
Jane Smith
Jane Smith

I’m Jane Smith, a senior content writer with over 15 years of experience in the packaging and printing industry. I specialize in writing about the latest trends, technologies, and best practices in packaging design, sustainability, and printing techniques. My goal is to help businesses understand complex printing processes and design solutions that enhance both product packaging and brand visibility.