Warehouse automation magazine feature visual
Application note

Q&A: FORTNA, WES Integration, and Seven Questions for Warehouse Automation Vendors

Jane Smith

I'm an office administrator for an 800-person company. I manage all service orders, including roughly $400,000 annually in material handling and warehouse-related purchasing across six vendors. I report to both operations and finance.

I'm not a warehouse automation engineer. But I've sat in enough WES and material handling discussions over the past three years to know the questions that matter. Here are seven I'd ask before picking a vendor — or signing off on a recommendation.

1. What does FORTNA actually do in warehouse automation?

FORTNA works in warehouse automation and material handling — that includes conveyor systems (the fortna conveyor line), warehouse execution system software (fortna wes), and integration with WMS and controls layers. As a buyer, the practical distinction is that they cover both the physical conveyance and the execution software that runs on top of it.

What I'd verify: whether the specific project has dedicated FORTNA implementation support behind it, or whether the team you're meeting is mostly coordinating between three other subcontractors. That's not a knock on FORTNA — it's something I now check with every vendor after a 2023 project where "full service" turned out to mean "we subcontracted three parts and didn't tell you."

2. What matters most when choosing a conveyor system?

The hidden costs aren't in the hardware. They're in downtime, maintenance contracts, and expansion flexibility.

An operations manager I worked with put it plainly: "A conveyor down for an hour costs us one number. Down for a day costs us a different conversation."

Three questions I ask now:

  • Is the support structure rated for your actual throughput, not the spec-sheet figure?
  • Is maintenance handled directly or contracted out — and what's the contract response time if it's contracted?
  • What does the incremental cost look like if you need to add a sortation line in 18 months?

I once signed a "standard" conveyor maintenance agreement without realizing standard didn't include installation supervision. That came as a change order. I learned to read the scope section twice.

3. What does the FORTNA WES platform actually do?

A warehouse execution system (WES) sits between the WMS and the automation controls. The WMS manages inventory and order release; the WES schedules work, balances tasks, and coordinates the conveyor and sortation equipment in real time.

From my experience, the WES platform's value shows up during exceptions — when an order changes, inventory doesn't match, or equipment jams. That's when the WES is either helping you recover quickly or leaving your floor team to figure it out manually.

So the procurement question I'd ask is: "Walk me through how your WES handles a mid-shift order change from receipt to dispatch." If the demo skips exception handling entirely and only shows the happy path, you're watching a process flow, not tested software.

FORTNA's WES is built to integrate with both their own equipment and third-party systems. But confirm that the exact integration you need has been done before — not just that it's technically possible.

4. What should I look for in a warehouse execution system manufacturer?

Look at the implementation team, not just the feature list. I've seen WES platforms with impressive feature matrices where the implementation engineer assigned to our project had never worked on a system our size before.

Questions I ask now:

  • Who exactly on your team will be doing the implementation?
  • How many deployments have they done at roughly our scale?
  • Can you connect me with a reference customer who was in a comparable situation — not a five-year mature deployment, but one that went live in the past 18 months?

That last one matters. A reference customer who's still working through post-go-live adjustments will tell you more about the actual experience than any case study.

5. How do I choose a WMS integration manufacturer or partner?

This is where communication failures have cost me the most time.

I once said "WMS integration" and meant two-way API-level order and inventory sync. The vendor heard "CSV export that drops into your reporting." We discovered the gap three weeks before go-live. Nobody was lying — we were using the same words with completely different definitions.

Now I confirm three things before discussing price:

  1. Is the integration a pre-built connector, or custom work from scratch?
  2. Has this team integrated with our specific WMS version before?
  3. Who provides the test environment — and who signs off on integration testing?

That last point — "you provide" versus "we provide" — often decides whether integration takes a week or a month. When both sides know exactly who does what, the project moves faster and costs less on both ends. Efficiency isn't just about speed; it's about not paying twice for the same misunderstanding.

6. WES OEM vs private label: what would I actually ask?

This is one of those questions that sounds technical but comes down to support and accountability.

In simple terms: WES OEM arrangements typically involve licensing or rebranding another company's engine. A private-label or original-brand WES is developed and maintained by the vendor whose name is on it.

Both paths can work. An OEM arrangement might get you a faster deployment or more generalized features. A private-label system often offers more customization and clearer ownership of the product roadmap.

But I wouldn't decide based on the label alone. I'd ask:

  • Who develops and maintains the core WES code?
  • When we file a change request, who owns it — the software originator or the reseller?
  • What does the release cycle look like, and when was the last major update?

If the answers are vague, that tells you something. Not about the product necessarily — but about the support layer you'd be relying on.

7. What hidden costs should an administrative buyer watch for?

The costs that don't show up on the initial quote and show up later on a change order:

  • Installation supervision: Often quoted separately. Easy to miss if you're comparing bottom-line figures.
  • Integration testing: "Tested" doesn't always mean "tested in your environment." Staging and cutover time can be a separate line item.
  • Annual maintenance and support: Usually 15-20% of the base price, but often shown as a single line that's easy to gloss over.
  • Version upgrades: If WES upgrades aren't covered in the support contract, the next major release could come with a separate bill.

These aren't dealbreakers — they're just costs you want in the budget before someone across the table says "we can add that." A few years ago, our system integrator went dark for three days during a warehouse transition. That's when I stopped treating redundancy and documentation as optional. Now every vendor contract I touch has an explicit line for emergency-support scope and upgrade pricing.

It's not glamorous procurement work. But if it saves one awkward change order, it's worth the extra questions.

Share insights with your project team Contact FORTNA
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.