Order Submitted trigger

Managing post-purchase actions efficiently is crucial for any business. The Order Submitted Trigger in Stack automates workflows based on completed orders, whether from 1-Step or 2-Step order forms. This guide will help you understand what this trigger does, how it differs from other order-related triggers, and how to configure it for optimized workflow automation.

What is the Order Submitted Workflow Trigger?

The Order Submitted Trigger activates a workflow when an order is placed through an order form. Unlike basic order form triggers, this trigger captures both primary purchases and upsell transactions, making it ideal for:

• Sending order confirmation emails
• Automating upsell follow-ups
• Updating customer records with order details
• Segmenting customers based on purchase behavior

This trigger supports custom values, allowing businesses to dynamically reference product names, quantities, prices, and payment methods inside workflows.

Key Benefits of the Order Submitted Workflow Trigger

• Automated Engagement: Sends order confirmations and upsell offers instantly.
• Increased Revenue: Enables upsell workflows to boost sales.
• Time-Saving Automation: Reduces manual order management tasks.
• Detailed Order Insights: Captures product and payment data for better automation.

Order Submitted vs. Order Form Submitted

Understanding the difference between these triggers is essential for choosing the right one for your automation.

Feature	Order Submitted	Order Form Submitted
Trigger Activation	Fires for each product purchase (Primary, Bump, Upsell)	Fires once per order submission, regardless of products purchased
Filter Capabilities	Can filter by product, price, source, submission type	No filtering by product/price
Custom Values	Provides order details like product names, prices, quantities	Limited order details available

Configuring the Order Submitted Workflow Trigger

Add Order Submitted Trigger

1. Navigate to the Automation tab and select Workflows.
2. To create a new workflow, click + Create Workflow. To add the trigger to an existing workflow, find and open the desired workflow for editing.
3. Click on Add New Trigger and search for “Order Submitted”. Select it from the list.

Applying Filters

Filters allow you to fine-tune your workflow trigger by specifying conditions based on order details. This ensures the automation runs only when certain criteria are met.

Global Product

This filter triggers the workflow based on a specific product or price.

• Is: Triggers the workflow only when the specified product is purchased.
• Is Not: Excludes the selected product, ensuring the workflow runs for all other products except the one specified.

Order Source

Determine where the order was placed to ensure the workflow triggers only for purchases from a specific source.

• Options: External, Form, Membership, Order Form, Payment Link, Store, Survey
• Operators:
  • Is: Triggers only for the selected order source.
  • Is Not: Excludes the selected order source.

Sub-Source

Refine the Order Source further by targeting specific funnels, pages, or subcategories.

• Operators:
  • Is: Triggers only when the order matches the selected sub-source.
  • Is Not: Excludes orders from the selected sub-source.

In Funnel/Website

Ensure workflows trigger only when an order form is submitted through a specific funnel or website.

• Operators:
  • Is: Triggers only if the order is submitted through the selected funnel or website.
  • Is Not: Excludes orders from the selected funnel or website.

Page Is

Trigger workflows only when an order form is submitted on a specific page within a funnel or website.

• Operators:
  • Is: Triggers only when the order is submitted on the selected page.
  • Is Not: Excludes orders from the selected page.

Submission Type

Trigger workflows based on the type of purchase made.

• Primary: Initial product purchase.
• Bump: Optional add-ons during checkout.
• Upsell: Offers presented post-checkout.

Product Price

Trigger workflows based on the specific price of a product.

• Operators:
  • Is: Triggers when the product is purchased at a specific price.
  • Is Not: Triggers when the product is purchased at any other price.

Enable “Allow Multiple”

To ensure seamless automation for both primary purchases and upsells, enable the Allow Multiple setting. This allows the workflow to trigger separately for each purchase event.

• When Allow Multiple is ON: The workflow can trigger multiple times for the same contact.
• When Allow Multiple is OFF: Any upsell purchases made by the customer won’t trigger a new instance if the workflow is still active from the primary purchase.

Frequently Asked Questions

Q: Does this trigger work with upsell purchases?
Yes, the Order Submitted Trigger fires for both primary purchases and upsells, provided Allow Multiple is enabled in workflow settings.

Q: Can I use this trigger to send order confirmations?
Yes, you can automate order confirmation emails and use the Shopping Cart element to include product details dynamically.

Q: How do I ensure the workflow only triggers for a specific product?
Use the Global Product filter and select “Is” or “Is Not” to include/exclude specific products.

Q: Will this trigger affect my existing order form workflows?
No, the Order Submitted Trigger works independently from the Order Form Submitted Trigger, allowing more granular control over workflow execution.

Q: Can I trigger workflows based on the payment method used?
Yes, you can apply filters based on the payment gateway (Stripe, PayPal, etc.) to trigger different workflows for different payment methods.

When Does the Order Submitted Trigger Activate?

The trigger activates when a 1-Step or 2-Step order form is submitted, and it also fires upon an upsell purchase. If a customer buys products A and B on an order form and product C as an upsell, the trigger will activate twice: once for the initial purchase and once for the upsell.

Important: Ensure the Allow Multiple setting is enabled in Workflow Settings if you want the trigger to activate for both primary and upsell purchases. Avoid using wait steps if you plan on selling upsells or bumps for the same product, as they can prevent the trigger from activating multiple times for the same contact.

Note: This feature is only compatible with version 2 funnels.

Differences from the Order Form Submitted Workflow Trigger

Here are the key differences between the Order Submitted and the Order Form Submitted triggers:

• Single Checkout Object: The Order Submitted trigger does not activate multiple times for multiple product purchases within the same session.
• Direct Filtering: You can filter the trigger based on global product/price, a feature not available in the existing trigger.
• Custom Values: Utilize order-related custom values within workflows, including customer details, order information, coupon codes, and payment gateway data.

Note: Custom values will only appear in the dropdown if the Order Submitted Trigger is part of the workflow steps.

Sending Order Confirmations via Email Templates

You can use an email template to send order confirmations by incorporating the Shopping Cart element. This element automatically populates product details like quantities, images, and prices.

Tip: Add custom images for your products in the Payments ➝ Products page to ensure the Shopping Cart element displays the correct visuals. If no image is added, a default image will be used.

To send an email confirmation, ensure the Shopping Cart element is included in your template, and the template is linked in the workflow’s Send Email action.

Understanding Submission Type Filters

• Primary: Activates if any primary product is purchased at checkout.
• Bump: Activates only if a bump product is purchased.
• Upsell: Activates only for upsell purchases. It does not trigger on the initial order form submission for primary or bump products.

Impact on Existing Order Form Submission Triggers

The Order Submitted trigger does not affect existing order form submission triggers. However, using the Order Submitted trigger is recommended to leverage order-related custom values and coupon information.

Available Filters, Conditions, and Custom Values

Trigger Filters

1. Product

   • Operators: is, is not
   • Selectable Items: Global product name

2. Price

   • Operators: is, is not
   • Selectable Items: Price Name

3. Order Source

   • Operators: is, is not
   • Selectable Items: Order form

4. Submission Type

   • Operators: is, is not
   • Selectable Items: Primary, Bump, Upsell

5. Funnel

   • Operators: is, is not
   • Selectable Items: Funnel names

6. Page

   • Operators: is, is not
   • Selectable Items: Page inside funnel

If/Else Conditions

• Order Source
• Product
• Payment Gateway: Stripe, Paypal
• Order Total: Numeric operators
• Submission Type
• Funnel

Custom Values

Order

• Currency symbol ($)
• Currency code (USD)
• Cart Total
• Order total
• Coupon code
• Total discount
• Created on
• Created at
• Order ID
• Payment Gateway

Customer

• ID
• First Name
• Last Name
• Name
• Email
• Phone
• Full Address
• City
• State
• Country
• Postal Code

These tools and settings allow you to efficiently manage upsells and order confirmations, enhancing your customer interaction and sales strategy with Stack.

Key Benefits

• Automation: Simplify post-purchase tasks such as sending confirmation emails and notifications.
• Improved Customer Experience: Ensure timely follow-ups after a payment is completed.
• Data Management: Automatically update records when an order is submitted.

How to Use the Order Submitted Trigger

1. Navigate to Automation Settings.
2. Select Payment Links Workflow.
3. Enable the Order Submitted Trigger.
4. Configure actions such as:
   • Sending confirmation emails.
   • Updating customer data.
   • Notifying relevant teams.
5. Save and activate the workflow.

PayPal Support for Recurring Invoices

Stack allows businesses to offer PayPal as a payment method for recurring invoices, provided autopayment is not enabled.

Key Benefits

• More Payment Options: Customers can choose PayPal for recurring invoices.
• Improved Usability: Supports businesses relying on subscription-based or repeat billing models.
• Enhanced Customer Satisfaction: Provides flexibility in payment methods.

How to Enable PayPal for Recurring Invoices

• Ensure that PayPal integration is active in your system.
• Note that PayPal does not currently support auto-payments for recurring invoices. Ensure autopayment is not enabled.
• Your customers can now select PayPal as a payment method when paying their invoices.