# Kits and Subscription Boxes

A **kit** is a SKU made of other SKUs of the same client: a gift set, a bundle, a starter pack. Lift supports kits built at packing, kits built ahead and kept in stock, and subscription boxes whose contents change from one cycle to the next.

You manage a client's kits from the client's page under **Clients**: **New kit**, **Kit contents**, **Subscription cycles** and **Build orders**.

## Creating a kit

On the client's page, choose **New kit**. Fill in:

- **Kit SKU** (up to 50 characters, for example `GIFT-01`), **Name** (up to 255 characters) and an optional **Barcode**.
- **Contents of one kit**: a **Product SKU** and **Quantity** for each component, with **Add product**. Components are products of this client only, and a kit cannot contain another kit. A kit has up to 50 components, each with a quantity from 1 to 10,000.

Choose **Create kit**.

You can also create kits in the [SKU import](/docs/3pl/skus) with two extra columns: **kind** (`ITEM` or `KIT`) and **components**, written as `SKU:quantity` pairs separated by semicolons, for example `MUG-01:1;TEA-50G:2`. A product cannot later become a kit, or a kit a product.

## Kit versions

Changing a kit's contents makes a new version. **Orders already taken keep the version they arrived with** until you choose **Update open orders**. The kit's page lists each version with its open orders and contents.

## Kits built at packing

By default a kit is **built at packing**: the order's kit line is picked as its components, and the packer builds the kit at the pack station while scanning each component. Nothing is stocked ahead.

## Kits built ahead

A kit you sell often can be built ahead and stocked on its own lot.

1. On **Build orders**, choose **Stock this kit** for the kit. That gives it its own product in OpenBoxes. Only a stocked kit can be built ahead.
2. Under **New build**, choose the **Kit** and **Kits to build** (1 to 10,000), then **Start build**. Each build uses the kit's current contents. The components go to the kitting area.
3. When the kits are made, open the build, enter **Kits built** under **Record kits built**, and choose **Complete build**. The kits come back into stock.

A build shows **Picking components**, **At kitting**, **Completing**, **Coming back** and then **Done**, or **Cancelled**. Cancelling a build releases the components back to the depot. If a build shows **Needs attention**, choose **Resolve this build** and say what happened to the components.

**Orders for a kit you built ahead.** Each client chooses how orders for a stocked kit are filled, on the **Build orders** page: **Build at the pack station** (the default, as before), **Ship built kits first** (ships kits built ahead when there are enough for the whole line, and otherwise the kit is built at the pack station) or **Ship built kits only** (ships only kits built ahead, and the order waits for stock until more are built). The account owner or an Admin changes it, and a change applies to orders that arrive after it.

## Subscription boxes

A **subscription box** is a kit with **cycles**: the box's contents for a run of days. Each order takes the cycle running on the day it arrives, so a monthly box can change its contents every month while the client keeps sending orders for the same SKU.

On the kit, choose **Subscription cycles**, then **Add cycle**:

- **Name** (up to 64 characters).
- **First day** and **Last day**. Leave the last day empty to keep it running. Cycles of one box cannot overlap.
- **Expected boxes** (optional): used to plan the build.
- **Contents of one box**: a **Product SKU** and **Quantity** for each item.

Each cycle shows **Upcoming**, **Running** or **Ended**, with its open and shipped orders. **Build ahead** shows the boxes still to send in each cycle: the larger of the open orders and the expected boxes not yet shipped.

Only a cycle no order has used can be deleted. To stop a cycle that orders already use, change its last day.

