Bundled items

How inventory types can suggest required companions, optional choices, category-backed options, and charged extras when added to an order.

Help updated for v0.10.21 · 2026-07-13

What a bundle does

A bundled item rule lives on an inventory type. It says “when this type is added to an order, also consider these companion types.” That companion might be required, included by default, optional, charged, no-charge, or added as its own standalone line. Bundles are best for remembering the normal support gear around a rental type without turning every order into a hand-built checklist.

Think of bundles as a starting shape rather than a locked package. A lighting console might suggest a case, desk lamp, network switch, UPS, or screen. A wireless mic type might suggest batteries or spare clips. The order builder can accept the defaults, choose from optional groups, adjust quantities, or remove lines when the job does not need them. If the user adds more than the included quantity, Pluck can treat the extra quantity as billable so the order total still reflects the real rental scope.

Bundles are intentionally not the same thing as kits. A bundle does not mean the gear is physically taped together, assigned to one Asset ID, or always rented as one object. It is a memory aid and pricing aid inside order building. Use it when the user needs a reliable starting checklist, not when the warehouse needs to track an assembled physical unit.

When reviewing a type, use the relationship tab to see both sides of the bundle rule: what this type adds to orders, and which other types use this type as a required, optional, charged, no-charge, or category-derived companion.

Required, optional, and category-backed choices

Required bundle companions are added because the primary type normally cannot be fulfilled without them. Optional bundle choices let the user pick from a group, such as one of several monitor options or one of several power options. Category-backed choices are broader: the bundle can point at a category, and the available types in that category become the possible choices when the order is built.

Use category-backed choices when the exact option should stay flexible. For example, a bundle might need “one audio console,” but the quote does not need to decide the exact console until later. That behaves much like category placeholders in estimates: useful for planning and pricing, but it should become concrete before reservation or pick. The user experience should make the choice point clear instead of silently adding the wrong item.

Changing bundle quantities on an order

Bundle quantities are allowed to change on the order. The template helps the user remember what usually ships, but the order is the truth for this customer and this rental. If the bundle starts with two batteries and the user changes it to four, the order should preserve that decision and show whether the added quantity is included or charged.

When reviewing an order, look for bundled lines and any markers that show the line came from another type. If an added companion is free only up to a certain quantity, increasing the quantity may create a charged extra. If the user removes a bundled companion, that removal should affect only the current order unless they intentionally edit the source type’s bundled-item rules.