> For the complete documentation index, see [llms.txt](https://docs.pyck.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pyck.cloud/graphql-api/queries/inventoryitemsets.md).

# Inventory Item Sets

Inventory Item Sets Query

Returns a paginated list of InventoryItemSet objects, with optional filtering and ordering. Item sets allow grouping multiple inventory items together for collective operations.

## Arguments

| Name      | Type                         | Description                                                            |
| --------- | ---------------------------- | ---------------------------------------------------------------------- |
| `after`   | `Cursor`                     | Returns the elements in the list that come after the specified cursor  |
| `first`   | `Int`                        | Returns the first *n* elements from the list                           |
| `before`  | `Cursor`                     | Returns the elements in the list that come before the specified cursor |
| `last`    | `Int`                        | Returns the last *n* elements from the list                            |
| `orderBy` | `InventoryItemSetOrder`      | Ordering options for item sets returned from the connection            |
| `where`   | `InventoryItemSetWhereInput` | Filtering options for item sets returned from the connection           |

## Return Type

`InventoryItemSetConnection!` - A connection to a list of InventoryItemSet objects with pagination information.

## Notes

The `data` field contains custom item set attributes as JSON. You can use the `Data`, `DataHasKey`, `DataIn`, and `DataContains` filters to query based on JSON content. For complex JSON field queries, see [Advanced JSON Field Queries](https://github.com/pyck-ai/docs/blob/main/graphql/advanced/json-field-queries.md).

## Usage Example

```graphql
query {
  # Search item sets by SKU
  inventoryItemSets(
    where: {
      skuContains: "BUNDLE"
    },
    orderBy: { direction: DESC, field: CREATED_AT }
  ) {
    edges {
      node {
        id
        sku
        dataTypeSlug
        data
        createdAt
        items {
          id
          sku
          data
        }
      }
      cursor
    }
    totalCount
  }
}
```

```graphql
query {
  # Get item sets with specific data type
  inventoryItemSets(
    where: {
      dataTypeSlug: "product_bundle"
    },
    first: 20
  ) {
    edges {
      node {
        id
        sku
        dataTypeSlug
        data
        items {
          id
          sku
          inventoryJSONData
        }
      }
    }
    pageInfo {
      hasNextPage
      hasPreviousPage
      startCursor
      endCursor
    }
  }
}
```

```graphql
query {
  # Get item sets that contain specific items
  inventoryItemSets(
    where: {
      hasItemsWith: [
        { skuContains: "COMP-001" }
      ]
    }
  ) {
    edges {
      node {
        id
        sku
        items {
          id
          sku
        }
      }
    }
  }
}
```

## Common Filters

* `skuContains` - Search by item set SKU substring
* `sku` - Find by exact item set SKU
* `dataTypeSlug` - Filter by data type slug
* `hasItems` - Filter item sets that have items
* `hasItemsWith` - Filter by criteria on contained items
* `createdAtGTE` / `createdAtLTE` - Filter by creation date range

## Notes

* Item sets represent grouped collections of inventory items
* Useful for managing product bundles, kits, or component sets
* Each item set has its own SKU for identification and tracking
* Support custom fields through data/dataType system
* Items in a set can be managed collectively for operations
* Enable complex inventory relationships and hierarchies


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pyck.cloud/graphql-api/queries/inventoryitemsets.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.