--- title: "Maintain a Kit" canonical: "https://kb.myframeworks.com.au/space/FRAM/28409362/Maintain%20a%20Kit" format: markdown --- Define and maintain a kit product and the components that make up that kit using the **Kit Maintenance** screen. > 📝 ## Prerequisites > 📝 > 📝 - A Kit Header product has been created using [Create a Kit Header](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28409352). The Kit Header product cannot be a Tally product. > 📝 - Component products to be added to the kit already exist in **Product Maintenance**. > 📝 - Your user role has permission to access **Inventory > Maintenance > Kit Maintenance**. > 📝 - For Assembly kits, the prerequisites and configuration in the [Custom Manufacturing - Implementation Guide](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/737837057) have been completed. ## The Kit Maintenance Workflow 1. Open the **Kit Maintenance** screen from **Frameworks Menu > Inventory > Maintenance > Kit Maintenance**. 2. Create a new kit, or find an existing kit to edit or delete. 3. Select the **Kit Type** that matches how the kit will behave on sales orders and purchase orders. 4. Add components to the kit, including tally products where required. 5. Save the kit, or delete it if it is no longer required. ![image-20260611-012451.png](media://d3efb868-4d10-468c-8b66-cf97948f8fc6) --- ## Kit Types Select the **Kit Type** based on how the kit should behave when added to a sales order or purchase order. Frameworks supports four kit types: **Assembly**, **Exploding**, **Non-Exploding**, and **Template**. ### Assembly ![image-20260611-012741.png](media://2219ec96-5682-409f-9215-b329f0da9377) The **Assembly** kit type is used for custom-built items such as custom doors, where each item ordered has its own configuration but follows a common build pattern. The Assembly kit acts as a reusable template on the sales order, and when the order is marked as **Entry Complete** Frameworks converts each Assembly kit line into a unique stocked product called a **Special Assembly Product**. The componentry is copied and locked against that new product, and Assembly tasks are created against the linked Process Model so the work flows through the **Production Dashboard** and **Process Management Dashboard**. Assembly kits behave like template kits at order entry — components can be customised on the sales order line — but the downstream conversion to a Special Assembly Product is unique to the Assembly kit type. The kit itself is never sold from stock; it is instantiated each time it is ordered. Once **Assembly** is selected, the same options as Template kits become available: - **Allow products not on the kit to be added**: Enable to allow products to be added to the kit, through the **Kit Order Line Maintenance** window, at the time of entering the product on a transaction. This includes adding special products from the **Actions** menu. - **Can kit products be selected**: Enable to allow counter staff to select which default components are included on the line at order entry. When disabled, individual components can still be removed by clicking the **Close** icon. - **Can Change kit Price**: Enable to allow users to update the kit's **Sell Price** or **Sell Price by GP%** by clicking the **Pencil** icon. The **Special Buy-in** option is always available regardless of this setting. Assembly kits require additional setup beyond the **Kit Maintenance** screen, including the **InvKitPrefixS** and **InvKitNextNo** system settings, a manufacturing branch, Assembly standard tasks, and a linked Process Model. > ✅ Refer to the [Custom Manufacturing - Implementation Guide](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/737837057) for the complete setup sequence, and to [Understanding Custom Manufacturing with Assembly Kits](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/737738753) for background on how the workflow operates end to end. ### Exploding ![image-20260611-012558.png](media://2af82cad-f7cb-4380-af28-a19dec8c65bf) The **Exploding** kit type explodes the kit into its components at sales order and purchase order entry. Once exploded, the system lists all kit components individually on the customer sales invoice or docket. Exploded components behave like any other product on the transaction and no further kit functionality applies. ### Non-Exploding ![image-20260611-012620.png](media://164a5d2d-c6ec-4c52-b49c-05e4b86f07b0) The **Non-Exploding** kit type keeps the kit header product on the transaction rather than breaking it into components. Two variations apply: - **Non-exploding kit defined as a normal stocked product** (product type = 0). The kit must be assembled in **Kit Assembly/Disassembly** before sale, because stock levels are adjusted for the kit header product when a sale is made. - **Non-exploding kit defined as a non-stocked product** (product type = 1). Stock levels do not need to be maintained for the kit header product. When a sale is made, stock levels are adjusted only for the component products, not the kit header. Once **Non-Exploding** is selected, the following options become available: - **Sum the Component costs as the kit standard cost**: Enable to calculate the cost of the kit header product as the total cost of its components. - **Sum the Component sell prices as the kit std sell**: Enable to calculate the sell price of the kit header product as the sum of the sell prices of its components. - **Update Kit Product costs and prices**: Used together with the **Sum the Component...** checkboxes. When enabled and saved, Frameworks reprices the kit header to the sum of the components and updates the unit sell and unit cost based on the selected options. Clicking this is a once-off reprice. The **Sum** options do not apply to exploding kits, because exploding kits list the individual components on a sale. ### Template ![image-20260611-012649.png](media://4a68d8c9-e4e7-49e5-9881-80f19537b856) The **Template** kit type (also known as "Kits on the Fly") lets users add a kit at sales order or purchase order entry and then choose the required components, including special products and special buy-ins, at the time of product entry. Kit pricing can also be adjusted at that point. Once **Template** is selected, the following options become available: - **Allow products not on the kit to be added**: Enable to allow products to be added to the kit, through the **Kit Order Line Maintenance** window, at the time of entering the product on a transaction. This includes adding special products from the **Actions** menu. - **Can kit product be selected**: Enable to allow users to select the components they want to add to the kit at the time of entering the product on a transaction. When disabled, users can still remove a component by clicking the **Close** icon. - **Can change kit price**: Enable to allow users to update the kit's **Sell Price** or **Sell Price by GP%** by clicking the **Pencil** icon. The **Special Buy-in** option is always available regardless of this setting. --- ## Create a New Kit Create a new kit and add its components from the **Kit Maintenance** screen. ### Steps 1. From the **Kit Maintenance** screen, click **New**. The right side of the screen becomes editable. 2. In the **Kit Name** field, select the kit name defined in [Create a Kit Header](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28409352). The description auto-populates. Click **Search** to open the **Product Finder** window if needed. 3. From the **Kit Type** drop-down menu, select **Exploding**, **Non-Exploding**, **Template**, or **Assembly**, and configure the available options for that kit type as described in the **Kit Types** section. 4. Click **Add** to add each component to the kit header, then complete the component fields: - **Component**: Click **Search** to find the product to add to the kit. - **Description**: Auto-populated based on the selected component. - **Qty**: Enter the quantity required. Cannot be zero. - **UOM**: Populated from **Product Maintenance**. - **Std Cost**: Populated from **Product Maintenance**. - **Unit Sell**: Populated from **Product Maintenance**. 5. If any component is a Tally product, edit the tally quantities using the **Tally** procedure described below. 6. Click **Save** to apply the changes. --- ## Edit Tally Quantities on a Component When a kit includes tally products, the **Tally** button allows tally quantities for the products on the kit to be edited and maintained. ### Steps 1. In the components grid, click the product line to edit. 2. Click **Tally**. The **Tally Maintenance** window opens. 3. Edit the tally quantities for the product within the kit. 4. Click **Save/Close** once the tally has been updated. --- ## Maintain an Existing Kit Edit the components, kit type, or kit-type options on an existing kit. ### Steps 1. From the **Kit Maintenance** screen, click **Find** to return a list of all kits, or refine the search using the **Kit Name** and **Component Code** fields if known. 2. Click the **Kit Name** hyperlink to display the kit information on the right side of the screen. 3. Click any editable field to change its value. The **Kit Name** and **Description** fields cannot be edited. To change these, delete and recreate the kit. 4. Click **Save** once all changes have been made. --- ## Delete a Kit Remove a kit that is no longer required. ### Steps 1. From the **Kit Maintenance** screen, click **Find** to return a list of all kits, or refine the search using the **Kit Name** and **Component Code** fields if known. 2. Click the **Kit Name** hyperlink to display the kit information on the right side of the screen. 3. Click **Delete**. A confirmation prompt displays. 4. Click **Yes - Perform delete** to confirm the deletion. ## Result The kit is created, updated, or deleted in **Kit Maintenance**. Created and updated kits are available for selection on sales orders and purchase orders, and behave according to the selected kit type. Deleted kits no longer appear in **Kit Maintenance** searches. > ✅ ## Related Tasks > ✅ > ✅ - [Create a Kit Header](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28409352) > ✅ - [Custom Manufacturing - Implementation Guide](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/737837057) (required setup for Assembly kits) > ✅ ## Related Information > ✅ > ✅ - [Understanding Custom Manufacturing with Assembly Kits](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/737738753) > ✅ - [Kit Maintenance](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28409556) --- ## Additional Information - System flag **FWSOFKitComp** — Enable to expand non-exploding kits to show componentry in the **Sales Order Fulfilment** screen. - System flag **InvRctKDA** — Enable to disassemble non-stocked kits at receipt. - System flag **SOPPS20Kit** — Enable to print components on the picking slip for all non-exploding kits.