GXO Logistics and Agility Robotics announced an expansion of their Digit humanoid-robot partnership on October 26. The agreed next stage includes sites in Statesville, North Carolina, and Lebanon, Tennessee. Deployments are expected to begin in early 2027 with Digit 4, followed by a transition to Digit 5 when it becomes commercially available.
This is an agreed expansion rather than a report that the new sites are already operating. It builds on the program in Flowery Branch, Georgia. The companies report more than 100,000 totes moved at that facility; this is their cumulative-work claim, not a productivity measurement independently performed by SIExpo.
A robot inside a warehouse workflow
The earlier agreement uses a Robots-as-a-Service model. Our interpretation is that evaluation needs to include support and integration rather than the machine alone.
Agility describes Arc as its cloud platform for fleet management and connection to existing automation, including compatible mobile robots and management and execution systems. That is the supplier's description, not our interoperability test against arbitrary warehouse software.
Our editorial interpretation is that a dependable outcome hinges on the handoff between systems. For each tote, the operation needs to establish when it is ready for collection, whether it has been accepted at the next point, and what happens when a stage does not finish. Robot movement is the visible part; a confirmed completed operation is the useful result.
What the count establishes
A cumulative tote count indicates a volume of work, but does not by itself provide speed, availability, or cost per completed cycle. Comparing this approach with an alternative requires a period, working hours, task mix, and interruption records. We do not infer those missing measures from the reported total.
Likewise, a successful cycle at one facility does not automatically establish the same outcome elsewhere. Layout, loads, and conveyor integration may require separate validation. This is a general engineering consideration rather than a reported fault at either selected site.
The distinction also matters when reading a future product transition. Starting with one robot generation and planning a later upgrade are different milestones. An evaluation should preserve the actual hardware and software versions associated with each result rather than combining them into an undifferentiated performance story.
A practical criterion for the next stage
We would assess a future pilot using completed, acknowledged operations under the site's real workload. Human interventions and recovery after interruption should be counted separately. Such measurement should not turn employees into an invisible fallback whose contribution disappears from the report.
The boundaries of safe operation also need to be defined for the actual environment. A product description does not replace assessment of the integrated workflow. SIExpo has not visited the facilities, tested Digit, or certified the safety of the proposed deployments.
The next verifiable step is the actual start of the agreed operations and a subsequent account of their results. Until then, the news is an expanded commercial partnership with named locations and a future schedule. Keeping that distinction visible makes it possible to follow robotics progress without counting plans as completed deployments.
*AI illustration: a conceptual editorial image, not a documentary photograph or an actual product screen.*
*Editorial verification: 2026-10-26T17:41:07.909939+00:00.*
