> every product needs to have data added to the specific metafield for it to be available in flow   No, that's not correct. Sorry you got that misdirection. Flow reads the metafield definitions on the shop to populate them under 'fields with argument...

Ok. That screenshot tells me that Flow asked for the tags on the product at the time of the workflow run and none were present. So I bet the product was created without tags and then (maybe immediately, maybe later, but definitely *after* the workflo...

What is the trigger you have specified in the workflow? Maybe the trigger is firing (and the workflow is running) before Printify has added the tags to the product.

Flow's API client _should_ be able to read any publicly-readable definitions on the shop. Are you able to see both definitions when querying them from the Admin GraphQL API? (e.g. with https://shopify.dev/docs/api/usage/api-exploration/admin-graphiql...

Based on that screenshot it looks like you still have the For Each step iterating over some data _other_ than the order's fulfillments/fulfillmentOrders? (The step's description reads `For each item in getOrderData` when it should read something like...

So, you don't need to 'Get order data' (fetch a list of orders) because you _already_ have the order (from 'Order created').   Instead, remove the `Get order data step' and use the For Each to iterate over the order's fulfillments.

Here's documentation about For Each: https://help.shopify.com/en/manual/shopify-flow/reference/actions/for-each  

Hi @Johnnyw11 ,   The action Move Fulfillment Order operates on fulfillment orders (not an order itself). An order can have one to many fulfillment orders. So, you can insert a For Each step before that action and iterate over all the fulfillment ord...

Hi Sportology,   Have you tried making a workflow to do this? It seems entirely possible by using conditions in the workflow to create branched logic and then using the data picker to select the fields to add as tags.