When you source an AI sex doll, you are buying two supply chains, not one: the doll factory and the electronics and software operation behind the AI features. Most sourcing failures come from the second chain. The silicone can be flawless while the app has no owner, the firmware has no update path, and the warranty quietly excludes every part that makes the product "AI".
This checklist is for brand owners, distributors and sourcing managers comparing suppliers in China. It covers the questions that separate a real AI product supplier from a trading company assembling off-the-shelf modules, and the contract terms that protect you after the deposit is paid.
Appearance gets a supplier shortlisted. Electronics, documentation and support decide whether the program survives.
Four supplier types, four risk profiles
| Supplier type | What they control | Typical strength | Typical weakness |
|---|---|---|---|
| Full-stack doll factory with in-house electronics integration | Body, molds, assembly, electronics integration, firmware loading, test | Traceability, service access, consistent quality | May still rely on a software partner for the app and cloud |
| Doll factory with a technology partner | Body and final assembly; partner owns the AI module and app | Good body quality, faster access to AI features | Split responsibility when something fails |
| Electronics integrator | Boards, sensors, firmware and app; buys dolls from a factory | Stronger software and electronics | Less control over the body and final QC |
| Trading company | Neither body nor electronics; coordinates suppliers | Convenient communication, mixed catalogues | Limited technical depth, weak traceability, slower problem solving |
None of these is automatically bad. A trading company can be useful for a small mixed order. The mistake is paying full-stack prices for a coordinator that cannot open a unit, explain the firmware or stock a spare board.
Separate the factory from the assembler
Ask five questions in the first call. The answers usually reveal the real structure.
- Who owns the molds? The factory, the customer, or a third party? For custom work, mold ownership should be written down.
- Who writes the firmware? In-house, a partner, or the board vendor? Ask for a version history.
- Who holds the app store and cloud accounts? If the supplier holds them, you have less control than you think.
- Who signs the test record? A named QC role, or the salesperson?
- Who handles an RMA for a failed sensor? The factory, the electronics partner, or the customer?
If the answers change between the sales call and the contract, treat that as a warning. A supplier that is vague about ownership before the order will be vaguer after it.
Software ownership and the app
The app is part of the product, not a free accessory. Before you sign, settle these points:
- White-label or shared app. A shared app may show other brands, collect data for the supplier, or be discontinued without notice.
- Source code and escrow. You may not need the source on day one, but you need a release plan if the supplier disappears.
- Store accounts. The Apple and Google developer accounts should be in your name, with the supplier as a contractor.
- Cloud accounts. The backend, database and voice-service accounts should be owned by you or held under a clear reseller agreement.
- API keys. Do not let the supplier hide usage inside a bundled fee with no visibility.
- Update policy. How often, for how long, and who pays for security patches after the warranty?
- End-of-life. What happens to cloud features if the service is retired? Is there an offline fallback?
- Data processing. A written agreement covering audio, transcripts, retention, deletion and subprocessors.
For privacy specifics, see our AI sex doll privacy guide.
Hardware documentation to request
A serious supplier can provide a document pack without weeks of delay. Ask for:
| Document | What it tells you | Red flag |
|---|---|---|
| Module-level BOM | Board revision, speaker, microphone, battery, sensors | Only a generic feature list |
| Board revision history | Whether changes are controlled | "Same as sample" with no version |
| Wiring and connector map | Serviceability and spare-part compatibility | No map, sealed electronics |
| Firmware version and changelog | Update discipline | No version number on the unit |
| Battery test summary | Transport and safety readiness | No UN38.3 or cell documentation |
| EMC and RF reports | Wireless module compliance | Report for a different module |
| Material reports | RoHS, REACH, silicone or TPE specification | Certificate with no model scope |
| Test record sample | What is checked per serial number | Only a final inspection photo |
Check that the report names the model and configuration you are buying. A certificate for a bare silicone sample is not a certificate for a heated doll with a radio module and a lithium battery.
Compliance is a chain, not a sticker
Depending on the destination, the finished product may need CE or UKCA marking, an EU or UK declaration of conformity, RoHS and REACH statements, EMC and radio test reports, battery transport documents and safety documentation. The importer is usually responsible for the final product, even when the factory supplies the reports.
Three practical rules:
- Match the scope. The report should cover the product, not just a component.
- Keep the technical file. Declarations, reports and labels should be stored with the SKU, not in a sales folder.
- Confirm the label. The importer name, address, model and warnings may need to appear on the product or packaging.
For market-specific detail, see our EU compliance guide and US import guide.
Sample and pilot plan
Do not scale from a hand-built demo. Order a sample from current production, then run a pilot of 10 to 20 units for 30 to 60 days. The goal is to find integration faults while the volume is small.
| Test | How to run it | What it reveals |
|---|---|---|
| Language and accent | Record 20 real phrases in the target accent, including names and interruptions | Whether the voice pack and microphone work outside the demo |
| Network failure | Disconnect Wi-Fi during a conversation and reconnect | Recovery behavior and user experience |
| Touch zones | Test every zone, then pose the doll and test again | False triggers and calibration drift |
| Heating | Log temperature at three points and test the cutoff | Hot spots and safety behavior |
| Cleaning | Clean according to the manual, then restart and test | Moisture ingress and port durability |
| App lifecycle | Pair, update, delete account, reinstall, pair again | Account and firmware lock-in |
| Service | Replace a speaker or sensor with the supplied procedure | Whether field repair is realistic |
| Shipping | Drop and compression test the packed carton | Damage risk to head and ports |
Keep a fault log with serial numbers, firmware versions and the exact conditions. A supplier that reviews the log with you is more valuable than one that only offers a replacement. See our sample order guide for the commercial side of the pilot.
Contract clauses that matter
| Clause | What to specify | Why |
|---|---|---|
| IP ownership | Molds, sculpts, firmware, app, content and brand assets | Prevents the supplier from reusing your custom work |
| Tooling | Who pays, who stores, who may use it, what happens on termination | Molds are often the largest custom investment |
| Exclusivity | Model, market, channel and duration | Avoids a competitor selling the same custom body |
| Change control | Written approval before any BOM, firmware or material change | Prevents silent substitutions |
| Warranty split | Body, skeleton, electronics, battery and consumables | Electronics fail differently from silicone |
| Spare parts | List, price, lead time and support period | Determines whether you can service the product |
| Firmware support | Update frequency, security patches and end-of-life notice | Connected products age quickly |
| Data processing | Roles, retention, deletion, breach notice and subprocessors | Privacy exposure sits with the brand |
| Penalties | Late delivery, quality failure and unreported changes | Gives the schedule teeth |
| Audit rights | Production visit or live video audit | Verifies the line, not the showroom |
For a clause-by-clause review, see 12 clauses to check before signing an OEM contract.
Cost and MOQ questions
Compare quotations on the same scope. Ask each supplier to separate:
- Unit price at sample, pilot and production volumes.
- Tooling and engineering (NRE).
- Sample cost and whether it is credited against the order.
- App white-label and cloud setup.
- Certification and test reports.
- Packaging, manual, charger and accessories.
- Freight, insurance and Incoterm.
- Spare-parts kit and warranty terms.
A low unit price with unbundled app, certification and spare parts is not a lower total cost. Our wholesale pricing guide explains how to normalize FOB, CIF and landed cost.
Red flags
- The demo app has no privacy policy or account deletion.
- "AI" turns out to be a fixed script with no model or update path.
- The supplier cannot say which board revision is in the unit.
- No serial-number test record, only a photo of the finished doll.
- The cloud account is in the supplier's name with no export option.
- Warranty covers the body but excludes electronics, battery and sensors.
- No spare modules are stocked, and lead time is "depends".
- EMC or RF reports are for a different module or a bare component.
- The factory video shows a showroom, not the production floor.
- The BOM changes after the sample without written approval.
Field notes from supplier audits
- Ask to see a unit opened. The inside tells you more than the outside. Look for strain relief, coating and connector quality.
- Ask for the last 20 RMA reasons, redacted. A supplier that tracks failure reasons can improve. A supplier that cannot is guessing.
- Ask for a firmware changelog. It shows whether updates are managed or improvised.
- Test in your language on a video call. Do not accept a pre-recorded voice demo.
- Confirm who pays return freight. A generous warranty with expensive return shipping is not generous.
- Visit or video-audit during production. A quiet line and a full burn-in rack tell different stories.
Frequently asked questions
How do I find a real AI sex doll manufacturer in China?
Start with suppliers that can explain both the body and the electronics, then verify with a video audit, a production sample, a serial-number test record and a spare-parts list. A manufacturer should be able to show the mold shop, the electronics bench and the burn-in area.
Should I buy from a trading company?
It can work for small or mixed orders, but you give up technical depth and traceability. If you use one, name the actual factory and the electronics partner in the contract, and require direct access to their QC records.
What MOQ should I expect?
Sample orders can be as low as one piece. Production MOQ depends on the model, packaging and electronics batch. Ask for both numbers, and confirm whether the sample cost is credited.
Who owns the app if I private-label?
It should be you, with the supplier as a contractor. At minimum, the store accounts and cloud accounts should be in your name, and the contract should include source-code escrow and an end-of-life plan.
What certifications should I ask for?
Ask for the reports that match your product and market: CE or UKCA, RoHS, REACH, EMC and RF for wireless, battery transport documents and material reports. Check the model and configuration named in each report.
About this guide
Prepared by the CoolMate Silicone Doll Factory team based on OEM/ODM sourcing, supplier audits and AI module integration for companion doll brands. Contract and compliance points are commercial guidance, not legal advice. Confirm requirements with your counsel, customs broker and testing lab.
Last reviewed: 28 October 2026 by the CoolMate production team.
