TPMS ODM and Private Label — A Buyer's Guide What to settle before signing a private-label TPMS programme: who owns the tooling, what can be branded, and the questions that expose a trading company.

The difference between a factory and a trading company

Most TPMS suppliers look identical on a website. A few product photographs, a specification table, a claim about capacity, and an invitation to request a quotation. The differences only become visible when the programme starts and something has to change.

A trading company buys finished sensors and sells them on. That is a legitimate business, and in some cases it is the right one to buy from. But it constrains what a private-label programme can deliver, because every change has to be requested of somebody else. A change to the radio firmware, a new marking convention, a different cell, a packaging variant — each one goes out to a third party and comes back on their schedule if it comes back at all.

A factory can make those changes itself, and can say why a batch behaved differently. The practical test is not what a supplier claims about its premises, but whether it can answer technical questions in its own words. Ask why a particular pressure range was chosen, or what happens to accuracy at the cold end of the range, and the answer separates the two quickly.

What can actually be branded

Buyers often assume the branding conversation is about a sticker. It is worth enumerating what is genuinely changeable, because the scope differs enormously between suppliers.

Element	Typically brandable	Notes
Laser marking on the sensor	Yes, at a factory	Wheel positions, part numbers, your brand
Housing	Sometimes	Often requires tooling; a cost and a lead time
Label	Yes	Your artwork, your regulatory text
Packaging	Yes	Retail box, blister or bulk carton
Manual	Yes	Your language and layout
App identity	Depends on the supplier	Name, icon and in-app branding if they control the app
Firmware / radio behaviour	Only at a factory	Needed if your app must talk to the sensor

That last row is the one buyers underrate. If the sensor's Bluetooth service is fixed, an app built by your own developer may not be able to read it, and you will end up shipping the supplier's app. For a brand-led programme that is often unacceptable, and it is a question worth asking before the first order rather than after.

Ask these before you commit

A programme that goes badly usually went badly because one of these was never asked.

Who owns the tooling? If a housing mould is made for you, who holds it and what happens if you leave? Get this in writing.

Can I see the firmware behaviour? Ask for the Bluetooth service and characteristic documentation. A supplier who cannot produce it is reselling.

What is the minimum order quantity, and does it change? MOQ is often quoted for a standard configuration and quietly revised for a branded one. Confirm both.

Will you sell my branded product under your own name? The answer should be an unqualified no. If it is anything else, the programme is a channel demonstration for the supplier's own brand.

What happens if a batch is wrong? A factory can trace a batch to production. Ask how.

Whose regulatory work is it? Certification and market approvals have to be assigned explicitly. A supplier who says "yes, we handle that" without naming the market and the document is not answering.

The capacity question, and how to read an answer

Every supplier quotes a monthly capacity figure. The number matters less than whether it is credible and whether it is available to you.

A credible capacity claim is one that connects to something checkable: a supply relationship, a run rate, a component purchase. Our own figures are 30,000 sensors a month in capacity and more than 10,000 sets a month supplied into Chinese two-wheeler aftermarket programmes. Those are not the same thing as a promise to deliver 30,000 units to a new customer in month one, and a supplier who blurs that distinction is telling you something.

The question to ask is not "what is your capacity" but "what is already committed, and where would my volume fit". A factory running at ninety per cent for domestic programmes cannot absorb a new export order quickly, whatever the headline number says.

Lead time is a design decision, not just a number

Two programmes with the same quoted lead time can behave very differently, depending on what sits on the critical path.

• Standard configuration from stock. Fastest. Marking is the only variable.
• Standard configuration with custom marking. Fast if the marking file is agreed up front, slow if it is revised after production.
• Custom housing. Dominated by tooling, which is weeks rather than days.
• Custom firmware or protocol. Dominated by your own specification, and by how completely it was written.

The recurring lesson in all four is that the bottleneck is usually the buyer's own specification, not the factory. A programme with a frozen specification runs; one with a specification that keeps improving does not.

Where the software usually surprises people

Buyers spend time on the sensor and treat the app as a detail, which is the wrong way round for a consumer-facing product.

Two things need deciding early. First, whether you need iOS as well as Android. Android development is typically available and iOS is frequently scoped per programme, which is a reasonable arrangement but not an instant one. Second, whether you are white-labelling an existing app or building your own. Building your own is entirely possible on a factory platform, but it requires the Bluetooth documentation and a clear protocol, and it moves the critical path onto your developer.

If the answer is "we will sort out the app later", plan for the sensor programme to finish before the product does.

A short checklist

Before signing a private-label TPMS programme, be able to write down the answers to these. If any is blank, the programme has an unresolved dependency.

1. Which elements carry my brand, and who owns the tooling for each.
2. Whether the Bluetooth behaviour is documented well enough for my own app.
3. The MOQ for a branded configuration specifically.
4. Whether the supplier will compete with my branded product.
5. Batch traceability and the process if a batch is wrong.
6. Which certifications are in scope, for which markets, and who owns each.
7. Android and iOS scope.
8. What is frozen and what is still open.

A supplier who answers all eight with specifics is worth a programme. One who answers with adjectives is not. If you want to compare that against how we work, the OEM and ODM page sets out what we do in-house and what we will not claim, and the private-label page lists the branding options in detail.