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.
How to Structure Product Data: A Practical PIM Model
Learn how to structure product data in a practical PIM model, using reusable attributes, product-type templates, variants, categories, and relationships before you load the catalog.
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.
What you can do in Utomo
Learn how to structure product data in a practical PIM model, using reusable attributes, product-type templates, variants, categories, and relationships before you load the catalog.
- Typed, validated attributes defined once and reused
- Attribute sets as templates per product type
- A category tree for browsing and filtering
- Associations for variants, accessories, and spare parts
Frequently asked questions
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.
See how Utomo handles your product data
Start a 30 day trial to structure product information, connect assets, and prepare controlled output from one private workspace.