Information processing system, information processing method and program

Abstract

To provide an information processing system preventing a next customer at the same table from ordering on the same slip while the account of a previous customer at the table is still incomplete in a mobile order system of a restaurant.SOLUTION: An information processing system includes a control unit. When first receiving, from a user terminal, table identification information for identifying a table or a seat of a restaurant used by a user of the user terminal, the control unit generates slip identification information corresponding to the table identification information and causes the user terminal to display an order screen. Further, when next receiving the same table identification information, the control unit determines whether or not a prescribed time has elapsed since the immediately previous reception of the table identification information or since the reception of the first order information after the reception of the immediately previous table identification information. When determining that the prescribed time has not elapsed, the control unit maintains the generated slip identification information, and when determining that the prescribed time has elapsed, the control unit generates new slip identification information different from the generated slip identification information.SELECTED DRAWING: Figure 4

Description

Technical Field

[0001] The present invention relates to an information processing system, an information processing method, and a program capable of receiving mobile orders from a user terminal in a restaurant.

Background Art

[0002] Conventionally, in restaurants, mobile order systems have been introduced that allow users to order food and beverages from their smartphones or the like.

[0003] For example, in Patent Document 1 below, in a restaurant, a printed matter with a two-dimensional code storing a table ID for identifying the table is installed on each table. By the user reading the two-dimensional code with a user terminal, access to the order page for food and beverages in the restaurant becomes possible, and through the order page, by transmitting order information together with the table ID to a server, a system enabling mobile orders for food and beverages is disclosed.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] By the way, among the above mobile order systems, there are those that only accept orders for food and beverages and perform settlement by other means, and those that can be executed within the system from order to settlement (by credit card or electronic money). Here, in the former case, especially in restaurants with a high customer turnover rate, there may be a case where the settlement of a customer who has finished eating and drinking at a certain table is incomplete (for example, the customer is waiting in line at the cash register for settlement), and the next customer is guided to the table, and an order is added to the ticket of the previous customer.

[0006] In view of the above circumstances, an object of the present invention is to provide an information processing system, an information processing method, and a program that can prevent a customer at the next table from placing an order on the same slip while the settlement for the customer at the previous table remains incomplete in a mobile order system of a restaurant.

Means for Solving the Problems

[0007] To achieve the above object, an information processing system according to an aspect of the present invention includes a control unit. When the control unit first receives table identification information for identifying a table or seat of a restaurant used by a user of the user terminal from the user terminal, the control unit generates slip identification information corresponding to the table identification information and displays an order screen on the user terminal. Further, when the control unit receives the same table identification information next, the control unit determines whether or not a predetermined time has elapsed since the table identification information was received immediately before, or since the first order information was received after the reception of the immediately preceding table identification information. Then, when the control unit determines that the predetermined time has not elapsed, the control unit maintains the generated slip identification information, and when the control unit determines that the predetermined time has elapsed, the control unit generates new slip identification information different from the generated slip identification information.

[0008] According to this configuration, the information processing system can prevent a customer at the next table from placing an order on the same slip while the settlement for the customer at the previous table remains incomplete in a mobile order system of a restaurant by forcibly switching the slip ID at a predetermined time regardless of whether the customer has settled or not. The predetermined time is, for example, 10 minutes, 15 minutes, 20 minutes, etc., but is not limited thereto.

[0009] When the control unit receives the same table identification information before the elapse of the predetermined time, the control unit may reset the predetermined time with the reception time as the start time.

[0010] With this configuration, when another user starts using the same table before the lapse of a predetermined time, the information processing system can secure the dining time of the other user by regarding the other user as a companion of the original user and restarting the count of the predetermined time based on the start time of the use by the other user.

[0011] When the control unit receives additional order information from the user terminal after receiving the first order information, the control unit may reset the predetermined time with the reception time as the starting time.

[0012] With this configuration, when the information processing system receives an additional order before the lapse of a predetermined time, the information processing system can secure the dining time of the additional order by restarting the count of the predetermined time based on the time of the additional order.

[0013] The control unit may be able to switch between a first mode of generating new slip identification information for each settlement of the user and a second mode of generating new slip identification information based on the lapse of the predetermined time.

[0014] With this configuration, the information processing system can flexibly select and use a first mode (normal mode) of switching slips for each settlement and a second mode (congestion mode) of automatically switching slips at a predetermined time according to the situation of the restaurant, such as during congestion and non-congestion.

[0015] When the congestion level of the restaurant becomes equal to or higher than a predetermined threshold value, the control unit may switch the first mode to the second mode.

[0016] With this configuration, the information processing system can easily switch from the first mode to the second mode during congestion without imposing a burden on the restaurant staff. The congestion level may be calculated, for example, as the ratio of the number of currently used tables to the total number of tables. In this case, the number of currently used tables may be counted as the number of slip identification information in use, or may be counted, for example, from the output of a sensor installed at each table to detect the presence or absence of use.

[0017] The control unit may cause the accounting terminal of the food and beverage store to display a user interface for switching between the first mode and the second mode.

[0018] With this configuration, the information processing system can cause the employees of the food and beverage store to manually switch modes according to various situations such as congestion.

[0019] The control unit may change the length of the predetermined time according to a predetermined trigger.

[0020] Here, the predetermined trigger is, but not limited to, time (time zone or time of day, etc.), congestion level, manual operation by employees, etc. With this configuration, the information processing system can adjust the timing until the slip is automatically switched according to various situations in the food and beverage store.

[0021] When the predetermined time has elapsed, the control unit may cause the information prompting the user to settle the account to be displayed on the order screen.

[0022] With this configuration, the information processing system can prompt customers who have not settled their accounts within the predetermined time to settle their accounts, so that even if the slip is switched, the next customer can be quickly guided to the table and the slip after the switch can be used.

[0023] The control unit manages the session with the user terminal that is the source of the table identification information, and even when the predetermined time has elapsed, as long as the session with the user terminal that received the table identification information immediately before continues, the new slip identification information is not generated, and the slip identification information generated immediately before may be maintained.

[0024] This can prevent the situation where after the set time has elapsed, if the previous customer sends the table identification information again and the additional order is added to the slip identification information of the next customer.

[0025] The information processing method according to another aspect of the present invention is When first receiving table identification information for identifying a table or seat in a restaurant used by the user of the user terminal from the user terminal, generate slip identification information corresponding to the table identification information, and display an order screen on the user terminal, Next, when receiving the same table identification information, determine whether a predetermined time has elapsed since the immediately preceding reception of the table identification information or since the reception of the first order information after the reception of the immediately preceding table identification information, If it is determined that the predetermined time has not elapsed, maintain the generated slip identification information, and if it is determined that the predetermined time has elapsed, generate new slip identification information different from the generated slip identification information, including this.

[0026] A program according to another aspect of the present invention causes an information processing apparatus to, When first receiving table identification information for identifying a table or seat in a restaurant used by the user of the user terminal from the user terminal, generate slip identification information corresponding to the table identification information, and display an order screen on the user terminal; Next, when receiving the same table identification information, determine whether a predetermined time has elapsed since the immediately preceding reception of the table identification information or since the reception of the first order information after the reception of the immediately preceding table identification information; If it is determined that the predetermined time has not elapsed, maintain the generated slip identification information, and if it is determined that the predetermined time has elapsed, generate new slip identification information different from the generated slip identification information.

Effect of the Invention

[0027] As described above, according to the present invention, in a mobile order system of a restaurant, it is possible to prevent a situation where the next customer at the same table places an order on the same slip while the accounting for the previous customer at the table is incomplete. However, this effect does not limit the present invention.

Brief Description of the Drawings

[0028]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Embodiments for Carrying Out the Invention

[0029] Hereinafter, embodiments of the present invention will be described with reference to the drawings.

[0030] [Configuration of the System] FIG. 1 is a diagram showing the configuration of a restaurant menu ordering system according to an embodiment of the present invention.

[0031] As shown in the figure, this system includes a restaurant information providing server 100 on the Internet 50, user terminals 200 of users who use each table T of a plurality of restaurants, and restaurant terminals 300 installed in each restaurant.

[0032] The restaurant information providing server 100 is a web server that operates a portal site on which information about restaurants is posted. The restaurant information providing server 100 is connected via the Internet 50 to a plurality of user terminals 200 and restaurant terminals 300 of a plurality of restaurants.

[0033] The restaurant information providing server 100 provides a search system for restaurant information for users of the user terminal 200 on the above portal site. Specifically, the restaurant information providing server 100 searches for restaurant information that meets the search criteria based on a search request from the user terminal 200, generates a web page on which the search results are posted, and transmits it to the user terminal 200. In addition, the restaurant information providing server 100 substitutes for the reservation acceptance process for any restaurant from the user terminal 200 of the user who has viewed the restaurant information.

[0034] In addition, the restaurant information providing server 100 provides a management screen (web page) for restaurant information for restaurants (franchise stores) posted on the above portal site. The user of the restaurant terminal 300 can edit and update the restaurant information on the web page provided to the general user as the above search results via the management screen, and upload the web page onto the above portal site.

[0035] The user terminal 200 (200A, 200B,...) is a terminal used by the user, and is, for example, a smartphone, a mobile phone, a tablet PC, or the like. The user terminal 200 accesses the restaurant information providing server 100, receives the above web page, and displays it on the screen by a browser or the like.

[0036] The user terminal 200 determines the search criteria for restaurants on the above portal site based on the user's operation, and transmits a restaurant search request based on the search criteria to the restaurant information providing server 100.

[0037] On the other hand, the restaurant information providing server 100 can receive orders for food and drinks at each table of a restaurant from users who use each table T of the restaurant via the user terminal 200. For example, when the user terminal 200 reads a two-dimensional barcode C printed and placed on a card, plate, stand, etc. at each table of the restaurant, and a table usage start request is sent to the restaurant information providing server 100 based on the read information (URL including the table ID), the restaurant information providing server 100 displays an order screen for the restaurant menu on the display unit of the user terminal 200.

[0038] Then, when the restaurant information providing server 100 receives the input of the user's order via the order screen, it sends the received order information to the restaurant terminal (POS terminal) 300 of the restaurant. The order information is transferred from the restaurant terminal 300 to a terminal in the kitchen (not shown). Also, the restaurant information providing server 100 accumulates the received order information, and when it receives a request for settlement processing from the user, it ends the order reception process from the user terminal 200 and waits for an order request (reading of the two-dimensional barcode C) from the next customer.

[0039] In this way, the user terminal 200 also functions as a mobile order terminal for receiving orders from users who use each table T of the restaurant and sending the order information to the restaurant information providing server 100. An application (hereinafter also referred to as an MO application) capable of executing processing related to mobile orders in cooperation with the restaurant information providing server 100 may be installed on the user terminal 200.

[0040] The restaurant terminal 300 is a terminal installed in each restaurant, such as a tablet PC, a notebook PC, a desktop PC, etc. Based on the operation of the administrator, the restaurant terminal 300 can execute processing related to its own restaurant information, such as editing and updating the above-mentioned restaurant information, through communication with the restaurant information providing server 100. In addition, the restaurant terminal 300 mediates communication between the restaurant information providing server 100 and the kitchen terminal or the POS terminal in the above mobile order processing. Of course, the restaurant terminal 300 may also serve as the above kitchen terminal or POS terminal and communicate directly with the restaurant information providing server 100.

[0041] By the way, in the conventional mobile order system, especially in restaurants with a high customer turnover rate, there is a case where the accounting of a customer who has finished eating at a certain table is in an unfinished state (for example, the customer is waiting in line at the cash register for accounting), and the next customer is guided to the table, and an order is added to the ticket of the previous customer.

[0042] Therefore, in this embodiment, as shown in the figure, the restaurant information providing server 100 can forcibly switch the ticket ID (ticket number) that identifies the ticket of a customer at a predetermined set time at a single table T regardless of whether the previous customer has completed the accounting (before the session of the previous customer ends), especially when the restaurant is crowded, and start the next session. The details of the automatic switching process of the ticket ID will be described later.

[0043] [Hardware Configuration of Restaurant Information Providing Server] FIG. 2 is a diagram showing the hardware configuration of the above-mentioned restaurant information providing server 100. As shown in the figure, the restaurant information providing server 100 includes a CPU (Central Processing Unit) 11 (server control unit), a ROM (Read Only Memory) 12, a RAM (Random Access Memory) 13, an input / output interface 15, and a bus 14 that connects these to each other.

[0044] The CPU 11 appropriately accesses the RAM 13 or the like as necessary, and comprehensively controls the entire blocks of the food service information providing server 100 while performing various arithmetic processes. The ROM 12 is a non-volatile memory in which firmware such as an OS, programs, and various parameters to be executed by the CPU 11 are fixedly stored. The RAM 13 is used as a working area of the CPU 11 or the like, and temporarily holds an OS, various applications being executed, and various data being processed.

[0045] Connected to the input / output interface 15 are a display unit 16, an operation reception unit 17, a storage unit 18, a communication unit 19, and the like.

[0046] The display unit 16 is a display device using, for example, an LCD (Liquid Crystal Display), an OELD (Organic ElectroLuminescence Display), a CRT (Cathode Ray Tube), or the like.

[0047] The operation reception unit 17 is, for example, a pointing device such as a mouse, a keyboard, a touch panel, or other input devices. When the operation reception unit 17 is a touch panel, the touch panel can be integrated with the display unit 16.

[0048] The storage unit 18 is a non-volatile memory such as an HDD (Hard Disk Drive), a flash memory (SSD; Solid State Drive), or other solid-state memories. Stored in the storage unit 18 are the above-mentioned OS, various applications, and various data.

[0049] Particularly in this embodiment, the storage unit 18 stores data, applications, and other programs for the food service information providing server 100 to execute mobile order processing and automatic ticket ID switching processing described later. As will be described later, the storage unit 18 has a food service information database, a user information database, and a POS information database as databases including such data.

[0050] The communication unit 19 is various modules for wireless communication such as, for example, an NIC (Network Interface Card) for Ethernet or a wireless LAN, and is responsible for communication processing between the user terminal 200 and the restaurant terminal 300.

[0051] [Database Configuration of Restaurant Information Providing Server] FIG. 3 is a diagram showing the configuration of the database possessed by the restaurant information providing server 100.

[0052] As shown in the figure, the restaurant information providing server 100 has a restaurant information database 31, a user information database 32, and a POS information database 33 in the storage unit 18.

[0053] The restaurant information database 31 stores, for each restaurant, the name of the restaurant, location information (address or latitude and longitude), area information, access information (nearest station information, walking distance information from the nearest station), telephone number, an ID (store ID) for identifying the restaurant, genre information on the business type and services of the restaurant, information for introducing the restaurant (information indicating the characteristics of the store such as a PR text of the store, event information held by the restaurant, etc.), image data related to the restaurant (for introducing the restaurant), menu information related to the menu provided by the restaurant, average budget information, business hours, website URL, and other information. These information are input from the restaurant terminal 300 of each restaurant via the management screen provided by the restaurant information providing server 100.

[0054] The above menu information is information corresponding to the menus posted on the website of each restaurant on the portal site, and stores the menu names of a plurality of menus that each restaurant can provide, for each restaurant. The menu information may be stored for each menu category such as, for example, appetizer / main course / meat dish / fish dish / carbohydrates / side menu, lunch / dinner / course, etc. In addition to character information indicating the menu name, price, description, etc., the menu information also stores image information such as a photo taken of the menu in an associated manner. Furthermore, information on the calories, quantity, and raw materials of each menu may also be stored.

[0055] The above genre information may include more detailed sub-categories such as yakitori and tempura in Japanese cuisine, and pasta and pizza in Italian cuisine, in addition to main categories such as Japanese cuisine, Chinese cuisine, Italian cuisine, French cuisine, and barbecue.

[0056] The user information database 32 stores information about users who are users (members) of the restaurant information service provided via the portal site provided by the above restaurant information providing server 100 and own the user terminal 200. Specifically, the user information database 32 stores information such as user ID, password, name, email address (and other information that is the destination of messages), phone number, address, age (group), gender, and birthday for each user.

[0057] The POS information database 33 stores POS data based on orders received from the user terminal 200 at each table T. The POS data is composed of, for example, table ID, ticket ID, entry time, number of customers, ordered menu, number of orders (quantity), sales amount, and order time.

[0058] In this embodiment, the restaurant information providing server 100 can switch between a normal mode (first mode) in which the ticket ID of each table T is switched for each settlement of each table T (a new ticket ID is generated for each settlement), and a congestion mode (second mode) in which the ticket ID is automatically switched based on the elapsed time since the start of use of the table T when the restaurant is congested (a new ticket ID is generated when a predetermined set time has elapsed). The POS information database 33 also stores information about the mode currently being executed among the normal mode and the congestion mode.

[0059] Among these, when in the congestion mode, the POS information database 33 stores, for each table T in the restaurant, the count information of the elapsed time since the two-dimensional barcode C was read by the user terminal 200 and a table usage start request was received. The elapsed time is reset when a table usage start request is received immediately after from the table T (or its user terminal 200).

[0060] These databases are mutually referred to and used as necessary in the mobile order processing by the restaurant information providing server 100.

[0061] [System Operation] Next, the operation of the system configured as described above (mainly the restaurant information providing server 100) will be described. The operation is executed by the cooperation of the hardware such as the CPU 11 of the restaurant information providing server 100 and the software stored in the storage unit 18. In the following description, for convenience, the CPU 11 is taken as the main operating body.

[0062] FIG. 4 is a flowchart showing the flow of the slip ID automatic switching process when receiving a mobile order by the restaurant information providing server 100. In this operation, it is assumed that the restaurant information providing server 100 has already started the mobile order receiving operation in the normal mode.

[0063] First, the CPU 11 of the restaurant information providing server 100 determines whether the degree of congestion in the restaurant has reached a predetermined threshold or more (step 41). The CPU 11 may calculate the degree of congestion, for example, as the ratio of the number of currently used tables T to the total number of tables T. In this case, the number of used tables T may be counted as the number of used slip IDs, or for example, sensors for detecting the presence or absence of use (human sensors such as temperature sensors and optical sensors) may be installed on each table T and counted from the output of the sensors.

[0064] When it is determined that the above congestion level has reached a predetermined threshold or higher (Yes in step 41), the CPU 11 switches the above normal mode to a congestion mode and updates the mode information in the above POS information database 33 (step 42).

[0065] Subsequently, the CPU 11 determines whether it has received a request to start using the first table T in the congestion mode (table ID) from the user terminal 200 via the two-dimensional barcode C of any table T (step 43). Note that the operation by the user to start such use (the operation of reading the two-dimensional barcode C) is also referred to as "check-in". The request to start using may include a different terminal ID for each user terminal 200 that is the transmission source.

[0066] The request to start using table T may include, in addition to the above table ID, information regarding the number of users using the table T. When the CPU 11 determines that it has received the above table ID (Yes in step 43), it generates a slip ID for the table T to be used and stores it in the above POS information database 33, and starts counting the usage time (step 44).

[0067] Subsequently, the CPU 11 stores the above number-of-users information in the POS information database 33 and transmits an order screen for mobile orders to the user terminal 200 (step 45).

[0068] Subsequently, the CPU 11 determines whether it has newly received a table ID from the user terminal 200 via the two-dimensional barcode C of the table T to be used (step 46).

[0069] Subsequently, the CPU 11 refers to the above POS information database 33 and determines whether the usage time from the reception of the previous table ID has elapsed the set time at the time of receiving the new table ID (step 47). Here, the set time is, for example, 10 minutes, 15 minutes, 20 minutes, etc., but is not limited thereto.

[0070] When it is determined that the usage time at the time of receiving the above table ID has elapsed the set time since the previous reception (Yes in step 47), the CPU 11 generates a new slip ID different from the slip ID stored in the POS information database 33 until then, updates the information, and starts counting the usage time (step 48).

[0071] On the other hand, when it is determined that the usage time at the time of receiving the above table ID has not elapsed the set time since the previous reception (No in step 47), the CPU 11 maintains the current slip ID, resets the usage time being counted in the POS information database 33 (step 49), returns to step 46 above, and repeats the subsequent processing. Here, when it is determined that the set time has not elapsed, the counting of the usage time from the beginning may be continued without resetting the usage time.

[0072] Subsequently, the CPU 11 determines whether there is an end trigger for the congestion mode (step 50).

[0073] When it is determined that there is no end trigger for the congestion mode (No in step 50), the CPU 11 returns to step 46 above and repeats the subsequent processing.

[0074] On the other hand, when it is determined that there is an end trigger for the congestion mode (Yes in step 50), the CPU 11 switches the congestion mode to the normal mode and ends (step 51). The end trigger is, for example, when the above congestion level becomes less than the above predetermined threshold value (or a different threshold value), when an end instruction for the congestion mode is transmitted from an employee's terminal to the food service information providing server 100, when a predetermined time (for example, 1 hour, 2 hours) has elapsed since the start of the congestion mode, when a set time (for example, the end time of lunch time) has arrived, etc., but is not limited to these.

[0075] FIG. 5 is a diagram conceptually showing the slip ID switching process when the usage time at the time of receiving the above new table ID has elapsed the set time along the time axis.

[0076] As shown in the figure, after a certain customer A checks in at table A and a ticket ID "001" is generated, if another customer B checks in at table A after the usage time has elapsed the above-set time, regardless of whether customer A is waiting for billing or has completed billing, a new ticket ID "002" is generated for customer B separately from the above ticket ID "001".

[0077] In this case, not only when customer B is someone other than customer A, but also when customer B is a member who dines with customer A, separate ticket IDs are generated for both of them, and the orders from their respective user terminals 200 are processed separately. When customer A and customer B dine together, they may be billed individually with each ticket ID, or the employee may sum up the two tickets on the POS terminal at the time of billing.

[0078] FIG. 6 is a diagram conceptually showing, along the time axis, the ticket ID switching process when the usage time has not elapsed the above-set time at the time of receiving the above new table ID.

[0079] As shown in the figure, after a certain customer A checks in at table A and a ticket ID "001" is generated, if another customer B checks in at table A before the usage time has elapsed the above-set time, the ticket ID "001" is maintained, and the usage time is reset starting from the time of customer B's check-in so as to count, and the order from customer B's user terminal 200 also converges to the said ticket ID "001". Also, although the tickets converge due to customer B's check-in, the reset of the usage time may be executed at the time of the first order from customer B's user terminal 200.

[0080] In this way, when another customer starts using the same table before the set time has elapsed, by regarding the other customer as a co-diner of the original customer and recalculating the usage time based on the start time of the other customer's use, it is possible to ensure the dining time of the other customer.

[0081] FIG. 7 is a diagram showing an example of a POS register screen that the food service information providing server 100 causes the food service terminal 300 (or a POS terminal or a cashier terminal) to display.

[0082] As shown in this figure, in addition to general display items including a slip ID 60 and the like on the POS register screen, the food service information providing server 100 may display, on the POS register screen, a mode switching button 61 as a user interface for switching the current mode to another mode, together with information indicating the current mode among the normal mode and the congestion mode. In the example of this figure, the current mode is the normal mode, and the mode switching button 61 for switching to the congestion mode is displayed.

[0083] Thereby, an employee can manually perform mode switching according to the congestion situation and other various situations in the food service. The pressing operation of the mode switching button 61 can also serve as an "end trigger for the congestion mode" in step 50 of FIG. 4 above. Further, the pressing operation can also serve as a start trigger for the congestion mode in step 42 of FIG. 4, and otherwise, an employee may manually switch the congestion mode / normal mode from the food service terminal 300, a handy terminal, or the like.

[0084] [Summary] As described above, according to the present embodiment, the food service information providing server 100 can prevent a situation where, in a mobile order system of a food service, a customer at the next table places an order on the same slip while the accounting for the customer in front of the table remains incomplete, by forcibly switching the slip ID based on a predetermined set time regardless of whether the customer has completed the accounting.

[0085] [Modification Example] The present invention is not limited only to the above-described embodiment, and various changes can be made without departing from the gist of the present invention.

[0086] In the above-described embodiment, the food service information providing server 100 has been executed by switching between the normal mode and the congestion mode, but the congestion mode (automatic slip ID switching process) may always be executed as a single mode.

[0087] In the above-described embodiment, when the food and beverage store information providing server 100 receives the table ID from the user terminal 200, it starts counting the elapsed time from that point, and when it receives the table ID immediately after that, it determines whether the elapsed time exceeds the set time (such as 15 minutes). Instead of this, the food and beverage store information providing server 100 may start counting the elapsed time at the time of receiving the first order (when receiving order information), rather than at the time of receiving the table ID from the user terminal 200, considering that there are customers who take time from the start of using the table to placing an order.

[0088] In the above-described embodiment, when the food and beverage store information providing server 100 receives additional order information from the user terminal 200 after receiving the first order information after generating the slip ID, it may reset the set time with the time of this reception as the starting time. With this configuration, when the food and beverage store information providing server 100 receives an additional order before the set time has elapsed, it can ensure the dining time for the additional order by restarting the count of the set time based on the time of the additional order.

[0089] In the above-described embodiment, the food and beverage store information providing server 100 may change the length of the set time in response to a predetermined trigger. Here, the predetermined trigger includes, but is not limited to, time (time zone or time of day, etc.), congestion level, manual operation by an employee via the store management screen, etc. For example, the set time may be 15 minutes during lunchtime and 30 minutes during dinnertime. Also, it may be preset so that the set time becomes longer as the congestion level increases or as the number of orders increases. With this configuration, the food and beverage store information providing server 100 can adjust the timing until automatically switching the slip according to various situations in the food and beverage store.

[0090] In the above-described embodiment, when the set time has elapsed since the start of use of the user's table T, the food and beverage store information providing server 100 may display information prompting the user to settle the bill on the mobile order screen of the user terminal 200. With this configuration, the food and beverage store information providing server 100 can prompt customers who have not settled the bill within the set time to settle the bill, so that even if the ticket ID is switched, the next customer can be quickly guided to the table T and the ticket after the switch can be used.

[0091] In the above-described embodiment, an example in which a ticket ID is assigned to each table T is shown. Instead of this, the two-dimensional barcode C may be installed for each seat of the table T, and a ticket ID may be assigned and managed for each seat. For example, when there are four seats in one table T, a ticket ID is assigned to each of the four seats, or to every two seats. As a result, within each seat in one table T, the switching process of the ticket ID is independently executed according to the above-mentioned usage time.

[0092] In the above-described embodiment, after the set time has elapsed since the start of use of the user's table T, if a user who has stayed for the set time or longer reads the two-dimensional barcode C again and makes an additional order request, the order will be associated with the ticket ID of the next customer switched due to the elapse of the set time. Therefore, the food and beverage store information providing server 100 may manage the session by, for example, using a Cookie or a session ID to identify the communication partner with the time point when the table ID is received from the user terminal 200 as the start time of the session. Even when a new table ID is received from the user terminal 200, as long as the previous session continues (access from the same session ID as before), the previous ticket ID is maintained even after the set time has elapsed, and if there is an additional order request in the session, the order is added to the ticket ID. When it is confirmed that the previous session has ended (access from a different session ID than before) after the set time has elapsed, the ticket ID may be switched. This can prevent an order added by the previous customer by re-reading the two-dimensional barcode C after the set time has elapsed from being added to the ticket ID of the next customer.

[0093] The processing of the restaurant information providing server 100 in the above embodiment may be executed in a distributed manner by a plurality of servers. For example, the order reception processing for mobile orders and the ticket ID switching processing may be executed by separate servers.

[0094] In the above embodiment, in order to prevent the situation where the next customer at the same table places an order on the same ticket while the settlement for the customer in front of the table is incomplete and the orders of both customers are mixed, the restaurant information providing server 100 forcibly switches the ticket ID when a predetermined set time has elapsed since the start of use (check-in or first order) of the table T, regardless of whether the customer has completed settlement. Instead of this, after a predetermined set time has elapsed since the start of use of the table T by a certain user, the restaurant information providing server 100 may restrict the generation of a new ticket ID and the reception of an order (display of the order screen) until the settlement processing for the ticket ID of the user who has already checked in is completed even if there is a check-in request from another user to the same table T (seating restriction processing). By this seating restriction processing, the problem of the above-mentioned mixed orders can also be avoided.

[0095] In this case, for example, after a certain customer A checks in to table A and the ticket ID "001" is generated, if another customer B attempts to check in (operation of reading the two-dimensional barcode C) to the same table A on the user terminal 200, the CPU 11 determines whether the elapsed time since the check-in (or first order) of customer A exceeds the above set time (for example, 10 minutes, 15 minutes, etc.). And when it is determined that the elapsed time exceeds the set time, the CPU 11 rejects the check-in and displays an error message on the user terminal 200 of customer B indicating that the check-in cannot be performed because the previous customer has not completed settlement. On the other hand, when it is determined that the elapsed time does not exceed the set time, since customer B is likely to be a companion of the above customer A, the CPU 11 permits the check-in, transmits an order screen for mobile orders to the user terminal 200 of customer B, and enables the reception of an order.

[0096] After the generation of a new slip ID and the reception of orders are restricted, if the CPU 11 receives a regulation release request from an employee's terminal, it releases the regulation and allows a new customer check-in. For example, after customer A checks in and customer B, who is accompanying customer A, arrives at the store after exceeding the set time, if customer A notifies the employee to that effect and the employee presses the regulation release button displayed on the setting screen of table A on the application of the employee's terminal, a regulation release request including the table ID of table A is sent from the employee's terminal to the food and beverage store information providing server 100.

[0097] As a result, the above regulation for table A is released. When customer B checks in, an order screen for mobile orders is sent to the user terminal 200 of customer B, and orders can be accepted. In the display of the error message at the time of the above seating regulation, a message may be displayed to call out to the employee to release the seating regulation when sitting with a customer before settlement. Also, in this case, for table A, the set time is counted based on the check-in time of customer B, and when the set time elapses, the seating regulation is performed again.

[0098] Also in this seating regulation process, the food and beverage store information providing server 100 may change the length of the above set time according to a predetermined trigger. Here, the predetermined trigger is time (time zone or time of day, etc.), congestion level, manual operation of the employee via the store management screen, etc., but is not limited to these. For example, the set time may be 15 minutes during lunch time and 30 minutes during dinner time. Also, it may be preset so that the set time becomes longer as the congestion level increases or as the number of orders increases. With this configuration, the food and beverage store information providing server 100 can adjust the timing from check-in to the start of seating regulation according to various situations in the food and beverage store. Also, the time zone for executing the seating regulation process (for example, 12:00~14:00, 18:00~20:00, etc.) may be settable from the employee's terminal.

[0099] In addition, in the above seating restriction process, when the set time has elapsed since the user started using the table T, the food and beverage store information providing server 100 may display information prompting the user to settle the bill on the mobile order screen of the user terminal 200. With this configuration, the food and beverage store information providing server 100 can prompt customers who have not settled the bill within the set time to settle the bill, thereby minimizing the seating restriction time and quickly guiding the next customer to the table T.

[0100] In the above-described embodiment, an example was shown in which the food and beverage store information providing server 100 on the cloud executes a food and beverage store search process for a plurality of user terminals 200. However, a server having the same function as the above food and beverage store information providing server 100 may be installed for each food and beverage store, and the control process of the above menu ordering interface may be executed.

[0101] In the above-described embodiment, an example was shown in which the present invention is applied to a mobile order system that can be ordered from the user terminal 200. However, the present invention can be similarly applied to an order terminal installed in each food and beverage store, that is, a tabletop order system that can be ordered from a tabletop terminal installed on each table T, a smart speaker order system that can be ordered from a smart speaker (with a microphone) installed on each table T, and other systems that can be ordered from a floor robot that patrols the floor of the food and beverage store.

[0102] Among the inventions described in the claims of the present application, the invention described as "information processing method" is such that each step thereof is automatically performed by at least one device such as a computer by information processing using software, and is not performed by a human using a device such as a computer. That is, the "information processing method" is an information processing method using computer software, and is not a method of operating a computing tool called a computer by a human.

Explanation of Reference Numerals

[0103] 11…CPU 12…ROM 13…RAM 14…Bus 15... Input / Output Interface 18... Memory Unit 19... Communication Unit 31... Restaurant Information Database 32... User Information Database 33... POS Information Database 61... Mode Switch Button 100... Restaurant Information Providing Server 200... User Terminal 300... Restaurant Terminal C... Code (2D Barcode)

Claims

1. when initially receiving table identification information from a first user terminal that identifies a table or seat in a restaurant used by a user of the first user terminal, generating slip identification information corresponding to the table identification information and displaying an order screen on the first user terminal; after generating the slip identification information, when the same table identification information is received from a second user terminal, determining whether or not a predetermined time has elapsed since the table identification information or the first order information was received from the first user terminal; if it is determined that the predetermined time has elapsed, the control unit restricts the generation of new slip identification information and the display of the order screen on the second user terminal until a notification of completion of the transaction processing corresponding to the generated slip identification information is received. An information processing system comprising:

2. 2. The information processing system according to claim 1, When the control unit determines that the predetermined time has not elapsed, the control unit causes the second user terminal to display the order screen. Information processing system.

3. 3. The information processing system according to claim 1, When the control unit receives a request to lift the restriction, including the table identification information, from a terminal of an employee of the restaurant after the generation of the new slip identification information and the display of the order screen have been restricted, the control unit lifts the restriction on the display of the order screen corresponding to the table identification information and causes the second user terminal to display the order screen. Information processing system.

4. 3. The information processing system according to claim 1, The control unit changes the length of the predetermined time in response to a predetermined trigger. Information processing system.

5. 3. The information processing system according to claim 1, The control unit displays, when the predetermined time has elapsed, information prompting the user to make a payment on the order screen. Information processing system.

6. when initially receiving table identification information from a first user terminal that identifies a table or seat in a restaurant used by a user of the first user terminal, generating slip identification information corresponding to the table identification information and displaying an order screen on the first user terminal; after generating the slip identification information, when the same table identification information is received from a second user terminal, determining whether or not a predetermined time has elapsed since the table identification information or the first order information was received from the first user terminal; When it is determined that the predetermined time has elapsed, generation of new slip identification information for the second user terminal and display of the order screen are restricted until a completion notice of accounting processing corresponding to the generated slip identification information is received. Information processing method. **Claim 7** In an information processing apparatus, when first receiving table identification information for identifying a table or seat of a restaurant used by a user of the first user terminal from the first user terminal, generating slip identification information corresponding to the table identification information and causing the first user terminal to display an order screen; after generating the slip identification information, when receiving the same table identification information from a second user terminal, determining whether or not a predetermined time has elapsed since receiving the table identification information or first order information from the first user terminal; when it is determined that the predetermined time has elapsed, restricting generation of new slip identification information for the second user terminal and display of the order screen until a completion notice of accounting processing corresponding to the generated slip identification information is received A program for causing the above to be executed.

Images