Setting up Relations
Overview
This guide provides a step-by-step process for suppliers to correctly set up bundled items in an Excel catalog upload template. Bundled items are products or services sold together as a single offering. Proper configuration is essential to ensure accurate pricing, order processing, and catalog visibility.
In our online catalog, bundles are groups of related items linked to a main product. These items can be customized in different ways. Some related items can be marked as mandatory—for example, when a car must be linked to a required leasing contract. Other related items can be sorted into categories such as accessories, similar products, spare parts, or replacements. In the shop, all of these appear under the 'Related Products' section, organized into tabs for easy navigation.
General Relation Setup Requirements
To create a relation between products, ensure the following data is provided:
SupplierID: Identifier of the product’s supplier.
SupplierAID: Article identifier assigned by the supplier.
Catalog Container ID (optional): Required only if the referenced product is located in a different catalog than the main article.
These values are necessary to establish a valid reference in the system.

Input : Supplier ID / SupplierAID
It is also important to determine whether the related products are mandatory. In the catalog template for your main item, you will find a section for related products that appears as follows:

Relationship Setup : Catalog Template Required Fields
Simple Steps to Set Up Product Relations
Get Product Details:
Find the SupplierID and SupplierAID for the related product.
Check Catalog Location:
If the related product is in another catalog, note its Catalog ID (Container ID).
Decide Relation Importance:
Decide if the related product is mandatory or optional.
Fill the Catalog Template:
Step 1: Enter SupplierID.
Step 2: Enter SupplierAID.
Step 3: Add the Catalog ID if it’s from another catalog.
Step 4: Choose the Relation Type (e.g., accessories, spare part). If unsure, it defaults to "mandatory".
Step 5: Mark with "X" if the related product is mandatory, leave blank if not.
Step 6: Set the display order (position in the catalog).
Step 7: Define the quantity—some relation types require it to be fixed and meet a minimum order quantity
Product relation types define how related items connect to the main product. These relations are shown in shop groups and help guide users toward relevant or required items. Below are the main relation types with their descriptions:
Relation Types:
Type | Description |
accessories | Items that extend or enhance the functionality of the main product. |
similar | Items that serve the same purpose and can be used interchangeably. |
sparepart | Replacement items used for repair or maintenance of the main product. |
followup | Newer or more advanced items that serve the same purpose as the main article. |
consists_of | Component items that together form a parts list for the main product. |
diff_orderunits | Same product offered in different packaging or unit sizes (e.g., bottle, barrel). |

Relation Types, Mandatory and Relations
Important information
There is a difference in how relations are displayed to your customer, depending on the technical implementation. Following we will show both ways to use mandatory relations, depending of the implementation of your customer. To check, what implementation the customer is using, get back to service.beneering.com to ask for it.
Standalone BeNeering Cloud
mandatory_choose_quantity
Products that must be purchased together, with the option to select the quantity.

Setting up values in Catalog Template
Item Displayed on Shop Screen

mandatory_default_quantity
Required items with a predefined default quantity.

Setting up values in Catalog Template
Item Displayed on Shop Screen

mandatory_choose_item
Adds a new tab for selecting a single item, with a fixed quantity

Setting up values in Catalog Template
Item Displayed on Shop Screen

MyCart BeNeering Cloud
In MyCart implementation, no mandatory relations are available at the moment. Please check again later in this documentation to see, if they are supported now