Skip to Content

Wiki source code of Checkin Data Import Tool

Version 4.1 by David Muszynski on 2025/04/11 18:15
Show last authors
1 The Checkin Data Import Tool (CDIT) has the ability to import Customers, Products and Suppliers from other POS systems into CheckIn. It also has the ability to import Lightspeed/POSIM Line Items data and generate Invoices/Line Items into CheckIn from that data. The Line Items data process is a bit more involved and takes some cleanup of the data and ensuring things imported in properly. This document details the process step by step.
2
3 **File Setup**
4
5 * Begin by downloading the latest version of CDIT in box/dropbox. ([[https:~~/~~/app.box.com/s/eduypm8kh721bv8ax7v2gtk5843jky8i>>url:https://app.box.com/s/eduypm8kh721bv8ax7v2gtk5843jky8i]])
6 * Download the Official Current Checkin Release
7 * Create a folder locally for the current customer's import, with the Current Checkin Release. Replace the Checkin interface file with the latest version of the CDIT.
8
9 **Data Review**
10
11 * Open Customers, Products, Suppliers and Line Items. Find and replace all commas with blank. Find and replace all quotes (") with blank. This can sometimes mess with the import process.
12 * Check for any blank lines at the END of these import spreadsheets. Sometimes there are hundreds of blank lines at the end of these documents.
13 * In the Line Items data, make sure it references the Customer IDs and Product IDs properly.
14
15 **Company Setup**
16
17 * Launch all of the CheckIn files (by selecting all the files and right clicking open - some of the file references might be odd because of the CDIT not being the original interface file)
18 * Navigate into the company setup and select Define Tax Codes and create a Default Tax. Assign it to store ID 100
19 * Create a Store record with store ID 100 in the Stores list
20
21 **Begin Import**
22
23 * Navigate to the Import Layouts -> lightspeed_import layout
24 * Drag all the import files into the relevant section
25 * Select the import button.
26
27 **Field Mapping**
28
29 **Customers** - this is rarely ever changed. Typically we are not importing tax info unless specified but customer or notes. Sometimes there are extra fields at the end that the customer wants imported, but for the most part its very straight forward.
30
31 [[image:Screenshot%202024-11-15%20at%201.19.03%20PM.png||height="665" width="1000"]]
32
33 **Suppliers **- This one is done less often and people tend to not always use our template. It is a very simple import so typically we don't have issues here, but this may have to be mapped manually.
34
35 [[image:Screenshot%202024-11-15%20at%201.27.01%20PM.png||height="657" width="1000"]]
36
37 **Products **- This is one of the more complicated ones. Sometimes the field mapping gets messed up on this. Still unsure what the best practices are for item ID. When doing a Invoice Line Item import, you NEED to import their Product ID into our _Item_ID. However, in general it is best to let CheckIn create our own Item IDs and then have their Product IDs (particularly if they have duplicates) import into the Old_Barcode field.
38
39 [[image:Screenshot%202024-11-15%20at%201.40.08%20PM.png||height="668" width="1000"]]
40
41