Demo vs Pilot vs Production Deployment

A demonstration has an observation boundary

A video can show a task occurring, but usually does not disclose every attempt, reset, operator input or failure. Keep edited video, live demonstration and laboratory evaluation distinct. If the source shows only the successful segment, record what is visible without inferring unattended reliability. Ask for the selection procedure and a continuous trial record when the decision depends on repeatability.

A pilot is an evaluation stage

A pilot can establish that a system was tested in a relevant setting. Its duration, task boundary, human support and acceptance criteria determine what was learned. GXO’s source explicitly distinguishes proof-of-concept work from the later commercial Digit agreement. That transition is useful evidence; a generic partnership announcement without the same detail should not receive the same maturity label.

Production needs a described operation

Seek a customer, facility or service area, recurring task and a dated operational statement. Co-op’s account describes a delivery service following a local pilot, while identifying store staff and customer interaction in the workflow. That supports the delivery-stage account, not autonomous completion of every retail step. Production is a property of a defined operation rather than the company as a whole.

Do not add announced units to installed fleets

DHL’s statement separates existing Stretch use from intended expansion. Sam’s Club similarly separates floor-scrubber operation from the rollout of scanning attachments. Planned purchases, options, capacity, orders and installed operational equipment are different quantities. Keep each in its own field with a date, and avoid counting one hardware platform repeatedly when its new functions are announced.

Upgrade the label only when evidence changes

A later source can justify moving a record from pilot to paid deployment or recurring operation. Preserve the earlier state and explain the new evidence. Also retain the exact robot generation: a current product page cannot silently rewrite an older deployment. If the site, version or operating conditions remain undisclosed, publish that limitation even when the overall commercial relationship is confirmed.

Additional disclosed fields

Commercial-agreement example

GXO distinguishes a prior proof of concept from its Digit service agreement

Customer confirmedReviewed 2026-09-28

Sources 1

GXO multi-year agreement with Agility Robotics

GXO · Published 2024-06-27 · Source accessed 2026-09-28

Customer describes commercial live-warehouse operation after a pilot. Does not identify current Digit 5 hardware.

Expansion distinction

DHL separates existing Stretch operation from a proposed expansion under an MOU

Customer confirmedReviewed 2026-09-28

Sources 1

DHL Stretch commercial deployment and expansion MOU

DHL Group · Published 2025-05-13 · Source accessed 2026-09-28

Rollout distinction

Sam’s Club distinguishes an existing floorcare fleet from a scanning-accessory rollout

Customer confirmedReviewed 2026-09-28

Sources 1

Sam’s Club inventory analytics rollout on existing robotic scrubbers

Sam’s Club / Walmart · Published 2022-01-27 · Source accessed 2026-09-28

Relationships & deployments

Related reading is an editorial crosslink. Sourced connections describe relationships reported in the cited material. A link to a versioned profile does not establish compatibility with that version unless the connection note explicitly identifies it.

Record history & verified changes

A research review records when we checked a source. It does not mark a product launch or a new deployment.

Initial reviewed record. No subsequent field change has been recorded.