Bundle Builder

Some things sell as a set. A shirt and a pant. A three-piece uniform. A gift pack. Bundle Builder takes two or more finished Tech Packs and merges their items into sellable kits — ERPNext Product Bundles — without anyone hand-picking item codes.

Getting there

Awesome bar: Cmd/Ctrl + K → type bundle builder.

Click path: Desk → GarmentFlow → Design → Bundle Builder.

The two steps

Step one — name it and pick the packs

Give the bundle set a name and choose two or more Tech Packs. That's it.

Step two — align them

One matrix. Rows are the bundles you'll create; columns are the packs. Each cell picks that pack's variant and size.

This is where the real work is, and where doing it by hand goes wrong. Two garments almost never share a size system — a pant "42" pairs with a shirt "M", not with a shirt "42". The matrix is where you say so, once, and every bundle in the set inherits the pairing.

Tick the rows you want, set prices, and create.

How items are resolved

Each cell resolves to a real item through that pack's registry, using only the dimensions that pack's items actually vary by.

That last part matters. One pack may vary by both variant and size; another only by size (one colourway); another only by variant (one size). Bundle Builder reads each pack's own granularity and matches accordingly, so packs with mismatched dimensions line up without you flattening them first.

Pricing and cost

• Price defaults to the sum of the packs' selling rates, editable per bundle. A cascading field at the top sets them all at once.
• Cost is the sum of the packs' unit costs, stored as the kit item's valuation rate.

The price is written to your default selling price list.

What gets created

For each ticked row, one Product Bundle with:

• a parent item under the Bundles item group,
• a unique item code derived from the set name,
• non-stock, sales-only (a bundle isn't inventory of its own — its components are),
• the resolved component items.

A row whose components already exist as a bundle is skipped and reported, not duplicated. Re-running the builder to add a few more combinations is safe.

A row with fewer than two components is ignored — a "bundle" of one is just the item.

Where bundles show up

Bundles appear in the Tech Pack Explorer on a Quotation, offered alongside the per-item quantities, so a salesperson can quote "shirt + pant, packed" as a line instead of assembling it every time.

The suggested rate there is the sum of each component's own Tech Pack selling rate times its bundle quantity — and it is only offered when every component has one. A bundle whose components aren't fully costed won't quietly quote at a wrong number.

What to do next

Read Costing the style for where the component prices come from, or Registry and barcodes for how items resolve.