CreatePurchaseOrderLineItemCommandRequestInput
Adds one article position to an existing purchase order. The order must be Open or Released — from InProgress onwards the position would already be part of a goods receipt. The article must already be assigned to the order’s supplier; this endpoint never creates that assignment. Fields the caller omits are resolved from the supplier’s master data, so the smallest useful request carries the article, the quantity, the net price and the VAT rate. - Request
CreatePurchaseOrderLineItemCommandRequestInputFields
ID of the purchase order the position is added to.
Indicates whether automatic workflows should be suppressed for this write. Defaults to false when omitted.
The article to order. It must already be assigned to the order's supplier; the API never auto-assigns. Kit articles, inactive articles and variation parents are rejected, exactly as on the create-order endpoint.
Ordered quantity; must be greater than zero.
Net purchase price per unit. Zero is allowed — it is the underlying column's own default — but a negative price is not.
VAT rate in percent, between 0 and 100 inclusive. A sanity bound only; specific rates are not whitelisted.
The supplier's own article number for this position. When omitted, resolved from the supplier's master data. A supplied value is used as given even when it differs from master data, because this is a free-text snapshot rather than a lookup key.
Expected delivery date of this position. When omitted, calculated from the article's (or, failing that, the supplier's) lead time in days, added to today.
Free-text note on the position, at most 2000 characters.
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?