OEM Thermostat FAQ: Tooling, MOQ, Firmware, and Branding

Questions we get before the first call

Do you have a minimum order quantity?

Yes, but it is a program decision rather than a published number. Volume interacts with tooling, test fixtures, and how much customization the product needs. A branding-only program on an existing platform can start smaller than a clean-sheet design with new injection molds. We quote the quantity you ask for and tell you where the cost curve changes.

Can we get samples before committing to production?

Prototypes are a paid stage, because they consume engineering time and often tooling. What you receive is a functional unit built to the agreed specification, with the test results and a list of known deviations. We do not present a bench sample as if it were a production unit.

Who owns the tooling and the design?

It is stated in the program agreement. Options range from customer-owned tooling with a documented buy-out, to tooling we hold and amortize across the program, to a licensed design where the customer owns the drawing but not the right to have it built elsewhere. Whichever applies, it is written down before the first mold is cut.

Can the product carry our brand and our model number?

That is the normal case. Enclosure color, overlay artwork, silkscreen, terminal labels, packaging, manuals, and the model number are all customer-defined. We will flag anything that creates a regulatory or support obligation the brand has not planned for.

Do you handle certification?

We handle the technical work and the coordination. The certificate is issued to a holder named in the agreement, usually the brand that sells the product or its importer. We prepare the technical file, supply samples, and work with the laboratory. We will not describe a product as certified before that certificate exists.

What about firmware and source code?

Three models: source code licensed to the customer, a binary with a documented parameter interface, or a maintenance arrangement where we own and update the firmware. Source access has a price and a support boundary, and both are better agreed at the start than during a field issue.

Can you replace a thermostat that is no longer available?

Often, yes. Send the existing unit, its manual, and a description of the equipment it controls. We build a behavior matrix from the old device and design the replacement to match it, including the parts of the behavior that are undocumented. Retrofit mounting and terminal layout usually matter as much as the control sequence.

Do you provide the mobile app and cloud?

We can, through a partner, or the customer can own the backend. For connected products we need a named owner for firmware updates, credential handling, and vulnerability response before launch. A connected thermostat without that owner is a liability, not a feature.

How long does a program take?

It depends on the level of customization, the number of validation cycles, and how fast design decisions are made on the customer side. We put dates in the program plan after the specification is agreed, and we update the plan when a decision slips rather than pretending the original date still holds.

Do you sell to contractors or end users?

No. We build for brands, equipment manufacturers, and specifying firms. If you need a small quantity for a single building, a distributor or a controls contractor is the right route, and we will say so rather than take an order we cannot support.

How does a program start?

Send the equipment type, voltage and load, sequence of operation, target market, and expected annual volume through the contact page. If you have an existing product, a manual, or a drawing, include it. The OEM process page describes what happens next, and capabilities covers the technical envelope.