Announcing AutomateWoo 3.0

In the next few days we will be releasing a major update to AutomateWoo, version 3.0. This update makes a significant and exciting change to customer management and we want to make sure you are aware of what is changing before update is available. Version 3.0 also includes some new features and improvements which we will discuss in this post.

Goodbye ‘users’ and ‘guests’, hello ‘customers’

The biggest change in AutomateWoo 3.0 is the introduction of a new customer data type which can handle both registered users and guests. Previously, AutomateWoo treated users and guests separately, since in WooCommerce both are technically very different. This was often a source of confusion and made the development of triggers overly complicated in many cases.

So what will actually look like? The good news is that you don’t have to do anything, we will handle the migration automatically and any custom functions you have written should be backwards compatible. After updating to 3.0 you will be prompted to complete a database upgrade which you should do immediately, this upgrade is crucial to keep your workflows running.

The changes related to the customer data type include:

  • All user variables have been renamed, e.g. {{ user.email }} will be now {{ customer.email }}
  • All user rules have been renamed e.g. User Order Count will be Customer Order Count
  • All user actions have been renamed e.g. Add Tags To User will be Add Tags To Customer
  • All user triggers have been renamed e.g. User Order Count Reaches will be Customer Order Count Reaches

These variables, rules, actions and triggers have been modified so that they now support guest customers. For example:

  • The trigger Customer Order Count Reaches now supports guest customers
  • The trigger Customer Total Spend Reaches now supports guest customers

Please note that you can always target only registered customers or only guest customers by using rules.

A complete abandoned cart rebuild

From a technical viewpoint, abandoned carts have been completely rebuilt in AutomateWoo 3.0. The major benefit of the rebuild is a massive performance improvement but additionally, all abandoned cart triggers now support the new workflow timing options allowing for more targeted scheduling.

We’ve also added an abandoned cart trigger that make use of the new customer data type and therefore works for both for both guests and users.

For technical and UX reasons, carts now have status property which can be either active or abandoned and there is now cart active timeout setting, which defaults to 15 minutes. This means any active cart will become abandoned if it’s inactive for 15 minutes, and once that happens any abandoned cart triggers will fire and add any workflows to the queue.

Again, there is no changes required for this, everything will be migrated along with the 3.0 database upgrade.

MailChimp for WordPress integration

A highly requested feature this year has been to send customers unique coupons after they subscribe to a MailChimp list. Since AutomateWoo doesn’t have subscribe form functionality we integrated with the popular MailChimp for WordPress plugin and created a new trigger that fires after a subscription occurs.

‘Fixed’ timing for workflows

A smaller addition to version 3.0 is a new workflow timing option called ‘fixed’. This option simply allows a workflow to be scheduled at a fixed or static date and time.

Product reviews

This update also introduces a ‘review’ data type and adds new trigger, New Review Posted, which will replace the now deprecated User Leaves Product Review and Guest Leaves Product Review triggers. This change reduces the effort required to create review reward workflows and also lays the groundwork for future review features.

Other minor changes

  • Various admin UX improvements
  • Add a new trigger: Subscription Created
  • Add a new variable: product.description
  • Added new rules: Subscription Items and Subscription Item Categories
  • Improved error handle of queued workflows, events are now marked as failed if a fatal error occurs while running
  • Fixed a few issues with the manual trigger tools

As this is major update, it’s a good idea to test the update in a development environment especially if you have are running any custom code for AutomateWoo. If you have any questions, concerns or feedback don’t hesitate to get in touch via email or in the comments below.

About the author

After developing custom WordPress themes and plugins for several years, Daniel Bitzer wrote the first line of code for AutomateWoo in 2015. He hails from Australia but loves to travel and work abroad.

  • frydmancom

    Hey Daniel, this looks great. Is it backward compatible to 2.5.x or do you have to be on 2.6.x or later to enjoy these features?

    • Dan Bitzer

      Yes we’re still backwards compatible to WooCommerce 2.4.0

      • frydmancom

        Awesome – thanks. Will go update and let client know they can use all of this lovely stuff.

  • Great updates. You guys are awesome, keep up the great work.

  • You rule Dan!!!!!

  • David Darke

    NICE!

  • Pingback: Weekly Roundup: June 9, 2017 – Sell with WP()

  • fariazz

    Looking forward to it, I was just about to implement it so will wait for the new version.

  • Dan Bitzer

    Thanks all, this update is now available!