Status 409
A shipment issue is already under way
shipment_in_progress
When it happens
A shipment issue for the order is already queued or running, or the shipment is being cancelled.
What to do
Wait for the order.updated event: the outcome will be in shipment or shipment_attempt.
Can’t find the answer, or the error keeps coming back? Write to us and quote the X-Request-Id from the response so we can find the request. Contact us
Endpoints that return it
- post
/orders/{order}/shipmentIssue the order's shipment with its carrier: the request runs in the background, the outcome shows in the order and arrives with order.updated - post
/orders/{order}/shipment/trackingWrite the tracking number of a delivery service without integration: number, link and service name - post
/orders/{order}/shipment/tracking/clearRemove a manually written tracking number
Response body
application/problem+json · ConflictProblem
typestringrequiredMachine type of the problem: a stable code to branch on, such as insufficient_scope. Every type has a page in the error catalog.
titlestringrequiredShort summary of the problem in the language of the request.
statusintegerrequiredHTTP status of the response.
detailstringExplanation of this occurrence in the language of the request.
currentobjectThe record as it is now, the fields the conflict is about: on_hand for stock_on_hand_changed, status for rejected order changes, status and order_id for a closed draft.
external_idstringFor external_id_in_use and external_id_archived — the taken external ID.
consent_kindstringFor consent_required — the kind of consequence to agree to.
consequencesmap of integerFor consent_required — what will change: kind of data → number of records.
- Minimum:
- 0
consent_tokenstringFor consent_required — fingerprint of the shown consequences. Repeat the request with consent[<consent_kind>]=<consent_token>.
variant_idintegerFor consent_required of a variant line in a product write — the variant: the consent is given by changing that variant (PATCH /v1/variants/{variant}).
limitintegerFor plan_limit_reached, address_book_full, bulk_operation_queue_full and webhook_endpoint_limit_reached — the limit.
- Minimum:
- 0
fieldstringFor customer_contact_in_use — the contact that belongs to another customer: phone or email.
- Values:
phoneemail
existing_customer_idintegerFor customer_contact_in_use — the customer the contact belongs to.
receivedintegerFor upload_offset_mismatch — bytes the upload has received: the offset to continue from.
- Minimum:
- 0
operation_statusstringFor bulk_operation_finished — the status the operation finished with.