I work for a FulfillmentService and we’ve recently started enabling permitsSkuSharing for some of our clients. We’ve recently noticed that setting permitsSkuSharing : true removes the “Fulfill Item” option from the order screen, while leaving permitsSkuSharing : false keeps that button present. I’ve included images from 2 development stores where I recreated this (one with the setting disabled, one with the setting enabled). This hasn’t become an ISSUE yet, but we are starting to get questions about it and we haven’t been able to find this behavior documented anywhere. Could someone shed some light on why enabling Multi-Managed Inventory removes that option from the UI?
If you’re a fulfillment service, you control the fulfillment after it’s been requested for fulfillment.
For example, the screenshots indicate a fulfillment request has already been made (clicking the Request Fulfillment button, or triggering by API), the next logical step would be for the fulfillment service to fulfill the order, then mark as fulfilled + add tracking via the API.
Or if the store wanted to actually “Fulfill item”, they would want to cancel the request so the fulfillment service does not fulfill it, then they would change the location of the fulfillment order to the location they fulfilled it from, so they could mark it fulfilled, accurately representing the location they fulfilled from.
Hi JoesIdeas,
I’m very familiar with the FulfillmentService workflow and understand that as a FulfillmentService we control the fulfillment after the request has been submitted and accepted.
In both screenshots fulfillment has been requested from our FulfillmentService AND has been accepted. However, in 1 scenario (permitsSkuSharing : false) the “Fulfill Item” option is still present while in the other scenario (permitsSkuSharing : true) that option is still present. My question relates specifically to the presence of that option as it relates to the permitsSkuSharing flag.