Retail kits and assembly: selling bundles without losing the components

Implementation · 7 min read

A bundle looks simple on the shelf: three products, one box, one price. In the system it is a promise — that selling the box will correctly reduce the stock of everything inside it. Break that promise and the components quietly drift: the kit sells, the parts stay on the books, and the next count discovers phantom stock. Business Central handles this with assembly; the trick is knowing which "kit" mechanism a store actually has, and picking the assembly policy on purpose.

Three different things get called a kit

The confusion is understandable: search results for retail kits mix Business Central assembly with Dynamics 365 Commerce product kits, which are configured in Commerce headquarters under Retail and Commerce, Products and categories, Released product kits — a different product surface with kit orders and BOM journals of its own. An LS Central store working in Business Central should reach for the assembly BOM. Reaching for Commerce kit documentation while standing in Business Central is how kit projects stall in the first week.

There is also a fourth thing sometimes called a kit: selling several ordinary items together under a promotion. That is a pricing exercise, not an inventory one — no assembly, no parent item, and each component keeps its own stock life. Use it when the bundle is only a price story. The moment the bundle needs its own shelf identity, its own barcode, or availability answers of its own, it needs to be a real assembly item.

Assemble-to-stock or assemble-to-order

The Assembly Policy field on the item card carries the decision, and the two options behave very differently at the point of sale:

• Assemble-to-Stock is for standard items, such as packaged kits, that are assembled and stored for future sales. The kit is picked and processed as a single item and treated like a finished item. On a sales line, Business Central checks availability for the assembled item only — not for its components. If the shelf is empty, the answer is "no kits", even when the back room holds every component.
• Assemble-to-Order items are not expected to sit in inventory. Enter one on a sales order and an assembly order is automatically created and linked to that sales line, ready to be customised — components and resources on the linked order can be edited for the customer's specification before it is assembled and shipped.
• Mixed lines have a rule. When assemble-to-order and ordinary inventory quantities are combined on one sales order, the assemble-to-order quantities must be shipped first. Staff who promise a partial shipment of shelf stock first are fighting the system.

For most retail bundles — gift sets, seasonal packs, starter kits — assemble-to-stock is the honest choice: the bundle is standard, customers buy it off the shelf, and the assembly work belongs in a quiet hour, not in the middle of a sale. Reserve assemble-to-order for bundles the customer genuinely configures. One more wrinkle worth knowing: an item set to assemble-to-stock can still be assembled to order in a specific sale, but that is an exception path, not a reason to blur the policy.

Build the assembly BOM

1. Create the parent item first. The kit gets its own item card, its own description, and its own price. Components keep their own cards and remain sellable on their own unless the store decides otherwise.
2. Open the Assembly BOM from the item card. Navigate to Bill of Materials, then Assembly, then Assembly BOM.
3. Add one line per component. Set Type to Item for a stocked component or Resource for labour, choose the component in No., and enter the Quantity Per — how many of that component go into one kit. The description fills in from the component.
4. Check the flag. Back on the item list, the Assembly BOM field shows Yes for the item. If it does not, the BOM was not saved on the item staff think it was.
5. Set the Assembly Policy deliberately. Assemble-to-Stock for shelf bundles, Assemble-to-Order for configured bundles, per the decision above.

Keep the BOM boring. Every component line is a stock movement waiting to happen, so a BOM that lists packaging, inserts, and labour as stocked items will consume them all on every assembly. Labour belongs on a Resource line, not as a phantom stocked item that someone later has to count.

Sell and assemble without losing components

For assemble-to-stock kits, the work happens in the assembly order. Create one from Assembly Orders with New, choose the kit in Item No., and enter the Quantity to build. The lines arrive from the assembly BOM with their quantities scaled. Post the order and the components are consumed while the finished kits land in inventory as single items, ready to be picked and sold like anything else.

Watch the availability step: if one or more components are not available for the quantity and due date, the Assembly Availability page opens and shows how many kits can actually be assembled from what is on hand. Affected lines carry an Avail. Warning. The documented ways out are to postpone the starting date, replace the component with another item, or select an available substitution if one is defined. What not to do is quietly reduce the build quantity and leave the warning unexamined — a recurring warning is usually a component stock problem (a miscount, a missed receipt) announcing itself early, while it is still cheap.

Discipline that keeps component stock honest:

• Assemble in batches, on a schedule. Ad-hoc one-off assemblies are where postings get skipped. A skipped posting is a kit sold and components never consumed.
• Never sell components out of an assembled kit informally. If a customer wants one part from a built kit, the kit must be disassembled on paper or the part sold from component stock — not lifted out of the box and forgotten.
• Count components and kits as one family. A count that verifies kits but not their components, or the reverse, cannot catch the drift this article exists to prevent.

Returns and unbundling

A returned kit is where bundle processes usually break. The customer brings back the box; one component is missing or damaged. If staff simply put the kit back into inventory as one unit, the store now holds a kit that is not a kit, and the component stock is wrong in the opposite direction.

The clean pattern: receive the return against the kit item, inspect it, and then decide. A complete, resaleable kit goes back as a kit. An incomplete one should be unbundled — in Commerce kit processing this is the disassembly order's job, which reverses assembly by raising component inventory and lowering the kit; the same principle applies wherever kits are broken down. The surviving components go back to component stock, the missing or damaged component is written off through the store's normal adjustment process, and no phantom kit remains on the shelf count. Note the Commerce posting rule as a general warning about finality: once an assembly order is posted it cannot assemble more kits — a new order is needed — so postings should be checked before they are made, not repaired afterwards.

What success looks like

Build one kit end to end and audit it. Post an assembly order for a small quantity, then verify three things: component inventory fell by exactly Quantity Per times the number of kits; kit inventory rose by the number of kits; and a sales line for the kit now checks availability against the kit itself. Then return one kit incomplete and unbundle it, and confirm the surviving components are back in component stock and no whole kit remains overstated. If both halves of the loop reconcile, the bundle is safe to sell at volume.

FAQ

A kit shows unavailable but all components are in stock. Why? For an assemble-to-stock item, availability is checked on the assembled item only. Build more kits with an assembly order; component stock alone does not create kit availability.

Can components still be sold individually? Yes. Components keep their own item cards. Assembly consumes component stock; it does not reserve every unit for kits.

Is a Business Central assembly the same as a Commerce product kit? No. They are different mechanisms in different products, with different setup and order types. Confirm which product the store runs before following any kit procedure.