There are different types of product attributes used to present the product information on an eCommerce website or a marketplace: drop-down lists, numbered lists, slider (ranged) attributes, color swatches, simple text fields, etc. Based on this variety of options, there are different types of fields distinguished on Sellbery by the type of value they represent, their purpose, and their function on Sellbery.

Field types by a purpose:

Required. The list of required fields is predefined by the Export Point API. It is a number of mandatory fields without which the products cannot be uploaded to the Export Point.
Preferred. These fields are not mandatory but are usually as important as the required ones. If it is possible based on the product data in the Import Point, the preferred fields should be mapped for each connection.
Optional. These are all fields that are not required or preferred. They may or may not be mapped depending on what product parameters you wish to transfer to the Export Point.
Variant. A specific field type which is used for mapping fields that are used for product variations. Variant fields from the Import Point need to be mapped to the variant fields of the Export Point if you want your configurable (variation) products to be exported properly.

Field types by value:

String - the value of this field is a simple string (e.g. text or numeric value such as name or description);
Decimal - the value of this field is a decimal (e.g. price);
Integer - the value of this field is an integer (e.g. quantity);
Boolean (logical - true or false) - this field contains "Yes" or "No" value (e.g. "is customizable = yes").

Field types by function:

1. Simple. A basic field that can contain any kind of text or numeric value. Is available for both Import and Export points. Is marked with a "circle" at the Mapping section.

2. Enum. A simple field that allows the selection of one option from the list. This field type is only available for the Export point, can be mapped with the help of the "Add Custom Value" option. Is marked with a "numbered list" sign at the Mapping section.

3. Object. It's a composite field that cannot be mapped directly because it always contains enclosed fields (like a category tree). The enclosed fields may be of all possible types. The mapping is only done for the enclosed fields, never for the object itself. It is available for both Import and Export points. Is marked with a "triangle" at the Mapping section.

4. Array. A composite field that cannot be mapped directly because it consists of a set of options, each of which must be mapped separately inside an array. This type is available for both Import and Export points. Is marked with a "rhombus" ("diamond") sign at the Mapping section.

On Sellbery, the mapping rules can be created in several possible ways:


This means that a field from an Import point is mapped to a field from an Export point directly.

Click on the field in the Import Point column then click on the corresponding field in the Export Point column, and your Mapping Rule is ready!

The fields may be of the same type (string to string, array to array) or different types (string to integer, object to simple). When a mapping rule is created for the fields of different types, Sellbery displays a warning message and asks if it is necessary to modify the data for the target field (e.g. compress the string if it is too long for the target system, or use a different field type if the current one is not allowed by the target system).

Custom Value

The "Add Custom Value" option is used if there is no corresponding Import Point attribute that could be mapped to the Export point field (e.g. "Condition" enum field with "new", "used", "refurbished" etc. options, only one of which can be applied).

Also, this option is used to assign a custom value to the Export point field if the value existing in the Import point cannot be used for some reason (e.g. apply a custom "quantity" value or set your own brand name for all products).

Composite Value

The "Add Composite Value" option is used to modify the value of some Export fields based on the seller's requirements. For example, add a custom brand name to the 'title' field or combine several attribute values into one Export field (short description + description, name + size + color, etc.). This functionality is designed to apply certain data changes to all of the exported products at once without having to modify them on the Import Point.

In order to create a Mapping rule with composite value, follow the below procedure:

Click "Add Composite Value" button;
Select the Export point field that will contain the composite value;
Click on the Import point fields that you want to include in the composite value or type the necessary custom text in the pop-up and save the field.

# is used as a delimiter between different attributes or custom text included in a composite value.

If you click on the Import point field but do not see it added to the Composite Value pop-up, try to switch to a different browser, e.g. Google Chrome.


The "Converter" function at the Mapping section can be used for changing the numeric values for the Export system based on the selected conversion rules. For example, multiply the price by 2 or increase it by 15%.

To convert the attribute value, enable Converter on the Mapping page, click on the Import point field then the Export point field. The conversion pop-up will open and you will see the options for converting the value of the selected attribute.

On the screenshot above, you can see that the field types are different - "String" on the Import Point (source value) will be converted to "Decimal" on the Export point.

The Conversion Strategy drop-down allows selection between Integer and Decimal for the format of the Export field. If you choose Decimal, you should also set a "Fraction value" which indicates the number of signs after the comma that will be shown in the price field (12,99 would be a decimal with two signs after the comma, for example).

The Action field allows selection between "Add" and "Multiply" options indicating how the price should be changed. The Value field is used for entering the actual value by which the price must be changed (e.g. enter "2" for multiplying the price twice, or 0.05 to increase it by 5%).

If you have any questions about mapping some specific fields, please check out the information in the Integrations Guide or contact our support team.
Was this article helpful?
Thank you!