Trendyol Marketplace Setup Configurations
Last updated
Was this helpful?
Last updated
Was this helpful?
The deployment of the Marketplace Dashboard application on ACC is necessary. To log in to your ACC account, access with your username and password.
Click on App Store from the navigation menu on the left. Locate Trendyol and initiate the deployment process by selecting your relevant project.
Once the deployment process is complete, click on My Applications from the left menu. Select the relevant application to navigate to the application page. Complete the necessary build and deployment processes. Upon completing these processes, the Tendyol application will become visible in the left menu of Omnitron.
After the deployment, databases and tables will be created in the backend.
After the deployment process of the application is completed in ACC, the sales channel will be automatically created in Omnitron. It is necessary to fill in the fields within this sales channel.
Access the settings for the sales channel via Omnitron > Settings > Sales Channels.
Field Name
Description
Example
Information
Required
Channel Name
Sales channel name
Trendyol
Automatically generated
Required (should not be changed)
Catalog Name
Catalog name created for Trendyol *Can vary from brand to brand
Trendyol
Automatically generated
Required (should not be changed)
Channel Type
Channel type *All sales channel types come as a dropdown in Omnitron
Sales Channel
Automatically generated
Required (should not be changed)
Status
No processes will run until the sales channel is activated
Passive
Predefined as inactive (should be activated)
Required
Schema Type
The field where information desired to be kept in the sales channel settings is defined. The information provided here and the necessary information for the operation of this sales channel are retrieved from Omnitron.
The schema containing the minimum requirements for the operation of the sales channel is automatically created. Additional information you want to keep can be added here (such as information needed for the ERP integration of the sales channel). The key-value information that will be included in Channel Config is provided here. In the "Value" section of the dictionary, you will find key, label, required, and data_type.
key -> Information on which key will be used to access the data through channel config.
label -> Information on how it will appear in the interface form in Omnitron Sales Channel settings.
required -> Information on whether the respective value is mandatory (true/false).
data_type -> Information on the data type of the respective value (list, text, integer, bool, json).
{
"store_code": {
"key": "StoreCode",
"label": "Mağaza Kodu",
"required": false,
"data_type": "text"
},
"base_url": {
"key": "base_url",
"label": "Base Url",
"required": true,
"data_type": "text"
}
}
Default information has been automatically entered.
Required (Can be added, but existing fields should not be changed)
Base Url
Trendyol's API URL
https://api.trendyol.com/sapigw
Automatically filled in by default
Required
Sales Url
Trendyol’s site URL
https://www.trendyol.com/
Automatically filled in by default
Required
Username
Seller's designated username information for Trendyol API, provided by Trendyol
******************
Obtained by contacting Trendyol (API KEY information in Trendyol Seller Panel)
Required
Password
Seller's designated password information for Trendyol API, provided by Trendyol
******************
Obtained by contacting Trendyol (API SECRET KEY information in Trendyol Seller Panel)
Required
Supplier ID
Seller's designated supplier ID information, provided by Trendyol
144
Obtained by contacting Trendyol (supplierid information in Trendyol Seller Panel)
Required
Category Ids
Main category IDs to be used via the https://api.trendyol.com/sapigw/product-categories endpoint by Trendyol
368, 522, 1070
It is left blank by default. (Obtained from Trendyol)
Required
Feature Flags
Enables the activation or deactivation of running processes. The crucial point to note here is that even if the respective process is not functioning, it must be added here with a value of false. (Detailed information about feature flags is provided in the Feature Flags section under Title 9 below.)
{
"get_brands": true,
"get_orders": true,
"get_cancel_orders": true,
"get_refund_orders": false,
"send_invoice_link": true,
"send_delete_products": true
}
All predefined flags have been set to false.
.
Required
Brands
The brand name information for the products sold by the brand on Trendyol is entered here. (This information is obtained from Trendyol.)
Akinon
It is left blank by default.
v
Cargo Company Id
The cargo company ID on the Omnitron side, used to determine the selected shipping information when transferring orders from Trendyol to Omnitron. If this value is empty, Omnitron will default to selecting the first-found cargo company based on predefined mapping made according to the cargo company in the "Cargo Company Settings" section in Omnitron, based on the shipping information received from Trendyol. If this cargo company is not added in the cargo company settings, orders cannot be written.
104
It is left blank by default.
Optional
Use Neighborhood
Whether the neighborhood information in the address data will be used during order creation is determined by this information. If it is active, when creating an order, the neighborhood information in the shipping and billing addresses on the order is processed in the step of creating the address for the relevant order in Omnitron.
Passive
Predefined as passive. If the neighborhood information is mandatory in the company's system, this field must be activated.
Optional
Default Reason Id
If the reason id in the return data retrieved from Trendyol is not included in the Refund Reason Mapping, the refund data is retrieved and written to Omnitron with the entered Omnitron refund reason id information. (The id information can be obtained with {omniton_url}/api/v1/channel/{channel_id}/cancellation_reasons/?cancellation_type=refund&is_active=true)
5
It is left blank by default.
Required
Refund Reason Mapping
Mapping the refund reason information on Trendyol with the refund reason information in Omnitron for the return process. The key should be the reason id on Trendyol (can be checked at https://developers.trendyol.com/docs/marketplace/iade-entegrasyonu/iade-sebepleri), and the value should be the reason id in Omnitron ({omniton_url}/api/v1/channel/{channel_id}/cancellation_reasons/?cancellation_type=refund&is_active=true to get id information).
{
“501”:”7” ,
“551”:”5”
}
It is left blank by default. When left blank, the refund reasons are written with the "Default Reason Id" information in the step above when return information is retrieved from Trendyol.
Optional
Refund Start Date
The initial start date information when returns will begin to be retrieved. The format should be in epoch timestamp
1696974480
It is left blank by default.
Optional
Orders Refundable Days
The information about how many days after the order creation date the return can be made.
15
Set to 15 days by default.
Optional. When left blank, the default is 15 days.
Channel Store Code
Store code information to be sent to ERP.
4042
It is left blank by default.
Optional
Failed Integration
Records with errors in the integration process are penalized and held for a certain period. (Detailed information is given in the 3rd heading in the Failed Integration Setting section 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
}
}
Automatically filled in by default.
Required
Erp Code
Sales channel code defined for Trendyol in the brand.
TY
It is left blank by default.
Optional
Send Shipping Info
The field is related to whether Trendyol or the brand will manage the shipping process.
Passive
Predefined as passive. (If passive or not selected at all, Trendyol manages the shipping process.. If active, the brand manages the shipping process itself.)
Optional
Get Discount Amount
Information about using discount data when fetching the order data. If the value is inactive or not selected, the discount information is not used. If it is active, the discount information is used.
Inactive
The default is set to inactive.
Optional
Order Number Format
When fetching the order data from Trendyol to Omnitron, the order number is adjusted according to this format. If this value is left empty, the order number will be written to Omnitron by default in the format of “{orderNumber}-{id}”
TRD-{orderNumber}-{id}
The default is left blank.
Optional
Cancellation Reason Id
Information about which reason ID will be used when fetching canceled orders from Trendyol to Omnitron. (The ID can be retrieved using the endpoint: {omnitron_url}/api/v1/channel/{channel_id}/cancellation_reasons/?cancellation_type=cancel&is_active=true)
4
The default is left blank.
Required
Unsupplied Reason Id
Information about the reason ID to be assigned for packages with the status “Unsupplied” when fetching canceled orders from Trendyol. (The ID can be retrieved using the endpoint: {omnitron_url}/api/v1/channel/{channel_id}/cancellation_reasons/?cancellation_type=cancel&is_active=true)
4
The default is left blank.
Optional (If this value is not provided, the “Cancellation Reason Id” from the previous item will be used.)
Unpacked Reason Id
Information about the reason ID to be assigned for packages with the status “Unpacked” when fetching canceled orders from Trendyol. (The ID can be retrieved using the endpoint: {omnitron_url}/api/v1/channel/{channel_id}/cancellation_reasons/?cancellation_type=cancel&is_active=true)
3
The default is left blank.
Optional (If this value is not provided, the “Cancellation Reason Id” from the previous item will be used.)
Send Cancel Reason Id
506
The default is left blank.
Optional
Attribute Set Strategy
A strategy setting that determines which feature set the products belong to.
CategoryNode
The default is filled in.
Required (Should not be changed)
Order Start Date
The start date of the order integration. The format should be dd-MM-yyyy.
30-07-2023
The default is left blank.
It should be filled in when order fetching begins
Exclude Cargo Company Ids
Cargo company IDs to be ignored when fetching orders are specified here. When an order arrives from Trendyol, the cargo company corresponding to the IDs defined here will be used, and the order data will be written to Omnitron with the information entered in the Cargo Company Id.
132
159
The default is left blank.
Optional
Exclude Send Shipping Info
The list of cargo IDs that the brand does not want to send to Trendyol. When order data is fetched from Trendyol, if the “Send Shipping Info” value is active and the cargo ID corresponding to the order’s shipping information is not in this list, the tracking number will be written as “null” to Omnitron.
104 125
The default is left blank.
Optional
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 will be added before the address data in the mapping operations, and in search operations, the address will be queried using the sales channel filter with the channelId_address information.
Inactive
The default is left blank.
Optional
Buffer Stock
The value to be deducted from the product's current stock when sending stock information to Trendyol. If no value is entered, the product's current stock will be sent to Trendyol.
3
The default is left blank.
Optional
Records with errors in the integration process are temporarily withheld with a penalty. The values for "RETRY_INTERVAL" and "EXPIRATION_DATE" are in seconds.
The RETRY_INTERVAL value indicates how long to wait when an error occurs.
The EXPIRATION_DATE value indicates until when the retry will be attempted after an error.
The MAX_RETRY_COUNT value specifies the maximum number of retry attempts.
The "sent_to_remote" setting defines how many hours Trendyol will be able to retrieve the result of the operation after the request is sent to Trendyol.
Any updates made to these values will apply to the next operations. For example, if an SKU’s stock update was previously placed in the penalty queue with a retry interval of 3 hours, and the retry interval is updated to 2 hours, the product will be retried after the 3-hour penalty period. If the update results in an error, the product will then fall into the penalty queue with the new 2-hour retry interval.
For example: If there is any error for a product during the sending process to Trendyol (e.g., missing stock, price data, incomplete mapping on the Omnitron side, or product not found, no response from Trendyol within the sent_to_remote time on the Trendyol side), the product will be penalized with the current failed integration setting. During the penalty period, no sending operations can be performed for that product. Since the product encountered an error, it will not be retried for a certain period. This ensures that the records with errors do not block the other records.
The category tree is pulled based on the Category Ids added within the sales channel.
After the category tree is pulled into Omnitron, it can be viewed under the Category Management section when Trendyol is selected as the Sales Channel.
After this process is successfully completed (can be monitored from the logs), the flow that retrieves the attributes will run. Once the attribute-related processes are completed (if the Brands flow has been successfully completed), the next steps should be followed.
Once the category tree pull step is completed, the user must perform category matching through the Mapper.
The Akinon Mapper function within Omnitron allows users to configure and manage the attribute values of the products they want to sell on marketplace sales channels. Additionally, it provides the opportunity to check whether the attributes and attribute values are correct before the products are listed for sale.
Products need to be added to the relevant category tree on Trendyol. Each product should be added to only one category. Otherwise, an error will be encountered by Trendyol during the submission process.
When the Trendyol marketplace application is installed on the relevant brand's Omnitron, it will appear as Trendyol in the left menu.
Dashboard data related to the Trendyol marketplace application is located on this screen.
TOTAL SKUs IN THE CATALOG Number of SKUs with product type "simple" and active status added to the relevant catalog
NUMBER OF SKUs ON SALE Number of SKUs sent to the marketplace and 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 that are sellable 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 included in the catalog.
NUMBER OF SKUs WITH PRICE DIFFERENCES THAT WERE FIXED Number of SKUs with price differences between Omnitron and the marketplace If differences were found, an additional task was executed to correct them and the discrepancies were resolved.
TOTAL STOCK COUNT IN THE CATALOG Total stock count of all products in the marketplace catalog
TOTAL STOCK COUNT Total stock count of products currently on sale in the marketplace
TOTAL STOCK DIFFERENCE Stock of products in the catalog that are not on sale in the marketplace
NUMBER OF SKUs WITH STOCK DIFFERENCES Number of SKUs with stock differences between Omnitron and the marketplace If differences were found, an additional task was executed to correct them and the discrepancies were resolved.
The screen where logs and reports are located.
The logs of the flows are located on this screen.
Brands Flow that enables brands entered in the channel settings to be pulled into Omnitron.
Default Attributes Flow that prepares predefined fields (remote_id, title, etc.) for the mapping process during product sending.
Category Node Flow that pulls the entire category tree structure of the main categories entered in the channel settings into Omnitron.
Category Attributes Flow that pulls the category attributes entered in the channel settings into Omnitron.
Product Create Flow that sends products created in Omnitron to the marketplace.
Product Update Flow that sends updated products in Omnitron to the marketplace.
Product Delete Flow that removes products deleted from the Omnitron catalog from sale in the marketplace.
Stock Flow that sends updated stock information of products whose stock has been updated in Omnitron to the marketplace.
Price Flow that sends updated price information of products whose prices have been updated in Omnitron to the marketplace.
Order Create Flow that pulls orders from the marketplace into Omnitron.
Order Update Flow that updates the status, invoice, or shipping tracking number of orders in the marketplace when they are updated in Omnitron.
Order Refund Approve Flow that sends approved refunds in Omnitron to the marketplace.
Reject Refund Flow that sends rejected refunds in Omnitron to the marketplace.
Order Cancel Flow that updates the status of orders cancelled in the marketplace in Omnitron.
Order Refund Flow that updates the status of fully refunded orders in the marketplace in Omnitron.
Order Items Flow that updates the status of orders in Omnitron when their status changes in the marketplace.
Send Cancel Order Items Flow that updates the status of cancelled orders in Omnitron to the marketplace.
Split Packages Flow that sends order splitting requests coming from Omnitron or another OMS system to the marketplace.
Compare Attributes Flow that updates the status of category attributes in Omnitron when they change in the marketplace.
A reporting screen for products that are added to the catalog in Omnitron but not listed for sale on Trendyol, where the price and stock information on Trendyol do not match the data in Omnitron.
The screen for creating, adjusting, and viewing alarms related to the flows.
Return requests pulled from the marketplace via the RefundOrder flow are created in Omnitron with the status OPEN and appear on specific screens for manual review and potential rejection.
If the requests reviewed on these screens are rejected, the RejectRefund flow sends the rejection reason, description, and any attached photos back to the marketplace.
Refund rejections are processed through this screen.
The following steps should be followed for errors encountered in the logs:
“Stock data not found” error indicates that the product's stock data is missing. The stock data should be added for the relevant product.
“Price data not found” error indicates that the product's price data is missing. The price data should be added for the relevant product.
“Barcode not found in your product list” and “Product not found for price and stock update” errors may occur if the product was previously successfully sent to Trendyol but has been removed from the Trendyol panel. The product’s integration action information should be deleted, and the product should be sent again to Trendyol.
“You need to contact your category responsible for the locked product” error indicates that the product is locked. The brand needs to unlock it from the panel.
“Unreported order of ERP can not be canceled” error indicates that the order has not yet been sent to ERP. To proceed with the cancellation, the order needs to be sent 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.
The "Some products not found. Product remote ids: xxx" error occurs in the order flow because the related product does not have a product integration action record. This product may have been modified through the Trendyol panel. First, check if the product exists in the catalog, then review the logs in the Product Create flow.
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, go 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:
Quickly 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 "The relevant record is not in queue. The item may have been penalized or check product is saleable" received after product triggering occurs because:
The products being sent have already been sent before, and since they are considered as product updates rather than creates, this error is encountered.
This error may also appear if a product whose sending process is already ongoing is triggered again.
For the Order Update (send_update_orders) flow, in cases where the order status cannot be updated on the MPD side:
If there is an ongoing or initiated return process for the order, it will not be updated.
The tracking number will only be updated if the “Send Shipping Info” flag is actively enabled. For more details, see the “Feature Flags” section. (Note: updates may still occur even if there is no shipping info depending on the cargo provider.)
The status of an order cannot be updated retroactively. Therefore, manual intervention in the flows is not recommended.
The frequency value is set by default as shown in the table below. These values can be changed by the Marketplace team.
Flag
Description
Frequency
get_orders
This flag allows orders with the “Created” status on Trendyol to be pulled into Omnitron, going back 12 hours from the flow’s execution time. Before activating this flag, the settings listed in the second section above (Sales Channel Definition), including Cargo Company Id, Use Neighborhood, Send Shipping Info, Get Discount Amount, Order Number Format, Exclude Cargo Company Ids, Exclude Send Shipping Info, Order Start Date, and Use Channel Id In Address Mapping, must be properly configured.
It runs every 5 minutes.
get_cancel_orders
Orders with the “Cancelled, UnSupplied, UnPacked” status on Trendyol are pulled into Omnitron, going back 12 hours from the flow’s execution time, and a cancellation request is generated with a maximum of 6 cancellation plan entries. Before activating this flag, the settings in the second section above (Sales Channel Definition), including Cancellation Reason Id, Unsupplied Reason Id, and Unpacked Reason Id, must be properly configured.
It runs every 5 minutes.
send_cancel_order_items
Ensures that the cancellation information, which was created in Omnitron (except for the reasons corresponding to the Cancellation Reason Id and Unsupplied Reason Id in the channel config), is sent to Trendyol. Before activating this flag, the settings in the second section above (Sales Channel Definition), including Send Cancel Reason Id, Cancellation Reason Id, Unsupplied Reason Id, and Unpacked Reason Id, must be properly configured.
Important Note: It is essential to distinguish between the cancellation reasons in the Order Cancel flow and those used in this flow. When performing a cancellation, the reason corresponding to the Cancellation Reason Id, Unsupplied Reason Id, and Unpacked Reason Id in the channel config should not be selected. If selected, this cancellation will not be sent to Trendyol.
It runs every 5 minutes.
get_refund_orders
Claims with the “Created” status on Trendyol are pulled, and the claim rows are retrieved to create a refund 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 Orders Refundable Days, must be properly configured.
It runs every 5 minutes.
send_update_orders
If the order status in Omnitron is "Preparing," it updates the status of the order items to "Picking," and if the order has an invoice, it updates the status to "Invoiced" on the Trendyol side. Before activating this flag, the setting for Send Shipping Info in the second section above (Sales Channel Definition) must be properly configured.
With this flow, the invoice and order status are updated. The tracking number is only sent if Send Shipping Info is active.
Carriers entered under Exclude Send Shipping Info are excluded from this process.
It runs every 5 minutes.
send_split_packages
Allows splitting orders created on Trendyol into multiple packages. It works by sending a request to the marketplace endpoint in the specified format by the OMS.
Web Hook Setting to be Entered in Omnitron:
Omnitron > Akinon OMS > Settings > Web Hooks > New Webhook
Target Url: https://mp_frontend_url/flow-trigger/mp_frontend_url_slug/split_packages
Mp_frontend_url:
It is the URL found under ACC > Projects > Applications > Trendyol. Mp_frontend_url_slug is the part before '.lb.akinoncloud.com'
Event Type: order.split_package_{oms_channel_id}
oms_channel_id endpoint:
{omnitron_url}/oms/channels/?limit=9999&limit=20&page=1
Note: 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 works through an outbound trigger sent by OMS.
send_delete_products
Ensures that the stock of products removed from the catalog is set to 0 on Trendyol.
It runs every 5 minutes.
send_products_updated
Ensures that the products to be updated are sent to Trendyol.
It runs every 5 minutes.
send_products_inserted
Ensures that the products added to the catalog, along with their price and stock, are sent to Trendyol. 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_order_items
Allows pulling orders with the “Shipped” or “Delivered” status on Trendyol, going back 24 hours from the flow's execution time, and updates them item-wise in Omnitron.
It runs every morning at 06:00.
send_approve_refund_orders
Ensures the approval of the created return request on Trendyol.
It runs every 5 minutes.
send_updated_product_price
Ensures that the updated product prices are sent to Trendyol.
It runs every 5 minutes.
send_updated_product_stock
Ensures that the updated product stocks are sent to Trendyol. Before activating this flag, the Buffer Stock setting in the second section above (Sales Channel Definition) must be properly configured.
It runs every minute.
reject_refund
When this flag is activated, rejection of return requests listed on the Marketplace panel can be performed. With the activation of the flag, return requests can be rejected by adding a reason, description, and image through the panel.
It is done through the Marketplace dashboard.
It is the ID defined on the Trendyol side that will be used when sending the cancellation information created in Omnitron (not coming from Trendyol) back to Trendyol. (A value must be entered from the reasonId column in the following link:)
Detailed documentation regarding the Mapper and the definitions to be made in the Mapper can be found in here.
Product triggering from the Dashboard is only for the create process. If a product update needs to be triggered, it must be done via CSV in the "Update Bulk Product Version Date" section under "Update by Uploading a File" in the channel settings (top right corner). For triggering processes, you can refer to this document: .
