> 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/enums/repositorytype.md).

# RepositoryType

RepositoryType Type

Enum defining whether a repository can be moved or is fixed in place.

## Values

| Value     | Description                                                               |
| --------- | ------------------------------------------------------------------------- |
| `dynamic` | Repository that can be moved (e.g., pallets, totes, trolleys, forklifts)  |
| `static`  | Repository that is fixed in place (e.g., warehouse, zones, shelves, bins) |

## Usage Example

```graphql
query {
  repositories(
    where: { type: static }
  ) {
    edges {
      node {
        id
        name
        type
        virtualRepo
      }
    }
  }
}
```

```graphql
mutation {
  createInventoryRepository(
    input: {
      name: "Main Warehouse"
      type: static
      virtualRepo: false
    }
  ) {
    inventoryRepository {
      id
      name
      type
    }
  }
}
```

## Notes

The actual type of repository (warehouse, shelf, bin, pallet, etc.) is determined by:

* The repository's name
* Its position in the hierarchy (parent-child relationships)
* Custom data fields via dataType

For example, a static repository at the root level might be a warehouse, while a dynamic repository might be a pallet or forklift.


---

# 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/enums/repositorytype.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.