Content tags: BOM import, BOM export, bill of materials import, import BOMs, export BOMs, bulk BOM, packaging import, BOM spreadsheet, BOM excel
Labels: BOM, packaging, import, export
The BOM importer lets you set up which packaging your products ship with in bulk, instead of editing each product's BOM by hand. The workflow is a round-trip: export your current BOMs to Excel, edit the file, and import it back. Exporting first is also the easiest way to get a correctly formatted file to fill in.
[VIDEO: Walkthrough of the BOM export → edit → import round-trip with a simple packaging example]
Exporting BOMs
- Go to Products.
- Optionally filter the list, or tick the products you want to export. With nothing selected, the export covers every product in the current filter.
- Open the Actions dropdown and choose Export BOMs.
The file downloads as an Excel file (.xlsx). For very large exports, it is emailed to you instead.
[SCREENSHOT: The Products list with the Actions dropdown open, showing Export BOMs and Import BOMs]
Tip: Products that don't have a BOM yet still export as a row, so you can export a handful of products, fill in their packaging, and import — no need to build the file from scratch.
The simplest import
Each row is one packaging line. The file is grouped by Item number — every row for the same product is read together. To give the Aurora Classic Tee a hangtag, a care label, and a polybag, you need three rows:
| Item number | Row type | Line type | Scope | Component item number | Quantity |
|---|---|---|---|---|---|
| AURORA-TEE | line | packaging | product | PKG-HANGTAG | 1 |
| AURORA-TEE | line | packaging | product | PKG-CARELABEL | 1 |
| AURORA-TEE | line | packaging | product | PKG-POLY-M | 1 |
Then import the file:
- Go to Products, open the Actions dropdown, and choose Import BOMs.
- Under Upload Excel file (.xlsx), select your file.
- Click Import.
You'll see a confirmation like "Imported BOMs for 1 product". If any product couldn't be imported, an error message naming that product appears so you can fix it and re-import.
[SCREENSHOT: The Import BOMs modal with a file selected and the Import button]
Targeting specific variants
The Scope column controls which variants a line applies to. Use it when some variants need different packaging.
| Scope | Applies to | What else the row needs |
|---|---|---|
product | Every variant of the product | Nothing extra |
attributes | Only variants matching an attribute filter | Scope attributes, e.g. Color: Black |
variant | One specific variant | Scope variant SKU |
Write attribute filters as Attribute: value, separating multiple values with commas and multiple attributes with semicolons — for example Color: Black, Navy; Size: M.
How importing behaves
- Each product is fully replaced. All rows for an item number rebuild that product's BOM from scratch — anything previously on it that isn't in the file is removed.
- Other products are untouched. Only products whose item number appears in the file are changed.
- Excel only. The importer accepts
.xlsxfiles — the same format the export produces. - Large files are processed in the background and a confirmation is emailed when done.
Column reference
The export includes every column below. Headers are matched by name, so you can leave columns you don't need blank. Item number is always required.
| Column | Description |
|---|---|
| Item number | The product the BOM belongs to. Required on every row. |
| Product name | For your reference only — not used on import. |
| Row type | Use line for a packaging line. (template_link and template_line are covered in the advanced guide.) |
| Line type | Use packaging. |
| Scope | product, attributes, or variant. |
| Scope variant SKU | The variant's SKU. Required when Scope is variant. |
| Scope attributes | Attribute filter like Color: Black; Size: M. Required when Scope is attributes. |
| Component item number | The packaging product used on this line. |
| Component SKU | Optional — pins a specific packaging variant. Leave blank to use the packaging product directly. |
| Quantity | How many packaging units per sold unit. Decimals are allowed. |
| Return on credit notes | Yes or No — whether the packaging is reversed when goods are returned. Defaults to Yes. |
| Include in COGS | Yes or No. Defaults to Yes. |
| Line key, Template, Enabled, Line effect, Overrides template line, Overrides BOM line, Sort order | Used for templates and overrides — see the advanced guide. Leave blank for simple lines. |
Troubleshooting
When a product fails to import, the message tells you what to fix. Common ones:
| Message | Cause |
|---|---|
| No product found with item number … | The host product doesn't exist. Create it before importing its BOM. |
| No component product found with item number … | The packaging product in Component item number doesn't exist or is misspelled. |
| BOM line is missing a Quantity | A line row has no quantity. Every line needs one. |
| Variant-scope lines require a Scope variant SKU | A variant row is missing its Scope variant SKU. |
| No variant found with SKU … on product … | The Scope variant SKU doesn't belong to that product. |
Tip: If a row is silently ignored, check the Row type column — packaging lines must have it set to
line.
Related articles
- [LINK: Advanced BOM imports: templates, overrides, and exclusions — linking templates and fine-tuning inherited lines from the file]
- [LINK: Setting up BOMs and BOM templates — building BOMs directly in the product editor]
- [LINK: Importing a production order from Excel — another Excel-based importer]