Electronic Components · 18 attributes

Industrial sensor product attributes

Industrial sensor attribute template: sensing distance or range, output type, supply voltage, housing, connection, IP rating and IO-Link data for each SKU.

Download CSV template JSON Editorial reference

Industrial sensors are a family of categories that share a few attributes and differ in many others. Inductive, photoelectric, capacitive, ultrasonic and pressure sensors all have an output type, supply voltage, housing and connection, but each has its own measuring principle, range and accuracy terms. A schema that forces them into one flat template usually ends up with empty or misused fields.

Rated sensing distance is a good example of a value that needs context. For an inductive sensor it is measured against a standard steel target, and non-ferrous metals reduce it by a correction factor. Shielded and unshielded versions of the same body size have different ranges. Supplier files that give only a number in millimeters leave buyers guessing whether it applies to their target and mounting.

Electrical and mechanical fit decide whether a replacement drops in. Output type, such as PNP or NPN with normally open or closed contacts, has to match the controller input. Connector type and pinout have to match the existing cordset, and the housing thread, ingress rating and any hazardous-area marking must suit the location. IO-Link capability adds parameters of its own.

The sensors 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. 10 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 PX-M12-02PS-C4
GTIN / UPC gtin_upc Identifier Core 5412345000433

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
Voltage - Supply voltage_supply Text · V Core 10-30 VDC
Operating Temperature operating_temperature Text · °C Core -25 °C to +70 °C
Ingress Protection Rating ingress_protection_rating Controlled list Core IP67
Repeatability / Accuracy repeatability_accuracy Text · % Buyer decision Repeatability ≤ 5 % of Sr

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
Sensor Type sensor_type Controlled list Core Inductive Proximity
Rated Sensing Distance (Sn) / Measuring Range rated_sensing_distance_sn_measuring_range Text Core 2 mm (Sn, standard steel target)
Output Type output_type Controlled list Core PNP-NO 3-Wire
Package / Case (Body Style) package_case_body_style Controlled list Core Cylindrical threaded, M12 x 1
Material - Body material_body Controlled list Buyer decision Stainless steel 316L
Product Lifecycle Status product_lifecycle_status Controlled list Channel / evidence Active

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
Termination Style termination_style Controlled list Core Connector, M12 4-pin
Shielding (Flush Mountable) shielding_flush_mountable Controlled list Buyer decision Shielded (flush mountable)
Communication Interface communication_interface Controlled list Buyer decision IO-Link v1.1 (COM3)

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
RoHS / REACH Status rohs_reach_status Controlled list Channel / evidence RoHS3 Compliant; No SVHC > 0.1%
Country of Origin country_of_origin Controlled list Channel / evidence Japan
Hazardous Area Certification hazardous_area_certification Controlled list Channel / evidence ATEX II 3G Ex ec IIC T4 Gc (where certified)

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.

Output Type

PNP NOPNP-N.O.3-wire PNP normally openSourcing, N.O.PNP/NOP NO 3 wire

Normalized to PNP-NO 3-Wire

Rated Sensing Distance (Sn)

4mm4 mm0.157"Sn=44mm nom.0.16 in

Normalized to 4 mm

Ingress Protection Rating

IP-67IP 67Ip67IP67 ratedIP67 (IEC 60529)ip67

Normalized to IP67

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.

  • Target Material Correction Factor
  • Cable Length and Jacket Material
  • IO-Link Version, COM Mode and IODD Reference
  • Wetted / Process Connection Material
  • Weld-Field Immunity

Questions the record must answer

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

  • Will this sensor detect an aluminum target at the same distance as steel?
  • Is this PNP normally open, to match the inputs on my existing controller?
  • Does it use the same M12 4-pin connector as the cordset already installed?
  • Can this sensor be flush mounted in a steel bracket?

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

Why do catalogs list different sensing distances for what looks like the same sensor?

Manufacturers quote several distances: rated operating distance, assured operating distance, and sometimes extended-range values. For inductive sensors, all of them are defined against a standard steel target, and other metals give shorter ranges. Shielded and unshielded variants of one body size also differ. Store the rated distance with its definition and target, keep the assured distance and correction factors as separate fields where published, and do not compare values that use different definitions.

Do inductive, photoelectric and pressure sensors need separate schemas?

They benefit from a shared core and separate extensions. Common fields such as output type, supply voltage, housing, connection, ingress rating and operating temperature apply to all of them. Principle-specific fields do not: sensing distance and target correction for inductive, light source and sensing mode for photoelectric, and pressure range, reference type and wetted materials for pressure sensors. Model one base template with a type-specific attribute set per sensor class, so empty fields reflect genuine absence.

What is the minimum data needed to list a sensor on a parametric web page?

Enough for a buyer to confirm function, electrical fit and mechanical fit. That usually means sensor type, sensing range or measuring range with its unit, output type and switching function, supply voltage range, housing style and size, connection type with pin count, ingress rating and operating temperature, plus the manufacturer part number. Without output type and connection, a buyer cannot tell whether the sensor will work with an existing controller and cordset, so those fields should block publication when missing.

How should IO-Link capable sensors be modeled?

Record IO-Link as a communication interface value, and add its specification version, the supported transmission rate or COM mode, and whether the sensor also works in standard switching mode. Link the device description file, known as the IODD, as a source document, since it describes the parameters a controller can read and set. Keep process data details in that file rather than duplicating them as attributes, and take all values from the manufacturer's documentation.

Claro

See where your catalog breaks — free

Claro runs this automatically: resolve identity, fill missing attributes, validate updates, and write clean records back into your PIM/ERP. Upload a sample supplier file for a free catalog audit.

Get a free catalog audit

Related resources

More Electronic Components templates