Removing permitsSkuSharing field from fulfillment service

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.

Why we made this change

By enabling permitsSkuSharing for all fulfillment services, we're standardizing inventory behavior across fulfillment services and simplifying the API. Previously, having permitsSkuSharing set to disabled would restrict inventory to a single location. This didn't always represent how the merchant's inventory item was setup in the real world.

Impact on your app

• GraphQL: In the unstable or 2026-04 and later releases, if you are querying for the permitsSkuSharing field or sending it in mutations in API version, you will begin receiving errors.
• REST: In the unstable or 2026-04 and later releases, the permitsSkuSharing field won't be returned in GET requests. In POST and PUT requests, the permitsSkuSharing argument will be ignored.
• permitsSkuSharing will be enabled for all fulfillment services.
• When permitsSkuSharing was disabled, inventory could only be stocked at a single location. With it enabled for all fulfillment services, inventory can be stocked at multiple locations.

What you need to do

• Remove any reads/writes of permitsSkuSharing from your code for the unstable or 2026-04 and later releases.
• Review any business logic that assumed inventory could only be stocked at a single location for a fulfillment service.