Use Case: Third-Party Logistics
AMR orchestration across multi-client 3PL operations
3PL floors run multiple client SKUs and operational rhythms concurrently. Stateful Robotics coordinates AMR task execution across all of them without client operations interfering with each other.
The Problem
What breaks AMR operations in 3PL environments
Conflicting client operational rhythms
Two client operations on the same floor have different peak windows and different storage zones. A robot assigned to client A's pick run may be blocking an aisle that client B's inbound receiving run needs. Sequential dispatch per client doesn't see this conflict.
Dynamic carrier arrival changes floor priority
An early carrier arrival at a dock requires urgent outbound preparation that wasn't in the original run plan for that client. The WMS updates priority, but AMR runs from other clients already have robots occupying the approach aisles.
Fleet capacity contention across clients
Shared AMR fleets need to be allocated across concurrent client operations. Without visibility into all active task graphs, robots end up idle waiting for instructions for one client while another client's run is starved of capacity.
No run history for post-shift analysis per client
3PL operators need to report operational performance back to clients. When the orchestration layer discards task history at the end of each run, there's no data trail to show cycle times, delays, and their causes per client per shift.
How It Works
Cross-client task graph coordination
Each client operation gets its own task graph
Ops requests from different client WMS systems are compiled into separate task graphs. Dependencies within each client's operation are resolved independently. Robots are allocated from the shared fleet pool at assignment time, after conflict pre-checking across all active graphs.
Cross-graph conflict pre-check before dispatch
The fleet coordinator checks for aisle conflicts, zone contention, and robot capacity constraints across all active task graphs before issuing assignments. Conflicts are surfaced before any robot moves, not after it has caused a queue.
Per-client run history retained
Every completed task graph is stored with full execution history, including replan events. 3PL operators can export per-client run data for shift reporting, SLA validation, and identifying recurring floor patterns that affect that client's operations specifically.
Multi-WMS integration
In multi-client 3PL environments, different clients often use different WMS systems. Stateful Robotics can accept ops requests from multiple WMS sources simultaneously. Each source connects via the same REST API; the orchestration layer handles cross-source task coordination.
Operations tier and above support up to 3 WMS integrations. Fleet tier supports unlimited sources. Custom WMS integrations are scoped and built during the onboarding engagement.
3PL Pilot
Bring one client operation into the pilot first
A 3PL pilot typically starts with a single client's operations and expands to cross-client coordination once the initial integration is running. We scope pilots to your specific floor configuration.