Retail Web Application for Daily Customer Purchase Limits

Time Frame: Preferably 30 Days to Complete this Project from the Date of Post Creation Overview: HTML5 based web application to function as a redundant encrypted database driven solution allowing simultaneous queries from multiple clients via a PCI Compliant secure (SSL/HTTPS://) connection to transmit, store, & query sensitive customer data and purchase(transaction) information. Employee would scan or enter a customer’s Driver’s License or State ID into the system. Once recorded this customer entry will be created to track every customer’s purchases and prevent all customers from purchasing a given quantity limit per day. The database will need to be accessed from multiple locations allowing different businesses or retail locations to reference every individual’s purchase quantity upon checkout at each location. This application could be accessed via a web URL. Requiring each retailer to login using their own credentials. All transactions handled by that retailer are tagged with their location, time, date, quantity, customer info. The database would need to be able to handle a large load (hundreds to thousands) of queries simultaneously and redundantly backup all of the information. Retail/Business Interface: The retail management would be able to log in to the system under their user name (independent for each location). Retail facing interface allows the retailer to look-up individuals that have completed purchases and add quantities of items purchased as well as view what total they have purchased elsewhere that day being certain that they are not allowed to exceed the daily limit. Each transaction would be tagged with the location at which the transaction was completed. Administrative Interface: Administrative interface would allow us to add additional retailers and create their login credentials (Usernames & Passwords). It would also need to provide us the ability to query and run reports on the data and either export as a CSV or display in graphical chart/diagram format. This interface would have complete control over all aspects of the application’s appearance, rights/privileges, users, locations, data, etc. We could also create additional login/user accounts that have only privileges to read data and not write it. Additional Future Features: The integration of card scanners to auto populate the Customer Facing Interface. (If this application is built for mobile devices, the scanning function could be built from the barcode scanning function of the mobile device, or allow for a peripheral device to be connected to the host.) Cross-platform downloadable app on the app store for Windows, Android, Apple devices alike for the various interfaces Restrict transactions based upon Date of Birth (Declining the ability to complete a purchase if age of customer is below that of 21). In the event of unstable or lost internet connection, the application could cache the daily transaction information database and update it in a given time interval to allow temporary offline access and update the transaction data periodically when and if the internet connection is re-established. One possible/important aspect would be to allow white-listed IP address access making the application even more secure. Only IP addresses that have been given access and added to the white list would be granted privileges to use the application. This would restrict the use of the application to the inside of the business itself.