Claims:WE CLAIM:
1. A system to use restaurant services, comprising of:
at least one optical code pre-programmed with a Uniform Resource Locator (URL);
at least one wireless transceiver;
one or more portable devices;
at least one short-range communication device pre-programmed with a URL; and
at least one server,
wherein the optical code and short-range communication device are positioned on the serving area,
wherein the portable devices connect to the server through the wireless transceiver, when either the optical code or the short-range communication device is scanned to enable user proximity detection,
wherein the portable device is configured to display menu items from the server through the URL for real-time interaction with the user to place orders, and
wherein the system thus provides a dynamic interface through a progressive web app that
does not require downloading.

2. The system as claimed in claim 1, wherein the optical code includes an image, a bar code, a Quick Response (QR) code, and text.

3. The system as claimed in claim 1, wherein the short-range communication device includes beacons, near-field communication (NFC) tag, and radio-frequency Identification (RFID) tag.

4. The system as claimed in claim 1 includes a scanner embedded within a URL positioned on the serving area that enables the scanning of the optical code without the downloading of an app.

5. The system as claimed in claim 1, wherein the portable device includes a mobile phone, tablet, and laptop.

6. A method to use restaurant services, method comprising steps of:
reading an optical code or short-range communication device pre-programmed with a URL which are positioned on serving area through a portable device of user;
identifying the URL with hash code by the portable device;
extracting the hash code and matching it with a table ID;
generating a unique session ID for the user;
requesting list of menu items offered by an establishment from a server through a wireless transceiver by the user to place orders;
displaying the menu items from the server based on the request to the user for real-time interaction with the establishment on the portable device;
receiving an order of one or more selections of menu items from the portable device device;
communicating the order of one or more selections of menu items to the establishment with instructions via the server; and
serving the selected order by the establishment based on the instructions communicated through the server, thus resulting in a dynamic interface being provided through a progressive web app that does not require downloading.

7. The method as claimed in claim 6, wherein the portable device connects to the server through the wireless transceiver, when either the optical code or short-range communication device communicates with the portable device to enable user proximity detection.

8. The method as claimed in claim 7, wherein the optical code includes an image, a bar code, a Quick Response (QR) code, and text.

9. The method as claimed in claim 7, wherein the short-range communication device includes beacons, near-field communication (NFC) tag, and radio-frequency Identification (RFID) tag.

10. The method as claimed in claim 6, wherein the user has the option to add or remove items from their cart.

11. The method as claimed in claim 6 further comprising of providing feedback by the users to the establishment through a page in the URL through their portable device connected to the server.

12. The method as claimed in claim 6, wherein the users seated at the same serving area are clubbed under the same table ID.

13. The method as claimed in claim 6 further comprising of paying bill by the users to the establishment in a page in the URL through their portable device connected to the server.

14. The method as claimed in claim 13, wherein the user has the option to split the bill with other users seated within the same serving area.

15. The method as claimed in claim 6, wherein the user has the option to redeem rewards offered to them by the establishment without the downloading of an app.

16. The method as claimed in claim 6, wherein inactive users are automatically logged out of their respective sessions after a set amount of time, thus enabling a layer of security from and for subsequent users.

17. The method as claimed in claim 6, wherein the menu items include food, beverages, goods, or combinations thereof.

18. The method as claimed in claim 6, wherein the establishment comprises of a restaurant, bar, stadium, gallery, arena, product provider, service provider, or combinations thereof.
, Description:FIELD OF THE INVENTION
The present invention relates generally to the field of communication used in the restaurant service sector of the catering industry. More particularly, the present invention relates to system and method to use restaurant services and place orders through an on-site wireless network access device. Advantageously, the present invention provides a dynamic interface through a progressive web app (PWA) that requires no downloading.

BACKGROUND OF THE INVENTION
Restaurant dining in general, is a service on offer that has evolved into something that is far from being just about the food - at least from the customer’s perspective. People who eat out seek an experience to remember and are likely to spend more time and money at a place where they feel engaged. It is the responsibility of the management to make sure that their customers are treated well and are left with an overall positive impression of their restaurant. Being the most visible public service industry, restaurants and hotels are subject to a considerably wide range of customer expectations that comprise of an ever-increasing demand for convenience.

Some restaurants offer an online ordering facility for their eat-in or take-out services through a website. Such websites maybe provided by the restaurant itself or by a third-party online service provider. To place an order, a customer needs to connect their web browser to the restaurant’s website using the Internet. Once connected, the customer is normally required to go through a registration process that creates a user account on their behalf using their personal information that includes their name, address, phone number, email address and credit/debit card information. In case the customer already has an account, they have to sign in to the account by entering their username and password.

Even though the website is in possession of the customer’s personal information that includes their home address, their current physical location is unknown to the service provider or the restaurant. A restaurant that has multiple locations would require the customer to go through a list of locations and find out which location is the one they have to place their order at. The availability of different menus at different locations adds more to the complexity of the ordering process and renders it error-prone. For example, in the eat-in scenario, the ordering website has no way of determining whether the customer is still on their way to or is physically inside the restaurant. Food that has been prepared too early lacks the intended level of taste and quality. Similarly, food that has been prepared late forces the customer to endure a wait that could have been avoided.

Some service providers offer a custom application for certain types of mobile devices. This application needs to be downloaded and installed on a customer’s mobile device and can only work with the service provider supplying the application. Owing to this, it can be ascertained that separate applications are needed for different service providers. Multiple custom applications have to be developed in order to support multiple devices. Also, app developers or publishers who make apps for the service industry face the difficulty of getting people to download their apps. As a result of this, it makes it harder for them to market their product to restaurant owners and users however helpful the app/tool might be.

WO2016188470 discloses a graphic code-based smart meal-ordering system comprising of at least one mobile device, a server, at least one smartphone terminal, and a graphic code provided on the dining table. The mobile terminal scans a graphic code and transmits the graphic code to the server. The server validates the permission of the mobile terminal, where the permission refers to the mobile terminal.

Accordingly, there exists a need for a customizable system and method to use restaurant services that enables the use of a dynamic interface through a progressive web app that does not require any downloading.

OBJECTS OF THE INVENTION
One or more of the problems of the conventional prior art may be overcome by various embodiments of the system and method of the present invention.

It is the primary object of the present invention to provide a customizable system to use restaurant services and place orders through an on-site wireless network access device.
It is another object of the present invention, wherein the system to use restaurant services provides a dynamic interface through a progressive web app (PWA) that does not require downloading.

It is another object of the present invention to provide an optical code which is pre-programmed with a Uniform Resource Locator (URL).

It is another object of the present invention, wherein the system includes a short-range communication device pre-programmed with a URL which is positioned on the serving area.

It is another object of the present invention, wherein the short-range communication device includes beacons, near-field communication (NFC) tag, and radio-frequency identification (RFID) tag.

It is another object of the present invention, wherein the system enables for faster scanning of the URL.

Another object of the present invention is to provide a customizable method to use restaurant services with a dynamic interface through a progressive web app that does not require downloading.

It is another object of the present invention to provide a bill-splitting service to customers that is accessible within the PWA.

It is another object of the present invention, wherein the system is configured to obtain feedback from the customers.

It is another object of the present invention, wherein the system is configured to efficiently manage a customer-centric rewards system.

Another object of the present invention is to provide system and method that enables the availing of valet services with a scheduling feature.

SUMMARY OF THE INVENTION
Thus, according to the primary aspect of the present invention, there is provided a system to use restaurant services, comprising of:
at least one optical code pre-programmed with a Uniform Resource Locator (URL);
at least one wireless transceiver;
one or more portable devices;
at least one short-range communication device pre-programmed with a URL; and
at least one server,
wherein the optical code and short-range communication device are positioned on the serving area,
wherein the portable devices connect to the server through the wireless transceiver, when either the optical code or the short-range communication device is scanned to enable user proximity detection,
wherein the portable device is configured to display menu items from the server through the URL for real-time interaction with the user to place orders, and
wherein the system thus provides a dynamic interface through a progressive web app that
does not require downloading.

It is another aspect of the present invention, wherein the optical code includes an image, a bar code, a Quick Response (QR) code, and text.

It is another aspect of the present invention, wherein the short-range communication device includes beacons, near-field communication (NFC) tag, and radio-frequency Identification (RFID) tag.

It is another aspect of the present invention, wherein the system includes a scanner embedded within a URL positioned on the serving area that enables the scanning of the optical code without the downloading of an app.
It is another aspect of the present invention, wherein the portable device includes a mobile phone, tablet, and laptop.

Another aspect of the present invention is directed to provide a method to use restaurant services, the method comprising steps of:
reading an optical code or short-range communication device pre-programmed with a URL which are positioned on serving area through a portable device of user;
identifying the URL with hash code by the portable device;
extracting the hash code and matching it with a table ID;
generating a unique session ID for the user;
requesting list of menu items offered by an establishment from a server through a wireless transceiver by the user to place orders;
displaying the menu items from the server based on the request to the user for real-time interaction with the establishment on the portable device;
receiving an order of one or more selections of menu items from the portable device device;
communicating the order of one or more selections of menu items to the establishment with instructions via the server; and
serving the selected order by the establishment based on the instructions communicated through the server, thus resulting in a dynamic interface being provided through a progressive web app that does not require downloading.

It is another aspect of the present invention, wherein the portable device connects to the server through the wireless transceiver, when either the optical code or short-range communication device communicates with the portable device to enable user proximity detection.

It is another aspect of the present invention, wherein the optical code includes an image, a bar code, a Quick Response (QR) code, and text.

It is another aspect of the present invention, wherein the short-range communication device includes beacons, near-field communication (NFC) tag, and radio-frequency Identification (RFID) tag.

It is another aspect of the present invention, wherein the user has the option to add or remove items from their cart.

It is another aspect of the present invention, wherein the user provides feedback to the establishment through a page in the URL through their portable device connected to the server.

It is another aspect of the present invention, wherein the users seated at the same serving area are clubbed under the same table ID.

It is another aspect of the present invention, wherein the user pays their bill to the establishment in a page in the URL through their portable device connected to the server.

It is another aspect of the present invention, wherein the user has the option to split the bill with other users seated within the same serving area.

It is another aspect of the present invention, wherein the users have the option to redeem rewards offered to them by the establishment without the downloading of an app.

It is another aspect of the present invention, wherein inactive users are automatically logged out of their respective sessions after a set amount of time, thus enabling a layer of security from and for subsequent users.

It is another aspect of the present invention, wherein the menu items include food, beverages, goods, or combinations thereof.

It is another aspect of the present invention, wherein the establishment comprises a restaurant, bar, stadium, gallery, arena, product provider, service provider, or combinations thereof.
BRIEF DESCRIPTION OF THE DRAWINGS
Figure 1: illustrates a method to use restaurant services according to the present invention through an access point in the form of an NFC-enabled QR Code.
Figure 2: illustrates a system through which restaurant services can be availed according to the present invention through an access point in the form of an NFC-enabled QR Code.
Figure 3: illustrates a method to use restaurant services according to the present invention which can be utilized by two customers (user 1 and 2) and point of service entities.
Figure 4: illustrates menu screens for the progressive web app that are in accordance with an embodiment of the present invention.
Figure 5: illustrates one manifestation of the environment that can be utilized to experience all aspects of the present invention.
Figure 6A: is a flowchart illustrating the bill-splitting feature of the invention in accordance with an embodiment of the present invention, which can be utilized by the customer and point of service entities when the customer opts to split the bill/tab in accordance with the individual orders placed.
Figure 6B: is a flowchart illustrating the bill-splitting feature of the invention in accordance with an embodiment of the present invention, which can be utilized by the customer and point of service entities when the customer opts to split the bill/tab equally.
Figure 6C: is a flowchart illustrating the bill-splitting feature of the invention in accordance with an embodiment of the present invention, which can be utilized by the customer and point of service entities when the customer opts to pay for the entire bill/tab.
Figure 7: is a flowchart illustrating the feedback system of the invention in accordance with an embodiment of the present invention, which can be utilized by the customer and point of service entities.
Figure 8: is a flowchart illustrating the rewards system of the invention in accordance with an embodiment of the present invention, which can be utilized by the customer and point of service entities.
Figure 9: is a flowchart illustrating the valet feature of the invention in accordance with an embodiment of the present invention, which can be utilized by the customer and valet service entities.

DETAILED DESCRIPTION OF THE INVENTION WITH REFERENCE TO THE ACCOMPANYING FIGURES
The present invention as herein described relates to a system and method to use restaurant services and place orders through an on-site wireless network access device. Advantageously, the present invention provides a dynamic interface through a progressive web app that does not require downloading and utilizes the system by using either of three access points namely Near Field Communication (NFC), Quick Response Code (QR Code) or through a scanner embedded within the PWA itself. The NFC tag and QR Code maybe combined to form an NFC-enabled QR Code should spatial problems be a concern.

Figure 1 illustrates a method to use restaurant services through an access point in the form of an NFC-enabled QR Code. The method comprises of the following: 100 is the QR Code for use on the table that has a unique, shortened URL linked to it. This may be placed over an NFC tag [101] for use on the same table that also has a unique, shortened URL linked to it to form an NFC-enabled QR Code [102]. When 102 is scanned or read [103], using the portable mobile device, the unique, shortened URL with hash code is identified [104]. At step 107, the unique, shortened URL that is attached to the QR Code [105] is hit and the count increases by 1 in the QR code scan counter. At step 108, the unique, shortened URL that is attached to the NFC tag [106] is hit and the count increases by 1 in the NFC tag read counter. At step 109, the hash code is extracted from the unique, shortened URL. At step 110, the extracted hash code is matched with its corresponding unique table ID present in the database. At step 111, if the matching process is successful, the location of the user is determined through the table ID and a unique session ID is generated for the customer. At step 112, if the matching process fails and does not return any result, an error message is displayed. At step 113, if the step 111 goes through, the URL that is linked to a table in the restaurant opens and the customers now have access to all the menu items available at the restaurant through the ordering platform that opens in the form of a PWA.

Figure 2 illustrates a system through which restaurant services can be availed through an access point in the form of an NFC-enabled QR Code [200]. In an aspect, the system comprises of at least one optical code pre-programmed with a Uniform Resource Locator (URL); at least one wireless transceiver; one or more portable devices; at least one short-range communication device pre-programmed with a URL; and at least one server. The short-range communication device includes beacons, near-field communication (NFC) tag, and radio-frequency Identification (RFID) tag. The method comprises of the following: 201 is the process through which the QR Code of 200 for use on the table that has a unique, shortened URL linked to it is scanned. 202 is the process through which the NFC tag of 200 for use on the same table that also has a unique, shortened URL linked to it is read. After the NFC-enabled QR Code is scanned or read using the portable mobile device, the unique, shortened URL with hash code [203] is identified. The hash code is extracted [204] from the unique, shortened URL. The extracted hash code is now matched with its corresponding unique table ID [206] present in the database [205]. If the matching process is successful, the location of the user is determined through the table ID [206] and a unique session ID [207] is generated for the customer. If the matching process fails and does not return any result, an error message [209] is displayed. Once the session ID [207] has been created, the URL that is linked to a table in the restaurant opens and the customers now have access to all the menu items available at the restaurant through the ordering platform that opens in the form of a PWA [208].

Figure 3 illustrates a method to use restaurant services which can be utilized by two customers (user 1 and 2) and point of service entities. The method comprising: At step 300, the customers take their respective portable devices. At step 301, if the portable devices have a camera app that can scan QR Codes, the customers open the camera app (native) and point the portable devices at the NFC-enabled QR Code. At step 302, if the portable devices do not have a camera app that can scan QR codes and are also not NFC-ready, the customers can make use of the website which serves as an embodiment of the invention that enables the scanning of QR Codes without the downloading of an app and points said portable devices at the NFC-enabled QR Code. At step 303, if the portable devices are NFC-ready, the customers place the portable devices over the NFC-enabled QR Code. At step 304, the QR Code is scanned using either the process 301 or 302 depending on the nature of the device. At step 305, the NFC tag is read using the process 303. At step 306, the unique, shortened URL with hash code is identified. At step 307, the unique, shortened URL that is attached to the QR Code is hit and the count increases by 1 in the QR code scan counter. At step 308, the unique, shortened URL that is attached to the NFC tag is hit and the count increases by 1 in the NFC tag read counter. At step 309, the hash code is extracted from the unique, shortened URL. At step 310, the extracted hash code is matched with its corresponding unique table ID present in the database. At step 311, if the matching process is successful, the location of the user is determined through the table ID and a unique session ID is generated for the customer. At step 312, if the matching process fails and does not return any result, an error message is displayed. At step 313, if the step 311 go through, the URL that is linked to a table in the restaurant opens and the customers now have access to all the menu items available at the restaurant through the ordering platform that opens in the form of a PWA. It should be noted that User 1’s session ID and User 2’s session ID have now been clubbed with the same Table ID. At step 314, as soon as 313 is executed, all user/customer activity is tracked for a period of about 15 minutes and they have the option to browse the menu page and place orders at will. At step 315, if there is no activity on the users’ side for more than a period of about 15 minutes after 313 has been executed, for security reasons that include but not limited to misuse by next set of customers that scan the code/read the tag at the same table, and internet time wastage due to inactivity, all users are logged out and their session IDs are cleared. This ensures that the ecosystem is reliable and efficient. At step 316, the customers now have the option to add or remove items from their respective carts. Any number of items may be added to their carts in any random order or quantity. At step 317, the customers, once done with the process 316 move on to confirm their orders either through a social login or through a signup option within the PWA. At step 318, the orders placed by the customers through the PWA are clubbed together as one and reflected on the restaurant’s Web App/Android™ App/point of sale (PoS) system. At step 319, the restaurant’s management now edits and confirms the order based on availability. A notification is sent to the customers’ portable devices via a cloud messaging service once their orders have been confirmed. At step 320, the restaurant serves the orders to the customers once they are ready. The step 316 may be performed any number of times until step 321 is performed and confirmed. At step 321, the customer generates the bill for the order placed. This option may be accessed at any time after the process 319. This option can be accessed by either one of the customers. At step 322, once the step 321 is executed by either one of the customers, both of them are logged out and their session IDs are cleared. The case is the same irrespective of the number of users logged into the same table.

Figure 4 illustrates menu screens for the progressive web app that are in accordance with an embodiment of the present invention. Referring to Figure 4, 401 is the QR Code scanning page of the PWA. It has a real time video feed through the portable device’s camera. Once scanned, the browser automatically redirects to that particular restaurant’s menu page 403 where the customer can choose from various categories that include but not limited to starters, main course, and desserts, a variety of dishes that include but not limited to dish 1, and dish 2. The customer may or may not have the option to access the quick settings that include but not limited to W - Water, F - Feedback, V - Valet, and C - Call waiter. When the F - Feedback option is selected, the browser navigates to the restaurant’s feedback page 405 where the customers can rate the restaurant’s service, ambience and also add in their suggestions and complaints. Once the feedback has been submitted, the browser navigates to the menu page 403. When the V - Valet option is selected, the browser navigates to a QR Code scanning page 408 that scans only the QR Code on the valet card provided to the customer. Once the QR Code has been scanned, the browser navigates to the valet page 410 where the customer has the option to cross-verify the serial number on the valet card with the serial number displayed on 410. Here, a delivery time for the vehicle may be set and confirmed. Once the delivery time is confirmed, the browser navigates back to the QR Code scanning page 401 and the subsequent instruction is sent to the personnel in charge of the valet service.

Figure 5 illustrates one manifestation of the environment that can be utilized to experience all aspects of the invention. Referring to Figure 5, 500 is Table 1 at the restaurant that seats customer 1 [506] and holds the NFC-enabled QR Code 503. 501 is Table 2 at the restaurant that seats customer 2 [507], customer 3 [508] and customer 4 [509] and holds the NFC-enabled QR Code 504. 502 is Table 3 at the restaurant that seats customer 5 [510], customer 6 [511] and customer 7 [512] and holds the NFC-enabled QR Code 505. 513 is the order that 506 goes on to place through the PWA after scanning/reading 503. 514 is the order that 507, 508 and 509 go on to place through the PWA after scanning/reading 504. 515 is the order that 510, 511 and 512 go on to place through the PWA after scanning/reading 505. 516 is the network (WAN) where all the orders from 500, 501 and 502 are collected and stored in the database. At 517, the orders that are stored in the database are sent through a cloud messaging service to the Web App/Android ™ App/PoS system 518 that the restaurant uses to monitor and manage its service activities. At 519, the orders that have been placed are now edited and confirmed based on availability and this process serves as the communication line between 518 and the kitchen [520]. Subsequently, 506, 507, 508, 509, 510, 511 and 512 may also get notifications through a cloud messaging service about their orders getting confirmed. 521 is the order corresponding to 500 that has been prepared and served in accordance with the instructions given to 520 by 518. 522 is the order corresponding to 501 that has been prepared and served in accordance with the instructions given to 520 by 518. 523 is the order corresponding to 502 that has been prepared and served in accordance with the instructions given to 520 by 518.

Figure 6A illustrates the bill-splitting feature of the invention in accordance with an embodiment of the present invention, which can be utilized by the customer and point of service entities when the customer opts to split the bill/tab in accordance with the individual orders placed. At step A600, the customers take their portable devices. There are three customers with three portable devices who are seated at the same table. At step A601, if one of the three portable devices have a camera app that can scan QR Codes, the customer opens the camera app (native) and points it (portable device) at the NFC-enabled QR Code. At step A602, if one of the three portable devices do not have a camera app that can scan QR codes and is also not NFC-ready, the customer can make use of the scanner embedded within the PWA which serves as an embodiment of the invention that enables the scanning of QR Codes without the downloading of an app and points it (portable device) at the NFC-enabled QR Code. At step A603, if one of the portable devices is NFC-ready, the customer places it (portable device) over the NFC-enabled QR Code. At step A604, the QR Code is scanned using either the process A601 or A602 depending on the nature of the device. At step A605, the NFC tag is read using the process A603. At step A606, the unique, shortened URL that is attached to either the QR Code or the NFC tag is hit and the portable device’s browser redirects to the desired URL. At step A607, the desired URL that is linked to a table in the restaurant opens and the customers now have access to all the menu items through the ordering platform that opens in the form of a PWA. At step A608, the customers now have the option to add or remove items from their carts. Any number of items may be added to the cart in any random order or quantity. At step A609, the customers, once done with the process A608 move on to confirm their orders either through a social login or through a signup option within the PWA. At step A610, the orders that have been placed by the customers through the PWA on their portable devices are reflected on the restaurant’s Web App/Android™ App/PoS system. At step A611, the restaurant’s management now edits and confirms the orders based on availability. A notification may be sent to the customers’ portable devices via a cloud messaging service once their orders have been confirmed. At step A612, the restaurant now serves orders to the customers once they are ready. The process A608 may be repeated any number of times until the process A613 is performed and confirmed. At step A613, the customers generate the bill for the orders placed. This option may be accessed at any time after A609. A616 is the bill amount B1 for the first customer, A617 is the bill amount B2 for the second customer and A618 is the bill amount B3 for the third customer. At step A619, when the first customer selects the pay as per order option, A616 alone may be settled or just displayed depending on whether a payment gateway has been integrated or not. At step A620, when the second customer selects the pay as per order option, A617 alone may be settled or just displayed depending on whether a payment gateway has been integrated or not. At step A621, when the third customer selects the pay as per order option, A618 alone may be settled or just displayed depending on whether a payment gateway has been integrated or not.

Figure 6B illustrates the bill-splitting feature of the invention in accordance with an embodiment of the present invention, which can be utilized by the customer and point of service entities when the customer opts to split the bill/tab equally. At step B600, the customers take their portable devices. There are three customers with three portable devices seated at the same table. At step B601, if one of the three portable devices have a camera app that can scan QR Codes, the customer opens the camera app (native) and points it (portable device) at the NFC-enabled QR Code. At step B602, if one of the three portable devices do not have a camera app that can scan QR codes and is also not NFC-ready, the customer can make use of the scanner embedded within the PWA which serves as an embodiment of the invention that enables the scanning of QR Codes without the downloading of an app and points it (portable device) at the NFC-enabled QR Code. At step B603, if one of the portable devices is NFC-ready, the customer places it (portable device) over the NFC-enabled QR Code. At step B604, the QR Code is scanned using either the process B601 or B602 depending on the nature of the device. At step B605, the NFC tag is read using the process B603. At step B606, the unique, shortened URL that is attached to either the QR Code or the NFC tag is hit and the portable device’s browser redirects to the desired URL. At step B607, the desired URL that is linked to a table in the restaurant opens and the customers now have access to all the menu items through the ordering platform that opens in the form of a PWA. At step B608, the customers now have the option to add or remove items from their carts. Any number of items may be added to the cart in any random order or quantity. At step B609, the customers, once done with the process B608 move on to confirm their orders either through a social login or through a signup option within the PWA. At step B610, the orders that have been placed by the customers through the Progressive Web App on their portable device are reflected on the restaurant’s Web App/Android™ App/PoS system. At step B611, the restaurant’s management now edits and confirms the orders based on availability. A notification is sent to the customers’ portable devices via a cloud messaging service once their orders have been confirmed. At step B612, the restaurant now serves orders to the customers once they are ready. The process B608 may be repeated any number of times until the process B613 is performed and confirmed. At step B613, the customers generate the bill for the orders placed. This option may be accessed at any time after confirming an order B609. B616 is the bill amount B1 for the first customer, B617 is the bill amount B2 for the second customer and B618 is the bill amount B3 for the third customer. At step B619, when the first customer selects the pay equal share option, (B1+B2+B3)/3 or (B616+B617+B618)/3 may be settled or just displayed depending on whether a payment gateway has been integrated or not. At step B620, when the second customer selects the pay equal share option, (B1+B2+B3)/3 or (B616+B617+B618)/3 may be settled or just displayed depending on whether a payment gateway has been integrated or not. At step B621, when the third customer selects the pay equal share option, (B1+B2+B3)/3 or (B616+B617+B618)/3 may be settled or just displayed depending on whether a payment gateway has been integrated or not.

Figure 6C illustrates the bill-splitting feature of the invention in accordance with an embodiment of the present invention, which can be utilized by the customer and point of service entities when the customer opts to pay for the entire bill/tab. At step C600, the customers take their portable devices. There are three customers with three portable devices seated at the same table. At step C601, if one of the three portable devices have a camera app that can scan QR Codes, the customer opens the camera app (native) and points it (portable device) at the NFC-enabled QR Code. At step C602, if one of the three portable devices do not have a camera app that can scan QR codes and is also not NFC-ready, the customer can make use of the scanner embedded within the PWA which serves as an embodiment of the invention that enables the scanning of QR Codes without the downloading of an app and points it (portable device) at the NFC-enabled QR Code. At step C603, if one of the portable devices is NFC-ready, the customer places it (portable device) over the NFC-enabled QR Code. At step C604, the QR Code is scanned using either the process C601 or C602 depending on the nature of the device. At step C605, the NFC tag is read using the process C603.

At step C606, the unique, shortened URL that is attached to either the QR Code or the NFC tag is hit and the portable device’s browser redirects to the desired URL. At step C607. the desired URL that is linked to a table in the restaurant opens and the customers now have access to all the menu items through the ordering platform that opens in the form of a PWA. At step C608, the customers now have the option to add or remove items from their cart. Any number of items may be added to the cart in any random order or quantity. At step C609, the customers, once done with process the C608 move on to confirm their orders either through a social login or through a signup option within the PWA. At step C610, the orders that have been placed by the customers through the PWA on their portable devices are reflected on the restaurant’s Web App/Android™ App/PoS system. At step C611, the restaurant’s management now edits and confirms the orders based on availability. A notification is sent to the customers’ portable devices via a cloud messaging service once their orders have been confirmed. At step C612, the restaurant now serves orders to the customers once they are ready. The process C608 may be repeated any number of times until the process C613 is performed and confirmed. At step C613, the customers generate the bill for the orders placed. This option may be accessed at any time after confirming an order C609. C616 is the bill amount B1 for the first customer, C617 is the bill amount B2 for the second customer and C618 is the bill amount B3 for the third customer. At step C619, when the first customer selects the pay for table option, (B1+B2+B3) or (C616+C617+C618) may be settled or just displayed depending on whether a payment gateway has been integrated or not. This action blocks out the option to pay for the other customers seated at the same table since the entire bill/tab has been covered for. At step C620, when the second customer selects the pay for table option, (B1+B2+B3) or (C616+C617+C618) may be settled or just displayed depending on whether a payment gateway has been integrated or not. This action blocks out the option to pay for the other customers seated at the same table since the entire bill/tab has been covered for. At step C621, when the third customer selects the pay for table option, (B1+B2+B3) or (C616+C617+C618) may be settled or just displayed depending on whether a payment gateway has been integrated or not. This action blocks out the option to pay for the other customers seated at the same table since the entire bill/tab has been covered for.

Figure 7 illustrates the feedback system of the invention in accordance with an embodiment of the present invention, which can be utilized by the customer and point of service entities. At step 700, the customer takes a portable device. At step 701, if the said portable device has a camera app that can scan QR Codes, the customer opens the camera app (native) and points it (portable device) at the NFC-enabled QR Code. At step 702, if the portable device does not have a camera app that can scan QR codes and is also not NFC-ready, the customer can make use of the scanner embedded within the PWA which serves as an embodiment of the invention that enables the scanning of QR Codes without the downloading of an app and points it (portable device) at the NFC-enabled QR Code. At step 703, if the portable device is NFC-ready, the customer places it (portable device) over the NFC-enabled QR Code. At step 704, the QR Code is scanned using either the process 701 or 702 depending on the nature of the device. At step 705, the NFC tag is read using the process 703. At step 706, the unique, shortened URL that is attached to either the QR Code or the NFC tag is hit and the portable device’s browser redirects to the desired URL. At step 707, the desired URL that is linked to a table in the restaurant opens and the customer now has access to all the menu items through the ordering platform that opens in the form of a PWA. At step 708, the customer selects the feedback option. At step 709, the customer rates the quality of the service and the experience through parameters that include but not limited to ambience, cleanliness, and staff etiquette. At step 710, the customers, once done with the process 709, may move on to provide their details either through a social login or through a signup option within the PWA. At step 711, the customers may now submit their virtual feedback form by confirming the process 710.

Figure 8 illustrates the rewards system of the invention in accordance with an embodiment of the present invention, which can be utilized by the customer and point of service entities. At step 800, the customer takes a portable device. At step 801, if the said portable device has a camera app that can scan QR Codes, the customer opens the camera app (native) and points it (portable device) at the NFC-enabled QR Code. At step 802, if the portable device does not have a camera app that can scan QR codes and is also not NFC-ready, the customer can make use of the scanner embedded within the PWA which serves as an embodiment of the invention that enables the scanning of QR Codes without the downloading of an app and points it (portable device) at the NFC-enabled QR Code. At step 803, if the portable device is NFC-ready, the customer places it (portable device) over the NFC-enabled QR Code. At step 804, the QR Code is scanned using either the process 801 or 802 depending on the nature of the device. At step 805, the NFC tag is read using the process 803. At step 806, the unique, shortened URL that is attached to either the QR Code or the NFC tag is hit and the portable device’s browser redirects to the desired URL. At step 807, the desired URL that is linked to a table in the restaurant opens and the customer now has access to all the menu items through the ordering platform that opens in the form of a PWA. At step 808, the customer selects the rewards option. At step 809, the customer now has the option to view all the rewards that are on offer at the relevant restaurant and the number of reward points required to redeem a specific one. At step 810, if the customer has enough points to redeem a particular offer, the redeem option is selected. At step 811, the offer that has been redeemed causes a subsequent set of instructions to be sent to the restaurant’s Web App/Android™ App/PoS system and the applied changes to the bill amount 813 (cash discounts 811) and additions to the order 814 (items given free of charge 812) may be viewed by the customer.

Figure 9 illustrates the valet feature of the invention in accordance with an embodiment of the present invention, which can be performed by the customer and valet service entities with a scheduling feature. The said feature is utilized by the customer via the progressive web app and is managed by the restaurant through another web app or Android™ app that directs the personnel in charge of the valet service. At step 901, if the said portable device has a camera app that can scan QR Codes, the customer opens the camera app (native) and points it (portable device) at the NFC-enabled QR Code. At step 902, if the portable device does not have a camera app that can scan QR codes and is also not NFC-ready, the customer can make use of the scanner embedded within the PWA which serves as an embodiment of the invention that enables the scanning of QR Codes without the downloading of an app and points it (portable device) at the NFC-enabled QR Code. At step 903, if the portable device is NFC-ready, the customer places it (portable device) over the NFC-enabled QR Code. At step 904, the QR Code is scanned using either the process 901 or 902 depending on the nature of the device. At step 905, the NFC tag is read using the process 903. At step 906, the unique, shortened URL that is attached to either the QR Code or the NFC tag is hit and the portable device’s browser redirects to the desired URL. At step 907, the desired URL that is linked to a table in the restaurant opens and the customer now has access to all the menu items through the ordering platform that opens in the form of a PWA. At step 908, the customer selects and opens the valet option irrespective of whether they have placed an order or not. At step 909, the customer now scans the QR Code on the valet card that was given to them before they entered the restaurant. An embedded scanning page similar to the one mentioned in the step 902 is used. This page redirects to the page that requires inputs from the customer. At step 910, the customer may now input the tentative vehicle pickup time after checking if the serial number on the valet card matches the one that has been detected by the PWA. At step 911, the customers, once done with the process 910, may move on to provide their details either through a social login via or through a signup option within the PWA. This confirms the pickup request for the vehicle and this is turn may be sent to the Android™ App that the personnel in charge of the valet service use. At step 912, once the vehicle is ready for pickup, the valet personnel may now send a notification to the customer’s portable device through a cloud messaging service. At step 913, the customer picks up the vehicle. At step 914, the customer now returns the valet card if it is meant to be reused. Care should be taken to note that the traditional method of handling valet services may also be employed in case the customer decides not to use the service provided by the present invention.

The menu items include but not limited to food, beverages, goods, or combinations thereof. The establishment comprises of a restaurant, bar, stadium, gallery, arena, product provider, service provider, or combinations thereof. In one embodiment, Point of Sale (PoS) system is integrated to monitor and manage all the service activities initiated by the user through the progressive web app within the restaurant. Thus, the system to use restaurant services provides a dynamic interface through a progressive web app that does not require downloading.

The foregoing description comprises of illustrative embodiments of the present invention. Having thus described exemplary embodiments of the present invention, it should be noted by those skilled in the art that the within disclosures are exemplary only, and that various other alternatives, adaptations, and modifications may be made within the scope of the present invention. Merely listing or numbering the steps of a method in a certain order does not constitute any limitation on the order of the steps of those method. Many modifications and other embodiments of the invention will come to mind to one skilled in the art to which, this invention pertains, having the benefit of the teachings presented in the foregoing descriptions. Although specific terms may be employed herein, they are used only in a generic and descriptive sense and not for purposes of limitation. Accordingly, the present invention is not limited to the specific embodiments illustrated herein.