I’ve always grouped the order with the parent order. I’ve never allowed them to merge.
Nope;
Negative price isnt the issue, normal tags applied manual with negative value work fine. Printed total and ticket order total lines are corrent with lines merged through printing.
The issue is specific to the adjust order price action tags.
I’m kinda late to the game but I was thinking what if you have a rule that fires if a kids meal is on the ticket and then parse the ticket order’s order tags and if AM is > 0, set PR == AM then AM == 0.
JTR have you tried setting it to Use Order Price as false? Also could you pm me a copy of the database so I can check it?
I did, have tried all options i could think of;
Will send shortly.
Had to send weetransfer link as exceeded forum 10mb limit even after clearing transactions
Have enabled daily offer to work any day, search discount in rules for related rules. Other daily deals using the adjust order price action are just unmapped at the minute.
{PLAIN TOTAL} also effected.
In summary issue hapens with print merge lines enabled.
2x order line doesnt cause issue
1x and 1x merged does
Include in order price or not makes no difference.
Also after you comment of 1 for 1 is not intended use, have tested with 2 get 1 free, and same issue…;
FWI {ORDER TAG PRICE} and {ORDER TAG TOTAL PRICE} dont work with adjust order price tags.
{ORDER TAG TOTAL} returns the total of 1x the tag value/price…
Also not adding 2 seperate orders with same negative order tag (manually added);
These two order lines merge without issue on print.
And for completeness those 2 orders on their own ticket;
With 3rd just to give a value for ticket total.
FWI {ORDER TAG PRICE} and {ORDER TAG TOTAL PRICE} dont work with adjust order price tags.
{ORDER TAG TOTAL} returns the total of 1x the tag value/price…
This is not the case for a normal manually added order tag with minus value, price based order tag values return as expected.
As sugested before I am pretty sure the issue in the print merging process is only calculating 1x the order tag amount.
The issue is seperated from non adjust order price tags as tags created by this action use seperate key in the order tag JSON;
AM: rather than usual PR:
Which would explain why the {ORDER TAG PRICE} expressions dont work for the action created tags.
Technically it is modifying the order and not just applying tags. It looks like there might be something happening. We will look at it.
Finally, just to confirm it is specific to the merging in print processing setting to dont merge makes all values as they should be;
Been thinking about that and yer, kind of get whats happening, its not a normal tag as potentially could lead to a loop crash if tag changes order price it is causing its own update…
So its using its own subsystem piggybacking on order tags.
This all to me points back to the origional presumption, given that all onscreen is ok is that the code relating to the tag amount use by adjust order price action isnt accounting for merged quantity.
Did this bug ever get looked into?
Live system is a few versions old so am relying on a dirty hack of adding a HHmmss free tag if its is a applicable product for daily deals;
