# Mapper
Please review this documentation to learn about the capabilities, usage scenarios, and standard operational instructions offered by Akinon Mapper.
## Introduction
The purpose of the Mapper page is to correctly map marketplace attribute values with the corresponding attribute values in Omnitron.
This mapping ensures that:
* Product data is sent to the marketplace in the correct format.
* Required fields are fully completed.
* Integration errors caused by data inconsistency are prevented.
* Manual operation load is reduced.
* The mapping process is accelerated thanks to AI support.
With the new screen and AI-supported mapping features, this process is now much faster and more user-friendly.
**General Page Structure:**
The Mapper screen consists of 3 main sections:
* **Top Area:** Category selection
* **Left Panel:** Marketplace Attribute List
* **Right Panel:** Omnitron Mapping Area
## Using Mapper
{% stepper %}
{% step %}
#### STEP 1: Category Selection
The category selection area is located in the upper section of the page.
There are two different ways to use this:
**1.1 If a Category is Selected**
* The mapping performed is only valid for the selected category.
* Different mapping rules can be defined for different categories.
* It is preferred, especially in attribute structures that vary based on the category.
For example:
* "Size" mapping might be different in the Shoe category,
* "Size" mapping might be different in the Textile category.
In this case, a specific rule must be defined by selecting a category.
**1.2 If No Category is Selected**
* The mapping performed is valid for all categories.
* A global mapping rule is created.
This usage is:
* Ideal for attributes that are common across all categories.
* For example, general fields like "Color", "Brand", "Gender".
{% endstep %}
{% step %}
#### STEP 2: Reviewing Marketplace Attributes
After category selection, the marketplace attributes are listed on the left side.
The list is ordered according to the following logic:
**2.1 Required and Mapped Attributes**
* Located at the top of the list.
* Have a green check mark and a required label next to them.
* Mapping is complete for these attributes.
**2.2 Required and Unmapped Attributes**
* Shown only with the required label.
* These are fields that have not been mapped yet.
* They must be mapped when sending products to the marketplace.
* If unmapped, they should be completed as a priority.
**2.3 Mapped Attributes**
* These are attributes that have been mapped but are not required.
* Shown only with a green check mark.
**2.4 Unmapped Attributes**
* These are attributes that are not required and have not been mapped yet.
{% endstep %}
{% step %}
#### STEP 3: Selecting the Marketplace Attribute to be Mapped
The marketplace attribute to be mapped is selected from the left panel.
Examples:
* Color
* Size
* Gender
* Material
* Season
When selected, the right panel becomes active and the relevant mapping screen opens.
{% endstep %}
{% step %}
#### STEP 4: Entering the Rule Name
First, the Rule Name is entered in the right panel.
This field:
* Is used to define the mapping rule.
* Must be given a meaningful and descriptive name.
Examples:
* Color Mapping Rule
* Size Mapping Rule
* Gender Mapping
{% endstep %}
{% step %}
#### STEP 5: Selecting the Mapping Method
The user selects one of the following 4 methods:
1. Standard
2. Fixed
3. Merge
4. Custom
The details of these methods are explained in separate headings below. The following steps are specific to the Standard mapping method.
{% endstep %}
{% step %}
#### STEP 6: Selecting the Source Attribute
This area lists the attributes in Omnitron.
Here:
* It is determined which Omnitron attribute the selected marketplace attribute will be mapped with.
Example:
Marketplace Attribute: Color\
Source Attribute: The "Color" attribute in Omnitron
After this selection, the system loads the values.
{% endstep %}
{% step %}
#### STEP 7: Value-Based Mapping
After the source attribute is selected, in the lower section of the screen:
* On the left side → Omnitron values
* On the right side → Marketplace values
are listed.
**7.1 Automatic Mapping**
If:
* The data type of both sides is "dropdown list"
* And the label values are exactly the same
The system performs automatic mapping.
These mapping:
* Are shown in green color.
* Come pre-selected automatically.
* Only work when creating a new rule.
This feature provides significant time savings.
**7.2 Manual Mapping**
For values that do not map automatically, the user can make a manual selection.
How is it done?
* From the dropdown list opposite the Omnitron value
* The appropriate marketplace value is selected.
Manually performed mappings:
* Are shown in orange color.
* Indicate user intervention.
{% endstep %}
{% step %}
#### STEP 8: AI-Supported Mapping
There are two different artificial intelligence actions on the Mapper screen.
**8.1 Map Unmapped Values**
This feature:
* Takes all values that have not been mapped yet.
* Artificial intelligence generates the most suitable mapping suggestions.
* Displays the results in a popup screen.
Within the popup:
* Omnitron value
* Current marketplace value
* AI suggestion
* Approval sign
are found.
The user can:
* Approve all suggestions.
* Approve only selected ones.
The approved suggestions are automatically reflected in the form.
This feature provides a great advantage, especially for attributes with hundreds of values.
**8.2 Re-map Mapped Values**
This feature:
* Analyzes previously mapped values.
* AI offers a suggestion if it finds a more accurate map.
Example:
"Dark Brown" might have been mapped to "Light Brown".
AI can suggest changing this to a more appropriate marketplace value.
The user can:
* Keep the current map.
* Accept the AI suggestion.
This feature increases mapping quality.
{% endstep %}
{% step %}
#### STEP 9: Saving Operation
After all mappings are complete:
* The Save button is clicked.
* The rule is created or updated.
{% endstep %}
{% endstepper %}
## Mapping Methods
### Standard
This is the most frequently used method.
It directly maps Omnitron attributes and values to marketplace attributes and values.
### Fixed
When the Fixed option is selected, the value entered in this field is used directly by the system as the value to be sent. Therefore, the value to be defined in the system for the relevant attribute should be entered, not the visible label.
For example, if the label of the attribute is "Other" but its corresponding value in the system is "1234", the expression to be sent should be "1234", not "Other".
### Merge
Multiple Omnitron attributes are combined to create a single marketplace field.
For example:
Brand + Model + Size → Can be combined into a single field and sent to the relevant marketplace.
The merging process can be checked in the preview area.
### Custom
This is a mapping method designed to be used in more complex scenarios.
In this method:
* Conditional rules can be written.
* Special transformation can be performed for specific values.
* The output can be an object or text.
* A default (fallback) value can be defined.
* A value dictionary (mapping dictionary) can be defined.
Example:
"Red" → "0005"\
"Blue" → "0001"
Additionally, a default value to be sent in case of an error can be determined.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.akinon.com/tutorials/omnitron/mapper.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.