> ## Documentation Index
> Fetch the complete documentation index at: https://docs.soundchecklive.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Stock, units and kits

> Where your gear lives and how it's counted: stock locations, serialized units with serials and asset tags, and kits (cases and bundles) with their contents and accessories.

A simple inventory is a name and a count. As you grow, you need more: gear in two warehouses, wireless packs you track by serial, and road cases that always travel full. This page covers those three tools.

![Locations tab of Inventory with the default warehouse and a second stock location](https://mintcdn.com/soundchecklive/e-SmuOY4KzOPmXhu/images/gear/locations-light.png?fit=max\&auto=format\&n=e-SmuOY4KzOPmXhu\&q=85\&s=a3c7e978bd83d0241d418282e36feaf7)

## Stock locations

A stock location is a place gear lives: a warehouse, a shop, a truck.

### Add a location

1. Open **Show prep → Inventory** and choose the **Locations** tab, next to **Items** and **Availability**.
2. Add the location. The address field suggests places as you type.
3. Mark one location as the default. New bookings ship from it.

Like the **Availability** tab, **Locations** shows only for people who can manage gigs.

### Archive or restore a location

Archiving a location hides it from pickers and keeps its history. Archived locations are listed under **Archived**, where you can restore them. A location that was never used is removed instead.

### Split stock between locations

On a bulk item, **Stock by location** splits the total between locations. Anything left over shows as **Unallocated**. Filter the items list by **Location** to see what each one holds.

### Where a booking ships from

Each booking on a gig names a **Ships from** location. The default is preselected when you add it. The gig row shows "Ships from" and the location, "No ship-from location" when there's none, or "Ships from an archived location" after the location was archived. If a location holds fewer than the line asks for, the add form warns you, for example "Main warehouse holds 4. This line asks for 6."

When you **Return** a booking from the item record, you choose where it lands, and the stock moves to that location. There's no separate transfer between locations. To move stock that isn't booked, change the item's **Stock by location** split.

## Serialized units

Set **Tracking** to **Serialized (one row per unit)** for gear you track piece by piece, such as wireless packs, in-ear packs or laptops.

* The item's **Units** section lists every unit with its serial, asset tag, status and location.
* Add one unit, or add several at once with an optional serial prefix (`SM58-001`, `SM58-002`, …).
* The item quantity follows its units. Units marked retired or lost drop out of the count.
* Units in maintenance can't be booked.

You can add up to 500 units at once. A serial must be unique within its item, and an asset tag unique across your organization. A unit on an open booking is locked in the grid. A unit's condition and notes can't be edited on the web.

On a booking for a serialized item, **Pick** chooses which units go out, up to the booked quantity. A unit can't be on two overlapping bookings. The pack sheet then lists the picked units, by serial, or by asset tag for a unit with no serial.

> [!TIP]
>
> Track by serial only what you need to find by serial. Cables, gaffer tape and stands are fine as **Bulk (count only)**. Serialized items are more work to keep current.

## Kits, cases, and accessories

A kit is an item that carries other items. Set **Kit type** on the item:

| Kit type | Use it for | Stock |
| - | - | - |
| **Case (holds its contents)** | A road case that always travels full | The case is a real thing you own |
| **Bundle (no stock of its own)** | A set you always book together, such as a "Ceremony kit" | Only its contents have stock |
| **Not a kit** | Everything else | Its own count |

![A case kit opened from the items list with its contents, stock and upcoming bookings](https://mintcdn.com/soundchecklive/e-SmuOY4KzOPmXhu/images/gear/kit-light.png?fit=max\&auto=format\&n=e-SmuOY4KzOPmXhu\&q=85\&s=6299bf8c8f033423993fbffb04667781)

In the item's **Contents and accessories** section, add the items inside the kit and how many of each per kit. An item that isn't a kit has an **Accessories** section instead, for extras that usually go with it.

* Booking a kit books its contents with it. Contents can't be removed on their own. Change the kit booking instead.
* Accessories are offered as checkboxes when you add the kit to a gig, under **Add accessories**, each shown as "N× name per kit".
* A kit can't contain another kit.

On the gig, kits show their contents nested under them as "N× name", each with its own **Short** badge. On a pack sheet, a kit's contents can't be ticked on their own. Tick the kit's line.

### Worked example: one bundle for every wedding

You send the same ceremony setup to every wedding: 2 wireless mics, 1 small speaker, 1 mixer, 2 stands.

1. Choose **Add item**. Name it *Ceremony kit*, and set **Kit type** to **Bundle (no stock of its own)**.
2. In **Contents and accessories**, add the four items with their counts.
3. On each wedding's **Inventory** tab, add one *Ceremony kit*.

Each wedding now books all four items in one line. If two weddings on the same day both want the kit and you own only two wireless mics, the second one shows **Short** on the mics.

> [!NOTE]
>
> Inventory doesn't copy with a gig made in the web app. Duplicates, template copies and repeated dates start as drafts with no inventory; only their outside gear copies. A bundle is the fastest way to put the same gear on each new gig. **Add a pack** is different: it adds a starter pack of common gear to your inventory, then books it.

## Related

> [card] [Availability and shortages](https://docs.soundchecklive.io/features/gigs/gear/availability.md)
>
> How kits, units and locations affect what's free.

> [card] [Packing out and back in](https://docs.soundchecklive.io/features/gigs/gear/packing.md)
>
> Pack sheets, ticking kits, and returning stock.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.