Thermostat and HVAC control product attributes

Thermostats and controls sit at the junction of several systems, so most of their data is about compatibility. A buyer needs to know which equipment types the control supports, how many heating and cooling stages it can run, which terminals it provides and whether it needs a common wire for power. These facts are often spread across a feature list, a wiring diagram and a small-print compatibility table.

The category also covers very different devices: low-voltage residential thermostats, line-voltage thermostats for baseboard heat, and networked controllers for commercial buildings. Line-voltage devices need contact ratings and switch forms, while commercial controllers need communication protocols and sensor input types. A shared schema works when those fields are conditional on the control type instead of required everywhere.

Stage configuration is frequently written as a shorthand like 3H/2C that has to be split into separate fields to be searchable. Listings and program eligibility flags, such as smart thermostat certifications, should be stored as evidence with their source and the date they were checked rather than as marketing text.

The thermostats & controls attribute template

18 candidate fields in 5 groups, ordered the way a record gets built: identify the item, capture its specifications, then record fit and the evidence behind any claim. 9 are marked Core: without them the item cannot be identified or filtered. Example values show the expected format only; they do not describe a real SKU.

Identity

Which exact item, variant and pack this record describes.

Check before use: Preserve leading zeros and punctuation, validate against the manufacturer record, and check the GTIN check digit and packaging level before linking.

Attribute	Type	Priority	Example format
Manufacturer Part Number manufacturer_part_number	Identifier	Core	TS-3H2C-WF
GTIN-12 (UPC) gtin_12_upc	Identifier	Core	012345322006

Technical specifications

Measured or rated values that must travel with their unit and test conditions.

Check before use: Store the number and unit separately. Convert only when the source unit and test conditions are known.

Attribute	Type	Priority	Example format
Control Voltage control_voltage	Controlled list	Core	24 VAC (18-30 VAC)
Setpoint Range setpoint_range	Text · °F	Core	40-90 °F (4.5-32 °C)
Power Method / C-Wire Requirement power_method_c_wire_requirement	Controlled list	Buyer decision	24 VAC hardwired; C wire required for Wi-Fi
Contact / Load Rating contact_load_rating	Text · A	Buyer decision	22 A at 120-240 VAC resistive
Control Differential (Deadband) control_differential_deadband	Number · °F	Buyer decision	1.0 (adjustable 0.5-2.0)
Enclosure Rating enclosure_rating	Controlled list	Channel / evidence	NEMA 1 (indoor)

Selection attributes

The type, material and option choices buyers filter and compare on.

Check before use: Map supplier wording to a governed vocabulary only after checking the source text and which variant it applies to.

Attribute	Type	Priority	Example format
Control Type control_type	Controlled list	Core	Low-voltage room thermostat
Heat Stages heat_stages	Number	Core	3
Cool Stages cool_stages	Number	Core	2
Switch Action / Contact Form switch_action_contact_form	Controlled list	Core	SPST (line-voltage models)
Communication Protocol communication_protocol	Controlled list	Buyer decision	BACnet MS/TP (EIA-485)

Fit & compatibility

What the item mounts to, mates with, replaces or works alongside.

Check before use: Keep model and series qualifiers. A similar-looking part is not a verified fit until a source says so.

Attribute	Type	Priority	Example format
System Compatibility system_compatibility	Controlled list	Core	Heat pump with auxiliary / emergency heat
Terminal Designations terminal_designations	Text	Buyer decision	R, Rc, W/W1, W2, Y, Y2, G, C, O/B, S1, S2, L/A
Remote Sensor Input Type remote_sensor_input_type	Controlled list	Buyer decision	10K NTC Type II (10K-2)

Evidence & compliance

Listings, standards, classifications and origin claims that need a document behind them.

Check before use: Link the manufacturer document or label with its edition or date. Never copy a certification from a neighboring SKU.

Attribute	Type	Priority	Example format
Agency Listing agency_listing	Controlled list	Channel / evidence	UL 60730-1 / UL 60730-2-9; cUL
Country of Origin country_of_origin	Controlled list	Channel / evidence	Mexico (MX)

Normalize supplier values

The same value arrives in many spellings. Map each raw string to one governed value, and keep the raw text beside it so a reviewer can see what the supplier actually wrote.

Often missing from supplier files

These fields are commonly absent from price lists and basic feeds, even though the information usually exists in a datasheet, label or installation manual. Treat an empty value as a request for evidence, not as permission to fill it from a similar model.

• Terminal designations
• Power method / C-wire requirement
• ENERGY STAR or JA5 smart thermostat eligibility flags
• Remote sensor input type (10K-2 vs 10K-3)
• BACnet listing and device profile

Questions the record must answer

Buyers and counter-sales reps choosing thermostats & controls ask questions like these. Each one needs a specific field, sourced for the exact variant.

• Will this thermostat run my heat pump with electric backup heat?
• I don't have a C wire at the wall. Will it still work?
• Can our BACnet building controller read and write its setpoints?
• Will it accept the 10K duct sensor we already have installed?

From supplier file to record

1. Resolve identity first. Link the supplier SKU, manufacturer part number and packaging identifiers without merging distinct variants or pack sizes.
2. Extract with the source attached. Pull values from rows, tables and datasheets, keeping the raw text, unit and page or row reference.
3. Map to your classification. Assign the ETIM, ECLASS, UNSPSC or internal class your company licenses, and keep the supplier's original terms.
4. Review, sync and watch. Hold conflicts and safety-related values for a category expert, write approved values to ERP or PIM, and recheck when the supplier sends a new file.

For the full method, see how to build a category attribute template and the category catalog gap audit.

FAQ