Yes there are absolutely work arounds, including using the GraphQL version of this same object instead of REST (which is what I did). My point is that every other part of the new FulfillmentOrders API uses SKUs, not product IDs. Thus the REST endpoin...

Yeah, but with the new system you have to accept a FulfillmentOrder before you can create a Fulfillment. This is why it's a problem. It's going to be a problem for everyone using fulfillments in a while because they're ditching the old Fulfillment sy...

I'm using the new fulfillment system as it is linked in the original post. The REST endpoint is: GET https://{shop}.myshopify.com/admin/api/{api_version}/assigned_fulfillment_orders.json?assignment_status=fulfillment_requested&location_ids[]={assigne...

Exactly, this API is useless without it. And its in the GraphQL so why have REST if its not actually going to contain the useful info.

I'm trying to build a fulfillment workflow using the APIs as described here: https://shopify.dev/apps/fulfillment/fulfillment-service-apps/manage-fulfillmentsHowever, the REST API appears to be missing a critical piece of data. The line items don't c...