How do I import bundle components, and why does the import fail?
Bundle components have their own import. On the product list, select Import, choose Relationships, and upload a file with Bundle SKU, Component SKU, and Component Quantity. The product import sets two related options: Fulfill With Components takes Auto, Yes, or No, and Inventory Includes Components takes true or false. A blank cell keeps the existing choice.
Endless checks every row before it changes anything. If any row has a problem, the import changes nothing, and the “Import failed” notification’s Raw metadata lists each reason with example SKUs:
- Bundle SKU not found or Component SKU not found. The SKU must match an existing, unarchived product.
- Invalid composition. Aliases, Bundles, and Finished Goods can contain Finished Goods or Parts; Bundles cannot contain Bundles.
- A value a spreadsheet rewrote, such as 8.5E+11. Format the column as text and export again.
- A quantity of zero or less.
Some problems stop the import at that row, such as a bundle listed as its own component, a loop where a component already contains the bundle, or a product managed by bill of materials revisions. Bundles earlier in the file are already updated. Fix the row, check that bundle’s components, and import the file again. Contact Endless support for help with an import that stopped.
When a bundle appears in the file, Endless deletes all of its existing components and replaces them with the file’s rows. Bundles that are not in the file keep their components. If the same bundle and component appear twice, the last row is used.
Create missing products with a product import first, because the relationships and cost estimate imports work with existing products only.
The import does not ask for a brand, because a SKU is unique across your company. The relationships export offers an optional Brand to export only that brand’s bundles. It does not use the product list’s filters, search, or sorting.