AI AUTOMATION · MODULE 04 OF 08 | breadcrumb: Home > Learn > AI automation > Modules > 04 Rules-based automation first
Module 04: Rules-based automation first
Rule-based automation should come before AI in an ecommerce store, because the most useful automations in most stores contain no AI at all. They are rules: when this happens, if that is true, do this.
Quick answer
Build rule-based automation in your ecommerce store before AI. A rule has a trigger, optional conditions and an action, and it does the same thing every time. Rules handle tags, alerts, routing, notifications and summaries cheaply and predictably. Shopify Flow is free on Basic, Grow, Advanced and Plus; connectors handle cross-system rules.
Lesson 4 of 8 in our free AI automation guide. Read it in about 10 minutes, then work through the checklist at the end.
Why should rule-based automation come first?
Rules are cheap, predictable and easy to check. When a rule is wrong, you can see why in one line. They also force the decisions AI cannot make for you: your refund limit, your fraud threshold, your reorder point. Every good AI workflow later sits on top of rules like these.
How is a rule built?
Trigger, conditions, action. Shopify Flow uses exactly this structure: "Shopify Flow monitors your store for events and lets you create a sequence of actions that are taken in response" (Shopify Help Center, checked Oct 20, 2026). Zapier, Make and n8n use the same idea across apps.
Here is rule 1 from the table below, built in Shopify Flow (illustrative example; your threshold will differ):
- 01Trigger:
Order created.
- 02Condition:
order total is greater than $300, or the shipping address country differs from the billing address country.
- 03Action:
add the tag "review" to the order, and send an internal email to the person who checks orders.
- 04Owner and review:
the ops lead reads every tagged order the same day and checks the workflow's run history on Mondays.
Written out like this, the rule fits on an index card. That is the test: if you cannot write a rule on an index card, it is not ready to automate.
Ten rules worth building
| # | When | If | Then | Reversible? |
|---|---|---|---|---|
| 1 | An order is created | Total is over your fraud-check threshold | Tag "review" and notify a person | Yes |
| 2 | An order is created | It contains a fragile or oversized item | Tag "special handling" | Yes |
| 3 | Stock changes | Available stock is at or below the reorder point | Alert the buyer | Yes |
| 4 | Tracking is added | Always | Send the shipping confirmation with a tracking link | Yes |
| 5 | Tracking shows a delay | Delay over 2 days | Send a delay update with the new date | Yes |
| 6 | Every morning | Always | Send the daily summary: orders, stock cover, late orders, health warnings | Yes |
| 7 | An order is late | Not shipped by ship-by time | Alert the ops lead | Yes |
| 8 | A return is requested | Inside the return window and under your refund limit | Approve and send a label | Partly |
| 9 | A customer orders for the third time | Always | Tag "repeat customer" | Yes |
| 10 | A product goes out of stock | It has active ads | Alert the ads owner to pause | Yes |
Rule 8 moves money, so it carries a limit and a weekly review. Rule 10 alerts rather than pausing ads directly, because budget decisions stay with a person.
How do you test a rule?
Run it on a copy or with tags only for a week. Check every order it touched. Then switch on the real action. Name an owner, set an alert for failed runs and review the log weekly.
When does a rule need AI?
When the input is language (a free-text customer message) or a pattern too fuzzy to write down. That is Module 05.
Where automation stops
Let AI do the busywork. Three actions always wait for a person:
- 01Price changes outside the limits you set.
A pricing mistake can sell your stock at a loss in minutes.
- 02Refunds above a set amount.
Small ones can be automatic. Big ones get a second look.
- 03Anything touching account health.
Appeals and policy replies are written and checked by people.
We add three more to every build: account appeals and reinstatement, policy decisions (what your store promises customers) and any situation nobody has written a rule for. Everything else: automate it, log it and review it every week.
Five guardrails sit under every workflow: limits on every action, approval for anything risky, only the access each tool needs, a log of every step and one person who owns the outcome. What your AI says, you said.
Key takeaways
- Trigger, conditions, action: same structure everywhere.
- Start with tags and alerts; add actions that move money last, with limits.
- Test with tags for a week before the real action.
- Every rule has an owner and a failure alert.
Do this now
- Pick three rules from the table that match your top-scoring tasks from Module 02.
- Build them as tags or alerts only.
- Review every order they touched after one week.
- Turn on the real action for rules that were right every time.
- Add each rule to your automation register with an owner.
Tool for this lesson: Shopify Flow; Zapier, Make or n8n for cross-system rules.
Ecom Relays is not paid by and not affiliated with any tool listed. We name widely used tools so you know your options. Amazon, Walmart and Shopify are trademarks of their owners; Ecom Relays is not affiliated with them.
Most new stores take months to find steady sales, and some never do. Inventory, platform fees, freight and ad spend are paid by you. Automation saves time on repeat work. It does not create demand for a product.
A note on AI claims: the FTC has warned businesses not to exaggerate what their AI can do (FTC business guidance, "Keep your AI claims in check," Feb 27, 2023). We describe each tool from its own documentation, label vendor figures as vendor estimates and never say that AI will produce sales for you. AI here means software that drafts, sorts, checks and alerts. People still own the decisions.
The problem this lesson fixes
-
In owners' words:
"Orders ship with the wrong item, or none at all."
-
Cause:
no checks on special orders before they reach the packer.
-
Fix:
rules 1, 2 and 7 from the table above. If you want the routing rules written and built with you, they are part of the 14-Day Ops Foundation.
-
Measure:
order errors per 100 orders.
Talk it through with a real person
Book a free 30-minute session with an ops lead. Bring one workflow you want off your plate, and we will tell you plainly whether to automate it, how and where it should stop. A real person replies within one business hour, 9am to 6pm US Central, Monday to Friday. No pitch deck.
A written plan within 3 business days. No sales call required.
Free
Ask a real expert. Free.
A real person replies within one business hour, 9am to 6pm US Central, Monday to Friday.
Request received.
That did not send.
You can reach an ops lead directly, and nothing you typed is lost.
Do rules need code?
Usually not. Flow, Zapier and Make are visual builders, and most of the ten rules above can be built by someone comfortable with spreadsheets. API work is needed for some 3PL and marketplace connections, where a developer or an integration tool does the linking once and the rules sit on top.
Is Shopify Flow free?
Yes, on Basic, Grow, Advanced and Plus (Shopify Help Center, read Oct 20, 2026). Send HTTP Request needs Grow or above, and tasks created by custom partner apps need Plus. Most in-store rules, such as tags, alerts and holds, work on Basic.
Can Sidekick build rules for me?
It can draft Flow workflows from a description. They are inactive by default and tagged so you can find them, and Shopify says to "thoroughly review and test" them before use (Shopify Help Center, read Oct 20, 2026). Treat a Sidekick draft like a new colleague's first attempt: check every condition before you switch it on.
How many rules is too many?
When nobody can name the owner of each one. Keep a register: one line per rule with what it does, the systems it touches, its owner and how to switch it off. If two rules do the same job, or one fires so often that nobody reads its alerts, merge or retire it.
What if a rule fires on the wrong orders?
Turn it off, fix the condition and re-test with tags only for a few days. Then check every order it touched while it was wrong and correct those by hand. Write down what happened in the register, because the same mistake often appears in a similar rule elsewhere.
Should refunds ever be a rule?
Only small ones inside written policy, with a weekly review. Set the limit in dollars, keep anything above it with a person and sample the automatic refunds each week to make sure the rule still matches your policy. Refunds move money, so they are the last rules to switch on.
Sources8 sources
- 01help.shopify.comchecked Oct 20, 2026Primary
- 02help.shopify.comchecked Oct 20, 2026Primary
- 03help.shopify.comchecked Oct 20, 2026Primary
- 04zapier.comchecked Oct 20, 2026Primary
- 05make.comchecked Oct 20, 2026Primary
- 06n8n.iochecked Oct 20, 2026Primary
- 07help.shopify.comchecked Oct 20, 2026Primary
- 08ftc.govchecked Oct 20, 2026Primary
Free and ungated. No sign-up wall. Ecom Relays is not a course or coaching program. We do not sell stores and we never promise income.
Next step
Ask a real expert. Free.
A real person replies within one business hour, 9am to 6pm US Central, Monday to Friday.