Authoring Hub - Target market

Please note that items aren’t copied from the source catalog; the Target Market catalog creates a new itemRef instead.

To do that, on the three dots, choose Add Catalog Dependencies Browser.

This opens a new tab. Drag it to the right side of the screen and drop it to view both catalogs side by side.

Click Add dependency catalog, then choose the catalog you want to reference.

In the Dependency Browser, select the desired items and click Add X items to view.

Please note the following:

• A new itemRef is created in the selected group in the editor
• The item keeps the same code as in the dependency catalog, and its itemRef points back to that source catalog.

Alternatively, you can drag an entire group from the Dependency Browser and drop it into Items.

For other ways to add items (such as creating them from scratch or duplicating) see this article.

Please note that target market catalogs have restricted editing capabilities compared to standard catalogs — many advanced fields are not available.

Classification, lifecycle, clearanceDistances, insertionOffsets, variantProposals, engineeringData are available for editing in standard catalog only. 

In a target market catalog, you can:

- Add the item name, refCodes, image, and dimensions
- Specify the item description
- Add moreInfoLinks
- Assign the item to a group using the groupRefs field
- Add context information
- Link restrictionRefs.

To import items or groups from source catalog, click three dots next to the catalog name and choose Import. 

Select the file, pick the Items or Item Groups option as destination and click Import.

Please make sure that Items and Groups in import files follow the following structures to ensure proper hierarchy and categorization.

Items Files

The import file should define the item hierarchy structure.

You can find a sample import file attached at the end of this article. The file should contain the following fields:

• code – a unique identifier for each item (e.g., a_01, a_02)
• groupRefs – an array of group codes the item belongs to (e.g., ["WCS_WCA_D1V_W30"]), linking items to their parent groups from the group hierarchy, using this syntax

• itemRef – a reference to the actual item definition in the source catalog, using the format CATALOG_REFERENCE_CODE:ITEM_CODE (e.g., NOBILIA:w20_1).
  To find the source catalog reference code, click the three dots next to the catalog name and copy its reference code (e.g. 'd').  

  

Items with the same groupRefs are organized under the same category. Multiple items can reference different product variants while belonging to the same group.

Item Groups Files

The file should define a hierarchical tree structure where items are organized through parent-child relationships.

• Top-level groups (e.g., WCS, BCA codes on the example below) have no parent
• Child groups reference their parent in the _PARENT_ column (e.g., WCS_WCA has parent WCS)
• Deeper nesting creates sub-categories (e.g., BCA_DRW_D1D is a child of BCA_DRW, which is itself a child of BCA)

You can find a sample import file attached at the end of this article.

To add the same restriction to multiple items, return to the Items tab, select the items by checking them, click the Actions button, and choose Link Restrictions.

A list of all restrictions will be displayed. Select the required restriction, click Use Template.

Click Save to apply the changes to the items.

You can find more detailed instructions on creating and linking restrictions in this article.

Pricing is not automatically inherited from the source catalog. To ensure items calculate correctly in a target market catalog, the following must be configured manually: 

• Pricing tasks
• Price tables
• Price rules
• Price values

For more information on configuring pricing, see the Pricing logic summary article.