PES wraps any device in a software layer that makes it a first-class object in WorkFlow Studio. No more rough handoffs. No more silos. One orchestration layer for your whole floor.
All that’s required
to integrate any device
Manual handoffs between
wrapped devices
Orchestration layer
for all devices on the floor
Live deployments
running PES today
Most warehouses that have invested in automation end up running a collection of systems that don’t truly communicate. AutoStore handles AutoStore orders. The wrapper handles wrapping. The WMS manages waves. A human coordinator bridges the gaps — because the systems are connected, but not orchestrated.
Every boundary between systems costs time and labor. Equipment idles while it waits for a signal from an adjacent system. Workers intervene to manage transitions. Supervisors monitor multiple dashboards and manually sequence work.
This is the integration problem — and it compounds as you add more automation. The more systems you add, the more boundaries you create.
System A finishes and signals System B. System B starts. There is no shared state, no capacity awareness, no load balancing. They are connected but not orchestrated — and every boundary is a place where work stalls.
A conveyor sits idle waiting for a robot pick. An ASRS queues orders that a downstream station isn’t ready for. Neither system knows what the other is doing. Both run below capacity as a result.
Every system boundary requires a human coordinator. You added automation to reduce labor — but you’re still paying someone to stand between your automated systems and translate between them.
Each new system you add creates new integration points. What started as two systems becomes five. The coordination overhead grows with every investment, not shrinks.
Most “integrations” between automation systems are rough handoffs at the boundary. PES wrappers eliminate the handoff entirely.
A wrapped device isn’t connected to PES — it is part of PES. PES knows its state, its queue, its capacity, its availability, and optimizes work distribution across it in real time, exactly the same as a native Prime robot or station.
The result is true orchestration: every device on the floor working together under one system, with one source of truth.
If the device exposes a PLC interface or an API, Prime builds a PES software wrapper around it. The wrapper speaks PES's internal protocol — state, capacity, task queuing, availability reporting.
Once wrapped, the device reports its state, queue, and capacity to PES continuously. PES can read current throughput, remaining capacity, task queue depth, and availability — the same data it gets from every native Prime robot.
Inside WorkFlow Studio, the wrapped device is a draggable object in WorkFlow Builder. It can be sequenced with Prime robots and stations, assigned tasks, incorporated into workflow logic, and monitored on dashboards — alongside everything else PES is running.
PES treats the wrapped device exactly like a Prime robot. It routes work to it, sequences tasks across it and adjacent devices, and balances load dynamically. The wrapped device is no longer a dumb device waiting for a signal at the boundary — it is interleaving with every other device on the floor in real time, with no human coordinator required.
Every device below has a production-ready PES wrapper — tested, deployed, and running in live operations. If your facility uses any of them, integration is immediate.
Once wrapped, a device is no longer a dumb device sitting at the boundary of your operation. It becomes a participant — interleaving with Prime robots, stations, and other wrapped devices to create efficient, coordinated workflows that no single vendor’s system could produce alone.
The library grows with every deployment. If your device isn’t on this list, custom wrapper development is a normal part of the Prime onboarding process — scoped and priced before deployment begins.
Wrappers built for multiple pallet wrapping machine brands. Whatever wrapper you run, Prime can integrate it. Tell us what you have.
Automated pallet dispensers integrated as first-class PES workflow objects.
PTU wrapped and sequenced with Prime robots for fully orchestrated pallet handoffs.
Vertical transfer units orchestrated within multi-level fulfillment workflows.
Integrated into Prime’s receiving station software. Captures dims and images of new SKUs when they first enter the facility — automatically, as part of the receiving workflow.
Pallet integrity check before a dispenser, RackBot, or wrapper. Verifies pallet is straight and stable enough before the next workflow step — preventing jams and errors downstream.
Scans every case on a pallet and records it in the PES audit trail. Critical for food producers required to document chain of custody — every pallet, every case, every location.
Automated crane systems wrapped as PES device objects. PES directs crane moves as part of the unified workflow — no separate crane controller required at the boundary.
Pallet conveyor systems and turntables wrapped as PES workflow objects. PES sequences pallet flow across conveyors, gates, and turntables in coordination with robots and stations.
Print-and-apply labeling machines wrapped as PES workflow objects. PES directs the AMR to the PANDA station, triggers the label cycle, and routes the labeled pallet onward — all as one uninterrupted workflow.
AGV forklift systems are good at autonomous movement. What they don’t have is order execution ability — they can navigate and transport, but they don’t know what to get, when to get it, or in what sequence to keep a downstream pick system running at capacity.
PES fills that gap. Prime wraps the AGV forklift as a device and directs it through the same orchestration layer as every other device on the floor. PES knows what the system needs, when it needs it, and where it’s located — in racking, floor stacked, or staged. It directs the forklift to the right location, pulls the right pallet, and delivers it just in time.
The result: the pick system is never starved. No supervisor manually dispatching forklifts. The entire replenishment loop runs inside PES, synchronized with everything downstream.
The most demanding workflow — pallets shift in transit, requiring careful sensing and adjustment. PES coordinates the forklift with receiving workflows to capture inventory on entry.
PES sequences outbound pallets and directs the forklift to load in the correct order — staging, sequencing, and loading coordinated as a single PES workflow.
PES directs the forklift to pull the right SKU from racking or floor storage and place it into RackBot or onto a MobilePallet frame — just in time to keep the pick system fed.
Labeled pallets moved from print-and-apply stations to outbound staging — the forklift runs the move on PES direction without a human dispatcher in the loop.
SKUs no longer needed in the active pick field are directed to putaway locations by PES — the forklift receives the task, executes the move, and confirms completion back to PES.
The AGV forklift vendor provides the navigation. PES provides the execution intelligence. Together, they close every pallet movement loop on the floor — without a supervisor dispatching manually.
Every arm can pick. The physical act of moving a case from one point to another is not where you win or lose. That’s solved hardware.
Maximum arm efficiency is achieved through smart order matching and pick sequencing — through the intelligent execution of what gets picked, when, and in what sequence. Blind manual execution of orders saturates arm capacity and leaves throughput on the table. Smart execution, driven by the orchestration layer, is where the throughput is.
PES provides that execution intelligence. It sequences picks across arms and robots together, matches orders to maximize arm utilization, and coordinates arm output with every downstream device in the workflow.
Kawasaki, Fanuc, or any other arm. The PES wrapper is built around the arm's interface — not the brand. Case picking arms, layer picking arms: if it exposes an API or PLC, Prime wraps it. The end effector is the critical hardware variable; the software wrapper handles the rest.
Arms already running under a third-party execution system can be wrapped and integrated into PES as a device object — PES orchestrates around the arm without replacing the existing system. Or, for operations building fresh, PES is the execution layer directly: routing work to the arm, sequencing picks, coordinating with every other device on the floor.
Once wrapped, the arm is no longer a silo with its own pick queue. PES distributes work across the arm and Prime robots together — interleaving picks, matching orders to arm capacity in real time, and eliminating the idle time that comes from managing an arm as a standalone station.
Connecting a device is not the same as orchestrating it. WorkFlow Studio is what makes the difference. It’s the application where every device on your floor — Prime and third-party alike — becomes part of a unified, configurable, monitorable fulfillment system. Site Manager handles operational control; WorkFlow Studio handles configuration and execution across every device.
WorkFlow Builder is where you design the logic. Drag Prime robots, Prime stations, and any wrapped third-party device into a workflow. Sequence them. Define conditions. Set priorities. If it’s on the floor and wrapped in PES, it’s an available object in the builder.
Real-time visibility into every device, every robot, every station — Prime and third-party alike. Current state, queue depth, throughput, availability. One dashboard replaces monitoring every system separately. No more toggling between five vendor portals to understand what your floor is doing.
Manage live workflows, adjust priorities, respond to exceptions, and rebalance work across devices — all from WorkFlow Studio. When something changes on the floor, one operator in one application makes the adjustment. Not three operators across three vendor systems.
AutoStore is excellent storage technology. It delivers storage density that’s genuinely hard to match. Its limitation is that it runs as a silo — its own WCS, its own pick queue, its own logic, with no real-time connection to what the rest of your floor is doing.
The result: AutoStore runs its pick queue on its schedule. Downstream stations wait. Prime robots route around it. Human coordinators bridge the gap between what AutoStore is releasing and what the rest of the operation can absorb.
PES wraps the AutoStore as a device object, exposes it in WorkFlow Builder, and folds its picks into the unified fulfillment flow alongside Prime robots and stations. AutoStore’s picks are now part of the same orchestration layer as every other device on your floor.
You keep the storage density you paid for. You get PES orchestration across the full floor. You don’t replace the AutoStore, and you don’t buy a second WES.
AutoStore runs its own pick queue, releasing orders on its schedule. Downstream stations idle waiting for releases. Human coordinator manually batches and sequences work between AutoStore and the rest of the operation.
PES wraps AutoStore as a device object. Its picks are folded into the unified fulfillment flow. PES routes work to and from AutoStore based on real-time capacity — the same way it routes to any Prime robot. One coordinator, one dashboard, one system.
AutoStore’s storage density + PES orchestration across the full floor. No replacement. No second WES. No new vendor.
PES is the execution layer below your WMS, not a replacement for it. Orders flow from the WMS into PES. PES executes across the full floor — directing robots, stations, and wrapped third-party devices. Confirmations flow back to the WMS when execution is complete.
The WMS doesn’t need to know which robot picked which pallet, which station processed which case, or which wrapped device handled which transfer. PES handles execution. Your WMS handles the order record. Each system does what it’s designed to do.
PES connects to WMS, ERP, and MES via standard APIs. SAP integration is in live production at a Regional Distribution and Manufacturing Operation.
Orders in, confirmations out. PES receives work from your WMS and returns execution confirmations. Your WMS stays the order-of-record system.
Live SAP integration running at a Regional Distribution and Manufacturing Operation. Standard API-based connection handles order release and inventory confirmation.
Manufacturing execution systems connected via standard APIs for factory automation workflows where PES manages AMR missions and material flow.
The MobilePallet AMR drives into the U-shaped conveyor system and transfers the pallet — a fully PES-directed handoff. The conveyor is wrapped as a PLC device; PES routes the robot to it based on real-time conveyor capacity, sequences the transfer, and continues the workflow downstream. No separate conveyor controller. No human coordinator at the boundary.
Every other automation vendor requires commitment to a closed ecosystem. New robots, new stations, new software, new everything — their stack only.
Prime’s approach is different because warehouses are different. Most operations have existing infrastructure, equipment that can’t be written off, and systems that are partially working. A strategy that ignores this isn’t a strategy — it’s a fantasy.
PES is designed to wrap what you have, orchestrate what you add, and give you one unified system as your floor evolves. You don’t have to start over to get the orchestration you need.
Describe what you’re running — the robots, the ASRS, the conveyors, the WMS. We’ll walk you through how PES wraps it and what orchestration looks like for your specific operation.
If it has a PLC or an API, we’ve almost certainly seen it before — or can build the wrapper. The conversation starts with your floor, not our product catalog.
We’ll respond within one business day to schedule a technical walkthrough. No sales pitch — you’ll talk to someone who knows the platform.
