Trendyol Marketplace Setup Configurations

1. Deployment of the Marketplace Dashboard Application on ACC

The deployment of the Marketplace Dashboard application on ACC is necessary. To log in to your ACC account, access https://console.akinoncloud.com 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.

2. Defining Sales Channels

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.

3. Failed Integration Setting

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.

4. Creation of Category Tree and Development of Attributes for Sales Channel

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.

5. Marketplace Mapping Implementation

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.

Detailed documentation regarding the Mapper and the definitions to be made in the Mapper can be found in Mapper tutorial.

6. Adding Products to the Category Tree

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.

7. Defining Screens

When the Trendyol marketplace application is installed on the relevant brand's Omnitron, it will appear as Trendyol in the left menu.

7.1. Dashboard Screen

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.

7.2. Monitoring Screen

The screen where logs and reports are located.

7.2.1. Log Screen

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.

7.2.2. Reports Screen

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.

7.3. Alarm Screen

Creating Alarms and Notifications

The Marketplace Dashboard is an advanced automation platform designed to streamline e-commerce integrations. Alarms and notifications play a critical role in informing users about integration errors, data delays, and successful completions. Thanks to real-time alerts, users can quickly identify and resolve issues related to integrations, ensuring seamless e-commerce operations. This ultimately contributes to delivering the best shopping experience to end customers.

Benefits of Alarms and Notifications

• Real-Time Issue Detection: Alarms immediately detect integration errors and ensure accurate data flow between systems.

• Proactive Issue Resolution: Alarms allow timely intervention in integration-related issues, minimizing downtime and operational impact.

• Enhanced Data Integrity: By preventing data delays or interruptions, alarms support consistent and accurate data processing workflows.

• Optimized Customer Experience: Fast resolution of integration issues ensures that order, stock, and product data remain up to date, delivering a seamless shopping experience to customers.

• Improved Operational Efficiency: With alarms, users are informed about critical events and can focus on strategic tasks.

• Data-Driven Decision Making: Alarms provide valuable insights to help optimize integration processes.

• Reduced Downtime: Early detection of problems minimizes system outages and prevents revenue loss.

• Customizable Alerts: The Akinon Marketplace Dashboard offers flexible alarm customization options to suit business needs.

• Seamless Cross-Platform Communication: Alarms facilitate communication and synchronization between different e-commerce systems.

With alarms on the Akinon Marketplace Dashboard, users can monitor and manage their e-commerce integrations effectively, ensuring a reliable, efficient, and customer-centric shopping experience.

Steps to Create an Alarm and Notification

Step 1: Access Alarm and Notification Settings The Marketplace Dashboard is not a standalone product with a separate URL. To access it, go to the left-side menu in Omnitron, click on Sales Channels, then select Marketplace, and finally click on Marketplace Operations from the dropdown menu.

Step 2: Create a New Alarm and Notification Rule On the Alarms screen, click the + New Alarm button located at the top right corner.

On the settings page that opens, select a Flow Name from the dropdown list.

Configure the alarm conditions based on specific criteria such as error rate, flow duration, time interval, and metric value.

Select a notification channel and add the email addresses of the individuals or teams who should receive the notifications. (There is no limit to the number of email addresses that can be added.)

Step 3: Saving the Alarm and Notification Rule

Once the alarm rule is successfully configured, click the “Save” button to finalize and activate the alarm.

Thanks to the power of alarms and notifications in the Akinon Marketplace Dashboard, e-commerce integrations become significantly more efficient. Real-time monitoring allows immediate intervention in case of issues, ensuring data accuracy and delivering a seamless customer experience. Customizable alerts enable teams to stay informed and make data-driven decisions effectively.

Error Rate: The alarm is triggered if the number of errors within the defined time range exceeds the specified threshold.

Average Flow Time: The alarm is triggered if the average processing time of the flow exceeds the defined duration within the selected time range.

7.4. Reject Refund Screen

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.

8.Steps to Follow for Errors

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.

• 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: Flow Trigger Document.

• 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.

• Errors Received After CSV Upload:

  • sku cannot identify please check your csv file. Header value should be set this: sku This error occurs when the first row of the CSV file does not contain “sku” as the header. The CSV file must be created according to the template provided on the trigger screen.

  • The relevant SKU not exists in omnitron. Request URL: {url} This error is triggered when the specified SKU does not exist in Omnitron.

  • The relevant record is processing in another queue, LocalBatchId: {local_batch_id} This error appears if the product, which is already in the middle of a processing flow, is triggered again. You should check the product logs and wait for the flow with “Waiting” status to complete. Once completed, the log can be filtered by SKU to view the final status.

  • The relevant record is not in queue. the item may have been penalized or check product is saleable This error is returned if the product status is inactive or if it is not included in the catalog.

• 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.

• During the Product Deletion process, the following errors may be received from Trendyol:

  • "Price and stock cannot be updated for deactivated products"

  • "Price or stock updates cannot be made for archived products"

  These errors will be processed as successful in our system; however, stock reset operations will not be applied to the related products. Therefore, it is important to pay attention to the following points:

  • If you have archived or deactivated products via the Trendyol panel, stock updates for these products will not be possible. This may lead to the risk of overselling in the future.

  • To prevent this risk, it is recommended to remove the products from the catalog via Omnitron instead of archiving or deactivating them through the Trendyol panel.

  • If the product cannot be removed from the catalog in Omnitron (e.g., because another sales channel is using the same catalog), and you still need to archive or deactivate it, then when unarchiving or reactivating the product in the Trendyol panel, make sure the product is present in the Omnitron catalog.

  Akinon is not responsible for any sales or stock issues that may arise during this process. It is important to act accordingly to ensure the process runs smoothly.

9. Feature Flags

The frequency value is set by default as shown in the table below. These values can be changed by the Marketplace team.

10. Initial Trendyol Integration Setup Flow