Any ideas on this?

Sorry that you didn't get an answer right away. If you have questions that require a guaranteed response, I'd suggest the On Premise SLA support plan, or the Developer Support Services plan if your questions will involve code.

https://upendoventures.co...merce-On-Premise-SLA

https://upendoventures.co...ce-Developer-Support

As for your question, it's surprisingly the first time I remember being asked that. Right now, you're unable to use the DNN tokens without employing a workaround. You'll need to override the e-mail(s) in question by removing their task from the order workflow, and then replace the task with your own, where you can do your own token replacement. Documentation for all of this is below.

https://hotcakescommerce....Mail-Template-Tokens

https://hotcakescommerce....r-Workflow-Solution-

https://hotcakescommerce....ers-Programmatically

I've created a GitHub issue to have the DNN token engine integrated into the e-mail parsing in the future.

https://github.com/Hotcak...erce/core/issues/126

So, I tried to create a new workflow in which you can kind of override the e-mail.
However, I noticed that this only works in the NEW order process.

So when you send the order e-mail again from the backoffice, it completly ignores this workflow (I guess that is why it is called LoadProcess[b]New[/b]OrderAfterPaymentsTasks)

But then again, you would expect the order e-mail would look the same everywhere, if it is new, or resent or whatever...

So, my question I think is, what should I override to make sure the order [b]always[/b] uses the custom e-mail.