Overview
The VIP integration requires several pieces of information provided by VIP to be input as attributes in various locations through the system. Once configured, the system will run automatically daily but can also be push manually or the file the would be push can be downloaded for analysis.
Procedure
Preparation
- Create a customer to use when a transaction does not have a customer attached (Walk Up Customer for example). Keep the account number available for step 3.
- Set Global Entity Settings
- VIP FTP Info - Set server location & credentials for the FTP server
- ISV ID / SRS ID - Values provided by VIP for the reporting entity (Cloud Retailer Business) and software vendor respectively
- Summarize Non-retail Sales - Roll all non-Distributor sales into a generic customer (recommended)
- Fill in the Empty Customer Number Override with the account number of the customer you created in step 2
- Configure Distributors (Locations)
- Each active Location in Cloud Retailer that is to export data to VIP will need dome Distributor / Warehouse values associated with it that are provided by VIP. Required fields are indicated in the Attribute section of the Location.
- Configure Suppliers
- Each active Supplier in Cloud Retailer should have a 3 character code associated with it provided by the VIP.
- Configure Wholesales (Customers)
- Each active Customer in Cloud Retailer has attributes to indicate whether the customer is a Wholesale / Distributor and provides additional reporting / categorization data for the retailer. Required fields are indicated in the Attributes section of the Customer.
- Configure Products
- Each active Product has some optional attributes for categorization and reporting overrides. Required fields are indicated in the Attributes section of the Product.
- Products for VIP are keyed off of the primary product code. Customers are going to need to create an alternate code using the UPC of the product and make the primary product code in Cloud Retailer the one from VIP