What is the SKU?
Materials, intended use, age grading, packaging, components and the claims a customer will see.
Market-readiness planning
Confirm the product before you make the promise.
Safety, wireless, privacy and data requirements depend on the actual SKU, users and sales markets. We build these questions into project discovery rather than attaching broad certification claims to every product.
A working principle
One character can create several different regulatory products.
A decorative plush, a Bluetooth speaker toy and a cloud-connected AI companion may share the same character art but carry materially different responsibilities. Product readiness starts by separating those configurations early.
What is inside it?
Battery, charging, radio module, app, microphone, speaker and the product’s physical interfaces.
What moves where?
Voice, account, analytics and knowledge data; storage region, vendors, permissions and deletion path.
Where will it sell?
Country or region, importer and retailer requirements, language, labelling and documentary obligations.
Project decision table
Questions that prevent a late-stage surprise.
Target marketCountry and selling channel
Confirm where the SKU is offered and who imports, distributes or sells it. Marketplace and retailer rules can sit alongside statutory obligations.
Product classAge, function and claims
Check the intended user, whether it is a toy or another consumer product, and whether product claims change the assessment.
Connected hardwareBattery, radio and charging
Determine whether power, wireless modules or other electronics create a separate testing, documentation or labelling workstream.
AI & dataVoice, personal data and cloud
Map the data flow and decide model, hosting, retention and contractual safeguards with the project’s actual audience and geography.
EvidenceFactory and project records
Collect the build version, materials, test scope, labels, manuals and approval record for the specific product configuration.
Important boundary
This page is a planning tool, not legal or certification advice.
We do not publish a blanket statement that every product meets every standard. The correct route depends on the final product, factory, documentation, target jurisdiction and qualified specialists where required.
- Give us intended sales markets at the beginning—not just at production
- Flag any electronics, microphones, connected app or cloud service
- Keep age range and marketing claims aligned with the intended configuration
- Plan time and budget for appropriate review, testing and documentation