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
id
ID!
Unique identifier of the collection movement
movementType
String!
Type of movement operation being performed
Usage Example
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
Movement Types
CollectionMovements support various movement types depending on the operation:
item_transfer: Moving items between repositoriesrepository_transfer: Moving entire repositoriesbulk_move: Moving multiple items in a single operationpicking_operation: Movement as part of order pickingreceiving_operation: Movement during goods receivingadjustment: Inventory adjustments and corrections
Relations
CollectionMovement
N:1InventoryCollection: Multiple movements belong to a single collectionCollectionMovement 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
Last updated
Was this helpful?
