Skip to main content


In the marketplace usage scenarios of Akinon customers, the integration between Omnitron and marketplaces will be brought to a traceable structure (with apache nifi infrastructure), this tracking structure will be provided directly to the customer with logs, reporting and data incompatibilities.


The MP Dashboard application is an application that can be accessed via Omnitron. If Omnitron users are running the MP Dashboard application of the project under their authority, users will see the application directly in the Omnitron's left menu.


MP Dashboard application provides Omnitron based user authorization solution. An Omnitron user can easily access the MP Dashboard application without the need for additional authorization.

Note: If the authorized project uses the MP Dashboard application, visible in the left menu.


With the Akinon MP Dashboard application, users can monitor the data of sales channels more effectively and users are instantly informed in cases of data conflicts between platforms. There is a Dashboard screen to present this data to the users as a summary. This screen presents the data on both sides and the differences between them.

Total Number of SKUs in MP Sales Catalog: Number of products with "Active" status in the catalog of the relevant sales channel in Omnitron.

MP Total Number of SKUs for Sale: The number of products active and on sale in the Marketplace.

Number of SKU Differences: It is the difference between the number of SKUs are active in the catalog of the relevant sales channel in Omnitron and the number of products that are active and on sale in the marketplace.

Total Stock Quantity in MP Sales Catalog: The stock amount of SKUs that meet all the necessary conditions (Price, Stock, Official) to be available for sale on Omnitron.

MP Total Stock in Sale: It is the total amount of stock that is active and on sale on the Marketplace side.

Total Stock Difference: It is the difference between the stock amount of the SKU that meets all the necessary conditions (Price, Stock, Official presence) and the stock amount active and on sale in the Marketplace.

Number of SKUs with Price Difference: It is the number of SKUs with a price difference between the SKUs with "Active" status in the catalog of the relevant sales channel and the SKUs that are active and on sale in the Marketplace.

Number of SKUs with Stock Difference: It is the number of SKUs with a stock difference between the SKUs with the status "Active" in the catalog of the relevant sales channel and the SKUs that are active and on sale in the Marketplace.


This menu includes Logs and Reports of the project created on the MP Dashboard and functions that facilitate the monitoring of integration flows within the project. These functions are:

  • Logs
  • Reports


It facilitates instant tracking of all integration flows by providing detailed log tracking of all integration flows in the project and downloading log files.

The Logs page shows the log information of each execution of the relevant flow by listing them in rows.

In addition to the status of each execution of an integration flow (success, waiting, failed), this page displays detailed information such as the status of all end-to-end activities concerning the related flow (success, waiting, failed), the operator triggering the execution (system, user), the flow’s execution time, and the success rate of the transactions in the flow.

Click on Execution ID to examine the transaction-based log details in an execution of the integration flow. The flows of the transaction will be listed in the pop-up. Here, the Log File of transaction logs with Failed status can be downloaded for detailed control. Also filtering options (SKU or Status) can be used to filter the data shown.

The sub-flows in each integration flow are displayed with the boxes under the Activity-Based Status heading. If the relevant sub-flow has been successfully completed, it will be displayed in Green; if it has failed, it will be displayed in Red. If the log data in the sub-flow is needed to examine in details, the log file can be downloaded by clicking on the file icon on the relevant sub-flow box.

Note: The log file download functionality is not displayed for sub-flow activities that do not contain logs.


The report screen is the screen where the data obtained from the logs are interpreted and presented to the end user with all the details. On this screen, detailed reports on the product, price and stock flow of the relevant project are presented.


This page list is sent to users via Alarm Notifications and is added to the Notification Settings page when case-specific Alarm Conditions occur while setting up the integration flow. It facilitates viewing detailed alarm notification content for the relevant Project and Integration Flow.

Select the Integration Flow you will access for alarm details to bring up a detailed alarm list below. When the limit value set for a certain time period is exceeded while establishing the integration flow, notifications are received with the selected notification method and alarms are listed on the Triggered Alarms page in the application.

In addition, there is a +New Alarm button in the upper right corner of the Alarm screen. Clicking this button will display the Alarm Settings page below. In this screen, alarms can be created by selecting the flow, alarm type and value.

Alarm Status: This is the field where the necessary conditions are defined to give a warning in case the performance of the integration flow exceeds the determined limits. There are two different performance metrics used to identify warning conditions in the application: “Error Rate” and “Avg. Flow Time.”

The alarm condition is the field where the conditions required for the warning of the MP Integration, the average response time, the number of incoming data remains lower than the specified limits or exits. More than one alarm can be installed for an integration flow.

Metric Type: A single selection must be allowed in Dropdown list. List contents are; “Error Rate”, “Avr. Response Time ”,” Number of Orders ”,” Number Of Cancellation Request ”

Error Rate: The alarm should work if an error is encountered on the ratio determined in requests to the MP side.

Avr. Response Time: The alarm must operate in case of no longer response to the request by MP.

Number of Orders: Alarm should operate if the order does not come to the order by MP over a certain time (ex. 2 hours).

Number of Cancellation Request: If more than Y is requested by the MP in time X, the alarm should go on.

Sales of Out of Stock Products: Although the product stock is zero for the sales channel, the alarm should work if the order is received by MP. Order number and SKU information should be included in the alarm. MP Dashboard Displaying MP Dashboard