Contact GK Thermostat: Start a Private-Label Program

Start with the equipment

The fastest way to get a useful reply is to describe what the thermostat will control. A model number and a photo of the existing control tell us more than a page of requirements written from memory.

What to include

• Equipment type: rooftop unit, fan coil, heat pump, unit heater, VAV box, or something else
• Supply voltage and the load being switched, including whether it is inductive
• Sequence of operation, or the existing thermostat's manual if there is one
• Destination market and the compliance scope you expect
• Display and enclosure expectations, and whether a retrofit plate is needed
• Connectivity: none, BACnet, Modbus, Wi-Fi, Bluetooth, or a combination
• Whether you need firmware source, a fixed binary, or a maintenance arrangement
• Expected annual volume and the launch window you are working toward
• Branding assets if they exist: logo, model numbering, packaging direction

If the program is a replacement for a discontinued product, send a unit. We will open it, document the behavior, and compare it with the platforms we build.

Email

sales@gkthermostat.com

Put the equipment type and the market in the subject line. Attachments are fine; if a file is large, send a link. We sign a mutual confidentiality agreement before reviewing drawings or firmware, and we can send our template first if your legal team prefers.

What happens after you send it

We read the requirement, check it against the platforms and processes described on this site, and reply with either questions, a request for a call, or a statement that the program is outside our scope. The reply is written by someone who will work on the program, not by a lead-qualification team.

If the fit is plausible, the next step is a specification review. That is where the requirement becomes a document with an I/O list, a sequence of operation, a compliance route, and acceptance criteria. The OEM process page lists the stages after that, including the points where your team has to make a decision.

Existing production programs

For a quality, change, or shipment question on a product already in production, include the model number, the serial or lot identifier, and the firmware version if it is known. That lets us pull the build and test record before replying. Engineering changes and supplier notifications come through the same channel, with the program name in the subject.

Suppliers and service partners

Component suppliers, test houses, and design partners are welcome to introduce themselves. Send a short note describing what you supply, the certifications or accreditations you hold, and the customers or industries you serve. We review new suppliers against our approved supplier process, which includes a site audit for safety-critical categories.

What we will not do

We will not quote a certification, a delivery date, or a piece price before the specification exists. We will not put a competitor's product in our catalog or copy a patented enclosure. And we will not take on a program we cannot support after shipment; if the answer is no, you will get it early, with a reason.

Before you write

The capabilities page describes what we build, products lists the reference platforms, and quality and compliance covers the evidence trail. If those pages answer your question, the first email can be short.