AI hardware quotes are easy to misread. A product may combine an enclosure, PCB, radio module, battery, microphones, camera, display, sensors, firmware, app, cloud service, AI model, test fixtures, packaging, and market-specific evidence. Two suppliers can answer the same email while pricing different combinations of those layers.
The first task is not “get the lowest price.” It is to define what the price is supposed to represent.
1. Name the quote level
| Quote level | What it can support | What must be visible |
|---|---|---|
| Rough-order range | Route selection and budget screening | Reference, architecture direction, assumptions, volume scenario |
| Sample quote | A named prototype or sample revision | Sample type, quantity, pass criteria, temporary parts, handover |
| Engineering / NRE quote | Design, integration, firmware, DFM, fixture, or validation tasks | Tasks, outputs, milestones, inputs, changes, exclusions |
| Tooling quote | Named custom parts and tool trials | Tool type, material, finish, cavities, ownership, revisions |
| Pilot or production quote | A controlled product revision at stated quantities | BOM, drawings, tests, packaging, commercial basis, alternates |
If the architecture is still open, request route options and a rough-order range. If the team needs a functional prototype, request one sample scope. Calling either response a mass-production quote creates false precision.
2. Give the supplier one controlled configuration
A useful RFQ identifies exactly what is being priced. Use a reference product plus marked changes, an existing supplier platform, a prototype revision, or a controlled package of CAD, drawings, BOM, and software requirements.
- Configuration name: one version with defined options—not several alternatives hidden in one total.
- Reference and delta: what should stay, change, or be proposed.
- Physical definition: dimensions, weight direction, materials, finish, controls, connectors, battery, and accessories.
- Electronics definition: processor or performance target, radios, sensors, audio, camera, power, charging, storage, and approved or prohibited modules.
- Files and revision: current CAD, drawings, BOM or block diagram, UI flow, firmware notes, artwork, and packaging files, each versioned or dated.
Ask for separate options when battery, radio, enclosure process, sensor, display, packaging, or software scope changes.
3. Define what the next sample must prove
A visual model, electronics bench prototype, interaction demo, integrated functional sample, and production-intent prototype are different deliverables. Name the user action and expected response; list the interfaces and failure states that must work; state what may remain temporary; and give measurable acceptance criteria.
Also require a written list of what the sample does not prove about tooling, compliance, reliability, production yield, or final unit cost.
4. Split hardware, firmware, app, cloud, and AI responsibilities
“AI included” is not a quote scope. Record who supplies, integrates, owns, maintains, and pays for each layer.
| Layer | Questions the quote should answer |
|---|---|
| Hardware | Which parts are standard, custom, substituted, customer-supplied, or provisional? |
| Firmware | Who owns source and binaries, controls keys and updates, fixes defects, and supports programming? |
| App / SDK | Which platforms, accounts, APIs, source files, store submissions, languages, and maintenance are included? |
| Cloud / AI | Whose account, model, data flow, usage fee, service limit, and change responsibility are assumed? |
| Production test | Who develops fixtures, software, golden units, limits, logs, calibration, and failure handling? |
Separate one-time engineering, per-unit hardware, tooling, fixtures, laboratory work, and recurring software or cloud charges. Otherwise a low unit price may hide the largest lifecycle cost.
5. State quantities and the commercial basis
- Sample quantity by revision and destination.
- Pilot quantity and realistic production quantity breaks.
- Currency, tax basis, delivery term, destination, payment milestones, and quote validity.
- Customer-supplied parts, nominated vendors, approved alternates, and long-lead items.
- Treatment of scrap, overage, rework, engineering changes, and material price changes.
MOQ is not a universal property of a supplier. It may be driven by a display, battery, PCB panel, custom color, package printing, component reel, or production-line economics. Ask which item creates each minimum.
6. Put target market and compliance scope into the RFQ
Market and intended use affect design inputs, documentation, testing, labels, and packaging. For EU products that require CE marking, the manufacturer must identify applicable requirements, complete the conformity route, prepare technical documentation, and issue the declaration of conformity. A supplier report alone is not a general “CE certificate.”
For U.S. radio-frequency devices, the FCC equipment-authorization route depends on the exact device and configuration. A certified transmitter module can help, but host integration, labeling, RF exposure, antenna, and other conditions still need review.
If the product contains lithium batteries and will ship by air, identify the exact cell or battery and ask whether the manufacturer or distributor can provide the UN 38.3 test summary. Shipping configuration remains separate from product design.
This is planning guidance, not a product-specific compliance determination. Final requirements depend on the product, use, claims, market, operator, importer, and controlled configuration.
7. Require assumptions, exclusions, and alternatives
- Every missing input replaced by an assumption.
- Standard parts and processes versus custom work.
- Excluded engineering, firmware, app, cloud, testing, certification, packaging, logistics, tax, and after-sales work.
- Customer dependencies and decision deadlines.
- Items that can change price, MOQ, timing, or feasibility.
- Recommended alternatives and the tradeoff each one changes.
A quote without assumptions is not more certain. It only hides where the uncertainty went.
8. Normalize quotes before comparing totals
| Comparison field | What to record |
|---|---|
| Product baseline | Revision, option, modules, materials, finish, accessories, packaging |
| Deliverable | Sample type, quantity, files, source, fixtures, reports, acceptance evidence |
| One-time charges | Engineering, tooling, fixtures, artwork, setup, laboratory work |
| Recurring charges | Per-unit hardware, licensing, app, cloud, AI usage, support |
| Commercial basis | Quantity, currency, tax, delivery term, destination, payment, validity |
| Uncertainty | Assumptions, exclusions, alternates, dependencies, unresolved risks |
Only compare totals after each row describes the same configuration and scope. Otherwise compare routes, not prices, and request a revised quotation.
A minimum quote-readiness package
- One-page context: user, use case, target market, reference, current stage, and next decision.
- Controlled configuration: named version, fixed requirements, flexible items, and prohibited substitutions.
- Sample or production scope: quantity, deliverable, acceptance criteria, and destination.
- Technical package: available CAD, drawings, BOM or block diagram, interfaces, software responsibilities, artwork, and packaging direction.
- Quote template: one-time, per-unit, recurring, optional, excluded, assumptions, quantity breaks, and terms.
- Open-question log: each missing input, owner, due date, and effect on price or route.
Frequently asked questions
Can a supplier quote from only a reference?
A reference can support a rough route or budget discussion. A comparable quote also needs the changes, configuration, sample goal, quantity, target market, and included engineering and software scope.
Do I need a complete BOM?
Not for every early estimate. A production-intent quote needs a controlled configuration, BOM or proposed equivalent, drawings, test scope, quantities, and commercial terms.
Why do quotes vary so much?
They often describe different products or scopes. Normalize the configuration, deliverables, charges, terms, assumptions, and exclusions before comparing totals.
Should certification be included?
Ask suppliers to separate pre-compliance work, formal testing, documentation support, retesting, and exclusions. Final obligations depend on the exact product and market.
Official references for planning
- European Union: CE marking requirements and manufacturer responsibilities
- U.S. FCC: equipment-authorization procedures and guidance
- U.S. FCC: transmitter-module and host-product guidance
- IATA: lithium-battery transport and UN 38.3 information
Turn your current inputs into a quote-ready sourcing path.
Send one product reference and your current stage. Aixumo will help clarify the likely route, missing quote inputs, supplier types, sample sequence, and next useful sourcing action.