Shopify Flow is a core part of most Order Editing setup. It controls when orders are released from their editing window and become available to your fulfilment workflow, whether that's Shopify Admin, a 3PL, an ERP, or any downstream system.
Most merchant using Order Editing has a Shopify Flow running in the background. It's imported once during onboarding and, in most cases, never touched again.
💡 Good to Know: Shopify Flow is a free automation platform built into Shopify, available to all merchants. No coding required. Order Editing provides pre-built Master Flow files you can download from the Help Center and import directly, and the Order Editing team handles setup for you during onboarding.
What Does the Flow Actually Do?
In simple terms, the Flow creates a delay. When a customer places an order, the Flow holds that order back from your fulfilment systems for a set period of time, your editing window, so the customer has time to make changes. Once the window closes, the Flow releases the order and it moves into fulfilment.
The method it uses to "hold" the order depends on which Flow type you're running. Some delay payment capture. Some withhold a tag. Some place the order on fulfilment hold. But the core job is the same: keep the order out of your downstream systems until the customer is done editing.
Why Does This Feel Like It Duplicates What Order Editing Already Does?
This is the most common question we get, and it's a fair one. You set an editing deadline inside Order Editing, then you set what looks like the same delay inside Shopify Flow. It feels redundant. It's not.
The two systems serve different purposes:
Setting | What It Controls | Who It Talks To |
Order Editing deadline | The customer-facing editing window. Controls when the timer appears, when editing options show, and when they disappear. | Your customer (via the Thank You Page and Order Status Page) |
Shopify Flow delay | The system-level release gate. Controls when the order becomes visible to your fulfilment systems by changing payment status, applying a tag, or releasing a hold. | Your fulfilment stack (3PL, ERP, WMS, or Shopify Admin) |
Order Editing manages what the customer sees. Shopify Flow manages what your systems see. They need to be set to the same value because they're coordinating the same window from two different sides.
This separation is intentional. Shopify does provide APIs that could handle order release natively, but every merchant's fulfilment stack is different. Some systems pull orders by payment status, others by tags, others by fulfilment status. By using Shopify Flow for the system side, Order Editing works with every fulfilment stack on the market, regardless of how that system pulls orders from Shopify. No custom integration required, no matter what your setup looks like.
Set It and Forget It
After your initial setup, the Flow runs silently in the background on every order. You don't need to monitor it, update it, or interact with it.
⚠️ The One Exception: Changing Your Editing Deadline
If you adjust your editing deadline in Order Editing (e.g. from 30 minutes to 60 minutes), you must also update the delay in your Shopify Flow to match. This is the only reason you would ever need to open or modify your Flow after initial setup. Everything else is handled automatically.
To update the Flow delay:
Go to Shopify Admin > Apps > Shopify Flow.
Open your Order Editing workflow.
Find the "Wait" step and change the duration to match your new editing deadline.
Click Save.
That's it. If you never change your editing deadline, you never need to touch the Flow.
⚠️ Don't modify the Master Flow yourself. If you need to make any changes beyond the editing deadline timing, please reach out to the Order Editing team for guidance. The Master Flows are configured specifically for your setup, and incorrect changes can cause orders to release too early, too late, or not at all.
The Future of Flow in Order Editing
Order Editing is actively building native integrations that will handle order release without requiring Shopify Flow. This work is underway and expected to roll out during 2026. When it ships, merchants will be able to manage everything, the customer-facing editing window and the system-level order release, from within Order Editing alone.
Until then, Shopify Flow remains the standard approach for most merchants. It's stable, proven across thousands of stores, and requires no ongoing maintenance beyond the editing deadline scenario described above.
When native order release is available, we'll notify all merchants and provide a migration path. No action will be required until you're ready to switch.
The Three Flow Types
Order Editing provides three pre-built Master Flow templates. Each one matches a different way your systems interact with Shopify orders. The Order Editing team will recommend the right one during onboarding based on your fulfilment setup.
1. Delayed Payment Capture Flow
Best for: Systems that download orders with "Paid" status (e.g. ShipStation, Linnworks, Fulfillrite, CIN7, Smartpack).
This is the most common Flow type. It delays payment capture until the editing period ends. While the grace period is active, the order stays in "Authorised" status. Your external system only sees it once payment is captured and the status changes to "Paid." If you fulfil directly from Shopify Admin without any external systems, this is also the Flow type you'll use.
Step | What Happens |
1. Order created | Customer completes checkout. Payment is authorised but not captured. |
2. Grace period active | Customer can edit their order. Payment status remains "Authorised." |
3. Systems wait | Any system that downloads "Paid" orders ignores this one. |
4. Grace period ends | Editing window expires. |
5. Payment captured | Flow captures payment. Order status changes to "Paid." |
6. Order released | Order is now visible to your fulfilment workflow. |
⚠️ Payment Setting Change Required: You must change Shopify's payment capture from "Automatically at checkout" to "Manual" or "Automatically after fulfilment." Go to Shopify Admin > Settings > Payments > Payment capture method. This is safe and standard. 95% of Order Editing merchants use this setting. Payment is still captured automatically by the Flow when the grace period ends, the customer experience doesn't change.
Master Flow file: DELAYED_Order Editing_Master Flow.flow
2. Released Tag Flow
Best for: Systems that download orders tagged with "Released" (or a custom tag). Common with custom integrations and some ERPs.
This Flow waits for the editing period to end, then applies a "Released" tag to the order. Your external system watches for this tag and only pulls orders once it appears.
Step | What Happens |
1. Order created | Customer completes checkout. No "Released" tag applied. |
2. Grace period active | Customer can edit their order. Tag is withheld. |
3. Systems wait | Any system that downloads by tag ignores this one. |
4. Grace period ends | Editing window expires. |
5. Tag applied | Flow adds the "Released" tag to the order. |
6. Order released | External system sees the tag and pulls the order for fulfilment. |
Payment setting change: Not required. Leave on Automatic.
Master Flow file: RELEASED_Order Editing_Master Flow.flow
3. ON-HOLD Tag Flow
Best for: Systems that download orders with "Unfulfilled" status (e.g. ShipHero, Kayo 3PL, SendCloud, ShipVine).
This Flow places an "ON HOLD" fulfilment status on orders during the editing window, then removes it when the grace period ends. Your external system skips held orders and only pulls them once the hold is released and the status changes to "Unfulfilled."
Step | What Happens |
1. Order created | Customer completes checkout. Order is placed "ON HOLD." |
2. Grace period active | Customer can edit their order. Hold status active. |
3. Systems wait | Any system that downloads "Unfulfilled" orders skips this one. |
4. Grace period ends | Editing window expires. |
5. Hold removed | Flow changes status to "Unfulfilled." |
6. Order released | External system sees "Unfulfilled" status and pulls the order. |
Payment setting change: Not required. Leave on Automatic.
Master Flow file: HOLD_Order Editing_Master Flow.flow
Which Flow Do You Need?
The right Flow depends on how your systems interact with Shopify orders. If you use a 3PL or ERP, ask them: "What order status or condition triggers an order download?" Then match the answer below.
Your Setup | Use This Flow | Payment Setting Change? | Common Systems |
Fulfil from Shopify Admin only | Delayed Payment Capture | Yes (Manual or Auto at Fulfilment) | Shopify Admin (no external systems) |
External system downloads by "Paid" status | Delayed Payment Capture | Yes (Manual or Auto at Fulfilment) | ShipStation, Linnworks, CIN7, Fulfillrite, Smartpack |
External system downloads by tag | Released Tag | No | Custom integrations, some ERPs |
External system downloads by "Unfulfilled" status | ON-HOLD Tag | No | ShipHero, Kayo 3PL, SendCloud, ShipVine |
Real-time sync (no trigger) | Delayed Payment Capture | Yes | Dexion (syncs edits in real-time) |
💡 Not sure? The Order Editing team recommends the right Flow type during onboarding. If you're already set up and not sure which Flow you're running, go to Shopify Admin > Apps > Shopify Flow and look for a workflow with "Order Editing" in the name.
How to Import a Master Flow
Order Editing provides pre-built Flow files that you import directly into Shopify Flow. No coding or manual configuration required. In most cases, the Order Editing team handles this for you during onboarding, but here are the steps if you need to do it yourself.
Download the Master Flow file from the Order Editing Help Center. Each Flow type has a dedicated article with the download link.
Go to Shopify Admin > Apps > Shopify Flow.
Click "Create Workflow" or "Import."
Select "Import workflow from file" and upload the .flow file.
Configure the timing to match your editing deadline (e.g. 30 minutes). This must match the editing deadline you've set in Order Editing > Settings.
Click "Activate" and then "Save."
⚠️ Timing Must Match: The delay in your Shopify Flow must match the editing deadline in Order Editing. If your editing deadline is 30 minutes, set the Flow delay to 30 minutes. A mismatch means orders could be released while customers are still editing, or held longer than necessary.
Order Editing Tags
Order Editing applies tags to orders at key moments in the editing lifecycle. These tags are how Order Editing communicates with Shopify and any connected systems. You can also use them as triggers in Shopify Flow to build your own custom automations.
Core Tags
Tag | When It's Applied | What It Means |
orderediting | Customer saves changes to their order | The order has been edited. Use this to trigger post-edit workflows (e.g. notify your team, update external systems). |
orderediting:downsized | Customer reduces their order total | The customer removed items or switched to cheaper options. Useful for flagging orders that may need partial refunds. |
orderediting:reversed | Unpaid edits are automatically reversed | The customer added items but didn't complete payment before the deadline. Order Editing reverted the changes. |
orderediting:duplicated | Shopify Flow duplicates an order | A new order was created by duplicating the original. Used in some integration workflows. |
Authorization Tags
Tag | When It's Applied | What It Means |
orderediting:authorization_warning | Order is approaching auth expiry | The payment authorisation is close to expiring. Action may be needed to capture payment before it lapses. |
orderediting:authorization_captured | Payment captured to prevent expiry | Order Editing automatically captured payment to avoid losing the authorisation. |
Cancellation Tags
Tag | When It's Applied | What It Means |
orderediting:cancellation_requested | Customer requests cancellation | A cancellation has been requested but not yet processed. |
orderediting:cancellation_approved | Cancellation is approved | The cancellation has been approved and is being processed. |
orderediting:cancelled | Order is cancelled | The order has been fully cancelled. |
cancelled_store_credit | Cancelled with store credit refund | The customer received store credit instead of a payment gateway refund. |
cancelled_payment_gateway | Cancelled with gateway refund | The refund was processed through the original payment method. |
cancelled_support_ticket | Cancelled via support ticket | The cancellation was initiated through a customer support ticket. |
Beyond Order Release: Other Flow Use Cases
While order release is the primary reason every merchant has a Shopify Flow, the tag system opens up additional automation possibilities. These are optional and most merchants don't need them, but they're available if your workflow requires them.
Custom Cancellation Automation
Build Shopify Flow workflows that react to cancellation tags. For example, automatically issue a full refund when the orderediting:cancelled tag is applied, or route orderediting:cancellation_requested orders to a manual review queue before processing.
Support Ticket Order Holds
When a customer submits a support ticket through Order Editing, you can configure it to automatically hold the order. This prevents fulfilment until your team resolves the issue. Once resolved, remove the hold status or tag in Shopify Admin and the order proceeds to fulfilment.
Klaviyo Integration
Order Editing connects directly with Klaviyo (not through Shopify Flow) to power two email automations. An "Edits Saved" trigger sends customers a confirmation when they update their order. A "Post-Purchase Upsell Email" triggered by "Order Created" reaches customers in their inbox with a link back to their editing window, driving upsell conversion for customers who closed the Thank You Page before seeing their options.
Pre-Order Editing
When you enable pre-order editing in Order Editing > Settings, you need to disable any active Shopify Flows that would conflict. Pre-orders have different timing requirements (longer editing windows, no immediate fulfilment), so the standard grace period Flows don't apply.
Reverse Unpaid Order Edits
Order Editing can automatically reverse any unpaid additions when the editing period expires. This is handled natively by Order Editing (no Flow required), but the orderediting:reversed tag is applied when it happens. You can use this tag as a trigger in Shopify Flow to notify your team or take follow-up action. See Reverse Unpaid Order Edits for full details.
Troubleshooting Shopify Flow
If orders aren't releasing to your fulfilment workflow as expected, check these common issues.
Symptom | Likely Cause | Fix |
Orders stuck in "Authorised" status | Delayed Payment Capture Flow isn't running or timing is wrong | Check Shopify Flow > verify the Flow is active and the delay matches your editing deadline |
Orders never get the "Released" tag | Released Tag Flow isn't active or failed | Open Shopify Flow > check the run history for errors |
Orders stuck "ON HOLD" | ON-HOLD Flow didn't remove the hold after grace period | Check Flow run history. Manually remove hold for stuck orders in Shopify Admin. |
Flow timing doesn't match editing deadline | Flow delay and Order Editing deadline are out of sync | Update both to the same value (e.g. 30 minutes in both places) |
External system pulling orders during editing window | Wrong Flow type for your system's download trigger | Confirm how your system pulls orders and switch to the matching Flow type |
Flow shows errors in run history | Shopify Flow encountered an unexpected condition | Check the error detail in Flow run history. Common causes: order already cancelled, payment already captured by another system. |
💡 Check Flow Run History: Go to Shopify Admin > Apps > Shopify Flow and click on your active Flow. The "Run history" tab shows every execution, including any that failed. This is the fastest way to diagnose Flow issues.
Frequently Asked Questions
Do all merchants need Shopify Flow?
Yes, currently. Every Order Editing merchant has a Shopify Flow running as part of their setup. It handles the system-level order release that coordinates your editing window with your fulfilment workflow. This is being replaced by native functionality in 2026, but for now it's a standard part of every installation.
Why do I set the editing window in two places?
The editing deadline in Order Editing controls the customer-facing timer. The delay in Shopify Flow controls when the order is released to your systems. They serve different purposes but must be set to the same value. Shopify does offer APIs that could handle both, but using Flow ensures Order Editing works with every merchant's fulfilment stack regardless of how their systems pull orders. See "Why Does This Feel Like It Duplicates What Order Editing Already Does?" above for the full explanation.
Is it safe to change my payment capture setting?
Yes. Changing from "Automatically at checkout" to "Manual" or "Automatically after fulfilment" is standard practice. 95% of Order Editing merchants use this configuration. Payment is still captured automatically by the Flow when the grace period ends. The customer experience doesn't change.
What happens if a customer edits their order after the Flow has already run?
They can't. Customers can only edit during the grace period. Once the editing deadline passes and the Flow releases the order, the editing window closes and no further changes are possible.
When would I ever need to open my Flow after setup?
Only if you change your editing deadline in Order Editing. If you update it from 30 minutes to 60 minutes (for example), you also need to update the delay in your Shopify Flow to 60 minutes. Outside of that, the Flow requires no attention. If you need to make any other changes to the Flow for any reason, reach out to the Order Editing team for guidance first.
Do I need to adjust my editing rules or fulfilment conditions for Flow?
No. Editing rules, restrictions, and fulfilment conditions are powered natively by Order Editing's rules and restrictions engine at the app level. They don't depend on Shopify Flow and don't require any Flow configuration. This is part of the migration already underway to move functionality off Shopify Flow and into Order Editing directly.
Can I use multiple Flow types at the same time?
Generally, you should use one Flow type that matches your primary system. If you have multiple systems with different download triggers, contact the Order Editing team for guidance on the best configuration.
What if my 3PL or ERP is not listed?
The three Flow types cover virtually all systems. Ask your provider how they pull orders from Shopify (by payment status, tag, or fulfilment status) and use the matching Flow. If you're unsure, the Order Editing team can help.
Can I customise the Flow delay for different products or order types?
The Master Flows apply a single delay to all orders. For custom logic (e.g. longer editing windows for pre-orders, shorter windows for time-sensitive items), you can duplicate and modify the Flow in Shopify Flow's editor. The Order Editing team can also help build custom Flows.
Will Order Editing remove the need for Shopify Flow?
Yes. Native order release functionality is in development and expected to roll out during 2026. When available, merchants will be able to manage the editing window and system-level order release entirely from within Order Editing, without Shopify Flow. We'll notify all merchants when it's ready and provide a simple migration path. Until then, Flow remains the standard, stable approach.
Can I modify the Master Flow myself?
The only change you should make yourself is updating the "Wait" step to match a new editing deadline. For anything else, please reach out to the Order Editing team. The Master Flows are configured specifically for your setup, and incorrect changes can cause orders to release too early, too late, or not at all.
Where can I download the Master Flow files?
Master Flow files are available to download directly from the Order Editing Help Center. If you're not sure which file you need, reach out via the support chat in the app and we'll point you to the right one.
How do I know if my Flow is working correctly?
Go to Shopify Admin > Apps > Shopify Flow and click your active workflow. Check the "Run history" tab to see every execution. Green ticks mean successful runs. Red marks indicate errors that need attention. You can also place a test order and watch it move through the Flow in real time.