Design a Web App using Laravel

Design a Laravel Web App - description follows, as well as drawings and diagrams attached. There will be some small features (eg minor variations to screen layouts, etc) to be reviewed while project is in progress, but the scope details 99% of functionality required. - - - - - - - Design & Develop Web App using Laravel Required to be hosted locally, and draw some data from a local MDB database file (table references to be provided) Functionality as follows; Part A – Customer Order System Ability to transact customer special orders 1. New Order Order details captured as per diagram 1. These are saved to Laravel database using a unique ID (system generated) – if there are multiple lines for the order, they will have a letter following – eg 1000-A, 1000-B, etc When order is saved, a customer reference is to be printed on a thermal docket. 2. View Orders Ability to view all orders stored, as per diagram 1. If a customer order contains multiple items, they will each show up as an individual line, with the common order ID. 3. Raise Purchase Order This will group customer orders that have not been previously ordered by supplier, and allow user to manually add items to the bottom. Items can be removed (using ‘x’ on far right.) When Purchase order is saved, it is printed and emailed. It then applied an ‘ordered’ date to each of the customer orders – indicating that they have been ordered from the supplier on that date. (3b is an example layout of printed purchase order) 4. Allocate Stock The supplier received order (Goods Received) will be inputted to the separate MDB database file under a unique GR number. User can select supplier, enter GR number, and it will pull list of products and quantities received. This screen will show all ‘ordered’ goods that have not yet been received from that supplier. If goods have been received on this GR docket, customer can ‘allocate’ goods to customer. This will print a thermal docket for that good with customer details, and save as ‘allocated’ 5. Customer Pickups User enters the code of a picked up item, and this marks that line as ‘picked up’ in the database. Part B – Servicing 10. Instrument is checked in (10) and details stored in database 11. View All – a list of all instruments is displayed, including filters and search functions 11b. Edit – service person can check box to mark completed, and add unique notes. 12. A pickup can be registered. At this time, a report is printed (A4) including a set of standard notes as per instrument type.