As custom calculations works differently from regular calculations creating an automatic selector may create issues. Instead you can try enabling it with Update Ticket Calculation action after first item added to ticket. (eg. ticket state changes from new to new orders).
Might be a nice sample for implementing some unusual calculations.
@madiha what @emre just suggested works great I just tested it on your db. Much cleaner and easier to do and less chance of conflicts with rule events.
However one issue still remains @emre and I know you fixed it with the test versions we are testing but 4.1.82 it still rounds 0. Even with custom calculation.
Example if ticket total = 0 it adds .05 to ticket. or if total = 4.40 it makes it 4.45
I noticed in the latest test version we are using it does not do this.
BTW I found a workaround that works… use the custom calculation as @emre described then add a Ticket Total Changed rule and put in an Update Ticket Calculation action with Remove Calculation set to true.
Sometimes exploring things is good. It helps you get an understanding you wouldn’t have if someone just gave you the answers. But yeah I am glad you got an answer that works for you. It also helps Samba grow if more people attempt things and break things vs just getting step by steps all the time.
You typically will test things so I didnt really direct those comments at you.
how do i mention rounding rate is custom
Update Ticket Calculation action after first item added to ticket. (eg. ticket state changes from new to new orders