AI Smart Hardware

AI Hardware ODM Partner: Six Questions That Filter Suppliers

Engineers at a development bench in the factory
Development bench, where firmware scope and certification planning meet. Reference photography from our production line or product set.
TITLE: AI Hardware ODM Partner: Six Questions That Filter Suppliers DESC: A buying script for AI hardware ODM partner selection: MOQ, tooling, certification scope and importer duties, with the answers that reveal real capability. KEYWORDS: ai hardware odm partner, odm vs oem electronics, shenzhen supplier, ai hardware manufacturing, odm moq TAGS: ODM, sourcing, compliance, MOQ, Shenzhen Q: What is the difference between an ODM and an OEM supplier for AI hardware? A: An OEM supplier builds to your design and drawings; an ODM partner holds a platform you configure. In practice most AI hardware projects sit between the two, so ask which parts are fixed and which are open to change. Q: What MOQ should I expect from a Shenzhen AI hardware supplier? A: Published policy at WingPhoenix starts at 500 units for standard builds, 300 for AI glasses and 50 for service robots quoted per project. White-label firmware or app work starts at 2,000 units because it carries engineering time.

Most AI hardware sourcing failures are not factory failures. They are specification failures: the buyer asked about price and lead time, the supplier answered those two questions well, and nobody established who owns the tooling, which certification scope is booked, or what happens when the second hardware revision changes the radio module. A structured script of six questions filters suppliers faster than any factory tour. The answers below reflect published policy you can hold a supplier to in writing, and they apply whether you are buying AI device line hardware or a private-label build.

1. Where does your platform end and my design begin?

This is the OEM versus ODM question, and vague answers are a warning sign. A genuine ODM partner can name the fixed elements: enclosure family, PCB outline, sensor set, firmware stack. It can also name what is open: logo, packaging, colour, app skin, wake word, language pack. If a supplier claims everything is customisable, they are either an OEM contract manufacturer with no platform, or they are quoting engineering you have not scoped. Ask for the change list in writing before the quotation. For a platform-based route, the OEM/ODM services page sets out the usual configuration boundaries.

2. What are the real MOQs, and what drives them?

MOQ is not one number. It is a ladder, and each rung has a reason. A supplier who cannot explain the reason is guessing.

ConfigurationPublished MOQWhat drives the threshold
Standard build500 unitsComponent reels and line setup
Logo printing500 unitsPad or screen fixture
Custom packaging1,000 unitsPrint run and die-cut tooling
Firmware or app white-label2,000 unitsEngineering and test time per release
AI glasses300 unitsLower unit volume, higher assembly value
Ring, education, companion1,000 unitsSmall-format assembly and test fixtures
Service robots50 units, quoted per projectIntegration and risk assessment work

Ask what happens below the threshold. A supplier that will run 200 units at a higher unit cost is more useful to a pilot than one that refuses outright.

3. Which certification scope is booked, and per which revision?

Certificates are not a factory attribute; they are a test scope booked with an accredited laboratory per hardware revision. Documents supplied per model and revision typically include CE RED (EN 300 328, EN 301 489, EN 62368-1), FCC Part 15 B/C, UKCA on request, RoHS 3, REACH SVHC screening, battery UN38.3 plus SDS, and EN 1811 nickel release where the product touches skin. Toy scope (EN 71-1/-2/-3, EN 62115, Toy Safety Directive 2009/48/EC) is decided by the age grading printed on the packaging, not by the buyer's intention. For service robots, expect an EMC and low-voltage scope, a class 1 laser statement for the LiDAR, and a documented risk assessment. If a supplier says "we are CE certified" without naming the standard and the revision, treat the answer as incomplete.

4. How is the build tested, and at what AQL?

QC gates are the cheapest insurance in the order. Ask for the sequence: IQC on incoming components, IPQC in process, FQC before packing, OQC on the finished lot, at AQL 2.5 major and 4.0 minor. Ask who signs the OQC record and whether you receive it. The how we build and test page shows what that looks like on a real line, and it is a fair benchmark for any supplier you are comparing.

5. What are the commercial and logistics terms?

Get the terms in one place before negotiation starts. Samples run 3-5 days from stock and 7-15 days configured, with sample cost credited against mass production. Production is 25-35 days, 30-40 for education builds, and 12-20 weeks where ODM tooling is involved. Shipping is EXW, FOB Shenzhen, or DDP by air or sea. Warranty is 12 months with 2 % free replacement parts shipped with the order. Then separate the supplier's obligations from yours: EU and UK importer duties such as WEEE, BattG, DEEE/Triman, EORI and VAT sit with the importer, not the factory. A supplier who blurs that line is a compliance risk.

6. What will this product not do?

This question separates serious partners from order takers. Health metrics are wellness guidance, never diagnosis. Translation output is a reference translation, not a certified, legal or medical one. A companion robot is not a monitoring or emergency-response device. Google Play and GMS are not licensed by default. If your supplier volunteers these limits before you ask, their engineering team is reading the same specification you are. Before you commit, work through the how to vet a supplier checklist against the product catalogue, then send the specification with your answers to these six questions attached.

Questions buyers ask

What is the difference between an ODM and an OEM supplier for AI hardware?

An OEM supplier builds to your design and drawings; an ODM partner holds a platform you configure. In practice most AI hardware projects sit between the two, so ask which parts are fixed and which are open to change.

What MOQ should I expect from a Shenzhen AI hardware supplier?

Published policy at WingPhoenix starts at 500 units for standard builds, 300 for AI glasses and 50 for service robots quoted per project. White-label firmware or app work starts at 2,000 units because it carries engineering time.

Related: more on ai smart hardware · buyer guides · customisation tiers