​

On October 29, Symbotic and Walmart announced an expanded agreement covering 25 U.S. regional distribution centers, with an initial commitment of about $6 billion over several years.

Three days earlier, GXO and Agility Robotics announced Digit humanoid deployments at two more U.S. sites, expected to begin in early 2027.

Both announcements are large. Both are also written in the future tense.

For the companies involved, that’s normal. For everyone else buying from these vendors, it raises a different question than the one most coverage asks.

It isn’t whether the technology works.

It’s whose schedule, and which product generation, your own program ends up tied to.

Commitments Written in the Future Tense

Start with what the Symbotic release says. It describes a spend commitment and planned additions to Walmart’s regional distribution network. It gives no per-site timeline and no site-level scope. Symbotic’s forward-looking statements also list possible termination of the agreement, in whole or in part, among the risks.

None of that is a criticism. It’s what a plan looks like before the work begins.

The GXO announcement adds a second feature. Deployments at Statesville, North Carolina, and Lebanon, Tennessee, are expected to begin in early 2027 using Digit 4, then migrate to Digit 5 when it becomes commercially available. Agility says early customer access to Digit 5 is expected in the first half of 2027, with general availability targeted for the end of that year.

The only operating evidence in the release is a company claim that Digit has moved more than 100,000 totes at GXO’s Flowery Branch, Georgia, site. The release reports no uptime, intervention rate, or cost baseline. And that evidence comes from the current generation, not the one the program is expected to migrate to.

Then there’s the order book. Agility’s commercial update cites a Digit 5 order figure above $300 million. The same release says that figure is potential multi-year value, subject to contractual milestones and product specifications, and not current revenue. Separately, Agility and Churchill Capital Corp XI expect to close a capital raise of about $465 million on November 4, subject to shareholder approval.

The figures cited here come from company announcements, rather than independent operating evaluations.

Why Buyers Who Aren’t the Anchor Should Care

A program of this size shapes a vendor’s calendar.

Installation crews, commissioning engineers, and support attention are finite. The releases don’t say how that capacity will be allocated across customers. They also don’t say who carries the cost when a program moves from one hardware generation to the next.

That matters most for buyers whose programs are small relative to the anchors. Their go-live dates, support priority, or hardware generation could be set by commitments they never saw. The usual consequences are delayed go-lives, extra commissioning work, and re-validation of a product that changed partway through.

I’m not claiming any vendor will deprioritize smaller customers. These announcements don’t show that.

The point is narrower. Nothing in them protects you if it happens, and contracts signed now are where that protection has to be written.

The Roadmap Exposure Check

Before signing with, or expanding, a vendor that has just announced a large anchor commitment, a financing event, or a next-generation product, I would want five answers in writing, and in the contract where possible.

1. Slot priority. Over the next 24 months, how many concurrent site programs will the vendor’s installation and commissioning teams carry? What protects your go-live date if a larger customer’s schedule moves?
2. Generation clause. Which hardware and software generation will be delivered at go-live? What triggers migration to the next one, and who pays for the migration, retraining, re-validation, and downtime?
3. Slip scenario. If the next generation’s availability date slips, can the current generation keep operating and stay supported? On what terms, and for how long?
4. Contingency share. Which of the vendor’s cited orders and pipeline figures are firm revenue, and which depend on milestones, specifications, or approvals?
5. Evidence transfer. What operating data exists for the exact generation you’re buying, such as uptime, interventions per shift, and sustained throughput? What shows it carries over to the generation the contract migrates you to?

These aren’t equally weighted.

Questions 2 and 5 are the ones I would refuse to sign without. If you can’t say who pays for a generation change, or what evidence supports the new generation, you’ve accepted a roadmap decision you don’t control.

What to Reconsider

A large commitment tells you a vendor has demand. It doesn’t tell you where your program sits in the queue.

The evidence you rely on should match the product you will actually receive. A tote count from one generation doesn’t validate the next. A headline order value that depends on milestones isn’t a delivery schedule.

So when the vendor’s roadmap and your go-live date conflict, which one moves?

3 Signals Worth Watching

1. Site-level detail from Symbotic and Walmart

The release gives no per-site timeline or scope. Until the companies disclose either, the $6 billion figure is a statement of intent, not a schedule. Watch for rollout sequencing and what each distribution center is expected to receive.

2. Whether the Digit 5 dates hold

Early customer access is targeted for the first half of 2027, and general availability for the end of 2027. Watch for any change to those dates, and for what customers on Digit 4 are told about migration timing and cost.

3. Operating evidence for Digit 4

The only figure published so far is a tote count from one site. Watch for uptime, intervention rates, and sustained throughput from GXO’s current and planned sites. Those numbers would establish a baseline against which the next generation can be evaluated.

If this question is active in your organization, tell me where the operating reality differs from the technology narrative.

​