2026-11-06
Most sensor buying decisions start with the unit price and end with a returns problem six months later. After supplying programmable and Bluetooth TPMS sensors to tire shops, distributors and fleet operators across North America, Europe and Asia, the pattern we see is consistent: the sensors that cause trouble are rarely the cheapest or the most expensive. They are the ones chosen without matching three things to the actual work — the programming route, the vehicle mix, and the environment inside the tire.
This guide sets out the questions worth asking before a workshop or distributor standardises on a sensor, including the cases where a particular product is the wrong choice.
The cost of a sensor job is dominated by how long a lift stays occupied, not by the part. In a conventional bench-programmer workflow the technician leaves the vehicle four times: to remove the old unit, to reach the programmer, to confirm the write, and to return. Bluetooth programming removes those handoffs because the write happens at the vehicle, from an app on a phone or tablet.
That matters most in two situations: a mobile fitter working at a roadside or a customer premises, and a small shop where one lift serves every job. It matters least in a high volume rebuild shop that programmes sensors in batches at a bench, where a wired programmer can still be faster per unit.
Q: Can a phone-based sensor replace my bench programmer completely?
A: For routine replacement work on supported vehicles, usually yes. But programming does not read or clear fault codes, so a workshop that performs diagnostics still needs a scan tool. Treat the app as a programming route, not a diagnostic replacement.
Q: Will the app work where mobile data is poor?
A: Confirm this with the supplier before standardising. Some apps need connectivity to look up protocols; others cache the database locally. A basement workshop and a roadside van have very different connectivity, and the answer changes the buying decision.
A programmable sensor is a blank unit that accepts a protocol written into it. Two capabilities hide behind the word, and buyers often conflate them. The first is writing a vehicle protocol so the sensor communicates in the correct format and frequency. The second is cloning the original sensor identifier, which lets the replacement present itself to the vehicle as the part it replaced. Cloning is what avoids a relearn procedure on vehicles that refuse manual activation.
Neither capability is unlimited. Protocol coverage is finite and tied to model years, and coverage lists age. Before a distributor commits to a single SKU programme, the sensible request is a coverage list checked against the top twenty vehicle models the trade actually sees, not a headline percentage.
Q: Is 98 percent coverage a reliable figure?
A: Treat any coverage percentage as a claim to test, not a specification to trust. Ask for the underlying list and check it against your own vehicle mix. A sensor covering 98 percent of a market you do not serve is worth less than one covering 80 percent of the vehicles in your bays.
Q: When does cloning an original identifier cause problems?
A: If the original sensor is faulty in a way that corrupted its stored data, cloning may reproduce the fault. In that case the correct route is writing a fresh protocol for the vehicle rather than copying the old identifier.
Vehicles in the same market do not share one sensor band. North American models lean toward one frequency and European and Asian models toward another, and a general repair shop sees all of them in a single week. Two separate part numbers doubles the lines a distributor must fund and doubles the chances one goes out of stock at the wrong moment.
A dual frequency unit stores both protocol sets in one housing, with the correct protocol selected at programming time. The saving is not in the unit price; it is in working capital and shelf space. A distributor running a 60-line TPMS catalogue can often compress it substantially, and every removed line is a line that no longer needs forecasting.
Q: Does a dual frequency sensor cost more than a single frequency one?
A: Usually somewhat more per unit. The comparison that matters is total programme cost: fewer SKUs means less dead stock, less emergency air freight, and fewer lost sales when a specific part number runs out.
Q: Can one dual frequency unit serve both bands at once?
A: No. The sensor holds both protocol sets but operates on the protocol written at programming time. It is one part number serving two bands across different vehicles, not one sensor serving two bands simultaneously.
Three figures decide whether a sensor survives its service life, and all three are routinely skimmed.
Sealing deserves its own paragraph because it is invisible on the invoice and expensive later. IP67 protection combined with a stainless steel housing and sealed potting keeps out the moisture and road salt that sit inside a tire cavity. A board that is not protected fails quietly, and the failure is usually blamed on the brand rather than on the specification.
Q: Does higher IP rating always mean longer life?
A: Not on its own. The rating describes resistance to water and dust ingress under test conditions. Housing material, potting quality and vibration tolerance matter as much, which is why a specification sheet alone should not carry the decision.
Q: Which temperature figure matters more, the high or the low end?
A: Both matter, but for different markets. Cold climate customers care about the low end because a battery that cannot deliver current at -30 C will drop out; hot climate and heavy load applications stress the upper end.
A sealed sensor with a flat cell becomes electronic waste and a replacement sale. A sensor with a replaceable cell can be restored, which changes the economics for any operator maintaining hundreds of wheel positions. The saving is not the cell cost; it is the avoided labour and the avoided disposal of a functioning unit.
Q: Is a replaceable battery always the better choice?
A: Not automatically. A replaceable cell requires a serviceable housing, and a housing that opens is a housing that can leak if resealed carelessly. For a workshop with trained technicians the trade is worthwhile; for a consumer fitting sensors once, a sealed long life unit may be simpler.
Questions that separate a supplier from a reseller, in the order we would ask them:
Q: What is a fair sample size for a trial?
A: Enough to cover the vehicle mix a shop actually sees, across at least two brands and both frequency bands, and enough to include a repeat job so the technician tests the workflow a second time. Five units of one model proves very little.
Fit the sample units on real customer vehicles, record programming time per job against the previous method, and note every case where a vehicle refused the procedure. Run at least one job on a vehicle known to be difficult. If the protocol list and the real world agree after twenty fitments, the standardisation decision is evidence based rather than price based.
Q: How long should a trial run before a purchasing decision?
A: Long enough to cover seasonal variation if the market is severe, and at minimum twenty fitments. A trial that only covers summer fitment in a cold climate market has not tested the specification that matters most.
Shenzhen June Electronics Co., Ltd. has manufactured TPMS sensors, programming tools, diagnostic scanners and truck, fleet, RV and trailer TPMS systems since 2016, supplying OEM and ODM customers exporting from China. The observations above come from supporting workshops and distributors through sensor standardisation projects. Buyers are welcome to request protocol coverage lists and a trial batch matched to their vehicle mix.
english
français
Deutsch
Italiano
Русский
Español
português
Nederlandse
ελληνικά
日本語
한국
العربية
हिन्दी
Türkçe
indonesia
tiếng Việt
ไทย
বাংলা
فارسی
polski