Choosing an Automated Warehouse Supplier: 4 Scenarios, 4 Different Answers
-
There's no single best supplier. But there are four distinct buying problems.
-
Scenario 1: You're buying a component
-
Scenario 2: You're buying an integrated system
-
Scenario 3: You're buying capacity under someone else's brand
-
Scenario 4: You're buying a migration path
-
How to know which scenario you're in
There's no single best supplier. But there are four distinct buying problems.
Ask ten procurement managers which automated warehouse supplier is the best and you'll get ten answers. Ask them what they were actually buying and the answers collapse into four categories.
That's the problem with most "what to look for in a automated warehouse supplier" checklists. They assume everyone is solving the same problem. In practice, I've watched nearly identical RFQs go to completely different supplier types — and both projects succeeded, for opposite reasons.
After six years tracking our material handling and storage equipment budget (roughly $1.8M annually across VLM, racking, and shuttle modules), I can tell you the four scenarios I see, and how the buying criteria change in each. The right question isn't "who's the best supplier." It's "which of these four am I actually in?"
- Scenario 1: You're buying a component (a single VLM, a racking bay, a shuttle module).
- Scenario 2: You're buying an integrated system (ASRS + racking + conveyor + WCS).
- Scenario 3: You're buying capacity under someone else's brand (OEM or private label).
- Scenario 4: You're buying a migration path (bulk racking now, automation later).
Scenario 1: You're buying a component
Single-unit purchases. One Modula vertical lift module to replace a manual aisle. One pallet racking run. One shuttle module bolted onto an existing system.
Here's the counterintuitive part: in this scenario, price is the third thing you should compare, not the first. The first is service radius. The second is spare parts availability.
Why does this matter? Because a VLM down for eight hours costs you labor redirection. A VLM down for eight days because the nearest technician is 600 miles away costs you throughput. That's a very different number.
Two things I learned the hard way:
Communication failure. I said "standard footprint." The supplier heard "whatever fits your bay." Result: a Modula VLM that arrived 200mm too wide for our existing guarding. Not the supplier's fault — my specification wasn't explicit enough. Now every component purchase includes a measured-and-signed footprint drawing before the PO goes out.
Process gap. We didn't have a formal acceptance checklist for component deliveries. Cost us on the third installation when a minor electrical fault wasn't documented, and the warranty clock started anyway. That checklist now has 14 line items. It took 40 minutes to build. I wish I'd built it after the first time.
For component sourcing, the criteria list is short: service radius (<4 hours preferred), spare parts lead time (ask for a written parts list with current lead times, not a catalog), and installation documentation quality. Modula storage systems have an obvious advantage here if you're in their multi-city service footprint — Chicago, Fort Wayne, Milwaukee, Minneapolis, Des Moines, Miami — and an obvious disadvantage if you're not. That's not a sales pitch; it's just how service networks work.
Scenario 2: You're buying an integrated system
ASRS plus racking plus conveyor plus WCS integration. This is where the buying criteria inverted for me.
In Scenario 1, I negotiate hard on price. In Scenario 2, I stop negotiating on price and start negotiating on responsibility boundaries.
The risk weighing: Vendor A quoted $1.42M with clear integration responsibility. Vendor B quoted $1.18M but excluded WCS-to-WMS interface work ("to be coordinated with your IT team"). That $240K gap looks like savings until you compute the downside — worst case, an integration project that runs 6 months long at $40K/month in internal engineering time. Best case, it works and you saved $240K. The expected value said go with B. The downside felt catastrophic.
I went with A. Here's why that mattered: in a system purchase, the supplier you're evaluating is really a risk owner, not a vendor. If they won't own the interface, you own it. If you own it, the only question is whether you have the team to execute — and most mid-market operations teams don't.
What to actually check in this scenario:
- Reference calls with the same integration scope. Not "did they deliver?" — "did they deliver with a scope that also included that WCS layer?"
- The interface specification document. Ask for one before signing. If they don't have a template, that tells you something.
- Standard alignment. ANSI/ASME B30.13 (for automated storage/retrieval), ANSI MH16.1 (industrial steel storage racks), and local seismic compliance should appear in the proposal without you asking. If they're missing, the proposal is a brochure.
And here's the honest limitation: not every supplier is equally strong in Scenario 2. Some are excellent component manufacturers (Scenario 1) who also offer integration. Those are different skill sets. Ask directly: "How many integrated projects of this exact scope have you delivered in the last 24 months?" A vague answer is an answer.
Scenario 3: You're buying capacity under someone else's brand
OEM or private label. You're not buying a Modula — you're buying something that says your brand, built to your spec, with a warranty that may or may not transfer to your customers.
The obvious checks: manufacturing consistency, traceability of component lots, and whether the OEM supplier will support your end customers directly (under your name) or route it back through you. The non-obvious check is the warranty chain.
I've seen an OEM arrangement where the equipment warranty was honored — technically. In practice, the end customer called us, we called the OEM, and three weeks passed before a technician was dispatched. Everyone did what the contract said. The outcome was still bad.
If you're in this scenario, test the warranty chain in advance: file a mock claim before signing. See how long each hop takes. That five-minute test has saved me more due diligence time than any reference call.
Scenario 4: You're buying a migration path
You're starting with bulk warehouse racking today and planning to add automation in 18–36 months. This is the scenario where the "cheapest option now" is most likely to cost you double later.
Why? Because racking purchased without future automation in mind is often incompatible with it — wrong bay depth, wrong beam capacity, wrong flue spacing for NFPA 13 sprinkler compliance once you add an ASRS canopy. Retrofitting is possible. It is rarely cheap.
The counterintuitive advice: in Scenario 4, you often should not buy the cheapest bulk racking. You should buy the racking that preserves your upgrade path, even at a 10–15% premium. I watched a peer team save $60K on initial racking in 2022 and spend $118K in 2024 retrofitting for a shuttle system that the original layout couldn't accommodate. That's not a made-up number — that's the kind of redo that budgeting processes don't catch until the next cycle.
For racking sourcing in this scenario, three specs matter more than price: beam capacity reserved for future loads, aisle widths compatible with either forklift or shuttle access, and seismic bracing that meets the higher of today's or your projected local code (ASCE 7 provisions apply — check your jurisdiction).
How to know which scenario you're in
Three questions. Answer honestly.
1. Can my project be described on one purchase order line? If yes, you're in Scenario 1. If you need a scope of work document, you're in Scenario 2.
2. Who signs off on the integration interface? If it's your IT team, you're in Scenario 2 and you need a supplier who will own that interface, not coordinate it. If it's the supplier, ask to see the deliverable template.
3. Will I need to do this again in 24 months? If yes, you're in Scenario 4, and today's purchase should be evaluated on upgrade compatibility, not just unit cost.
If none of these questions have clear answers yet, you're not in any scenario — you're in a pre-scenario. That's fine. It just means the next purchase shouldn't be equipment. It should be data: SKU velocity, SKU growth rate, and peak-to-average throughput ratio. Those three numbers determine which scenario you'll actually land in. Everything else is negotiation.
Look, I'm not going to pretend there's a universal answer. There isn't. The honest version is: the right automated warehouse supplier for you depends entirely on which of these four paragraphs you just recognized yourself in — and on whether you're willing to admit that before the RFQ goes out.