Skip to main content
PATCH
Error

Authorizations

Authorization
string
header
required

Prefix the value with "ApiKey" to indicate the custom authorization type

Path Parameters

inventoryOrderId
string<uuid>
required

Body

application/json

Request body for modifying an inventory order. All five top-level fields are optional. Omit a field to leave it unchanged. Behaviour depends on the order's current status:

  • SUBMITTED: all five fields are writable.
  • PROCESSING or SHIPPED: only customerPoNumber may be present in the body. Sending any other field (even with a value equal to the current one) returns 409 Conflict.
  • Any other status (ORDERED, RECEIVED, PARTIALLY_RECEIVED, COMPLETE, CANCELLED): the endpoint returns 409 Conflict.

Sending {} (no fields) returns 400 Bad Request. Items semantics: if items is omitted entirely, the existing lines are left unchanged. If items is sent as [], the request is rejected (an order must have at least one active line). Per entry: omit id to add a new line; include id (with any subset of other fields) to update — server prefills skuId, pricingId, discountedPrice, warrantyPricingId, and type from the existing row. Send {"id": "...", "delete": true} to cancel a specific line. Existing lines whose id is not mentioned are left alone.

warehouseId
object
required

New warehouse for the order. Writable only when status is SUBMITTED.

regionId
object
required

New region. Writable only when status is SUBMITTED.

customerPoNumber
object
required

Customer PO number. Writable when status is SUBMITTED, PROCESSING, or SHIPPED. Send an explicit JSON null to clear the existing value; omit the key to leave it unchanged.

billingType
object
required

Billing type. Writable only when status is SUBMITTED.

items
object[]

Optional list of item changes. Omit the key to leave items unchanged. Sending an empty array returns 409 (orders must keep at least one active line).

Response

Inventory order updated

Inventory order information

id
string<uuid>
required

Order ID

Example:

"123E4567-E89B-12D3-A456-426614174000"

status
enum<string>
required

Order status

Available options:
CANCELLED,
COMPLETE,
ORDERED,
PARTIALLY_RECEIVED,
PROCESSING,
RECEIVED,
SHIPPED,
SUBMITTED
Example:

"PROCESSING"

warehouse
object
required

Warehouse information

reason
enum<string>
required

Order reason

Available options:
ONE_OFF,
RESTOCK
Example:

"ONE_OFF"

inventoryOrderItems
object[]
required

Inventory order items

inventoryOrderShipments
object[]
required

Inventory order shipments

friendlyOrderId
string

Human-readable friendly order ID (order number shown to customers). Null for orders created before this field was populated.

Example:

"ORD-000123"

customerPoNumber
string

Customer PO number

Example:

"PO-12345"

billingType
enum<string>

Billing type

Available options:
SUBSCRIPTION,
PURCHASED
Example:

"SUBSCRIPTION"

submittedBy
object

Person who submitted the order

createdAt
string<date-time>

UTC ISO-8601 timestamp when the inventory order was created.

Example:

"2026-02-26T14:15:22.123Z"

updatedAt
string<date-time>

UTC ISO-8601 timestamp when the inventory order was last updated.

Example:

"2026-03-15T09:00:00.000Z"

expectedShipDate
string<date>

Date by which the inventory order is expected to ship (calendar date, no time component).

Example:

"2026-03-10"