Basic Assignments
 
Options & Settings
 
Main Time Information
Color Code: Yellow
Assigned To: Brandon Moore
Created By: Brandon Moore
Created Date/Time: 5/8/2018 10:20 am
 
Action Status: Blank (new)
Show On The Web: Yes - (public)
Priority: 0
 
Time Id: 3742
Template/Type: Brandon Time
Title/Caption: Adilas Time
Start Date/Time: 5/14/2018 8:30 am
End Date/Time: 5/14/2018 12:15 pm
Main Status: Active

Sorry, no photos available for this element of time.


Notes:

Working on adilas ecommerce pieces and training details.

Morning meeting. Steve was working on code. I was updating adilas ecommerce stuff. Russell came on and reported on some of his projects.

Information from Russell and Chris Johnnie about coupons, loyalty points, and gift cards.

- Gift cards - be able to get a random number and put it onto a card. The random number makes it harder for someone to use another card (security issues). He needs to be able to scan it and see what is on the card. He also needs a spot to scan the card and have it use that as a payment option. It needs to go full circle. They need to be able look things up, add to it, take away from it, and view levels. Both tied to a customer and not tied to a customer (generic card). Be able to use this in both the normal secure cart and the ecommerce cart. Easy to load card.

- Punch cards - every cart that is $15 or more is eligible. If the cart is a counter sale, they could be prompted to sign-up if they want. Once they are in, the points would automatically accumulate based off of the rules. Once they get to a certain level, say 15 points, they get $10 off of the purchase. They want it really automated and almost a non-thinker type process. They want a quick interface to allow for the sign-up process.Just to recap Notification when a customer is eligible, notification when a customer has points they can redeem. Customers can choose how much they want to pull out. They must pull out blocks of points at a time. For example they have to pull out 15 Points to get $10 off. They cannot pull 10 points and get $7.50 off.

- Coupons - add, edit, copy, delete (permanent hide status), details - coupon code, coupon text or description, quantity, status, type ($'s off or % off), usage (unlimited, limited amount, unlimited no additional discount, limited amount no additional discount) , customer limit, specific item or part id, status (blocked or open or deleted), minimum value to activate, etc. See Russell's page afb_coupons_rules_logic_settings.cfm - branch ram-42. See the link below for the spreadsheet planning.

https://docs.google.com/spreadsheets/d/1ANHIdJx6zbV4BM_pZ1biOTmK-SJrKwLUoxuHYMA7BJM/edit#gid=0

10 - 1 with Eric - planning out the loyalty points and special accounts.

Estimated amount Chris is willing to contribute

Gift Cards

$3500-$5000

Puch Card

$1500-$3000

Cupons

$1500-$3000

We talked quite a bit about using the builders and logic (part of the UI) as the master options. The builders might be things like locations, part categories, customer types, and even the item or part id level. Lots of field names and lists to  help us make and generate the rules.

We do have a more complicated issue when we do cross-corp loyalty points. These cross-corp things struggle with pre-calculated totals and such.

We talked about migration paths and getting existing customers into the basic loyalty points as well as getting new customer using our basic adilas loyalty points.

User communities - who wants to join up and put a list of priorities together. We then work and prioritize these features and get them in place as soon as possible.

As part of the conversation, I gave Eric permission to run with the basic loyalty points. He will get a plan ready and then re-present it back to me before going into the coding stage. Good stuff and trying to remove as many obstacles as possible.