How to Configure Marketplace Attribute Mapping in Omnitron?

Omnitron Marketplace Mapper enables users to configure and match their product attributes and attribute values for Marketplace Sales Channels. It also allows users to verify the correctness of product features and values prior to listing them for sale.

Marketplace Attributes​

The Marketplace Attributes page lists the attributes for the related Marketplace. On this page, Users can view the PK (Primary Key), Name, Related Mapping Rule Set Name and Updated Date of the Marketplace Attributes, and filter Marketplace Attributes with respect to Attribute Name and/or Attribute Set values.

Marketplace Attribute Values​

The Marketplace Attribute Values page lists the attribute values of the related Marketplace’s attributes. On this page, users can view the Primary Key (PK), Attribute, Name, Value, Updated Date of the Marketplace Attribute Values and filter Marketplace Attribute Values with respect to Name, Attribute, and/or Attribute Set values.

• Primary Key: ID of the relevant attribute value, has to be unique.

• Attribute: Attribute that the relevant attribute value depends on.

• Name (Attribute Value’s Label): Label of the attribute value. For example, there can be an attribute value with a label of “White” and a value of “0001”. In other words the Name of the attribute value.

• Value (Attribute Value): Attribute Value identifier, has to be unique.

Mapper​

The Mapper page lists predefined Mapping Rule Sets of rules for Marketplace Attributes. A Mapping Rule can be described as the set of attribute value mappings between the Omnitron and related Marketplace. Users can create a New Mapping Rule Set by clicking on the + Add New Attribute Mapping Rule button, or edit existing rule sets by clicking on the Edit button on the row.

Additionally, users can filter Mapping Rules with respect to Rule Set Name, Target Attribute, Target Attribute Set, Creation Date and Updated Date on this page. This allows them to conveniently find and manage the specific mapping rules they need for their products listed on the marketplace.

Add/Edit Mapping Rule Form​

By clicking the + Add New Attribute Mapping Rule button or the Edit button in the list, users can access Add/Edit Mapping Rule Form. To create a set of attribute value mappings between the Omnitron and related Marketplace, users must complete the Mapping Rule Name and Target Attribute (Related Marketplace Attribute) fields. If the mapping rule requires customization based on categories, users can select the specific category for customization in the Target Attribute Set field, located next to the Target Attribute.

Target Attributes can be filtered by clicking on the “Show only required target attributes” checkbox.

Users can create or edit Mapping Rules for Omnitron Attributes and related Marketplace Attributes by choosing the four primary Mapping Methods that Akinon Mapper offers:

• Standard Mapping

• Fixed Value Mapping

• Merge Fields Mapping

• Custom Mapping

Standard Mapping​

The Standard Mapping method is used to directly map Omnitron Attribute & Attribute Values to Marketplace Attribute & Attribute values. Users can select which Omnitron Attribute Value will be matched to which Marketplace Attribute Value. After selecting the Standard Mapping Method, users should select the Source Attribute (Related Omnitron Attribute) for direct mapping.

If users want to manually match their Source Attribute Values to Target Attribute Values, the Add static value to value mapping checkbox should be marked. With this action, all of the Source Attribute Values will be listed, and users can select the related Target Attribute Values for each.

If both the Source and Target Attributes’ data types are “dropdown”, an auto-mapping is performed with respect to the attribute values. Auto-mapped attribute values can be distinguished from the corresponding green checkbox icon. This feature can be used only for Adding a New Mapping Rule.

If the Show Description checkbox is checked, target and source attribute labels can be seen, if not, attribute values can be seen on the Attribute Values list.

On the other hand, if users want to send their Source Attribute Values directly to the related Target Attribute, the Add static value to value mapping checkbox should not be marked. Please note that Source Attribute Values’ parameter should either be present as a Marketplace Attribute Value or the related Marketplace Attribute accepts free-text inputs for the Target Attribute while the checkbox is not marked.

Fixed Value Mapping​

The Fixed Value mapping method is used to assign a fixed value to a Marketplace Attribute for all the products being sent. There are three options for the fixed Marketplace Attribute Value:

• Null: Target Attribute Value is sent as null for all marketplace products (e.g., "Origin":null).

• Empty String: Target Attribute Value is sent as an empty string for all marketplace products (e.g., "Origin":"").

• Custom: A specified custom value is sent for all marketplace products (e.g., "Size": "Standard").

  

Merge Fields Mapping​

The Merge Fields mapping method allows users to create an attribute value by combining Source Attribute Values or Fixed Values into a corresponding Marketplace Attribute Value.

By selecting the Concatenate function under the Function tab, users can merge one or more Source Attributes with Fixed Values in the Content tab. The Output Preview field displays the template (showing which Source Attributes and/or Fixed Values were used to create the Marketplace Attribute Value) and the resulting value under the "Preview Output Template" and "Sample Output Value" sections, respectively.

Custom Mapping​

The Custom mapping method is used for more complex mappings that cannot be handled by the other three mapping methods. Some of the Rule Set components are explained below.

• type: Defines the Mapping Type and can be one of the following:

  • attribute: Maps a source attribute to a target attribute.

  • attribute_kwargs: Maps a source attribute to a target attribute as an object.

  • field: Uses various fields (such as SKU, base code, or localized attribute values) as the target attribute value.

  • stdout: Uses fixed values as the target attribute value.

  • mapping: Maps source attribute values to target attribute values individually.

• key: Source Attribute Key, required when the Type is set to attribute, attribute_kwargs, or field.

• condition: The condition that must be met for Marketplace Attribute Value integration. For example, when the Source Attribute Value is "Unisex Child" or "Child", the attribute value mapping will integrate accordingly.

    {
        "query": {
            "attributes__integration_gender__in": [
                "Unisex Child",
                "Child"
            ]
        },
        "condition_type": "liquer"
    }

• is_object: Indicates whether the rule’s output will be sent as an object.

  • is_object: true output example:

         "size": {
              "label": "36",
              "value": "0012",
              "data_type": "dropdown",
              "_translations": {
                  "us": {
                      "label": "6"
                  }
              }
          }

  • is_object: false output example:

      "size": "0012"

• order: The priority value of the rule.

• concat: Specifies whether the rule’s output should be concatenated with other rules. This is a boolean parameter.

• prefix: The prefix value for the target Marketplace Attribute Value, which is used when the concat parameter is set to true.

• default_value: The fallback Marketplace Attribute Value if the mapping fails.

• mapping_dict: A dictionary mapping Source Attribute Values to Marketplace Attribute Values. It must be used when the Type is set to mapping.

  • Example of mapping_dict:

    {
        "Red": "0005",
        "Blue": "0001",
        "Grey": "0004",
        "Brown": "0007",
        "White": "0002",
        "Yellow": "0006"
    }

    

Custom Mapping Example:

The field If fails, send a default value as; located at the bottom of the page is used to send a fixed value to the respective target attribute in case an error occurs during the mapping process, as defined in the mappings above.

After the relevant Mapping Method and mapping configuration are filled out, by clicking on the Save button, a Mapping Rule can be created/edited. By clicking on the Clear the Rule button, relevant Mapping Rule can be cleared. In other words, the mapping rule still exists, but without any configuration.

Mapping Control​

The Mapping Control function enables users to verify which values will be sent to the marketplace for the attributes of a product after the mapping processes.

When the Mapping Control list page is opened, all products on the catalog for the related Marketplace are listed. Users can view the products that are in the Marketplace Catalog with respect to their all attributes, SKU, Base Code, Category, etc information, filter the Marketplace-Catalog products with respect to all-product-attributes, preview & download the Marketplace Attributes and Marketplace Attribute Values for filtered products on this page.

After filtering the Marketplace-Catalog Products, clicking on the Show Mapping Result button opens the Mapping Control pop-up, in which the Marketplace Attributes and Marketplace Attributes can be seen and downloaded by the users.

Warning​

1. Mapper page and its functions can also be used for Marketplaces with the Sales Channel type.

2. However, when editing schemas created under Sales Channel, users are warned about the possibility of function loss.

   
3. In marketplaces with Sales Channel type, the old mapping screens (Schema, Attribute Mapping, Category Attribute Mapping) cannot be used.

   
4. The Mapping Control function is only applicable to Marketplaces with the Sales Channel type.