I don't normally revert to the forums to promote my "idea box" submission, but I'm a bit desperate. I posted an item in there about the discount codes and their current inability to be customized by member type within the same product ticket. Presently you can only apply the same discount amount or percentage to ALL membership types within a product ticket. Unfortunately that means if you have different early bird or discounted amounts for a conference or event registration, you have to either adjust your entire pricing structure to be a single amount off, OR you have to set up different tickets for each group that gets a different early bird discount. Problem with option #2 is that any member type could sign up for any of those different tickets and then you get an absolutely administrative nightmare. If anyone else out there has experienced this, please consider voting for the idea in the idea box. Otherwise have mentioned this in various submissions over time, but things get lost pretty easily in the idea box and because you cannot comment on other's posts it's hard to consolidate items together. Here is the submission in the idea box: http://unity.yourmembershipinc.com/IdeaBox/default.aspx?id=3309 Ok, I'm done. =). Thanks!

Are you currently using attendee types?

We've tested them out before, but the issue kind of remains. It seems like it's just an extra step that members will "hopefully" read through, but it doesn't actually restrict access. If we listed say "Student members" as one attendee type and "Members" as another we are bound to get some people who are students clicking into the member attendee type, and expired members (who probably don't know they're expired) signing up under the "member" attendee type. Unless attendee types can restrict specific membership types, and expired/nonmembers from selecting specific attendee types it doesn't quite solve the issue unfortunately. To my understanding attendee types don't allow for the functionality to restrict access to specific member types. And to restrict to members one we'd have to have two entire  

Sorry that last part was meant to say - we cannot restrict our conference registration to members only because then we would have to have two entirely separate registrations for members and nonmembers and in turn we'd have to combine the registration tracking from the two systems which is equally tedious.