Simplifying Creating Kits and Simples

Kits & Configurables Imports

This document assumes that you know about basic product imports in SalesWarp.  If you need more information, check out our help documentation at https://documentation.saleswarp.com

Simplifying the import of Kits and Configurables into SalesWarp is a two-step process. 

First, ensure all the products exist or are created in in SalesWarp.  The following five pieces of information are required to create a SIMPLE base product in SalesWarp.  You can use your regular imports already established for this, but if you are trying to quickly set up new products and kits, there are five minimum data elements required to SELL a product through SalesWarp.  While this two-step method adds an additional step, it makes troubleshooting import issues easier, as product creation will be separate from tying simple products to kit/configurable parents, and, also due to the fact that that each type of complex product type requires different information.

• Type
• SKU
• Name
• Unit_price
• MSRP

For the first round, (where you are only importing the SIMPLE SKUs)  you do NOT select either the Kit or Configurable selections on the Settings tab.  Just map the five required items and import the products (the type field is on the "product info" tab, which will map and import just fine.)

Complete the simple product import as you would usually do.

Tying Simples to Configurable and Kit Parents

To Tie kits and configurable together into their groups, you'll do a separate import.  I recommend doing kits and configurables separately, then you will select the type from the settings, specifying the fields and the delimiters.

For Kits, the items required are:

• Type
• SKU
• Kit SKU (think parent)
• Component Quantity

For Configurables, the required items are:

• Type
• SKU
• Configurable SKU (think parent)
• Variation Type
  • If you have multiple variation TYPES, such as Color and Style, they both are required to be identified at the configurable SKU level
    • In alphabetical order
    • Delimited consistently
  • Variation Name
    • In the same order as the TYPES so if you have color and size it would be (Blue;12 in), since the variant types have to be listing in alphabetical order.

For each and every configurable SKU you define, each variant TYPE AND NAME must be separated by the same character.  You specify which character you used as a separator when you do the actual import. 

Do not use commas and do not use any special character you might have in a SKU such as underline or dash.  SalesWarp recommends the pipe character "|".  This is the shift of the backslash "\" character which is usually located right above the enter key (at least on desktop PC keyboards)

Using the NAME of your product can be helpful while you are building your file, but is not required, you can either remove it before importing, or simply don't map it.  But it can help to keep your sanity, especially if you are importing a LOT of kits or configurable groups.

ALL SKUs are required in the SKU column, whether kit, configurable or simple.  The "parent" for each type is only entered on the simple line items, in the Configurable SKU or Kit SKU column.  Refer to image below.

Notes and Comments:

At this time, the product import only allows a SKU to exist in the file a single time (Column B), so you should do as much as you can as far as importing all the simple products and and all the unique kit SKUs for any given kit.  Then the shared component would have to be added to each kit through the user interface.

Note that you do not have to import kits and configurables in this two-step process.  If you want to build your files out to include the five required pieces of info in a single file feel free to do so.  This makes creating products easier, separating product creation from the tying of simples to parents.

We are looking into separating the kit/configurable import into a separate import type, so that you can build multiple kits with common SKUs, in a single file.  When that happens, then the two-step process would be required, should you have the common SKU that belongs to multiple kits (or you could still update that one SKU in the kit through the user interface)