This file outlines details of customers. Kimelo will send this file once a day. Sellers can upload this file whenever they desire to make changes to their customer data. Sample file:
customers_yyyy-mm-dd-hh-mm-ss - sheet.csv
Customers are the ones who can place orders through Kimelo to be fulfilled by the sellers. Kimelo has been designed to help sellers transition their existing customers to digital ordering by inviting them to Kimelo.
Customers however are also separate businesses. Kimelo facilitates transactions and enables creation of customers. But once customers join Kimelo they can act on their own behalf as well and the seller won’t be able to authoritatively replace edits the customer has made to their own data.
| Filename pattern | customers[datetime].csv |
|---|---|
| ERP to Kimelo | Y |
| Kimelo to ERP | Y |
| System of record | ERP |
| Status | Available |
| Frequency | Daily |
These are the attributes for a customer location defined in the distributor ERP for use in the Kimelo system. Kimelo may also transmit customer attributes back to the ERP with updated customer information in this file format.
Required means if attribute is null we skip that record and log an error.
| Column Name | Example Value |
|---|---|
| erp_customer_id | 123456 |
| restaurant_name | Michal's Restaurant - San Francisco |
| address | 123 Fourth St |
| city | San Francisco |
| state | CA |
| zipcode | 94132 |
| is_checkout_enabled | TRUE |
| erp_price_tier_id | edlp_1 |
| "[email protected]", "[email protected]" | |
| phone_number | 6506697681 |
| store_key | SF1 |
| Column Name | Data Type | Required | Description |
|---|---|---|---|
| erp_customer_id | String | Required | A unique identifier for a customer location within the distributor’s ERP system |
| restaurant_name | String | Required | The customer-selected name of the location |
| address | String | Required | The street address of the customer location |
| city | String | Required | The city name of the customer location |
| state | String | Required | The customer’s state, province, or similar |
| zipcode | String | Required | The 5-digit postal code of the customer location |
| is_checkout_enabled | Boolean | Required | Indicates whether the customer location is allowed to check out orders |
| Array of Strings | Optional | A list of email addresses associated with the customer location, granting access to the system. | |
| phone_number | Array of Strings | Optional | A list of phone numbers (without country codes) for users who have access from the customer location. |
| erp_price_tier_id | String | Optional | The ID of the price tier that defines any specific item prices. Provide a corresponding price tiers in the price tier file first. A customer without a price tier will see base prices. |
| payment_term_days | Integer | Optional | The days until payment is due, based on the customer’s Payment Term. This lets Kimelo show the due date on an invoice. |
| credit_limit | Currency | Optional | The amount of unpaid balance the customer can carry. |
| store_key | String | Optional | The main distribution center in the vendor organization that serves this customer. Manual imports: Kimelo defaults to current context. FTP: required only if you have multiple distribution centers. |
| proprietary_tags | Array of Strings | Optional | The proprietary tags identifying groups of products given customer should see. They need to correspond to the same column in products file. |
June 18, 2025
04/7/2025
Kimelo models customers similar to a business entities with an address, name and contact information. Customers however can not be accessed directly. Instead Kimelo supports a separate object of a User. A single customer account can be accessed by multiple Users. Similarly a User can access multiple Customers.
As such only the User (the people who act on behalf of the Customer) can place orders on behalf of a Customer. Users can be invited to Customer accounts by the seller or by Kimelo team through email or text. After accepting the invitation the User will be prompted to create a password used to log in to Kimelo and place orders. To learn more about user invitation refer to Kimelo help center and user guide.
The contact details provided by the seller will be used to invite the Users but do not create the Users. Sellers are not allowed to modify the Users’ passwords. In case of forgotten login and/or password Kimelo Users can reach out to Kimelo support.
Each Customer created by sellers needs to be identified with an erp_customer_id which will them be used throughout the Customer lifecycle on Kimelo. The email and phone number provided in the file will be used only to invite the first User to the Customer. After the first User is invited, this information will not affect who can access given Customer on Kimelo.
This file is how price tiers can be assigned to individual customers. This can be done by assigning a previously created price tier to a set of customers. Price tier in this file is identified by a unique erp_price_tier_id that has been supplied during creation of the price tier via the price_tiers.csv file.
This file is how payment terms can be assigned to customers. As of January 2025 Kimelo supports two parameters:
payment_term_days - this defines what is commonly referred to as ‘net days’. Kimelo defines an invoice payment date by adding this number of days to the delivery date. E.g. for an order that has a delivery date of Feb 1, placed by a customer with payment_term_days = 1 the payment due date on the invoice will be set to Feb 2.
payment_term_days = 0. This is also a value that will be set for all customer by default until provided otherwise.payment_term_days after the non-zero value has been set will not result in setting it to 0. After this value has been set for a given customer it has be set explicitly to be updated.credit_limit - this defines the maximum amount of unpaid invoices a given customer can accumulate through Kimelo to be able to place additional orders. Customer will not be allowed to place an order that would bring the sum of unpaid invoices (even if all these invoices are within the payment term, before those invoices become overdue) beyond this number.Sellers can decide whether they allow given Customer to place orders to them by specifying is_checkout_enabled parameter. A Customer for whom this parameter is set to FALSE will not be able to place new orders. If this field is left empty Kimelo will insert TRUE value.