Order Finished Trigger Block

What’s in This Article

What this trigger does
When to use this trigger
When not to use this trigger
Block settings explained
Trigger frequency options
Common use cases
What data this block uses
Important things to know
Example automations
Best practices

What This Trigger Does

The Order Finished trigger fires when:

A contact completes an order, and
Patch receives a notification that the order is finished, and
The order data is available for the automation to use

In simple terms:
“Run this automation after someone buys something.”

When to Use This Trigger

Use Order Finished when you want to:

Send receipts, thank-you messages, or “what to expect next” instructions
Start a post-purchase nurture sequence
Trigger upsell/cross-sell offers based on what they bought
Send review requests for specific products
Track CLV / revenue milestones (ex: “spent over $250”)
Create VIP tagging based on purchase amount or product category
Run win-back campaigns for people who stop purchasing

When Not to Use This Trigger

Don’t use Order Finished if:

You need to automate based on visits/check-ins (use Check-In Finished). Orders happen when the contact makes a purchase. Check-ins happen when they show up to the location.
You need reminders for a scheduled appointment or booking time (use a calendar/event trigger)
You don’t have reliable order data flowing into Patch (confirm the integration/source first)
You need to trigger on an abandoned cart or incomplete checkout (use an abandoned/checkout trigger if available)

Block Settings Explained

Details (Info Panel)

This section explains:

How the block is triggered
When to use this block

It’s informational only—no settings here change behavior.

Add Conditions

Use Add Conditions to control which orders can trigger the automation.

Common examples:

Only run if Order Revenue is greater than $X
Only run if Product Name contains “Membership”
Only run if Product Category = “Birthday Party Add-ons”
Only run if RFM = 555 (loyalists)
Only run if SMS Opt-In is true (for SMS messages)

Important: Conditions are evaluated when Patch receives the finished order event.

Configure Trigger Frequency

This section controls how often the trigger runs for the same contact, based on the count of orders that match your rules.

Frequency option 1: One time at a certain number of orders

Use this when you want the automation to run once when a contact hits a milestone order number.

Examples:

Run on the 1st order only (first purchase welcome)
Run on the 3rd order only (loyalty reward)

Frequency option 2: Every X orders

Use this when you want the automation to repeat on a pattern.

Settings you’ll see:

Number of orders

This is the “X” in Every X orders.

If you enter 2, the automation runs every 2 orders.

Starting with order

This sets where the counting begins.

Examples:

Start at 1 → runs on 1, 3, 5, 7…
Start at 2 → runs on 2, 4, 6, 8…
Start at 5 → runs on 5, 7, 9, 11…

Common Use Cases

First purchase “welcome” + instructions (order #1 only)
Membership upsell after day-pass purchase
Post-purchase review request for the exact product they bought
Cross-sell add-ons (gloves, socks, food, party extras, etc.)
High-spend VIP tagging (total spend over $X)
“Come back soon” offer after a purchase
Loyalty milestones (every 5 orders, reward message)

What Data This Trigger Has Access To

Order Finished includes more data than Check-In Finished.

Order Finished trigger data includes:

Revenue / order totals (amount paid, totals, etc. based on your source)
Product data (product names, items, quantities, categories—based on your integration)
Order metadata (order ID, time, location/source—based on your integration)
Contact data (standard + custom fields)

Important Things to Know

This trigger runs when an order is finished and Patch receives it.
Some order sources sync periodically (not in real time). If you need immediate messaging, confirm whether your system sends orders instantly or in batches.
If a contact places multiple orders quickly, frequency settings help prevent over-messaging. The Throttle Action block can also help with this.
Use conditions to avoid sending the wrong follow-up (ex: don’t upsell a membership to someone who already bought one).

Example Automations

Example 1: First Purchase Thank You (Order #1 only)

Trigger: Order Finished
Frequency: One time at a certain number of orders → 1
Send SMS/Email: “Thanks for your order! Here’s what to expect next…”

Example 2: Upsell Membership After Day Pass

Trigger: Order Finished
Condition: Product Name contains “Day Pass”
Delay: 1 day
Send SMS: “Want to upgrade to a membership and save on every visit? Here’s the link.”

Example 3: Review Request for a Specific Product

Trigger: Order Finished
Condition: Product Category = “Retail” (or Product Name contains “Gloves”)
Delay: 2 days
Send SMS/Email: “How was your new gear? Want to leave a quick review?”

Example 4: VIP Tag for High Spenders

Trigger: Order Finished
Condition: Order Revenue ≥ $250
Action: Add Tag “VIP”
Send SMS: “Thanks for being a VIP! Here’s a perk for your next visit.”

Best Practices

Use Order Finished for revenue-based journeys (post-purchase, upsell, loyalty).
Use conditions to personalize by product, category, or spend level.
Use One time for first-order experiences and special milestones.
Use Every X for repeat buyer rewards (but don’t overdo it).
Add delays for review requests (don’t ask immediately after purchase).
Always confirm the contact has the right SMS/email consent before messaging.