How long does an Onedot product data onboarding take?
The supplier catalog is processed directly (straight through processing) and an ERP/PIM import file is generated. The intermediate results of the categorization, attribute mapping, normalization, etc. are displayed to the user via so-called feedback tasks, in which validation and overriding of the automated suggestions is possible.
The feedback is then implemented in a new processing and an updated ERP/PIM import file is created. In the case of a catalog update, the feedback effort is minimal, since the mapping profile is applied from the initial connection.
How does the Onedot platform know how to prepare product data?
At the beginning of the collaboration, the product data model (PDM) is mapped by the dealer in the Onedot platform and continuously kept up-to-date via a synchronization process with the ERP/PIM.
This means that Onedot knows the categories, attributes, value lists, etc. for creating the automated mapping proposals. The product data export (PDE), i.e. the extract from the merchant ERP/PIM, is used for the initial training of the Onedot platform. This provides the merchant with a merchant-specific machine learning model for automated onboarding.
What happens if the supplier changes the data format or catalog structure?
Onedot supports the automated import of common formats such as CSV, Excel, XML, TXT. For specific formats, the import may need to be configured once by an Onedot data specialist. There is no catalog structure requirement and the structure is allowed to change. Onedot automatically maps new categories, attributes, values to the merchant target model. When mapping for the first time, it is recommended that the user validates the automated suggestions. The more the supplier changes on his side, the more validation is recommended by Onedot.
On average, how long does it take a user to complete feedback tasks?
The time required depends on the size of the catalog, i.e. number of SKUs, attributes, categories, and can take from a few minutes to several hours. To keep the feedback effort for the user as low as possible, intermediate results are displayed aggregated. This means that when categorizing, for example, the user may not check each product, but at the product segment level. The attribute mapping is structured in such a way that attributes can be checked as "globally" mapped, but the software maps this on a category-specific basis.
How does a product data onboarding via the Onedot product data platform work?
The customer can define the relevant onboarding modules at the beginning of the collaboration. The onboarding process usually includes the following modules:
1. import product data
2. Product data synchronization with ERP PIM
3. Extraction (attributes are extracted from continuous text)
4. Categorization (products are assigned to dealer categories)
5. Attribute mapping (supplier attributes are assigned to dealer attributes)
6. Normalization (of numbers, units, value lists)
7. Creation of ERP/PIM import file