> 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/types/collectionmovement.md).

# CollectionMovement

CollectionMovement Type

Represents a single movement operation within a collection of related inventory movements. CollectionMovement is used to track individual movement steps as part of larger, coordinated inventory operations.

## Fields

| Field          | Type      | Description                                  |
| -------------- | --------- | -------------------------------------------- |
| `id`           | `ID!`     | Unique identifier of the collection movement |
| `movementType` | `String!` | Type of movement operation being performed   |

## Usage Example

```graphql
query {
  createInventoryCollectionMovement(input: {
    dataTypeSlug: "bulk_transfer"
    data: {
      reason: "warehouse_relocation"
      priority: "high"
    }
    collection: [{
      handler: "item_transfer"
      fromID: "repo-uuid-1"
      toID: "repo-uuid-2"
      itemID: "item-uuid-1"
      quantity: 100
    }, {
      handler: "item_transfer"
      fromID: "repo-uuid-1"
      toID: "repo-uuid-2"
      itemID: "item-uuid-2"
      quantity: 50
    }]
  }) {
    inventoryCollection {
      id
      handler
      assignee
      assignmentDate
    }
    movements {
      id
      movementType
    }
    workflows {
      id
      status
    }
  }
}
```

## Mutation Examples

### Update Collection Movement

```graphql
mutation {
  updateCollectionMovement(input: {
    dataTypeSlug: "warehouse_transfer"
    data: {
      status: "in_progress"
      updated_by: "user-123"
    }
  }) {
    inventoryCollection {
      id
      data
      updatedAt
    }
    workflows {
      id
      status
    }
  }
}
```

## Movement Types

CollectionMovements support various movement types depending on the operation:

* **`item_transfer`**: Moving items between repositories
* **`repository_transfer`**: Moving entire repositories
* **`bulk_move`**: Moving multiple items in a single operation
* **`picking_operation`**: Movement as part of order picking
* **`receiving_operation`**: Movement during goods receiving
* **`adjustment`**: Inventory adjustments and corrections

## Relations

* **CollectionMovement** `N:1` **InventoryCollection**: Multiple movements belong to a single collection
* **CollectionMovement** references **ItemMovement** or **RepositoryMovement**: Individual movement operations
* **CollectionMovement** can be associated with **PickingOrder** or **ReceivingInbound**: Order-related movements

## Common Use Cases

* **Bulk Transfers**: Moving large quantities of items between warehouses
* **Order Fulfillment**: Coordinating multiple picking movements for a single order
* **Receiving Operations**: Processing incoming shipments with multiple items
* **Inventory Adjustments**: Making coordinated adjustments across multiple locations
* **Workflow Orchestration**: Managing complex multi-step inventory operations

## Best Practices

* Use descriptive movement types to clearly identify the purpose of each movement
* Group related movements into collections for better tracking and rollback capabilities
* Monitor movement status through associated workflows
* Consider transaction boundaries when processing collection movements
* Use appropriate handlers for different types of movement operations


---

# 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/types/collectionmovement.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.