Companion Robot Content Pack: From Demo to Shelf
A trade-show demo runs on a single firmware image with English prompts, a generic wake word and cached audio clips. A shelf-ready companion robot must deliver consistent, compliant speech behaviour across all target markets — without relying on cloud inference, real-time translation or third-party APIs. That gap is not bridged by software alone. It is closed by hardware revision control, certification scope alignment and deliberate content scoping at the factory gate. This article outlines where procurement decisions intersect with regulatory boundaries and engineering reality.
Content Packs Are Not Apps — They Are Firmware-Bound Assets
A companion robot content pack includes voice prompts, response logic, phoneme libraries, and context-aware dialogue states. These are compiled into the firmware image during build. Unlike mobile apps, they cannot be updated over-the-air without triggering a new CE RED and FCC test cycle. The companion robot supports up to four language packs per hardware revision, but each must be selected before firmware finalisation. Adding Dutch or French after sample approval means delaying production by 7–10 days for recompilation and retesting — and revising the CE RED document checklist.
Wake Word Customisation Is a Compliance Trigger
The wake word defines the device’s radio emission profile under EN 300 328. Changing it alters the acoustic trigger model, microphone sensitivity thresholds and audio buffer handling — all of which affect RF stability and electromagnetic compatibility. Custom wake words require full EMC revalidation and must be booked with the accredited lab alongside the hardware revision. This is why OEM/ODM services include wake word confirmation as a mandatory sign-off step, not a post-shipment option.
Offline Content Means Localised Assets — Not Just Translated Text
Offline operation requires embedded speech synthesis, grammar rules, and culturally appropriate response templates — all stored in flash memory. A French content pack does not reuse English phonemes with translated subtitles; it embeds French prosody models, regional intonation cues and locally validated vocabulary. This is why MOQ for custom language packs starts at 1,000 units: enough volume to justify dedicated firmware builds and lab validation. For reference, the learning pad follows the same principle — no cloud dependency, no fallback to English when connectivity drops.
Compliance Starts with What the Device Says — and When
Voice output falls under EN 62368-1 (audio pressure limits) and EN 301 489 (acoustic emissions). Dialogue length, repetition frequency and maximum loudness are part of the safety test plan. A content pack that triggers rapid-fire responses every 1.2 seconds may fail acoustic stress testing — even if the hardware passes standalone EMC. That is why our how we build and test process includes dialogue timing audits during FQC, aligned to the published content spec.
| Decision Point | Factory Gate | Certification Impact | Procurement Note |
|---|---|---|---|
| Wake word selection | Firmware sign-off | Full CE RED + FCC retest required | Book lab slot before sample approval |
| Language pack count | Build configuration | No impact if within original test scope | Max four per revision; confirm before MOQ |
| Offline voice assets | Firmware compilation | Affects flash memory allocation and thermal profile | EN 62368-1 audio pressure tests use final assets |
| Dialogue timing logic | FQC audit stage | Part of acoustic stress test plan | Must match signed content spec |
| Age grading (if applicable) | Packaging design sign-off | Triggers EN 71-1/-2/-3 and EN 62115 booking | Grading printed on box determines toy scope |
These constraints apply equally across the product catalogue, whether selecting the smart health ring or the Health & Wellness line. Voice behaviour is never an afterthought — it is a defined, tested, documented layer of the product. To avoid delays, align your content requirements with our how to vet a supplier checklist and submit your full language and wake word specification using the send us the specification form before placing the sample order.
Questions buyers ask
Can I change the wake word after mass production?
Wake word customisation must be confirmed at firmware sign-off. Each revision requires retesting for CE RED and FCC Part 15 compliance. No field updates are certified.
Do your companion robots ship with preloaded content in Dutch or French?
Language-specific content packs are built per order. Offline voice assets, dialogue trees and pronunciation models are locked at firmware release — not downloaded post-shipment.
Related: more on ai companions · buyer guides · customisation tiers