Laddawn.com : Coupon Code Box Implementation & Mockups

Goals

To conditionally offer customers, at the contact and bill-to level, to utilize coupon codes and get a percentage off a certain order. Phase one will address simple creation of coupon codes, entered by the Marketing group via Laddawn Helpdesk Tickets. Phase two will allow Marketing to create coupon codes through an online tool.

Background and strategic fit

As we continue to do more specific targeting of our users based on what they do (or don't do) at Laddawn and Laddawn.com, having the ability to offer a coupon code to incent and encourage certain behaviors is an important function to have to try and drive additional sales. For example, if we can send coupon codes as a last resort to people with expiring quotes, it will drive some additional sales. If we can incent zero accounts to try Laddawn with coupon codes, it could get them - finally - into our online ecosystem.

Phase One Requirements

User interaction and design

Elements for Laddawn.com:

A. When the user first logs in
While the user will likely be coming onto the site from an email that has been sent them letting them know about a coupon code, we want to be consistent with experience and messaging, so a graphic at the top of the screen upon the user logging in is something we'll want to implement here. It should stay with the user regardless of page until they use the coupon and check out. 

**Important note: You are going to see some references to "Exhibit A" in the next few mockups. Exhibit A is the proposed back-end coupon generator, which is not yet functional. When it does become functional, I will add a new ticket into the Helpdesk, which will refer to this page. Until that coupon generator launches, all ticket requests will come via email or helpdesk ticket and will include the elements you see in Exhibit A.**
 

Example 1 - Promo Code on Homepage when people have a Single Coupon. The coupon description (in this example, "10% Off Your Entire Order") will be pulled from Field 2 of the Back End Coupon Creation tool in Appendix A below.  "Click here to learn more" will always be there. 

What changed? Nothing much here. We made slight revisions to the text within the orange banner and how to find it.

Example 2 - Promo Code on Homepage when people have Multiple Coupons. There is no need to pull from anything in Appendix A here. The only thing needed is a static statement "Get ready to save some money. Click here for your coupons." The entire orange banner and text should be clickable and generate the pop-up window with more detailed coupon descriptions.

What changed? Nothing much here. We made slight revisions to the text within the orange banner and how to find it.

Example 3 - Pop-Up Window When People Click the Orange Banner at the Top of the Homepage (showing both multiple and single coupon codes). 

In this example, you'll need to refer to Appendix A below.

• "SILLY10" is field number 1 in Appendix A
• "10% OFF your entire order" is field number 2 in Appendix A
• The black font description is field number 10 in Appendix A

What changed? 

• We left justified the coupon descriptions from the last version.
• We reduced the amount of overall text
• The individual coupons on this pop-up don't need to be clickable or underlined 
• We do not need category numbers in parenthesis

Example 4 - Coupon codes in the Cart (single and multiple)

When a contact has multiple coupon codes targeted to them (this will be rare, but inevitable), all available coupons will be shown, from best offer to lowest offer. In this case, the user has two coupon codes available but can only use one of them because this scenario covers an entire order and we'll only allow one coupon code per line. In the second example below, this assumes that the user has layflat bags in their cart. If they had mattress bags in their cart, they would only see the "SILLY10" coupon available.

In this example, you'll need to refer to Appendix A below.

• "SILLY10" is field number 1 in Appendix A
• "10% OFF your entire order" is field number 2 in Appendix A
• Expiration Date is pulled from field number 4, ("ending date") in Appendix A

What changed? 

• We moved the apply button to the far right
• We added the expiration date of the coupon to the middle
• Left justified the coupon code and it's basic description
• Removed the clickable "I" from the page
• Let's make sure that there's no decimals or extra zeroes in the coupon descriptor - if it's 10% off, it should say 10% off. We may, in the future, go one more decimal ("10.5%") but it'll be very very rare.

Example 5 - Application of Coupon Code (single and multiple). When the customer clicks on the APPLY button to apply the code, it looks like the screenshot below - the message that comes up telling the user that it's been applied. This window disappears automatically and then the banner in the header which refers to this coupon code automatically disappears. The only place you can remove the coupon code would be in the cart if you haven't checked out yet. See toaster and "remove" link in the below mockup. Note: if there are multiple coupons used, each coupon - and it's name - would appear as its own line item in the order totals at the bottom right. The mockups below only show one, but if there's more each one should show, with its individual discount.

What changed? 

• We changed the text of the green toaster.
• Eliminated the specific coupon code callout in the order totals at bottom (this will be a single-line, aggregate amount if single or multiple coupons are used)

Example 6 - Coupons Removed

A customer will have an opportunity to change their mind and remove a coupon from a cart by clicking the "remove" button. They can, in effect, stash it to apply it to a different cart. Upon clicking of the "remove" link, a green toaster will pop up again and simply say "Discount removed from Cart." At this point, the orange banner we see in all the Examples above would come back up onto the screen and the notification in a cart about that coupon code would revert back to the original language in above Examples and the coupon discount line would revert back to $0.00. Single and multiple use toaster screenshots are below.

What changed? 

• We changed the text of the green toaster
• Eliminated the specific coupon code callout in the order totals at bottom (this will be a single-line, aggregate amount now if single or multiple coupons are used)
  
  

Example 7 - Coupons During Checkout

Code should also be reflected in the checkout process (and beyond, including order confirmations) along the right side where other subtotals are. Each coupon discount applied should be listed in the Order Total as seen below. If there are multiple coupons used, then each one would be listed in the Order Total.

What changed?

• Removed individual coupon code listings and went  back to aggregate coupon amount (this will be a single-line, aggregate amount if single or multiple coupons are used)

Example 8 - Coupons at Order Summary

Important: The mockup below shows a mockup in Order History, though it would be materially similar for the Checkout Summary as well. As with the mockup above, if there are multiple coupons used, each coupon and it's amount should be itemized in the Order Total.

What changed?

• Reverted back to original presentation of having one single coupon code amount (this will be a single-line, aggregate amount if single or multiple coupons are used)

SHARING & OTHER IMPLEMENTATIONS

For "off-site" functionality such as emailed cart shares, the aim is to simply mirror what is shown on the cart pages for users. If a user is sharing an item, no changes are needed to the current layout because a code hasn't been applied yet. For cart shares, see below.

A. Coupon Available: Example of statement in shared cart when user has a coupon available.

B. Floor Threshold: Example of statement in shared cart when user still needs to spend X in order to qualify.

C. Coupon Applied: Example of statement in shared cart when user has applied a coupon (disregard dollar amounts in mockup below).

Questions

Below is a list of questions to be addressed as a result of this requirements document:

Appendix

Setting up Coupon Codes. Back end tool for Marketing to create, modify and get reporting on coupon codes.

Appendix A - Back End Coupon Creation Tool

B. Active Coupon Code Reporting

OLDER DESIGNS BELOW, STORING HERE IN CASE.

Option 2

Option 3

Other Conditional Considerations/Treatments

If there is a spending cap or threshold on any coupon codes (for example, "10% off when you spend a minimum of $1500"), in place of the coupon code availability statement, we should have an incentive statement to create awareness of how much more a person needs to spend in order to be able get the discount. 

If there is a cap/threshold on a certain product category, for example if you need to spend a certain amount in order to use a coupon, the remaining amount to earn the coupon should also be reflected in that statement. Like so:

WE ARE HOLDING OFF ON CAPS/MAXIMUMS FOR THE TIME BEING. DISREGARD THE NEXT SENTENCE AND MOCKUP. In the event that a cap has been reached, for example, a coupon where you can earn 10% off an order with a maximum savings amount of $10, the message to let people know they've reached their cap should also be shown.

IT Notes

(These are original notes that have since been updated elsewhere. Keeping just in case. Nothing to see here......)

To accommodate a sales contact adding a single coupon code to their shopping cart that applies to individual item(s) or an entire master order, the following database changes will be required:

• Gather a list of valid coupons from the CRM SQL database for the sales contact and active cart, and return this info to the UI.  This will include checking expiration dates, seeing if the coupon has already been used (for one-use coupons) and checking if the coupon is already in another of the contact's carts.
• Modify the cart total logic to include the Coupon Discount Amount, and calculate a new cart total. Return the coupon discount amount to the UI.  This must take into account individual item(s), product categories, level 3 data (ie, vented job, printed job) and coupon percentages applied to the entire cart (Stock, MOD, Samples).
• Save the coupon code and coupon amount in the shopping cart record, to be used by Checkout to display the cart totals, as well as for order creation.
• During Order Creation, save the coupon code and the discount% by line item in new fields of the order line item file.  Also add the coupon percent to the 1% Web Discount in the Discount% field of each line item.  Use the total percentage to calculate the Discount$ for this order. The coupon discount% will also be stored (by item) in a new field so that we can separate a coupon discount from a web discount for reporting and G/L accounting.  Adding the web discount and coupon discount together in the existing discount field will allow the new discount to flow through the Avante system without any reporting changes, since all Bookings and Sales Reports show Net$, minus discounts.
• Send the Coupon Discount$ along to the Share Email and Order Acknowledgement to be shown on the email.
• Create new dictionaries for user reporting, separating the Web Discount and Coupon Discount percentages and amounts. 
• When the order is shipped and invoiced, separate the coupon discount from the web discount, updating a new G/L account.  Calculate a new discount using the coupon discount% applied to the shipped amounts only.
• Modify the Invoice Email/Fax to show the Coupon Discount Amount below the Web Discount Amount after the Merchandise Subtotal line.
• Modify selected Bookings and Sales Reports that currently show the Web Discount as a separate column, to separate the discounts into two columns.
• Modify Avante Order Display Screen to show the Coupon Code and Coupon Amount on the Totals Screen.
• New Coupon Reporting - requirements unknown at this time.

Notes from meetings w/Scott, Owen, Jeff and Susan:

1. Scott would like the Coupon Discounts to flow into a separate G/L Account than the Web Discounts
2. Owen would like all Bookings and Sales Reporting to continue to show Net Sales (minus Web Discounts and Coupon Discounts).  Should have the ability to report web discounts and coupon discounts separately.
3. All coupons will be for a specific contact, although the coupon setup may allow Marketing to select ALL contacts for a billto or selective contacts for a billto to receive the coupon.
4. CE should be allowed to enter coupons on behalf of the customer
5. Will need ability to create coupons for Printed Jobs, Vented Jobs, etc.
6. Discussed whether the Coupon entry should remain in the Cart or whether it should be moved to the Payment screen. Concerns with multiple carts was discussed.  I will try to put together some numbers of how many saved carts any one contact has going at a time (looking back 1 week?).
7. Coupons will be for percentages only - Flat Amounts have been removed from the design.

Possibility for storing the new Coupon Discount%:

• Save the Coupon Discount% and Coupon Discount$ by Line Item in SODET - these fields will be used for reporting and breaking out the Coupon Discount from the Web Discount
• Store the Web Discount% + Coupon Discount% together in SODET<7>.  Store the Web Disc$ + Coupon Disc$ in SODET<26>.  This will allow all bookings and sales reporting to continue to use this single field for calculating Net$.  No report changes will be required.
• When needed, we can easily separate the Coupon Disc% and $ from the Web Disc% and $ by using the two new Coupon fields.  Probably a good idea to create new disctionaries showing the web disc% and $ by subtracting out the coupon % and $.