Compliance
Product Compliance
Product compliance should be tied to the exact item being sold, its intended use, technical features, claims, supply chain and route to market. The company needs a controlled method for identifying applicable requirements, obtaining evidence, approving changes and deciding whether a product is ready for China.
Building Compliance into the Product Decision
01
Create the controlled product definition
Record models, specifications, materials, components, intended users, functions, claims, packaging and manufacturing sites. Compliance decisions should be traceable to a specific version of the product.
Product baseline: Model / Function / Materials / Claims / Manufacturer
02
Map requirements to evidence
For each identified requirement, record the responsible party, evidence needed, status and decision date. Standards, testing, certification, labels and documentation should sit in one readiness view.
Requirement map: Requirement / Evidence / Owner / Status / Expiry
From Product Specification to Market Release
03
Control suppliers and technical changes
Supplier substitutions, component changes, firmware updates, manufacturing moves and artwork revisions can affect earlier conclusions. Procurement and product teams need a formal notification and review route.
Change record: Change / Affected evidence / Reviewer / Release decision
04
Set a documented release gate
No commercial release should depend on scattered emails or assumptions. Management needs a record of completed evidence, accepted exceptions and the person authorised to approve launch.
Release decision: Evidence / Exceptions / Conditions / Approver
Compliance Decisions Before Commercial Launch
Guide
Guidance on product definitions, requirement mapping, testing, certification, labels, supplier controls, technical files and release decisions.
Comparison
Comparisons of product, testing and certification routes across scope, evidence, timing, cost, responsible parties and commercial flexibility.
Review
Reviews of technical specifications, claims, standards, supplier evidence, labels, change control, documentation and market-release readiness.
FAQ
Answers to management questions on applicable requirements, tests, certificates, labels, suppliers, product changes, records and release authority.
Resources
Product files, requirement registers, evidence lists, supplier declarations, change records and release checklists for cross-functional teams.
Tool
Tools for requirement mapping, evidence-gap review, supplier follow-up, change assessment and product-release decisions.
Case
Examples of how foreign companies organised product evidence, resolved supplier gaps and prevented uncontrolled changes from reaching the market.
News
Developments affecting product standards, certification, technical documentation, labelling and market-access planning in China.
How to Use the Product Compliance Hub
Use Guide to frame the work, Comparison and Review to test alternatives and risk, and FAQ and Resources to prepare the working file. Tool and Case support the management recommendation; News confirms whether the underlying assumptions remain current.
Management should approve the controlled product definition, requirement map, evidence owners and release authority before launch. Current requirements should be confirmed for the specific product, and every material technical or supplier change should return to the documented review process.