Will every robot made in China get a permanent identity code? A draft proposes ‘one machine, one code’
A five-page consultation would require manufacturers of industrial, service and special-purpose robots made in China to register products, mark every unit before factory release and file the used code within 20 working days. It is not yet a final rule.
The short version
- What happened
- The consultation covers complete robots manufactured in China, including industrial, service and special-purpose robots, and makes manufacturers responsible for registration, marking and filing.
- Who it affects
- Robot buyers and workers could gain a clearer way to identify a machine and connect it to recalls or maintenance if access is usable and records stay current.
- What remains unproven
- The measures are a draft for public comment through 5 December 2026, not a final or commenced rule.
Keep in mind
The measures are a draft for public comment through 5 December 2026, not a final or commenced rule.
No final implementation date, complete penalty framework, platform specification or public-access model is provided.
The code is an identity and traceability mechanism, not evidence that a robot passed a safety, security or performance test.
The scope focuses on complete robots manufactured in China; treatment of imports, prototypes, components and rebuilds needs clarification.
The Impact of AI translated the Chinese sources; final interpretation should use the adopted Chinese text and official guidance.
Multi-source analysis · 3 linked sources. Primary analysed source date: 6 November 2026. Earliest linked supporting source: 30 October 2026.
Read the full report · 8 min The evidence, methods, implications and limitations
The answer: the draft creates a product identity, but the rule is not final
China's Ministry of Industry and Information Technology has opened consultation on five pages of interim measures for robot product identification codes. The proposal covers complete robot products manufactured within China, explicitly including industrial, service and special-purpose robots of different forms. Manufacturers would be responsible for assigning and filing the code. The ministry describes the goal as a unified robot 'identity card' supporting manufacturing discipline, safety governance and risk prevention from the supply side.
The code has four components: manufacturer code, product-description code, product sequence number and other code. Assignment would follow GB/T 48541-2026, China's newly published recommended national standard for robot identification numbers, and related standards. The official standards record says GB/T 48541-2026 was published on 30 October and is scheduled to take effect on 1 February 2027. The draft connects an administrative filing platform to that technical coding structure.
The qualification is essential. The ministry published the consultation on 6 November and invited comments through 5 December. The attachment is labelled a draft for comment. It does not state that every robot already carries the code, provide a final commencement date or show how consultation may change the provisions. It is a material proposal, not an active Breaking incident and not evidence that a nationwide traceability system is already operating.[1][2][3]
What manufacturers would register
A producer would register through a code-service platform, providing enterprise name, unified social credit code, legal representative and other entity information, plus its business licence and supporting documents. Product registration would add intended use, mechanical structure, power-supply method, communications method, company model designation, assembly-plant code, key components and software information. This could connect a legal maker and product family to each individual machine.
The platform would conduct a formal review within 10 working days. If materials were incomplete or failed the required form, the applicant would be told within five working days. When the enterprise name, legal representative, registered address or business scope changed, the manufacturer would have 20 working days from official approval to submit an update. The draft does not publish the complete data dictionary, say which fields will be public or explain how sensitive component and software information will be protected.
A registry can improve accountability only when records are accurate, changes are maintained and authorised users can query enough information to act without exposing unnecessary data. The proposal allows MIIT to commission a third-party technical-support institution to operate the platform. It does not identify that operator, specify retention, describe cross-border access or give a launch date. Those choices will determine whether the registry is a practical lifecycle tool or mainly a compliance database.[2]
The distinction that matters
How the proposed identity would be created
The consultation links the manufacturer, product model and individual unit through a service platform.
Register maker
Submit entity and licence details
Manufacturer record
Register product
Describe use, structure, communications, parts and software
Product record
Mark unit
Assign digital, human and machine-readable code
One machine, one code
File use
Report assignment within 20 working days
Lifecycle record begins
‘One machine, one code’ starts before factory release
A manufacturer would request sequence numbers according to real production need. Annual applications should generally not exceed 300% of the previous year's actual output. A company needing more could submit production evidence; a new producer or one operating for less than a year could rely on designed-capacity material. The cap appears intended to discourage code stockpiling while leaving a route for rapid growth, although the draft provides no evidence on likely demand or administrative capacity.
Before factory release, the manufacturer would assign a code to every robot and keep it consistent with the product's real information. The draft requires at least three forms: digital-storage, human-readable and machine-readable identifiers. They must correspond to the same record. The mark should be clear, visible and durable, difficult to damage or replace, and intended to remain unchanged, unalterable and unerased through the product's life.
Within 20 working days of assignment, the manufacturer would file the used code and accept responsibility for truth, accuracy and completeness, retaining supporting material. Codes obtained in the previous year but unfiled by 31 January would be cancelled. Robots sold before the measures take effect would not necessarily receive the new standard code: the proposal says makers should file their existing self-defined product serial numbers. That creates a transition record but not identical marking across old and new fleets.[2]
Traceability can support safety, but a code is not a certificate
A durable identity can help a buyer, maintainer or regulator distinguish one physical robot from another, connect it to a manufacturer and model, and follow software or component changes. In a recall or incident investigation, that can narrow the affected population. In a second-hand market it could strengthen provenance. In industrial fleets, a shared identifier may improve maintenance records where machines from several suppliers operate together.
The code itself does not show that a robot is safe, secure, reliable or suitable for a task. It is an index into information. If the record is wrong, late or inaccessible, the identifier can create false assurance. The draft supplies no performance tests for perception, manipulation, cybersecurity or human interaction. Those require separate product standards, conformity assessment, incident reporting and operational evidence. The proposal's safety value depends on whether recalls, maintenance and investigations actually use the identity.
The strongest human benefit would be a simple path from a code to current warnings, recall status and responsible manufacturer without exposing private operational data. A permanent identifier also creates risks: cloning, unauthorised rewriting, tracking or registry enumeration. Security tests should ask whether the three marking forms resolve to the same machine after wear, software updates, component replacement, resale and decommissioning—and whether an unauthorised party can misuse the link.[1][2][3]
What remains unresolved—and what would change the assessment
The public text lacks a detailed standalone penalty schedule. It assigns duties and describes cancellation of unused codes, supervision and policy support, but consequences for inaccurate filing, tampering, failure to mark or failure to update need clarification. GB/T 48541-2026 is a recommended national standard; reference from adopted measures could make its coding method operationally expected within scope, but that relationship must be read from the final text rather than assumed from the consultation.
Scope questions remain. The definition focuses on complete robots manufactured in China. It does not clearly resolve imported complete robots, components sold separately, software-only agents, prototypes, research devices or machines substantially rebuilt after sale. Exported Chinese-made robots may carry the code, but whether overseas owners can query or update the record is unexplained. Consultation responses and final guidance should address these cases before companies redesign production systems.
Confidence would rise with a final text stating commencement, transition, scope and enforcement; a published platform specification; and trial access for manufacturers, maintainers and buyers. MIIT could report registrations, codes assigned, timely filings, cancellations, corrections, duplicate detections and successful queries. For now, the finding is bounded: China proposes a concrete lifecycle identity system for domestically made robots. It may improve traceability if adopted and implemented well, but it does not certify safety and no outcome evidence shows improved recalls or fewer incidents.[1][2][3]
Keep following the evidence
Join The Impact Brief founding list for selected AI reports, their effect on people and the evidence limits. Read a sample first.
Continue the story
Read next
Continue exploring manufacturing: compare the finding and its evidence limits.
AI on the factory floor: who gets the gains, and who carries the risk?
A robot may take over a task while a worker keeps responsibility when something goes wrong. IBM’s survey of 800 leaders points towards job redesign, but its promises of higher productivity and fewer staff are expectations, not measured results.
Read the next reportExplore the full source and evidence record
What this means for people
- Robot buyers and workers could gain a clearer way to identify a machine and connect it to recalls or maintenance if access is usable and records stay current.
- Manufacturers would need registration, marking and filing systems tied to production, software and component records, with burdens for smaller producers.
- Second-hand owners and overseas users may benefit from provenance, but the draft does not explain their query or update rights.
Global context
Product identifiers already support recalls and maintenance in sectors such as vehicles and medical devices. Applying persistent identity to robots could make software and lifecycle accountability more concrete, but international usefulness depends on interoperable standards, secure registries and access rules for overseas owners and regulators.
What the evidence does not yet show
- The measures are a draft for public comment through 5 December 2026, not a final or commenced rule.
- No final implementation date, complete penalty framework, platform specification or public-access model is provided.
- The code is an identity and traceability mechanism, not evidence that a robot passed a safety, security or performance test.
- The scope focuses on complete robots manufactured in China; treatment of imports, prototypes, components and rebuilds needs clarification.
- The Impact of AI translated the Chinese sources; final interpretation should use the adopted Chinese text and official guidance.
What to watch next
- Changes between the consultation and final measures after 5 December.
- A commencement date, transition period and treatment of existing and imported robots.
- The platform operator, data fields, query rights, privacy controls and cybersecurity testing.
- Enforcement and remedy provisions for missing, false, cloned or altered codes.
- Evidence that the identifier improves recalls, maintenance or incident investigation rather than only registration volume.
Living evidence record
Impact record IAI-0U8FEDW
Evidence stage
Announced
Confidence
Supported
Reporting basis
Multi-source analysis
Independent or research support
Not yet
Record status
Monitoring
Last checked
7 November 2026
Source trail
3 direct sources across 2 source types.
People impact
Documented in this record.
Uncertainty
Limits and next checks are explicit.
Stages describe the evidence available—not whether a technology is good or bad. See the public method.
Evidence trail
Sources used for this report
Links checked 7 November 2026
Research question, topics and regions
China's draft lifecycle identification regime for domestically manufactured robot products
Topics: Robotics · Product identity · Traceability · Manufacturing · Safety governance · Standards
Regions: China · Asia & Middle East · Global
This report is labelled multi-source analysis. We summarise and analyse source material in our own words; company statements remain attributed claims until independently supported. Translated summaries preserve the meaning of the original source and link back to it. Read our editorial standards.
Reader commentary
What does this mean where you are?
Tell us what you have seen at work, in your community or in everyday life. A question is welcome too. No account is needed; we review notes before publishing them.
Explore commentary across the portal →Published reader notes
0No published reader notes yet. You can start the evidence-led discussion above.
Prefer a private correction or response? Contact the newsroom.