Branded Wake Words: Licensing, Model Rights and ODM Projects

22 Sep 20261075 wordsWingPhoenix AI factory team

Wake word licensing is rarely on the first agenda of an ODM kick-off, and it is almost always on the last one. By the time tooling is booked, the trigger phrase, the acoustic model behind it and the runtime that executes it may belong to three different parties. The purchasing manager who discovers this at pilot build stage has very little leverage left. This article sets out the IP questions worth settling before a purchase order, using the same sequence we apply to our own firmware and app white-label projects.

What exactly is being licensed

A wake word is not one asset. It is a phrase, a trained model that recognises the phrase, and an inference runtime that runs the model on the device. A supplier may own the runtime, license the model from a third party, and have no rights at all to the phrase you chose. Ask for a written schedule listing each component, its owner and the licence terms attached. If a supplier cannot produce that schedule, treat the project as unlicensed until they can.

The same discipline applies across a product family. A companion robot and a learning robot may share one trigger engine but carry different content licences, different age grading and different obligations. Bundling them into one agreement usually hides the differences rather than resolving them.

The clauses that decide ownership

Three clauses carry most of the risk. The first is assignment: does custom training data and the resulting model transfer to you, or does the supplier retain it and grant a licence back? The second is field of use: a licence for consumer hardware in the EU is not a licence for global distribution or for a different product category. The third is termination: what happens to devices already shipped if the licence lapses?

• Name the trigger phrase, model version and runtime separately, with an owner for each.
• State the territory, product category and channel the licence covers.
• Confirm whether custom-trained models are assigned to you or licensed back.
• Set out what happens to shipped units and spare parts if the licence ends.
• Require notice if the supplier's upstream licence terms change.
• Keep the licence schedule under version control alongside the hardware revision.

Where certification and licensing collide

Radio and safety testing is booked per hardware revision, and a change of wake word engine can be a change of firmware that affects the tested configuration. Under CE RED, the relevant standards are EN 300 328, EN 301 489 and EN 62368-1, with FCC Part 15 B/C for the US. If a licensed component is swapped after testing, the test scope may need to be re-booked with the accredited laboratory. That cost belongs in the project plan, not in a change request six weeks before shipment.

Platform rights and importer duties

Google Play and GMS are not licensed by default on any device we build. A buyer who assumes otherwise will discover the gap at the app store review, not at the factory. Distribution rights for app stores, voice assistants and content libraries sit with separate agreements, and each has its own territory rules. On the compliance side, EU and UK importer duties such as WEEE, BattG, DEEE/Triman and EORI/VAT registration remain with the importer of record, not the manufacturer.

Product category also changes the paperwork. A pocket translator produces reference translation output only. A companion robot is not a monitoring or emergency-response device, and health metrics are wellness guidance rather than diagnosis. Where a device is sold as a toy, the toy scope of EN 71-1/-2/-3, EN 62115 and Toy Safety Directive 2009/48/EC is decided by the age grading printed on the packaging and booked with an accredited laboratory per build. None of this is negotiable after the artwork is printed.

When to say no

A supplier who will not disclose the wake word licence chain is a supplier who will hand you that problem later, at your cost. The same applies to a supplier who offers a custom trigger phrase without a written assignment, or who treats platform rights as an implementation detail. Our own factory process documents the test scope per hardware revision for this reason, and buyers comparing suppliers should ask for the same evidence before samples. It is also worth reading the wider buyer resources on category-specific obligations before shortlisting.

For planning purposes, our published policy is straightforward: standard MOQ is 500 units, logo 500, custom packaging 1,000, firmware or app white-label 2,000, AI glasses 300, ring, education and companion models 1,000, and service robots 50 units quoted per project. Samples run 3 to 5 days for stock and 7 to 15 days configured, with sample cost credited against mass production. Production is 25 to 35 days, education 30 to 40 days, and ODM tooling 12 to 20 weeks. Terms are EXW, FOB Shenzhen or DDP by air or sea, with a 12-month warranty and 2 % free replacement parts shipped with the order.

Before you commit to tooling, send us the specification together with your intended trigger phrase, target territories and platform dependencies. We will return a written licence schedule alongside the quotation, so the IP position is settled while it is still cheap to change. Start at the contact page or review the product catalogue for comparable builds.

Questions buyers ask

Who owns the wake word model in an ODM project?

It depends on the contract, not the hardware. The trigger model, its training data and the runtime that executes it can each sit with a different party, so the purchase agreement must name each one separately.

Can a supplier reuse our branded wake word for another customer?

Only if the contract allows it. A custom trigger phrase trained on your data should be assigned to you with an exclusivity clause, while a generic engine licence may be shared.

Related: more on ai agents · buyer guides · customisation tiers