Put Shopify Flow Documentation to Work on Real Orders

By Milan Dhameliya · · 9 min read

Use Shopify Flow documentation to build a packing-review rule, keep conditions on the same line item, and test the orders that expose false positives.

Shopify Flow documentation lives in Shopify’s Help Center: start with the Flow reference, then open the specific trigger, condition, and action pages for your task. To turn those instructions into a reliable automation, define which orders should qualify, build the rule, and test both qualifying and nonqualifying examples before activating it.

This guide follows one illustrative packing rule from that first sentence to an approved workflow. A homeware merchant wants an order tagged for packing review when a single line contains at least two units of a product marked fragile. The example is a teaching scenario, not a client result or a universal packing recommendation. Its useful complication is that “fragile product somewhere in the order” and “quantity of two somewhere in the order” are not the same rule.

Read the documentation in the order your decision needs it

The reference separates triggers, conditions, actions, and connectors. A trigger starts the workflow, a condition decides whether it proceeds, an action does the work, and a connector exposes an app’s integration. You do not need to read every available action before building your first rule.

Shopify’s Flow overview says the app is available without an additional charge on Basic, Grow, Advanced, and Plus. Install it from the Shopify App Store and ensure the staff member has the required permissions. Some capabilities have separate restrictions: Send HTTP Request requires Grow or higher. Our packing example uses ordinary conditions and order tags, so it does not need that action.

If another app is involved, establish what it contributes before installing it. Our Shopify app selection guide provides a useful way to evaluate the operational need and dependencies.

Write the packing rule before opening the editor

Use this specification for the example: “When an order is created, add packing-review if at least one order line belongs to a product tagged fragile and that same line has a quantity of at least two.” Ask the packing lead to approve that sentence.

Keep the input and output distinct. fragile is a product tag describing the item. packing-review is an order tag telling staff to review the order. A product tag is not an order tag, and this workflow should not add the review label to your catalog.

Agree on examples before configuring anything:

That last outcome may reveal that your actual requirement is different. If packing needs review whenever the combined number of fragile units reaches two, stop and rewrite the specification. Summing quantities across matching lines requires different logic from checking each line’s quantity. Choosing a threshold is an operational decision; the editor cannot make it for you.

Use deliberate product tags and review whether your theme exposes them to customers. Shopify’s tag guidance recommends a consistent format and notes that some themes display product tags. Do not assume internal-looking labels are automatically private.

Build the workflow with both checks on the same item

Follow Shopify’s workflow creation instructions: go to Apps > Flow > Create workflow, choose Select a trigger, and select Order created. Name the workflow “Packing review — fragile line quantity” so the purpose is clear in the workflow list.

The Order created reference confirms that this trigger supplies the order object. It also covers a draft order converted into an order after being marked paid. This example classifies newly created orders; it does not decide whether payment is safe or whether fulfillment should start.

Add a Condition. Select order / lineItems / product / tags, retain the appropriate At least one of list matching, and compare the tag with fragile. Then use Add criteria for same item on the lineItems list. Select lineItems_item as the object, choose quantity, and require Greater than or equal to 2. Combine the checks with AND.

Shopify documents this grouping mechanism in its conditions reference. The second criterion must belong to the same line item. Do not accidentally attach it to the product’s tags list or create an independent order-wide quantity check.

The decisive test order is one fragile mug plus two ordinary napkins: if it gets the review tag, your two checks are finding evidence on different lines. A test containing only two fragile mugs would pass both the correct rule and that incorrect rule. It cannot distinguish them.

On the True branch, select Action > Add order tags and enter packing-review. Leave the False branch without an action. Shopify’s action reference confirms that the trigger supplies the order ID. Keep tag spelling consistent, including capitalization.

A review tag is a label. It does not, by itself, hold fulfillment, notify the warehouse, or guarantee anyone reads it. Before relying on it, decide where staff will see the label and who owns the review. If a fulfillment app already reacts to that tag, adding it can have consequences beyond the label; inspect those existing rules first.

Test the business rule without changing orders

Keep the workflow inactive while checking the logic. In Apps > Flow, open the workflow, choose Edit, and click Test your workflow at the trigger. Use + Add event > Create event to select suitable existing store data. Shopify’s testing guide explains how simulated events exercise the rule without performing live actions.

Prepare cases matching the five examples above. If you edit saved test data, confirm the actual fields represent your intended case; a friendly event name is not evidence of the data inside it. Inspect the path taken and the action preview for each case. Record the expected outcome before running it so you do not unconsciously accept whatever the workflow produces.

Test mode has limits. External-service actions can show configuration previews without simulating the response, and tests do not appear in Recent runs. Recording events can also involve real activity: creating an actual order to generate a recorded event still creates that order. For this exercise, prefer simulated events based on existing records.

Keep an acceptance note with the workflow name, input cases, expected tags, observed branches, and reviewer. Include a screenshot of the grouping around lineItems_item. This is more useful to the next staff member than “tested successfully,” because it records what success means.

Ask the packing lead to review the two-fragile-products case explicitly. An automation can execute exactly as configured and still implement the wrong packing policy. That discussion belongs before activation, when changing the specification is easy.

Separate a logic test from a real manual run

Once the simulated cases behave correctly, plan one controlled live check. Choose an appropriate order whose tagging consequences you understand. Shopify’s manual-run instructions require an active workflow and a supported trigger; Order created is supported.

Activate only when you are ready for new orders to qualify too. Open Orders > the selected order > More actions > Run Flow automation, select the workflow, and choose Run workflow. This performs the action. It is not the simulation described in the previous section.

Check the order afterward and confirm that staff can find the review label in their normal process. Avoid starting with a bulk selection: a single inspected order makes it easier to distinguish a logic error from another app’s behavior. Do not use this tagging exercise as permission to trial refunds, cancellations, or payment actions on customer orders.

For later runs on edited orders, review the quantity definition again. Shopify’s LineItem reference exposes both quantity and currentQuantity; the latter excludes refunded and removed units. A classification rule written for order creation needs another review before you use it as a current packing-state calculation.

Monitor the result people actually use

Open Apps > Flow > Recent runs, select a run, and inspect the condition and action details. The monitoring documentation explains filters for workflow, errors, actions taken, and text such as an order ID. Run history is retained for 14 days after completion, so keep your acceptance notes outside that temporary log.

If a run took no action, inspect the values and branch before rebuilding it. If Flow reports a successful tag addition but the tag disappears, investigate subsequent changes. Shopify’s Add order tags documentation specifically describes apps or admin users overwriting tags. Another automation’s update may explain the difference between the run log and the order you now see.

My recommended handoff has three owners: someone maintains product classification, someone maintains the workflow, and someone handles the review queue. One person can fill all three roles, but the responsibilities should be explicit. Catalog changes deserve the same care as workflow edits because they change which products qualify.

Use the same discipline when automating stock-related work: identify the relevant inventory state and location before defining the action. Our Shopify inventory tracking guide helps your operations team establish that starting point.

Know when this example is the wrong starting point

Skip this exact rule if you need a total across different fragile products, variant-specific handling, an enforced fulfillment hold, or a warehouse acknowledgment. Each requirement changes the data or action you must verify. A product-level tag is also too broad when only certain variants need special packing.

For a small order queue with no consistent packing policy, write the policy and use a manual review first. Automation is useful when the decision is repeatable and its output has an owner. Adding a tag nobody uses creates another field to maintain.

For requirements that extend beyond a workflow, our Shopify app development guide helps define the implementation scope. When commissioning more complex work, provide the business sentence, passing and failing orders, expected downstream action, and the person who approves it. That gives a studio something concrete to implement and test. Our Shopify automation and integration services can help turn that specification into a workflow your team can maintain.