Hey,
The docs on the fulfilment orders displayable attribute are a little confusing/unclear on what they cover. For example it says it won’t include fulfilment orders closed as part of a merge. However it doesn’t include any fulfillment orders that are closed. order - GraphQL Admin
Not sure if this is a bug in how that filter is applied or in the documentation but its pnot very clear as to the meaning and usage of this.
Hey @JordanFinners! The behavior here is expected, but the wording on the displayable argument is misleading. The “closed after being combined or moved” line is just one example of a hidden fulfillment order. What displayable: true actually does is return only the fulfillment orders a merchant currently sees as outstanding work, so anything in a closed state gets filtered out, even if it was closed by normal fulfillment rather than a merge or move.
I confirmed this on a test store. I fully fulfilled a plain single-location order with no merge or move involved, which left its one fulfillment order in CLOSED status, and displayable: true returned an empty list while displayable: false still returned that closed fulfillment order. So a normally completed fulfillment order behaves the same as a merge/move-closed one under this filter.
If you need every fulfillment order including the closed ones, use displayable: false (that’s the default). If you only want them when they’re still active, displayable: true is doing the right thing, it’s the docs example that undersells the scope. I’ve passed the wording feedback along to the team that owns these docs so the description can be made clearer - thanks for flagging!
Hey Donal,
Thank you for confirming this, yeah if the documentation could be clearer that would help 
I thought it meant displayable as the merchant could see in the admin view