Skip to main content

Product Information Management

Every voltage, frame and finish. One family to maintain.

Define a product once, generate the sellable variants from its axes and keep SKU-level exceptions explicit so shared data stays shared.

Walk through it All capabilities

The capability

Parent identity, child precision

A product family groups items that share a structure and most of their data. Within a family, a parent product holds the values every variant shares, such as output power, enclosure and efficiency class, while variant axes such as voltage, frame size, finish or thread size define the sellable children.

Autonera generates the variant matrix from the axes you enable, assigns each child its own identifiers and keeps inherited values linked to the parent. When a variant genuinely differs, such as a heavier shipping weight for one frame, the override is stored on that SKU and clearly marked, and can be reverted to inheritance at any time.

Families also carry requirements. A motor family can require voltage and frame on every child, while a fastener family requires thread, length and grade. Completeness is evaluated per variant, so a range can be released item by item as each SKU becomes ready.

How it works

Build a motor range from two axes

Turn axis values on and off to regenerate the variant matrix. Select a variant to see which values it inherits, override one, then edit the parent to see which children follow.

PARENT PRODUCT

General-purpose AC motor, 1 HP, 1800 RPM

Shared values are maintained here once. Change one and every variant without an override follows.

VARIANT AXES

Voltage

NEMA frame

9 sellable variants generated from 3 voltages x 3 frames, with 2 SKU-level overrides.

Variant matrix by frame and voltage
Frame115/230 V208-230/460 V575 V
56C
143T
145T
MTR-1-145T-575145T / 575 V
  • Axis valuesDefines identity

  • Output power Inherited

  • Enclosure Inherited

  • Efficiency class Inherited

  • Shipping weight SKU value

  • Insulation class Inherited

Problems it solves

Where this work usually breaks down

01

Duplicated parent data across hundreds of SKUs

Updating a shared value means editing every row, and some are always missed.

02

Variants that are not really variants

Without defined axes, items are grouped by name similarity, and buyers cannot select by the attribute that actually differs.

03

Exceptions that disappear

A SKU-specific value overwritten by a bulk parent update causes incorrect freight or ordering data.

04

All-or-nothing readiness

A family cannot be published until every child is complete, even when most are ready.

Functional capabilities

What Product Families & Variants includes

Family templates
Reusable structures that define attributes, groups and requirements for a product type.
Variant axes
Define one or more axes and generate sellable combinations automatically.
Inherited and SKU-level values
Parent values flow to children until a child explicitly overrides them.
Parent-child identity
Children keep their own identifiers, assets and relationships while staying linked to the parent.
Per-variant completeness
Readiness is evaluated for each SKU against family requirements.
Axis changes with impact preview
See which variants would be created or retired before changing an axis.

In industrial operations

A motor manufacturer consolidates a 2,000-SKU range

A manufacturer maintained each motor SKU as an independent record, so efficiency-class updates for a regulatory change took weeks.

  1. Motors are grouped into families with voltage and frame as variant axes.
  2. Shared electrical and mechanical values move to the parent; weights that genuinely differ stay as SKU values.
  3. The regulatory update is applied once at the parent and flows to every inheriting variant.
  4. Variants with explicit overrides are listed for engineering to confirm.

Result: The range is maintained from a fraction of the records, and exceptions remain visible instead of being silently overwritten.

Autonomous operations

How autonomous execution changes product families & variants

Agents propose family groupings and axes from flat supplier data, then keep parent and child values consistent as the range changes.

Agents carry out

  • Detect candidate families and axes in flat catalogs
  • Generate child records for new axis values
  • Flag overrides that conflict with parent updates
  • Complete missing variant values from source documents

People decide

  • Approve family structure and axes
  • Confirm whether an override remains valid
  • Decide which variants are released

Evidence recorded

  • Origin of every inherited and SKU value
  • Axis changes with the variants they created or retired
  • Approval history for overrides

Related capabilities

Works alongside

Feature guide

Product Data Modeling

Configurable entities, typed attributes, groups and calculated values for technical products.

Feature guide

Product Hierarchies & Taxonomy

Classification trees with inherited category requirements and controlled reassignment.

Feature guide

Packaging & Trade-Item Hierarchies

Each, inner, case and pallet levels with quantities, weights and identifiers.

Feature guide

Multi-Location Product Management

One product master with location-specific attributes, assortments and rules.

Capability area

Product Information Management

See where Product Families & Variants fits in the wider Product Information Management capability.

Buyer FAQs

Questions evaluators ask

How many variant axes can a family have?

Families can define multiple axes. Most industrial ranges use two or three, such as voltage, frame and enclosure, or diameter, length and finish.

Can a variant have its own images and documents?

Yes. Assets can be linked to the parent, to specific variants or to both, so a wiring diagram applies to all while a nameplate image applies to one.

What happens to overrides when the parent changes?

Overrides are preserved. Inheriting variants update immediately, and overridden values can be flagged for review.

Can we publish some variants before others?

Yes. Completeness and approval are evaluated per variant, so ready SKUs can be released while others are completed.

How does this relate to product hierarchies?

Families define structure and inheritance between parent and child products. Hierarchies and taxonomies organize families and products for navigation and classification.

Your next step

See Product Families & Variants on data like yours.

Bring a real file, catalog or record set. We will walk through how Autonera would handle it and where your team keeps the final say.

Book a Demo