System

Abstract

To more suitably accept orders.SOLUTION: A system capable of accepting an in-store customer order, which is order made by a customer's portable terminal in a store, is provided with: reading means for reading table identification information for identifying a table in the store; authentication information acquisition means for acquiring authentication information for authenticating the in-store customer order; and authentication information registration means for registering the table identification information as the authentication information for authenticating the in-store customer order of the table identified by the table identification information when the table identification information is read by the reading means and the authentication information is acquired by the authentication information acquisition means.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a system.

Background Art

[0002] A system is known in which a staff member (employee) of a restaurant receives an order from a customer using an order terminal (see, for example, Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, there is room for improvement in receiving orders within the store.

[0005] The present invention has been made in view of such circumstances, and an object thereof is to provide a technique for more suitably receiving orders.

Means for Solving the Problems

[0006] A system which is one aspect for solving the above-described problems is a system capable of receiving an in-store customer order which is an order using a customer's own mobile terminal within the store, the system including: a reading unit that reads table identification information for identifying a table within the store; an authentication information acquisition unit that acquires authentication information for authenticating the in-store customer order; and an authentication information registration unit that registers the authentication information as the authentication information for authenticating the in-store customer order of the table identified by the table identification information when the table identification information is read by the reading unit and the authentication information is acquired by the authentication information acquisition unit.

Brief Description of the Drawings

[0007]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Embodiments for Carrying Out the Invention

[0008] The order management system 1 of this embodiment is introduced, for example, into the store ST of a restaurant. In the store ST, customers who come to the store are guided to tables, the ordered items of the customers are cooked, and served to the tables. In the store ST, in addition to the store staff operating the terminal (the store staff order terminal 10 (described later)) to receive orders from customers, the customers themselves can also operate their own terminals (mobile terminals 20 (described later)) to place orders. That is, in the store ST, customers can either call the store staff to place an order or place an order using their own terminals. Hereinafter, the product order using the customer's own terminal in the store ST may be referred to as "in-store mobile order" or "self-terminal self-order" or "in-store customer order", etc.

[0009] A two-dimensional code (hereinafter, may be referred to as a store-provided code) for implementing in-store mobile orders is provided on each table in the store ST. Specifically, a sheet printed with the store-provided code is placed on each table in the store ST. The store-provided code is a two-dimensional code in which the table number of each table and a URL (hereinafter, referred to as the "access URL") that can access the order management server 30 (described later) are two-dimensionally coded.

[0010] FIG. 1 is a diagram showing a configuration example of the order management system 1. As shown in FIG. 1, the order management system 1 includes a store staff order terminal 10, a mobile terminal 20, an order management server 30, a kitchen printer 40, a payment terminal 50, a wireless router 60, and a gateway 70. Note that a configuration excluding some of the store staff order terminal 10, the mobile terminal 20, the order management server 30, the kitchen printer 40, the payment terminal 50, the wireless router 60, and the gateway 70 may also be referred to as the order management system 1.

[0011] The kitchen printer 40, the payment terminal 50, the wireless router 60, and the gateway 70 are installed within the store ST. These are connected to the LAN 80 laid within the store ST and can communicate with each other via the LAN 80. The wireless router 60 functions as an access point to wireless communication devices. The gateway 70 relays the LAN 80 and an external network (for example, the Internet). Also, within the store ST, there are the staff order terminals 10 and the mobile terminals 20. The order management server 30 is installed outside the store ST (for example, at the head office, data center, etc.). The order management server 30 may be referred to as a cloud server.

[0012] Figure 2 is a diagram showing a configuration example of the staff order terminal 10. The staff order terminal 10 is a terminal for the staff to input, etc., the orders received from customers. In FIG. 1, two staff order terminals 10 are shown, but the number of staff order terminals 10 used within the store ST is not particularly limited. As shown in FIG. 2, the staff order terminal 10 includes a control unit (CPU) 11, a touch panel 12, a communication unit 13, and a storage unit 15. The control unit 11 controls the entire staff order terminal 10. For example, the functions as the staff order terminal 10 are realized by the control unit 11 as hardware executing a program. The touch panel 12 functions as a display unit and an operation unit. The communication unit 13 communicates with each device within the LAN 80 via, for example, the wireless router 60, and further communicates with the order management server 30 via the gateway 70. The storage unit 15 stores various information.

[0013] FIG. 3 is a diagram showing a configuration example of the mobile terminal 20. The mobile terminal 20 is a smartphone or a tablet terminal possessed by a customer who has come to the store. As described above, in the store ST, the customer himself / herself can order products by operating the mobile terminal 20. Although two mobile terminals 20 are shown in FIG. 1, the number of mobile terminals 20 used in the store ST is not particularly limited (the number of mobile terminals 20 existing in the store ST depends on the number of customers who come to the store, etc.). As shown in FIG. 3, the mobile terminal 20 includes a control unit (CPU) 21, a touch panel 22, a communication unit 23, a camera 24, and a storage unit 25. The control unit 21 controls the entire mobile terminal 20. For example, the functions of the mobile terminal 20 are realized by the control unit 21 as hardware executing a program. The touch panel 22 functions as a display unit and an operation unit. The communication unit 23 communicates with the order management server 30 via, for example, an external network (e.g., the Internet). Note that the communication unit 23 may communicate with the order management server 30 via the wireless router 60 (LAN80). The camera 24 generates a captured image by imaging. Note that the control unit 21 has a function (code reading function) of performing image recognition (e.g., recognizing barcodes and two-dimensional codes) on the captured image generated by the camera 24. The storage unit 25 stores various information.

[0014] FIG. 4 is a diagram showing a configuration example of the order management server 30. The order management server 30 is a server that manages orders. As shown in FIG. 4, the order management server 30 includes a control unit (CPU) 31, a communication unit 33, and a storage unit 35. The control unit 31 controls the entire order management server 30. For example, the functions of the order management server 30 are realized by the control unit 31 as hardware executing a program. The communication unit 33 communicates with each device in the LAN80 via, for example, the gateway 70, and further communicates with the store clerk order terminal 10 via the wireless router 60. Also, the communication unit 33 communicates with the mobile terminal 20 via an external network. The storage unit 15 stores various information (e.g., transaction information described later).

[0015] The kitchen printer 40 is a device that is installed in a cooking area or the like where cooking is performed in the store ST and prints and issues various media (hereinafter simply referred to as "issuing"). For example, the kitchen printer 40 issues a cooking instruction slip. The cooking instruction slip is a slip that prints the instruction content regarding the cooking of the product ordered by the store clerk operating the store clerk order terminal 10 or the product ordered by the customer operating the mobile terminal 20. In addition, the kitchen printer 40 issues a customer receipt slip. The customer receipt slip is a slip provided to the customer when serving the ordered product, and is a slip that prints the ordered product, the settlement amount (price), etc. In addition, the kitchen printer 40 issues an order confirmation slip. The order confirmation slip is a slip provided to the customer based on the request from the customer, and is a slip that prints all the ordered products and the settlement amount ordered so far.

[0016] The kitchen printer 40 may issue a customer receipt slip printed with a settlement code (described later). In addition, the kitchen printer 40 may issue an order confirmation slip printed with a settlement code (described later).

[0017] In addition, the kitchen printer 40 may issue a customer receipt slip printed with a store-provided code (a two-dimensional code obtained by two-dimensionally coding the table number of the table and the access URL). In addition, the kitchen printer 40 may issue an order confirmation slip printed with a store-provided code.

[0018] The settlement terminal 50 is a device that settles the price of the product ordered and provided (served). The settlement terminal 50 executes a settlement process in response to the operation of the customer. The settlement terminal 50 may be a device called a cash register or a POS terminal. The settlement terminal 50 may issue a slip (such as a cooking instruction slip, a customer receipt slip, an order confirmation slip, etc.) instead of the kitchen printer 40. The settlement terminal 50 may issue a slip (customer receipt slip, order confirmation slip) printed with a settlement code (described later) or a store-provided code. Note that the store clerk may operate the settlement terminal 50.

[0019] FIG. 5 is a configuration example of transaction information managed by the order management server 30. As shown in FIG. 5(A), the transaction information managed by the order management server 30 includes, as data items for storing respective data, transaction identification information (transaction ID), table number, customer information, password (sometimes referred to as "passcode"), transaction classification, transaction start time, transaction end time, settlement type, number of orders, total amount, and each order (order 1, order 2, ...). Note that for data items in which data is not stored, the data item itself may not exist.

[0020] The data item "transaction identification information" stores the transaction identification information of the transaction (the transaction information). The transaction identification information is information that can uniquely identify each transaction (transaction information). The transaction identification information may be information including a date. For example, the transaction identification information may be YYYYMMDD - serial number. Also, when there are multiple stores, the transaction identification information may be information including a store code.

[0021] The data item "table number" stores the table number at which the customer of the transaction is seated. The table number is information that can uniquely identify each table. The data item "customer information" stores the customer information (seating guidance information) of the customer of the transaction. The customer information includes customer layer (gender, age), number of people (number of guided people), presence or absence of coupon use, etc. Note that the data item "customer information" may store the number of mobile terminals 20 connected (number of connected people) and the identification information of the connected mobile terminals 20 (for example, Mac address, telephone number, etc.). The store - side device (for example, the order management server 30, the settlement terminal 50, the device installed in the store or the head office) can calculate various connection rates (the ratio of the number of connected people to the number of guided people) from the number of guided people and the number of connected people (the number of connected mobile terminals 20). For example, the store - side device can calculate the connection rate of all visitors to the store, the connection rate for each customer layer, the connection rate for each day of the week, and the connection rate for each time zone. Also, information on the number of guided people and the number of connected people can be used, for example, when implementing a campaign to improve the connection rate, for determining the period and target of the campaign, and for estimating and verifying the effect of the campaign.

[0022] The data item "PIN" stores the PIN set by the customer of the transaction. The customer sets the PIN when conducting an in-store mobile order. The PIN is authentication information used for authenticating the in-store mobile order. The PIN is, for example, a four-digit number.

[0023] The data item "Transaction type" stores the transaction type of the transaction (information indicating the current state of the transaction). For example, the value "1" of the transaction type indicates "in transaction (unsettled)", and the value "2" of the transaction type indicates "transaction completed (settled)". The data item "Transaction start time" stores the transaction start time of the transaction. The transaction start time is the time when the transaction is started (the time when the customer is guided to the table). The data item "Transaction end time" stores the transaction end time of the transaction. The transaction end time is the time when the transaction ends (the time when settlement is completed).

[0024] The data item "Payment type" stores the payment type of the transaction (payment method, settlement method). For example, the value "1" of the payment type is cash, the value "2" of the payment type is credit card, and the value "3" of the payment type is electronic money. The data item "Order count" stores the order count of the transaction (the number of orders made in the transaction). That is, one transaction includes one or more orders. The data item "Total amount" stores the total amount of the transaction (the total amount of one or more orders made in the transaction. That is, the sum of the order amounts).

[0025] The data item "Order 1" stores information regarding the first order in the transaction. The data item "Order 2" stores information regarding the second order in the transaction. When the order count in the transaction is M times, there are data items up to "Order M".

[0026] "Order 1" has, as data items, an order type, an order time, an order amount, and ordered items. The same applies to "Order 2" and subsequent orders.

[0027] In the data item "order type", the order type of the order is stored. The order type is a classification indicating the subject of the order (the person who performs the order operation). For example, the value "1" of the order type indicates a staff order (an order made by the staff order terminal 10), and the value "2" of the order type indicates a customer order (an order made by the mobile terminal 20, i.e., in-store mobile order). In the data item "order time", the order time (order reception time) of the order is stored. In the data item "order amount", the order amount (total amount of the ordered items) of the order is stored. In the data item "ordered items", the ordered items of the order are stored. The ordered items are information about the items ordered in each order. Specifically, as shown in Fig. 5(B), "ordered items" has, as data items, for each item (Item 1, Item 2,...), a product code (product name), a price, and a quantity. Note that if there are M types of items in the order, there are data items up to "Item M".

[0028] Note that the configuration of the transaction information shown in Fig. 5 is an example. For example, the transaction information may have a data item "staff information" that stores information (staff code) for identifying the staff and the identification number of the staff order terminal 10 when the value of the order type is "1 (staff order)". Also, the transaction information may have a data item "customer information" that stores the identification number of the mobile terminal 20 when the value of the order type is "2 (customer order)". Thereby, for example, the terminals (or orderers) that placed the orders can be distinguished and managed.

[0029] (Display example of the staff order terminal 10) The staff order terminal 10 displays various screens for the staff who is the operator. For example, the staff order terminal 10 displays a home screen, a seating guidance screen, an order reception screen, an order confirmation screen, etc. on the touch panel 12.

[0030] Figs. 6(A) to 6(E) are schematic diagrams of the respective screens displayed on the store clerk order terminal 10. Fig. 6(A) is a schematic diagram of the home screen. The store clerk order terminal 10 displays the home screen after power-on or after login authentication. As shown in Fig. 6(A), various buttons (such as a seating guidance button, an order button, etc.) are provided on the home screen.

[0031] Fig. 6(B) is a schematic diagram of the seating guidance screen. The seating guidance screen is a screen that is operated when guiding a customer who has come to the store to a table. The store clerk order terminal 10 displays the seating guidance screen based on the operation of the seating guidance button on the home screen (Fig. 6(A)). As shown in Fig. 6(B), an input area for inputting various seating guidance information (table number of the guided table, customer layer of the guided customer, number of customers in the guided group, presence or absence of a coupon, etc.) that the order management system 1 should acquire when guiding a customer to a table is provided on the seating guidance screen. Also, a back button, an order button, and a confirmation button are provided on the seating guidance screen. The order button and the confirmation button are operable (the operation becomes effective) when information (at least the table number) is input into the input area.

[0032] When the store clerk guides a customer who has come to the store to a table, inputs information into the input area, and then accepts an order without leaving the table, the store clerk operates the order button on the seating guidance screen. When the store clerk guides a customer who has come to the store to a table, inputs information into the input area, and then leaves the table once (when accepting an order when called again, when the customer himself uses the mobile terminal 20 to place an order, etc.), the store clerk operates the confirmation button on the seating guidance screen.

[0033] Figure 6(C) is a schematic diagram of the table designation screen. The store clerk order terminal 10 displays the table designation screen based on the operation of the order button on the home screen (Figure 6(A)). Also, the store clerk order terminal 10 displays the table designation screen based on the operation of the order button on the seat guidance screen (Figure 6(B)). As shown in Figure 6(C), the table designation screen is provided with an input area for entering the table number of the table for which a product has been ordered. The table designation screen is also provided with a back button and a confirmation button. The confirmation button is operable when the table number has been entered.

[0034] Figure 6(D) is a schematic diagram of the order reception screen. The store clerk order terminal 10 displays the order reception screen based on the operation of the confirmation button on the table designation screen (Figure 6(C)). As shown in Figure 6(D), the order reception screen is provided with buttons for selecting the type of product, an area for accepting the order operation for each individual product, and an area for displaying the products for which the order operation has been accepted. Note that the order reception screen in Figure 6(D) shows the state after the order operation for the product "omakase" has been accepted as one item in the order. The order reception screen is also provided with a cancel button and a confirmation button. The confirmation button is operable when the order operation for one or more products has been accepted. The order reception screen also displays the table number and the transaction ID (transaction identification information). When the store clerk has finished receiving the order, the store clerk operates the confirmation button on the order reception screen. That is, the store clerk operates the confirmation button after performing the necessary order operations on the order reception screen (Figure 6(D)).

[0035] Figure 6(E) is a schematic diagram of the order content confirmation screen. The store clerk's order terminal 10 displays the order content confirmation screen, for example, based on the operation of the confirmation button on the order reception screen (Figure 6(D)). As shown in Figure 6(E), the order content confirmation screen is provided with an area for displaying the products included in the order, an area for displaying the total amount of the order, etc. In addition, the order content confirmation screen is provided with a back button and a confirmation button. Also, the table number and transaction ID are displayed on the order content confirmation screen. When the store clerk finishes confirming the order content, the store clerk operates the confirmation button on the order content confirmation screen.

[0036] (Display example of the mobile terminal 20) The mobile terminal 20 displays various screens for the customer who is the operator. For example, the mobile terminal 20 displays a password input screen, a main screen, an order reception screen, a sharing screen, a settlement screen, etc. on the touch panel 22.

[0037] Figures 6(F) to 6(J) are schematic diagrams of the respective screens displayed by the mobile terminal 20. Figure 6(F) is a schematic diagram of the password input screen. The mobile terminal 20 displays the password input screen based on having read the store-provided code. As shown in Figure 6(F), the password input screen is provided with an area for inputting a password (for example, a 4-digit number) (input the set password for the first time, input the already set password for the second time and later). In addition, the password input screen is provided with a close button and a confirmation button. The confirmation button is operable when a password is input. Also, the table number is displayed on the password input screen. Note that a numeric keypad (number buttons) may be displayed on the password input screen.

[0038] Figure 6(G) is a schematic diagram of the main screen. The mobile terminal 20 displays the main screen, for example, based on the operation of the confirmation button on the password input screen (Figure 6(F)). As shown in Figure 6(G), the main screen is provided with an order button, a sharing button, and a settlement button. In addition, the main screen is provided with a close button. Also, the table number and transaction ID are displayed on the password input screen.

[0039] When a customer places an order using their own mobile terminal 20, they operate the order button on the main screen. When a customer causes another customer (family member, acquaintance, colleague, etc.) sitting at the same table to place an order using the other customer's mobile terminal 20, they operate the share button on the main screen. When a customer proceeds to payment (settlement), they operate the payment button on the main screen.

[0040] Figure 6(H) is a schematic diagram of the order reception screen. The mobile terminal 20 displays the order reception screen based on the operation of the order button on the main screen (Figure 6(G)). Also, the mobile terminal 20 displays the order reception screen based on reading a sharing code (the sharing code displayed on the sharing screen (Figure 6(I)) by another mobile terminal 20). As shown in Figure 6(H), the order reception screen is provided with buttons for selecting the type of product, an area for accepting the order operation of individual products, and an area for displaying the products for which the order operation has been accepted. Note that the order reception screen in Figure 6(H) shows the state after accepting the order operation for the product "omakase" as one item in the order. Also, the order reception screen is provided with a back button, a share button, and a confirmation button. The confirmation button is operable when the order operation for one or more products has been accepted. Also, the table number and transaction ID are displayed on the order reception screen.

[0041] When a customer proceeds with the order using their own mobile terminal 20, they operate the confirmation button after performing the order operation on the order reception screen. When a customer causes another customer sitting at the same table to place an order using the other customer's mobile terminal 20, they operate the share button on the order reception screen.

[0042] In addition, when the mobile terminal 20 displays an order reception screen based on reading the sharing code, for the table, an order for the product can be placed from the order reception screen, and by operating the sharing button on the order reception screen, the sharing screen (Fig. 6(I)) can be displayed. Therefore, when the mobile terminal 20 displays an order reception screen based on reading the sharing code, for example, it may display the table number, possible operations, etc., such as "Orders for table xx and the display of the sharing code are now available."

[0043] Fig. 6(I) is a schematic diagram of the sharing screen. The mobile terminal 20 displays the sharing screen based on the operation of the sharing button on the main screen (Fig. 6(G)). Also, the mobile terminal 20 displays the sharing screen based on the operation of the sharing button on the order reception screen (Fig. 6(H)). As shown in Fig. 6(I), the sharing screen displays a sharing code (reference symbol A in the figure) and a message instructing the mobile terminal 20 to read the sharing code. Also, a return button is provided on the sharing screen. Also, the table number and transaction ID are displayed on the sharing screen.

[0044] Fig. 6(J) is a schematic diagram of the settlement screen. The mobile terminal 20 displays the settlement screen based on the operation of the accounting button on the main screen (Fig. 6(G)). As shown in Fig. 6(J), the settlement screen displays a settlement code (reference symbol B in the figure) and a message instructing the settlement terminal 50 to read the settlement code. Also, a return button is provided on the settlement screen. Also, the table number and transaction ID are displayed on the settlement screen.

[0045] Note that the settlement terminal 50 starts the settlement process based on reading the settlement code (the settlement code displayed on the settlement screen (Fig. 6(J)) by the mobile terminal 20, the settlement code printed on the slip (customer copy slip, order confirmation slip)).

[0046] (Sharing code, settlement code) Describe the similarities and differences between the shared code and the settlement code. The shared code and the settlement code are the same (both are two-dimensional codes that two-dimensionally code the same type of information). Specifically, the shared code (settlement code) is a two-dimensional code that two-dimensionally codes a transaction ID and an access URL.

[0047] Note that the shared code (settlement code) may be a two-dimensional code that two-dimensionally codes a table number instead of or in addition to the transaction ID. That is, the shared code (settlement code) may be a two-dimensional code that two-dimensionally codes a transaction ID, a table number, and an access URL, or may be a two-dimensional code that two-dimensionally codes a table number and an access URL. In other words, the shared code (settlement code) is a two-dimensional code that two-dimensionally codes information that can directly or indirectly identify a transaction (at least one of a transaction ID and a table number) and an access URL. However, since the table is used by different customers one after another (because the table number does not unconditionally identify a transaction), from the perspective of preventing troubles, it is preferable that the shared code (settlement code) includes the transaction ID.

[0048] Also, the shared code and the settlement code may be different. For example, the settlement code may be a barcode or a two-dimensional code that codes a transaction ID, or may be a barcode or a two-dimensional code that codes a table number, or may be a barcode or a two-dimensional code that codes a transaction ID and a table number. That is, the shared code is a two-dimensional code that two-dimensionally codes information that can directly or indirectly identify a transaction (at least one of a transaction ID and a table number) and an access URL, but the settlement code may be a barcode or a two-dimensional code that codes information that can directly or indirectly identify a transaction (at least one of a transaction ID and a table number) (it does not have to be a code of the access URL).

[0049] (Operation of the Order Management System 1) Figs. 7 to 13 are explanatory diagrams for explaining the operation of the order management system 1. In the descriptions of Figs. 7 to 13, the operations of the wireless router 60 and the gateway 70 are omitted.

[0050] (Operation when a store clerk guides a customer to a table) Fig. 7 shows the operation when a store clerk guides a customer to a table. The store clerk guides the arriving customer to a table and operates the seat guidance button on the home screen (Fig. 6(A)) of the store clerk order terminal 10. Note that the store clerk order terminal 10 may send a request for acquiring the home screen to the order management server 30 after power-on or after login authentication, receive the screen information of the home screen from the order management server 30, and display the seat guidance screen. Alternatively, the store clerk order terminal 10 may store the screen information of the home screen in the storage unit 15 and display the home screen after power-on or after login authentication. Step S100: The store clerk order terminal 10 displays the seat guidance screen (Fig. 6(B)). Note that the store clerk order terminal 10 may send a request for acquiring the seat guidance screen to the order management server 30 based on the operation of the store clerk (operation of the seat guidance button on the home screen), receive the screen information of the seat guidance screen from the order management server 30, and display the seat guidance screen. Alternatively, the store clerk order terminal 10 may also receive the screen information of the seat guidance screen from the order management server 30 together with the screen information of the home screen, and display the seat guidance screen based on the operation of the store clerk. Alternatively, the store clerk order terminal 10 may store the screen information of the seat guidance screen in the storage unit 15 and display the seat guidance screen based on the operation of the store clerk. Step S101: The store clerk order terminal 10 receives an input of seat guidance information (table number, customer group, number of people, presence or absence of coupon, etc.) from the store clerk. Step S102: The store clerk order terminal 10 transmits the seat guidance information to the order management server 30 based on the operation of the store clerk (operation of the confirmation button on the seat guidance screen).

[0051] Step S103: The order management server 30 receives the seat guidance information. Step S104: The order management server 30 generates transaction information. For example, the order management server 30 may generate transaction information by setting (storing) values in respective data items as follows. In the data item "transaction identification information", the generated transaction identification information is set. In the data item "table number", the table number received as seat guidance information is set. In the data item "customer information", the customer layer, number of people, presence or absence of a coupon, etc. received as seat guidance information are set. In the data item "PIN", no value is set. In the data item "transaction category", the value "1 (in transaction)" is set. In the data item "transaction start time", the current time is set. In the data item "transaction end time", no value is set. In the data item "settlement type", no value is set. In the data item "number of orders", "0" is set. In the data item "total amount", "0" is set. Data items such as "order 1" are not generated.

[0052] (Operation when an order is placed by a store clerk (until the order reception screen is displayed)) FIG. 8 shows the operation when an order is placed by a store clerk (until the order reception screen is displayed). The store clerk operates the order button on the home screen (FIG. 6(A)) or the seat guidance screen (FIG. 6(B)). Step S200: The store clerk order terminal 10 displays a table designation screen (FIG. 6(C)). Note that the store clerk order terminal 10 may send a request for acquisition of the table designation screen to the order management server 30 based on an operation by the store clerk (operation of the order button), receive the screen information of the table designation screen from the order management server 30, and display the table designation screen. Alternatively, the store clerk order terminal 10 may receive the screen information of the table designation screen from the order management server 30 together with the screen information of the home screen (or the seat guidance screen), and display the table designation screen based on an operation by the store clerk. Alternatively, the store clerk order terminal 10 may store the screen information of the table designation screen in the storage unit 15 and display the table designation screen based on an operation by the store clerk. Step S201: The store clerk order terminal 10 accepts input of a table number from the store clerk. Step S202: Based on the operation of the store clerk (operation of the confirmation button on the table designation screen), the store clerk order terminal 10 sends a request to obtain an order reception screen to the order management server 30. For example, the store clerk order terminal 10 sends a request to obtain an order reception screen including the order type (value is "1 (store clerk order)") and the table number to the order management server 30.

[0053] Step S203: The order management server 30 receives the request to obtain the order reception screen. Step S210: The order management server 30 determines whether an order can be accepted. For example, if the value of the transaction classification of the transaction with the table number (the table number included in the request to obtain the order reception screen received from the store clerk order terminal 10) is "1 (in transaction)", the order management server 30 determines that an order can be accepted, and if the value of the transaction classification of the transaction with the table number is "2 (transaction completed)", the order management server 30 determines that an order cannot be accepted.

[0054] Step S220: The order management server 30 that determines that an order can be accepted sends the screen information of the order reception screen to the store clerk order terminal 10 together with the transaction ID of the transaction (the transaction with the table number included in the request to obtain the order reception screen received from the store clerk order terminal 10). Step S221: The store clerk order terminal 10 that has received the screen information of the order reception screen displays the order reception screen (Fig. 6(D)).

[0055] Step S230: The order management server 30 that determines that an order cannot be accepted sends error information (table invalid) to the store clerk order terminal 10. Step S231: The store clerk order terminal 10 that has received the error information (table invalid) displays the error information (table invalid). For example, the store clerk order terminal 10 displays the error information in a pop-up manner on the table designation screen (Fig. 6(C)) (displaying a small screen with the error information superimposed on the front of the table designation screen).

[0056] (Operations when an order is placed by a store clerk (after the order reception screen is displayed)) Figure 9 shows the operations during an order by a store clerk or a customer (after the display of the order acceptance screen). It is assumed that the store clerk order terminal 10 is displaying the order acceptance screen (Figure 6(D)) (step S221 in Figure 8). Step S301: The store clerk order terminal 10 receives an order input from the store clerk. Step S302: Based on the operation of the store clerk (operation of the confirmation button on the order acceptance screen), the store clerk order terminal 10 displays an order content confirmation screen (Figure 6(E)). Note that the store clerk order terminal 10 may send a request to obtain the order content confirmation screen to the order management server 30 based on the operation of the store clerk, receive the screen information of the order content confirmation screen from the order management server 30, and display the order content confirmation screen. Alternatively, the store clerk order terminal 10 may also receive the screen information of the order content confirmation screen, which is the next screen, together with the screen information of the order acceptance screen from the order management server 30, and display the order content confirmation screen based on the operation of the store clerk. Step S303: Based on the operation of the store clerk (operation of the confirmation button on the order content acceptance screen), the store clerk order terminal 10 sends the order information to the order management server 30. For example, the store clerk order terminal 10 sends order information including the order type (value is "1 (store clerk order)"), the transaction ID, and the order content (ordered products, prices, quantities, etc.) confirmed on the order content confirmation screen to the order management server 30.

[0057] Step S304: The order management server 30 receives the order information. Step S310: The order management server 30 determines whether the order can be accepted. For example, if the value of the transaction classification of the transaction with the transaction ID (included in the order information received from the store clerk order terminal 10) is "1 (in transaction)", the order management server 30 determines that the order can be accepted. If the value of the transaction classification of the transaction with the transaction ID is "2 (transaction completed)", the order management server 30 determines that the order cannot be accepted.

[0058] Step S320: The order management server 30 that has determined that it is possible to accept an order registers the order. For example, the order management server 30 sets (stores) values in the respective data items of the transaction (the transaction with the transaction ID included in the order information) as follows. For the data item "order count", a value obtained by adding "1" to the current value is set. For example, if the current value is "0" (if this order is the first order), "1" obtained by adding "1" to the current value "0" is set in the data item "order count", and if the current value is "1" (if this order is the second order), "2" obtained by adding "1" to the current value "1" is set in the data item "order count". Also, if this order is the Mth order, the data item "order M" is set based on the order information. For example, if this order is the first order, the data item "order 1" is set based on the order information, and if this order is the second order, the data item "order 2" is set based on the order information. Also, if this order is the Mth order, the data item "total amount" is set based on the order amounts of the data items "order 1" to "order M". For example, if this order is the first order, the order amount of the data item "order 1" is set in the data item "total amount", and if this order is the second order, the sum of the order amount of the data item "order 1" and the order amount of the data item "order 2" is set in the data item "total amount".

[0059] Step S321: The order management server 30 that has registered the order information transmits order reception completion information to the store clerk order terminal 10. Note that the order management server 30 may transmit the screen information of the home screen to the store clerk order terminal 10 instead of or in addition to the order reception completion information. Step S322: Subsequently, the order management server 30 transmits the slip data to the kitchen printer 40. For example, the order management server 30 transmits slip data including the transaction ID, the order amount, and the ordered items to the kitchen printer 40. The order management server 30 may transmit slip data including the order type (value is "1 (store clerk order)") to the kitchen printer 40.

[0060] Step S323: The store clerk order terminal 10 that has received the order acceptance completion information (or, instead of or in addition to the order acceptance completion information, the screen information of the home screen) displays the home screen (Fig. 6(A)). That is, since the order has been normally accepted, the screen of the store clerk order terminal 10 transitions from the order content confirmation screen (Fig. 6(E)) to the home screen (Fig. 6(A)).

[0061] Step S324: The kitchen printer 40 receives the slip data. Step S325: The kitchen printer 40 issues slips (cooking instruction slips, customer copies) based on the slip data. The kitchen printer 40 may issue a customer copy with the settlement code printed thereon. Also, the kitchen printer 40 may issue a customer copy with the store-provided code printed thereon instead of or in addition to the settlement code.

[0062] Step S330: The order management server 30 that has determined that an order cannot be accepted transmits error information (order acceptance not possible) to the store clerk order terminal 10. Step S331: The store clerk order terminal 10 that has received the error information (order acceptance not possible) displays the error information (order acceptance not possible). For example, the store clerk order terminal 10 displays the error information as a pop-up on the order content confirmation screen (Fig. 6(E)).

[0063] (Operations after reading the settlement code) Fig. 10 shows the operations after reading the settlement code. Step S401: The payment terminal 50 reads the settlement code. The settlement code may be the settlement code displayed on the payment screen (Fig. 6(J)) of the mobile terminal 20, or may be the settlement code printed on a slip (customer copy, order confirmation slip, etc.). Step S402: The payment terminal 50 that has read the settlement code transmits payment request information to the order management server 30. For example, the payment terminal 50 transmits payment request information including the transaction ID to the order management server 30.

[0064] Step S403: The order management server 30 receives the settlement request information. Step S410: The order management server 30 determines whether it is possible to accept the settlement. For example, if the value of the transaction classification of the transaction with the transaction ID (the transaction ID included in the settlement request information received from the payment terminal 50) is "1 (in transaction)", the order management server 30 determines that it is possible to accept the settlement. If the value of the transaction classification of the transaction with the transaction ID is "2 (transaction completed)", the order management server 30 determines that it is not possible to accept the settlement.

[0065] Step S420: The order management server 30 that determines that it is possible to accept the settlement transmits settlement information (a part of the transaction information of the transaction) to the payment terminal 50. For example, the order management server 30 transmits settlement information including the transaction ID, the total amount, and the ordered items to the payment terminal 50. The order management server 30 may further transmit settlement information including the order type (the order type for each order) to the payment terminal 50. Thereby, the payment terminal 50 can issue a receipt that prints whether the order (order 1, order 2,...) was placed by the store clerk or by the customer himself.

[0066] Step S421: The payment terminal 50 receives the settlement information. Step S422: The payment terminal 50 executes the settlement process. For example, the payment terminal 50 executes the settlement process by the settlement method selected by the customer while displaying a settlement screen (not shown). Step S423: The payment terminal 50 transmits settlement completion information including the transaction ID and the settlement type to the order management server 30. Step S424: The payment terminal 50 issues a receipt.

[0067] Step S425: The order management server 30 receives the settlement completion information. Step S426: The order management server 30 registers the completion of the transaction. For example, the order management server 30 sets (stores) values in the respective data items of the transaction (the transaction with the transaction ID included in the settlement completion information) as follows. In the data item "transaction type", "2 (transaction completed)" is set. In the data item "transaction end time", the current time is set. In the data item "settlement type", the settlement type of the transaction (the settlement type included in the settlement completion information) is set.

[0068] Step S430: The order management server 30 that determines that it is not possible to accept settlement transmits error information (settlement acceptance not possible) to the settlement terminal 50. Step S431: The settlement terminal 50 that has received the error information (settlement acceptance not possible) displays the error information. For example, the settlement terminal 50 displays the error information in a pop-up manner on the settlement screen (not shown) (displays a small screen showing the error information superimposed on the front of the settlement screen).

[0069] (Operations after reading the store-provided code (until the display of the PIN input screen)) FIG. 11 shows the operations after reading the store-provided code (until the display of the PIN input screen). Step S501: The mobile terminal 20 reads the store-provided code (a two-dimensional code obtained by two-dimensionally coding the table number and the access URL of the table). The store-provided code may be a store-provided code printed on a sheet placed on each table, or a store-provided code printed on a slip (customer copy slip, order confirmation slip). Step S502: The mobile terminal 20 that has read the store-provided code transmits a request to obtain the PIN input screen to the order management server 30. For example, the mobile terminal 20 transmits a request to obtain the PIN input screen including the table number to the order management server 30.

[0070] Step S503: The order management server 30 receives the request to obtain the PIN input screen. Step S510: The order management server 30 determines whether the reading of the store-provided code is valid. For example, if the value of the transaction category of the transaction with the table number (the table number included in the acquisition request of the PIN input screen received from the mobile terminal 20) is "1 (in transaction)", the order management server 30 determines that the reading of the store-provided code is valid. If the value of the transaction category of the transaction with the table number is "2 (transaction completed)", the order management server 30 determines that the reading of the store-provided code is not valid.

[0071] Step S520: The order management server 30 that determines that the reading of the store-provided code is valid transmits the screen information of the PIN input screen to the mobile terminal 20. Step S521: The mobile terminal 20 that has received the screen information of the PIN input screen displays the PIN input screen (Fig. 6(F)).

[0072] Step S530: The order management server 30 that determines that the reading of the store-provided code is not valid transmits error information (invalid reading) to the mobile terminal 20. Step S531: The mobile terminal 20 that has received the error information (invalid reading) displays the error information (invalid reading). For example, the mobile terminal 20 pops up and displays the error information (displays a small screen with the error information superimposed on the front of the reading screen) on the reading screen (not shown) for reading the code.

[0073] (Operations after entering the PIN (until the order reception screen is displayed)) Fig. 12 shows the operations after entering the PIN (until the order reception screen is displayed). It is assumed that the mobile terminal 20 is displaying the PIN input screen (Fig. 6(F)) (step S521 in Fig. 11). Step S601: The mobile terminal 20 accepts the input of the PIN from the customer. Step S602: Based on the customer's operation (operation of the confirmation button on the PIN input screen), the mobile terminal 20 transmits a request to acquire the main screen to the order management server 30. For example, the mobile terminal 20 transmits a request to acquire the main screen including the table number and the PIN to the order management server 30.

[0074] Step S603: The order management server 30 receives a request to obtain the main screen. Step S610: The order management server 30 determines whether it is possible to accept an order. For example, if the value of the transaction classification of the transaction with the table number (the table number included in the request to obtain the main screen received from the mobile terminal 20) is "1 (in transaction)", the order management server 30 determines that it is possible to accept the order. If the value of the transaction classification of the transaction with the table number is "2 (transaction completed)", the order management server 30 determines that it is not possible to accept the order.

[0075] Step S620: The order management server 30 that determines that it is possible to accept an order determines whether a PIN is stored (stored) in the transaction with the table number. Step S630: The order management server 30 that determines that the PIN is not stored registers the received PIN. Specifically, the order management server 30 sets the PIN included in the request to obtain the main screen received from the mobile terminal 20 in the data item "PIN" of the transaction with the table number (the table number included in the request to obtain the main screen received from the mobile terminal 20). That is, the order management server 30 registers the PIN acquired from the mobile terminal 20 in association with the table number acquired from the mobile terminal 20. In other words, the order management server 30 registers the PIN for authenticating the in-store mobile order in the table in the transaction (transaction information).

[0076] Note that in the scenario of the first input (i.e., setting) of the PIN, no PIN is stored in the transaction with the table number. In the scenario of the second and subsequent inputs of the PIN (inputting the already set PIN), a PIN (already set PIN) is stored in the transaction with the table number.

[0077] Step S640: The order management server 30 that has determined that the PIN is stored determines whether the stored PIN matches the received PIN. That is, the order management server 30 determines whether the PIN stored in the data item "PIN" of the transaction for the table number matches the PIN included in the acquisition request of the main screen received from the mobile terminal 20.

[0078] Note that after the customer inputs the PIN on the PIN input screen (Fig. 6(F)), the main screen (Fig. 6(G)) is displayed, and after receiving an order from the customer, the main screen is displayed again (see Fig. 9). Basically, the customer inputs the PIN from the PIN input screen only once (the first time the PIN is set). The situation where the customer inputs the PIN again from the PIN input screen (input for the second time and later) is limited to the situations described below.

[0079] When the customer inputs the PIN again from the PIN input screen, the customer inputs the PIN (set PIN) input (set) for the first time, which is memorized in the head (or recorded on a memo paper, etc.) into the PIN input screen. Therefore, if the customer inputs the PIN, except for cases of mistakes (memory mistakes, input mistakes, etc.), the order management server 30 determines that the PINs match. On the other hand, when a person other than the customer (a non-related person who is not a family member, acquaintance, colleague, etc. sitting together) reads the store-provided code of the table and inputs the PIN, except for cases where the PIN has leaked or coincidentally matches, the order management server 30 determines that the PINs do not match.

[0080] The situation where the customer inputs the PIN again from the PIN input screen (inputs after the second time), for example, is when the customer closes (drops) the browser. The mobile terminal 20 temporarily stores (caches) the table number and the PIN, and accesses (browses) each screen using the temporarily stored information. However, when the browser is closed (dropped), the temporarily stored information becomes unavailable (for example, the temporarily stored information is erased and the temporarily stored information cannot be referenced), and it becomes impossible to return to (display) the main screen (Fig. 6(G)) or the order reception screen (Fig. 6(H)). That is, if the customer closes the browser, subsequent orders become impossible.

[0081] Note that even if the browser is closed (even if the temporarily stored information is erased, etc.), the order management server 30 continues to hold the transaction information (Fig. 5) including the table number and the PIN. Therefore, if the customer reads the store-provided code again and inputs the correct PIN (the same PIN as the set PIN) on the PIN input screen displayed after reading the store-provided code, the transaction can be resumed (continued) from immediately before.

[0082] On the other hand, if the customer forgets the correct PIN and inputs an incorrect PIN (a PIN different from the set PIN) on the PIN input screen displayed after reading the store-provided code, the transaction is not resumed because the PIN is different (Fig. 12). Note that since a new transaction (transaction information) is generated based on the operation of the store clerk order terminal 10 (Fig. 7), even if the customer inputs an incorrect PIN on the PIN input screen displayed after reading the store-provided code, a new transaction is not generated.

[0083] As a method for dealing with the case of forgetting the correct PIN, for example, there are the following coping methods 1, coping method 2, and coping method 3. · Coping method 1 (reset of PIN) On a maintenance screen (not shown) displayed on a terminal operated by a store clerk (for example, the store clerk order terminal 10, other terminals), an operation to request reset (clear, erase, delete) of the password for the transaction information of the table (for example, an operation to specify the table number, an operation to execute the reset of the password, etc.) is accepted. Based on this operation, password reset request information is sent from the terminal operated by the store clerk to the order management server 30. The order management server 30 that has received the reset request information resets the corresponding password (the password for the transaction information of the table instructed by the store clerk). The order management server 30 resets the password according to the instruction, but does nothing with other information (for example, order information, etc.) other than the password (because other information is retained as it is). Therefore, the customer can restart the transaction by re-reading the store-provided code for the table and entering the password (which may be the same as the previous password or different from the previous password). That is, the store clerk intervenes and deals with it by resetting the password (by the password reset function).

[0084] ·Countermeasure method 2 (notification of password) On a maintenance screen (not shown) displayed on a terminal operated by a store clerk (for example, the store clerk order terminal 10, other terminals), an operation to request inquiry of the password for the transaction information of the table (for example, an operation to specify the table number of the corresponding table, an operation to execute the inquiry of the password, etc.) is accepted. Based on this operation, password inquiry request information is sent from the terminal operated by the store clerk to the order management server 30. The order management server 30 that has received the inquiry request information notifies (sends) the corresponding password (the password for the transaction information of the table instructed by the store clerk) to the terminal operated by the store clerk or notifies (sends) it to the kitchen printer. The store clerk conveys the password notified and displayed on the terminal operated by the store clerk or the password notified and printed by the kitchen printer to the customer. The customer can restart the transaction by re-reading the store-provided code for the table and entering the password (which may be the same as the previous password or different from the previous password). That is, the store clerk intervenes and deals with it by inquiring about the password (by the password inquiry function).

[0085] ·Countermeasure method 3 (reading of shared code) When another customer's mobile terminal 20 has read the shared code (when another customer's mobile terminal 20 can display an order reception screen (Fig. 6(H))), since the other customer's mobile terminal 20 can also display the shared code, if the other customer's mobile terminal 20 reads the shared code, although the PIN number is forgotten (in other words, re-entry of the PIN number on the PIN number input screen is not required), the order reception screen (Fig. 6(H)) can be displayed again (that is, the transaction is restarted).

[0086] Step S650: The order management server 30 that has registered the PIN number or the order management server 30 that has determined that the PIN numbers match transmits the screen information of the main screen to the mobile terminal 20 together with the transaction ID of the transaction (the transaction with the table number included in the order reception screen acquisition request received from the store clerk order terminal 10). Step S651: The mobile terminal 20 that has received the screen information of the main screen displays the main screen (Fig. 6(G)). Step S652: Based on the customer's operation (operation of the order button on the main screen), the mobile terminal 20 transmits a request to acquire the order reception screen to the order management server 30. For example, the mobile terminal 20 transmits a request to acquire the order reception screen including the order type (value is "2 (customer order)") and the transaction ID to the order management server 30. Step S653: The order management server 30 receives the screen information of the order reception screen. Step S654: The order management server 30 transmits the screen information of the order reception screen to the mobile terminal 20. Step S655: The mobile terminal 20 that has received the screen information of the order reception screen displays the order reception screen (Fig. 6(H)).

[0087] Step S660: The order management server 30 that has determined that the order cannot be received transmits error information (order reception impossible) to the mobile terminal 20. Step S661: The mobile terminal 20 that has received the error information (order reception not possible) displays the error information (order reception not possible). For example, the mobile terminal 20 pop-up displays the error information (a small screen on which the error information is displayed is superimposed on the front of the main screen) on the PIN input screen (Fig. 6(F)).

[0088] Step S670: The order management server 30 that has determined that the PIN does not match transmits the error information (PIN does not match) to the mobile terminal 20. Step S671: The mobile terminal 20 that has received the error information (PIN does not match) displays the error information (PIN does not match). For example, the mobile terminal 20 pop-up displays the error information (a small screen on which the error information is displayed is superimposed on the front of the main screen) on the PIN input screen (Fig. 6(F)).

[0089] (Operations after reading the shared code (until the order reception screen is displayed)) Fig. 13 shows the operations after reading the shared code (until the order reception screen is displayed). Step S701: The mobile terminal 20 reads the shared code. The shared code may be a shared code displayed on the shared screen (Fig. 6(I)) by another mobile terminal 20. Step S702: The mobile terminal 20 that has read the shared code transmits a request to acquire the order reception screen to the order management server 30. For example, the mobile terminal 20 transmits a request to acquire the order reception screen including the order type (value is "2 (customer order)") and the transaction ID to the order management server 30.

[0090] Step S703: The order management server 30 receives the request to acquire the order reception screen. Step S710: The order management server 30 determines whether it can accept an order. For example, if the value of the transaction category of the transaction with the transaction ID (the transaction ID included in the acquisition request of the order reception screen received from the mobile terminal 20) is "1 (in transaction)", the order management server 30 determines that it can accept the order. If the value of the transaction category of the transaction with the transaction ID is "2 (transaction completed)", the order management server 30 determines that it cannot accept the order.

[0091] Step S754: The order management server 30 that determines that it can accept the order transmits the screen information of the order reception screen to the mobile terminal 20. Step S755: The mobile terminal 20 that has received the screen information of the order reception screen displays the order reception screen (Fig. 6(H)).

[0092] Step S760: The order management server 30 that determines that it cannot accept the order transmits error information (invalid reading) to the mobile terminal 20. Step S761: The mobile terminal 20 that has received the error information (invalid reading) displays the error information (invalid reading). For example, in a reading screen (not shown) for reading the code, the error information is pop-up displayed (a small screen displaying the error information is superimposed on the front of the reading screen for display).

[0093] (Operations when the customer places an order (after the order reception screen is displayed)) The operations of the mobile terminal 20 for placing an order after the display of the order reception screen (Fig. 6(H)) are the same as the operations of the store clerk's order terminal 10 for placing an order after the display of the order reception screen (Fig. 6(D)) (Fig. 9). Again, using Fig. 9, the operations when the customer places an order (after the order reception screen is displayed) will be described. It is assumed that the mobile terminal 20 is displaying the order reception screen (Fig. 6(H)) (Step S655 in Fig. 12, Step S755 in Fig. 13). Step S301: The mobile terminal 20 accepts an order input from the customer. Step S302: The mobile terminal 20 displays an order details confirmation screen (a screen similar to the order details confirmation screen in Fig. 6(E)) based on the customer's operation (operation of the confirmation button on the order reception screen). Note that the mobile terminal 20 may send a request to obtain the order details confirmation screen to the order management server 30 based on the customer's operation, receive the screen information of the order details confirmation screen from the order management server 30, and then display the order details confirmation screen. Alternatively, the mobile terminal 20 may receive from the order management server 30 not only the screen information of the order reception screen but also the screen information of the next screen, which is the order details confirmation screen, and then display the order details confirmation screen based on the customer's operation. Step S303: The mobile terminal 20 sends the order information to the order management server 30 based on the customer's operation (operation of the confirmation button on the order details reception screen). For example, the mobile terminal 20 sends order information including the order type (value is "2 (customer order)"), the transaction ID, and the order details (ordered products, prices, quantities, etc.) confirmed on the order details confirmation screen to the order management server 30.

[0094] Step S304: The order management server 30 receives the order information. Step S310: The order management server 30 determines whether it is possible to accept the order.

[0095] Step S320: The order management server 30 that determines that it is possible to accept the order registers the order.

[0096] Step S321: The order management server 30 that has registered the order information sends order reception completion information to the mobile terminal 20. Note that the order management server 30 may send the screen information of the main screen to the mobile terminal 20 instead of or in addition to the order reception completion information. Step S322: Subsequently, the order management server 30 sends the slip data to the kitchen printer 40. For example, the order management server 30 sends slip data including the transaction ID, the order amount, and the ordered products to the kitchen printer 40. The order management server 30 may send slip data including the order type (value is "2 (customer order)") to the kitchen printer 40.

[0097] Step S323: The mobile terminal 20 that has received the order acceptance completion information (or, instead of or in addition to the order acceptance completion information, the screen information of the main screen) displays the main screen (Fig. 6(G)). That is, since the order has been normally accepted, the screen of the mobile terminal 20 transitions from the order content confirmation screen to the main screen (Fig. 6(G)).

[0098] Step S324: The kitchen printer 40 receives the slip data. Step S325: The kitchen printer 40 issues slips (cooking instruction slips, customer copies) based on the slip data. The kitchen printer 40 may issue a customer copy with a settlement code printed thereon. Further, the kitchen printer 40 may issue a customer copy with a store-provided code printed thereon instead of or in addition to the settlement code.

[0099] Step S330: The order management server 30 that has determined that an order cannot be accepted transmits error information (order acceptance not possible) to the mobile terminal 20. Step S331: The mobile terminal 20 that has received the error information (order acceptance not possible) displays the error information (order acceptance not possible).

[0100] Note that when a store clerk places an order (in the case of an order by the store clerk terminal 10), it is necessary to input the table number (Fig. 8 → Fig. 9). When a customer (including "other customers" who have read the shared code) places an order (in the case of an order by the mobile terminal 20), it is not necessary to input the table number (Fig. 11 → Fig. 12 → Fig. 9, or Fig. 13 → Fig. 9).

[0101] Note that when a customer (excluding "other customers" who have read the shared code) places an order (in the case of an order by the mobile terminal 20), it is necessary to input the PIN (Fig. 11 → Fig. 12 → Fig. 9). When an "other customer" who has read the shared code places an order (in the case of an order by the mobile terminal 20), it is not necessary to input the PIN (Fig. 13 → Fig. 9). When a store clerk places an order (in the case of an order by the store clerk terminal 10), it is not necessary to input the PIN (Fig. 8 → Fig. 9).

[0102] Although the system 1 according to the embodiment has been described above, according to the system 1, for example, it is possible to more preferably receive orders as follows (1) to (6). (1) If the customer reads the store-provided code placed on the seated table using his / her mobile terminal 20 and sets (inputs) a password, the order reception screen (FIG. 6(H)) can be displayed on the mobile terminal 20 (steps S501 to S521 in FIG. 11 → steps S601 to S630 to S655 in FIG. 12). Therefore, the customer can order products using his / her mobile terminal 20 (FIG. 9). (2) The password can be set immediately after being guided to the table. Specifically, if there is transaction information with the transaction classification “1 (in transaction)”, a password input screen (FIG. 6(F)) is displayed on the mobile terminal 20 (steps S510 (YES) to S521 in FIG. 11). Therefore, the customer can also execute the first order using the mobile terminal 20. That is, for example, without waiting for the slip (customer copy slip) received at the time of serving the products of the first order carried out through a store clerk, the customer can order using the mobile terminal 20 from the beginning. Also, since the store-provided code is installed on each table so that anyone can read it, it is possible to play a prank such as reading the store-provided code installed on an unoccupied table and placing an order for products. However, since no transaction information is generated until the customer receives the table guidance from the store clerk, even if the store-provided code on the table is read and an order operation is performed before the generation of the transaction information, the order will not be accepted, and unnecessary cooking and serving can be prevented in advance. (3) After the display of the order reception screen, until the settlement is completed, there is no need to read the store-provided code, nor is it necessary to input the set password (correct password), and orders can be placed any number of times from the displayed order reception screen (step S655 in FIG. 12 → steps S301 and subsequent steps in FIG. 9). Therefore, once the customer sets a password, he / she can easily order products any number of times using his / her mobile terminal 20 thereafter. (4) When the store-provided code is read, a request for entering a PIN is made (steps S501 to S521 in FIG. 11). Also, when the store-provided code is read after the PIN is set (when the PIN is registered in the transaction information), if the entered PIN matches the set PIN, an order acceptance screen is displayed (steps S601 to step S640 (YES) to S655 in FIG. 12). Therefore, even if the customer closes the order acceptance screen, if the customer reads the store-provided code again and enters the correct PIN, orders can be placed thereafter. Also, even if a store-provided code of the table where the customer is seated is read by someone else (a non-related person who is not a family member, acquaintance, colleague, etc. sitting at the same table), since the PIN is unknown, unauthorized orders (irregular orders) by others can be excluded. Note that when the mobile terminal 20 of a family member, acquaintance, colleague, etc. sitting at the same table reads the store-provided code, if the PIN is communicated, the order acceptance screen can be displayed on the mobile terminal 20 of the family member, acquaintance, colleague, etc. sitting at the same table. Therefore, a family member, acquaintance, colleague, etc. sitting at the same table can place an order using their own mobile terminal 20. (5) The mobile terminal 20 can display a sharing code (the sharing screen in FIG. 6(I) can be displayed from the sharing button on the main screen in FIG. 6(G) or the sharing button on the order acceptance screen in FIG. 6(H)). Therefore, if the sharing code is read by the mobile terminals 20 of family members, acquaintances, colleagues, etc. sitting at the same table, the family members, acquaintances, colleagues, etc. sitting at the same table can easily place an order using their own mobile terminals 20 (without the need to enter a PIN). (6) As described above, in the mode of placing an order using the customer's own mobile terminal 20, the customer can place an order using their familiar own mobile terminal 20. Also, on the store side, since there is no need to prepare a terminal for each table, it is cost-effective.

[0103] (Modifications, etc.) As described above for each embodiment, the configuration of the device, the configuration of the data, the processing flow, the display and output modes, etc. can be appropriately changed as shown in, for example, (1) to (16) below. Also, (1) to (16) below can be appropriately combined with each other.

[0104] (1) In the above embodiment, an order confirmation slip button is provided on the home screen (FIG. 6(A)) of the store clerk order terminal 10, but an order confirmation slip button may also be provided on the main screen (FIG. 6(G)) of the mobile terminal 20. That is, in addition to the store clerk, the customer may also be able to request the issuance of an order confirmation slip.

[0105] Note that when there is an operation of the order confirmation button by the store clerk on the store clerk order terminal 10, the store clerk may be requested to input the table number. When the table number is input, a request for issuing an order confirmation slip including the table number may be transmitted to the kitchen printer 40 via the order management server 30, or may be transmitted to the kitchen printer 40 without going through the order management server 30 (via the wireless router 60). Also, when there is an operation of the order confirmation button by the customer on the mobile terminal 20, a request for issuing an order confirmation slip including the table number may be transmitted to the kitchen printer 40 via the order management server 30, or may be transmitted to the kitchen printer 40 without going through the order management server 30. When the mobile terminal 20 transmits a request for issuing an order confirmation slip to the kitchen printer 40, it may notify the store clerk that the order confirmation slip has been issued (for example, a notice of issuing an order confirmation slip including the table number may be transmitted to the store clerk order terminal 10 via the order management server 30, or may be transmitted to the store clerk order terminal 10 without going through the order management server 30.

[0106] (2) In the above embodiment, an example where the mobile terminal 20 transitions to the order reception screen (FIG. 6(H)) as the next screen when reading the shared code (symbol A) on the shared screen (FIG. 6(I)) has been described (FIG. 13), but it may transition to the main screen (FIG. 6(G)) as the next screen. That is, in step S702 of FIG. 13, the mobile terminal 20 may transmit a request for acquiring the main screen to the order management server 30, and in step S754 of FIG. 13, the order management server 30 may transmit the screen information of the main screen to the mobile terminal 20.

[0107] In the case of the mode of transitioning to the order reception screen after reading the shared code, since the main screen is displayed after actually placing an order on the order reception screen (Figure 13 → Figure 9), other customers (family members, acquaintances, colleagues, etc.) who are sitting together can, if they read the shared code on the mobile terminal 20 and place an order from the order reception screen displayed after reading, operate the payment button on the main screen displayed after the order to display the settlement screen (Figure 6(J)). On the other hand, in the case of the mode of transitioning to the main screen after reading the shared code, since the main screen is displayed after reading the shared code, other customers who are sitting together can, if they read the shared code on the mobile terminal 20, operate the payment button on the main screen displayed after reading to display the settlement screen. That is, in the case of the mode of transitioning to the main screen after reading the shared code, other customers who are sitting together can display the settlement code (symbol B) without placing an order.

[0108] (3) In the above embodiment, the shared screen (Figure 6(I)) and the settlement screen (Figure 6(I)) are displayed as separate screens, but they may be combined into one screen.

[0109] (4) In the above embodiment, an example of providing a shared screen (Figure 6(I)) and a settlement screen (Figure 6(I)) separately from the main screen (Figure 6(G)) has been described, but the shared code (settlement code) may be displayed on the main screen. This can reduce the trouble of operating the share button and the payment button.

[0110] (5) In the above embodiment, the main screen (Figure 6(G)) has been described as an example of the screen of the mobile terminal 20, but the main screen may not be provided. For example, when an operation of the confirmation button is performed in a state where the PIN number is input on the PIN number input screen (Figure 6(F)), the mobile terminal 20 may transition to the order reception screen (the order reception screen with the payment button further arranged). That is, the main screen (Figure 6(G)) and the order reception screen (Figure 6(F)) may be combined into one screen.

[0111] (6) When the order management server 30 transmits the screen information of the password input screen to the mobile terminal 20 (step S520 in FIG. 11), it may transmit the screen information together with the transaction ID of the transaction (the transaction of the table number included in the acquisition request of the password input screen received from the mobile terminal 20). In this case, the mobile terminal 20 may display the transaction ID on the password input screen (FIG. 6(F)). Further, in this case, after the input of the password (step S602 in FIG. 12), the mobile terminal 20 may transmit a request for acquiring the main screen including the transaction ID (a request for acquiring the main screen including the transaction ID and the password) to the order management server 30 instead of the table number.

[0112] (7) In the above embodiment, the shared code has been described as a two-dimensional code in which information that can directly or indirectly identify a transaction (at least one of the transaction ID and the table number) and the access URL are two-dimensionally coded. However, the shared code may be a two-dimensional code in which, in addition to the information that can directly or indirectly identify a transaction, a password (set password) is two-dimensionally coded. That is, the password may be obtained from the shared code.

[0113] In the example shown in FIG. 13, the order management server 30 transmits the screen information of the order reception screen to the mobile terminal 20 if it determines that order reception is possible (step S710 (YES)). However, in the mode in which the two-dimensional code in which, in addition to the information that can directly or indirectly identify a transaction, a password is two-dimensionally coded is used as the shared code, when the order management server 30 determines that order reception is possible (step S710 (YES)), it further determines whether the password stored as the password of the transaction (or the table) matches the received password (the password obtained from the shared code). If it determines that they match, it may transmit the screen information of the order reception screen to the mobile terminal 20.

[0114] In addition, in the above embodiment, as a countermeasure when forgetting the correct PIN, Countermeasure 3 (reading of the shared code) was described. However, if the PIN can be obtained from the shared code, the PIN can also be obtained from the shared code displayed on the mobile terminal 20 of another customer. The PIN obtained from the shared code displayed on the mobile terminal 20 of another customer may be displayed.

[0115] (8) In the above embodiment, an example was described in which the PIN input on the PIN input screen (FIG. 6(F)) is used to determine whether to display the main screen (FIG. 6(G)) (steps S640 to S651 in FIG. 12). However, the PIN input on the PIN input screen (FIG. 6(F)) may be used to determine whether to display the order reception screen (FIG. 6(H)). Further, it may be used to determine whether the order reception server 30 accepts order information (determines whether to register an order). In addition, according to these modes, when the browser is closed (when the temporarily stored information cannot be used), the order reception screen cannot be displayed, or the order reception server 30 cannot accept order information. However, as described above, if the correct PIN is input on the PIN input screen, etc., the transaction can be resumed.

[0116] (9) In the above embodiment, an example was described in which the mobile terminal 20 displays the shared code (FIG. 6(I)). However, the shared code may be printed on a slip (customer copy slip, order confirmation slip). That is, in the above embodiment, it was explained that the kitchen printer 40 (or the settlement terminal 50) may print a settlement code or a store-provided code on a slip (customer copy slip, order confirmation slip). However, the shared code may be printed instead of the store-provided code.

[0117] More specifically, when the PIN is not stored in the transaction information, the kitchen printer 40 (or the payment terminal 50) may issue a slip printed with a settlement code, or may issue a slip printed with a store-provided code instead of or in addition to the settlement code. When the PIN is stored in the transaction information, the kitchen printer 40 (or the payment terminal 50) may issue a slip printed with a settlement code, or may issue a slip printed with a store-provided code instead of or in addition to the settlement code, or may issue a slip printed with a shared code instead of or in addition to the settlement code. That is, the kitchen printer 40 (or the payment terminal 50) may print the store-provided code (similarly for the settlement code) whether or not the PIN is stored in the transaction information, but may print the shared code only when the PIN is stored in the transaction information.

[0118] That is, the mobile terminal 20 may display an order reception screen based on an operation of an order button on the main screen, or may display an order reception screen based on reading a shared code displayed by another mobile terminal 20, or may display an order reception screen based on reading a shared code printed on a slip (customer copy slip, order confirmation slip).

[0119] (10) In the above embodiment, the PIN, which is the authentication information for in-store mobile orders, has been described as a four-digit number, but it may be less than four digits or more than four digits. The authentication information does not have to be a number. For example, it may be an alphabet, a symbol, or the like. The authentication information may be a combination of numbers, alphabets, and symbols. Also, a character such as an animal may be used as the authentication information.

[0120] When using alphabets, symbols, etc. as authentication information, similar to displaying the numeric keypad when using numbers as authentication information, the mobile terminal 20 may display a keyboard (alphabet buttons, symbol buttons). Also, when using characters as authentication information, character buttons obtained by schematizing the characters may be displayed, or character buttons may be displayed on a character selection screen (not shown) where a plurality of character buttons are arranged. Note that when using characters as authentication information, a character number or the like may be assigned to each character (character button), and the character number may be stored in the transaction information (FIG. 5).

[0121] (11) In the above embodiment, an example in which the order management server 30 manages (stores) transaction information as one record (file) has been described (FIG. 5), but it may be managed separately in two or more records. In the example shown in FIG. 5, there is a data item "PIN number" in the transaction information, but the data item "PIN number" may not be present in the transaction information. Separately from the transaction information (transaction information without the data item "PIN number"), a record consisting of the data item "transaction identification information" and the data item "PIN number", or a record consisting of the data item "table number" and the data item "PIN number" may be managed. That is, the PIN number (authentication information) only needs to be managed in association with the transaction and does not necessarily have to be stored in the transaction information.

[0122] (12) In the above embodiment, the terminal used for in-store mobile order has been described as the customer's own terminal, but it may be a lending terminal lent by the store ST to the customers who visit the store. That is, the mobile terminal 20 may be the customer's own terminal or a lending terminal of the store ST.

[0123] Note that after Customer A reads the store sharing code using their own mobile terminal 20, the sharing code may be displayed on the mobile terminal 20 and presented to Customer B (the co - seated customer of Customer A). Customer B may read the sharing code presented by Customer A using the mobile terminal 20 which is the lending terminal. Or, after Customer A reads the store sharing code using the mobile terminal 20 which is the lending terminal, the sharing code may be displayed on the mobile terminal 20 and presented to Customer B. Customer B may read the sharing code presented by Customer A using their own mobile terminal 20. That is, in the in - store mobile order of one transaction, orders made by the customer's own terminal, i.e., the mobile terminal 20, and orders made by the lending terminal, i.e., the mobile terminal 20, may be mixed.

[0124] Orders made by the customer's own terminal and orders made by the lending terminal may be managed separately. For example, the value "1" of the order type may be for store staff orders (orders made by the store staff order terminal 10), the value "2" of the order type may be for customer orders (orders made by the customer's own mobile terminal 20), and the value "2" of the order type may also be for customer orders (orders made by the mobile terminal 20 which is the lending terminal).

[0125] (13) In the above - described embodiment, an example of issuing a slip (order confirmation slip) printed with the ordered items and the settlement amount as the order history has been described, but the order history may be displayed on the screen. FIG. 14 is a schematic diagram of each screen displayed by the mobile terminal 20.

[0126] For example, an order history button may be displayed on the main screen of FIG. 6(G). Based on the operation of the order history button, the mobile terminal 20 may display an order history screen as shown in FIG. 14(D), for example. The order history screen of FIG. 14(D) will be described later.

[0127] Instead of the main screen of FIG. 6(G) in the screen transition of FIGS. 6(F) - 6(J), the mobile terminal 20 may display a main screen as shown in FIG. 14(B), and based on the operation of the order history button BT21, may display an order history screen as shown in FIG. 14(D), for example. The main screen of FIG. 14(B) and the order history screen of FIG. 14(D) will be described later.

[0128] In the above-described embodiment, an example has been described in which the mobile terminal 20 displays a PIN input screen (FIG. 6(F)) after reading the store-provided code. However, the mobile terminal 20 may display a guidance screen after reading the store-provided code.

[0129] FIG. 14(A) is a schematic diagram of the guidance screen. The guidance screen displays guidance information regarding in-store mobile orders. As shown in FIG. 14(A), messages MS10 to MS12 are displayed on the guidance screen. Further, an "x" button BT15 and a close button BT16 are provided on the guidance screen.

[0130] Message MS10 is a message for guiding the setting of a passcode (PIN). Message MS11 also overlaps with message MS10, but first, it is a message for instructing the representative customer to set a passcode. Message MS12 is a message for instructing other customers in the same group to read the two-dimensional code (shared code, settlement code) displayed on the screen of the representative's mobile terminal 20. The "x" button BT15 and the close button BT16 are buttons to be operated after finishing checking the content of the guidance screen.

[0131] FIG. 14(B) is a schematic diagram of the main screen (a main screen different from the main screen in FIG. 6(G)). The mobile terminal 20 displays the main screen in FIG. 14(B) based on, for example, an operation of the close button BT16 (or an operation of the "x" button BT15) of the guidance screen (FIG. 14(A)). As shown in FIG. 14(B), an order button BT20 and an order history button BT21 are provided on the main screen. Further, a shared / settlement code (reference numeral C in the same figure) and link information LJ22 are displayed on the main screen.

[0132] The order button BT20 is a button to be operated when placing an order for a product. The order history button BT21 is a button to be operated when displaying the order history. The shared / settlement code is the same shared code as the settlement code. The link information LJ22 is link information to be operated when checking the guidance.

[0133] Figure 14(C) is a schematic diagram of a small screen (password input small screen) SG30 displayed (popped up) in front of the main screen of Figure 14(B). The mobile terminal 20 displays (pops up) the small screen SG30 in front of the main screen as shown in Figure 14(C) based on, for example, an operation of the order history button BT21 on the main screen (Figure 14(B)). As shown in Figure 14(C), messages MS31 and MS32 are displayed on the small screen SG30. In addition, an input display area AR33 is provided on the small screen SG30. Also, an "x" button BT35 and an OK button BT36 are provided on the small screen SG30.

[0134] The message MS31 is a message instructing the input of a password. The message MS32 is a message instructing to call a store clerk if the password is forgotten. The input display area AR33 is an area where the password is input and displayed. The "x" button BT35 is a button to be operated when stopping the input of the password. The OK button BT36 is a button to be operated when finalizing the password displayed in the input display area AR33.

[0135] Figure 14(D) is a schematic diagram of the order history screen. The mobile terminal 20 displays the order history screen of Figure 14(D) based on, for example, a password being input in the input display area AR33 of the small screen SG30 (Figure 14(C)) and the OK button BT36 being operated. As shown in Figure 14(D), a number display area AR40, a total display area AR41, and an order display area AR42 are provided on the order history screen. Also, a close button BT46 is provided on the order history screen. The mobile terminal 20 displays the main screen (Figure 14(C)) based on an operation of the button BT46.

[0136] The number display area AR40 is an area for displaying the number of connected people (the number of mobile terminals 20 that have accessed the order management server 30) and the number of guided people. The total display area AR41 is an area for displaying the total amount of ordered products (excluding canceled products). In addition to the total amount of ordered products, the total number of ordered products may be displayed in the total display area AR41.

[0137] The order display area AR42 is an area for displaying each order (order 1, order 2,...). One or more products are displayed as ordered products in each order display area AR42.

[0138] A status mark (icon, label) MS43 indicating the status is attached to each ordered product. In the example shown in FIG. 14(D), the ordered product "omakase" at the order time "19:12" is attached with a status mark MS43 of "not provided". That is, it is indicated that the ordered product "omakase" is in the state of not being provided (not served). The ordered product "sake" at the order time "19:23" is attached with a status mark MS43 of "provided". That is, it is indicated that the ordered product "sake" is in the state of being provided (served). The same applies to the ordered product "beer" at the order time "19:15". The ordered product "salmon" at the order time "19:23" is attached with a status mark MS43 of "canceled". That is, it is indicated that the ordered product "salmon" is in the state where the order has been canceled (for example, the cancel flag is set for the product "salmon" in the transaction information).

[0139] For unprovided ordered items, a cancel button BT44 is provided. For example, in the example shown in FIG. 14(D), the ordered item "omakase" at the order time "19:12" is unprovided, so a cancel button BT44 is provided in association with the ordered item "omakase". When the cancel button BT44 is operated, the ordered item "omakase" is cancelled (for example, a cancel flag is set for the item "omakase" in the transaction information).

[0140] In the order history screen of FIG. 14(D), new orders are displayed from top to bottom (the newer ones are displayed higher), but orders including unprovided items are displayed higher. For example, in the order history screen of FIG. 14(D), the order at the order time "19:23" is the newest order, but since "omakase" included in the order at the order time "19:12" is unprovided, the order at the order time "19:12" is displayed at the topmost position.

[0141] Note that when the order history button BT21 on the main screen (FIG. 14(B)) of the mobile terminal 20 is operated, the small screen SG30 is displayed, and when the order button BT20 on the main screen (FIG. 14(B)) is operated, the small screen SG30 is also displayed. That is, it may be set as a control that when the order button BT20 on the main screen (FIG. 14(B)) is operated → the small screen SG30 is pop-up displayed → after the password is input, the confirm button BT36 is operated → it transitions to the order reception screen (FIG. 6(H)), and no password is required during the transition from the store-provided code reading → the guidance screen (FIG. 14(A)) → the main screen (FIG. 14(B)). It may be set so that the password is required only at the first operation of the order button BT20 and the order history button BT21, and not at the second and subsequent operations. Also, the mobile terminal 20 displays the guidance screen (FIG. 14(A)) based on the operation of the link information LJ22 on the main screen (FIG. 14(B)).

[0142] Alternatively, instead of or in addition to the main screen (Figs. 14(B), 6(G)), an order history button may be displayed (arranged) on another screen (e.g., an order reception screen (Fig. 6(H)), a sharing screen (Fig. 6(I)), a settlement screen (Fig. 6(J))), and control may be provided to transition from the other screen to the order history screen. On a terminal operated by a store clerk (e.g., the store clerk order terminal 10, another terminal), the order history screen for each table may be displayed by designating the table number. Instead of or in addition to the order history screen (Fig. 14(D)), a number display area AR40 may be provided on another screen (e.g., the main screen (Figs. 14(B), Fig. 6(G)), the sharing screen (Fig. 6(I)), the settlement screen (Fig. 6(J))), so that the number of connected people and the number of guided people can be confirmed on the other screen. On a terminal operated by a store clerk, the number of connected people and the number of guided people for each table may be displayed by designating the table number.

[0143] (15) In the above embodiment, the store clerk order terminal 10 requests screen information from the order management server 30 and displays each screen (Fig. 6) (that is, the store clerk order terminal 10 is a so-called client specialized for an input / output interface or the like, and an example of displaying each screen by a browsing function) has been described. However, the store clerk order terminal 10 may generate screen information by itself according to the operation of the operator or the like and display each screen. The same applies to the mobile terminal 20.

[0144] (16) Some or all of the functions (input / output, storage, processing (including judgment)) in each device (e.g., the store clerk order terminal 10, the mobile terminal 20, the order management server 30, the settlement terminal 50, etc.) may be realized in another device different from the device described as the execution subject of the function.

[0145] <Summary of the Embodiment> [Technical Field] The present invention relates to a system. [Background Art] A system is known in which a staff member (store clerk) of a restaurant accepts an order from a customer using an order terminal (see, for example, Patent Document 1). [Prior Art Documents] [Patent Documents] [Patent Document 1] Japanese Patent Application Laid-Open No. 2018-128826 [Summary of the Invention] [Problems to be Solved by the Invention] However, there is room for improvement regarding the acceptance of orders in the store. The present invention has been made in view of such circumstances, and an object thereof is to provide a technique for more suitably accepting orders. [Means for Solving the Problems]

[0146] (1) One aspect for solving the above-described problems is a system capable of accepting in-store customer orders, which are orders using the customer's own mobile terminal (for example, mobile terminal 20) in the store, the system comprising: a reading means (for example, camera 24 or a code recognition function by control unit 21) for reading table identification information (for example, a store-provided code) for identifying a table in the store; an authentication information acquisition means for acquiring authentication information (for example, a password) for authenticating the in-store customer order; and an authentication information registration means (see, for example, step S630 in FIG. 12) for registering the authentication information as the authentication information for authenticating the in-store customer order for the table identified by the table identification information when the table identification information is read by the reading means and the authentication information is acquired by the authentication information acquisition means. The system is characterized by comprising the above. According to the system of (1), orders can be more suitably accepted.

[0147] (2) It is provided with order receiving means for receiving the in-store customer orders (for example, the part where the mobile terminal 20 displays the order receiving screen in FIG. 6(H)). The order receiving means reads the table identification information by the reading means, acquires the authentication information by the authentication information acquisition means, and when the authentication information acquired by the authentication information acquisition means matches the authentication information registered as the authentication information for authenticating the in-store customer orders of the table identified by the table identification information read by the reading means, it receives the in-store customer orders of that table (for example, displays the order receiving screen in step S652 after step S650 in FIG. 12). It is the system according to (1), characterized in that. (2) According to the system of (2), orders can be received more preferably.

[0148] (3) When the authentication information for authenticating the in-store customer orders of one table is registered by the authentication information registration means (for example, when a password is stored in the transaction information), it is provided with display means for displaying code information (for example, a shared code) that enables receiving the in-store customer orders of that table (see FIG. 6(I) for example). The order receiving means receives the in-store customer orders of that table when the code information enabling the reception of the in-store customer orders of one table displayed by the display means is read by the reading means (for example, displays the order receiving screen in step S755 after step S701 in FIG. 13). It is the system according to (2), characterized in that. (3) According to the system of (3), orders can be received more preferably.

[0149] (4) It is provided with settlement means, and the settlement means is capable of settlement based on the code information displayed by the display means (for example, the settlement code in FIG. 6(J) is the same as the shared code in FIG. 6(I) and is capable of settlement in step S422 after step S401 in FIG. 10) (in other words, it is possible to place an order using the settlement code). It is the system according to (3), characterized in that. (4) According to the system, orders can be received more preferably.

[0150] (5) It includes a history display means (FIG. 14(D)) that displays the order history in the table (order display area AR42) and accepts order cancellation (cancellation button BT44). The history display means displays the order history (FIG. 14(C) → FIG. 14(D)) by acquiring the authentication information, and is the system according to (1) or (2). (5) According to the system, the order history can be preferably confirmed and cancellation can be accepted.

[0151] Note that a program for realizing the functions of each of the devices described above (for example, the store clerk order terminal 10, the mobile terminal 20, the order management server 30, the payment terminal 50, etc.) may be recorded on a computer-readable recording medium, and the program recorded on this recording medium may be read into a computer system and executed to perform the processing of each of the above devices. Here, "reading the program recorded on the recording medium into a computer system and executing it" includes installing the program in the computer system. The "computer system" as used here shall include hardware such as an OS and peripheral devices. Also, the "computer system" may include a plurality of computer devices connected via a network including a communication line such as the Internet, WAN, LAN, or dedicated line. Further, the "computer-readable recording medium" refers to a portable medium such as a flexible disk, a magneto-optical disk, a ROM, a CD-ROM, etc., and a storage device such as a hard disk built into a computer system. Thus, the recording medium storing the program may be a non-transitory recording medium such as a CD-ROM. Also, the recording medium includes an internal or external recording medium provided so as to be accessible from a distribution server for distributing the program. The code of the program stored in the recording medium of the distribution server may be different from the code of the program in a form executable by the terminal device. That is, as long as it can be downloaded from the distribution server and installed in a form executable by the terminal device, the form stored in the distribution server does not matter. Note that the program may be divided into a plurality of parts, downloaded at different timings, and then combined on the terminal device, or the distribution servers for distributing each of the divided programs may be different. Furthermore, the "computer-readable recording medium" shall also include a volatile memory (RAM) inside a computer system serving as a server or a client when the program is transmitted via a network, which holds the program for a certain period of time. Also, the above program may be for realizing a part of the functions described above.Furthermore, it may be a so-called differential file (differential program) that can be realized in combination with a program already recorded in a computer system for the above-described functions.

Explanation of Signs

[0152] 1…System 10…Clerk Order Terminal 20…Mobile Terminal 30…Order Management Server 40…Kitchen Printer 50…Payment Terminal 60…Wireless Router 70…Gateway

Claims

1. A system capable of receiving an in-store customer order, which is an order using the customer's own mobile terminal in the store, comprising: a reading means for reading table identification information for identifying a table in the store; an authentication information acquisition means for acquiring authentication information for authenticating the in-store customer order; an authentication information registration means for registering the authentication information as the authentication information for authenticating the in-store customer order of the table identified by the table identification information when the table identification information is read by the reading means and the authentication information is acquired by the authentication information acquisition means; A system characterized by comprising the above.

2. An order reception means for receiving the in-store customer order is provided, and the order reception means receives the in-store customer order of the table when the table identification information is read by the reading means, the authentication information is acquired by the authentication information acquisition means, and the authentication information acquired by the authentication information acquisition means matches the authentication information registered as the authentication information for authenticating the in-store customer order of the table identified by the table identification information read by the reading means. The system according to claim 1.

3. A display means for displaying code information enabling acceptance of the in-store customer order of one table when the authentication information for authenticating the in-store customer order of the one table is registered by the authentication information registration means is provided, and the order reception means receives the in-store customer order of the table when the code information enabling acceptance of the in-store customer order of one table displayed by the display means is read by the reading means. The system according to claim 2.

4. A settlement means is provided, and the settlement means is capable of settlement based on the code information displayed by the display means. The system according to claim 3.

5. A history display means for displaying an order history for the table and accepting cancellation of the order is provided, and the history display means displays the order history by acquiring the authentication information. The system according to claim 1 or claim 2.

Images