Child Product End Date in Self-Service Store
Hello! I'm looking for some guidance about how to properly set up a Child Product in the Self-Service Store. I've reviewed the three SSS videos but didn't find an answer to my question.
Let's say I have this setup:
How do I set things up so that access to Child Product A lasts as long as the member account is paid up? I'm not sure what settings to include for the Child Product to achieve this.
- Master Product 1 (1 day)
- Master Product 2 (10 days)
- Child Product A, which will be available for both Master Products 1 and 2
So, for Master Product 1 members, they have access to Child Product A for 1 day, then when they renew they continue to have access to it, etc. For Master Product 2 members, they'll have access for 10 days and as long as they renew, they'll continue to have access. If they don't renew, Child Product access will cease on the date their membership expired and they didn't renew.
You need to have 2 child products in this case.. not 1.
So create the Child Product 1 with the SAME recurring setting as the Master Product 1 (1 day).
Create the Child Product 2 with the SAME recurring setting as the Master Product 2 (10 day).
User purchases the master product (which is a recurring product) to buy credits. The user will earn credits each recurring cycle when the payment comes in for the master product.
When they redeem credits towards child product 1, their access to child product will be extended by 1 day.
When they redeem credits towards child product 2, their access to child product will be extended by 10 day.
But if you want the access to child product to be automatically renewed when they purchase the master product... then what you need to do is setup Product Chaining instead of using SSS.
Setup a product chaining rule in dap that says .. automatically extend access to child product when the user gets access to master product.
If you use SSS, then it's upto the user to redeem credits every month or every day. It is not automatically redeemed.
Originally Posted by tamjl
Hi, Veena -
I'm not sure I understand.
If I set up a product chain that gives access to Child Product A when someone is added to Master Product 1 or 2, then they wouldn't need to use their SSS credits -- they'd already have access simply by virtue of having purchased Master Product.
I want them to buy credits, use them, and have access to a course (child product) only for as long as they're subscribers to the Master Product. So, if I'm understanding you correctly, the first option you described is what I need to do.
But I don't understand "their access to child product will be extended by 10 day" (in the example of purchasing a 10-day master product. What do you mean "will be extended by"?
Let's say Harry buys Master Product 2 on May 1. His subscription will renew 10 days later unless he unsubscribes. Then, on May 5, he gets around to applying some credits toward purchasing Child Product 2. I think in your example, his access to Master Product would end on May 10 if he doesn't renew, and his access to Child Product 2 would end on May 15. Am I understanding that correctly?
If so, that's not quite what I'm aiming for. His access to Child Product 2 should also expire with his Master Product subscription on May 10 if he does not renew. But if he continues to renew, he should be able to continue having access to Child product for as long as he's a member of Master Product.
I'm not sure how to proceed, then. Is what I'm describing possible?
An additional idea...does this work:
Child Product is set up as non-recurring product. Member buys it with SSS credits after joining Master Product. I set up a product chain that instructs DAP to remove member from CP when they're removed from MP.
Would that mean that as long as they renew automatically each period, they never lose access to CP? And they lose access to CP immediately when they unsubscribe?
No... that wont work. When they unsubscribe, dap does not trigger the product chain rule automatically.
You will have to manually remove their access from product for now... until we figure out a way to automate this.
Ah, ok. Thanks for helping me figure out what's possible and what's not for now!
Tags for this Thread