How can I automate daily order fulfillment checks without infinite coding?

[FurtherRecords]

order created->check fulfillment->if yes->email/if no->wait 1 day->check fulfillment again

In order to do this I have to write infinite code asking the flow app to check again. wait again. check again. I cant just link from wait 1 day back in to the original check condition?! If I wanted to check every day for a year I'd have to write/draw 780 boxes to make this work?

https://streamable.com/dff96c (video of the issue)

[paul_n]

What you are suggesting is that you want an infinite loop full of wait steps, which is not something that we would support without limits that would shut it down after so many loops. So it wouldn't work for this use case regardless. 

An alternative approach for something like this would be to schedule a workflow to run every day and check for any unfulfilled orders. Then do something based on what you get back. We do have the features needed to do this kind of thing in progress. 

[FurtherRecords]

---

@paul_n wrote:

An alternative approach for something like this would be to schedule a workflow to run every day and check for any unfulfilled orders. Then do something based on what you get back. We do have the features needed to do this kind of thing in progress. 

---

OK. So this feature doesn't exist right now, but you hope to implement it soon? 

I have a similar issue, where I have drawn a workflow with 7 check/wait loops (1 for every day of the week) which all lead to a "send internal email" if the condition is met. That means I have to draw in 7 "send internal email" action boxes. It would be nice if all 7 condition met boxes could be connected to the same "send email" action box.

[paul_n]

A co-worker pointed out that it's not clear if you are trying to check if the order is fulfilled or unfulfilled. If you want to send something when the Order is Fulfilled, then you can just use the Order Fulfilled trigger.

[FurtherRecords]

Honestly I just wrote that flow as an example to show support how difficult it was to re-check a condition after an initial failure. I thought it would be a simple example.

The main purpose of the flow would ultimately be to check if an order is domestic/international and then check standard/express. Send the packing team an email if unfulfilled after certain length of time (based on intl/domestic/standard/express). Then send packing team another email after it was marked as fulfilled but has not started tracking yet despite some time passing (ie they marked as fulfilled but it didn't get packed/shipped/tracked yet).

This means that conditions must be rechecked after initial failures and there are multiple conditions that lead to the same action.

This is my first attempt at flows and I'm not a programmer so I'm trying to understand what it can and can't do and therefor what it might be useful for. We're a small company and the more I can automate the better!

[shopflex1]

You can try ShopFlex , which is like Flow but more flexible. The check loop is implemented through event. First, it listens order create event from Shopify, then check fulfillment status after 1 day. If the order is fulfilled, it will send the notification Email, otherwise it emit an order event, which will go back to the first step.

I made a video to demo it: https://youtu.be/z3qIiTTM_Z0