TOPIC: group rate

i am trying to set my group rate to discount for 4 or more..
individual rate is 200
group rate per person is 175.00

it does not calculate
maybe I am not putting in the right info initially in the group fields.. can you help me here...?

Be sure to check out our video tutorials as you\'d see how to properly setup your event...

For the Individual Rate, put 200.00

Then in the group rate area that has multiple rows of input boxes, put...

Number of Members: 4
Group Rate: 700.00
Rate Per Person: 175.00

Just above this, you can see some explanation including this:
[Rate / Person] x [Number of Members] = [Group Rate]

After saving, you should see TWO occurrences of this event in your Event Management area... one for the 1 person pricing and one for the 4 or more members pricing.

I just upgraded to the latest version and started working on a registration. I\'ve set everything up as instructed in the group pricing, yet on the billing page it shows the regular amount and that\'s what it charges.

I have an event for individuals and/or couples (a marriage seminar). So my group rate is only for 2 people. It\'s $25 per individual or $40 per couple. On the page where I enter each person\'s info it says \"Registration Fee: 2 x $20.00\" as it should. But when I get to the billing info page, it says \"Your total Registration cost: 2 x $25.00 = $ 50.00\"... and that\'s how much it charges the credit card.

Why?

I am experiencing the exact same problem.
I have the latest version of DT register installed and eveything appears to work perfectly except group rate discounts.

I have tediously watched every single video and have everything set up exactly as described.

In my case I am charging $25 for individuals and $40 for couples.

On member 1 & 2 information it does show the Registration Fee: 2 x $20.00 at the top correctly, but on the billing information it shows
Your total Registration cost: 2 x $25.00 = $ 50.00 ?

What could be causing this?

I am under the gun since I am now live with the registration.
Any quick guidance would greatly appreciated.


Thanks.

This issue appears to have been fixed in 2.3.6.