top of page

WMS Integration: Pairing a Modular WMS With an Existing WES

A software integrator specializing in warehouse automation systems already had an established WES (warehouse execution system: software that directs automation equipment and the work moving through it in real time). It needed a WMS that could manage inventory and the wider fulfillment process without duplicating what the WES already did. Torvyn designed and demonstrated a modular WMS integration built to run alongside it.

At a Glance

  • Who: an integrator with an established WES, supporting complex distribution and fulfillment operations

  • Problem: WMS and WES responsibilities that overlap

  • Solution: a modular WMS with clear ownership between the two systems

  • Status: designed and demonstrated, not yet in production

The Problem: Two Systems, Overlapping Jobs

Traditional enterprise WMS platforms are often built around their own fixed workflows and their own rules for allocation (reserving specific inventory for specific orders). In a highly automated facility, that can overlap with a WES that already owns much of the execution logic.

When the two do not line up cleanly, projects can require extra customization, complicated handoffs between systems, and workarounds built for each site.

Why It Is So Common

In automated distribution centers, the WMS, WES, WCS (warehouse control system: software that controls the equipment itself), ERP, shipping platforms, and warehouse automation systems often come from different vendors. Connecting them technically is only part of a WMS integration. The harder part is deciding which system owns each process, so information moves cleanly and no logic is built twice.

The Approach

Torvyn held several demonstrations and working sessions with the software integrator's leadership and technical team. The sessions focused on specific WMS workflows and on how responsibility could be divided between the two systems.

Torvyn demonstrated inventory management, receiving and putaway, waving (releasing groups of orders to the floor together), cycle counting, rate shopping, manifesting, and dashboards. The team's feedback led to two findings.

  • Allocation has to be flexible. In some environments the WMS should not lock inventory to orders before execution. The WMS holds inventory and order requirements, and the warehouse execution system makes certain execution decisions based on real-time conditions.

  • Ownership can be split at picking. The WES keeps picking and automation execution. Torvyn handles what comes before and after.

​

This feedback directly shaped how Torvyn approaches allocation, slotting, and fulfillment in its WMS.

The Solution: What Torvyn Designed

Before Picking: Torvyn WMS

Inventory, receiving, putaway, cycle counting, and order management.

Picking: Existing WES

Picking and automation execution.

After Picking: Torvyn WMS

Packing, cartonization (choosing the right box for each order), rate shopping (comparing carrier rates), manifesting (creating the shipping documents carriers require), and shipping.

When work reaches the execution layer, Torvyn passes the right information to the 

WES. Execution results and inventory movements flow back, so the WMS keeps an accurate view of inventory and order status.

 

The design is modular on purpose. The division of responsibility can be adapted to each operation, and depending on the facility it can also connect to ERP, WCS, warehouse automation systems, and carrier and shipping platforms.

Vargo Flow Diagram - Tyler Morgan - Logo added.png

What Day-to-Day Use Would Look Like

People would work in the system that fits their role, without coordinating handoffs by hand. Work that needs automated execution would pass to the WES, and status and inventory changes would come back automatically. The goal is for the whole workflow to run as one connected process.

Projected Impact

hese projections come from the requirements identified in discovery and the Torvyn team's experience with WMS, WES, and warehouse automation projects. The WMS integration has been designed and demonstrated. It is not yet running in production.

  • Most confident: clear ownership between the WMS and WES, less duplicated logic between systems, and simpler handoffs.

  • Also expected: more freedom for a software integrator or operator to choose the right technology for each layer of the operation, and potentially less custom development to make separate systems work together.

  • To be measured in a live deployment: implementation cost, throughput, and labor savings.

Where This Applies

Modern warehouses rarely run on a single software platform, so most WMS integration work means fitting into systems that already exist. The best answer is not always replacing them. Often it is setting clear ownership between them, so each one does what it handles best.

Running a Warehouse Execution System and Evaluating a WMS?

Tell us how your systems divide the work today, and we will show you where a modular WMS could fit.

Read more about how we can support Custom Content & WMS.

bottom of page