English Boards > Requests

Membership/Loyalty Integration

<< < (2/2)

emre:
These are really amazing features John. I'm adding a screenshot from V3 for showing how we'll handle customer management with V3.



I think I should focus on V3 development because going with V2 makes things harder for me as I have to implement same features on both V2 and V3 and sometimes I make mistakes and release bugs with V2... From now on I should only fix bugs on V2.

My plan is creating the first V3 alpha before entering FEB and we'll continue development of these features on V3. How it sounds?

jenem:
Thanks for update Emre,

Good work looking forward to V3

Edgar

JohnS:
I've just checked out V2.79...

Awesome  :D
Thank you for the changes & updates.

Now before I continue I just want to say Emre, I understand that V3 needs to get off the ground, and therefore respect that focus needs to be on V3 features and design, not V2. Like I have said before - what can we achieve with V2. My ideas and suggestions are just that - and you have the right to say 'No, next version', and I will not be offended.

PS - If you need help testing V3 please let me know.

Question 1. Customer selection is by 'Phone' when scanning or using caller id. As per my suggestion earlier (about scanning customer card during item entry) how would you plan to make a 'Customer Card' integrate into the system. For example, product barcodes are usually EAN8/13, so if customer numbers are no longer than say 6 digits, the system will never get confused if the barcode is a product or customer number due to the length. If you create your own barcodes, then use 7 digits to again avoid overlapping barcodes. By this method would you search the customer database after products to find a match?

The reason for this question is for preparation of current customer/membership cards in readiness for V3. As I suggested before about a prefix to the customer number - I don't think that is necessary, and I don't think at this stage alphanumeric customer numbers are needed.


Question 2. There is an Action to Update Ticket Account - I have tried this, but can not get it to work. How do you use this?.
Is there a possibility to add Customer Group Code to this?


Great work team.

Bring on V3!! (yes I am just a little excited)

emre:
Hello I think I missed your last post sorry.

1. Like we did for weight barcodes we can differ customer barcodes with prefixes.
2. Update ticket account used for assigning an account to a ticket. We use it for linking tables with customer accounts so when users clicks to Boss table ticket automatically assigns to Boss account.

On latest release I added two new parameters to "Customer Selected to Ticket" event. One of them is LastOrderTotal. For example it is possible to execute actions if Previous Order Total is > 100.. The other one is LastOrderDays. It returns the day count between last order date and today. So we can execute promotions if Previous Order is not older than 5 days...

I wrote it here to document new membership features...

Navigation

[0] Message Index

[*] Previous page