Robot Supplier Reference Checks: How Buyers Should Verify Similar Projects Before Award

The following scenario is illustrative and does not represent data from any specific deployment. A supplier's proposal includes a list of reference customers. It may show logos of well-known companies, a count of installations (“500+ robots deployed”), or case studies with photographs. For a buyer about to commit to a purchase, the question is not whether these references exist. The question is whether they are comparable to the buyer's project. A logo on a website may represent a robot that was supplied but not integrated. An installation count may include deployments that are nothing like the buyer's application. A case study may describe a pilot that never went into sustained production. This article explains how to verify supplier references before award, focusing on comparability, contractual role, and evidence quality.

A Customer Logo Is Not a Comparable Project Reference

A supplier may list a major manufacturer as a customer. That manufacturer may have purchased a completely different robot model for a different application, in a different industry, with a different integration scope. The logo proves that the supplier has sold equipment to a recognizable company. It does not prove that the supplier has experience with the buyer's specific task, part complexity, production volume, or system integration requirements.

Before treating a reference as evidence of capability, the buyer should ask:

• What robot model was deployed?
• What application was the robot used for?
• What was the supplier's actual scope of delivery (hardware only, hardware plus integration, full system including software)?
• When was the deployment completed, and is it still operational?
• How many units are in sustained production, as opposed to pilot or demonstration?

If the supplier cannot answer these questions for a listed reference, the reference is a logo, not evidence. The buyer should not infer capability from it.

Project references are one evidence category within broader robot supplier due diligence, not a substitute for it.

Define Your Similarity Profile

To evaluate whether a supplier's reference is comparable, the buyer first needs to define what “comparable” means for their project. A similarity profile is a structured description of the project's key characteristics, used as a baseline for comparison.

The similarity profile should include:

• Application: The specific task (e.g., machine tending, bin picking, welding, dispensing, sanding)
• Payload and part characteristics: Weight, dimensions, material, surface, tolerance
• Process requirements: Cycle time, quality standards, throughput per shift
• Environment: Cleanroom, dusty factory, washdown area, hazardous zone, ambient temperature range
• System interfaces: PLC, WMS, MES, vision, safety controller, third-party equipment
• Scale: Number of robots, number of sites, number of shifts
• Region: Geographic location, regulatory environment, language, support timezone

Use a robot vendor comparison scorecard only after defining which evidence is relevant to the specific requirement.

Application and scale comparability

Two projects in the same industry are not necessarily comparable. A robot that tends a CNC machine in an automotive plant is not comparable to a robot that performs bin picking in the same automotive plant, even though both are “automotive manufacturing.” The application, payload, process, and integration requirements are different.

Similarly, a single-robot pilot is not comparable to a ten-robot production line. The pilot may have been supported by a dedicated engineering team, with no pressure to maintain uptime. The production line requires sustained operation, maintenance procedures, spare parts management, and operator training. The buyer should weight references by the similarity of application and scale, not by the impressiveness of the customer name.

Separate Hardware Supply From Integration Delivery

A supplier's role in a reference project may be limited to supplying the robot arm. The integration, EOAT design, programming, safety system, and commissioning may have been performed by a different company. If the buyer's project requires the supplier to perform integration, a reference where the supplier only supplied hardware is not evidence of integration capability.

The buyer should verify, for each reference:

• Did the supplier provide the robot hardware?
• Did the supplier design and build the EOAT?
• Did the supplier program the robot and integrate it with external systems?
• Did the supplier perform the safety design and risk assessment?
• Did the supplier commission the system on-site?
• Did the supplier provide ongoing maintenance and support?

Actual contractual role

The supplier's contractual role in a reference project determines what the reference proves. If the supplier was the hardware vendor, the reference proves that the hardware was purchased and, presumably, installed. It does not prove that the supplier can design a cell, program the robot, or integrate with a WMS. If the supplier was the system integrator, the reference proves integration capability but may not prove hardware reliability over time, because the hardware may have been serviced by the end user's maintenance team.

The buyer should ask the supplier to state, for each reference, what their actual contractual scope was. If the supplier is reluctant to disclose this, it may indicate that their role was narrower than the reference implies.

Version, Deployment Date, and Stage Matter

A reference from five years ago may involve a robot model that has been discontinued or significantly updated. A reference from a trade show demo may represent a prototype that was never deployed in production. A reference from a pilot that ran for three months does not prove sustained operation over years.

The buyer should verify:

• Hardware and software version: The robot model and controller software version used in the reference, compared to the version proposed for the buyer's project
• Deployment date: When the system went live, and whether it is still operational
• Current stage: Pilot, early production, sustained production, or decommissioned
• Operating hours: If available, the cumulative operating hours or number of completed tasks

For cross-country deployments, robot supplier support for global rollouts should be assessed separately from a single successful installation reference.

Pilot vs sustained operations

A pilot is a limited-duration deployment designed to prove feasibility. It is typically staffed by engineers, run under controlled conditions, and not subject to production pressure. A pilot that achieves 95% availability for two weeks does not prove that the system will achieve 95% availability over six months of three-shift operation with operator turnover, maintenance delays, and part variant changes.

Sustained production operation is a different evidence category. It demonstrates that the system can operate under real conditions, that maintenance procedures exist and are followed, that spare parts are available, and that the system has been updated and maintained over time. The buyer should weight sustained production references more heavily than pilot references, and should be skeptical of references that do not specify the deployment stage.

Questions for a Consenting Reference Customer

If the supplier provides a reference customer who has agreed to be contacted, the buyer should prepare a structured set of questions. The goal is to verify the supplier's actual role and capability, not to obtain confidential business information.

Questions to ask:

• What robot model and software version were deployed?
• What was the supplier's scope of delivery and integration?
• Were there any significant issues during commissioning, and how were they resolved?
• Has the system been updated since deployment, and were the updates smooth?
• What is the maintenance arrangement, and is support responsive?
• Were operators trained by the supplier, and was the training adequate?
• What would you do differently if you were starting this project again?

The buyer should avoid asking for confidential pricing, internal production data, or negative opinions about the supplier that the reference customer may not be comfortable sharing. The goal is to verify facts and gather operational insights, not to conduct an audit of the reference customer's business.

Corroborating a Reference Without Over-Claiming

A supplier's marketing materials are not independent verification. The buyer should corroborate references using publicly available information:

• Joint press releases: If the supplier and the customer issued a joint announcement, it confirms the relationship and may describe the scope
• Public case studies: If the customer published a case study on their own website or in a trade publication, it provides an independent perspective
• Conference presentations: If the project was presented at an industry conference, the presentation may include technical details not in marketing materials
• Site visits: If the reference customer agrees to a site visit, the buyer can observe the system in operation and ask questions directly

Corroboration strengthens a reference but does not prove that the supplier will perform identically on the buyer's project. The buyer should use corroborated references as evidence of capability, not as a guarantee of outcomes.

What a Reference Cannot Prove

Even a well-verified reference has limits. A successful deployment at another site does not prove that:

• The buyer's network and IT environment will support the same integration
• The buyer's part variants will achieve the same cycle time or quality
• The buyer's safety assessment will reach the same conclusions
• The buyer's operators will achieve the same productivity after training
• The buyer's maintenance team will resolve issues at the same speed

Each of these depends on site-specific conditions that the reference cannot validate. The reference proves that the supplier has experience with a similar application. It does not replace a project-specific pilot, validation, or acceptance test.

Reference Red Flags and Missing Evidence

The following patterns should prompt the buyer to question a reference:

• Only trade show demos: No sustained production references, only demonstrations at exhibitions
• Unexplained integration role: The supplier cannot describe what they did versus what others did in the project
• Version mismatch: The reference uses a different robot model or software version than proposed, with no explanation of how the capability transfers
• Marketing-only evidence: The reference exists only as a website case study, with no verifiable deployment date, location, or contact
• Reluctance to provide details: The supplier is unwilling to discuss the reference in any specificity, citing confidentiality for information that is not actually confidential

A reference that cannot withstand basic scrutiny is not a reference. It is a marketing claim. The buyer should treat it accordingly and request evidence that can be verified.

Reference-Check Worksheet

The following worksheet structure can be used to document reference checks:

Each reference should be documented in this format. The worksheet is the buyer's evidence that the reference check was performed, not just a list of logos from the supplier's presentation.