Custom Mobile Robot Base vs Turnkey Robot
Choose between a mobility base, configurable platform and complete turnkey robot according to integration responsibility and product strategy.
Technical guide · Last reviewed 18 August 2026
Robot Prototype Acceptance Test Plan
Turn prototype goals into measurable tests for payload, navigation, runtime, interfaces, safety behavior and recovery.
Who this is for
robot startups, product companies, universities, integrators and international OEM/ODM buyers
Link every test to a requirement
Turn prototype goals into measurable tests for payload, navigation, runtime, interfaces, safety behavior and recovery. For this part of the decision, document the current workflow, responsible users, normal operating conditions and exceptions. Avoid treating a brochure feature as evidence until the offered configuration and site assumptions are confirmed.
Ask the supplier to distinguish standard capability, project option, integration dependency and customer responsibility. Convert the answer into a measurable requirement or acceptance record wherever the outcome matters to safety, service level, custody, compliance or total cost.
Use representative payload and environment
Turn prototype goals into measurable tests for payload, navigation, runtime, interfaces, safety behavior and recovery. For this part of the decision, document the current workflow, responsible users, normal operating conditions and exceptions. Avoid treating a brochure feature as evidence until the offered configuration and site assumptions are confirmed.
Ask the supplier to distinguish standard capability, project option, integration dependency and customer responsibility. Convert the answer into a measurable requirement or acceptance record wherever the outcome matters to safety, service level, custody, compliance or total cost.
Test failures and recovery, not only normal tasks
Turn prototype goals into measurable tests for payload, navigation, runtime, interfaces, safety behavior and recovery. For this part of the decision, document the current workflow, responsible users, normal operating conditions and exceptions. Avoid treating a brochure feature as evidence until the offered configuration and site assumptions are confirmed.
Ask the supplier to distinguish standard capability, project option, integration dependency and customer responsibility. Convert the answer into a measurable requirement or acceptance record wherever the outcome matters to safety, service level, custody, compliance or total cost.
Record configuration, results and open issues
Turn prototype goals into measurable tests for payload, navigation, runtime, interfaces, safety behavior and recovery. For this part of the decision, document the current workflow, responsible users, normal operating conditions and exceptions. Avoid treating a brochure feature as evidence until the offered configuration and site assumptions are confirmed.
Ask the supplier to distinguish standard capability, project option, integration dependency and customer responsibility. Convert the answer into a measurable requirement or acceptance record wherever the outcome matters to safety, service level, custody, compliance or total cost.
A feature list is not an operating plan.
Projects become fragile when routes, users, exceptions, integrations and ownership are postponed until after purchase.
Use the pilot to answer a defined investment decision with agreed evidence—not simply to demonstrate that a robot can move.
Frequently asked questions
Should a prototype pass production tests?
The test level should match the milestone. A prototype may validate core risks while documenting work still required for production.
Who signs acceptance?
Named customer and supplier stakeholders should review evidence against the agreed milestone criteria.
What should we send for an initial assessment?
Provide the use case, users, environment, payload, route or workspace, systems to integrate, expected quantity, destination market and target timing. Sensitive details can follow under appropriate confidentiality terms.
What should appear in the quotation?
The quotation should identify configuration, scope, interfaces, deliverables, assumptions, exclusions, acceptance approach, support and commercial terms.
Related decision guides
Using ROS 2 in a Production Robot
Plan architecture, real-time boundaries, lifecycle, security, testing and support when moving a ROS 2 prototype toward production.
Robot Battery and Transport Certification Planning
Plan cell selection, pack design, BMS, charging, protection, thermal testing and transport documentation for mobile robots.