CreateKitItemCommandRequestInput
Creates a new KitItem in one call. The request carries exactly the fields of this kind: mandatory ones, optional ones, and none of those the kind does not have. The item is valid right away: item number, name, at least one category and the mandatory fields of the kind are required. Everything else, such as prices, descriptions in further languages, suppliers and images, is added through its own sub-resource. - Request
CreateKitItemCommandRequestInputFields
Name of the item in the default language. Further languages and sales channel texts are the descriptions of the item.
The identifiers of the item. The item number (SKU) is mandatory and unique.
The IDs of the categories the new item is assigned to. At least one: every item that is not a combination of a variation parent has a category, and an item without one is not valid (an empty list is refused with 400). A combination takes over the categories of its parent and is created through the combinations of the parent, which have no such field. Further assignments are made through the categories of the item.
Whether the item is active. Defaults to true when omitted.
The ID of the product group.
The ID of the manufacturer.
The ID of the item condition, for example new or used.
The ID of the delivery status of the item (the master data of delivery statuses, for example "in stock" or "ships in 3 days").
The ID of the tax class. When omitted the item gets the company default. The value must reference an existing tax class.
The ID of the shipping class.
Outer dimensions as shipped.
Weights.
Customs information.
Sales unit and content with its base price.
The components of the kit. At least one. Later changes go through the components of the kit.
The characteristic values (German 'Merkmalwerte') assigned to the item. Omitted means none.
The attribute values of the item, per attribute, sales channel and language. Omitted means none. The attributes the system derives itself, such as those of a voucher, cannot be sent.
The custom field values of the item. Omitted means none. A custom field has to apply to the item, which depends on its product group.
The free-text variations of the item (German 'Freitext'), added in the same call. Every kind can have them. Omitted means none. Refused with 409 for an item of the fulfillment network.
The simple selection variations of the item with their values, added in the same call. Only the kinds that allow them have this field; the reasons that forbid them for a given item are in 409 SELECTION_VARIATION_NOT_ALLOWED_FOR_ITEM_TYPE. Omitted means none.
The sales channels the item is activated in, set in the same call. The item has to be in a category that is active in each of them. Omitted means none; the item is activated afterwards through its sales channels.
The prices of the item, created in the same call. Every part is the model of the matching prices route. Omitted means the item is created without prices and they are set through those routes.
Suppresses the automatic workflow triggers of this call. Defaults to false when omitted.
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?