1. Marketing/Acquisition
1.1. Promos
1.1.1. Can credits be used with promos?
1.1.1.1. Promos will not be applied to items being redeemed with a token, but you can choose to use your token on a promo item
1.1.1.2. Ignore items that are available for token in the promo
1.2. CRM
1.2.1. Emails where billing $ is referenced changed to reference credits
1.2.2. Emails showcasing available outfits for credit shoppers that month?
1.2.3. Impact segmentation in CRM campaigns, because no longer able to segment by 'x$ in account and higher', for example
1.3. Loyalty
1.3.1. Does Refer a Friend change?
1.3.2. Any changes to points system in MyBeneFits?
1.3.3. Does using a credit earn loyalty points the same way buying something normally does?
1.3.3.1. How many loyalty points does it earn?
1.4. How will this be marketed onsite?
1.4.1. New page explaining?
1.4.2. Upgrade push?
1.4.3. Assets driving users to upgrade?
1.4.4. Going to need a lot of new creative
1.5. Start running media to sell this?
1.5.1. Ahead of time so that users can get excited?
1.5.2. Track/attribute new users who respond to media and then sign up? Existing users that upgrade?
1.5.3. 'Upgrade' link in ads/media/paid social?
2. Merch
2.1. May see uptake in inventory depletion for outfit items?
2.1.1. Planning/projection impact
3. Site Merch
3.1. Merched via Collection page?
3.2. Certain outfits restricted?
3.2.1. Threshold one - based on price
3.2.2. Threshold two - custom setting
3.3. Allowed to use credit to purchase outfit on Waitlist?
3.4. New tag necessary for outfits available for credit redemption?
3.5. Will be running two different product catalogues - or at least need to display two different product lists out of one Ecat
3.5.1. Have to be able to take our Ecat and for single items and outfits, we also say how many tokens its worth
3.5.2. The reason we need a separate Ecat is because we'll have people in the old program, and we'll want to offer different outfits, AND because the price of the outfits for the two groups will be different (show different VIP prices)
4. Frontend Website
4.1. Grids
4.2. PDP
4.2.1. How will we show that outfit can be redeemed with credit on PDP?
4.2.2. Option to 'Redeem with Credit'?
4.2.2.1. Yes, will be able to AtC with credit
4.3. Checkout
4.3.1. How will we determine what outfit/item will credit be applied to?
4.3.1.1. What if they have multiple credits, can they get more than one thing?
4.3.2. Do we give them the option to apply credit in the cart?
4.3.2.1. Yes - they will get to choose what they want to apply it to in the cart
4.3.3. How do we show this in subtotal?
4.3.4. Does usage of credit count towards free shipping?
4.3.5. Can you purchase other things with it at the same time?
4.3.5.1. Can you use alt/other payment methods to pay for other items in your cart?
4.3.6. Is sales tax applied to the item/outfit purchased with credit?
4.3.7. The cart will need to handle both old-style billed credits and newly issued outfits credit
4.4. Other pages to update
4.4.1. T&Cs
4.4.2. Privacy Policy
4.4.3. FAQ
4.4.4. How it Works
4.4.5. Gift Cards?
4.4.6. My BeneFits?
4.5. My Account
4.5.1. Shown in red header text beneath tabs
4.5.2. Order History page needs to be updated to be able to show credits
4.5.3. Online Cancel flow will need to be udpated
4.5.3.1. If possible to downgrade, need to add that into Online Cancel flow
4.5.4. Downgrade mechanism?
5. Backend (CMS, Console, etc.)
5.1. How will this be shown in Bond?
5.1.1. Ability for GMS to give credit?
5.2. If a user returns the item, do they get their credit back?
5.2.1. Can they choose whether to exchange or get credit back or get cash refund?
5.3. GMS agent training
6. EU
6.1. Additional steps for individual country compliance?
6.2. Additional steps for GDPR compliance?
7. Overview
7.1. Goals
7.1.1. Whole new site experience
7.1.2. New pricing model
7.2. Measures of Success
7.2.1. Gap between Cash & GAAP reduced by [x] OR gap equals [x] by [date]
7.2.1.1. GAAP Target:
7.2.1.2. Cash Target:
7.2.2. Credit Redemption Rate
7.2.3. Goods purchased with Credit
7.2.4. Users upgraded to VIP+
7.2.5. LTV of VIP+ customers
7.2.6. Purchase funnel KPIs for credit purchases
7.2.7. Cancellation Rate of VIP+
7.3. Concept
7.3.1. Store Credit - Token - redeemable for outfit (or single item)
7.3.1.1. Token expires after 12 months OR if they cancel their membership
7.3.1.2. Will also be done in Retail
7.3.1.3. Will also be done in Mobile App
7.3.1.4. This will be the new VIP membership, no new tier
7.3.1.4.1. Get rid of shop or skip?
7.3.1.4.2. Will existing membership credits in user's account be turned into tokens? At what rate?
7.3.1.4.3. How do users sign up?
7.3.1.4.4. How will returns work?
7.3.1.5. No breakage?
7.3.1.5.1. Correct - all tokens will expire after 12 months
7.4. Business Execution
7.4.1. Will be run side by side with old model for some time
7.4.2. US to start, with testing period
7.4.2.1. EU to come after US
7.4.2.2. Start testing in April, 4-5 months
7.4.2.3. Will we AB test individual components of this? Test the entire experience as a whole?
7.4.3. FL first, then SXF then GFB
7.5. Technical Execution
7.5.1. On CF or Bento/Tier 1?
7.5.2. How will AB test be set up?
7.5.3. Database changes to support?
7.5.3.1. New set of tables to represent object in DB
7.5.3.1.1. Multiple token types - mostly similar to membership credit system
8. Resources
8.1. UX
8.1.1. Jack Bowen
8.2. Engineering
8.2.1. Dane Pescaia
8.2.2. Michael Blair
8.2.3. Brent Jones
8.2.4. John Blayter
8.2.5. Andrew Householder
8.3. QA
8.3.1. Jill Curtis
8.4. Other
8.4.1. Tim Collins
8.4.2. Mel Cummings
8.4.3. Jamo Yee
8.4.4. Marcelo Vaz
9. Schedule
9.1. Q1
9.1.1. Mock up the full flow
9.1.2. Start tech dev
9.1.3. Focus groups to plan marketing
9.2. Q2
9.3. Q3
9.4. Q4
9.4.1. Go live in October
9.4.2. Testing in EU by EoY
10. Accounting
10.1. How do we show this on our books?
10.2. How will returns be handled?
11. Retail
11.1. VIP can redeem token in store
11.2. Mechanism to join new program in store?
12. Data/Reporting
12.1. Will need dual reporting for old model vs. new model for a while
12.2. Need to convert all reporting for metrics around billed store credit usage to new credit usage
12.2.1. New db fields need to be referenced in reporting