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

# Inventory

> Keep everything your team could sell in one place, then list it when it is ready.

**Inventory** holds your team's **assets**: the codebases, Raw data, and tasks you could sell,
each with its own description, domain, and asking price. An inventory asset exists independently
of any listing. You [list it for sale](/sell/listings/create-a-listing#from-inventory) when it is
ready, and one asset can sit in several listings. Codebases and Raw data can be listed from
Inventory; list tasksets from **Listings**; other kinds cannot be listed from Inventory yet.

<Note>
  Inventory is rolling out workspace by workspace. If **Inventory** is not in your sidebar, create
  listings from [Listings](/sell/listings/create-a-listing#from-listings).
</Note>

Some assets belong to a kind that no longer takes new assets: Harbor tasksets, and the HUD
environments and tasksets DataVendor carried over into Inventory from your listings. You can view,
group, or delete them, but not edit them, and listings that already carry them keep selling.

## Asset stages

DataVendor sets each asset's stage from what it holds. You never set a stage yourself.

| Stage | Meaning |
| - | - |
| **Incomplete** | Some details are missing, such as the description, a domain, the asking price, or codebase metadata. Hover the marker to see which; click it to open the asset's edit page on the first missing detail, in a new tab. |
| **Proposed** | The details are filled in, but no data is linked yet. |
| **Complete** | Every detail is filled in and the data is linked. Ready to list for sale. |

An asset is **Proposed** when you [register it without its code](/sell/inventory/add-assets#add-in-bulk-via-api).
That tells DataVendor what you could supply if a buyer appears. Proposed assets stay between your
team and DataVendor; they never appear in the catalog.

## Complete an asset

On an incomplete asset's page, choose **Complete asset** to open its edit page at the first
missing field. Save your changes with **Save changes** or ⌘S.

To link data to a codebase that has none, choose **Link data**. It opens **Add in bulk via API** on
**Step 2: Link data**; copy the snippet into a coding agent. It attaches a repository from GitHub,
GitLab, or Bitbucket, or a ZIP. Once the data is
linked, DataVendor measures it and fills in the repository metrics it can read. If you would
rather not use an agent, [import the repository from a forge](/sell/inventory/add-assets#codebases)
as a new asset instead.

## Groups

Groups organize your inventory. A group can hold assets of different kinds. Create one with
**New group**, or select assets and choose **Group** to move them into an existing or new group.
Assets not in a named group appear under **Ungrouped**. Deleting a group keeps its assets and moves
them to Ungrouped.

## Next

[Add assets](/sell/inventory/add-assets) to fill your inventory.


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