Would love to see some additiFuflillment_order fields

Retired Boards Appdev Fulfillment Api
,
1

The move to new-style fulfillments (by requesting fulfillment_orders for each order) was aimed at decoupling orders from fulfillments; the idea is that the fulfillment_order has all the information needed to complete the fulfillment.
We retrieve REST fulfillment orders with our solution: which now is 1) get list of orders 2) for each order, get the fullfillment_orders
But the disadvantage is the double API call per order, plus the fact that fulfillment_orders do not not have all the data that we need to be able to fulfill

  1. Order has the ISO country code in the shipping_address resource. But the destination object in fulfillment_order only has the full countryname. Which requires us to maintain a translation table, since the countries used in destination are not ISO and have to be parsed. So: Shopify: could you please add ISO “country_code” to “destination”?
  2. Passing custom information between merchant and shipper, The only option is adding merchant_requests, but the merchant UI does not have easy access to that object. In practice we use “tags”, which is easier and a convenient way to tag orders and xfer messages from merchant to shipper. So: Shopify, could you please add “tags” or a similar easy-to-add property to the fulfillment_order ?
  3. The 2 calls per order. Ideally, we would only retrieve a paginated list of fulfillment_orders assigned to a location, which would speed up the process by skipping a lot of API calls . And these features would allow us to get rid of Orders completely, just the OrderID would suffice

Tx!

2

Hi MichielfromNL,

I can for sure pass on the feedback to our product teams around multiple API calls, and to include the ISO “country_code” in the destination object, as well as having an easy-to-add property like “tags” to the fulfillment_order to facilitate the transfer of custom information between merchants and shippers.

Would the process of using the fulfillmentOrders query, on the Admin GraphQL API be easier for your use case?

3

Hi Liam,

Thanks very much for passing that info on!

About graphql: I am aware of the fact that at some point in time, in any case this year, we need to move from REST to GraphQl . But I haven’t studied that in great detail yet. As far as I understand, Graphql has in itself the ability to “join” queries, i.e. get data from multiple objects in a single Query. ; if that is also possible in Shopify graphQl: then there is no fundamental further need to follow up. But even then, having the mentioned fields in a single query would make queries simpler I guess.

Thanks again, for helping out!
Michiel