Authoring Hub - Sets definition guidelines

This article explains how to define and create sets in the catalog.

Overview

A set is a top-level item used to group multiple related products into a functional unit (e.g., showering, vanity, bathing). Sets are used primarily for AutoDesign placement and AI recognition.

Important: The set itself does not own configuration logic. All configuration logic remains on the sub-items.

Set structure

A set is built as a top-level (dummy) item with:

• A specific and clear classification
• Sub-items representing the possible products

Sub-items can be linked via spaceholders or direct links, depending on the approach and use case.

Example: Showering set

Set - Showering

• tray
• enclosure
• shower
• faucet
• accessories

Set types

Static sets

In this model, specific items are linked directly to the set, defining a unique set with a predefined combination.

Use case: When the manufacturer wants to sell or propose a specific combination of items.

Dynamic sets

A dynamic set uses sub-items such as configurators or spaceholders that contain the configuration logic and specific features.

Use case: Supports a guided design experience, allowing designers and users to easily change items within the set.

Logical structure and granularity

Driver sub-item

One of the sub-items acts as the driver. Sets are typically created per baseItemType and classification (often per dimension or type). This ensures valid combinations and avoids incorrect configurations.

Configuration logic

All configuration logic (features, options, restrictions, compatibility rules) must remain on the sub-items. The set only groups items and provides context.

Recommended approach

Create one set per base item to:

• Avoid invalid combinations
• Prevent incorrect configurations
• Enable better control of compatible components

Example

Note: For items that are resizable or can have different dimensions, the ideal scenario would be a single set with range values or proposed values. This would reduce the number of sets to create. However, this is not currently possible due to limitations in AutoDesign and AI services.

What to avoid

Visibility on browser and item list

Set visibility on the browser and item list depends on agreements with the manufacturer regarding how sets will be used in designs.

Browser visibility

Follow manufacturer agreements to set the correct visibility:

• Set visible=false  if the set should not appear in the browser

Item list visibility

If items must appear on the item list to group sub-items, the set must have a refCode.

Important:

• The set cannot have the same refCode as any other item (otherwise it will be priced as that item)
• Use a generic refCode that does not exist in the catalog
• There is no specific rule or pattern for set refCodes — just ensure the refCode does not exist within price values

Creating a set

Before starting

Identify which sub-items will be used in the set.

Steps

1. Create a dummy item for the set
2. Define the classification for the set
3. Define the item dimensions considering the sub-items (use geometry bounding box if needed)
4. Add the sub-items (static or dynamic) that will assemble the set
5. Ensure sub-items carry the features and configuration logic