Skip to main content
object

Requires read_assigned_fulfillment_orders access scope, read_merchant_managed_fulfillment_orders access scope, read_third_party_fulfillment_orders access scope or read_marketplace_fulfillment_orders access scope.

A fulfillment hold currently applied on a fulfillment order.

•String!
non-null

The localized reason for the fulfillment hold for display purposes.

•String

An identifier an app can use to reference one of many holds it applied to a fulfillment order. This field must be unique among the holds that a single app applies to a single fulfillment order.

•App

The app that created the fulfillment hold.

•Boolean!
non-null

A boolean value that indicates whether the requesting app created the fulfillment hold.

•ID!
non-null

A globally-unique ID.

•FulfillmentHoldReason!
non-null

The reason for the fulfillment hold.

•String

Additional information about the fulfillment hold reason.


Was this section helpful?

•mutation

Applies a fulfillment hold on a fulfillment order.

As of the 2025-01 API version, the mutation can be successfully executed on fulfillment orders that are already on hold. To place multiple holds on a fulfillment order, apps need to supply the handle field. Each app can place up to 10 active holds per fulfillment order. If an app attempts to place more than this, the mutation will return a user error indicating that the limit has been reached. The app would need to release one of its existing holds before being able to apply a new one.

Arguments

•FulfillmentOrderHoldInput!
required

The details of the fulfillment hold applied on the fulfillment order.

•ID!
required

The ID of the fulfillment order on which a fulfillment hold is applied.


Fields

•FulfillmentHold

The fulfillment hold created for the fulfillment order. Null if no hold was created.

•FulfillmentOrder

The fulfillment order on which a fulfillment hold was applied.

Anchor to remainingFulfillmentOrderremainingFulfillmentOrder
•FulfillmentOrder

The remaining fulfillment order containing the line items to which the hold wasn't applied, if specific line items were specified to be placed on hold.

•[FulfillmentOrderHoldUserError!]!
non-null

The list of errors that occurred from executing the mutation.


Was this section helpful?

•interface

Was this section helpful?
OSZAR »