Skip to main content
Products

Product Bundles

Create a catalogue bundle that groups hardware and a license, set each child's billing term, add the bundle to a quote, and see how bundles sync with Autotask, ConnectWise, HaloPSA, and Dynamics 365.

Written By Victor Raessen

Last updated 19 days ago

Salesbuildr bundles let you sell multiple products as one package on a quote. A bundle is a Salesbuildr concept β€” parent line plus child products, with pricing built from the children. How that structure appears in your PSA depends on which integration you use, but the same pattern applies everywhere: the bundle parent never syncs outbound; only the child component lines do.

To build a reusable package β€” for example a laptop plus a Microsoft license β€” start with Create a hardware and license bundle. The rest of this article explains structure, pricing, and PSA handoff.

Create a hardware and license bundle

Use this walkthrough when you sell a standard kit that mixes one-time hardware with a software license. The example is a laptop and a Microsoft license. The same steps work for any hardware plus license (or service) pair.

Do this in the catalogue first. Then add the finished bundle to a quote. A one-off bundle you create only inside the quote editor is harder to reuse.

Before you start

  • Your workspace has a PSA connection or Standalone set up. The create buttons stay disabled until that is done.
  • You can create products (Product editor permission).
  • At least one category already exists. The product form will not save without a category.
  • Both items you want inside the bundle already exist as catalogue products. A bundle can only search for products that are already in Salesbuildr β€” it cannot create the laptop or the license as you add them.
  • Those child products are Listed. Unlisted products stay in the catalogue but are hidden from everyday search, including the bundle search.

If you do not see Create bundle product on the product list, ask an admin. That button appears when the workspace can send quotes to customers.

1. Confirm the laptop and the license exist

Open Products. Search for each item by name or manufacturer part number (MPN).

What you sellHow to create it if it is missingTypical Term
Laptop (or other hardware)Create product, or import from the Marketplace by MPNOne-time
Recurring Microsoft license (Microsoft 365, CSP seats)Create service. Cloud seats can also come from Pax8 or Working with Microsoft CSP productsMonth or year
One-time / perpetual Microsoft licenseCreate productOne-time

On each child, open Edit and set Pricing β†’ Term to the billing period you actually invoice. The bundle parent has no Term field. Each child keeps its own term, and the bundle card totals those children by term (for example one-time hardware plus monthly license).

Required on each child:

  • Name
  • Categories β€” at least one
  • Listed β€” on
  • Pricing β†’ Term β€” one-time for the laptop; month, year, or one-time for the license, matching how you bill it

Leave Price, Cost, and Markup empty on everyday hardware so dynamic pricing can follow the distributor feed. Type a sell price on the license when the feed does not set one.

You cannot put one bundle inside another. If search does not return an item, it is usually unlisted, in an unlisted category, or not created yet.

2. Create the bundle

  1. Go to Products.
  2. Click Create bundle product. The product editor opens already set to type Bundle.
  3. On General info, enter a Name customers will recognise as the package β€” for example β€œStandard laptop with Microsoft 365”.
  4. Open Categories and assign at least one category.
  5. Leave Listed on so quoters can find the bundle.

You do not set a sell price or term on the bundle itself. Pricing on a bundle only shows Can be sold and, when leasing is enabled, the leasing toggles.

3. Add the child products

  1. Open the Bundle section.
  2. In Add product, type the laptop name or MPN and click the result. Repeat for the Microsoft license. Use Advanced search when you need filters.
  3. Under Products added, set Quantity for each child β€” this is the quantity per bundle, not the quote quantity. Each quantity must be greater than 0 (use 1 unless the kit includes more than one of that item).
  4. Leave Price blank to use each child’s catalogue sell price. Type a price only when this package should override the catalogue for that child.
  5. Check the Total under the table. You should see separate totals per term β€” for example a one-time amount for the laptop and a monthly (or yearly) amount for the license.
  6. Click Create.

To change a child’s term later, edit that product (Products β†’ open the laptop or the license β†’ Pricing β†’ Term), not the bundle. The next quote that adds the bundle picks up the child’s current term.

4. Add the bundle to a quote

  1. Open a quote and click Add product.

  2. Search for the bundle by name. You can also select it on Products and use Add to quote.

  3. Set the bundle quantity. Child quantities multiply:

    Final child quantity = bundle quantity Γ— quantity per bundle

    Example: the bundle contains 1 laptop and 1 license. Quote 5 bundles and the quote has 5 laptops and 5 licenses.

On the quote you see:

  • One parent line β€” the package name. This row has no price and no billing term.
  • Child lines nested under it β€” the laptop (one-time) and the license (its own term), each with its catalogue price unless you overrode it on the bundle.

Open Manage bundle on the parent line to change a child’s quantity, cost, or sell price on this quote, or to add another catalogue product to this instance. That does not change the catalogue bundle.

To control what the customer sees, use Show bundle products in Manage Settings (or the same control in Manage bundle for this line only). See Quote Editor. For how to present licenses so the proposal matches the invoice, see Presenting licenses and services so clients see the value.

How bundles work in Salesbuildr

A bundle is a catalogue product that groups other products together. Create one with Create bundle product on Products, then add child products and quantities in the Bundle section. See the walkthrough above, or Product Detail for the full product editor.

Parent line and child products

On a quote, a bundle appears as:

  • One parent line β€” the bundle itself. This is the line your customer sees as the package name on the proposal (unless you choose to show bundle contents β€” see Quote Editor).
  • Child lines β€” each product inside the bundle, nested under the parent. Each child keeps its own product type (hardware, service, labour, and so on), pricing, and billing term.

The bundle parent is a grouping row. It does not carry its own billing term or PSA catalogue record β€” only the child products do.

Pricing comes from the children

Bundle pricing is built from the child products you add:

  • Each child has its own cost and sell price (from the catalogue, distributor feeds, or manual overrides).
  • The bundle card in the catalogue shows totals grouped by billing term β€” for example, one-time hardware plus monthly service on the same bundle.
  • The bundle parent does not have a separate price field. What the customer pays is the sum of the enabled child lines.

Quantities multiply

Each child has a quantity per bundle (set when you build the bundle in the catalogue). When you add the bundle to a quote and set a bundle quantity, Salesbuildr multiplies:

Final child quantity = bundle quantity Γ— child quantity per bundle

Example: a bundle contains 2Γ— laptops and 1Γ— docking station. If you quote 3 bundles, the quote syncs 6 laptops and 3 docking stations to your PSA.

How bundles sync to your PSA

Salesbuildr bundles are a quote and catalogue feature. No PSA receives a grouped bundle header when a quote syncs β€” only the individual child products appear on the opportunity or quote in your PSA.

BehaviourAll supported PSAs
Bundle parent on a Salesbuildr quoteNot synced β€” the wrapper row stays in Salesbuildr only
Child products inside the bundleSynced individually β€” each enabled child becomes its own PSA line
Quantities on PSA linesReflect the bundle multiplier (bundle qty Γ— child qty per bundle)
Salesbuildr bundle catalogue productsNot pushed to the PSA catalogue β€” rebuild packages in Salesbuildr or quote components separately
Optional add-ons on a bundleSync when selected on the quote, following the same flattening rules

The sections below cover PSA-specific import behaviour and post-sale handoff.

ConnectWise Manage

Catalogue import

When Salesbuildr imports your ConnectWise product catalogue, each ConnectWise catalogue row becomes one Salesbuildr product. The import does not expand ConnectWise bundle definitions into Salesbuildr bundle children.

What you have in ConnectWiseWhat appears in Salesbuildr
A bundle catalogue item with component productsA single flat product β€” no child products are created automatically
Individual component products in the catalogueEach imports as its own separate product (if category mapping allows)

Practical impact: If you rely on ConnectWise bundle structures today, rebuild those packages in Salesbuildr β€” create a Salesbuildr bundle product and add the component products manually β€” or quote the components as separate lines.

For general ConnectWise product import settings, see Importing Products and ConnectWise Manage Setup.

Quote and opportunity sync

When a quote with bundles syncs to a ConnectWise opportunity, Salesbuildr flattens the bundle:

Salesbuildr quote lineSynced to ConnectWise opportunity?
Bundle parent lineNo
Each enabled child product inside the bundleYes β€” each appears as its own opportunity product line
Optional add-ons on the bundle (if selected)Yes β€” add-ons and their bundle children follow the same flattening rules

On the ConnectWise opportunity Products tab you see individual catalogue products, not a grouped bundle header. If a bundle child fails to sync, check that component product β€” not the bundle parent.

Post-sale: Create ticket

After a quote is approved, Create ticket hands work off to ConnectWise as a service ticket β€” not as a ConnectWise project, project phase, or phase task.

  • The line picker lists bundle components as separate selectable lines, not the bundle parent.
  • Product and labour children are selectable; service children are not shown (they remain on the opportunity for contract or agreement workflows).
  • ConnectWise receives a service ticket with product line items converted from the selected opportunity products.
  • No ConnectWise project, phase, or task is created from bundle structure.

See Fulfillment Tickets for the full post-sale workflow.

Autotask

Catalogue import

Salesbuildr syncs individual products and services from Autotask. Autotask Service Bundles are not imported β€” neither as Salesbuildr bundles nor as grouped PSA records. If recurring services are configured as service bundles in Autotask, recreate them in Salesbuildr as individual products or build a Salesbuildr bundle manually.

Salesbuildr bundle products are also not pushed back to Autotask as catalogue items.

See Autotask Configuration for sync limitations.

Quote sync

When a quote with bundles syncs to Autotask, the bundle parent row is skipped. Each enabled child product, service, or labour line syncs as its own Autotask quote item with the multiplied quantity.

Post-sale: Create ticket

Create ticket on an approved quote creates an Autotask service ticket with ticket charges for the lines you select.

  • Bundle components appear as separate selectable lines in the picker β€” not the bundle parent.
  • Only product lines can be selected as Autotask ticket charges. Service and labour lines appear in the dialog under Not added as ticket charges and cannot be checked. Add services to an Autotask contract from the quote (Add items to contract). Labour feeds estimated hours on the ticket.
  • You can split bundle components across multiple tickets from one quote.

HaloPSA

Catalogue sync

Bundles created in Salesbuildr do not sync to HaloPSA as bundles. Only standard product, service, and labour catalogue rows push to Halo. If you need matching bundle items in Halo, create them manually in the Halo item catalogue.

See HaloPSA Setup for troubleshooting bundle sync.

Quote sync

When a quote syncs to HaloPSA, bundle children appear as individual quotation lines β€” the bundle parent is not included. Quantities and pricing on each line reflect the child row on the Salesbuildr quote, including the bundle quantity multiplier.

Post-sale: Create sales order

HaloPSA uses Create Sales Order instead of Create ticket. The behaviour differs from ConnectWise and Autotask in one important way:

  • Bundle components appear as separate selectable lines β€” not the bundle parent.
  • Product, service, and labour lines are all selectable (Halo includes services in the sales order dialog).
  • Halo receives a sales order with the selected lines β€” not a grouped bundle record.

See Fulfillment Tickets for the Halo sales order workflow.

Dynamics 365

If you use the Dynamics 365 integration, the same flattening rules apply:

  • Salesbuildr bundle catalogue products are not pushed to Dynamics.
  • On quote sync, the bundle parent is not included β€” only enabled child lines appear as quote detail rows.
  • Post-sale ticket creation is not available for Dynamics in Salesbuildr today; bundle structure does not map to Dynamics project phases or tasks.

Quick reference

TopicSalesbuildrConnectWiseAutotaskHaloPSA
PSA catalogue bundles on importN/AOne flat product per row; no component expansionService Bundles not importedIndividual items only
Bundle on Salesbuildr quoteParent + child linesChild lines only on opportunityChild lines only on Autotask quoteChild lines only on Halo quotation
Outbound catalogue syncBundle type not pushedNot pushed as CW bundleNot pushedNot pushed as Halo bundle
Post-sale handoffPick flattened child linesService ticket + product linesService ticket + ticket chargesSales order
Service children in post-sale pickerN/ANot selectableNot selectableSelectable
Project phases / tasksNot createdNot createdNot createdNot created

See also