N11 Marketplace Setup Configurations
Last updated
Was this helpful?
Last updated
Was this helpful?
The Marketplace Dashboard application needs to be installed on ACC. To log into your ACC account, access using your username and password. Click on the App Store in the navigation menu on the left side. Find N11 and start the installation process by selecting your relevant project.
Once the installation process is complete, click on "My Applications" in the left menu. Select the relevant application and go to the application page. Complete the necessary build and deployment processes. Once these steps are finished, the N11 application will appear in the left menu in Omnitron.
After 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 out.
Access the settings for the sales channel via: Omnitron > Settings > Sales Channels.
Field Name
Description
Example
Information
Requirement
Channel Name
Sales Channel Name
N11
Automatically created.
Required (should not be changed)
Catalog Name
Catalog Name Created for N11
*May vary from brand to brand.
N11
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 unless it is activated.
Inactive
By default, it is set to inactive. (It needs to be activated)
Required
Schema Type
This is where the information to be kept in the sales channel settings is defined. The information here is used to generate the required forms in Omnitron for the operation of the sales channel. A schema containing the minimum requirements for the sales channel to work is automatically created. Additionally, you can add information here that you wish to keep (for example, information required for ERP integration of the sales channel). The key-value information that will be included in the Channel Config is provided here. The dictionary in the value section contains key, label, required, and data_type.
key -> The key used to access the information via the channel config.
label -> How the information will appear in the form in the Omnitron Sales Channel settings interface.
required -> Whether the value is required (true/false).
data_type -> The data type of the value (list, text, integer, bool, json).
{
"store_code": {
"key": "StoreCode",
"label": "Mağaza Kodu",
"required": true,
"data_type": "text"
},
"base_url": {
"key": "base_url",
"label": "Base Url",
"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)
App Key
App Key Information Defined for the Brand by N11 (This information is obtained from N11.)
********************
It is obtained by contacting N11.
Required
App Secret
App Secret Information Defined for the Brand by N11 (This information is obtained from N11.)
********************
It is obtained by contacting N11.
Required
Base Url
API URL for N11
https://api.n11.com/ws/
It is pre-filled by default.
Required
Sales Url
N11 Site URL
https://www.n11.com/
It is pre-filled by default.
Required
ERP Code
Sales Channel Code Defined for N11 in the Brand
4000
It is left empty by default.
Optional
Category Ids
Main category IDs to be used for N11 are added here.
1001770
1002032
1001873
It is left empty by default.
Required
Feature Flags
It allows the activation or deactivation of active processes. The important point to note here is that even if the related process will not be active, it must still be added here as false. (Detailed information about feature flags is provided in the "Feature Flags" section under Heading 9 below.)
{ "send_delete_products": true,
"get_orders": true,
"get_cancel_orders": true,
"send_update_orders": false,
"send_invoice_link": true,
"send_products_inserted": true
}
All predefined flags are set to false.
Required
Deny Reason Id
It is the information about which ID will be used when rejecting a cancellation request in the Cancel Request flow in N11. (This information is obtained from N11.)
Possible values:
61 -> Out of Stock Product
62 -> Campaign Ended
63 -> Product Delivered in Good Condition
64 -> Product Damaged
81 -> Product Not Accepted for Return Due to Legislation
81
It is left empty by default. The possible values are provided in the first column.
Required
Cancellation Reason Id
It is the information about which reason ID will be written to Omnitron when fetching cancelled orders from N11. (The ID information can be obtained via the endpoint {omnitron_url}/api/v1/channel/{channel_id}/cancellation_reasons/?cancellation_type=cancel&is_active=true)
4
It is left empty by default. It can be obtained from the cancellation reasons in the Omnitron interface.
Required
Unsupplied Reason Id
It is the reason ID that will be assigned for packages with the "Unsupplied" status when canceled orders are pulled from N11. (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
The default is left empty. Cancellation reasons can be retrieved from the Omnitron interface.
Optional
Unpacked Reason Id
It is the reason ID that will be assigned for packages with the "Unpacked" status when canceled orders are pulled from N11. (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
The default is left empty. Cancellation reasons can be retrieved from the Omnitron interface.
Optional
Refund Reason Id
It is the information about which reason ID will be written in Omnitron when fetching cancelled orders from N11, if the related order has an invoice, and a cancellation request of type refund is created. (The ID information can be obtained via the endpoint {omnitron_url}/api/v1/channel/{channel_id}/cancellation_reasons/?cancellation_type=refund&is_active=true)
2
It is left empty by default. It can be obtained from the cancellation reasons in the Omnitron interface.
Required
Cancellation Map
The cancellation reason information on N11 is matched with the cancellation reason information in Omnitron for the cancellation process. The key in this mapping should be the reason ID from N11, and the value should be the reason ID from Omnitron. (The ID information can be obtained via {omnitron_url}/api/v1/channel/{channel_id}/cancellation_reasons/?cancellation_type=cancel&is_active=true)
{
“501”:”7” , “551”:”4”
}
It is left empty by default. (If left empty, when cancellation information is fetched from N11, the "Cancellation Reason Id" from the previous step will be used to write the return reasons.)
Optional
Cargo Company Id
It is the cargo company ID on the Omnitron side that will be used to determine the selected cargo information when an order is written from N11 to Omnitron. If this value is empty, Omnitron will use the predefined mapping in the "Cargo Company Settings" section based on the cargo information from N11 and select the first available cargo company. If the cargo company is not listed in the cargo company settings, the order cannot be written.
104
It is left empty by default.
Optional
Use Neighborhood
Whether the neighborhood information will be used in the address data when creating an order is determined by this information. If active, the neighborhood information in the shipping and billing addresses on the order will be processed during the address creation step for the relevant order in Omnitron.
Inactive
It is left inactive by default. If the neighborhood information is required in the company's system, this field should be activated.
Optional
Failed Integration
Records with errors in the integration process are held for a certain period with a penalty. (Detailed information is provided under Heading 3, "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
}
}
It is pre-filled by default.
Required
Send Shipping Info
This is related to whether N11 or the brand will manage the shipping process.
Inactive
It is left inactive by default. (If inactive or not selected, N11 will manage the shipping process, meaning N11 will write the order information to the shipping company. If active, the brand will manage the shipping process itself.)
Optional
Cancellation Reason Type Id
It is the cancellation reason type that allows partial cancellations in Omnitron to be communicated to N11 in a partial manner. (This information is obtained from N11.)
Possible values:
61 -> Out of Stock
62 -> Defective/Flawed/Damaged Product
63 -> Incorrect Price
64 -> Force Majeure
65 -> Other
65
It is left empty by default. (This field should be filled if the send_cancel_order_items flag, which ensures that partial cancellations in Omnitron are sent to N11, is enabled.)
Optional
Attribute Set Strategy
It is the strategy setting that defines which feature set the products belong to.
CategoryNode
It is pre-filled by default.
Required (Should not be changed)
Exclude Cargo Company Ids
The cargo company IDs to be ignored when fetching orders are specified here. When an order comes from N11 with a cargo company corresponding to the IDs defined here, the information entered in the Cargo Company ID will be used to write the order data to Omnitron.
132
159
It is left empty by default.
Optional
Order Start Date
It is the start date of the order integration. The format should be dd/MM/yyyy.
30/07/2023
It is left empty by default.
This information should be filled when the order fetching starts.
Get Discount Amount
This refers to the use of the discount information when pulling the order data. If this value is inactive or not selected, the discount information is not used. If active, the discount information is used.
Passive
It is left false by default.
Optional
Order Number Format
When pulling the order data from N11 to Omnitron, the order number is adjusted according to this format. If this value is left blank, the order number will be written to Omnitron by default in the format of “{orderNumber}-{id}.
N11-{orderNumber}-{id}
It is left empty by default.
Optional
Use Channel ID In Address Mapping
If the brand wishes, they can activate this field to perform address mapping operations on a channel basis. If this field is activated, the channel ID will be added before the address data in the mapping process, and during search operations, the query will be made using the sales channel filter with the channelId_address information.
Inactive
It is left empty by default.
Optional
Get Discount Amount
It is related to the use of discount information when retrieving the order data. If this value is inactive or not selected at all, the discount information will not be used. If it is active, the discount information will be used.
Inactive
It is left empty by default.
Optional
Order Number Format
When retrieving the order data from N11 to Omnitron, the order number is set according to this format. If this value is left blank, the order number will be written to Omnitron by default in the format "{orderNumber}-{id}"..
N11-{orderNumber}-{id}
It is left empty by default.
Optional
Buffer Stock
It is the value to be deducted from the product's current stock when stock is fed to N11. If no value is entered, the product's current stock will be sent to N11.
3
It is left empty by default.
Optional
OMS Enabled
If N11 manages the shipping processes for brands using OMS, and if the tracking number for the OMS package should be written to the Omnitron order's tracking number field using the campaignNumber (or trackingNumber if campaignNumber is not available) obtained from N11, this setting should be enabled.
Inactive
It is left empty by default.
Optional
Records with errors in the integration process are held for a certain period with a penalty. The values for "RETRY_INTERVAL" and "EXPIRATION_DATE" are given in seconds.
RETRY_INTERVAL: The duration to wait when an error occurs.
EXPIRATION_DATE: The time until which the system will attempt to retry after an error.
MAX_RETRY_COUNT: The maximum number of retry attempts.
sent_to_remote: This setting determines how many hours N11 will allow to obtain the result of the operation once the request has been sent to N11.
Any update made to these values will apply to the next processes that will run. For example, if a SKU's stock update previously went into the penalty queue with a retry interval of 3 hours, and the retry interval is updated to 2 hours, then after the previous penalty period of 3 hours has passed, if the system tries the stock update again and encounters an error, it will enter the penalty queue with the new retry interval of 2 hours.
For example;
If there is any error for a product in the requests to be sent to N11 for product shipment (such as missing stock or price data, incomplete mapping on the Omnitron side) or on the N11 side (such as product not found, no response from N11 within the time given by sent_to_remote), the product will be penalized according to the current failed integration settings. During the penalty period, no shipment operation will be performed for this product. This ensures that the product will not be retried for shipment within a certain period due to the error it encountered.
The category tree is drawn based on the Category IDs added within the sales channel.
Once the category tree is pulled into Omnitron, when "N11" is selected under "Sales Channels," the category tree can be viewed in the "Category Management" section.
Once this process is successfully completed (it can be tracked from the logs), the flow responsible for pulling the attributes will run. After the attribute-related operations are completed (the "Create Default Attribute" flow has run and finished successfully), the next steps should be carried out.
After the category tree pulling process is completed, users need to make category mappings through the Mapper.
The Akinon Mapper function within Omnitron allows users to configure and manage the features of the products they want to list on marketplace sales channels according to the requirements of each marketplace. Additionally, this function provides the ability to check whether the features and attribute values are correct before the products go live, helping to prevent potential errors.
On the N11 platform, products need to be added to the relevant category tree. Each product should only be added to one category. Otherwise, you may encounter an error during the submission process by N11.
When the N11 marketplace application is installed on the relevant brand's Omnitron, it will appear as "N11" in the left-hand menu.
The dashboard data related to the N11 marketplace application is available on this screen.
TOTAL SKU IN CATALOG The total number of SKUs added to the relevant catalog, where the product type is "simple" and the status is "active".
NUMBER OF SKUs ON SALE The number of SKUs that have been sent to the marketplace and are currently on sale.
TOTAL SKU DIFFERENCE It refers to 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 the products available for sale in Omnitron and those listed for sale on the marketplace. Specifically, products in Omnitron are considered based on having a price, stock greater than zero, a category, an image, and being listed in the catalog.
NUMBER OF SKUs WITH PRICE DIFFERENCE (FIXED) The number of SKUs with a price discrepancy between Omnitron and the marketplace. In case of discrepancies, a separate task was executed to fix the differences, and they have been resolved.
TOTAL STOCK IN CATALOG The total stock quantity of all products listed in the marketplace catalog.
TOTAL STOCK ON SALE The total stock quantity of products currently on sale in the marketplace.
TOTAL STOCK DIFFERENCE The total stock quantity of products that are in the catalog but not currently available for sale on the marketplace.
NUMBER OF SKUs WITH STOCK DIFFERENCE The number of SKUs with stock discrepancies between Omnitron and the marketplace. In case of discrepancies, a separate task was executed to fix the differences, and they have been resolved.
This screen contains the logs and reports.
The logs of the flows are available on this screen.
Category Node A flow that ensures the full category tree structure of the main categories entered in the channel settings is pulled into Omnitron.
Order Create A flow that enables orders from the marketplace to be imported into Omnitron.
Product Create A flow that sends products entered in Omnitron to the marketplace.
Product Update A flow that sends updated products from Omnitron to the marketplace.
Product Delete A flow that removes products deleted from the Omnitron catalog from sale on the marketplace.
Order Update A flow that updates the order status, invoice, and tracking number in the marketplace based on updates made in Omnitron.
Cancel/Refund Orders A flow that updates the status of cancelled or refunded orders from the marketplace in Omnitron.
Cancellation Requests A flow that creates cancellation requests in Omnitron for orders with cancellation requests initiated in the marketplace.
Send Cancel Order Items A flow that sends order lines related to approved cancellation requests from Omnitron to the marketplace.
Stock A flow that sends the updated stock information of products from Omnitron to the marketplace.
Price A flow that sends updated price information of products from Omnitron to the marketplace.
Category Attribute and Values A flow that pulls the category attributes entered in the channel settings into Omnitron.
Create Default Attributes A flow that prepares predefined fields (e.g., remote_id, title, etc.) for use during the product mapping process.
Get Updated Orders A flow that updates the status of orders in Omnitron based on changes made in the marketplace.
Split Packages A flow that sends order split requests from Omnitron or another OMS to the marketplace.
Compare Attributes A flow that updates the attribute values of categories in Omnitron based on changes made in the marketplace.
The screen is used to view reports about the mismatch between the price and stock information on N11 and the data in Omnitron for products that have been added to the catalog in Omnitron but have not been listed for sale on N11.
The screen allows you to create, set, and view alarms related to the flows.
Here are the errors you may encounter in the logs and the steps to resolve them:
“Stock data not found”: This 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”: This error indicates that there is no price data for the product. The price data for the relevant product needs to be added.
“Product not found”: This error shows that the product has not been sent to N11. This error may occur in the Delete product, Stock Update, or Price Update flows. Check the product-related error in the Product Create or Update logs.
“The product is listed in the category [category name] on N11 with category ID [category ID]. You can enter this ID to resend the product.”: This error indicates that the N11 side did not accept the product submission with the category selected in Omnitron. The category information for the product in Omnitron should be updated as specified in the error.
“This product is already pending approval. It will be published once approved.”: This error indicates that the product has already been successfully sent to N11. Approval needs to be done from the N11 panel.
“Unreported order of ERP cannot be canceled”: This error indicates that the relevant order has not been transmitted to ERP yet. To proceed with the cancellation, the order must first be sent to ERP.
“Address is not valid. channel: 137 code: 137_Merkez model: Township city id: …, city name: ….”: This error indicates that the mapping for the Township in the address data within the order needs to be done.
“The product you entered is listed with XXXX seller code on your side. You can update your product through this product.”: This error occurs during product submission when the seller code sent differs at the product level in Omnitron. To resolve this, you can activate the send_delete_product_seller_code flag to trigger the Send Delete Product Seller Code flow.
Product triggering under the Dashboard is only for the create process. If you want to trigger a product update, it must be done via CSV in the "Update by Uploading a File" section under "Update Bulk Product Version Date" in the channel settings (top right corner).
Stopping the Transmission of Faulty Products or Resending Unsent Products Faulty products are retried for a certain period according to the rules defined in Failed Integration under channel settings. Products that stop being retried based on this rule require manual triggering. To remove products from this state and lift the penalty, navigate to Omnitron > Settings > Sales Channels, select the relevant channel, and use the "Update by Uploading Files" button (located to the left of "Delete Bulk Failed Integration") to upload a CSV file.
If too many faulty products accumulate in the queue, since processing is done in batches of 50, the next products may not be processed. There are two solutions to this:
Immediately fixing errors related to mapping, catalog, stock, price, etc., and then triggering the CSV update.
Adjusting the Failed Integration settings in the channel settings to ensure proper time intervals.
For the "Failed to suggest product to the catalog" error, if the issue is related to attribute values, the Category Attributes flow should be executed to fetch the latest attribute values. If necessary, the Compare Attributes flow should also be triggered.
The error message received after product triggering — "The relevant record is not in queue. The item may have been penalized or check product is saleable" —
Occurs when the products being sent have already been transmitted, and are therefore evaluated as updates rather than creations.
This error can also occur if a product that is still in the sending process is triggered again.
For issues or resolutions related to 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 will only be populated if the “Send Shipping Info” feature is explicitly marked as active. Please refer to the “Feature Flags” section for details.
The status of an order cannot be updated retroactively. Therefore, manual intervention in the flows should be avoided.
The frequency values are by default as shown in the table below. These values can be modified by the marketplace team.
Flag
Description
Operating Frequency
get_orders
This ensures the pulling of orders with "New" and "LATE_SHIPMENT" statuses from N11, based on the flow's operation date, into Omnitron. When orders are pulled from N11, the order lines are created in the "waiting for approval" status. Once the corresponding order lines are approved on the N11 side, they transition to the "approved" status. Before activating this flag, the settings listed under the second heading above (Sales Channel Definition), such as Cargo Company Id, Use Neighborhood, Send Shipping Info, Exclude Cargo Company Ids, Order Start Date, Use Channel Id In Address Mapping, Get Discount Amount,Order Number Format and OMS Enabled, must be properly configured.
It runs every 5 minutes for the "New" status and every 8 hours for the "LATE_SHIPMENT" status.
send_update_orders
It allows retrieving updated orders and sending them to N11 with item-specific "shipping company and tracking number" information. The shipping company information is mapped from the shipping data in Omnitron to the corresponding shipping information on N11. The tracking number is the tracking number of the order in Omnitron.
With this flow, the invoice and order status are updated. However, the tracking number is only sent if Send Shipping Info is active.
It runs every 5 minutes.
split_packages
This feature allows orders created on N11 to be split into multiple packages. It operates by sending a request in the specified format to the marketplace endpoint via OMS.
OMS Web Hook Configuration in Omnitron:
Navigate to Omnitron → Akinon OMS → Settings → Web Hooks → New Web Hook.
Set the Target URL as: https://{mp_frontend_url}/flow-trigger/{mp_frontend_url_slug}/split_packages
Parameter Definitions: mp_frontend_url:
Can be found in Acc → Projects → Applications → N11 → URL.
mp_frontend_url_slug:
The part of the URL before “.lb.akinoncloud.com”.
Event Type: order.split_package_{oms_channel_id}
Not: The channel ID here refers to the channel ID in OMS, not the Omnitron channel ID.
Additional Headers:
{"Authorization":"Token xxx"}
Config:
{}
Retry Countdown Config:
{"choice":"fixed","kwargs":{"seconds":120
It operates through an outbound trigger sent by OMS.
send_delete_products
It ensures that the stock of products removed from the catalog is set to 0 on the N11 side.
It runs every 5 minutes.
send_products_inserted
It ensures that products added to the catalog are sent/updated to N11. Before activating this flag, the Buffer Stock setting mentioned in the second heading above (Sales Channel Definition) must be properly configured.
It runs every 5 minutes.
get_updated_order_items
It allows sending requests going back 15 days from the flow's execution time to retrieve orders with "Completed" and "Shipped" statuses on N11, and updates the status and tracking number information in Omnitron on an item basis.
It runs every morning at 06:00.
get_cancellation_request
It retrieves the "REQUESTED" status order line cancellation requests from N11 within the last 24 hours from the flow's execution time. If the relevant order has an invoice, it rejects the request with a Deny Reason Id. If there is no invoice, the cancellation request is approved on N11 and the order is moved to the "COMPLETED" status, allowing it to appear in the "Cancel Order" list.
Before activating this flag, the Deny Reason Id must be entered as specified in the second heading above (Sales Channel Definition).
It runs every 5 minutes.
get_cancel_orders
It retrieves the "COMPLETED" status order line cancellation requests from N11 within the last 24 hours from the flow's execution time. If the order line has an invoice in Omnitron, it processes a return; if there is no invoice, it ensures the cancellation request is created with a maximum of 6 cancellation plan attempts. Before activating this flag, the Cancellation Reason Id, Cancellation Map, and Refund Reason Id settings, as specified in the second heading above (Sales Channel Definition), must be properly configured.
.
It runs every 5 minutes.
send_updated_product_price
It ensures that the updated product prices are sent to N11.
It runs every 5 minutes.
send_updated_product_stock
It ensures that the updated product stock levels are sent to N11. Before activating this flag, the Buffer Stock setting, as specified in the second heading above (Sales Channel Definition), must be properly configured.
It runs every minute.
handle_package_combinations
After the OMS package splitting process, when Omnitron pulls the changes made by OMS, it ensures that the package information of orders with updated order item tracking details is reported to N11 as "combine/separate."
It runs every 5 minutes.
send_cancel_order_items
It ensures that partial cancellations made on the Omnitron side are reflected as partial cancellations on N11. Before activating this flag, the Cancellation Reason Type Id setting, as specified in the second heading above (Sales Channel Definition), must be properly configured.
It runs every 5 minutes.
For more information about the Mapper and the definitions you need to make, you can refer to .
The mapping operations that must be performed specifically for N11 can be found in .
You can refer to this document for triggering processes: .
