This is written for distributors, brand owners and integrators evaluating a smart home OEM or ODM partner, not for hobbyists sourcing a single unit. Matter products carry a few sourcing questions that a generic "find a factory" guide skips.
Step 1: Decide how much of the design you actually want to own.
If you have no in-house hardware or firmware team, ODM is the realistic starting point: you pick an existing, working reference design and put your brand on it. If the product is meant to be a differentiated flagship, or you need IP you can defend, OEM is worth the longer lead time. Most brands run both at once: ODM for the volume catalog, OEM for the one product that carries the brand.
Step 2: Check the chip platform and protocol before anything else.
Ask which wireless SoC the reference design uses and whether it runs Matter over Wi-Fi or Matter over Thread. This decides your customer's setup experience: Wi-Fi needs nothing extra, Thread needs a Border Router already on the network. If your target category spans both (say, a plug-in Wi-Fi hub product and a battery sensor line), confirm the manufacturer has working reference designs for both, not just one retrofitted to claim the other.
Step 3: Ask about the Matter certification path directly, don't assume it.
Every Matter device ships with a Device Attestation Certificate. There are two ways this usually works with a manufacturer:
- Ship under the factory's own certification. Fastest, cheapest, but the product is tied to their vendor identity, not yours.
- Get your own DAC. Some manufacturers can run the certification process for you or transfer a DAC to your brand's own vendor ID. This matters if you plan to sell under your own name long-term or need to control firmware updates independently later. Confirm this is actually offered; it's a service, not a default.
Step 4: Get a real sample before you talk volume.
A working sample, in your hands, on your network, connecting to the ecosystem you actually care about (Apple Home, Google Home, Home Assistant), tells you more in an afternoon than a spec sheet does in a week. Confirm what the sample lead time looks like and whether it reflects the production hardware or a hand-built prototype.
Step 5: Confirm what "customization" actually covers.
On the ODM side, customization is usually limited to enclosure color, branding, and firmware-level configuration (device name, default behaviors). On the OEM side, ask specifically what's changeable: PCB layout, connector type, radio power, firmware feature set. Get this in writing before quoting volume pricing, since scope changes after a quote is where sourcing timelines usually slip.
Step 6: Ask what happens after the sale.
Firmware updates for Matter devices are ongoing, not one-time. Confirm who pushes updates, how long the manufacturer supports the platform, and what happens if you need a fix after your own certification is in place.
Quick checklist to bring to a first call:
- Which chip platform, and Wi-Fi or Thread?
- Ship under their DAC, or can we get our own?
- Sample lead time, and is it production-representative hardware?
- What's actually customizable at OEM level vs. ODM level?
- Who owns firmware updates post-launch?
Where Rez-ti fits. Rez-ti's existing catalog (switches, downlights/spotlights, LED strip drivers, curtain motors, mmWave presence sensors, a Thread Border Router, a VRF controller) runs on a Matter-native ESP32-C3 (Wi-Fi) / ESP32-H2 (Thread) platform, so the ODM path starts from a working reference design rather than a blank sheet. For brands that need their own certification identity, Rez-ti's manufacturing partner offers a DAC transfer service rather than requiring everyone to ship under one shared certification. Custom OEM development is handled directly, not templated, so it's worth a direct conversation about scope before assuming what's configurable.