That is the kind of thing that we are lacking which would make prices lists more powerful.
{PRICE:X} being a order level.
Would be good to have a {TICKET TOTAL:x} which would solve my previous question of a way to calculate on template the saving. so long as we could call the ‘normal’ rice list in some way/
Ie
[={TICKET TOTAL:Normal}-{TICKET TOTAL:{ENTITY DATA:Customers:Price List}}]
on customer entity would show their savings 
1 Like