We have improved our existing loyalty system and make lots of enhancement. In new system, referral customer and employee will be tracked and get benefits of sales occurred from Sales Order or POS.
Loyalty point begin when customer start purchasing above Purchase Limit and then after customer will always get point on every purchase. In configuration, there are some general configuration for getting points for each one. It is easy to define accounts for discount and cash out.
In Sales Order form, you can select Referral Customer and enter how many points to redeem. Redeem points will be automatically converted into discount amount.
Points will be added in customer after invoice will be paid. (created from sales order).
Referral customer and employee (sales person) will earn points.
You can select Referral Customer from POS and redeem points.
It will print redeem point in POS Receipt.
It will make separate journal entry for redeem points entered from POS.
We can have all points information in customer form also like below images.
Employee will get commission amount in their salary as per their sales during a month and job position in company. Multiplier value will be use for calculation of monthly commission amount. Employee contract must have Working Schedule define.
At time of creating employee payslip, employee points will be automatically selected and use in calculation.
Once employee payslip is confirmed, we will have corresponding points entry in employee form.
In this system, its possible to provide CASH amount to customer instead of discount during purchase and also generating valid accounting entries.
Cash Out will make entry same like redeem point for customer.
We have implemented solution for allowing payment process via SagePay from OpenERP. We will see how this module is developed.
We will start from configuration of SagePay account information. It is very important to select appropriate “MODE” of SagePay account.
It is possible that customer may have more than one credit cards. We can configure credit card related information into Customer form itself. We are storing credit card number into database with encrypted format.
To process with sagepay, we have added option into OpenERP voucher form. We can easily make payment or stop it from here.
We are allowing to make three types of transactions with SagePay from OpenERP.
Further process will work according to selected transaction.
After making process, SagePay server will give response about transaction and we are storing that into database for future actions.
We are storing mainly following data:
– Transaction ID
– Transaction Status
– Transaction Message
Now It is very easy to stop your transaction for any reason.
We are restricting user to make any invalid actions on transactions.
It is displaying VOID response from SagePay server. It is possible to perform on transactions which are registered with SagePay.
As mentioned above, it is possible to ABORT only DEFERRED transactions.
We are getting status “REGISTERED” for AUTHENTICATE type of transaction. And that transaction has to AUTHORIZE with SagePay.
We are keeping record of each and every transaction with detail information in OpenERP.
This is how SagePay Simulator page looking.
Here we have to Add IP address of our server or machine from where we are accessing our SagePay account through API. And also add appropriate Currency code for allowing transactions.
It is displaying list of transactions that is related with our account.
OpenERP Point of Sale has return product facility available from order Form view. But this feature is not available in POS interface. We have implemented very important feature – “Return products from POS Interface” so user don’t require to leave POS Interface to return the products.
Below is the screen for normal SALE mode. We have created 3 different buttons to identify the order mode.
1. Sale Mode, is a normal mode
2. Missing Receipt Mode, in which if customer doesn’t have receipt but still salesman can return order so in this case only negative order will be generated.
3. Return Mode, to return the products by comparing with original order.
Once the order is placed, we can see barcode on receipt for that order number generated.
And here is the order which is generated from POS interface.
Now lets try to return the product from POS interface.
When we click on “Return Order” button, at that time this popup will open to enter order reference number.
Here in the image where we can enter order number using barcode or manually.
Once the exact order is found, then list of products will be loaded which are available in the selected order.
If we try to select more product quantity than selected order quantity then it will raise an warning message.
We can also mention any reason for returning products what customer specified.
Once we complete partial return order then we can return the same order again for remaining product quantities displayed in following screen.
Here is the order return receipt in negative if we are returning products.
In order list we can see that main order and return orders have same order numbers with positive and negative values.
POS Order form with corresponding values.
In “note” field, we can find reason which is entered during return products.
Recently we have made integration with OpenERP with Authorize.net for payment services. Now we have integrated OpenERP with another Payment services, BluePay. We can have more information from http://www.bluepay.com. With help of this module, it is very easy to process with credit card from OpenERP interface.
First of all we have to create account on BluePay and get required information and use those information to connect with BluePay from OpenERP. We have tested each transaction in TEST mode.
It requires credit card information to make transactions. We are storing required details into Customer form. We are using AES algorithm for securing credit card number into database.
Sometimes it is require to know that customer has enough balance in his credit card or not. We are giving facility that user will enter amount that he has to check for particular customer and get relevant message.
As we are storing credit card number in a secure way in database so it is not allow to change credit card number directly.
We have improved GUI of voucher for sending payment request to BluePay. It allows to send request only one time if it will succeed. And also stroing transaction related information into voucher for future purpose. It will cancel payment request with BluePay if we are going to cancel voucher.
Sometimes it is require that customer wants to pay amount in installment. We are allowing to create recurring payment request with BluePay.
We are keeping track of messages for each and every transactions occur during recurring payment.
User can change any parameter during recurring payment process execution. And can cancel it also.
We are tracking details of each and every transactions with BluePay.
User can print transaction details on PDF report by entering date range and proper parameter selection.
We have implemented solution for allowing payment process via Authorize.Net from OpenERP. We are still improving this module by adding new functionalities. Currently we have implemented feature with Customer Invoice and Customer Invoice Refund.
In OpenERP, first we have to configure credentials for conneting with Authorize.Net. we are working on encryption/decryption of credit card information.
For payment process, it requires customer address information. We are directly taking “Invoice” type address information from customer.
Also added new fields related to Credit Card information. Currently we are processing with only one credit card. In future we are going to add feature for defining more than one credit card and activating one of them or ask user to select anyone. If “Allow Credit Card Payment” is TRUE then it will allow to do process. This field is useful during automatic payment process by cron job.
In below screen, we can see that credit card number can be change and how it will look like.
Here we have used AES algorithm to store credit card information for security purpose. We are using this algorithm for encryption/decryption.
Currently we put option for payment in Customer Invoice and Refund Customer Invoice.
After payment procedure, OpenERP will get response from Authorize.Net with information like “Transaction ID”, “Response Text”.
Company will get an email also once payment request is completed.
Sometimes, if we want to pay back to customer because of any reason. We have implemented feature that we can easily pay from Refund Invoice. But refund invoice has to be created from existing Customer Invoice only.
We can have the same process in Refund Customer Invoice also.
We will get same response during refund procedure if our transaction is completed successfully.
We are going to implementing this feature for Voucher and POS.