Upload data to Pepperi such as customers, items, contact persons for your Accounts, order history, XML files for use in Account Dashboard Widgets charts and graphs and more.
The files relate to specific features in Pepperi or components of your automated ERP Integration with Pepperi.
To understand the requirements for formatting of each file see the article specific to that feature and the links to sample files in the table below.
You can do a manual test if you would like to upload one of the files to check the format or data:
Settings -> ERP Integration -> File Upload and Logs
Click Upload
Using the menu to select the file type you would like to load:
Mapping Fields
When mapping field names from CSV files to Pepperi fields, you must use the mapped names indicated in the Pepperi back office. The header field names in the file must match the mapped name of the fields listed in the Pepperi Web Admin. If a header field is not recognized as an mapped name, the file will fail. Please read this article before you create your file headers: Mapping Fields in data files loaded by FTP or Integration
Overwrite and Selective Overwrite
Some file types support "Overwrite" and/or "Selective overwrite". For a full explanation with examples of these files types see: Uploading Overwrite and Selective overwrite data files
| Name | Component using this file |
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 |
| Accounts Related Files | |||
| Accounts |
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 your Pepperi users to Accounts. 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 |
|
| Accounts - custom |
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 |
|
| Accounts-Users | This file assigns sales rep users to accounts. Only the changes indicated in the file will be loaded. See detailed information here: Accounts Users File Upload |
API_Accounts-Users_Distributor_xxxx.csv API_Accounts-Users_OVERWRITE-Distributor_xxxx.csv API_Accounts-Users_SelectiveOverwrite-Distributor_xxxx.csv |
|
| Accounts - catalogs |
This file assigns Catalogs to Accounts. If you are using Multiple Catalogs, you need to assign them to specific Accounts. To create multiple catalogs: 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 |
|
| Account Types |
Associate Accounts with an Account Type. Account types are used to indicate inventory source and destinations in Transaction Types. For details on using Account Types see: Account Types To load different types in separate files, the Account <type_name> is indicated in the file name. For example: API_Account_Van, API_Account_WarehouseA, API_Account_WarehouseB To load all Account Types associations in one file use the default filename "API_Account_Distributor_xxxxx.csv" |
API_Account_Distributor_xxxxx.csv API_Account_<type_name>_Distributor_xxxxx.csv |
Accounts sample file |
| Contact Person |
Use this file to load contacts to your Accounts. Contacts may then be connected as buyers to the B2B Storefront. How to Upload Contacts to Accounts (Sample file included)
|
API_ContactPerson_Distributor_xxxxx.csv |
|
| Pricing Related Files | |||
| Price List Information | General information about your price lists: name, currency, ID, hidden/active. For details: Upload Price List Information |
API_PriceLevel_yyyy-mm-dd_hhmmss_Distributor_xxxx.csv API_PriceLevel_Overwrite_yyyy-mm-dd_hhmmss_Distributor_xxxx.csv |
|
| Price Level Items |
Detailed list of all prices per each Item for the price level. 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 |
Price Level Items Example |
| Special Price Level (SPL) | Temporarily overwrites the prices of a subset of items in a price level. For detailes: Special Price Level Feature (SPL) |
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. |
SPL Example |
| Payment |
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) |
Payments Sample |
|
Transaction Related Files |
|||
| Transactions / Sales Order History |
Upload Transactions - transactions (orders, returns, invoices, etc.) in your ERP 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 |
|
|
Activity Related Files |
|||
| Activity Types |
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 |
|
| Activity Planning |
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 |
N/A see link to article | |
|
Items and Inventory |
|||
| Items |
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 above. 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 |
Sample API_Item File |
| Inventory Update | You can update the inventory quantity for your items using this simple file with only 2 columns. See this article for details: Item Inventory Update |
API_Inventory_yyyy-mm-dd_hhmmss_Distributor_xxxx.csv API_Inventory_Overwrite_yyyy-mm-dd_hhmmss_Distributor_xxxx.csv |
|
| Account Item Stock | Update the item stock count at the Account (store). For details: How to Upload Account Item Stock |
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 |
Account Item Stock Sample File |
| User Defined Table Data |
|
||
| User Defined Tables (UDT) |
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 |
Sample API_MapData File |
0 comments
Please sign in to leave a comment.