The new home for your products

The goal is simple: stop managing fragmented files and data and start selling. We transform your catalog into an intelligent ecosystem where each SKU is enriched, localized, and ready to be published on your sales channels (Print, Catalogs, eCommerce, Marketplaces, B2B Area, etc.).

1. Define the Data Model

Before uploading products, think about the data sources to import: this will help organize clear and easy access for all involved teams without complicating or burdening the information structure.

• Activate Languages (Locales): Define in which languages and regions you want to describe and narrate your products.

• Configure Attributes: Define key fields such as Color, Material, Season.

• Configure at least one Media attribute: This is where you can start enjoying the power of the unified platform. With media attributes you can merge your Products with their Digital Assets and represent the product story with the most appropriate Digital Assets.

Choose your preferred execution mode:

• From operational interface: Manually configure Attributes, Families and all the information you need if you want full immediate control of the structure.

• With your Customer Success: if you have a complex catalog, share a sample set with your reference Customer Success, they will know how to assist you. 

• AI Data Modeling: Leverage artificial intelligence (currently in beta via MCP) to analyze your data and automatically generate the most suitable model for your catalog. Ask your Customer Success for info to try this mode.

## In-depth articles
- How to configure the Data Model
- Products Localization Configuration
- Media attributes: what they are and how to create them
- Configure MCP for AI Data Modeling (BETA) 

2. Manage the Variant model (optional)

In THRON you can structure your products in two ways:

• Simple Product: a unique product, without variations (e.g. a book, an accessory in a single version).
• Product with Variants: a "parent" product (Product Master) that groups multiple versions of the same item, each defined by specific attributes such as Size or Color. Each unique combination corresponds to a distinct SKU.

If your products have variations (e.g. Size and color), configure variants to manage complexity without duplicating work.

You can configure which attributes belong to the Master level (e.g. generic description, editorial photo) and therefore common to all variants and which instead at Variant level (e.g. Size, Color, detail photo).

## In-depth articles
- Product Families and Variations Configuration Guide

3. Import your Products

Now that you have the container ready, fill it with products. The goal is to have a single organized and efficient access point to all product information.

Choose how to populate the catalog:

• XLSX Upload (Manual): Use the template to learn the basic format, fill the file with your data and proceed. The system will guide you in the Column Mapping: associate each column of your file to the corresponding attribute created in the Data Model. It is the fastest method for the first upload or for spot updates.

• Asset & Product Import (Automatic): Configure automation to synchronize THRON with your data source (e.g. ERP or server folders). The system will automatically import and update records, reducing manual intervention to zero.

## In-depth articles
- Import your Products via Interface (manual)
- Import your Products with an automation (Automated)

4. Organize the team and accesses

In THRON collaboration is granular: you don't have to give the house keys to everyone. Define work groups and decide who can modify critical data and who can only consult.

Permission assignment example:

• eCommerce Admin Group: They have full access. They manage the bulk import from ERP, define technical attributes and can govern the Completeness Markers to decide what goes online.

• Product Specialist Group: They have read-only access to technical data, but can modify the Editorial and Commercial attribute groups. Their task is to write captivating descriptions, manage translations in active Localizations and link Assets to product cards.

• External Agencies Group: They have limited access, for example, to an Incoming Media folder and read-only visibility on some product attributes (e.g. the SKU). They can upload photos and videos, but do not have visibility on the rest of the master data or publication logic.

## In-depth articles
- Configure users and work groups
- Attribute Rights - Coming soon
- Catalog and Category Rights - Coming soon

5. Enrich Product Cards with Digital Assets

Forget manual linking. In THRON, images and videos "talk" to your products: if you update a datum on the product card, the asset reflects the change instantly. Thanks to Data Inheritance, your files inherit the product metadata, making searching your archive surgically precise.

Now you can transform your product catalog into a multimedia experience. Don't limit yourself to a single image: use Media Attributes to organize every type of content needed for sales.

What is a Media Attribute? It is a "special field" of the product card designed to host digital assets. Instead of having a messy list of files, you can create them sorted specifically for each purpose. For example: 

• PDP Media: For official images of the product card.

• Brochures and Manuals: For technical PDFs or user guides.

• Lifestyle & Social: For emotional videos or contextualized shots.

• Certifications: For confidential documents (e.g. safety data sheets).

Here too you have two options: 

• Manual linking: You choose, file by file. It is the ideal solution for spot uploads or content that does not follow rules (e.g. a special Brochure).
• Automatic Linking: Let the platform work. It is the solution for those who have hundreds of SKUs and want zero stress. It relies on naming conventions. 

## In-depth articles
- Leverage Media attributes to link Products and Digital Assets
- Benefits of using media attributes (best practice)
- Asset & Product automatic link automation
- Discover how Assets inherit Product attributes

6. Set Completeness Markers of product cards (Optional)

When you are ready to distribute your products on sales channels (eCommerce, Marketplaces, PDF Catalogs, B2B Area), configure attribute mapping and automatic feeds. Do not do it immediately, wait until you have identified the channels to feed.

## In-depth articles
- What they are and how to configure Completeness Markers

7. Create Relations between Products (Optional)

In THRON, a product is never an island. Thanks to Reference Attributes, you can link product cards together to automatically manage accessories, compatibility ("works with...") or style suggestions ("complete the look").

We advise against creating a single generic "Related products" field.

Divide relationships by intention. For example:

• Technical Reference: For spare parts and technical compatibility.

• Bundle: For products that "go well together".

• Look Reference: For the "Total Look" or products suggested by the fashion coordinator.

• Showcases: Create thematic selections (e.g. "Christmas Special or Trade Fair").

## In-depth articles
- Relations between Products - Reference Attributes: what they are and how to configure them

Welcome to your Product Catalog environment on THRON

At this point:

• Your Product Catalog in THRON  is operational and data is protected from unauthorized changes.

• The catalog is structured, consistent and multilingual.

• The team can work by Progress Statuses, drastically reducing time-to-market.

• Publication on channels can be automated and therefore free from manual errors.

## What can you do now? 
Now you can feed your frontends without friction. Follow the guide:
- Channel Activation

Need help?

For technical issues, write to support@thron.com.