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!
-----
