How does the Retail3000 PriCat import work?

This document describes the operation of the Retail3000 Import when set to PriCat operation. Please note: This document does not cover the EDI PriCat Import, but only the Retail3000 import using PriCat translation tables.

Minimum requirements 

Retail3000 Import version 18.1 or higher

Retail3000 Offline Export version 18.1 or higher

RetailVista 18.1 or higher

Licenses

RetailVista basic, Exchange general, PriCat

The Retail3000 import normally works in 'Offline' situations with Retail3000 XML files from a headquarters that are retrieved via the RetailClient from an FTP server or central data folder. Since Retail3000 Import version 18.1 and higher, it is now possible to configure the use of PriCat translations. From that moment on, the linking of tables no longer takes place based on code, but on description, and the PriCat translation tables in RetailVista are used. Therefore, the Retail3000 XML export files have been expanded to include descriptions of master tables in addition to codes.

The whole idea behind the PriCat imports is that linking is done based on description instead of code. This greatly reduces the risk of data corruption because a matching description means that the data truly corresponds. However, a matching code does not guarantee anything; it is possible that the same code has been used for completely different data. By linking based on description, the system can also try to find the same description itself as much as possible. For example, a matching description can be found for the brand 'Hozelock'.

If this is not possible, then this PriCat connection is not complete and the processing of product data will not start. First, all connections must be valid, only then will the product data processing start.

In the above configuration screen, it is also visible that PriCat master tables can be ignored. This can be used to indicate that an import of master tables is not desired. The disadvantage of importing them can be that a large number of connections need to be made, even for data that is not desired at all. A practical example: Suppose a customer is only interested in products from a specific supplier. By importing the master tables first, there is a chance that hundreds of brands, product categories, classifications, etc. need to be linked before the product mutations can be read in. By indicating that the master tables should be ignored, the Retail3000 Import will start directly with the product data. This processing then takes place in two steps: Initially, a 'prescan' is done on all master data that appears in the product mutation file. This builds up the PriCat translations. If it turns out after checking that all PriCat connections are complete, the same file is processed again, but now 'definitely'.

When processing a product mutation file, suppliers are first created. In the above settings, it can be indicated that new suppliers are created as default PriCat connections to be ignored. For a supplier with an ignored PriCat connection, all product mutations will be completely ignored.

Once a supplier is linked in the PriCat translations (and not set to 'Ignore'), product mutations will be processed. Only the supplier setting 'Ignore Exchange product mutations' will be taken into account.

In addition to PriCat connections, there is also 'PriCat Classifications'.This is the translation of a PriCat product category to the classification 1-5. These links will also need to be updated in order to start processing the actual product mutation.