13
Add usage of subscription variables with order triggers
complete
Dan Bitzer
complete
This feature is shipping this week! Check out the update post for details on how this works in AutomateWoo 4.8 - https://woocommerce.com/posts/automatewoo-4-8/
A
Amber
Dan Bitzer: This is freaking brilliant! This is going to make my life soooo much easier. Thanks bunches!
Out of curiousity, would be possible in a future version to see a variable that lists all order numbers with a specific status (possibly with a link to either view or pay). Something like {{order.number_list | status: 'pending-payment'}}. That way we could pair a list of late orders.
Example:
----
Hi Name,
This is an automated reminder that the following invoices are past due:
- List of Orders (maybe prices and dates) {{order.number_list | status: 'pending-payment'}}
- Maybe an Order Total for all the above invoices {{order.number_list_total | status: 'pending-payment'}}
-----
That would be the icing on this already deeelicious cake and would pair really nicely with this new trigger. If not, no worries but seriously, thanks again for rolling this out. <3
A
Amber
Also, for anyone else following that this has been completed let me show you why it's so powerful.
With the implementation of these new triggers we can now create "Past Due" email notices that fire to clients (if the subscription renewal order hasn't been payed x days after it was generated) and they can look something like this. 👇😍
Dan Bitzer
Amber: Thanks so much for the feedback! Great to hear this feature is making life easier :)
Do you mind opening a new idea for the "order list" variable idea? I think it's a great idea!
Dan Bitzer
Update: This work has been finalized and is ready for release in AutomateWoo 4.8 later this month.
Dan Bitzer
in progress
We're starting work on this feature.
A
Amber
Woo hoo! Super excited!
A
Amber
Dan Bitzer: Any rough ETA? :)
Dan Bitzer
Hi Amber! This is in the final stages and is confirmed for our next release.
Most of our timing estimates have been delayed because of the transition to Automattic (https://automatewoo.com/blog/announcement-were-joining-automattic/) but we're planning to release the next version in October or November.
Dan Bitzer
Joey Ricketts I think this is probably a good idea. My only concern is that orders are usually not related to a subscription and many orders won't have a subscription linked with them.
Some triggers like 'Subscription Renewal Payment Complete' and 'Subscription Renewal Payment Failed' have both subscription and order data because every renewal payment has an associated order.
Can you give some more details on a specific use case where this is needed?
A
Amber
Dan Bitzer: Hey Dan,
Joey added this feature request after a conversation with me about my use case of AutomateWoo with Woo + Subscriptions; something that I'm also sharing with colleagues who are planning to have a similar setup.
I'm using Woo + Subs in an out-of-the-box type way. Essentially I've got my setup configured as a billing platform for my services.
For example, I have clients that are set on "Manual" subscriptions, and these clients pay by Cheque or e-Transfer. Due to how Subscriptions works, I go in the day before their next renewal order would generate, and change the status of the subscription to "Active" so that it generates the next order (otherwise it won't), even if the previous renewal order is Pending Payment. This essentially allows the customer to have a "late invoice/order."
AutomateWoo comes in super handy because I can trigger that Subscription status change automagically now, AND I can fire off a "Late Payment" email (i.e. 15 days past due) for those Manual subscription customers.
The only issue is that if I use the "Order" Trigger (i.e. Order Status - Pending Payment) and assign it rules like "Order Is Subscription Renewal - Yes" I unfortunately still can't take advantage of the subscription variables such as "Next Payment Date" or "Subscription Total" etc.
For example, I'd love to be able to include something like the following in an email but I can't:
Your last payment was on: {{ subscription.last_payment_date | format: 'm-d-Y' }}
Your next Invoice of {{ subscription.total }} will auto generate on: {{ subscription.next_payment_date | format: 'm-d-Y' }}
Hopefully that gives you a better understanding of a use case where it'd be beneficial to open up the subscription variables to other triggers, or maybe a combo of a trigger + specific rule.
Dan Bitzer
Amber: Thanks for the detailed explanation!
A
Amber
Dan Bitzer:
Any news on if you have plans to implement any subscription variables with order triggers. :)
Dan Bitzer
Amber: We're aiming to address this soon but at the moment we are working on other features.
This idea has a lot more votes since I last saw it so I'm putting higher on our list :)
C
CH
Dan Bitzer: Ooh any updates on this? This is certainly a missing piece in the puzzle! :D
Dan Bitzer
CH: I'm afraid there are no updates right now. Development on AutomateWoo has been paused for a couple of months while we settle in at Automattic. https://automatewoo.com/blog/announcement-were-joining-automattic/
A
Amber
Dan Bitzer: Well that's a bummer to hear (the update freeze for a few months part) after patiently waiting almost 9 months. :(