How Subscription is setup

Overview 

This section will give an overview how subscriptions are setup from application point of view.

Back office subscription setup

• First of all subscription needs to be setup in the Backoffice - see here
• Make sure that you have proper subscription attributes setup - atm only one is required - Renewal Contact Method attribute (We may amend the code so it is not loner needed)
• other subscriptions attributes: Case Preference and Membership Level
• We need to setup customer attributes as well if we need them:  beer_box_left_date and beer_box_join_date where prefix beer_box needs to match what is in the subscription table column customer_attribute_prefix 
• There is beer_box_membership customer attribute but that seems to be crated automatically  

Other important setup can be done via back-office: Subscriptions -> VW   where we can setup subscription events, baskets and groups - more about that here.

Back office - content setup (pages, snippets and product assortment)

• We have few pages that compose sign up process - WinePlan Discovery Club this one contains several snippets and rules to display correct context based on the membership level
• We need to make sure that URL aliases are setup in back office - Content → URL aliases - see as an example - URL - "/justReds"

• Panel Three Case Radio with Bottle Assortment Template is the template that holds case selection for signup process. Cases comes from product assortment in the catalogue - WinePlan Promotions → Partner Discovery Club Generic Promo 99.88

• There is also Subscription Hub which is enable only for DC and Beer Box - page My Wineclub Subscription Overview and hub is only visible to the client if next subscription even is less then two weeks in the future - see (SubscriptionHubController class).