The moment it happens

Flag risky WooCommerce orders before you ship

Orders that match your warning signs are posted to Slack and noted on the order itself.

Runs: The moment it happens
Apps: WooCommerce
AI: Not needed
Access: read+write

Send this to your assistant

Create a ClickRuntime automation: when a WooCommerce order comes in, flag it in #orders on Slack and add an order note if billing and shipping countries differ, the total is over $500, or it's a first-time email buying more than 5 items.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Add to ChatGPT Add to Claude

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

A WooCommerce shop that ships quickly is a target for card fraud. A stolen card is used for a high-value order, shipped to an address that does not match billing, and the real cardholder disputes the charge weeks later. The shop loses the goods, the payment and a chargeback fee, and a few of these can wipe out a month's profit. Reviewing every order by hand is not practical, so risky ones often ship before anyone looks twice.

When an order arrives, the automation applies your rules, such as a large total, a different shipping and billing country, a free email address on a high-value order, or several orders from one address in a short time. It can ask ClickRuntime's built-in AI to add a short risk note. Flagged orders are posted in Slack and an order note is added in WooCommerce.

It helps shops that ship physical goods and carry real chargeback exposure.

What you get out of it

Hold the order before it ships
A flag right after payment gives you time to check the details or contact the customer before the parcel leaves. Once it is shipped, a stolen-card order is gone. Contacting the customer first often settles whether the order is genuine within a single phone call.
Fewer chargebacks
Each chargeback costs the goods, the sale and often a fee. Even catching a few risky orders a month usually pays for the time spent reviewing. That is real money saved with little ongoing effort.
Reviewers focus on the few
Instead of checking every order, staff look at the handful that match your risk rules, which keeps the process light enough to continue. A short list is far more likely to be reviewed carefully than a long one.
Reasons are written on the order
The note added in WooCommerce records why it was flagged, so anyone who opens the order sees the concern and does not have to repeat the analysis. The next person on shift sees the concern without needing a separate message or meeting.
Rules you can tune
If too many good orders are flagged, tighten the rules, and if fraud slips through, add one. The rules match your own experience. Over a few months, your rules become a record of the patterns that matter to your shop.

How it works

What happens, step by step

When a new order is placed in your WooCommerce store, ClickRuntime checks it straight away.
It looks for warning signs: a billing country that differs from the shipping country, a total over $500, or a first-time buyer ordering more than five items.
If any apply, it adds a note to the order in WooCommerce explaining why it was flagged.
The same reasons are posted to your #orders Slack channel so someone can review the order before it ships.

Before it runs live

Connect WooCommerce
Paste your automation's link into the other app's webhook settings

What you get

RunsThe moment it happens

Flag risky WooCommerce orders before you shipjust nowSucceeded

Slack · #orders⚠️ Order #5530 (k.west@acme.example): Flagged for review: billing US vs shipping NG; total 742.00 USD

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.

Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

Changes you can ask for

Act only on the items that match your own rules, and skip the rest
Add an AI step, for example to summarize, sort or draft a reply
Add another app, for example also send it to Slack
Combine it with other WooCommerce steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.

suspicious_order_alert.pyexample

from clickruntime import on_event, credentials, http, notify

STORE = "https://yourstore.com/wp-json/wc/v3"

@on_event
def handle(event):
    o = event.json
    auth = (credentials.secret("WC_CONSUMER_KEY"), credentials.secret("WC_CONSUMER_SECRET"))
    reasons = []
    if o["shipping"].get("country") and o["billing"]["country"] != o["shipping"]["country"]:
        reasons.append(f"billing {o['billing']['country']} vs shipping {o['shipping']['country']}")
    if float(o["total"]) > 500:
        reasons.append(f"total {o['total']} {o['currency']}")
    items = sum(i["quantity"] for i in o["line_items"])
    if items > 5:
        past = http.get(f"{STORE}/orders", auth=auth, params={"search": o["billing"]["email"], "per_page": 2}).json()
        if len(past) <= 1:
            reasons.append(f"first-time buyer with {items} items")
    if not reasons:
        return {"flagged": False}
    note = "Flagged for review: " + "; ".join(reasons)
    http.post(f"{STORE}/orders/{o['id']}/notes", auth=auth, json={"note": note}).raise_for_status()
    notify.slack(f"⚠️ Order #{o['number']} ({o['billing']['email']}): {note}", channel="#orders")
    return {"flagged": True, "reasons": reasons}

FAQ

Common questions

Does it cancel orders automatically?

No. It flags the order and posts it for a person to review. Automatic cancellation risks refusing genuine customers, so the decision stays with you, and the order note records what was noticed. You remain in control of the final decision.

Which signs does it look for?

Typical ones are a high order value, mismatched billing and shipping countries, a free email address on a large order, and repeated orders from the same address. You choose which rules apply. Other rules can be added if you see another pattern.

How does the AI risk note work?

If you enable it, ClickRuntime's built-in AI reads the order details and writes a short comment on why it looks unusual. It is an aid for the reviewer, not a verdict, and needs no separate AI key.

What permissions does it need?

read+write. Nothing else in your accounts is used.

Does it need AI?

No. It runs without AI, so it doesn't use your plan's AI allowance.

How many runs does it use?

One run for each event the app sends.

Can I change how it works?

Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

The moment it happens