Certification Cost Estimator
What FCC, CE, UKCA and the rest actually cost a hardware product, line by line, with the lab turnaround for each one and the two or three levers that move the total by a factor. Lab and programme fees only - engineering is separate, and the page says where.
- You selected 2 markets. Most of the radio and emissions data is reused across them, which is why the second and third markets cost a fraction of the first. Decide the full market list before testing starts, though: adding a market afterwards can mean a return visit to the chamber for the deltas, and Japan reuses the least.
- Buying a pack from a supplier who already holds IEC 62133-2 approval for that exact pack, rather than having one built to your drawing, removes the longest battery item. It constrains your mechanical design, which is why this decision belongs in the enclosure review and not after it.
- Design for compliance before you book a chamber. Emissions failures are almost always a clock, a switching regulator, a cable or a return path, and all four are cheaper to fix in layout than in a shielding can retrofitted after the fact.
Line by line
Pre-compliance EMC scan
A day or two in a chamber before formal testing. Skipping this is the most expensive saving in hardware: a radiated-emissions failure found at the formal test costs you the retest fee and six weeks of schedule, and it is the failure most first boards have.
FCC with a pre-certified module
You inherit the module's FCC ID, which removes the whole intentional-radiator campaign. The conditions are real, though: the module's approved antenna, its approved layout keep-out, and the host label carrying the module's ID. Deviate and the grant does not cover you.
CE marking, Radio Equipment Directive
RED covers three things at once: the radio itself, electromagnetic compatibility, and electrical safety. A pre-certified module cuts the radio part, not the other two.
RoHS and REACH documentation
Mostly collecting declarations from suppliers. Cheap unless a supplier will not answer, at which point it is a sourcing problem.
EU Authorised Representative
An annual service fee, not a test. Required on the packaging and in the declaration of conformity.
Battery pack safety
The cell you bought is almost certainly already certified. The pack you built around it is not: the protection circuit, the welds, the enclosure and the charging regime are what gets tested, and a change of cell supplier restarts it.
UN 38.3 transport testing
Not a market approval. Without it no airline, courier or freight forwarder will legally carry your product, which makes it a shipping blocker rather than a selling one. Do it before the first production run leaves the factory.
Bluetooth SIG declaration and listing
Not optional if the word Bluetooth or its logo appears anywhere on the product, the box or the app store listing - that is a trademark licence, not a technical requirement. The fee depends on your SIG membership tier, so check the current schedule rather than this band.
Technical file and declarations of conformity
The deliverable the authorities actually ask for, and the one most often assembled in a panic. It includes the risk assessment, the standards list, the test reports, the bill of materials and the artwork proofs.
What is in these numbers and what is not
Every figure here is a third-party fee: an accredited test lab, a certification body, a notified body, or a programme like the Bluetooth SIG. They are bands for a small product on a typical 2026 schedule in a North American or European lab, and they move with the lab, the country and how busy the chamber is. Treat them as a budget line to defend, then get two real quotes.
What is not in them: engineering. Designing for compliance, sitting with the test engineer, diagnosing the emission at 118 megahertz, re-spinning the board, writing the risk assessment and assembling the technical file are all work somebody has to do, and that work is usually a similar size to the lab invoice. If you are building the budget for a funding round, the honest number is this total plus the engineering to earn it.
The module decision is the whole ballgame
There is one choice on this page that dominates every other: whether the radio arrives as a pre-certified module or as a chip you lay out yourself. A module carries its own grant, so the intentional-radiator campaign that is the most expensive and slowest part of a wireless programme largely disappears. You pay for it in unit cost, a dollar or two, and in board area.
The arithmetic is unsentimental. Below roughly ten thousand units a year, the module is almost always right, and founders who go chip-down at that volume are usually optimising a cost that has not arrived yet against a schedule risk that has. Above that, and especially above a hundred thousand, the saved unit cost outruns the certification bill and chip-down becomes the correct answer. The mistake is doing it in the wrong order: ship on a module, learn what the product is, then take the radio in-house for the second revision when the volume justifies it.
One caveat that catches people: a module's grant only covers you if you obey its conditions. The approved antenna, the keep-out around it, the label carrying the module's identifier. Change the antenna and you are back to a permissive-change filing or a full certification, which is exactly the cost you thought you had avoided.
Pre-compliance is not optional, it is just early
The one line nobody budgets is a pre-compliance scan, and it is the one that pays for itself most reliably. A day in a chamber with a near-field probe, before you book the formal test, finds the clock harmonic and the cable acting as an antenna while they are still cheap to fix. Discovering the same thing at the formal test costs the retest fee, the slot you lose, and the weeks it takes to get another one. The reserve above exists because that happens often. More on the design side of it in EMC by design: passing FCC and CE the first time, and on where certification sits in a startup's plan in the hardware startup roadmap.
If this number is going in a plan
Certification is where hardware schedules quietly lose a quarter, almost always because the board was not designed for it and nobody owned the file. We take founders through this end of the project regularly, on our own designs and on boards other people built: how we work with hardware startups sets out the engagement, the MCU selector is where the module-versus-chip-down decision is actually made, and a free 30-minute technical call is the quickest way to find out which half of this estimate applies to your product.