Understanding Column Mapping and Auto-Mapping
What Is Column Mapping?
When you import a CSV file, AccuArk needs to know which column in your file corresponds to which field in the system. For example, your file might have a column called "Product Name" that should map to AccuArk's "Item Name" field. Column mapping is the process of making these connections.
How Auto-Mapping Works
AccuArk automatically maps your CSV columns to its fields by comparing your column header names against a list of known keywords. This happens instantly when you load your file.
For example, for inventory items:
| Your CSV Column Header | Auto-Maps To |
|---|---|
| "Product Name" or "Item" | Item Name |
| "SKU" or "Item Code" | SKU |
| "UPC" or "Barcode" | Barcode |
| "Department" or "Category" | Category |
| "Sell Price" or "Retail Price" | Price |
| "Unit Cost" or "Buy Price" | Cost |
| "Quantity" or "On Hand" | Stock Quantity |
Auto-mapping recognizes many common variations of column names. If you exported the data from AccuArk, the column headers match exactly and every column auto-maps correctly.
The Mapping Grid
Step 2 of the import wizard displays a mapping grid with one row per column in your CSV file. Each row has:
- File Column — The exact header name from your CSV
- Maps To — A dropdown showing all available AccuArk fields plus a "(Skip)" option
- Preview — The value from the first data row, so you can verify the mapping is correct
Adjusting Mappings
To change a mapping:
- Find the row for the column you want to adjust
- Click the Maps To dropdown
- Select the correct AccuArk field from the list
To skip a column entirely (not import its data):
- Click the Maps To dropdown for that column
- Select (Skip)
Required Fields
Some fields are required for import and are marked with an asterisk (*) in the dropdown list. For example, "Item Name *" or "Customer Name *". You must map all required fields to a column in your CSV file before you can proceed.
If you click Next without mapping all required fields, AccuArk displays a message listing the unmapped required fields.
Lookup Fields
Some fields are "lookup" fields, meaning the value you provide must match an existing record in AccuArk. For example:
- Category on an inventory import must match an existing category name
- Customer Name on an invoice import must match an existing customer
- Account Type on a chart of accounts import must match a known account type
If a lookup value does not match, AccuArk reports it as a validation error in Step 3.
Tips for Successful Mapping
- Use the template — Export first to get a file with the exact column headers AccuArk expects. This ensures perfect auto-mapping.
- Check the preview column — Use the preview values to verify that each mapping is correct. If the preview shows a price in a "Name" field, the mapping is wrong.
- One field per column — Each AccuArk field can only be mapped to one CSV column. If you have duplicate mappings, only the last one is used.
- Extra columns are fine — If your CSV has columns that do not apply (e.g., an internal code you do not need in AccuArk), set them to "(Skip)". They are ignored during import.