Column Mapping

Column mapping is the brain of the import. This is where you tell the plugin which column in your file is the SKU, which is the name, which is the price, and so on.

What You See in Step 2

Step 2 of the Quick Import Wizard — left column = file columns, right column = WooCommerce fields.

The page has two sides:

• Left (File Columns): Every column found in the first row of your file
• Right (WooCommerce Fields): Every field you can map to, grouped by category

Between them, you drag and drop.

Auto-Match

When the page loads, the plugin tries to auto-match columns by name. So:

• SKU in your file → connects to the SKU field
• Regular Price → connects to the Regular Price field
• Product Name or Name → connects to the Name field

For standard CSV files, auto-match handles 80-100% of the work.

What Auto-Match Looks For

The plugin checks (case-insensitive):

• Exact name match: SKU = sku
• Space removed: Product Name = product_name
• Common aliases: Title = Name, Type = Product Type, etc.

How Aliases Work

The plugin has a built-in alias table with 200+ common column names. So these all map to SKU:

• sku
• SKU
• product_sku
• item_code
• manufacturer_code
• part_number

If your column uses a different name, you will need to map it manually.

Manual Mapping

For any column that did not auto-match:

1. Click the column on the left (it highlights in blue)
2. Click the target field on the right
3. A connection line appears between them

Or use drag-and-drop:

1. Click and hold a column on the left
2. Drag it to the field on the right
3. Release

Required Fields

Some fields are required. They have a red star next to the name.

Required Fields Per Entity

If you do not map a required field, the Next button is disabled.

Unmapped Columns

Columns on the left with no connection are ignored during import.

In the final step (Review), you will see a summary:

15 of 20 columns mapped. 5 columns will be ignored.

Click on the unmapped section to see which columns are being skipped.

"Use Only Mapped Fields" Option

By default, unmapped columns are silently ignored. But if you want the plugin to store unmapped columns as custom post meta, turn this off.

Adding a Column Not in Your File

Sometimes your file is missing a column you need. Example: your file has no "Status" column but you want every product to be publish.

How to Add a Default Value

1. Click + Add Field at the bottom of the mapper
2. Pick the WooCommerce field (e.g., Status)
3. In the value box, type the default value (e.g., publish)
4. Every row in the import will use this value

Default Value Variables

You can also use dynamic values:

Preview Data Button

Before finalizing the mapping, click Preview Data to see the first 10 rows of your file, with your mapping applied.

The preview shows:

• Column-to-field connections
• How your data looks after the mapping
• Any red errors (missing required values)

This is the best way to catch mistakes before running the import.

Save Mapping as Preset

If you import the same file format often, save the mapping to reuse later.

How to Save

1. Finish your mapping
2. Click Save Mapping button at the top
3. Give it a name (e.g., "Supplier X Daily Feed")
4. Click Save

How to Load

1. On Step 2, click Load Preset
2. Pick a saved preset from the list
3. Your mapping is applied automatically

Manage Presets

Go to Webkul WC Addons → Advance Import Export → Settings → Presets to:

• Rename presets
• Delete old presets
• Export presets as JSON (share with colleagues)
• Import presets from JSON

Field Categories (Right Side)

Screenshot: Target-field select expanded — every mappable WooCommerce field grouped by category.

The right side groups fields by topic to make them easier to find.

Products

• Basic — Name, SKU, Description, Short description
• Pricing — Regular price, Sale price, Sale dates
• Inventory — Stock, Manage stock, Backorders, Low stock
• Shipping — Weight, Length, Width, Height, Shipping class
• Categories & Tags — Categories, Tags, Brand
• Images — Featured image, Gallery
• Attributes — Color, Size, Material, etc.
• Variations — Parent SKU, Variation attributes
• SEO — Yoast, RankMath, AIOSEO (if compat on)
• Custom Fields — ACF, Meta Box (if compat on)
• Other — Status, Visibility, Featured, Virtual, Downloadable

Orders

• Basic — Order Number, Date, Status
• Customer — Customer Email, Billing/Shipping fields
• Items — Line items (JSON or concatenated)
• Payment — Payment Method, Transaction ID
• Shipping — Method, Cost

Value Mapping (Translate Values)

Sometimes the values in your file do not match what WooCommerce expects. Example: your file has rouge, bleu, vert but WooCommerce uses Red, Blue, Green.

Use value mapping to translate.

How to Set Up

1. Map the column first (e.g., Color → attribute: Color)
2. Click the Transform button next to the column
3. Pick Value Mapping
4. Add pairs:
   • rouge → Red
   • bleu → Blue
   • vert → Green
5. Save

Now every row with rouge becomes Red in WooCommerce.

See Transformations for more options (find/replace, math, formatting).

Column Separators

For columns with multiple values (like categories), you can set the separator.

Example

Your file has:

Categories
"Clothing > Men's > Shirts"
"Home, Kitchen, Dining"

The first row uses > as the hierarchy separator. The second row uses , as a list separator.

Settings

In Step 2, click Separators to set:

Mapping Decision Flow

When you arrive at Step 2, follow this:

Quick rules:

• Red star field = required (must map or set default)
• Auto-match uses aliases (Name, name, product_name all match Product Name)
• Save presets to skip this step next time

Troubleshooting

Related Pages

• Quick Import Wizard — Step 2 in context
• Transformations — Change values during import
• Migration Presets — Pre-made mappings for Shopify, Magento
• Compatibility — SEO, ACF, Dokan fields