Order Confirmation Automation sends transactional emails with order details, product information, pricing, and shipping info immediately after a customer completes a purchase. You can customize content, add SMS or Push Notifications, and ensure customers receive confirmation for every paid order.

The trigger for this workflow is preset to Paid for Order. The order status must sync to Omnisend, which happens automatically for all direct integrations (Shopify, BigCommerce, Magento, WooCommerce) and those integrated via API v3.

⚠️ Omnisend does not automatically disable your store's default order confirmation email. You must manually disable or modify platform emails to avoid sending duplicate confirmations:

To create the Order Confirmation workflow:

The default trigger is set to Paid for Order. This ensures the automation fires only when the order status changes to Paid, sending a targeted order confirmation email.

You can target your automation more specifically in the trigger filter settings. The rule specified in the filter must be met before the automation triggers.

Example: If you trigger the workflow when an order has a specific tag, that tag must be added automatically by your platform. Otherwise, add the filter to a Split Condition later in the workflow.

Target your automation based on contact profile data (Country, Gender, Tag) or Segment membership.

⚠️ Note: Using Segments based on purchase behavior adds overhead to the system and may delay automation triggering. For time-sensitive confirmations, use Split Conditions instead.

You can customize your Order Confirmation workflow to send different emails based on specific order details. For example, use a Split block to send one version of the email for orders above a certain total price and another for lower-value orders, tailoring the message to match each customer's purchase.

The default exit condition is Order Status is Cancelled, meaning contacts exit the workflow after receiving all messages or if the order is cancelled. You can add up to 5 different exit conditions with up to 5 filters each.

You can choose to avoid triggering the workflow for contacts already in this automation, limiting how often the same contact enters the sequence.

You can add a Delay block at any stage and set it from immediately to several months.

💡 Recommendation: Set delay to immediate or don't use a Delay block for Order Confirmation. Customers expect confirmation emails within minutes of purchase.

Add Email, SMS, or Push Notification messages to your Order Confirmation sequence. Once you add a message block, provide all required details (sender email address, sender name, subject line, etc.). If information is missing, you'll see warnings like "Missing email information" or "Missing SMS information" to help you resolve issues before going live.

The Order Confirmation preset includes special content blocks that auto-populate with order data when the email is sent:

All information auto-fills when the email is sent to a customer. It is not stored locally, so you won't be able to preview it after the message is sent.

If the customer provides a phone number at checkout, they may expect a confirmation SMS. You don't need to collect SMS opt-ins to send order-related messages, but make sure customers know you'll use their phone number to send Order Confirmation via SMS.

Although you can't add full order details to SMS messages, you can include personalized data like order number, customer name, and order total.

Note: Contacts must have an email address recorded in Omnisend to receive order confirmation emails. Although Order Confirmation is transactional (not marketing), your Workflow Channel Settings (in the trigger block) control whether non-subscribed contacts receive emails or skip the email block. By default, transactional workflows send to all contacts regardless of subscription status, but verify this setting if emails aren't sending.

Order Confirmation reports are available in the Reports tab, like all other Automation Workflows. Reports include:

If your Order Confirmation automation isn't sending emails, follow these steps:

💬 Learn more: Troubleshoot Transactional Automations

Why are customers receiving two order confirmation emails (from Shopify/WooCommerce and Omnisend)?

Omnisend does not automatically disable your store's default order confirmation email. To avoid duplicates:

Do customers need to be subscribed to receive order confirmation emails?

Contacts must have an email address recorded in Omnisend. By default, transactional workflows (like Order Confirmation) send to all contacts regardless of subscription status. If emails aren't sending, check your Workflow Channel Settings (in the trigger block) and verify that contacts have email addresses recorded in their profiles.

Is it possible to show tax separately in the email?

Yes, you can show tax as a separate field in the Order total content block. Customize which pricing details to display (subtotal, tax, shipping, discounts, total).

You can manage price format under Store settings → Currency format. Learn more about Currency Format settings.

Why didn't the automation trigger for orders placed before I enabled it?

Order Confirmation automations cannot be triggered retrospectively. The automation only works for orders placed after the workflow is published and active. Orders placed before enabling the automation, or orders where the status change occurred more than 3 hours after the order was placed (common with imports or manual updates in WooCommerce/API platforms), will not trigger the workflow.