ConvertItemToKitItemCommandRequestInput
Converts an existing standard item into a kit, so that selling one unit of it consumes a fixed set of component items from then on. The full component list is mandatory, because a standard item has no component list to fall back on - supplying at least one component is what makes the item a kit. The item keeps its ID, but the conversion resets several settings and converting back does not restore them: the suppliers are removed, because a kit has no suppliers; stock management is switched off first, which clears the per-warehouse minimum and maximum stock levels written through “PATCH /v2/items//warehouse-constraints” and switches “allowNegativeStock” off; and best-before dates, batches, serial-number tracking and divisible stock are switched off. The kit’s stock management is then derived from its components - it is stock-managed as soon as one component is - so read the item after the conversion to see the resulting settings. There is no direct reverse operation: removing the last component with “DELETE /v2/items//kit-items/components/” or “DeleteKitItemComponent” dissolves the kit and turns the item back into a standard item. Because an item that is itself a kit is never an eligible component, kits cannot be nested. Use “POST /v2/items//kit-items/components” or “AddKitItemComponent” to add a further component to a kit that already exists. - Request
ConvertItemToKitItemCommandRequestInputFields
Unique ID of the item that is converted into a kit.
The component items the kit consists of after the conversion. At least one component is required - it is what makes the item a kit. Components are stored in the order they are sent unless a component carries an explicit "position". The same component item may appear only once.
Client-supplied idempotency key. When provided, a repeated request with the same key and payload replays the original result instead of re-executing the mutation.
Was this page helpful?