File naming Convention

(xxxxx in the file names stands for your distributor ID number - How to find my distributor ID number)

Some file names have the example timestamp in the format of hhmmss (for example: 114327)

Example file

Load Accounts (Customers). 

The header fields in the file must match the field's mapped name. If a header field is not recognized as a field mapped name, the file will fail to load.  For important header field information see: Mapping Fields in data files loaded by FTP or Integration

The API_Account_ file does not support the Account-Users association, which is the assignment of sales reps or other users to Accounts/customers.

To load the Accounts-Users associations, you must use a separate file API_Accounts-Users_ explained below.

For details on the Accounts fields see  Explanation of Account fields

API_Account_Distributor_xxxxx.csv

API_Account_OVERWRITE_Distributor_xxxxx.csv

API_Account_ sample file

Data imported to Pepperi from any type of system, BI, ERP, CRM, etc.

used in the Accounts Dashboard Customization using Widgets

 E-SD-Distributor_xxxxxxx.xml

API_Accounts-Users_Distributor_xxxx.csv

API_Accounts-Users_OVERWRITE-Distributor_xxxx.csv

API_Accounts-Users_SelectiveOverwrite-Distributor_xxxx.csv

Accounts Users Example

This file assigns catalogs to accounts. If you are using Multiple Catalogs, you need to assign them to specific Accounts. Create multiple catalogs to assign to your Accounts. For instructions see: Setup Multi Catalogs. For the details on this file see: How to assign Catalogs to Accounts in bulk

The header fields in the file must match the field's mapped name. If a header field is not recognized as a field mapped name, the file will fail to load.  For important header field information see: Mapping Fields in data files loaded by FTP or Integration

API_Accounts-Catalogs_yyyy-mm-dd_hhmmss_Distributor_xxxx.csv 

API_Accounts-Catalogs_OVERWRITE_yyyy-mm-dd_hhmmss_Distributor_xxxx.csv 

API_Accounts-Catalogs_SelectiveOverwrite_yyyy-mm-dd_hhmmss_Distributor_xxxx.csv 

Accounts catalogs sample file

Loads accounts by type. Account types are used to indicate inventory source and destinations. For details on using Account types see: Account Types

The Account type name is indicated in the file name. For example: Vans, WarehouseA, WarehouseB, etc.

If no Account type is indicated in the file name and the default is used API_Account_Distributor_xxxxx.csv then the default type will be assigned - Customers

The same fields in the file are required as in API_Account_Distributor_xxxxx.csv (above)

API_Account_Distributor_xxxxx.csv

API_Account_<type_name>_Distributor_xxxxx.csv

Use this file to load contacts to your Accounts

How to Upload Contacts to Accounts (Sample file included)

API_ContactPerson_Distributor_xxxxx.csv

Contacts Example

API_PriceLevel_yyyy-mm-dd_hhmmss_Distributor_xxxx.csv

API_PriceLevel_Overwrite_yyyy-mm-dd_hhmmss_Distributor_xxxx.csv

Price List Info Example

Upload Price Levels pricing for your items, or upload a file that will overwrite your entire Price Level for items, or upload a file that will selectively update prices for items in your Price Level (without changing the rest of the items). 

The action will be taken depending on the way you name the file.

For more information see: Price List Items

API_PriceLevelItem_yyyy-mm-dd_hhmmss_Distributor_xxxx.csv

API_PriceLevelItem_Overwrite2011-03-24_hhmmss_Distributor_xxxx.csv

API_PriceLevelItem_SelectiveOverwrite_2011-03-24_hhmmss_Distributor_xxxx.csv

 API_SpecialPriceLevel_yyyy-mm-dd_hhmmss_Distributor_xxxx.csv

 API_SpecialPriceLevel_Overwrite_yyyy-mm-dd_hhmmss_Distributor_xxxx.csv

API_PriceLevelItem file is used to load the item prices for the SPL. 

Automatic ERP Integration Account Payment data

For more info see How to Upload Payments

E-P-2011-03-24_114327_Distributor_xxxxx.csv

(or E-P-Distributor_635667.csv)

Transaction Related Files

Upload Transactions - transactions in your system you want to upload to Pepperi. See How to Upload Transactions/Order History for details on file formats and naming.

Requires 2 files to be loaded - Transaction Header which includes the order header information and totals and Transaction Line  - which contains the line-item information for the items in the orders.

The header fields in the file must match the field's mapped name. If a header field is not recognized as a field mapped name, the file will fail to load.  For important header field information see: Mapping Fields in data files loaded by FTP or Integration

API_Transaction_<your transaction Name>_yyyy-mm-dd_hhmmss_Distributor_xxxxx​.csv

API_Transaction_<your transaction name>_Overwrite_yyyy-mm-dd_hhmmss_Distributor_xxxx.csv

API_TransactionLine_<your transaction name>_yyyy-mm-dd_hhmmss_Distributor_xxxxx.csv

API_TransactionLine_<your transaction name>_Overwrite_yyyy-mm-dd_hhmmss_Distributor_xxxxx.csv 

Order Header Sample File

Order Lines Sample File

Activity Related Files

Load Activities such as Visits, Surveys or any other custom Activity forms you have created.

The header fields in the file must match the field's mapped name. If a header field is not recognized as a field mapped name, the file will fail to load.  For important header field information see: Mapping Fields in data files loaded by FTP or Integration

API_Activity_<your_activity_name>_yyyy-mm-dd_hhmmss_Distributor_xxxxx​.csv

API_Activity_<your_activity_name>_OVERWRITE_Distributor_xxxxx​.csv

You can schedule activities for your sales reps in bulk via upload of a CSV file.

You can use the CSV file to load recurring activities - i.e. Every monday at 9:30AM, or Every 1st and 15th of the month. You can load in bulk and then the Pepperi Admin and sales reps will see everything on their Pepperi calendars.

For details on how to create and load this file: Upload Activity Planning

Items and Inventory

Load the Item data. Note that the inventory (stock count quantity) is loaded in a separate file (sample below). Prices such as Retail Price (API name: Price) and Wholesales Price (API name: SecondaryPrice) are loaded in this file. However, Price Levels are loaded in separate files listed in this article.

The header fields in the file must match the Mapped Name of the Item fields. If a header field is not recognized as an Items field mapped name, the file will fail.

For important header field information see: Mapping Fields in data files loaded by FTP or Integration

API_Item_yyyy-mm-dd_hhmmss_Distributor_xxxxx.csv

API_Item_Overwrite_yyyy-mm-dd_hhmmss_Distributor_xxxxx.csv

API_Inventory_yyyy-mm-dd_hhmmss_Distributor_xxxx.csv

API_Inventory_Overwrite_yyyy-mm-dd_hhmmss_Distributor_xxxx.csv

API_AccountItemStock_yyyy-mm-dd_hhmmss_Distributor_xxxx.csv

API_AccountItemStock__Overwrite_yyyy-mm-mm_hhmmss_Distributor_xxxx.csv

API_AccountItemStock__SelectiveOverwrite_yyyy-mm-dd_hhmmss_Distributor_xxxx.csv

llow you to load your own data into Pepperi for use in the Pepperi Rule Engine for calculations and validations.

Data in User Defined Tables is used in order to assign values to Custom Fields created in Pepperi.

For details: User Defined Tables

API_MapData

API_MapData_Overwrite

API_MapData_SelectiveOverwrite