Currently, new order emails, etc. are sent to the customer’s billing email address if it differs from the one that is on their customer profile.
This would allow a workflow to use the customer’s billing email address, making it more consistent with the other shop emails.
Open
Last updated: March 23, 2020
Log in to comment on this feature request.
For anyone still wanting this, I have written a snippet here, which will allow you to add it the order.billing_email variable. Tested and works (but does not show the updated email in the queue in admin)
https://gist.github.com/solaceten/7f03aed8c3b232742b1f6fb7777d8776
This is an essential request. In our set up, we use “customer.email” as the agent, and the order.billing_email for the end user. We desperately need to be able to send follow ups to {{ order.billing_email }}
For god’s sake, just add this {order_billing_address} variable. Currently, you’re forcing the customers to register an account before they can purchase anything, but many customers just don’t want to register. We’re losing many many anonymous customers! People’s buying habit is changing, not everyone wants to have an account with your website, just let them use their a billing email address.
It is crucial widely used but i have the feeling that noone really cares about this requests. Would be great if someone made that happen.
Why hasn’t this been implemented yet? This thread started over 3 years ago. The act of adding a simple {{ order.billing_email }} (and hopefully also a {{ subscription.billing_email }} ) should be trivial for the developers. If we go by votes – this is on page 7. Likely will never get added. Voting on suggestions to bring features to fruition is HORRIBLE to prioritize development. The developers should review these and then pick a few that make sense and put THOSE to a vote on which order to add them in. That’s the better way to do this.
Please make this happen, somebody! this is a crucial and wide used function. need billing email to be a variable!
yes, please make this happen! we need order.billing_email as a variable!
Please! Not having the option to send to billing email hurts. Even using this
{{ subscription.meta | key: '_billing_email' }}
doesn’t workDan Bitzer: No worries, just wanted to make sure I wasn’t doing anything incorrect.
Charles Stanisce: You are correct. Sorry, my previous comment wasn’t right. The
{{ customer.email }}
variable will use the user account email not the order billing email.Dan Bitzer: Hi Dan, I just sent out a manual workflow through AutomateWoo for all pending payment orders. It did not send it to the billing email address associated with the order. I just double checked the AutomateWoo log. Not sure if there is another setting?
Yes x100. We have so many customer/users that give us different emails for their billing invoices to be sent to. 9 out of 10 emails that we send through AutomateWoo are in regards to billing/invoice issues. This variable should send the email to the default billing email already associated to the account through WooCommerce, and if it doesn’t have one, default to the regular customer email address.
Adam Marshall: The
{{ customer.email }}
variable will actually use the billing_email field from the order data if there is an order present in the workflow data. The same applies for subscriptions. So all order and subscription triggers do NOT use the customer profile billing email.Exactly! I’m surprised this is not yet part of it too. Such a fairly straight forward Variable. In addition, please add {{ subscription.billing_email }} too (this one would affect me more and should be added the same time)
Exactly!
If a customer’s billing email address of an order is different from their account email address, all standard transactional emails are sent to the billing address.
If we want to send follow-up emails with AutomateWoo, currently we can only use the {{ customer.email }} variable (i.e. their account’s email address).
So, if we haven’t created new custom templates for all transactional emails (and sent them to their account’s email address), those customers could receive some emails on their account’s email address and some emails on their billing email address.
To avoid confusing them, we need to be able to use the {{ order.billing_email }} variable.