ShipDeliveryNoteCommandRequestInput
Marks every package of a delivery note that has no shipping date as shipped. When the last open package of the delivery note is shipped, the delivery note counts as shipped and its shipping is completed: the shipment is reported to the sales channel of the order, the shipping confirmation mail is sent if the shipping method and the settings ask for it and it was not sent yet, open drop-shipping and fulfillment orders of the delivery note are closed, and the workflow event ‘delivery note shipped’ fires. A refused action reports ‘errorCode’ (the main reason) and ‘blockers’ (all reasons, each with ‘code’ and ‘message’). errorCode is one of: DELIVERY_NOTE_NOT_FOUND (the delivery note was not found); DELIVERY_NOTE_ALREADY_SHIPPED (every package already has a shipping date); SHIPPING_DATE_OUT_OF_RANGE (the shipping date is outside the supported range); DELIVERY_NOTE_HANDLED_BY_FULFILLMENT_NETWORK (the delivery note is handled by the JTL Fulfillment Network and cannot be changed here). - Request
ShipDeliveryNoteCommandRequestInputFields
The ID of the delivery note.
The shipping date. Defaults to now.
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?