Test a Shopify Flow workflow without changing live store data
A Flow test can validate logic without changing live data, but it stops before modifying actions. Use it to find what still needs a real check.
The question
How do I test a Shopify Flow workflow without changing live store data?
- This applies when
- You are preparing to activate or change a valid Shopify Flow workflow and need to prove its trigger data, branches, variables, and operators without applying modifying actions. [Source 1]
- Nothing to do right now
- You need proof that a modifying action or an external service completed after a live run; use the last system's own test or result record for that job. [Source 1]
- Why this matters
- A workflow can follow the expected logic in Flow and still fail at the first modifying or external action, because the simulation stops before completing those actions. [Source 1]
- What to do
- Open Apps > Flow > Workflows, select the workflow, choose Edit, select its trigger, and confirm that Test your workflow opens. [Source 1]
- How to know you're done
- The passing and failing events follow the expected branches and Preview shows the expected data. Any unsimulated external action also shows the bounded result in the receiving system. [Source 1] [Source 2]
- What this doesn't prove
- A passing Flow simulation does not prove that a modifying action or external service completed, and the test run does not appear in Recent runs. [Source 1]
- Sources checked
- August 22, 2026
Shopify Flow can test a workflow against real or simulated store data without applying modifying actions. The test runs through the trigger, conditions, and data available to actions, then stops when it reaches the first action that would change something.
That makes the test useful for logic and data checks. It does not prove that every external system will accept the final action.
Open the exact test control
Open Shopify admin > Apps > Flow > Workflows. Select the workflow, choose Edit, select the workflow’s trigger, and choose Test your workflow. The expected screen is the Test your workflow dialog.
If any workflow step is incomplete or invalid, stop here. Shopify does not allow that version to run as a test, and activating it does not resolve the missing configuration.
Generate a passing and failing event
In the Test your workflow dialog, choose Generate events. Sidekick generates two saved events from existing store data, one intended to pass and one intended to fail.
Review the generated fields before running the test. Remove or change values that do not represent the case you need to prove.
Check each condition result
Select the passing event and confirm that the highlighted path reaches the expected action. Then select the failing event and confirm that the highlighted path stops on the intended condition.
Select each condition or action and open Preview. Confirm the displayed values, variables, operators, and AND or OR logic. A highlighted path that uses the wrong product, order, or customer data does not finish the intended test.
Separate external-service verification
Flow cannot simulate some external service actions, including HTTP requests. Those steps display a message that they cannot be simulated.
For a workflow with an external action:
- Complete the Flow test for the trigger, conditions, and payload values.
- Confirm the external service’s test or sandbox path, if it provides one.
- Use a bounded live case whose effects can be identified and reversed.
- Verify the result in both Shopify and the receiving service before widening the workflow.
The Flow simulation is finished when both saved events highlight the expected logic and Preview shows the expected data. The merchant job is finished only when the last system the workflow is meant to change shows the expected bounded result. If no safe external test or reversible case exists, leave the workflow inactive.
How to do it
- Open Apps > Flow > Workflows, select the workflow, choose Edit, select its trigger, and confirm that Test your workflow opens. [Source 1]
- Choose Generate events, review the two saved events, and keep one event that should pass and one that should fail using the intended store records. [Source 1] [Source 2]
- Select each saved event and confirm that the highlighted path, Preview values, variables, and operators match the expected result. [Source 1]
- When Flow shows Can't simulate this action, verify one bounded case in the receiving service and observe the intended result there before activating more broadly. [Source 1]
Open the official page, then report your progress
Progress stays in this browser on this device. We record only which official page you opened and whether you report that you finished or stopped at a step. AI Commerce Ready and Shopify do not check the result or change your store here.
- Where to do it
- Shopify admin → Apps → Flow → Workflows → Select the workflow → Edit → Select the trigger → Test your workflow
- What you should see
- The workflow editor opens the Test your workflow dialog with saved events and controls to add, record, create, or generate an event.
- How to know you're done
- The passing and failing events follow the expected branches and Preview shows the expected data. Any unsimulated external action also shows the bounded result in the receiving system.
- Stop here if…
- Stop without activating when a workflow step is invalid, the test data does not represent the intended case, or an external action has no safe test path or reversible bounded case. [Source 1]
Come back after: Keep this page open. After each Flow test or external-service check, return to this tab and compare the observed result with the finish condition before reporting progress.