Error 422 when trying to create a fulfillment, only supported action is cancel_fulfillment_order

Payments + Shipping & Fulfilment
, ,

Topic summary

Issue: Creating a fulfillment via API returns 422 Unprocessable Entity, despite the order appearing in the app’s assigned fulfillment orders. The related fulfillment order lists only one supported action—cancel_fulfillment_order—so a fulfillment cannot be created.

Details: The reporter states they have the required permissions (merchant_managed_fulfillment_orders and third_party_fulfillment_orders). An example X-Request-ID (53b27d73-df28-4634-9937-d3338da23605) was shared for traceability.

Impact: Blocks fulfillment creation through the current integration, implying the fulfillment order’s state or capabilities do not allow creation beyond cancellation.

Community input: Another participant confirms the same error and asks whether a solution was found.

Status: No resolution or workaround provided yet. Cause remains unclear; thread is open with a request for guidance on enabling fulfillment creation when only cancel_fulfillment_order is supported.

Summarized with AI on December 19. AI used: gpt-5.
1

Hi,

We are trying to create an order fulfillment and are receiving the following error: 422 Unprocessable Entity - Cannot create fulfillment for the fulfillment order.

The order is in our list of assigned fulfillment orders.

When we look at the assigned fulfillment order for that order we find that the only supported action is cancel_fulfillment_order. An example X-Request-ID: 53b27d73-df28-4634-9937-d3338da23605.

We have the required permissions according to the documentation (merchant_managed_fulfillment_orders and third_party_fulfillment_orders)

Thanks

2 Likes
2

Hi, chief_hopify

We are encountering the same issue. Have you managed to solve this problem? If so, what was the issue?

Kind regards,
Nebojsa

1 Like