commerce

Mark an order fulfilled

Mark a paid order handed over (or undo it): the call a warehouse or fulfilment system makes when goods leave.

A malformed UUID answers 400 validation_failed before resource access; a well-formed unknown UUID or one outside your workspace answers 404.

Only a paid order can be marked fulfilled; fulfilled: false undoes a mistaken hand-over.

Marking fulfilled emits the commerce.order.fulfilled webhook event once in the order's life.

Marking an order that is already fulfilled answers 200 with its first fulfilled_at and already_fulfilled: true, and sends nothing again: no second webhook, email or automation. Retrying the call is safe.

Marking an order again after fulfilled: false records the new fulfilled_at and announces nothing: the customer already heard it shipped. A mark that loses to a concurrent undo answers 409 conflict.

Courier bookings through The Courier Guy mark the order fulfilled themselves. A courier booked for an order already marked fulfilled only sends the buyer the tracking number.

patch/api/v1/commerce/orders/{id}/fulfilment

Request

  • Base URL: https://app.blueticked.com
  • URL: https://app.blueticked.com/api/v1/commerce/orders/{id}/fulfilment
  • Auth: HTTP bearer

Path parameters

idstring required

The resource's unique identifier.

Request body

fulfilledboolean required

Example request

{
  "fulfilled": true
}

Response

Success

okboolean required
fulfilled_atstring date-time nullable required
already_fulfilledboolean required

Example response

{
  "ok": true,
  "fulfilled_at": "2026-08-03T11:30:00.000Z"
}

Changes

No recorded changes to this operation across all 1 revision of this API.