The two words are used backwards
Ask five industrial TPMS suppliers what "ODM" means and you will get three different answers. In the sensor world the terms are used loosely, and the looseness costs money: a buyer who believes he has bought an OEM program often discovers in month three that only the label was his.
Here is the definition we work with, and it matches most of the industry:
- ODM — original design manufacturer. The supplier owns the design. You buy a finished product, and your brand goes on the housing, the packaging and the manual. What you can change is limited to what the supplier has already engineered, plus whatever it is willing to engineer for you.
- OEM — original equipment manufacturer. You own or co-own the specification. The enclosure, the mounting, the connector, the message layout, the alarm logic and the part number are defined by your document set, and the supplier builds to it. In practice the supplier's existing platform is usually the starting point, so the real difference is not "custom versus standard" — it is who holds the design record, and who is allowed to change it.
Notice the trap: "put my logo on it" is not a business model. It is a printing decision. Both models can carry your logo, and neither is defined by it.
What actually changes hands
Four things move between the two models, and it is worth asking about each separately, because suppliers rarely offer all four.
Firmware. In an ODM program you get the firmware that already exists. In an OEM program you should be able to get a variant with your defaults: the sensor ID scheme, alarm thresholds, units, the splash screen on the display, and your flavour of the output protocol. Ask who writes it, who validates it, and what happens when you want a change in year two. A trading company cannot answer that without going back to its factory; a manufacturer answers it from its own desk.
Tooling. A housing, a mounting bracket or a display bezel is tooling. Ask who pays for it, who owns the drawing, and whether the tool can move with you if the relationship ends. This is the most valuable negotiable asset in an OEM program and the one most often left undefined.
Documentation. This is the part buyers underestimate. A message map or DBC file, a register map for serial output, a connector pinout, alarm semantics, and a configuration tool for wheel count, sensor IDs and thresholds. Without them, integration is guesswork even when the hardware is perfect.
Certification. This is where optimistic conversations go wrong. A supplier who claims every certificate for every market has not understood your question. Our position is plain: we build to order, so the standard and the market are part of the project scope — you tell us where the machine will be sold, and together we define what has to be demonstrated for that market and by whom. Anyone who hands you a finished certificate file before knowing your market is selling you a photocopy, not a conformity assessment.
The four levers you are really buying
Stripped of vocabulary, an industrial TPMS sourcing decision comes down to four levers. Rank them before you talk to anyone.
1. Wheel count and radio coverage. One receiver addresses up to 256 wheel positions. Coverage on a long chassis is a different problem from capacity, and it is solved with repeaters, not with a bigger number. We delivered a production configuration for a 160-wheel beam carrier using two receivers and twelve repeaters, and the largest single machine we have instrumented carries 224 wheels across 28 axles.
2. The interface. CAN 2.0B at 250 kbps with a 500 ms data period by default, software-configurable, alongside J1939, RS485, RS232, Modbus RTU, PROFINET and UART. Whatever your controller already speaks is the cheapest place to start.
3. The mechanical and electrical fit. Enclosure, mounting, connector, IP68 sealing, and a DC 10–30 V supply that matches the machine. This is unglamorous, and it is what fails first in the field.
4. Branding. Labels, manuals, packaging, display splash. The easiest lever and the least valuable on its own.
If a supplier can move levers 1 to 3 to your specification, you have an OEM relationship whatever the contract is called. If it can only move lever 4, you have a distribution agreement with extra paperwork.
Six questions that reveal the model you are in
Ask these early. The answers are hard to fake.
- Which drawing number governs my product, and can I see the revision history?
- Who owns the firmware, and who signs off a change to it?
- Can I get a message map or DBC file before I place an order?
- Which parts do you design and build, and which do you buy in and assemble?
- Who is my engineering contact after the order, and what do they own?
- If I need a connector or enclosure change in year two, what is the process?
A supplier that answers the first five from memory and admits the sixth is the interesting one is a manufacturer. A supplier that answers all six instantly, with no questions back, is a sales office.
Which model should you choose
Choose ODM when your advantage is distribution, not engineering: you want a proven product, your own brand, a fast start, and you accept the supplier's design as it stands. This is the right answer for many fleet and aftermarket programmes, and pretending otherwise wastes money on custom work nobody asked for.
Choose an OEM programme when the machine around the sensor is yours. If your controller has a fixed message layout, if your harness ends in a specific connector, if a 3 kPa alarm band has to match your own maintenance rules, or if a spare part has to carry your part number on your dealer's shelf, then the design record has to be yours.
Mixed arrangements are normal and often sensible: customers frequently start with an ODM display and move to an OEM receiver variant once volume makes the firmware work worthwhile.
Commercial terms, honestly
Price, tooling cost, minimum quantity and schedule all depend on the same three variables: how much engineering the change needs, how many units you take, and how long the supply has to run. Nobody can give you a serious figure before the scope is defined, and a supplier who quotes one anyway is quoting a product that does not exist yet. Bring the wheel count, the voltage and the controller, and the discussion becomes concrete within one exchange.
How we work
GZVIA designs and builds the sensor, receiver, repeater, display and cloud platform in-house in Shenzhen — Infineon chips, IP68 housings, 433.92 MHz radio, internal sensors rated from −40 °C to +125 °C. We supply port machinery builders under their own brand, and our production configurations run from bus fleets up to the 160-wheel beam carrier and a 224-wheel single machine.
Read more about how we structure OEM and ODM programmes, or see who we are and what we build.
Send us the machine, the wheel count and the controller that has to receive the data, and we will tell you plainly which model fits and what it would take. Start the conversation here.