Robot Country of Origin Evidence: What to Capture and How

Country of origin evidence for a robot system covers the complete system and its major subsystems. At the system level, it covers the country in which the robot was finally assembled and the country or countries in which its primary components were manufactured. At the subsystem level, it covers the origin of the compute platform, actuator assemblies, sensor systems, power management hardware, and communication hardware.

For software, origin evidence covers the country in which the software was primarily developed and the country in which any active update or telemetry services are hosted. The distinction between system-level origin and component-level origin is important because some procurement restrictions apply only to the complete system's country of assembly, while others extend to the origin of named component categories. A record that captures both levels of detail can respond to either type of restriction without requiring additional investigation after the restriction is identified.

Primary sources for country of origin evidence include the manufacturer's official technical documentation, the product certificate of origin issued at the time of import, customs clearance documents, and the manufacturer's product labeling where it identifies the country of manufacture. These sources have different reliability profiles: a certificate of origin issued by a national customs authority is a formal declaration subject to legal consequence, while a product label is a commercial claim that is not independently verified.

For high-stakes provenance reviews, the strongest evidence comes from customs documentation supplemented by the manufacturer's technical specification, which together establish both the formal declaration of origin and the technical detail about which components were sourced from which countries. For subsystem and component origin, the primary sources are the subsystem manufacturer's product datasheet and the robot manufacturer's integration documentation, which typically identifies major subsystem vendors.

These documents should be preserved as part of the provenance record, not merely referenced by name, so that a reviewer can access the original source material rather than relying on the deployment team's summary.

Component-level origin tracking is more labor-intensive than system-level tracking but is increasingly required for deployments subject to restrictions that identify specific component categories. The most commonly scrutinized categories are compute hardware, communication chipsets, and sensor systems, because these categories are associated with the most significant security and technology control concerns. For each major component in these categories, the deployment record should capture the component manufacturer, the component part number, and the country of manufacture as stated in the manufacturer's documentation.

Where the robot manufacturer has published a bill of materials or integration guide that identifies major subsystem vendors, that document is the starting point for component-level origin tracking. Where no such document exists, the deployment team may need to rely on physical inspection, which can identify component manufacturers from physical labels or markings but may not establish the country of manufacture without additional research.

Physical inspection findings should be documented with photographs and notes about what was visible and what remains uncertain.

Many robot systems are assembled in one country from components manufactured in several others, which creates ambiguity when origin-based restrictions are framed in terms of the country of origin of the complete system rather than the country of origin of specific components. When a system has a mixed origin, the deployment record should document the origin of each major subsystem as specifically as available evidence permits, note the basis for each origin determination, and identify explicitly which elements of the system's provenance could not be verified from available sources.

A mixed-origin system is not automatically disqualified from deployment by any particular restriction; the compliance determination depends on the specific language of the applicable restriction and the identified origins of the relevant components or subsystems. The deployment team's role is to establish the factual record as accurately as possible; the compliance determination against that record is a legal and procurement question, not a deployment documentation question.

A complete mixed-origin record, with gaps explicitly identified and the steps taken to fill them documented, supports a more efficient compliance review than a partial record with unexplained blanks.

Robot manufacturers sometimes change the origin of components across production runs without necessarily issuing updated model designations. A robot purchased in one procurement cycle may have components from different origins than a nominally identical robot purchased in a later cycle. For deployments that span multiple procurement cycles, the origin record should be specific to the individual unit rather than to the model, and any manufacturer communications about component source changes should be captured in the record.

When a field replacement part is used to repair or upgrade a deployed robot, the origin of the replacement part should be recorded as an update to the affected subsystem's origin record. Over time, a well-maintained origin record reflects the actual composition of the deployed system rather than its as-shipped state, which may diverge significantly from the current state in long-running deployments with multiple maintenance events.

• Obtain the certificate of origin from customs documentation for each imported robot
• Record the country of manufacture for the complete system from the manufacturer's official product documentation
• Document the manufacturer and country of origin for the compute platform, sensor arrays, actuators, and communication hardware
• Preserve original source documents rather than only recording summary information
• Note explicitly which origin fields were established from primary sources and which were estimated or inferred
• Record the origin of replacement parts when field repairs or upgrades affect major components
• Update the origin record when the manufacturer announces changes to component sourcing