Amazon Marketplace Setup Configurations
Last updated
Was this helpful?
Last updated
Was this helpful?
The marketplace dashboard application needs to be installed on ACC. To do this, log in using the username and password at the link.
From the menu, go to the App Store, select Amazon, then choose the relevant project and proceed with the installation.
After the installation process, go to My Applications from the left menu, select the relevant application, and enter the application page.
Once the necessary build and deployment process is complete, the Amazon application will appear in the left menu on Omnitron.
Once the application deployment is completed on ACC, an automatic sales channel will be created in Omnitron. The fields within this sales channel need to be filled.
The Sales Channel can be accessed via Omnitron > Settings > Sales Channels.
Field Name
Description
Example
Information
Requirement
Channel Name
Sales Channel Name
Amazon:1_Channel
Automatically created.
Required (should not be changed)
Catalog Name
Catalog Name Created for Amazon
*May vary from brand to brand
Amazon:1_Catalog
Automatically created.
Required (should not be changed)
Channel Type
Channel Type
*All sales channel types are available as a dropdown in Omnitron.
Sales Channel
Automatically created.
Required (should not be changed)
Status
The sales channel will not work until it is activated.
Inactive
By default, it is set to inactive (it needs to be activated).
Required
Schema Type
This is the place where the information to be stored in the sales channel settings is defined. The necessary information for the operation of this sales channel is fetched in the form within Omnitron using the details here. A schema containing the minimum required information for the sales channel to function is automatically created. Additionally, you can add information you wish to store here (for example, information needed for ERP integration of the sales channel). The key-value information that will be in the Channel Config is located here. The dictionary in the Value section contains key, label, required, and data_type.
key -> Information about which key will be used to access the data via channel config.
label -> Information about how it will appear in the form on the Omnitron Sales Channel settings interface.
required -> Information on whether the value is mandatory (true/false).
data_type -> Information about the data type of the value (list, text, integer, bool, json).
{
"region": {
"key": "region",
"label": "Region",
"required": true,
"data_type": "text"
},
"base_url": {
"key": "base_url",
"label": "Base Url",
"required": true,
"data_type": "text"
},
"erp_code": {
"key": "erp_code",
"label": "Erp Code",
"required": false,
"data_type": "text"
},
"client_id": {
"key": "client_id",
"label": "Client Id",
"required": true,
"data_type": "text"
}
}
It has been automatically filled with predefined information.
Required: (Additions can be made, but existing fields should not be changed)
Base Url
API URL for Amazon
https://sellingpartnerapi-eu.amazon.com
It is pre-filled.
Required
Client Id
The client secret specified for Akinon in the Amazon API.
default
It is pre-filled.
Required
Client Secret
The client secret specified for Akinon in the Amazon API.
default
It is pre-filled.
Required
Access Key
The access key specified for Akinon in the Amazon API.
default
It is pre-filled.
Required
Secret Key
The secret key specified for Akinon in the Amazon API.
default
It is pre-filled.
Required
Market Place Id
The marketplace ID specified for Akinon in the Amazon API.
default
It is pre-filled.
Required
Refresh Token
The token used in service requests for the Amazon API.
default
It is obtained by contacting Amazon.
Required
Seller Id
The seller ID assigned by Amazon for the brand, specific to the Amazon API.
default
It is obtained by contacting Amazon.
Required
Region
The AWS region information that determines the sales area for the Amazon API.
eu-west-1
It is pre-filled.
Required
Category Ids
The main category IDs from Amazon are added here
21324944031,21324945031
12466781031,12466782031
12467009031,12467010031
It is left blank by default. (It is obtained by contacting Amazon.)
Required
Feature Flags
It allows the activation or deactivation of running processes. The important point to note here is that even if the related process will not run, it must still be added here as false. (Detailed information about feature flags is provided in the Feature Flags section in Heading 9 below.)
{
"get_orders": true,
"schema_update": false,
"send_products": true,
"get_cancel_orders": true,
"get_refund_orders": true,
"get_updated_orders": true,
"send_update_orders": true,
"send_delete_products": true,
"send_updated_product_price": true,
"send_updated_product_stock": true
}
All default flags are set to false.
Required
Send Shipping Info
The setting that determines whether the shipping process will be managed by Amazon or the brand.
Inactive
It is set to inactive by default. (If inactive or not selected, Amazon will manage the shipping process. If active, the brand will manage the shipping process.)
Optional
Cargo Company Id
The cargo company ID on the Omnitron side, used to determine the shipping information when an order from Amazon is written to Omnitron. (If Send Shipping Info is not active, the Shipping Company will be automatically updated based on the shipping information received from Amazon after the order is written to Omnitron).
4
By default, it is left blank.
Required
Use Neighborhood
This setting determines whether the neighborhood information in the address data will be used when creating the order. If active, the neighborhood information in the shipping address on the order will be processed during the address creation step for the relevant order in Omnitron.
Inactive
By default, it is set to inactive. If the neighborhood information is mandatory in the company's system, this field should be activated.
Optional
Order Number Format
When pulling order data from Amazon to Omnitron, the order number is set according to this format. If this value is left blank, the order will be written to Omnitron with the default Amazon order ID format (403-1234567-8765432).
AMZ-{n1}{n3}{n2}
By default, it is left blank.
Optional
Order Start Date
The start date of the order integration. The format should be %Y-%m-%dT%H:%M:%SZ.
2024-08-29T14:30:00Z
By default, it is left blank.
The information should be filled in when the order retrieval process starts.
Use Channel Id In Address Mapping
If the brand wishes, this field can be activated to perform address mapping operations on a channel basis. When this field is activated, the channel ID information is added to the address data, and during search operations, queries are made using the sales channel filter with the channelId_address information.
Inactive
By default, it is left blank.
Optional
Exclude Cargo Company Ids
If Send Shipping Info is not active, the shipping company will be updated based on the shipping information received from Amazon when the order is pulled. The cargo company IDs to be ignored when updating the shipping information in the order lines are specified here.
132
159
By default, it is left blank.
Optional
Default Reason Id
If the reason ID in the returned data pulled from Amazon is not found in the Refund Reason Mapping, the refund data will be pulled using the Omnitron refund reason ID entered in this field and written to Omnitron. (The ID information can be retrieved via {omniton_url}/api/v1/channel/{channel_id}/cancellation_reasons/?cancellation_type=refund&is_active=true)
5
By default, it is left blank.
Required
Refund Reason Mapping
{
“CR-UNWANTED_ITEM”:”7” ,
“AMZ-PG-BAD-DESC”:”5”, “CR-DEFECTIVE”:”4”,
“CR-ORDERED_WRONG_ITEM”:”11”,
“CR-FOUND_BETTER_PRICE”:”12”,
“CR-DAMAGED_BY_FC”:”13”,
“CR-MISSED_ESTIMATED_DELIVERY”:”14”,
“CR-MISSING_PARTS”:”15”,
“CR-DAMAGED_BY_CARRIER”:”16”,
“CR-SWITCHEROO”:”17”,
“CR-EXTRA_ITEM”:”18”
}
By default, it is left blank. (When left blank, the return reasons will be written using the 'Default Reason Id' information from the previous step when return data is pulled from Amazon.)
Optional
Refund Start Date
It is the initial start date for when returns will begin to be retrieved. The format should be %Y-%m-%dT%H:%M:%SZ.
2024-08-20T14:30:00Z
By default, it is left blank.
Optional
ORDER REFUNDABLE DAYS
Specifies how many days after the order creation date the return can be made.
7
By default, it is left blank.
Optional (When left blank, the default is 7 days)
Failed Integration
Records with errors during the integration process are held for a certain period with a penalty. (Detailed information is provided in Section 3 under 'Failed Integration Settings' below).
{
"order": {
"RETRY_INTERVAL": 28800,
"EXPIRATION_DATE": 57601,
"MAX_RETRY_COUNT": 3
},
"DEFAULT": {
"RETRY_INTERVAL": 28800,
"EXPIRATION_DATE": 57601,
"MAX_RETRY_COUNT": 2
},
"product": {
"RETRY_INTERVAL": 28800,
"EXPIRATION_DATE": 57601,
"MAX_RETRY_COUNT": 2
},
"productprice": {
"RETRY_INTERVAL": 28800,
"EXPIRATION_DATE": 57601,
"MAX_RETRY_COUNT": 2
},
"productstock": {
"RETRY_INTERVAL": 28800,
"EXPIRATION_DATE": 57601,
"MAX_RETRY_COUNT": 2
},
"sent_to_remote": {
"EXPIRATION_HOUR": 6
}
}
By default, it is pre-filled.
Required
Erp Code
Sales channel code defined for Amazon in the brand.
AMZ
By default, it is left blank.
Optional
Cancellation Reason Id
Specifies which reason ID will be used when writing canceled orders pulled from Amazon to Omnitron. (The ID information can be obtained via the endpoint {omniton_url}/api/v1/channel/{channel_id}/cancellation_reasons/?cancellation_type=cancel&is_active=true)
4
By default, it is left blank.
Required
Attribute Set Strategy
Specifies the strategy setting that determines which attribute set the products belong to.
CategoryNode
By default, it is pre-filled.
Required (Should not be changed)
Shipping Company Mapping
{
“mng”: “MNG Kargo”,
“yurtici”:”Yurtiçi Kargo”
}
By default, it is left blank.
Optional
Buffer Stock
Specifies the value to be deducted from the product's current stock when feeding stock to Amazon. If no value is entered, the product's current stock will be sent to Amazon
3
By default, it is left blank.
Optional
Has Barcode Exemption
Used when sending products to Amazon, the barcode exemption allows your products to be exempt from the requirement to use universal barcodes (such as UPC, EAN) when selling. This applies typically when you want to list your own brand or product on Amazon.
Inactive
By default, it is left blank.
Optional
Is Fba Channel
This setting determines whether the channel will operate as FBA (Fulfillment by Amazon).
Inactive
The default is left blank.
Optional
Records with errors during the integration process are temporarily delayed with a penalty. The values of 'RETRY_INTERVAL' and 'EXPIRATION_DATE' are in seconds.
The 'RETRY_INTERVAL' value specifies how long to wait when an error occurs. The 'EXPIRATION_DATE' value indicates how long the retries will continue after an error. The 'MAX_RETRY_COUNT' value defines the maximum number of retry attempts.
'sent_to_remote' determines how many hours Amazon will process and provide the result of the request once it is sent to Amazon.
Any update made to these values will be applicable for the next operations. For example, if a SKU was placed in the penalty queue with a retry interval of 3 hours for a stock update, and this retry interval is updated to 2 hours, the next time the product’s stock update fails after the original 3-hour penalty period, it will fall into the penalty queue with the new 2-hour retry interval.
For example;
If there is any error related to a product during the product submission process, such as missing stock or price data, incomplete mapping on the Omnitron side, or issues on the Amazon side (e.g., product not found, no response from Amazon within the time set by sent_to_remote), the product will fall into the penalty queue with the current failed integration setting. During the penalty period, no submission process can be performed for that product. As a result, this product will not be retried for submission within a certain period, preventing it from blocking the processing of other records.
The category tree is generated based on the added Category IDs within the sales channel.
Once the category tree is pulled into Omnitron, it can be viewed under the Category Management section when Amazon is selected as the Sales Channel.
After successfully completing this process (which can be monitored through the logs), the flow that pulls the attributes will be triggered. Following the completion of attribute-related tasks (when the Default Attributes flow has run and finished successfully), the next steps should be taken.
Once the category tree is pulled, the user needs to perform category mappings through the Mapper.
The Akinon Mapper function within Omnitron allows users to configure and manage the feature values of the products they wish to sell on marketplace sales channels according to the marketplace's requirements. Additionally, it provides the opportunity to check whether the features and feature values are correct before the products are listed for sale.
On Amazon, products need to be added to the relevant category tree. Each product should be added to only one category; otherwise, an error will occur during the submission process.
When the Amazon marketplace application is installed in the relevant brand's Omnitron, it will appear as 'Amazon' in the left-hand menu.
Dashboard data related to the Amazon marketplace application is available on this screen.
TOTAL SKU IN CATALOG The number of SKUs with a product type of "simple" and an "active" status that are included in the relevant catalog.
NUMBER OF SKUs ON SALE The number of SKUs that have been sent to the marketplace and are currently for sale.
TOTAL SKU DIFFERENCE The number of SKUs that are included in the catalog but not available for sale on the marketplace.In this section, a comparison is made between sellable products in Omnitron and the products listed for sale on the marketplace. Specifically, products in Omnitron are considered if they have a price, stock greater than zero, a category, a product image, and are listed in the catalog.
NUMBER OF SKUs WITH PRICE DIFFERENCE (FIXED) The number of SKUs with a price difference between Omnitron and the marketplace. If any discrepancies are found, a task is triggered to correct the differences, and the discrepancies are resolved.
TOTAL STOCK IN CATALOG The total stock quantity of all products in the marketplace catalog.
TOTAL STOCK ON SALE The total stock quantity of products that are currently on sale in the marketplace.
TOTAL STOCK DIFFERENCE The stock of products that are in the catalog but not on sale in the marketplace.
TOTAL NUMBER OF SKUs WITH STOCK DIFFERENCE The number of SKUs with a stock difference between Omnitron and the marketplace. If any discrepancies are found, a task is triggered to correct the differences, and the discrepancies are resolved.
The screen contains logs and reports.
The logs of the flows are located on this screen.
Category Node The flow that pulls the entire category tree of the main categories defined in the channel settings into Omnitron.
Category Attributes The flow that pulls the category attributes defined in the channel settings into Omnitron.
Default Attributes The flow that prepares predefined fields (such as remote_id, title, etc.) for the mapping process during product transmission.
Product The flow that sends products entered in Omnitron to the marketplace.
Delete Product The flow that removes products from the catalog in Omnitron and takes them off sale in the marketplace.
Stock The flow that sends updated stock information for products with updated stock in Omnitron to the marketplace.
Price The flow that sends updated price information for products with updated prices in Omnitron to the marketplace.
Order The flow that pulls orders from the marketplace into Omnitron.
Update Order The flow that updates the order status, invoice, and tracking number in the marketplace when they are updated in Omnitron.
Cancel The flow that updates the status in Omnitron for orders that have been canceled on the marketplace.
Get Updated Orders The flow that updates the status in Omnitron for orders whose status has changed on the marketplace.
Refund The flow that updates the status in Omnitron for orders that have been refunded on the marketplace.
Compare Attributes The flow that updates the status in Omnitron for category attributes whose status has changed on the marketplace.
The reporting screen displays products that have been added to the catalog in Omnitron but are not listed for sale on Amazon, highlighting discrepancies between the price and stock information on Amazon and the data in Omnitron.
The screen for creating, adjusting, and viewing alarms related to flows.
The following steps should be followed for errors encountered in the logs:
'Stock data not found' error indicates that there is no stock data for the product. The stock data for the relevant product needs to be added.
'Price data not found' error indicates that there is no price data for the product. The price data for the relevant product needs to be added.
'... attribute is required' error indicates a missing mapping for the related attribute. The mapping process should be done as outlined in Section 5 (Marketplace Mapping).
'Unreported order of ERP can not be canceled' error indicates that the order has not yet been transmitted to ERP. To proceed with the cancellation, the order must first be transmitted to ERP.
'Address is not valid. channel: 137 code: 137_Merkez model: Township city id: .., city name: …' error indicates that the Township mapping in the address data of the order needs to be done.
Stopping the shipment of faulty products or resending a product that couldn’t be shipped; Faulty products are attempted to be sent for a period based on the rules defined in the Failed Integration section of the channel settings. According to this rule, a manual trigger is required for products that have stopped being attempted.
To remove products from penalties in this situation, go to the Omnitron settings in the right menu, select Sales Channels and the relevant channel. On the page that appears, click the 'Update by Uploading Files' button located to the left of 'Delete Bulk Failed Integration' in the upper-right corner to upload a CSV file.
Error received after product trigger: "The relevant record is not in queue. The item may have been penalized or check product is saleable"
This error occurs when the products being sent have already been transmitted, and they are considered as updates rather than product creation. The same error will be encountered if a product still in the transmission process is triggered again.
Regarding the status/resolution of orders that cannot be updated on the MPD side via the Order Update (send_update_orders) flow:
If there is an ongoing or initiated return process for the order, it will not be updated.
The tracking number value will only be provided if the “Send Shipping Info” flag is active. For more details, refer to the "Feature Flags" section.
The order status cannot be updated retroactively. Therefore, manual intervention in the flows should be avoided.
The frequency value is set by default as shown in the table below. These values can be modified by the Marketplace team.
Flag
Description
Frequency
get_orders
The flow ensures that orders with the statuses 'PartiallyShipped', 'Unshipped', 'Shipped', and 'InvoiceUnconfirmed' from Amazon are pulled into Omnitron, going 12 hours back from the flow's execution time. Before activating this flag, the settings in the second section above (Sales Channel Definition), including Cargo Company Id, Use Neighborhood, Send Shipping Info, Order Number Format, Exclude Cargo Company Ids, Order Start Date, and Use Channel Id In Address Mapping, must be properly configured.
It runs every 5 minutes.
get_cancel_orders
The flow pulls orders with the 'Cancelled' status from Amazon, going 12 hours back from the flow's execution time, and creates a cancellation request in Omnitron with a maximum cancellation plan count of 6. Before activating this flag, the Cancellation Reason Id setting in the second section above (Sales Channel Definition) must be properly configured.
It runs every 5 minutes.
get_refund_orders
The flow pulls returns from Amazon and creates a return request in Omnitron. Before activating this flag, the settings in the second section above (Sales Channel Definition), including Default Reason Id, Refund Reason Mapping, Refund Start Date, and ORDER REFUNDABLE DAYS, must be properly configured."
It runs every 5 minutes.
send_update_orders
This flow ensures the update of invoice and shipping information for the order on Amazon's side.
Before activating this flag, the Send Shipping Info and Shipping Company Mapping settings in the second section above (Sales Channel Configuration) must be properly configured.
This flow updates the invoice and order status. The tracking number will only be sent if the Send Shipping Info flag is active.
It runs every 5 minutes.
send_delete_products
The flow ensures that products removed from the catalog have their stock set to zero on the Amazon side.
It runs every 5 minutes.
send_products
The flow ensures that products added to or updated in the catalog, along with their price and stock, are sent to Amazon. Before activating this flag, the Buffer Stock setting in the second section above (Sales Channel Definition) must be properly configured.
It runs every 5 minutes.
get_updated_orders
The flow checks the status of orders in Omnitron with 'Preparing' or 'Shipped' statuses on Amazon and updates those with 'Delivered' status to 'Delivered' in Omnitron. Before activating this flag, the Send Shipping Info setting in the second section above (Sales Channel Definition) must be properly configured.
It runs every morning at 06:00.
send_updated_product_price
The flow ensures that the product prices that need to be updated are sent to Amazon.
It runs every 5 minutes.
send_updated_product_stock
The flow ensures that the product stock that needs to be updated is sent to Amazon. Before activating this flag, the Buffer Stock setting in the second section above (Sales Channel Definition) must be properly configured.
It runs every minute.
The return reason information on the Amazon side is matched with the return reason information in Omnitron for the return process. The key value should be the reason ID from Amazon (which can be found at this link:), and the value should be the reason ID information from Omnitron. (The ID information can be retrieved via {omniton_url}/api/v1/channel/{channel_id}/cancellation_reasons/?cancellation_type=refund&is_active=true)
When the brand manages the shipping processes (if send_shipping_info is active), it is used to map the shipping company slug in Omnitron (Omnitron -> Settings -> Shipping Companies -> Shipping Company Title) with the carrier information on Amazon (can be obtained from the CarrierName section at).
Detailed documentation about the Mapper and the definitions that need to be made in the Mapper can be found in here.
The product trigger under the Dashboard is only for creating operations. If a product update is desired, it should be done via CSV by selecting the 'Update Product Version Date in Bulk' section in the top-right of the channel settings, then choosing 'Update by Uploading File.' For trigger operations, this document can be used: .
