Flow reacts to a block. It does not perform one.
Read this before any template. Prime MOQ's rules are enforced by the checkout validation Function, on every plan, whether or not you use Flow. Nothing in Flow can block an order, and turning Flow off never lets an order through. The Automations page says it directly:
Flow does not block anything Your rules are enforced at checkout on every plan, with or without Flow. What Flow adds is what happens around a block, and rules that change themselves.
So Flow does two jobs:
- After a block, do something about it: tag the customer, email your team, start a draft order.
- Change a rule automatically: tighten a maximum when stock is low, pause a rule after a promotion, reset a customer's repurchase count.
How limits are actually enforced is covered in How Prime MOQ Enforces Limits at Checkout.
Before you start
Open Automations in the Prime MOQ sidebar and turn on Send blocked orders to Shopify Flow. It is off by default:
Off by default. Turn it on once you have built a workflow, otherwise you are sending events nothing listens to.
Without it, no Prime MOQ trigger starts a workflow. Two limits apply once it is on: "Up to 100 workflow starts per hour. Repeat blocks from the same shopper within 20 seconds count once, so a frustrated customer clicking six times is one event." If the hourly limit is reached, the page shows how many blocks did not start a workflow that hour.
The Automations page is visible on every plan, so you can read what each workflow does before deciding. The Send blocked orders to Shopify Flow switch and Install on the ready-made workflows are Pro, and show a lock on the Free plan. The Flow triggers and actions themselves are installed with the app.
Triggers
| Trigger | Starts when | What it carries |
|---|---|---|
| Order limit blocked a customer | A Prime MOQ rule stops a customer from adding to cart or checking out on the storefront. | The product or variant, Customer ID, Rule name, Limit type (Quantity, Order value or Weight), What was violated, Attempted amount, Allowed amount, Unit, Where (product page or cart) and Shopper action. |
| Repurchase limit reached | A customer's cumulative purchases under a repurchase-limited rule reach the configured cap. | The customer, the order that reached the cap, Rule name, Limit quantity, Window (days) and Quantity used. |
Customer ID is empty for a guest. Use a "Customer ID is not empty" condition in Flow before any step that needs a customer. The trigger also has a Cart total field, which Prime MOQ does not fill in yet, so do not build a condition on it.
Every field of each trigger, with worked examples, is in Order limit blocked a customer and Repurchase limit reached.
Actions
| Action | What it does | Fields |
|---|---|---|
| Set rule limit | Adjusts one bound of an existing rule. | Rule ID, Bound (min, max, multiple, minValue, maxValue, minWeight or maxWeight), New value |
| Toggle rule | Enables or disables an existing rule. | Rule ID, Enabled (true to turn on, false to pause) |
| Reset repurchase counter | Clears a customer's tracked purchase count for a repurchase-limited rule. | Customer, Rule ID |
Every action needs a Rule ID
This is the step people get wrong. All three actions identify the rule by its Rule ID, and the field help says so: "Rule ID, copy it from that rule's edit page in Prime MOQ (not the rule name, which two rules can share)."
To find it, open the rule in Prime MOQ. The Rule ID appears under the page title, as "Rule ID:" followed by the ID, with a copy button beside it. The same ID is in the Rule ID card in the right-hand column, which notes it is for Shopify Flow actions. Paste it into the action's Rule ID field.
A rule name will not work, even if it is unique today. Names can be changed and duplicated. The ID cannot. See Finding a Rule ID for Flow.
Each action, field by field, with examples: Set rule limit, Toggle rule and Reset repurchase counter.
Ready-made workflows
The Automations page lists four workflows under Ready-made workflows. Click Install, download the workflow file, then in Shopify Flow click Create workflow, open the editor's ⋯ menu, choose Import and pick the file. Each one needs a small edit before you turn it on.
| Workflow | What it is for | Edit before turning on |
|---|---|---|
| Low stock tightens the maximum | When inventory drops below 10, set a rule's maximum to 2, so one buyer cannot take the last of a line. | The Rule ID in Set rule limit, and the threshold and maximum if 10 and 2 do not suit you. |
| Near-miss carts become leads | When a blocked cart is close to the rule's minimum, tag the customer as a lead, since a near miss is a warmer prospect than a cold one. The tag it adds is "BellowLimit". | Add a step after the tag, such as notifying a sales rep, if you want more than the tag. |
| Oversized cart becomes a freight quote | When a weight limit blocks a cart, email your freight or sales team everything they need to reply with a quote. The workflow sends the email only. To also create a draft order, add that step in Flow yourself. | The recipient address in the email step. |
| Repeat buyer worth a look | When a customer reaches a repurchase cap, tag them and email your team. Six valid orders can also be one reseller working around your checkout. | The recipient address in the email step. |
Near-miss and Oversized cart need an active minimum quantity rule and an active weight-limit rule respectively. Repeat buyer needs a rule with a repurchase limit configured. See Repurchase Limits, Capping Purchases Per Customer.
The full install walkthrough and what to do with each workflow are in Workflow Templates.
Low stock template or stock-aware maximum?
Both stop a thin line selling out to one buyer, in different ways.
- The stock-aware maximum lives inside the rule. It is continuous and per variant, follows stock up and down, and needs no Flow at all.
- The Low stock tightens the maximum workflow is event-driven. It changes the rule once when stock crosses a threshold, and because it is Flow, it can also do things outside Prime MOQ, such as notifying purchasing.
For a cap that simply follows inventory, use the stock-aware maximum. See Stock-Aware Maximum.
Recent activity on the Automations page
The Automations page keeps a log of "every trigger this app sent to Flow (or skipped, with why) and every action call received from Flow." It stays empty while Send blocked orders to Shopify Flow is off. When a workflow does not start, this log is the first place to look, because it shows a skipped trigger and the reason, such as being over the hourly limit. See The Flow Activity Log.
For the page as a whole, see Automations Overview.
Common mistakes
- Expecting Flow to enforce a limit. It never does. If a rule is not blocking, the problem is the rule, not the workflow.
- Leaving Send blocked orders to Shopify Flow off. The workflow is built and on, and nothing ever starts it.
- Typing the rule name into Rule ID. Copy the ID from the rule's edit page.
- Acting on a guest. Customer ID is empty for guest checkouts. Add a condition before tagging or emailing a customer.
- Pointing an action at a rule you later delete. The action then has nothing to change. Update the Rule ID when you replace a rule.