> 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/interfaces/withmovement.md).

# WithMovement

Interface for entities that support inventory movements

Audience: Programmer

The `WithMovement` interface is implemented by entities that can participate in inventory movements, enabling tracking of stock transfers and changes.

## Fields

| Field             | Type                 | Description                             |
| ----------------- | -------------------- | --------------------------------------- |
| `movements`       | `[Movement!]`        | List of associated movements            |
| `canMove`         | `Boolean!`           | Whether movements are currently allowed |
| `movementHistory` | `MovementConnection` | Paginated movement history              |

## Movement Types

Entities implementing WithMovement support:

* **Item Movements** - Individual item transfers
* **Collection Movements** - Batch transfers
* **Repository Movements** - Location-to-location transfers

## Implementing Types

* InventoryItem
* InventoryCollection
* Repository
* PickingOrderItem
* ReceivingInboundItem

## Usage

```graphql
query {
  inventoryItem(id: "123") {
    ... on WithMovement {
      canMove
      movements {
        id
        quantity
        fromRepository {
          code
        }
        toRepository {
          code
        }
        executedAt
      }
    }
  }
}
```

## Movement Lifecycle

1. **Created** - Movement planned
2. **Validated** - Business rules checked
3. **Executed** - Stock transferred
4. **Completed** - Movement finalized

## Validation Rules

Movements are validated for:

* Sufficient stock availability
* Repository permissions
* Business rule constraints
* Workflow approvals

## Best Practices

1. Check `canMove` before creating movements
2. Use transactions for multi-item movements
3. Track movement reasons with metadata
4. Implement audit trails
5. Consider movement reversals

## See Also

* [ItemMovement Type](/graphql-api/types/itemmovement.md) - Individual movements
* [CollectionMovement Type](/graphql-api/types/collectionmovement.md) - Batch movements
* [RepositoryMovement Type](/graphql-api/types/repositorymovement.md) - Location transfers


---

# 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/interfaces/withmovement.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.