Importing Bundles
Bundles are two or more items sold together. Creating a bundle allows you to group items that are exclusively sold together or group items that can be purchased together and separately.
This document covers the process of adding multiple bundles through CSV import. You can also add a single bundle.
CSV File Guidelines
You can import bundles using CSV files only; no other data or file formats are supported. Here are the key points to consider:
- Formulas in formula-driven attributes are executed automatically after bundles have been imported.
- If the CSV file doesn’t have an attribute that’s added to the category, you can add a new column in the CSV with the attribute name in the header. The upload process will populate the value for this attribute. Note that empty rows and columns are ignored.
- Each bundle should include a category node. If the category node is missing, the bundle won’t be created.
- Use the - > delimiter for category nodes. Incorrect mapping or absence of category nodes may result in bundle creation issues.
- The headers, represented in the first row of the CSV file, should match the attributes of the bundle. While attribute titles aren’t case-sensitive, maintaining case consistency with the original attribute titles is recommended.
- Empty rows and columns are ignored.
- When updating or upserting bundles, entering NULL in a spreadsheet cell will override existing values with blank values.
- The ActionTarget field determines what action is being taken for that row of data.
We recommend that you download the template file to use as a guide when creating your own CSV file for import to minimize errors during the import process.
Supported actions
| Action | Description |
|---|---|
| UPSERT | Creates a new bundle if the bundle doesn’t exist, or updates an existing bundle. |
| CREATE | Creates a new bundle. |
| UPDATE | Updates an existing bundle. |
| PUBLISH | Publishes an existing bundle that’s in draft state, making it available on the storefront. |
| UNPUBLISH_KEEP_DRAFT | Unpublishes an existing bundle. If a draft version exists, the live version is unpublished and the draft is retained. If no draft exists, the live version is unpublished is saved as a draft. |
| UNPUBLISH_KEEP_LIVE | Unpublishes an existing bundle and moves it to the draft state. If a draft of that item already existed, it’s deleted. |
| DELETE | Deletes the existing bundle. |
| ATTACH_BUNDLE_PRODUCTS | Adds products to an existing bundle. You can specify the product SKU and quantity of the bundle products in the items column. |
| DETACH_BUNDLE_PRODUCTS | Detaches products from an existing bundle and converts them to items. The items column holds the SKU and quantity of the bundle products to be detached from the bundled SKU. |
| CHANGE_CATEGORY | Updates the category of an existing bundle. Depending on how your storefront is configured, this may change where or how your bundle is viewed by the customer. |
| ATTACH_CHANNELS | Adds specified channels to the bundle. The channels column holds the channels to be attached. |
| DETACH_CHANNELS | Removes specified channels from the bundle. The channels column holds the channels to be detached. |
Attribute data format
When preparing your CSV file for import, ensure that the attribute data format aligns with attribute type requirements. Different attribute types have specific formatting criteria:
| Data Type | Format Rule |
|---|---|
| Text | Ensure the data is in text string format. |
| Number | Use numerical data only. All non-numeric data is ignored. |
| Boolean | Use TRUE or FALSE only. All other values are ignored. |
| Date | Format dates exactly as during attribute creation. |
| List of values | The value you enter must match one of the predefined values you set up when adding a list of values attribute. |
| Serial | Leave this field blank; fabric automatically generates the serial number during import. |
| SKU | Provide the SKU for the bundle to be created. |
The status attribute is imported as live only when all mandatory attributes are provided for the bundle. Otherwise, the status is automatically updated to draft, regardless of the value you provide in the file.
Prerequisites
Before initiating the bundle import, ensure that:
- You have created at least one leaf category with attributes assigned to it to add the bundle to. For more information about creating categories, see the Categories section.
- The CSV file adheres to the guidelines.
Procedure
-
In the left menu, click Product Catalog > List > Bundles.
The Bundles page is displayed. -
Click Import.
The Select a leaf category window is displayed. -
Select a Leaf.
The root categories and leaf categories appear as they’re set up in Categories. Depending on your configuration, you may have to select one or more root categories before selecting a leaf category. -
Click Next.
The Import CSV file window is displayed. This window provides a link to download an example template for the CSV file. -
To import a CSV file, do one of the following options:
- Drag and drop the CSV file into the window.
- Click Select a File from your computer.
-
Click Import file.
The CSV file is imported, and the bundles are added to your product list.
fabric stores the CSV files you upload to your account. You can view the status of the import and re-download the original files by visiting the Import History page.
Troubleshooting
Refer to the following table for a list of common errors when importing and how to correct them.
| Error Message | What it Means | What Happens to the Bundle | How to Resolve | Comment |
|---|---|---|---|---|
| Category Node not found | The category node name is incorrect or missing. | A bundle can’t be created without a proper category node. | Verify the name of the node and the delimiter. | |
| Internal Server Error | Server issues. | The bundle isn’t created or updated. | Try again. | This is an intermittent issue. |
| Attribute Name not found | The attribute mentioned in the CSV header isn’t added to the category. The attribute name must be an exact match. | The bundle is created, but this specific attribute will be ignored. | Check the attribute name and ensure it’s added to the category for importing bundles. | |
| Attribute Name value is invalid | The provided value has flaws or validation issues. | The attribute value won’t be saved to the bundle. | Provide the correct attribute value. | Example: Adding text for a number-type attribute triggers this error. |
| Status Mandatory attributes (required) | To set a bundle’s status to live, all mandatory attributes are required. | The bundle is created, and the attributes are updated. However, it can’t be set to live, defaulting its status to draft. | Ensure all mandatory attributes have a value in the CSV file. | For delta imports, all mandatory attributes and values are required to set the bundle’s status to live. |
| Some mandatory attribute values missing | Some mandatory attributes lack values in the CSV file. These are either globally mandatory attributes (set at the attribute level) or category-specific mandatory attributes. The bundle is created with errors; only values in the CSV are added. | Include values for all mandatory attributes. | Bundles with missing mandatory attributes can’t be set to live. |
Related Topics
Was this page helpful?