How to Get a Custom BLE Beacon Built and Shipped Without Designing Your Own Hardware
A beacon that’s 90% perfect off the shelf can still be useless. Wrong advertising interval, no room for your sensor data, a logo you can’t change. So you start pricing out a custom PCB and your timeline jumps from weeks to most of a year.
There’s a path between those two walls. You take an existing reference design from a contract manufacturer, change the parts that matter (firmware, branding, sometimes a sensor), and ship under your own name. This is the ODM route, and it’s how most “custom” beacons on the market actually get made.
This guide walks the full journey: deciding what custom means, picking a custom ble beacon manufacturer, scoping firmware, and getting samples through certification into production. Manufacturer selection and firmware scope decide whether you succeed, so that’s where we’ll spend the most time.
Step 1: Decide What “Custom” Actually Means for You
“Custom” covers a wide range, and each level has a different cost and lead-time hit. Before you talk to anyone, figure out which tier you need.
White-label ──► Custom firmware ──► Added sensors ──► Custom mechanical
$ / weeks $$ / weeks $$$ / months $$$$ / months
(logo, color) (advertising, (temp, motion, (new PCB, new
intervals, GATT) accelerometer) form factor)A white label ble beacon is the cheapest and fastest. You’re taking a stock unit and changing the case color, the silkscreen, maybe the packaging. No engineering, just a purchase order with cosmetic options.
Custom firmware is the next step up and where most products land. The hardware stays the same, but you change how it behaves: advertising format, intervals, GATT services, encryption, button actions. Same bill of materials, modest NRE (non-recurring engineering) charge, still measured in weeks.
Added sensors mean a board revision. Bolting on a thermistor, an accelerometer, or a hall sensor touches the PCB and usually means re-testing and re-certification. Plan in months.
Custom mechanical, a new enclosure or form factor, means injection mold tooling. That’s $$$$ and the longest lead time of all. Most founders don’t need it. Be honest about whether you do.
Step 2: Choosing a Manufacturer
This is the highest-leverage decision you’ll make, and unit price is the wrong thing to optimize first. A vendor that’s $0.30 cheaper but won’t expose firmware hooks or own certification can cost you months.
Most of the odm ble beacon supply chain runs through Shenzhen. MokoSmart and Minew are two well-known names that publish reference catalogs and customization options. I’m naming them as representative examples of the shenzhen ble beacon market, not ranking or endorsing either. There are dozens of capable shops, and a mokosmart custom beacon or a minew odm build follows the same evaluation logic as anyone else.
Avoid the generic Alibaba listing route unless you enjoy risk. You’ll get a low price and almost no engineering support, unclear certification, and no one to call when firmware misbehaves.
Here’s the framework. Score vendors against criteria that predict success:
Criteria Weight Vendor A Vendor B
--------------------------------------------------
Firmware flexibility 25% __ __
Certifications incl. 20% __ __
MOQ / pricing 20% __ __
Eng support / comms 20% __ __
Reference catalog fit 15% __ __
--------------------------------------------------
Weighted total 100% __ __Firmware flexibility is weighted highest for a reason. Ask directly: can you set custom advertising payloads? Do they support OTA updates? Will they expose source or at least a configurable SDK? A vendor that only flashes a fixed iBeacon image isn’t going to let you differentiate.
Certifications. Confirm which they provide (FCC, CE, IC, RoHS) and whether the design carries Bluetooth SIG qualification. The critical question: who pays, and who owns the listing. If certification is under the vendor’s name, switching suppliers later can mean re-certifying from scratch.
MOQ. Minimum order quantity scales with how much you customize. A stock unit might ship at 500 pieces; a firmware-custom run often starts at 1,000 to 3,000; sensor changes push higher. Get the MOQ for your tier in writing, not the catalog number.
Engineering support and comms. You want a named engineer who answers in English within a day, not a sales rep relaying messages. Test this during sampling. Slow replies now mean slower replies under production pressure.
Reference catalog fit. Start from a design that’s already close. The nearer the stock reference is to your need, the lower your NRE and the faster your timeline.
Step 3: Scoping Custom Firmware
Most of your differentiation as a custom firmware beacon lives here, so don’t hand-wave it. Write a firmware spec sheet, get the vendor to sign off on it, and treat that document as part of the contract.
[ ] Advertising format (iBeacon / Eddystone / custom)
[ ] TX power & advertising interval
[ ] GATT services & characteristics
[ ] Encryption / payload security
[ ] OTA update mechanism
[ ] Battery target vs. adv. frequency
[ ] Backhaul path (gateway / cellular / satellite)Specify the advertising format up front. iBeacon and Eddystone are fine for standard use, but if you’re packing sensor readings or an ID scheme into the payload, you need a custom format and the byte budget to fit it.
Pin down TX power and advertising interval because they drive both range and battery. A 100ms interval gives snappy detection and drains the coin cell in months; a 1-second interval might run for years. State a battery-life target and let it constrain the interval, not the other way around.
List your GATT services and characteristics, your encryption scheme (don’t ship plaintext IDs you care about), and your OTA update mechanism. OTA is easy to skip and painful to retrofit. If you’ll ever need to push a firmware fix to deployed units, design it in now.
Connectivity: a beacon is only useful if its data reaches you
Decide your backhaul on day one, not after the first run ships.
For fixed sites, gateways or phones collect advertisements and forward them. For mobile assets, that breaks the moment the asset leaves gateway range. Cellular works but burns power and adds cost per unit. For things that roam globally, emerging BLE-to-satellite networks such as Hubble’s satellite network let a beacon’s advertising packet get picked up from orbit. You get roughly a 13-byte window for arbitrary data per transmission. If out-of-coverage tracking is in scope, the firmware needs to format that payload. Write your backhaul path into the spec sheet alongside everything else (more on shaping that payload in the advertising packet docs).
Step 4: Samples, Validation, and Certification
Never go to mass production off a datasheet. Order pre-production samples and test them in your real environment, not a lab bench that flatters the radio.
Run actual RF and range tests where the beacons will live: through walls, near metal, in the weather they’ll see. Measure battery drain at your chosen advertising interval over enough days to extrapolate honestly. Validate that the custom firmware does what the spec sheet says, including OTA and any sensor reads.
Then nail down certification before you commit to volume. Confirm which regions are covered (FCC for the US, CE for Europe, IC for Canada), confirm the Bluetooth SIG listing, and confirm ownership in writing.
One trap to flag: if you alter the design after certification, even a board tweak for a sensor, you may trigger re-certification. Lock the design before you certify, or budget for doing it twice.
Step 5: Production and Shipping
With validated samples and certification settled, you’re negotiating a production run. A few things to get straight before money moves.
MOQ and pricing. You’ve already confirmed the MOQ for your customization tier. Push for a first-run quantity that matches real demand, not a number that leaves 5,000 units aging in a warehouse.
Payment terms. Typical structure is a deposit (often 30%) with the balance before shipment. Tie milestones to QC results, not calendar dates.
Tooling costs. Custom enclosures carry one-time mold costs. Confirm who owns the tooling. If you paid for it, you should be able to take it to another shop.
QC inspection. Pay for a third-party inspection or do a pre-shipment check yourself. Catching a bad batch in Shenzhen is cheap; catching it in your warehouse isn’t.
Lead times. A white-label run can ship in a few weeks. Firmware-custom builds usually run 6 to 12 weeks including sampling. Sensor or mechanical changes stretch to several months. Add buffer for sea freight and customs clearance.
De-Risking the ODM Path
Sourcing a custom ble beacon manufacturer comes down to three decisions done well. Pick a vendor on firmware flexibility, certification ownership, and engineering support rather than the lowest quote. Write a firmware spec sheet detailed enough that the vendor signs it. Design your backhaul in from the start so the data actually reaches you.
Handle those three, and everything else (certification, tooling, logistics) becomes predictable scheduling work. You can ship a beacon that fits your use case without ever laying out a PCB, and you’ll know exactly what you asked for and why.
Hubble Network connects your BLE beacons directly to satellites, so your data reaches you anywhere without gateways or cellular dead zones. See how it works →