How to Structure Product Data: A Practical PIM Model

Learn how to structure product data with a practical PIM model for attributes, variants, categories, and relationships so every channel receives consistent information.

Start with reusable product attributes

Attributes are the building blocks — name, weight, colour, material, technical specs. Define each once, with a type and validation, so the same field means the same thing everywhere it is used.

Build product-type attribute sets

An attribute set is the template a product is built from. Group attributes for a product type (for example “Footwear” or “Power tools”) so new products start complete and consistent.

Add categories and relationships

Categories organize products into a browsable tree; associations capture relationships like accessories, spare parts, and variants. Together they make the catalog navigable and ready to publish.

A few things you might be wondering.

Should I model everything up front?

Start with the attributes and sets you need to publish, then extend. Utomo lets you add attributes and sets over time without redoing existing products.

How many attribute sets do I need?

Usually one per meaningfully different product type. Too few and products carry irrelevant fields; too many and you duplicate work — aim for the smallest set that keeps products complete.

Can attributes be reused across sets?

Yes — that is the point. A shared attribute like “Material” is defined once and reused in every set that needs it, so its values stay consistent across the catalog.

Keep the story connected.

Let’s start with your products.

Explore the workspace with your own catalog.

· Aureon workspace