Shopify Flow , 63 recensioni

Great idea, but not very reliable at any kind of volume. Lost track of the number of times, Flow simply decides to skip orders and not process them. Even worse, it seems like Shopify doesn't monitor it to detect when it's getting backed up and not processing.

Could be a great tool but it requires us to go through 15,000 clicks to run-segment our current base of customers as it's limited to 50 customers at a time. The real-time segmentation once created is working well so far. Could be much better coming from Shopify.

Is usefull for basic stuff, but there is a lot of limitations when you want specific automation like hiding your product ONLY on online channel,it is not possible with flow , or you can't either check inventory at a specific location , you can only access cumulated inventory...
Idea is good execution is kind of useless, shopify should work more in this app.

Seems very limited. I wish it had more available elements to automate. For example you cannot automate any product elements such as automation of adding a tag.

Sholify Flow has enormous potential but at this stage is missing lots of really useful features - among them:
- ability to deal with metafields
- time based triggers (you cannot get a Flow started at a given time)
- I would love to see an integration with Office 365 and Microsoft Flow - that would be a very powerful combination
- Some sort of way to write Liquid code to handle some stages of processes whose complexity makes them better suited for text coding rather than visual coding

I believe future versions will eventually implement these features and lots more - at this time though the tool is only showing its potential

Can't do basic things such as update the item's weight, set HS Code designation upon publishing. or set "Continue selling when out of stock" to True. Basic, Shopify-native things. Weak.

The biggest problems are:

When you use variables to create conditions, you don't have access to those values in other steps, so you have to recreate all your logic in each step of the flow. For example, if I have a conditional that checks for a certain metafield key in your order line items skus, then in your action step, you'll need to recheck for that key using all the same logic. You can't pass values from one step to another. Which defeats the purpose of a conditional in most cases: if X, then do Y (to X). But X isn't accessible, so your flow actually goes if X, then if X do Y.

Also, you can use variables for things like metafield keys, but the app will throw an error saying the key is too long. But really, it's long because it's using liquid conditionals and loops, not because the actual value is long, which doesn't make sense.