Hello, I need help with the following: I have ONE (1) single membership program, managed by aMember. I have THREE (3) individual "lead generation" products, all offered through our standard 1ShoppingCart account. Whenever someone purchases ANY of the three "lead generation" products, they are automatically subscribed to the membership program. You may see where this is going. If someone purchases Product #1, s/he is automatically enrolled in the Membership program. => If a month later s/he finds product #2 on the Web and tries to purchase it, I need aMember to check her against the existing member database to determine if s/he is already enrolled. => If s/he's NOT enrolled, then I need aMember to continue the transaction, allow the purchase and enroll this person into the membership program. => If s/he's IS already enrolled, then I need aMember to disallow the transaction and send this member to another purchase page that allows him or her to receive a Member Discount on the product without re-enrolling them in the membership program they're already enrolled in. Is there an undocumented feature, or a script that will do this "existing member" check and then determine which product purchase link ("new customer" or "existing member") to send someone to? If not, I am not skilled to program such a script. Can someone do it, and at what cost, in what time frame? Thanks! J.
I think you are gonna have to move these products into amember and have the users order them via amember/1sc. David
David, Thanks for your reply. If only it were that easy (as moving the three products into AMember. Perhaps it is. I haven't found any features in AMember that allow me to have multiple individual products that are all "bundled" with a second, separate, single recurring billing membership "product." 1SC will not allow this, because their system will not "bundle" any AMember "product" with any other AMember or non-AMember product inside 1SC. Given 1SC's bundling restrictions, the only way I know how to do this would be to create a separate recurring billing for every individual front-end product (making each front-end product its own "membership program," which not only defeats the purpose of having a single membership program, but also causes the "sale" of a second recurring billing membership in 1SC PLUS - assuming that the autoresponder series is the same for every "membership" - eithercauses 1SC to reset the autoresponder series for the membership product back to "0" days, eliminating all of the history of the autoresponder series from the initial membership purchase date (if all the recurring billing memberships feed off of the same autoresponder series) OR requires a second, duplicate autoresponder series, which is just confusing to the member. I have not found any way to use the "allow" or "disallow" feature in AMember to solve this dilemma. If you know the answer, I'd greatly appreciate learning it from you more specifically. Many thanks!
By bundling, i mean put them all in the same single product. Do the same in 1sc. So you would now have product 4, "X ebook with a 30 day free trial to Y membership". David
David, Thanks for your help. But for each product, it would require a totally separate "membership" and a unique set of autoresponders for each product. So for each product, we would, essentially, be managing a new membership program. The only thing that would be the same would be the "members areas" on the Web. That would work for a single product, or maybe up to three. But we intend to have between 12 and 20 "lead-gen" products, all that funnel into ONE single "membership product" - and we want to manage only one member / subscriber "list" and one set of autoresponders. We've decided to put all of our lead-gen products into 1ShoppingCart as regular (non-aMember) products. When someone places an order for any lead-gen product, we'll manually "buy" them a membership, using their CC info to set up their aMember account and activate their 30-day free trial. If we discover that someone who purchases a lead-gen product is already a member, then we just won't sign them up again. SO WE COULD USE THIS: Some sort of script that would check the purchaser's e-mail address when they want to make a lead-gen purchase and check it against the aMember database of existing "members." Then if they aren't already a member, the script allows them to go through with the lead-gen purchase. But if they ARE already a member, the script redirects them instead to a "member's discount" purchase page, where they get the member discount price instead of the lead-gen price. Can this be done? Thanks!
Sounds like you are gonna need to have someone write you a custom script- maybe ask Larry at Jlogica. David