Removing `permitsSkuSharing` field from fulfillment service

Changelog
1

As of API version 2026-04, we've removed the permitsSkuSharing field from the FulfillmentService object and from the fulfillmentServiceCreate and fulfillmentServiceUpdate mutations. SKU sharing will be enabled by default for all fulfillment services.

This is a companion discussion topic for the original entry at https://shopify.dev/changelog/removing-permitsskusharing-field-from-fulfillment-service
Please make includeLegacy: true the default in the locations query
Please make includeLegacy: true the default in the locations query
2

If you call fulfillmentServiceCreate in 2026-04, it ends up creating the fulfillment service as if permitsSkuSharing is false, which is a big problem. I had to revert to 2026-01 where the field still exists to update the fulfillmentService and set it to true. Please fix it.

1 Like
3

Hi @npiasecki,

I’ve tried to replicate this behaviour on my test store and so far I have not been able, experiencing the following behaviour.

  1. When I create a fulfillment service with fulfillmentServiceCreate on 2026-04, it fails to create if I include permitsSkuSharing in the returned fields (not the query input variables, but the fields returned once the mutation is ran)

  1. When I do create the fulfillment service in 2026-04, then query the object in 2026-01, it returns permitsSkuSharing: true indicating it defaulted to true when I didn’t pass any input for it in 2026-04

  1. I’m fully able to assign inventory to this fulfillment service, as well as other fulfillment services and Shopify managed locations, without any issue. Indicating that permitsSkuSharing: true is working as expected.

Since I’m unable to replicate this behaviour, do you have any new specific examples for us to look into further where this behaviour is still occurring. If you can please provide us with the API calls used to create the fulfillment service, as well as a specific product id that you were unable to share the sku with other locations, as well as any errors or warnings you may have received. For the example API calls please provide the following details:

  • x-request-id from the HTTP Response Header
  • the full HTTP Response Body received.