When a 3PL creates a fulfillment service , which is the correct way and seamless way to interact with Shopify on behalf of a client, it implicitly creates an underlying location with the property “legacy” set to “true”. The problem is when the client connects other third-party apps that try to creat…

Hi @npiasecki , I appreciate your feedback on this behaviour, and I will be submitting this feedback on your behalf internally. While I can’t guarantee that this change will be made or when, I can assure you that our developers and product managers do take all of our merchant and partner feedback in…

Please make includeLegacy: true the default in the locations query

Fulfillment & Inventory

Kellan-Shopify March 9, 2026, 5:42pm 4

I’ve commented on the Removing `permitsSkuSharing` field from fulfillment service thread for further help looking into that behaviour.

Topic		Replies	Views
Removing `permitsSkuSharing` field from fulfillment service Changelog	2	59	March 9, 2026
App Fulfillment Service Location not allowing inventory stocked at multiple locations Fulfillment & Inventory fulfillment-services , inventory-management	2	245	March 25, 2025
Product stocked at both standard and app fulfillment service location Shopify App Store dev-stores	2	64	June 8, 2025
Call to Grahql to get fulfillmentId returns null even though I have locations configured as fulfillments GraphQL Admin API Troubleshooting rest-migration , general-gql-troubles	9	106	November 17, 2025
Are third party shopify locations deprecated? Fulfillment & Inventory fulfillment-services	3	82	June 20, 2025

Please make includeLegacy: true the default in the locations query

Related topics