Shopify fulfillment webhook events
Shopify sends 26 fulfillment events. Most follow a fulfillment order, from fulfillment_orders/fulfillment_request_submitted to fulfillment_orders/cancelled, and fulfillments/create and fulfillments/update follow the fulfillment itself.
Every event here can also reach agents as an MCP event through Hookdeck: MCP events →
fulfillment_events/create
documented from Shopify docs (example)
fulfillment_events/create New fulfillment event created
Identified by x-shopify-topic header
Resource fulfillment
{
"id": 1234567,
"fulfillment_id": 123456,
"status": "in_transit",
"message": "Item is now in transit",
"happened_at": "2021-12-31T19:00:00-05:00",
"city": null,
"province": null,
"country": "CA",
"zip": null,
"address1": null,
"latitude": null
} Key fields
| Field | Type | Example |
|---|---|---|
id | integer | 1234567 |
status | string | in_transit |
happened_at | string | 2021-12-31T19:00:00-05:00 |
Full schema: 18 fields.
From Shopify docs
-
Content type
application/json
fulfillment_events/delete
documented from Shopify docs (example)
fulfillment_events/delete Fulfillment event is deleted
Identified by x-shopify-topic header
Resource fulfillment
{
"id": 1234567,
"fulfillment_id": 123456,
"status": "in_transit",
"message": "Item is now in transit",
"happened_at": "2021-12-31T19:00:00-05:00",
"city": null,
"province": null,
"country": "CA",
"zip": null,
"address1": null,
"latitude": null
} Key fields
| Field | Type | Example |
|---|---|---|
id | integer | 1234567 |
status | string | in_transit |
happened_at | string | 2021-12-31T19:00:00-05:00 |
Full schema: 18 fields.
From Shopify docs
-
Content type
application/json
fulfillment_holds/added
documented from Shopify docs (example)
fulfillment_holds/added Hold added to a fulfillment order, once per hold
Identified by x-shopify-topic header
Resource fulfillment
{
"fulfillment_order": { … },
"fulfillment_hold": { … }
} From Shopify docs
-
Content type
application/json
fulfillment_holds/released
documented from Shopify docs (example)
fulfillment_holds/released Hold released from a fulfillment order, once per hold
Identified by x-shopify-topic header
Resource fulfillment
{
"fulfillment_order": { … },
"fulfillment_hold": { … }
} From Shopify docs
-
Content type
application/json
fulfillment_orders/cancellation_request_accepted
documented from Shopify docs (example)
fulfillment_orders/cancellation_request_accepted 3PL accepts a merchant's fulfillment cancellation request
Identified by x-shopify-topic header
Resource fulfillment
{
"fulfillment_order": { … },
"message": "Order has not been shipped yet."
} From Shopify docs
-
Content type
application/json
fulfillment_orders/cancellation_request_rejected
documented from Shopify docs (example)
fulfillment_orders/cancellation_request_rejected 3PL rejects a merchant's fulfillment cancellation request
Identified by x-shopify-topic header
Resource fulfillment
{
"fulfillment_order": { … },
"message": "Order has already been shipped."
} From Shopify docs
-
Content type
application/json
fulfillment_orders/cancellation_request_submitted
documented from Shopify docs (example)
fulfillment_orders/cancellation_request_submitted Merchant asks to cancel an approved fulfillment request
Identified by x-shopify-topic header
Resource fulfillment
{
"fulfillment_order": { … },
"fulfillment_order_merchant_request": { … }
} From Shopify docs
-
Content type
application/json
fulfillment_orders/cancelled
documented from Shopify docs (example)
fulfillment_orders/cancelled Fulfillment order is cancelled
Identified by x-shopify-topic header
Resource fulfillment
{
"fulfillment_order": { … },
"replacement_fulfillment_order": { … }
} From Shopify docs
-
Content type
application/json
fulfillment_orders/fulfillment_request_accepted
documented from Shopify docs (example)
fulfillment_orders/fulfillment_request_accepted Fulfillment service accepts a fulfillment request
Identified by x-shopify-topic header
Resource fulfillment
{
"fulfillment_order": { … },
"message": "We will ship the item tomorrow."
} From Shopify docs
-
Content type
application/json
fulfillment_orders/fulfillment_request_rejected
documented from Shopify docs (example)
fulfillment_orders/fulfillment_request_rejected 3PL rejects a merchant's fulfillment request
Identified by x-shopify-topic header
Resource fulfillment
{
"fulfillment_order": { … },
"message": "Can't fulfill due to no inventory on product."
} From Shopify docs
-
Content type
application/json
fulfillment_orders/fulfillment_request_submitted
documented from Shopify docs (example)
fulfillment_orders/fulfillment_request_submitted Merchant sends a 3PL a fulfillment request
Identified by x-shopify-topic header
Resource fulfillment
{
"original_fulfillment_order": { … },
"submitted_fulfillment_order": { … },
"fulfillment_order_merchant_request": { … }
} From Shopify docs
-
Content type
application/json
fulfillment_orders/fulfillment_service_failed_to_complete
documented from Shopify docs (example)
fulfillment_orders/fulfillment_service_failed_to_complete Fulfillment service intends to close an in-progress fulfillment order
Identified by x-shopify-topic header
Resource fulfillment
{
"fulfillment_order": { … },
"message": "We broke the last item."
} From Shopify docs
-
Content type
application/json
fulfillment_orders/hold_released
documented from Shopify docs (example)
fulfillment_orders/hold_released Last hold released, taking the fulfillment order off hold
Identified by x-shopify-topic header
Resource fulfillment
{
"fulfillment_order": {
"id": "gid://shopify/FulfillmentOrder/1",
"status": "open"
}
} Key fields
| Field | Type | Example |
|---|---|---|
fulfillment_order.id | string | gid://shopify/FulfillmentOrder/1 |
fulfillment_order.status | string | open |
Full schema: 3 fields.
From Shopify docs
-
Content type
application/json
fulfillment_orders/line_items_prepared_for_local_delivery
documented from Shopify docs (example)
fulfillment_orders/line_items_prepared_for_local_delivery Line items prepared for local delivery
Identified by x-shopify-topic header
Resource fulfillment
{
"fulfillment_order": {
"id": "gid://shopify/FulfillmentOrder/1",
"status": "open",
"preparable": true,
"delivery_method": { … }
}
} Key fields
| Field | Type | Example |
|---|---|---|
fulfillment_order.id | string | gid://shopify/FulfillmentOrder/1 |
fulfillment_order.status | string | open |
Full schema: 6 fields.
From Shopify docs
-
Content type
application/json
fulfillment_orders/line_items_prepared_for_pickup
documented from Shopify docs (example)
fulfillment_orders/line_items_prepared_for_pickup Line items prepared for pickup
Identified by x-shopify-topic header
Resource fulfillment
{
"fulfillment_order": {
"id": "gid://shopify/FulfillmentOrder/1",
"status": "open",
"preparable": true,
"delivery_method": { … }
}
} Key fields
| Field | Type | Example |
|---|---|---|
fulfillment_order.id | string | gid://shopify/FulfillmentOrder/1 |
fulfillment_order.status | string | open |
Full schema: 6 fields.
From Shopify docs
-
Content type
application/json
fulfillment_orders/manually_reported_progress_stopped
documented from Shopify docs (example)
fulfillment_orders/manually_reported_progress_stopped Manually in-progress fulfillment order marked back as open
Identified by x-shopify-topic header
Resource fulfillment
{
"fulfillment_order": { … },
"progress_stopped_by_app": { … },
"progress_stopped_by_user": { … }
} From Shopify docs
-
Content type
application/json
fulfillment_orders/merged
documented from Shopify docs (example)
fulfillment_orders/merged Several fulfillment orders merged into one
Identified by x-shopify-topic header
Resource fulfillment
{
"merge_intents": [ … ],
"fulfillment_order_merges": { … }
} From Shopify docs
-
Content type
application/json
fulfillment_orders/moved
documented from Shopify docs (example)
fulfillment_orders/moved Line items reassigned to a different fulfillment location
Identified by x-shopify-topic header
Resource fulfillment
{
"original_fulfillment_order": { … },
"moved_fulfillment_order": { … },
"destination_location_id": "gid://shopify/Location/1"
} From Shopify docs
-
Content type
application/json
fulfillment_orders/order_routing_complete
documented from Shopify docs (example)
fulfillment_orders/order_routing_complete Order routing finishes and fulfillment orders are assigned
Identified by x-shopify-topic header
Resource fulfillment
{
"fulfillment_order": {
"id": "gid://shopify/FulfillmentOrder/1",
"status": "open"
}
} Key fields
| Field | Type | Example |
|---|---|---|
fulfillment_order.id | string | gid://shopify/FulfillmentOrder/1 |
fulfillment_order.status | string | open |
Full schema: 3 fields.
From Shopify docs
-
Content type
application/json
fulfillment_orders/placed_on_hold
documented from Shopify docs (example)
fulfillment_orders/placed_on_hold Fulfillment order moves to ON_HOLD, on its first hold
Identified by x-shopify-topic header
Resource fulfillment
{
"fulfillment_order": {
"id": "gid://shopify/FulfillmentOrder/1",
"status": "open",
"fulfillment_holds": [ … ]
}
} Key fields
| Field | Type | Example |
|---|---|---|
fulfillment_order.id | string | gid://shopify/FulfillmentOrder/1 |
fulfillment_order.status | string | open |
Full schema: 27 fields.
From Shopify docs
-
Content type
application/json
fulfillment_orders/progress_reported
documented from Shopify docs (example)
fulfillment_orders/progress_reported Progress reported on a fulfillment order
Identified by x-shopify-topic header
Resource fulfillment
{
"fulfillment_order": { … },
"progress_report": { … },
"initial_status": "open"
} From Shopify docs
-
Content type
application/json
fulfillment_orders/rescheduled
documented from Shopify docs (example)
fulfillment_orders/rescheduled Fulfillment order is rescheduled and may merge with others
Identified by x-shopify-topic header
Resource fulfillment
{
"fulfillment_order": {
"id": "gid://shopify/FulfillmentOrder/1",
"status": "scheduled",
"fulfill_at": "2023-02-20T20:32:22-05:00"
}
} Key fields
| Field | Type | Example |
|---|---|---|
fulfillment_order.id | string | gid://shopify/FulfillmentOrder/1 |
fulfillment_order.status | string | scheduled |
fulfillment_order.fulfill_at | string | 2023-02-20T20:32:22-05:00 |
Full schema: 4 fields.
From Shopify docs
-
Content type
application/json
fulfillment_orders/scheduled_fulfillment_order_ready
documented from Shopify docs (example)
fulfillment_orders/scheduled_fulfillment_order_ready Scheduled fulfillment order becomes due
Identified by x-shopify-topic header
Resource fulfillment
{
"fulfillment_order": {
"id": "gid://shopify/FulfillmentOrder/1",
"status": "open"
}
} Key fields
| Field | Type | Example |
|---|---|---|
fulfillment_order.id | string | gid://shopify/FulfillmentOrder/1 |
fulfillment_order.status | string | open |
Full schema: 3 fields.
From Shopify docs
-
Content type
application/json
fulfillment_orders/split
documented from Shopify docs (example)
fulfillment_orders/split Fulfillment order split into several
Identified by x-shopify-topic header
Resource fulfillment
{
"split_line_items": [ … ],
"fulfillment_order": { … },
"remaining_fulfillment_order": { … },
"replacement_fulfillment_order": { … }
} From Shopify docs
-
Content type
application/json
fulfillments/create
documented from Shopify docs (example)
fulfillments/create New fulfillment created
Identified by x-shopify-topic header
Resource fulfillment
{
"id": 123456,
"order_id": 820982911946154500,
"status": "pending",
"created_at": "2023-02-20T20:31:11-05:00",
"service": null,
"updated_at": "2023-02-20T20:31:11-05:00",
"tracking_company": "UPS",
"shipment_status": null,
"location_id": null,
"origin_address": null,
"email": "jon@example.com"
} Key fields
| Field | Type | Example |
|---|---|---|
id | integer | 123456 |
status | string | pending |
created_at | string | 2023-02-20T20:31:11-05:00 |
Full schema: 77 fields.
From Shopify docs
-
Content type
application/json
fulfillments/update
documented from Shopify docs (example)
fulfillments/update Fulfillment details change
Identified by x-shopify-topic header
Resource fulfillment
{
"id": 123456,
"order_id": 820982911946154500,
"status": "pending",
"created_at": "2023-02-20T20:45:36-05:00",
"service": null,
"updated_at": "2023-02-20T20:45:36-05:00",
"tracking_company": "UPS",
"shipment_status": null,
"location_id": null,
"origin_address": null,
"email": "jon@example.com"
} Key fields
| Field | Type | Example |
|---|---|---|
id | integer | 123456 |
status | string | pending |
created_at | string | 2023-02-20T20:45:36-05:00 |
Full schema: 77 fields.
From Shopify docs
-
Content type
application/json
Route Shopify events by type.
Event Gateway receives every Shopify delivery and filters and routes it by event type, so each service gets only the events it handles.