Sprinkler head product attributes

Sprinkler heads are a system of bodies and nozzles, and that split drives most of the data problems in this category. The body sets pop-up height, inlet size and features such as pressure regulation and check valves, while radius, flow rate and precipitation rate depend on the nozzle and the operating pressure. A body sold without a nozzle has no single radius, yet supplier files often give one.

Spray bodies and rotors also behave differently. Rotors usually take a larger inlet, cover longer distances and ship with a set of nozzles, while spray bodies accept interchangeable nozzles sold separately. Treating them with one flat field list either leaves blanks or invents values that do not apply.

Water-efficiency and reclaimed-water details are increasingly required on commercial and municipal projects. Pressure regulation setpoint, check valve hold, matched precipitation, WaterSense labeling where the specification applies, and purple non-potable identification are the fields most often missing from supplier data, and they are usually hidden in part number suffixes or chart footnotes.

The sprinkler heads 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. 12 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
Brand brand	Controlled list	Core	Manufacturer name as printed on the label
Manufacturer Part Number (MPN) manufacturer_part_number_mpn	Identifier	Core	SR-4P-PRS45
GTIN (UPC-A) gtin_upc_a	Identifier	Core	012345044502

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
Pop-Up Height pop_up_height	Number · in	Core	4
Radius (Throw) Range radius_throw_range	Text · ft	Core	25-50 ft (nozzle dependent)
Flow Rate Range flow_rate_range	Text · gpm	Core	0.5-9.6 gpm (nozzle dependent)
Operating Pressure Range operating_pressure_range	Text · psi	Core	25-70 psi
Pressure Regulation Setpoint pressure_regulation_setpoint	Controlled list · psi	Buyer decision	Integral, 45 psi
Check Valve Hold check_valve_hold	Number · ft of head	Buyer decision	10
Precipitation Rate precipitation_rate	Number · in/h	Buyer decision	0.40 (matched across arc)

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
Sprinkler Type sprinkler_type	Controlled list	Core	Gear-drive rotor, pop-up
Arc Range arc_range	Text · °	Core	40-360° adjustable
Nozzle Configuration (As Shipped) nozzle_configuration_as_shipped	Controlled list	Core	Nozzle rack included, standard nozzle installed
Nozzle Trajectory nozzle_trajectory	Text · °	Buyer decision	25 (standard); 13 (low-angle)
Reclaimed Water Identification reclaimed_water_identification	Controlled list	Channel / evidence	Purple cap (non-potable)

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
Inlet Size & Thread Form inlet_size_thread_form	Controlled list · in	Core	3/4 in FNPT

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
Country of Origin country_of_origin	Controlled list	Core	United States
WaterSense Labeled watersense_labeled	Controlled list	Channel / evidence	Not applicable (specification covers spray sprinkler bodies)

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.

• Check valve hold (ft of head)
• Pressure regulation setpoint (psi)
• Nozzle trajectory
• Nozzle configuration as shipped
• Reclaimed water identification

Questions the record must answer

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

• Will this rotor throw 35 feet at the 45 psi I have at the head?
• Does it come with nozzles, or do I need to buy them separately?
• Will it stop the low-head drainage on my sloped zone?
• Is there a purple-cap version for our reclaimed water system?

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