-
The Phone Call That Changed My Job Description
-
My First Mistake: Treating This Like a Copier Refresh
-
A Conversation Where We Used the Same Words and Meant Different Things
-
What the Vendors Actually Taught Me
-
The Moment I Almost Went with the Wrong Option
-
Where Swisslog Fit In
-
What I Look For in a WES Supplier Now
-
What a Mid-Sized Project Actually Needs
-
What I'd Tell Another Admin Buyer in My Position
The Phone Call That Changed My Job Description
In September 2024, my VP walked past my desk and asked if I had 20 minutes. It was 4:45 on a Thursday. Twenty minutes turned into an hour, and by the end of it I had a new side project: help screen vendors for our distribution center expansion.
For context: I'm the office administrator for a 220-person company. I manage procurement across 14 vendors—office supplies, facilities, the occasional furniture refresh—about $1.2 million annually. I'm good at it. What I am not is a warehouse person.
Still, I said yes. That's what you do.
My First Mistake: Treating This Like a Copier Refresh
My first move was the same move I make every time: build a spreadsheet. When we replaced our copiers in 2022, I compared 5 vendors on 6 columns and picked the winner in about a week. I assumed warehouse control systems would work the same way. More columns, sure, but the same idea.
I assumed "WES" and "WCS" and "WMS" were basically interchangeable labels for the same thing. Didn't verify. Turned out they refer to different layers of the software stack, each with different jobs, and the vendors who sell them use the words in ways that don't always line up. In the standard stack, the WMS handles order and inventory management, the WES handles workflow and orchestration, and the WCS handles equipment control. Some vendors blur the boundaries on purpose.
That mistake cost me about three weeks of confusing conversations.
A Conversation Where We Used the Same Words and Meant Different Things
Here's what happened next. I told our operations lead, "I'll get the specs from all the vendors and compare." She heard, "I'll evaluate technical fit and integration complexity." Result: she briefed the vendors on the assumption I was qualified to judge their system architecture.
I wasn't. I could read a spec sheet. I could not tell you whether a particular WCS handles high-density shuttle coordination the way our operation needed.
We discovered this at the wrong time—about five vendor calls in—when one of them asked me a follow-up question about "how our current WMS handles wave release." I said I'd get back to them. Then I googled "wave release" in my car.
A lesson learned the hard way.
What the Vendors Actually Taught Me
Once I dropped the act and started asking honest questions, the process got much more useful. I talked to a mix of warehouse control system manufacturers and WMS integration suppliers, including a few calls with the Swisslog team. What I picked up, roughly in order:
Not all WES platforms are built for the same operation. Some are designed around high-volume, standardized SKU flow. Others are built for more complex, mixed environments. If your operation is a hybrid—which ours is, and a lot of mid-sized ones are—the fit question is different from the spec-sheet question.
The "integration" line on the brochure means almost nothing on its own. Everyone says they integrate with your WMS. The real question is how much custom work that integration takes, and who absorbs that cost and risk. That's where the timeline actually lives.
Warehouse storage systems are not plug-and-play. When I started, I assumed a warehouse storage system was basically a big racking unit. A Swisslog ASRS, a competitive stacker crane, whatever the label—same category, different logo. Didn't verify. Turned out it's an integrated mechanical, software, and controls package, and the software side is where most of the variance between vendors actually lives.
If I remember correctly, it was around our eighth vendor call that I realized I'd been asking feature questions when I should have been asking workflow questions. That was a turning point.
The Moment I Almost Went with the Wrong Option
By November, I had a shortlist. The numbers said go with a mid-size integrator—about 15% lower on the capital line, with what looked like similar specs. My gut said something was off. Their responses to my follow-up questions were slow, and the answers were generic.
I went with my gut and kept looking.
Later, when I talked to operations contacts at two other companies who had used that integrator, I heard the same theme—fine on the install, slow on the post-go-live support. Not a disaster. Just a preview.
I want to be fair here: I don't have enough data to say that integrator is bad. But the pattern was real enough that I dropped them from the shortlist. Post-decision doubt followed anyway. For about two weeks, I kept second-guessing whether I'd over-weighted responsiveness.
Where Swisslog Fit In
Our project wasn't huge. We're a 220-person company expanding into a new DC; this was a real capital commitment for us, but it's not a multi-site enterprise rollout. In this market, that puts you in an odd spot—interesting enough to get meetings, small enough that you worry about getting the B-team.
What stood out on the Swisslog calls: they took the sizing conversation seriously. Not in a "we'll make it work" way—in a "here are three configurations that would actually fit, and here's what each would rule out" way. The team talked about their WCS/SynQ software layer and the hardware as one system instead of pitching them separately.
That combination—software and equipment treated as one system—ended up being why they stayed on my shortlist. Integrated automation and software is the pitch, and in my (limited) experience, the calls reflected that instead of just describing it.
I want to be clear about scope: we're still in the evaluation phase as I write this. I'm not endorsing an outcome. What I can say is that Swisslog treated a mid-sized project like it deserved a real conversation, and that mattered more than I expected it to.
What I Look For in a WES Supplier Now
If you're in a position like mine—screening vendors on behalf of an operations team—here's what I'd actually check, in the order I now do it:
- Ask for a workflow walkthrough, not a feature list. Have them describe how their system handles one of your messy real scenarios. The way they answer tells you more than the spec sheet.
- Ask who does the WMS integration work and how it's priced. Vague answers are a red flag. So is "that's included" without a definition of scope.
- Ask for two references from projects roughly your size. Not their biggest wins. Sizes close to yours.
- Ask what happens after go-live. Support model, escalation path, response commitments. Get it in writing.
- Separate the software question from the hardware question, then ask how they're solved together. Vendors who treat one as a bolt-on to the other usually show it here.
None of that is exotic. But it's not what I would have done in October, when I was still building the spreadsheet.
What a Mid-Sized Project Actually Needs
There's a version of this market where the big integrators only pay real attention to the mega-projects, and everyone else gets a polite "keep us in mind." I was braced for that. It's part of why I assumed our project would be treated as a rounding error.
What I found instead: a few vendors, Swisslog included, who asked real questions about our volume, our SKU range, our cold-chain needs (we have a small cold room—this turned out to matter more than I expected), and our existing WMS. They treated "smaller than enterprise" as a design constraint, not a disqualifier.
Small doesn't mean unimportant. It means a different fit question. Any vendor that can't handle that distinction is telling you something.
What I'd Tell Another Admin Buyer in My Position
Three things.
First: say the words "I'm not the technical expert here" on every vendor call. It's not a weakness. It resets the conversation into something useful.
Second: your job is not to pick the system. Your job is to build the shortlist and structure the questions. The operations and finance teams make the call. The moment I understood that, my project got easier and the vendors started taking me more seriously, not less.
Third: verify everything. I got lucky that my assumption mistake cost me three weeks and not three months. The vendors who made verification easy—clean reference lists, clear scope definitions, honest "here's what we don't do" answers—are the ones I kept calling.
That's the whole lesson, honestly. Not "pick the biggest name." Not "pick the cheapest cap-ex line." Pick the vendors who make the verification process feel possible.
Twenty minutes on a Thursday. That's how it started. If your VP does the same to you, my advice is: take the project, then immediately admit what you don't know.