Portal login Get In Touch
Insight November 19, 2026 3 min read

From One Warehouse to Seven: Scaling an Inventory Robot Pilot

US Foods is adding inventory-scanning robot pilots at six more warehouses, a reminder that multi-site pilots need a plan built to reach a decision.

Engineer commissioning automation equipment during a site deployment

US Foods plans to begin piloting autonomous inventory-scanning robots at six additional warehouses by the end of the year, according to Supply Chain Dive. CEO David Flitman told investors on the company's November 5 earnings call that the technology costs roughly the equivalent of one worker and counts inventory accurately within 24 hours. Going from one test site to seven is where many automation programs either build a case for rollout or lose momentum, so how those pilots are structured matters as much as the robot itself.

Why inventory scanning is a good pilot candidate

Inventory counting is repetitive, labor heavy, and easy to measure. A cycle count either matches the system of record or it does not, and the cost of a manual count is already known. That makes scanning robots a practical first step for distribution operations: the robot does not handle product, the safety case is simpler than for picking or palletizing, and results show up in data the operation already tracks.

The flip side is that the robot is only as useful as the data path behind it. A scan that never reaches the warehouse management system, or arrives in a format nobody reconciles, produces a tidy demo and little operational value.

One site proves the robot, several sites prove the program

A single test site answers whether the technology works in one building with one team. Adding sites answers harder questions: does it work with different racking, lighting, aisle widths, and floor conditions; does it hold up across shifts and local practices; and can the support model scale without engineers traveling every time something drifts. Running pilots in parallel is a good way to get those answers quickly, but only if each site is set up to produce comparable data.

  • Common success criteria. Agree on count accuracy, time to complete a full count, exception rate, and uptime before the first robot ships, and measure them the same way at every site.
  • A baseline per site. Capture current manual count accuracy and labor hours so results are compared against each building's own starting point.
  • A defined pilot length and decision date. Pilots without an end date tend to linger as permanent experiments.

Site readiness is where schedules slip

Most of the friction in a multi-site pilot is not the robot. It is wireless coverage in the far aisles, network segmentation and IT security review, charging locations, mapping time, and integration with the inventory system. Each building tends to have its own surprises. A short readiness survey at every site before hardware arrives (network, power, layout, data integration, and who owns the robot day to day) usually saves more time than any tuning done after go-live.

It also helps to standardize the deployment package: the same commissioning checklist, acceptance test, and training plan at each location, with a log of what was different and why. That record becomes the playbook for a broader rollout.

What it means for a project

For operations leaders planning a pilot of their own, the US Foods expansion is a useful model: prove the technology in one place, then test it across a range of real conditions before committing to a full fleet. The value comes from treating the pilot as an engineering program with a test plan, readiness work, and a clear decision at the end.

That is the kind of work Emtech supports. Emtech's Lab team handles site operations and IT and network readiness, the Testing team builds test plans and data collection that drive go or no-go decisions, and the Deployment team manages installation, commissioning, and multi-site logistics. With engineers embedded in customer programs across more than 20 facilities in North America and Europe, Emtech helps teams turn a promising first site into a repeatable rollout.

Building toward production-grade automation?

Tell us where you are in your project and we will line up the right team, from R&D through live operations.

Start the Conversation
Get In Touch

Let's Start the
Conversation.

Tell us where the project stands. The response will come prepared: the right questions, the right context, and a clear picture of what working together involves.

Address
635 W Reynolds Ave
Centralia, WA 98531
Phone
Hours
Mon – Fri: 7:30am – 4:00pm PT
Response Time
Fit, timeline & next steps
confirmed on the first call
Connect with Emtech

Project Inquiry

Start the conversation

Tell Emtech where your project stands. The right engineer will follow up with next steps.