The fix: there is no listFulfillmentOrders module in Make.com's Shopify app. Call the REST endpoint directly with an HTTP module: GET /admin/api/2024-01/orders/{legacyResourceId}/fulfillment_orders.json — and use legacyResourceId (numeric), not the GID that searchOrders returns.

Symptom

You need fulfillment orders to fulfil a Shopify order from Make.com, but the Shopify app has no module for it, and passing the ID from searchOrders into other calls fails.

The two-ID trap

searchOrders returns a GraphQL GID in 1.id (like gid://shopify/Order/123). REST endpoints need the plain numeric 1.legacyResourceId. Meanwhile ActionCreateFulfillment is GraphQL and needs the GID form gid://shopify/FulfillmentOrder/{numeric_id} — construct it manually from the REST response.

Also required

Scopes: read_merchant_managed_fulfillment_orders and write_merchant_managed_fulfillment_orders on top of read_orders/write_fulfillments — write_fulfillments alone is not enough. And filter for fulfillment status open, or already-fulfilled orders throw unfulfillable status=closed.

How we hit it

A production order-fulfilment scenario for an e-commerce client after Shopify's 2026 auth changes (client-credentials grant, 24h tokens fetched fresh at scenario start).

Related landmines

All Make.com landmines

We build and maintain Make.com/Shopify integrations white-label. What we build →