.png)
Shopify Flow is included with every Shopify plan. Most stores either do not use it at all, or set up one simple tag workflow and stop there.
For B2B and manufacturing stores, Flow is more useful than that. It can handle account approvals, order holds, customer segmentation, and onboarding sequences without any third-party app. The logic runs directly in Shopify, against your real customer and order data, on triggers that Shopify already tracks.
Below are six complete workflow examples built for B2B and manufacturing stores. Each one describes what it does, what problem it solves, and where to find the full setup guide.
The problem: New wholesale applicants wait for manual review, even when the answer is obvious. A customer who registers with a corporate domain is almost certainly a business. One registering with Gmail probably is not.
What this workflow does: When a new customer registers, Flow checks whether their email domain belongs to a known free provider (Gmail, Yahoo, Outlook, Hotmail, and others). If the domain is business-only, the customer is automatically approved, tagged, and sent a welcome email. If it is a free domain, they are tagged for manual review and sent a holding email.
Trigger: Customer account created
Result: Automatic first-pass filter. Easy approvals handled without anyone touching them. Manual review queue contains only the edge cases.
Full guide: Flow: Auto-Approve Verified Business Emails
The problem: Applications get missed. Without a structured process, new registrations sit in a customer list with no flag, no assigned owner, and no urgency. Some follow up. Some disappear.
What this workflow does: The moment a new wholesale customer registers, Flow tags them as pending review, sends an internal alert to your team with the applicant's name, email, and company, and sends the applicant a confirmation email so they know their application is in progress. Optionally, it sends a follow-up reminder if the application has not been acted on within a defined time window.
Trigger: Customer account created
Result: Every application is captured and routed immediately. Nothing falls through the cracks before a human makes the review decision.
Full guide: Flow: New Wholesale Applicant Queue
The problem: Large orders go straight into the fulfillment queue alongside everything else. Errors on a $500 order are manageable. Errors on a $50,000 order, discovered after picking has started or a shipment has gone out, are not.
What this workflow does: When an order is created above a dollar threshold you define, Flow applies a fulfillment hold, tags the order, and sends a manager alert. The customer receives a normal order confirmation. The hold operates entirely on the fulfillment side. Managers review, then release or escalate.
Trigger: Order created
Condition: Order total exceeds threshold
Result: High-value orders get human review before any fulfillment resources are committed. Smaller orders process normally without delay.
Full guide: Flow: High-Value Order Hold
The problem: New wholesale accounts carry more risk than established ones. There is no order history, no sense of how they pay, and sometimes no confirmation that account details are accurate. Most stores have no way to automatically distinguish a first order from an account with two years of reliable history.
What this workflow does: When an order is created, Flow checks how many orders the customer has placed in total using the numberOfOrders field. If the count is two or fewer, the order is tagged, held, and routed to an internal review queue. Your team reviews and releases. All other orders process normally.
Trigger: Order created
Condition: numberOfOrders is 2 or fewer
Result: First and second orders from new accounts are reviewed before fulfillment. Established accounts are not affected.
Full guide: Flow: New Customer First-Order Review
The problem: Approving an account and assigning the correct pricing tier are two separate steps. When the second step relies on someone remembering to do it manually, it happens inconsistently. Customers log in to wrong pricing, no pricing, or a catalog that was not set up for their account type.
What this workflow does: When a customer account is approved, Flow reads signals from the customer record, such as industry tags or order volume data collected during registration, and branches based on what it finds. Each branch assigns the correct customer tags, places the account in the right pricing tier, and optionally sends a tailored welcome email that reflects the assigned tier.
Trigger: Customer account approved (or a specific tag added)
Condition: Branching on industry tag or order volume metafield
Result: Catalog and pricing assignment happen automatically at the moment of approval. Every approved account gets the right setup from day one.
Full guide: Flow: Segment Assignment on B2B Approval
The problem: Most B2B stores approve an account and send nothing useful. The customer logs in, does not know how to navigate the catalog, does not know who to contact, and either emails support or leaves without placing an order.
What this workflow does: When a customer account is approved (detected by the addition of an approved tag), Flow immediately sends a welcome email with the account portal link, catalog link, and next-step instructions. It also notifies the assigned sales rep that a new account is active. Optionally, it sends a follow-up email if the customer has not placed an order within a defined number of days.
Trigger: Customer tag added ("approved")
Result: Approval and onboarding become a single automated sequence. New customers receive everything they need to place their first order without any manual follow-up from your team.
Full guide: Flow: Welcome Sequence on B2B Approval
Several of these workflows are designed to run in sequence. The Auto-Approve workflow and the Applicant Queue workflow handle the front end of customer onboarding. Segment Assignment and the Welcome Sequence handle what happens after approval. The High-Value Order Hold and First-Order Review workflows sit at the order level, running independently each time an order is created.
You do not need to implement all of them at once. Each workflow is self-contained and can be installed and configured independently. A reasonable starting point is the workflow that addresses the most frequent manual task your team currently handles.
If you are not sure whether Shopify Flow or n8n is the right tool for a specific process, Conditional Logic Automations: When to Use n8n vs Shopify Flow covers how to make that decision.
For new users of Shopify Flow, Automating Back-Office Processes with Shopify Flow provides an overview of what Flow can handle natively before reaching for third-party apps.
These six workflows cover common B2B scenarios. For operations teams looking to go beyond individual workflows and build a repeatable automation program, the harder question is how to identify which processes to automate next, score them against each other, and sequence builds so the program keeps delivering ROI quarter over quarter.
The FlowKaizen guide walks through that system from the first workflow to a full program.
.png)
