Fashfed 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 with your username and password at the link.
From the menu, go to the App Store, select the "Fashfed" project for sales, and then select the relevant project to complete the installation.
After the installation process, go to "My Applications" from the left menu, select the relevant application, and enter the application page. After completing the necessary build and deployment processes, the Fashfed Marketplace Dashboard application will be available in the left menu of Omnitron.
It will appear as shown in the menu screen visual once the installation is complete.
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
Fashfed
Automatically created.
Required (should not be changed)
Catalog Name
Catalog Name Created for Fashfed
*May vary from brand to brand
Fashfed_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 activate any processes until it is enabled.
Inactive
Default is set to inactive (it needs to be enabled).
Required
Schema Type
The place where the information to be stored in the sales channel settings is defined. The information here will be used to bring the necessary details for the sales channel to work as a form in Omnitron. A schema containing the minimum required information for the sales channel to function is automatically created. You can add additional information here if needed (for example, information required for ERP integration of the sales channel). The key-value information that will be included in the Channel Config is listed here. In the dictionary in the value section, the following are included: key, label, required, and data_type.
key -> Information on which key will be used to access the information in the channel config
label -> Information on how the data will appear in the form on the Omnitron sales channel settings interface
required -> Whether the value is mandatory or not (true/false)
data_type -> The data type of the value (list, text, integer, bool, json)
{
"base_url": {
"key": "base_url",
"label": "Base Url",
"required": true,
"data_type": "text"
},
"access_token": {
"key": "access_token",
"label": "Access Token",
"required": true,
"data_type": "text"
},
"buffer_stock": {
"key": "buffer_stock",
"label": "Buffer Stock",
"required": false,
"data_type": "integer"
},
"category_ids": {
"key": "category_ids",
"label": "Category Ids",
"required": true,
"data_type": "list"
},
}
The default information has been automatically entered.
Required (Additions can be made, but existing fields should not be changed)
Base URL
API URL for Fashfed
https://5b6ccec26d28496598e9e44dae46e529.lb.akinoncloud.com
Required
Access Token
default
The default has been filled with default (This information is retrieved from Fashfed).
Required
Category Ids
The main category IDs on the Fashfed side are checked and added here.
[
{
"id": "99ae4410-7631-452c-bfb0-b7d636ea95eb",
"name": "Kadın",
},
{
"id": "be6e5517-926f-40ad-9476-5c378adaf937",
"name": "Erkek"
},
{
"id": "db3292d0-8b35-49cb-a612-b9241fc32c48",
"name": "Çocuk"
},
{
"id": "3cd2be5c-6274-4a7d-938d-8d404ac00c8a",
"name": "Ev & Yaşam"
}
]
f8aeb10e-f0f9-4f17-9687-60e542bdaefc
ffcc74a6-6b46-4820-91fd-d30501037aa0
The default is left empty. (The category IDs to be used, as provided in the table, are entered in this field)
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 run, it must be added here as false. (Detailed information about feature flags can be found in Section 9 under the Feature Flags heading below.)
{
"get_orders": false,
"get_cancel_orders": false,
"get_refund_orders": false,
"send_update_orders": false,
"get_updated_orders": false,
"delete_product": false,
"product": false,
"price": false,
"stock": false,
"send_refund_order_status": false,
"split_packages": false
}
The default for all flags has been set to false.
Required
Cargo Company Mapping
When an order is retrieved, it ensures that the order is written to Omnitron with a default shipping company, and if the shipping process is not managed by the brand (if send_shipping_info is not active), the shipping company will be set according to the mapping of the shipping information slug received from Fashfed.
{ "default": "3",
“yurtici”: “2”
}
The default has been filled with the default key.
Required
Use Cargo Label
If the shipping process is not managed by the brand (if send_shipping_info is not active), and if a shipping label is to be created when retrieving the relevant order from Fashfed, this setting should be enabled.
Note: The shipping label is in a fixed PDF format.
Inactive
The default is left empty.
Optional
Use Neighborhood
Whether the neighborhood information in the address data will be used when creating an order is determined by this setting. If active, the neighborhood information in the shipping and billing addresses of the order will be processed when creating the order's address in Omnitron. If inactive, the neighborhood information will not be used when pulling the relevant order into Omnitron.
Inactive
The default is left inactive. If the neighborhood information is mandatory in the company’s ERP, this field should be enabled so that the neighborhood information can be used from Omnitron.
Optional
Order Number Format
When pulling order data from Fashfed to Omnitron, the order number is set according to this format. If this value is left empty, by default, the order number will be written to Omnitron in the format "{orderNumber}-{id}". Here, "orderNumber" corresponds to the "order_number" field on the Fashfed side, and "id" corresponds to the "number" field.
FD-{orderNumber}-{id}
The default is left empty.
Optional
Default Reason ID
If the reason ID in the refund data pulled from Fashfed is not listed in the Refund Reason Mapping, the refund data will be pulled and written to Omnitron using the Omnitron refund reason ID entered in this section. (The ID information can be retrieved using the endpoint: {omnitron_url}/api/v1/channel/{channel_id}/cancellation_reasons/?cancellation_type=refund&is_active=true)
5
The default is left empty.
Required
Refund Reason Mapping
{
“f3909f53-a535-40cc-8d50-de0cd047aedd”:”7” ,
“f488f79f-503f-4787-a8ef-6a37b085b5e1”:”5”
}
The default is left empty. (When left empty, the refund reasons will be written with the "Default Reason Id" from the previous step when the refund information is pulled from Fashfed.)
Optional
Refund Start Date
The start date for when refunds will begin to be retrieved. The format is "yyyy-MM-ddTHH:mm:ssZ".
2023-07-01T00:00:00Z
The default is left empty.
Optional
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 Setting 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
}
}
The default has been filled.
Required
Send Shipping Info
The setting that determines whether the shipping process will be managed by Fashfed or the brand.
Inactive
The default is left inactive. (If inactive or not selected, Fashfed will manage the shipping process. If active, the brand will manage the shipping process.)
Optional
Cancellation Reason ID
The information on which reason ID will be used when pulling canceled orders from Fashfed to Omnitron. (The ID information 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 empty.
Required
Cancel Reason Mapping
{
“f3909f53-a535-40cc-8d50-de0cd047aedd”:”1” ,
“f488f79f-503f-4787-a8ef-6a37b085b5e1”:”3”
}
The default is left empty. (When left empty, the cancellation reasons will be written with the "Cancellation Reason Id" from the previous step when the cancellation information is pulled from Fashfed.)
Optional
Reject Item Reason
The reject (refund rejection reason) information used during the approval/rejection process of the refund data pulled with the refund order flow in the order.
Damaged
The default is left empty.
Optional
Attribute Set Strategy
The strategy setting that determines which feature set the products belong to.
CategoryNode
The default has been filled.
Required (Should not be changed)
Use Channel ID In Address Mapping
If the brand wishes, they can enable this field to perform address mapping on a channel basis. If this field is activated, the channel ID information will be added before the address data in the mapping process, and searches will be performed using the sales channel filter with the channelId_address information.
Inactive
The default is left empty.
Optional
Buffer Stock
It is the value to be subtracted from the product's current stock when sending stock feed to Fashfed. If no value is entered, the product's current stock will be sent to Fashfed.
3
The default is left empty.
Optional
Waybill Option
When updating orders on the Fashfed side, if the status of the related order is "Shipped" or "Delivered" and the enabled field in this setting is true, the waybill_number field will be updated with the order's invoice number if it is filled. If the invoice number is not available, it will be updated with the value entered in the default field.
{
"enabled": true, "default": "999"
}
{
"enabled": false, "default": ""
}
Optional
Send Cancel Reason ID
This is the ID in Omnitron that will be used when sending a cancellation—created in Omnitron and not originating from Fashfed—to Fashfed.
(The ID can be obtained via: {omnitron_url}/api/v1/channel/{channel_id}/cancellation_reasons/?cancellation_type=cancel&is_active=true)
Note: This ID must be different from the Cancellation Reason Id and the IDs listed under Cancel Reason Mapping, because cancellation requests coming from Fashfed are distinguished based on the reason.
10
The default value is left blank.
Optional
Records with errors during the integration process are held for a certain period with a penalty. The values for RETRY_INTERVAL and EXPIRATION_DATE are in seconds.
RETRY_INTERVAL: This field indicates how long to wait before retrying in case of an error, in seconds.
EXPIRATION_DATE: This field specifies how long failed integrations will remain before expiring, in seconds.
MAX_RETRY_COUNT: This field indicates how many more times to retry after an error. The retry will not happen for a period longer than the RETRY_INTERVAL.
sent_to_remote: In bulk requests, this field specifies the maximum time (in seconds) to wait for a response from the marketplace. For example, a value like { "EXPIRATION_HOUR": 360 } can be entered.
Any updates made to these values will be effective in the subsequent processes. For example, if a SKU is placed in the penalty queue with a retry interval of 3 hours for stock updates, and the retry interval is later updated to 2 hours, the next time the stock update for that product is retried and an error occurs, the penalty queue will reflect the new retry interval of 2 hours, instead of the previous 3-hour penalty.
In cases where there is an error in requests made from Omnitron to Fashfed, we use the failed integration settings to place the data in a penalty state for a certain period. For example, if there is a missing attribute value during product submission, we can enter these settings to ensure the error is corrected within a specified period.
The category tree is drawn according to the added Category IDs within the sales channel.
After the category tree is pulled into Omnitron, it can be viewed from the Category Management section when the relevant Sales Channel is selected as the corresponding Fashfed.
Once this process is successfully completed (it can be tracked through the logs), the flow that retrieves the attributes will run. Once the operations related to the attributes are completed (if the Default Attributes flow has run and finished successfully), the next steps should be carried out.
Users need to perform category mappings through the Mapper after the category tree is pulled.
The Akinon Mapper function within Omnitron allows users to configure and manage the attribute values of the products they want to sell on the marketplace sales channels according to the marketplace. Additionally, it provides the opportunity to check whether the attributes and their values are correct before the products are listed for sale.
The products need to be added to the relevant category tree on the Fashfed side. Each product should be added to only one category. Otherwise, an error will occur during the submission process.
When the Fashfed marketplace application is installed on the relevant brand's Omnitron, it appears as "Fashfed" in the left-side menu.
The dashboard data related to the Fashfed marketplace application is displayed on this screen.
TOTAL SKU IN CATALOG The number of SKUs in the relevant catalog that are of type "simple" and have an active status.
NUMBER OF SKUs ON SALE The number of SKUs that have been sent to the marketplace and are currently on sale.
TOTAL SKU DIFFERENCE The number of SKUs that are in the catalog but not on sale in the marketplace. In this section, a comparison is made between saleable products in Omnitron and the products listed for sale in the marketplace. In other words, products in Omnitron that have a price, stock greater than zero, a category, an image, and are in the catalog are taken as a basis.
NUMBER OF SKUs WITH PRICE DIFFERENCES THAT WERE CORRECTED The number of SKUs with price differences between Omnitron and the marketplace. If any differences are found, a task is executed to resolve the discrepancies, and they are corrected.
TOTAL STOCK IN CATALOG The total stock quantity of all products in the marketplace catalog.
TOTAL STOCK QUANTITY The total stock quantity of products currently on sale in the marketplace.
TOTAL STOCK DIFFERENCE The stock quantity of products that are in the catalog but not on sale in the marketplace.
NUMBER OF SKUs WITH STOCK DIFFERENCES The number of SKUs with stock discrepancies between Omnitron and the marketplace. If any differences are found, a task is executed to resolve the discrepancies, and they are corrected.
This is the screen where logs and reports are displayed.
The logs of the flows are displayed on this screen.
The reporting screen shows products added to the catalog in Omnitron but not listed for sale on Fashfed due to discrepancies between price and stock information in Fashfed and the data in Omnitron.
Creating Alarms and Notifications The Marketplace Dashboard is an advanced automation platform designed to simplify e-commerce integrations. Alarms and notifications play a vital role in informing users about critical events such as integration errors, data delays, or successful completions. With real-time alerts, users can quickly detect and resolve integration-related issues, ensuring seamless operation of e-commerce systems. This ultimately contributes to delivering the best shopping experience to end customers.
Real-Time Issue Detection: Alarms instantly identify integration errors, ensuring accurate data flow between systems.
Proactive Problem Solving: Alarms enable timely intervention in case of integration issues, minimizing downtime and operational impact.
Enhanced Data Integrity: Alarms help prevent data delays or disruptions, supporting consistent and accurate data processing.
Optimized Customer Experience: Fast resolution of integration problems ensures that order, stock, and product data stay up-to-date, providing a smooth shopping experience for customers.
Improved Operational Efficiency: With alarms, users are immediately informed about critical events, allowing them to focus on strategic tasks.
Data-Driven Decision Making: Alarms provide valuable insights that help optimize integration processes.
Reduced Downtime: Early detection of issues minimizes system downtime and prevents revenue loss.
Customizable Alerts: Akinon Marketplace Dashboard offers flexible alarm customization to meet business needs.
Seamless Cross-Platform Communication: Alarms help facilitate communication and synchronization across different e-commerce systems.
By leveraging the power of alarms in the Akinon Marketplace Dashboard, users can effectively monitor and manage e-commerce integrations, ensuring a reliable, efficient, and customer-centric shopping experience.
Step 1: Access Alarm and Notification Settings
Marketplace Dashboard is not a standalone product with a separate URL. To access it, go to the left menu in Omnitron, click on Sales Channels, then select Marketplace Operations from the dropdown menu.
Click the + New Alarm button located at the top right of the Alarms screen.
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 alerts. (There is no limit to the number of email addresses you can enter.)
Step 3: Saving the Alarm and Notification Rule
Once the alarm rule is successfully configured, click the Save" button to save the alarm.
Thanks to the power of alarms and notifications in the Akinon Marketplace Dashboard, e-commerce integrations become more efficient. With real-time monitoring, issues can be addressed immediately, ensuring data accuracy and delivering a seamless customer experience. Customizable alerts allow teams to stay informed and make data-driven decisions.
Error Rate: If the number of errors within the defined time interval exceeds the specified threshold, the alarm is triggered.
Average Flow Time: If the average processing time of a flow exceeds the defined duration within the given time interval, the alarm is triggered.
The screen used for triggering flows.
Errors that may be encountered in logs and their corresponding solutions are as follows:
"Stock data not found" → This error indicates that the product has no stock data. Stock data must be added for the relevant product.
"Price data not found" → This error indicates that the product has no price data. Price data must be added for the relevant product.
"... attribute is required" → This error indicates that there is missing mapping for the specified attribute. Mapping should be performed as described in Section 5 (Marketplace Mapping).
"Unreported order of ERP can not be canceled" → This error means that the related order has not yet been transmitted to ERP. To proceed with the cancellation process, 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 Township mapping in the order's address data needs to be completed.
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.
If too many faulty products accumulate in the queue, since processing is done in batches of 50, the queue may not reach the subsequent products. There are two solutions for this:
The first solution is to immediately fix errors related to mapping, catalog, stock, price, etc., and then trigger the CSV upload.
The second solution is to adjust the Fail Integration settings in the channel settings with proper time intervals.
For the "Failed to suggest product to catalog" error, if the issue is related to attribute values, the Category Attributes flow should be run to pull the current attribute values, and 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 is not "sku". 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 occurs when the specified SKU does not exist in Omnitron.
"The relevant record is processing in another queue, LocalBatchId: {local_batch_id}" This error occurs when a product that is still being processed is triggered again. Product logs should be checked to ensure that the flow in "Waiting" status is completed.
The default frequency values are as shown in the table below. These values can be modified by the Marketplace team.
Flag
Description
Frequency
get_orders
Retrieves orders with the "Preparing" status from Fashfed to Omnitron, going back 12 hours from the flow's execution time.
Before activating this flag, the settings in Section 2 (Sales Channel Definition)—Use Neighborhood, Use Channel Id In Address Mapping, Use Cargo Label, Cargo Company Mapping, Send Shipping Info, and Order Number Format—must be properly configured.
Runs every 5 minutes.
get_cancel_orders
Retrieves claims with the "Cancel Completed" status from Fashfed, going back 12 hours from the flow's execution time, and ensures that the cancellation process is performed in Omnitron with a maximum of 6 cancellation plans.
Before activating this flag, the settings in Section 2 (Sales Channel Definition)—Cancellation Reason Id and Cancel Reason Mapping—must be properly configured.
Runs every 5 minutes.
get_refund_orders
Retrieves refund claims with the "Open" or "Waiting" status from Fashfed, processes the claim lines, and creates a return request in Omnitron.
Before activating this flag, the settings in Section 2 (Sales Channel Definition)—Default Reason Id, Refund Reason Mapping, and Refund Start Date—must be properly configured.
Runs every 5 minutes.
send_update_orders
This flow ensures that the order status ("Preparing", "Shipped", "Delivered"), invoice information (invoice_number, invoice_date, e_archive_url), and tracking information (tracking_number, tracking_url, shipped_date) are sent to Fashfed.
Before activating this flag, the Send Shipping Info and Waybill Option settings under the second heading (Sales Channel Definition) should be properly configured.
With this flow, the invoice and order status will be updated. The tracking number will only be sent if Send Shipping Info is enabled.
.
Runs every 5 minutes.
send_split_packages
The necessary details can be found in the document at the link below: Split Package Flow
Operates via outbound triggering sent by OMS.
product
Ensures that products added or updated in the catalog are sent to Fashfed along with their price and stock.
Before activating this flag, the Buffer Stock setting in Section 2 (Sales Channel Definition) must be properly configured.
Runs every 5 minutes.
delete_product
Ensures that products removed from the catalog have their stock set to 0 on Fashfed.
Runs every 5 minutes.
price
Sends updated product prices to Fashfed.
Runs every 5 minutes.
stock
Sends updated product stock levels to Fashfed.
Before activating this flag, the Buffer Stock setting in Section 2 (Sales Channel Definition) must be properly configured.
Runs every minute.
get_updated_orders
When Fashfed manages the shipping process, retrieves orders that have moved to the "Shipped" or "Delivered" status in Fashfed, going back 24 hours from the flow's execution time. Updates the status and tracking_number (for "Shipped" status) in Omnitron on an item basis.
Before activating this flag, the Send Shipping Info setting in Section 2 (Sales Channel Definition) must be properly configured.
Runs every morning at 06:00.
send_refund_order_status
Approves or rejects the created return request on Fashfed.
Runs every 5 minutes.
send_cancel_order_items
This ensures that the cancellation information created in Omnitron for an order is sent to the Fashfed side. Before activating this flag, the settings under the second heading above (Sales Channel Configuration) — Send Cancel Reason Id, Cancellation Reason Id, and Cancel Reason Mapping — must be properly configured.
Important Note: It is crucial to distinguish between the cancellation reasons used in the Order Cancel flow and those to be used in this flow. In other words, when performing a cancellation here, the cancellation reason corresponding to the Cancellation Reason Id and Cancel Reason Mapping defined in the channel configuration must not be selected. If such a reason is selected, the cancellation will not be sent to the Fashfed side.
It runs every 5 minutes.
The default has been filled as.
It is the fixed token information to be used in requests sent to Fashfed. (You can check how to access the token information from the link:)
For the refund process, the refund reason information from Fashfed is matched with the refund reason information in Omnitron. Here, the key is the ID from Fashfed (the ID of those with a refund type on the URL), and the value is the reason ID in Omnitron. (The ID information can be retrieved using the endpoint: {omnitron_url}/api/v1/channel/{channel_id}/cancellation_reasons/?cancellation_type=refund&is_active=true)
For the cancellation process, the cancellation reason information from Fashfed is matched with the cancellation reason information in Omnitron. Here, the key is the ID from Fashfed (the ID of those with a cancel type on the URL), and the value is the reason ID in Omnitron. (The ID information can be retrieved using the endpoint: {omniton_url}/api/v1/channel/{channel_id}/cancellation_reasons/?cancellation_type=cancel&is_active=true)
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:
