# Sell 6 with price of 5

#21

Your tags are singular PBar but you action shows plural PBars

#22

thanks
i also corrected Promotion as it was without o
and finally it works

now lets move on to a more complex step
i want if i sold 9 to cancel the (Buy 5 Get 1 Free) and use (Buy 9 Get 3 Free)

i tried to make it by giving another free item when it reaches 9 and then when it reaches
12 another item will be free from the (Buy 5 Get 1) then it’s like (Buy 9 Get 3 Free)
as if i made this equation:
(B9G3) = (B5G1) + (B9G1) +(B5G1)
but i faced 2 problems:

1. the free item of the first (B5G1) is the first and so it is for the (B951) and this makes it decrement the price only 1 time for one of the 2 promotions

and when i select 12 it uses the second (B5G1) as it applies it on another item

so, how to make the free item not the same?

2)if it works it will be too many tags

is there any other way to cancel the first tag and add another tag?
i know that it’s poor explanation but this is the best i can do

#23

and it overwrites the (Buy 5 Get 1 Free) and it works fine for 6 ,12 ,18 but for 24 it makes 7 free instead of 6 and this is because it makes 2 (Buy 9 Get 3 Free) and 4 (Buy 5 Get 1 Free) but 3 of them are already used in the 2 (Buy 9 Get 3 Free)

simply my question is how to prevent using (B5G1) when using (B9G3)?

#24

Could you not combine separate offers rather than replace so it would be the difference?
Not tried, just an idea.
So buy 5 get 1, 9 get 2extra free etc? The extra free being the key term.
Again, not tried just a thought.

#25

thanks for help
but (B5G1) gives 1 free for every 6
this means that when i buy the first 6 one of them will be free and for the second 6 another 1 will be free and for
18 pieces 3 products and so on…
and for (B9G3) for the first 12 it gives 3 free item and for 24 piece 6 free and so on
my main problem is that i want to choose which items to apply the promotion on because they overwrite each other
in other words i want to remove the (B5G1) tag for items using (B9G3)

#26

what happens that:
for 6 pieces it applies (B5G1) on item X
and then for 12 it applies (B5G1) again on Y and applies (B9G3) on X Y Z
seems good ^^

for 18 it applies (B5G1) again on M
it’s fine till now
for 24 items it applies (B5G1) again on N
and applies (B9G3) on N O P
totally (B5G1) --> X Y M N
(B9G3) --> X Y Z N O P
total free items X Y Z M N O P
which are 7 not 6
thats why i’m saying we need to make them making tags on different items

hope i could explain it well this time

#27

Not much clearer but understand the issue.
Ok.
I e not had huge experience with this action yet so can you show your rule?
I have a solution in mind just need to see the rule.

#28

same for B9G3 but in another one
poor rule i know but i’m just a beginner

#29

Ok, this may work, may not.
Firstly I would recreate the promo rule using [:field name] where field name is the name of the field.
That will allow you to reuse one action multiple times in the rule.
Then we will have multiple promo actions using the same tag name and constraint them based on a report expression counting the number of applicable items.
Make the action and post a screenshot then we will discuss the rule.

#30

i tried to understand but i did not
can u tell me again what should i do
as i told you i’m a beginner

#31

Make a generic action like this one except for the adjust order prices action;

You will want to call it say ‘Generic X for Y items’
Hard code function to x for y and order tag name to promotion as it is.
Use the square brackets for description, x, y, group and order selectors.

#32

ok i’ve done this
and then what should i do?

#33

I would leave function as the selected option since the action is for x for y ppromo

#34

u mean sth like this?

#35

sir, what should i do then?

#36

Away from PC attached the minute, back at desk in half hour.

#37

Ok so in your rule add that action, then on action list right click and show all to make it visable again and add it again.
Then fill the fields from the rule instance of the actionsimilar to before for the 5+1 and 9+3 configerations.
Get that done and post a screenshot.
Dont bother testing yet, you will need action constraints. Will work that out in a sec but start with the above first.

#38

Then we can constrain the individual actions based on the quantity of applicable items.
This should give the total number of applicable products;

`[=TN('{TICKET ORDER QUANTITY TOTAL EXP:(ODI=True)&&(MT.Promotion=PBar)}')]`

So we can then constrain the actions to corresponding bracket of qty.

so for 5+1 would apply if qty between 5 and 12 so action constraint would be something like;

`[=TN('{TICKET ORDER QUANTITY TOTAL EXP:(ODI=True)&&(MT.Promotion=PBar)}')] > 5 && [=TN('{TICKET ORDER QUANTITY TOTAL EXP:(ODI=True)&&(MT.Promotion=PBar)}')] < 12`

9+3 would be more than 11 but less than 18

`[=TN('{TICKET ORDER QUANTITY TOTAL EXP:(ODI=True)&&(MT.Promotion=PBar)}')] > 11 && [=TN('{TICKET ORDER QUANTITY TOTAL EXP:(ODI=True)&&(MT.Promotion=PBar)}')] < 18`

If they use the same order tag i would have though it should overwrite the previous band promo tag

#39

excuse me for late answer sir,
i can’t get this quote, can u simplify it more?

#40

ok i have done this

is this right?

and where should i write this?!