Engineering note

KNAPP AS/RS, WES Sourcing and WMS Integration Costs: An Admin Buyer's Honest FAQ


By Jane Smith

I'm the office administrator at a 150-person third-party logistics and distribution company. I don't buy automation systems—operations does that. What I do is run the vendor paperwork, the purchase orders, the invoice reconciliation and the budget tracker finance stares at every month. Which means when a WES or WMS integration gets sourced, I'm the one who eventually finds out whether the quote was real.

I've been in this seat since 2020. Four software integration purchases and maybe a dozen quotes later, here's what I'd tell another admin buyer who just got pulled into "the automation meeting."

  • What does KNAPP actually sell?
  • Is KNAPP AS/RS only realistic for huge warehouses?
  • KNAPP was at Automatica 2025—what should we take from that?
  • How do you source a warehouse execution system without getting played?
  • What is "WMS integration wholesale," and is it cheaper?
  • What does WMS integration actually cost?
  • What breaks in these projects?
  • What do I ask before anyone signs?

What does KNAPP actually sell?

The whole stack, basically. KNAPP is an Austrian warehouse automation company—headquartered near Graz—and their portfolio runs from automated storage and retrieval systems (the OSR Shuttle is the name most people know) through conveyors, shuttle systems, autonomous mobile robots like the Open Shuttle, and the KiSoft software layer that sits on top as WMS/WCS/WES.

Here's the part that matters for sourcing: they're an integrated supplier. The mechanical systems and the software come from the same vendor, and the pitch is end-to-end automation rather than a bolt-on. That's genuinely useful if you're building a new facility. It's less useful if all you want is software integration on top of equipment you already own—because then you're paying for a bundle you don't need. Ask early which parts are separable. The answer shapes your entire budget.

Is KNAPP AS/RS only realistic for huge warehouses?

My honest read after watching this from the procurement side: yes, mostly, for their flagship AS/RS work. They built their reputation on large, complex, greenfield logistics centers, and the sales cycle reflects it. Even after choosing a vendor, I've sat through months before a single P.O. got issued.

To be fair, the portfolio has broadened—robotics and mobile platforms have brought the entry point down—and smaller deployments do exist. But if your board is approving a $200K automation project, you're not their typical customer, and pretending otherwise wastes everyone's time. That doesn't mean don't call them. It means ask directly what the minimum viable project looks like, and don't be offended by the answer. I've had vendors treat a $4,000 first order with more care than a $40,000 one, and those are the ones I still call. Small doesn't mean unimportant—it means potential.

KNAPP was at Automatica 2025—what should we take from that?

Automatica is the biennial robotics show in Munich; the 2025 edition ran in late June. KNAPP's warehouse robotics were part of the conversation, and if someone on your team came back with photos, that's great—but a trade show demo is not a validation test.

The question I now ask after every show: which of these things is shipping today, and which is a pilot? Vendors are usually honest about this if you ask plainly in writing. Get it in the minutes. If a capability is "on the roadmap," it does not go in your acceptance criteria, and it does not go in the business case. The show floor shows possibility; your contract has to be built on deliverables.

How do you source a warehouse execution system without getting played?

Four things, and none of them are glamorous. First, put the operations manager and a finance person in the room with you from day one—WES sourcing decisions that skip finance come back to bite you at the invoice stage. Second, write a two-page requirements document, not a twenty-page one; long documents get read by the sales team and nobody else. Third, issue an RFI before an RFP, because it filters out vendors who can't do your project before you burn a month on proposals. Fourth, do reference calls and insist on speaking to someone in a similar operation, not just their favorite customer.

And log everything. The most frustrating part of this job is how often the same question gets asked at four different stages because nobody wrote down the answer. You'd think a shared tracker would solve it, but the tracker only works if the first person fills it in.

What is "WMS integration wholesale," and is it cheaper?

This term gets thrown around a lot, and it usually means one of two things: buying through a value-added reseller rather than directly from the software vendor, or buying a licensed platform through a distributor who bundles implementation services.

Is it cheaper? Sometimes. But the spreadsheets said reseller option B would save us 15% and my gut said no—not because the number was wrong, but because the reseller had never integrated with our conveyor controls and couldn't name anyone who had. The two weeks after I pushed back were stressful. When we finally checked the references, I turned out to be right. Wholesale pricing shifts responsibility onto a middle party, and when something breaks at 2am, "that's the OEM's problem" is not a support plan. Cheaper mostly means you need to know exactly who owns what.

What does WMS integration actually cost?

Ranges only, based on quotes I've seen between 2023 and 2025 for mid-market distribution operations—not the flagship projects. Your mileage will differ, so treat these as a starting point for your own questions. Based on those quotes:

  • Software licensing: roughly $150K–$400K, scaled by warehouse count, user licenses and whether it's a perpetual or subscription model
  • Integration and configuration work: $100K–$300K, driven almost entirely by how many legacy systems you need to couple to
  • Commissioning and go-live support: $50K–$150K
  • Annual maintenance: typically 18–22% of license value—and yes, I've seen the lower number quoted and the higher number renewed in year two

What none of those numbers include: the internal labor on your side. Data cleansing, process mapping, training, and the downtime planning that nobody ever budgets for. In our 2024 consolidation, that overhead ate about as much staff time as the vendor's implementation team spent, and I had to go back and reframe the business case to finance. Two things I'd flag for anyone doing this: the MHI annual industry report consistently ranks warehouse automation among the top capital priorities—but market size numbers don't tell you what your integration should cost. And any guide that quotes a clean total is leaving out the part that surprises you.

One caveat on all of the above: my experience comes from a handful of quotes in mid-sized, non-greenfield operations. If you're pricing a 500,000 sq ft new build, your numbers are a different order of magnitude.

What breaks in these projects?

Data quality, almost always. Integrations don't fail because the software is bad; they fail because someone's SKU master has three duplicate item codes and a unit-of-measure field that means different things in different systems. The other recurring failure is acceptance criteria—"system operational" is not a milestone, and if it's in the contract, it's getting invoiced.

From my side of the desk, there's a third failure nobody talks about: the P.O. and invoice structure. If the implementation is split across five milestones and finance has to approve each one, you need that structure agreed before signature, not after. The vendor who couldn't provide a proper invoice once cost me a departmental budget fight I'd rather not repeat—and I did not make that mistake again.

What do I ask before anyone signs?

Keep it short and uncomfortable. Who owns the integration layer if the vendor and the reseller disagree? What's the specific, testable definition of go-live? What does year-three maintenance cost, in writing? Which reference customer runs the same combination of software and equipment we're buying? And what happens if half the scope is descoped—what's the price recalculation?

If a vendor can answer all five in writing without needing a week, that tells you more than the demo did.

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.

WCS Sourcing: Integrated vs. Standalone — A 6-Year TCO Comparison →