Most basic customer information can be imported as part of the Sales Data uploads, however if you want to include additional customer information such as address and contact information, or customer segmentation, then you will also need to upload a separate customer file as well as your sales data files.
When preparing your data files for upload (whether that is for manual upload via the Web Uploader in the application, or through an automatic import using the Email Data Import or FTP integration), there are some things you need to be aware of.
File Requirements
Files should be in a csv (comma separated values) format and should contain a maximum of 50000 rows only (large data sets should be broken into multiple files).
A Customer Data Template can be downloaded here and used to populate your data.
Field Descriptions
There are several fields that will be required (those with an asterisk) in order for your customer data to be imported, however there are optional fields that you may also want to consider sending to provide more data for analysis and segmentation.
Field | Type & Length | Description |
Customer Name* | String 200 | This is the name that will display in the application |
Customer ID* | String 100 | Every Customer needs a unique Customer ID - no two customers can share an ID |
Sales Rep | String 200 | Account manager assigned to this customer |
String 200 |
| |
Address Line 1 | String 200 |
|
Address Line 2 | String 200 |
|
Address Line 3 | String 200 |
|
City | String 200 |
|
Post Code | String 50 |
|
Country | String 200 | Recommend ensuring the formats are the same for all countries (e.g. ISO-3166 values) |
Phone Number | String 200 | Recommend including any country and area codes |
Platinum Customer | Boolean | Whether customer is a VIP customer |
Consultant | String 200 | Alternative account manager supporting this customer (must exist as a Sales Rep already) |
Category | String 200 | Generic field for customer segmentation (renamable) |
Campus | String 200 | Generic field for customer segmentation (renamable) |
Client Rank | String 200 | Generic field for customer segmentation (renamable) |
Locality | String 200 | Generic field for customer segmentation (renamable) |
Subdivision | String 200 | Generic field for customer segmentation (renamable) |
Is Individual | String 200 | Generic field for customer segmentation (renamable) |
Parent Child | String 200 | Generic field for customer segmentation (renamable) |
Industry Group | String 200 | Generic field for customer segmentation (renamable) |
Grouping | String 200 | Generic field for customer segmentation (renamable) |
Best Practices
Numerik strongly recommends that any integration follows these best practices:
Any high-quality integration must be resilient to transient faults, and integrations with Numerik are no exception. Integrations should be structured to support error handling and retry any imports that fail. It is the responsibility of the sender to review any error email reports and action resolutions as required.
For long-lasting transient faults, you will need to ensure consistency between Numerik and your source system once the fault is resolved.
You can perform bulk loads of historical data to re-sync systems and resolve data integrity issues as a result of any bugs or faults using the Web Uploader.