How Kimelo integrates with Oracle Netsuite

Kimelo developed a direct integration with Netsuite through its API. This document shows the steps to establish the API connection with Kimelo. Once completed, Kimelo will connect throughout the day to exchange the data necessary to power the Kimelo ecommerce experience.

How to prepare your system for integration

There are a few requirements for Kimelo to ensure a seamless integration of your products, customers, and order channel. The sooner you address these, the quicker your store will be online!

Customers

Before we integrate, you may need to review your main customer data so it will be accurate in Kimelo:

name Name of the customer (or business name)
email Customer's contact email, which helps you invite your customers to Kimelo
phone Customer’s primary phone number, another way to invite customers via text message
address Primary delivery address
city City where the customer is located
state State where the customer is located
zipcode Postal code of the customer’s address. Also maps customers to your delivery routes and fees.
credit limit amount Assigned credit limit for the customer. Leave empty for immediate-pay.
payment terms net days The number of days until a new invoice is due for payment for the customer. Also empty for immediate-pay.
inactive Whether the customer can shop in Kimelo

Kimelo can sync customers without payment terms or with net days.

Kimelo is not currently able to sync a customer who has day of the month terms.

Even when your existing systems handle payments, Kimelo uses this information to keep terms-based customers within purchasing limits.

Products

The integration keeps all your product data up to date in the Kimelo ecommerce experience. You only need to keep it current in Netsuite, as you already do. Examples of how we use product attributes:

NetSuite Field Name Description
itemId The product ID or SKU (Stock Keeping Unit) used to identify the item.
displayName A customer-facing name that’s often easier to read than the SKU.
description A description of the product, to help your customers make a buying decision.
manufacturer The brand or manufacturer that supplies the product.
upcCode The product’s barcode (Universal Product Code), used for scanning.
saleUnit and secondarySaleUnit These define how the product is sold — for example, by the "Each" or by the "Case".
primaryToSecondaryConversionRate Tells how many “Each” units are in one “Case” (e.g., 12 means 12 eaches in a case).
presentationItem.basePrice The base price of a single unit. We calculate the case price using this and the conversion rate.
quantityOnHand The amount of product available (not including what's already committed to orders).
locations Where the product is stored or shipped from — often a warehouse or store location.
weight The gross weight of the product, including packaging.
isInactive Whether the product is currently available. To appear in Kimelo, it must be active (isInactive = false) and in stock.

Sale Units of Measure. Kimelo supports **pack type variants for a given product ID, so if you sell products by item and by case, the two pack types will show up as package choices on our product page.

  1. If a Netsuite product has a Primary Sale Unit and Secondary Sale Unit , then we map it to the each/case in Kimelo.
  2. The Primary Sale Unit identifies which product sales unit is the Each in Kimelo
  3. primaryToSecondaryUnitConversionRate in Netsuite tells us how many each per case
  4. Kimelo translates any known alternative units into case or each. For example your cs, box, and set may map to our Case, and ea, item, and pc map to our Each. Please notify your account manager of these so we can prepare our mapper.

<aside> 👉

Catchweight in a future release. Netsuite does not currently support catchweight. This is how some distributors sell products such as meat and seafood by its actual weight, recorded at the time of sale. If you have this set up within Netsuite let us know, and we can assess enabling it.

</aside>

Enabling the system integration