Six automations cover most of the repetitive order and operations work that a growing Shopify store does by hand. Not sixty. Most stores that go looking for Shopify automation end up with a long list of clever ideas and a handful of half-built workflows nobody trusts. The better path is to build a small set of dull, reliable automations that remove daily chores, then add more only when a real bottleneck shows up.
Below are the six we would build first for a typical DTC store. Each one is written as a plain outline: a trigger (the event that starts it), conditions (the checks that decide whether it runs) and actions (what it does). The outlines are tool-agnostic. You can build most of them in Shopify Flow, and all of them in Make or Zapier.
Three rules before you build anything
- Automate a process that already works by hand. If the team cannot describe the manual steps the same way twice, automating it just makes the confusion faster.
- Tag first, act second. Most of these workflows start by adding a tag to an order, product or customer. Tags are visible in the admin, easy to filter, easy to undo, and they let a later workflow pick up where the first one stopped.
- Every automation gets an owner and a log. Someone needs to know it exists, what it does and where to look when it misfires. A shared sheet listing each workflow, its trigger and its owner is enough.
1. Flag risky orders before they ship
Fraudulent or problem orders are cheapest to deal with before fulfillment. This workflow catches them automatically and puts them in front of a person.
- Trigger: order created, or the order risk analysis completes.
- Conditions: Shopify's risk assessment is high, or the order is above a value threshold you set, or the shipping country differs from the billing country, or it is a first-time customer ordering an unusually large quantity of one item.
- Actions: tag the order for review, hold fulfillment where your setup allows it, and send an internal alert to email or Slack with the order link and the reason it was flagged.
Keep the conditions tight at first. A review queue that flags every third order gets ignored within a week.
2. Warn the buyer before stock runs out
Running out of a best seller is usually a notification problem, not a forecasting problem. Someone would have reordered if they had known.
- Trigger: inventory quantity changes for a product variant.
- Conditions: the new quantity is at or below a reorder point, and the product carries a tag such as core-line so seasonal or discontinued items do not trigger noise.
- Actions: notify whoever places purchase orders, add a row to a reorder sheet with the SKU, current stock and supplier, and tag the product low-stock so the team can filter for it.
A simple way to set the reorder point is your supplier lead time in days multiplied by your average daily sales for that SKU, plus a buffer. Store the number in a product metafield so the workflow can read it per product.
Be careful with automations that unpublish or hide products at zero stock. Pulling a product page that ranks in search can cost traffic that takes months to earn back. Showing it as sold out with a back-in-stock signup is usually the safer choice.
3. Tag customers the moment they become valuable
Your email platform, support team and ads all work better when repeat buyers are identified automatically rather than exported by hand once a quarter.
- Trigger: order paid.
- Conditions: the customer's total order count reaches a threshold (three is a common starting point) or their total spend passes a figure that makes sense for your average order value.
- Actions: add a customer tag such as vip, sync that tag to your email platform so it can drive a segment, and optionally notify support so VIP tickets are handled first.
Once the tag exists, other workflows can use it: priority packing, a handwritten note in the parcel, or early access to launches. If you run Klaviyo, the tag can feed a segment that triggers its own flow.
4. Catch orders that are stuck
Late shipments cause most where-is-my-order tickets. The fix is noticing them before the customer does.
- Trigger: a scheduled daily run.
- Conditions: the order is paid, not fulfilled, older than your promised dispatch window, and not tagged as a preorder.
- Actions: compile the list into one internal message each morning, tag each order delayed, and queue a short update email to the customer for a person to approve or send automatically.
A sample customer message:
Hi Sam, a quick update on your order. It is taking a little longer than usual to leave our studio, and we expect it to ship by Thursday. You will get tracking as soon as it does. Reply to this email if you have any questions.
Sending that before the customer asks turns a likely complaint into a small moment of trust.
5. Route orders that need special handling
Gift orders, preorders, local deliveries, personalized items and fragile products all need something different at packing. Relying on someone to read every order note is how gift receipts get missed.
- Trigger: order created.
- Conditions: any line item has a product tag such as preorder, personalized or fragile, or the order note or checkout attributes include gift details, or the shipping method is local delivery or pickup.
- Actions: add matching order tags, add a clear packing instruction to the order's internal notes, and notify the person responsible for that order type.
Tags from this workflow can also split your fulfillment queue so the team works through standard orders fast and handles special ones in a separate batch.
6. Log every refund with a reason
Refunds are data. Most stores process them one by one and never look at the pattern, so the same sizing issue or damaged-in-transit SKU keeps costing money.
- Trigger: refund created.
- Conditions: none needed to log; add a condition for the alert step, such as refunds on the same SKU passing a count within 30 days.
- Actions: write a row to a returns sheet with the date, order, SKU, amount and reason; tag the order with the reason category; and alert the product or ops lead when a SKU crosses your threshold.
A monthly look at that sheet often points to a fix that is not an automation at all: a clearer size chart, better packaging, or a product description that sets expectations properly.
Summary: the six workflows side by side
| Workflow | Trigger | Main action | Build difficulty |
|---|---|---|---|
| Risky order review | Order created or risk analyzed | Tag, hold, alert | Low |
| Low-stock warning | Inventory quantity changed | Notify buyer, log to sheet | Low to medium |
| VIP customer tagging | Order paid | Tag customer, sync to email | Low |
| Stuck order watch | Scheduled daily | Daily digest, customer update | Medium |
| Special handling routing | Order created | Tag, packing note, notify | Low |
| Refund logging | Refund created | Log row, threshold alert | Medium |
Where to build them: Flow, Make or Zapier
All three tools can run these workflows. The right choice depends on where the data needs to go.
| Tool | Best for | Watch out for |
|---|---|---|
| Shopify Flow | Anything that starts and ends inside Shopify: tagging, holds, metafields, internal notifications. It is a free Shopify app on paid plans and runs close to your store data. | Connections to outside tools depend on which apps offer Flow connectors; anything else needs an HTTP request step. |
| Make | Multi-step workflows that touch several tools, with branching, data formatting and error handling you can see on a visual canvas. | Usage-based pricing, so high-volume triggers like every inventory change can add up. Filter early in the scenario. |
| Zapier | Quick connections to a very wide range of apps, set up by non-technical team members. | Per-task pricing and longer multi-step zaps can get costly at volume; complex logic is harder to read than in Make. |
A common pattern is to use Flow for everything inside Shopify, then hand off to Make or Zapier only for the steps that need an outside system, such as writing to a spreadsheet or posting to a team chat.
Test with real orders, not assumptions
Before switching any workflow on for all orders, run it against a few test orders or a narrow condition, such as a single tagged product. Check that tags land where you expect, alerts reach the right person, and nothing fires twice. Then widen it.
How automations quietly break, and how to stop it
Automations rarely fail loudly. They drift. A workflow that ran perfectly in spring stops matching orders in autumn because something upstream changed, and nobody notices until a customer does. The usual causes are predictable:
- Renamed tags. Someone tidies product tags from Pre-order to preorder and every workflow checking for the old spelling stops firing. Keep a short list of the tags your automations rely on and treat them as fixed names.
- New apps writing to the same fields. A subscription app, a returns app or a new shipping tool may add its own tags or notes. Check your conditions after installing anything that touches orders.
- Duplicate triggers. The same workflow built once in Flow and once in Zapier, by two different people, sends every alert twice. The shared list of workflows prevents this.
- Silent errors. A connected account gets logged out, or an API permission changes, and the workflow fails in the background. Turn on failure notifications in whichever tool you use, and send them to a person rather than a shared inbox nobody reads.
- Thresholds that never get revisited. A VIP threshold or reorder point that made sense at one sales volume makes little sense at double or half that volume. Review the numbers each quarter.
What to check each month
- Open each workflow's run history and confirm it has fired recently and at a sensible volume.
- Spot-check five orders the workflow touched and five it skipped, and make sure both decisions were right.
- Read the alerts channel or inbox for anything that was ignored, and ask why. Ignored alerts usually mean the condition is too broad.
- Update the shared list with any changes, including who now owns each workflow if the team has shifted.
That review takes well under an hour for six workflows, and it is the difference between automations the team relies on and automations the team routes around.
Getting these built without adding to your list
If your team knows these workflows would help but nobody has the hours to build and maintain them, that is the work we take on. Our company agent builder service designs and builds automations and AI agents around how your store actually runs, and our virtual assistance and admin support team can handle the review queues, reorder lists and customer updates these workflows create, so the flagged items actually get acted on.