Job description
Functionalities:
1. User registration via e-mail address or telephone number (verification by e-mail and SMS, respectively);
2. Creating an order by selecting items from the menu by the customer;
3. From the restaurant side, a panel for creating a menu (individual items, including sets, eg a dish with options for selecting add-ons);
4. Possibility to edit the order;
5. Order history
6. Provision of invoice data
7. Preparation for integration with PayU.
8. Admin panel for adding restaurants and the ability to make changes to the menu or profile settings as admin.
A very similar website is e.g. www.knajp.pl
Principle of operation:
1. The customer enters the restaurant's website - he has the option to register or can enter without logging in.
2. The customer places an order - then information about the order is displayed on the restaurant's website, which the restaurant accepts - the message about accepting the order returns to the customer
3. The customer may change the order further - within the same order that is being updated, step 2 is repeated.
4. The customer may ask for an invoice - then he provides and sends the data (or only sends it if he has provided it earlier and has been saved) to the restaurant. The restaurant's data is displayed (without the integrated module for generating invoices - we assume that the restaurant is rewriting it manually).
5. The client chooses the moment when he wants to close the account (at any time, eg after a month), then he is transferred to PayU or another payment integrator, both the client and the restaurant with the payment made.
6. The restaurant has a constant view of all accounts - ie "open" accounts that do not require action, "closed" - ie. paid for, requiring only manual confirmation, and "requiring action" - ie those in which the restaurant must confirm acceptance of the order, its extension or, for example, issuing an invoice.
7. The customer and the restaurant have access to the order history.
