Conditional Check that a Fulfillment Location has enough stock to fulfill an order

[dverzani]

Just trying to figure out how I can add a conditional check to a Flow workflow to make sure that the assigned fulfillment location has enough inventory to fulfill all the items on the order prior to submitting the fulfillment request.  

 I want to add this condition right before Submit Fulfillment Request Actions.  That way if there is not enough inventory, I will not submit the fulfillment request, and instead shoot an email out to someone as a notification.

Thanks for any help!

[Kalen_Jordan]

I don't believe it's possible to query inventory data by location in flow natively. The flow team will probably reply here to confirm though. 

I assume you have multiple locations?

[paul_n]

One problem here is that you are moving it to a new location and thus you need to check that location not the original location. You could use something like "Get product variant data" with the line item SKU on that fulfillment order as part of the query. You could then use a condition to check that all of the variants are in stock. 

[dverzani]

Thanks for the reply and help Paul.  I was able to set this up and do some testing and the issue I am having is that the conditional check for the product variants inventory being greater than or equal to 1 is checking all products in all locations and not just those products on the fulfillment order in the assigned fulfillment location.  

The overall goal here is to (1) move orders to the Zenventory location, then check if the items on the order all have an available value of 1 or greater in that Zenventory location, (3) If true then submit a fulfillment request, if false the move the order to the alternate location (West Coast in my example).

Any additional help you can provide would be greatly appreciated.  Thanks!

[paul_n]

You would need to check two variables in the same condition loop:

Location inventory is under variant / inventoryItem / inventoryLevels / available 

with the location under: variant / inventoryItem / inventoryLevels / location / id

[dverzani]

Copy that.  So something like this?  

[paul_n]

Yeah, except you need to add a check for the available variable to that second condition via the "Add criteria for inventory_levels list item". Make sure to choose the inventory levels list and not another variable

[dverzani]

I feel like I am super close to having this correct, but I'm still off somewhere.  This is how I set it up:  It's failing that conditional check still.  

My example orders has 2 products on it. 1 that is available only in the Zenventory location and one that is available in both the Zenventory and West Coast location.  In this situation, I would need the conditional check to say True that all items are in stock (greater than or equal to 1) in the Zenventory location and move on to the next step.  

I truly appreciate your time and help, but I know I am still just missing some portion of this setup, logically.

Thanks!

[paul_n]

You are checking if all variants and all locations match, which is never true because not all location match that ID. I think you want all and "at least one of" the locations.

[dverzani]

Probably just Friday afternoon brain at this point, but I'm all mixed up now and what to change and try now.  When the order gets moved to that Zenventory location, would it not just be the one location there that is being matched at that point?

Maybe an example would help me more (visual learner) haha.  

Either way, thanks for the responses.  It seems pretty terrible if Shopify (with all the changes made a year ago this fulfillment order workflow) does not support the ability to make decisions based on stock levels in said fulfillment locations

[paul_n]

[dverzani]

Thanks, but that also did not work.  It really does sound like there is not a way to do this properly, which is very disappointing to Shopify users and 3PL fulfillment centers with client's who sell on Shopify.

[paul_n]

It can work. If you need further help, we need more detail than "it doesn't work". Usually what happens in scenarios like this is that we have incomplete information about your use case.