mutation ConvertStockItemToStandardItem($request: ConvertStockItemToStandardItemCommandRequestInput!) {
ConvertStockItemToStandardItem(request: $request) {
itemId
stockWrittenOff
}
}{
"request": {
"itemId": "id"
}
}{
"data": {
"ConvertStockItemToStandardItem": {
"itemId": "id",
"stockWrittenOff": true
}
}
}ConvertStockItemToStandardItem
Converts a stock item back into a standard item, so that its stock is no longer managed in warehouses. The item keeps its ID and all other properties. Three settings are reset as part of the transition and converting back does not restore them: the per-warehouse minimum and maximum stock levels written through PATCH /v2/items//warehouse-constraints are cleared, allowNegativeStock is switched off, and includeSupplierStock is switched off on every supplier of the item. Use POST /v2/items//stock-items/convert for the opposite direction.
If a request with this mutation’s Idempotency-Key was already completed, the response’s extensions contains an idempotency.{responseName} entry with wasReplayed: true.
ConvertStockItemToStandardItem(request: ConvertStockItemToStandardItemCommandRequestInput!): ConvertStockItemToStandardItemCommandResponse!Arguments
Unique ID of the converted item. Unchanged - a standard item keeps the ID it had as a stock item.
Indicates whether physical warehouse stock was actually booked out as part of the conversion. True when the item held stock in a warehouse, false otherwise - which includes the case where writeOffExistingStock was true but the item held none, and the case where the item's only stock is a supplier's, because supplier stock is not booked out. The caller cannot derive this from the request alone.
mutation ConvertStockItemToStandardItem($request: ConvertStockItemToStandardItemCommandRequestInput!) {
ConvertStockItemToStandardItem(request: $request) {
itemId
stockWrittenOff
}
}{
"request": {
"itemId": "id"
}
}{
"data": {
"ConvertStockItemToStandardItem": {
"itemId": "id",
"stockWrittenOff": true
}
}
}Was this page helpful?