h2. *User story*

Discount strategy would only work if customers know and see (reinforcement) these promotions are running while browsing on the app or web. As a marketeer I want to make sure our users can see the promotions visible at the right places to help them convert better.

h2. *Scope of change*

* Promotions module in CRM will have offer card and offer terms section added.

* API to get the offers relevant for a product and SKU. Best price/ You save.

* Product details offers

* Cart offers

* Terms & conditions

* Cart with free shipping display and combo offer display

h2. *{color:#205081}1. Promotions module (CRM){color}*

There are two new sections added in Promo module

*{color:#205081}a) Offer card{color}*

This section is not mandatory, so it'd have a switch which is OFF by default. "Display offer on web and app screens". If turned ON this will prompt to enter:

* Title – Limited to 40 characters. Required.

* Message – Limited to 100 characters. Required.

* Offer card image – Select from pre-uploaded list or upload a new one. Required. {color:#f79232}Size/dimension check: tbd{color}

* Logo image –  Upload one. Optional. {color:#f79232}Size/dimension check: tbd{color}

* PLP message bar –

*{color:#205081}b) Offer terms & conditions{color}*

This section is not mandatory, so it'd have a switch which is OFF by default. "Setup offer terms to display". If turned ON this will:

# Option to select whether to add offer terms or show a special page from a drop down list.

# If opting to add offer terms, user can add offer terms like attributes (much like product/audience attributes) which are all optional. At least one of them should be added if selected to setup.

  – Description

  – FAQ

  – Terms & conditions

* *Description* – This is free text field which is limited to 500 characters.

* *FAQ* – This is a question and answer format of text, where user can add multiple FAQs of question-answer pair.

* Terms & conditions – This is a bulleted list of information, where user can add multiple points/info.

* Offer terms should have *app links* and *deeplinks*, which can be copied from the promotion edit page (much like product list app link and deep link).

*{color:#205081}b) App links and deep links{color}*

* Offer terms should have app links and deeplinks, which can be copied from the promotion edit page (much like product list app link and deep link). So, business teams can start talking about upcoming offers too and start linking it from custom tiles.

* Merchandise rule products should also have app links and deeplinks, this will be passed to client to show to users when a user's cart or product viewed is partially eligible for the offer. We'll also make it available in CRM custom tiles for user to select.

  – Product attributes

  – Product list. This will be the same product list app link and deep link format.

  – Upload list

* These app links and deep links will also be available for copying in Promotion edit page.

* Deeplink for promotion products (for both product rule and BOGO rule):

  – Deeplink for Product list rule will be /products as we use today

  – Deeplink for T&C?

  – Deeplink for non product list (product attributes based, upload PIDs) would be /search.

* Promotion products for BOGO will have both Buy and Get product list in one single listing.

* Promo products listing PLP will have these names based on whether they are on web/app and if there's a promo code or not:

  – Web with promo code: Showing 303 results for SIROSA20

  – Web with no promo code: Showing 303 results for your promotion

  – App with promo code: SIROSA20

  – App with no promo code: Your promotion

h2. *{color:#205081}2. Custom tile actions (CRM){color}*

* In CRM custom tiles, under actions, we'll add "Offer terms". Selecting "Offer terms", will show a drop down "Select the promotion" for which offer term is to be shown.

* "Select the promotion" for "Offer terms" will have all the running and upcoming promotions which have terms available. It'll be shown in this format: ABCD200 offer terms.

* In CRM custom tiles, under actions, we'll also add "Promotion products". Selecting "Promotion products", will show a drop down "Select the promotion" for which products are to be shown.

* "Select the promotion" for "Promotion products" will have all the running promotions which have merchandise rule setup for some products (*not All*). It'll be shown in this format: ABCD200 products.

h2. *{color:#14892c}1. Product page and offers{color}*

# Only *live/running* offers which are setup as "Display offer on web and app screens" turned *ON* would be considered for this offer check.

# On PDP, we should be able to show the best price for the product. (on PDP itself, is possible). It'll also show the saving.

 – If the product has only one offer applicable, action text would directly take user to terms page.

 – If the product has multiple offers applicable, action text would take user to *offer list* page.

* Offer message on PDP will have saving too along with best price. Refer design mockup.

h3. *{color:#14892c}2. Offer list opened from PDP{color}*

All the offers checked about as fully or partially applicable for this product will be listed here.

* Offer list would be sorted with best offer giving highest discount value on top.

* All offers setup for display will be shown including Free shipping offers.

* For BOGO, both buy and get list products would qualify to be in offer list.

* Best price/Save value may not be available for all products. Eg, BOGO.

* Offer card will show the following details:

  – Offer card image

  – Offer call out image/logo

  – Offer value if available (Eg, Save ₹324)

  – Offer title

  – Offer message

  – Promo code

  – Terms links if available

  – Offer expiry time.

* Terms and conditions link would be shown when available.

* Priority order when offer value is same: ?

* If product only *partially qualifies* for the offer, there'd be a link to shop more:

  – If it has a merchandise rule, this link will take user to see all the applicable merchandise. {color:#f79232}Generic message copy TBD{color}.

  – If it does *not* have merchandise rule, there'll be a shop more message available for all. But it'd only have a link if user opened the offer from *cart*. This link will take user to *_homepage_* {color:#f79232}Generic message copy TBD{color}.

{color:#f79232}(Messaging based on different conditions to be shared (like ship min etc). TBD)

{color}

h2. *{color:#14892c}3. Cart page{color}* (client and API)

* Free shipping – show it in cart{color}

* Cart promotion bar

  – This will show the promo code if any is applied.

  – This will link to Offers list where user can see all relevant promotions.

  – If a promotion is already applied and it's not applicable anymore, relevant cue will be shown to user.

* Of a valid promotion is already applied:

  – Cart promo field will allow users to remove the promotion as well as go see all offers (offer listing page).

  – On the Offer listing page, user will see this promo's offer card on top and can remove this promotion using the Remove button.

  – All other promotion offer card (one not applied already) will have a "Apply" button. Clicking on this button will trigger a remove request first and then an apply. We'll fire *promo_applied event*, but *not* promo_removed. And, promo_applied event will have a property from_promo which will have the promo code that was removed.

– Engg to figure if server is passing the applied promo in T&C or client is remembering it.

* Displaying *cart items with promotion* applied

  – Cart items will be list in order of latest ATC first.

  – Cart items eligible for BOGO or merch offer will be listed together, taking the latest ATC.

  – Discount will be pro rated among the items (all merch rule).

  – If it's a BOGO offer, item level discount message will have promo code. "Rs 100 promo BOGOXYZ discount applied".

  – If it's a non BOGO offer (product rule), item level discount message will have no promo code. "Rs 100 promo discount applied".

h2. *{color:#14892c}4. Offer list from Cart{color}*

All the offer list conditions are same for Cart too, except these:

* Offers - Should be able to see all the offers which are relevant for _at least one item in the cart_ (for BOGO, both buy and get list products).

* Offer card will also have a "Apply" button. This button will be enabled only if offer is fully eligible and could be applied for items in cart.

* Doing a successful "Apply" from here would take user back to the Cart with promo applied.

* For non merchandise rule, shop more messaging would also have a link that would point to *_homepage_*

h2. *{color:#14892c}Component logic{color}*

* *Best price and Saving*

  – Besides SKU price and offer, we will also consider global budget available, and customer budget available. [If offer expired because of end time, budget exhaustion, customer budget exhaustion, it should not be listed at all]

  – For products with differently priced SKUs (available only) will calculate on highest SKU price available. For Cart, this won't be an issue as we will check for the specific SKU added to cart. Eg, For instance, for a product with 3 skus with displayed price [retail/sale price] of 100, 150, 200 respectively. This product qualifies for an offer having 10% off. We will consider the sku with price 200 and show saving of 20/-.

  – Best price won't have a Saving threshold as we show the selling price. In the cart, when we show the saving, we'll show saving only if it's Rs 50 or more.

* *Offer card sorting*

As stated above, offer cards will be sorted with best price / saving first. In this order:

  1. Best price / value

  2. If same value, sort by promotion type

  3. If no value computable, sort by promotion type

Promotion types will be sorted in this order:

  1. Overall offers (non merchandise rule)

  1.1. % offers of highest %value. Eg, 20% will be higher order than 10%

  1.2. Flat offers of hight value. Eg, 500 off will be higher order than 300

  2. Free shipping

  3. Merchandise rule offers

  3.1. % offers of highest %value. Eg, 20% will be higher order than 10%

  3.2. Flat offers of hight value. Eg, 500 off will be higher order than 300

* *Offer expiry time* display: [ [~krishna] to figure countdown timer unit in display]

  – Upcoming in 24 hours or more – Starts on 23 Jan, 2019

  – Upcoming in less than 24 hours – Starts in 1 hour [countdown of hours, minutes, seconds]

  – Ending in 24 hours or more – Valid till 23 Jun, 2019

  – Ending in less than 24 hours – Expires in 4 hours [countdown of hours, minutes, seconds]

  – Ended – Expired promotion

* *Offer removal and apply buttons*

  – Offer can be _removed_ from any of these screens. On removal, user will stay on those screens: cart, offer list from PDP, offer list from Cart, Offer terms.

  – On removing the offer, user will remain on the screen they were on and button will become "Apply" if they came from Cart.

  – Offer removal is available on PDP offer list so user knows they have already applied the offer.

* [~krishna] Handling button to no button look.

* Apply button will be there on offer card only if they see it from Cart: cart offer list, cart offer terms.

h2. *5. Offer terms*

* Terms link can take user to a special page or to an actual Offer terms page. There are 4 main sections in the terms page which are all optional:

# *Offer card* – Terms page will have the same offer card as seen in the offer list, with the following differences:

  – There could be an expiry time or starting time. Eg, "Starts in" or "Ends in". Also, this time would be countdown (same logic as countdown implemented for sale).

  – Handle the case where a terms link is opened for an offer that has expired.

  – Terms offer card will have "Apply" for fully eligible offer only if opened from cart offer list. Doing a successful "Apply" from here would take user back to the Cart with promo applied.

  – If this offer is already applied in cart, terms offer card will have a "Remove" action available.

  – Offer card and Offer terms are independent of each other (in setup). So, if there's no offer card. T&C will not have offer card or any kind of nudge including merch rule nudges.

# *Offer detail* – Descriptive field. Paragraph form

# *Frequently asked Questions* – Number bulleted Q&A format.

# *Terms and conditions* – Text bulleted information.

h2. *Segment events and tracking*

Refer DD-9083 for details.

h2. *A/B testing*

Experiences to be tested: The main purpose of this test is to test the visibility of offers to customers which is shown on PDP and cart.

# PDP - Showing "Offer row that may point to offer listing" vs not showing at all.

# PLP - Showing promotion message bar

# Cart - Showing "New promo field that takes to offer listing" vs Old promo text field

* What is *not* important for testing: Promo application splitting the applied promo and showing in cart.

* What would work for everyone in old and new experience

  – If someone goes directly to promo products list or offer terms or offer listing via custom tiles etc – It should work no matter whether they are in old or new experience.

h2. *Other resources*

* [Mockups|https://zpl.io/awnzDeN]