Customer Onboarding via CSV - Required Information
When migrating data from a previous system to Cin7 Core, you will need to provide Cin7 Core with data files in CSV format. The following fields and information are mandatory, please ensure all of this data is provided within the CSV files for quick and efficient onboarding.
Customer
Field |
Description |
Customer Name |
Customer Name |
Currency |
Customer currency. A 3-character currency code. |
Payment Term |
Customer payment term. Payment terms applied to all sales for this customer by default. (Eg: 30 days). |
Account Receivable |
The relevant 'AccountReceivable' account name that corresponds to the Customer. This account name or account code should be obtained from the XERO or QuickBooks Application end. Please get in touch with your bookkeeper/accountant if you are unsure of this field |
Tax Rule |
Specify an active Tax rule that will be applied for all sales for this customer by default. The product Sale Tax Rule will override this setting. |
Sale Price Tier |
Price tier name used for all sales to the customer by default. Price Tier names can be viewed/changed on the General Settings page. |
Sale Account |
The relevant 'Sale Account' account name that corresponds to the Customer. This account name or account code should be obtained from the XERO or QuickBooks Application end. Please get in touch with your bookkeeper/accountant if you are unsure of this field |
Supplier
Field |
Description |
Supplier Name |
Supplier Name |
Payment Term |
Supplier payment term. Payment terms applied for all purchases from this supplier by default (Eg: 30 days, Cash on Delivery). |
Account Payable |
The relevant 'AccountPayable' account name that corresponds to the Supplier. This account name or account code should be obtained from the XERO or QuickBooks Application end. Please get in touch with your bookkeeper/accountant if you are unsure of this field |
Supplier taxation rule |
Specify an active Tax rule that will be applied for all purchases from this supplier by default. Product Purchase Tax Rule will override this setting |
Currency |
Inventory List
Field |
Description |
Product SKU |
Each product must have a unique SKU. |
Product Name |
Product Name |
Type |
Product Type. You can create all products as 'Stock' type. Other available types are service, gift card, fixed asset, non-inventory. |
Category |
Provide a product category for each product. |
Unit of Measure |
A unit where you measure the product (Eg: Item, Kg, g, Litres etc.) |
Costing Method |
The costing method applied to the product. Valid values are FIFO, FIFO- Serial Number, FIFO – Batch, FEFO – Serial Number, FEFO – Batch, Special – Serial Number, Special – Batch. The meaning and the differences of each method are explained here. |
Stock on Hand
Note: If there are 0 stock in the Stock on Hand File, please remove them as there will be no use of uploading zero stocks
Field |
Description |
Product SKU |
Unique product code. |
Average cost |
Unit cost of a particular product batch in base currency. (If you don’t have an average cost for each product you can come up with an average cost for the products and specify it. This value can be changed later) |
Location |
Where the stock on hand is to be landed. (Eg: Main Warehouse) |
Received Date (YYYYMMDD) |
Date when this stock was received (If you do not have a specific date, you can use today’s date) |
BOM (Bill of Materials)
Note: Refers to Assembly BOM.
Field |
Description |
Product SKU |
Product SKU of the parent BOM product. |
Component SKU |
Component SKU identifying the product used as a component to manufacture the product specified in the ProductSKU field. Should be unique for the same ProductSKU value |
Quantity |
Quantity of the component in BOM |
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB