How to Create Kits or Bundles in Bulk


A kit is several different products but listed under one kit-specific sku. E.g. a pair of pants and a t-shirt listed under a different SKU. A bundle is usually a multiple of the same product.e.g. 10-pack of the same t-shirts.


You can promote your sales by including frequently bought items in a kit and bundling up a SKU which is bought in multiple quantities. 


Creating bulk kits/bundles is quite simple In StoreAutomator. You can use a spreadsheet to define the required fields, which are: 

  • SKUs to include
  • how many of each go into a bundle
  • kit price
  • kit product SKU to list under


Kits are defined as part of the standard Product Data Import feed file, with each kit occupying a single line. Use the “kit_item_sku_X” field to specify the SKUs that go into this kit and use the “kit_item_quantity_X” field to define how many of this SKU goes into the kit. There can be a maximum of 25 different SKUs in a kit. “kit_item_sku_X” and “kit_item_quantity_X” fields must be used as pairs to define the contents of a kit.

Below is a description of kit fields:







Max. 50 characters, must be in column A


Defines kit’s price calculation method

Values: dynamic-actual, dynamic-regular and fixed


Defines the SKUs that goes into this kit

Up to 25 items allowed in a kit


Defines the quantity for the member SKU

Up to 25 items allowed in a kit


Product Name

Max, 150 characters


Brand Name

Max, 100 characters, brand name to be created if it doesn’t exist


Regular price


If kit products don’t exist in StoreAutomator, they need to have SKU creation fields, which are title, brand name and price of the product, listed along with the SKU during the import.

Note: If you have a kit that contains only one master SKU, and another kit that contains 25 master SKUs, you must include these two in different import files; StoreAutomator can import SKUs with similar kit SKU counts.

Kit Families

You can also form kit families; the children would be the newly created kit SKUs, and a new parent SKU must be provided. Kit products use the same variation fields as normal variations.


For example you wanted to create bundles consisting of one t-shirt and one pants, both being the same size. You can form bundles of these t-shirt-pants in different colors and sizes and include them under a parent. Let's say t-shirts Style is T123, and the pants style is P456, then the bundle SKUs look like this: T123-b456-R-S, in this format, t-shirt style-color-size-pants style-color-size. You can create combinations of t-shirts and pants, their colors and sizes and locate them under a parent.




Variation Kit Fields

Use productdata.sku, title, brand_name, description and below fields to create kits from scratch in bulk quantities. Kit creation fields can be imported both in create or update importer mode.

Kit children creation is also possible, if you include variation creation fields (Parentage, variation_types, variation_options, parent_sku) in the same file; for child SKUs parentage must be "child". Including SKUs in kit_item_sku and kit_item_quantity is enough for creating kits.

A word about Kit Prices

While importing the excel file you can adjust the kit price, give a fixed price to the kit or you can have the StoreAutomator importer calculate a price as per your directions provided in the “kit_price_type” field. Below is a list of options that can be used with kit_price_type field:

Dynamic-actual: Use this setting to calculate price from Channel Actual Price with a percentage entered to the “price” field; actual_price times the value in “price” field of the feed file. Actual_price is your current sales price that is active on a channel with repricer. If you use this setting and don’t have a repricer this value falls back to dynamic-regular price,

Dynamic-regular: Use this setting to calculate price from regular price with a percentage entered to the “price” field; regular_price times the value in “price” field of the feed file,

Fixed: Use this setting to set kit’s price to a fixed value, as defined in the “price” field of the feed file. By default kit_price_type is set to "fixed".

If you prefer to assign prices to your kits, it is best that you leave this field excluded from your feed file.

Was this article helpful?

0 out of 0 found this helpful