JP7763122B2 - Order management device, order management method, and order management program - Google Patents

Description

The disclosed technology relates to an order management device, an order management method, and an order management program.

Traditionally, restaurants manage orders for each customer by accepting them from an ordering device installed in the customer guiding area (e.g., at a table).

For example, Patent Document 1 discloses a restaurant operation management system comprising a first mobile communication terminal operated by a restaurant staff member to input and send order information; a second mobile communication terminal to which various information owned by customers can be input and sent; a restaurant control device that compiles and manages order information; and a management control device that transmits and receives information between the first mobile communication terminal, the second mobile communication terminal, and the restaurant control device via communication lines and provides an information processing site that processes information related to the management and operation of the restaurant. The management control device includes a customer order site on the information processing site where customers can input and send order information. The first mobile communication terminal displays a two-dimensional code that records access information for accessing the customer order site. When the second mobile communication terminal operated by a customer accesses the customer order site based on the access information read from the two-dimensional code and inputs and sends order information, the received order information is sent to the restaurant control device. The restaurant control device then compiles and manages the order information transmitted from the second mobile communication terminal operated by the customer together with the order information transmitted from the first mobile communication terminal operated by the staff member.

Japanese Patent Application Laid-Open No. 2018-124694

With the technology in Patent Document 1, when customers order food using their own terminal devices, orders are accepted on a per-terminal basis, which means that it may be impossible to determine whether orders are from customers in the same area during the cooking, serving, or serving stages. For example, if cooking instruction slips are printed in the order in which the orders are received, order slips from various areas may be printed without being grouped by customer group. As a result, when cooking for each customer group, staff may make mistakes in the cooking order or serving destination.

The disclosed technology aims to provide an order management device, order management method, and order management program that can manage the cooking, serving, or provision of orders for each customer group when accepting orders via terminal devices owned by customers.

The order management device according to the first aspect is an order management device that communicates with multiple terminal devices, and includes a reception unit that receives orders from the multiple terminal devices, each of which includes an identifier that identifies one or more customers guided to a single area as a single unit, and a grouping unit that groups the multiple orders received within a predetermined period of time by the identifier.

In the first aspect, orders are grouped by the identifier contained in the order. Therefore, according to the first aspect, the cooking, serving, or provision of orders can be managed for each customer group.

The order management device according to the second aspect is the order management device according to the first aspect, wherein the grouping unit groups, by identifier, the orders received within a period set according to the number of customers or the number of terminal devices per unit from the time the first ungrouped order is received.

According to the second aspect, when a customer group has a large number of people, the waiting time for grouping orders can be extended, thereby increasing the number of orders grouped in a single output.

The order management device according to the third aspect is the order management device according to the first or second aspect, wherein the grouping unit extends the period when the customer places their first order in the unit compared to when the customer places an additional order.

According to the third aspect, the waiting time for grouping orders can be extended to accommodate the fact that a higher proportion of customers place initial orders compared to additional orders.

The order management device according to a fourth aspect is the order management device according to any one of the first to third aspects, wherein the grouping unit extends the period each time an order is received, within a range not exceeding a predetermined upper limit.

According to the fourth aspect, it may be possible to group additional orders placed after an additional order has been placed. Furthermore, according to the fourth aspect, it is possible to prevent the waiting time for grouping from becoming endlessly long.

The order management device according to the fifth aspect is the order management device according to any one of the first to fourth aspects, and includes an output unit that outputs the grouped orders received within the period after the period has elapsed.

According to the fifth aspect, the grouped orders are received by an external device or displayed on a display unit, allowing the external device or an employee to manage the cooking, serving, or provision of the orders.

The order management device according to the sixth aspect is the order management device according to the fifth aspect, wherein if the output unit receives orders from the same number of terminal devices as the number of customers in one unit corresponding to the identifier within the period, it outputs the grouped orders without waiting for the period to elapse.

According to the sixth aspect, when orders are accepted from the terminals of all members of a customer group, the orders are output to a printer or other device installed in the store without waiting for a certain period of time to pass, thereby shortening the time it takes to provide the items ordered by that customer group.

The order management device according to a seventh aspect is the order management device according to any one of the first to sixth aspects, and includes a generation unit that generates a two-dimensional code that is access information to an order screen and includes the identifier as a parameter, and the reception unit receives the order placed via the order screen from the terminal device that reads the two-dimensional code.

According to the seventh aspect, even if the terminal device and the identifier are not associated, it is possible to associate the identifier with the order.

The order management method according to the eighth aspect is an order management method for an order management device that communicates with multiple terminal devices, in which a computer executes the following processes: accepting customer orders from the multiple terminal devices, each of which includes an identifier that identifies one or more customers guided to a single area as a unit; and grouping the multiple orders accepted within a predetermined period by the identifier.

In the eighth aspect, orders are grouped by the identifier contained in the order. Therefore, according to the eighth aspect, the cooking, serving, or provision of orders can be managed for each customer group.

The order management program according to the ninth aspect is an order management program executed by an order management device that communicates with multiple terminal devices, and causes a computer to execute the following processes: accepting orders from multiple terminal devices, each containing an identifier that identifies one or more customers guided to a single area as a single unit; and grouping the multiple orders accepted within a predetermined period by the identifier.

In the ninth aspect, the computer is caused to perform the following process. That is, the order management program causes the computer to group orders by the identifier contained in the order. Therefore, according to the eighth aspect, the cooking, serving, or provision of orders can be managed for each customer group.

The disclosed technology allows for the cooking, serving, or provision of orders to be managed for each customer group.

FIG. 1 is a schematic configuration diagram showing an outline of an order management system. 1 is a block diagram showing a hardware configuration of an order management device according to a first embodiment. FIG. 1 is a block diagram showing a functional configuration of an order management device according to a first embodiment. FIG. 4 is a flowchart showing the flow of an order management process by the order management device according to the first embodiment. 4 is a flowchart showing the flow of an order management process by the order management device according to the first embodiment. 10 is an example of an identifier table of the order management device according to the first embodiment. 4 is an example of a slip in the order management system according to the first embodiment. 4 is an example of a slip in the order management system according to the first embodiment. 10 is a flowchart showing the flow of an order management process by the order management device according to the second embodiment. 10 is a flowchart showing the flow of an order management process by the order management device according to the second embodiment.

An example of an embodiment of the disclosed technology will be described below with reference to the drawings. Note that the same reference numerals are used to designate identical or equivalent components and parts in each drawing. Also, the dimensional proportions in the drawings have been exaggerated for the sake of explanation and may differ from the actual proportions.

An overview of how orders are managed using the order management system 1 of the present disclosure will be explained using Figure 1. The order management system 1 includes an order management device 10, a server 20, an accounting device 30, a printer 40, a handheld terminal 50, and a terminal device 60.

The order management device 10 is a device that manages orders. The order management device 10 communicates with terminal devices 60 via the server 20. The order management device 10 accepts orders that include an identifier that identifies one or more customers guided to an area from the server 20 as a single unit. In the present disclosure, this unit may be referred to as a customer group. An area may be a table, standing area, chairs, or a private room. The identifier is, for example, a combination of a store number for identifying the store and the table number of the table to which the customer group is guided. The order management device 10 generates a two-dimensional code that includes a QR code (registered trademark). The two-dimensional code is access information to an order screen that includes the identifier as a parameter.
The order management system 10 may have a redundant configuration that switches between a master and a backup in case of a failure. For example, the order management system 10A may be the master device, and the order management system 10B may be the backup device. In this disclosure, the order management system operating as the master device may be referred to as 10, and the reference numbers 10A and 10B may be used to distinguish between multiple order management systems.

Server 20 is a server that provides an order screen for customers visiting the store to place orders. Server 20 is, for example, a web server that provides a web page that constitutes the order screen. Server 20 receives a request from terminal device 60 that includes an identifier as a parameter. Server 20 then includes the received identifier in the order and sends it to the order management device 10.

The accounting device 30 is a device that processes orders by identifier.

Printer 40 is a printer installed inside the store. Printer 40 prints a two-dimensional code that includes an identifier. The printed two-dimensional code is placed by an employee in an area specified by the identifier. Printer 40 is also used to issue order slips, and the employee cooks or serves the food according to the printed slip.

The handheld terminal 50 is a terminal carried by an employee. The handheld terminal 50 transmits the number of customers, which is the number of people in a customer group, to the order management device 10 for each identifier. The handheld terminal 50 may also transmit the number of terminal devices, which is the number of terminal devices 60 used by the customer group. For example, an employee checks the number of terminal devices used by the customer group and transmits the number of terminal devices using the handheld terminal 50. In other words, the handheld terminal 50 transmits the number of terminal devices 60 with the same identifier for each identifier. The handheld terminal 50 may be a smartphone, tablet terminal, or the like.

The terminal device 60 is a smartphone, tablet, or other device owned by the customer. The terminal device 60 reads a printed two-dimensional code placed in the area using a camera installed on the terminal device 60. Next, the terminal device 60 sends a request including an identifier as a parameter to the server 20 using the access information of the read two-dimensional code. The terminal device 60 then acquires an order screen for placing an order and places the order. In other words, the terminal device 60 sends the order to the order management device 10 via the order screen. The terminal device 60 sends a value to identify itself, such as a MAC (Media Access Control address) address, an IP (Internet Protocol) address, or a value assigned to each terminal device 60, to the order management device 10 or server 20.

[First embodiment]
2 is a block diagram showing the hardware configuration of the order management device 10. The order management device 10 has a CPU (Central Processing Unit) 11, a ROM (Read Only Memory) 12, a RAM (Random Access Memory) 13, storage 14, an input unit 15, a display unit 16, and a communication interface 17. Each component is connected to each other via a bus 19 so that they can communicate with each other.

The CPU 11 is a central processing unit that executes various programs and controls each component. That is, the CPU 11 reads programs from the ROM 12 or storage 14 and executes the programs using the RAM 13 as a work area. The CPU 11 controls the above components and performs various calculation processes in accordance with the programs stored in the ROM 12 or storage 14. In the first embodiment, the order management program is stored in the ROM 12 or storage 14.

ROM 12 stores various programs and data. RAM 13 serves as a working area for temporarily storing programs or data. Storage 14 is composed of a storage device such as an HDD (Hard Disk Drive) or SSD (Solid State Drive), and stores various programs, including the operating system, and various data.

The input unit 15 includes a pointing device such as a mouse and a keyboard, and is used to enter various inputs.

The display unit 16 is, for example, a liquid crystal display, and displays various information. The display unit 16 may also be a touch panel type and function as the input unit 15.

The communication interface 17 is an interface for communicating with other devices. For this communication, a wired communication standard such as Ethernet (registered trademark) or FDDI, or a wireless communication standard such as 4G, 5G, or Wi-Fi (registered trademark) may be used.

Next, the functional configuration of the order management system 10 will be described.
3 is a block diagram showing an example of the functional configuration of the order management device 10. The order management device 10 has, as its functional components, a reception unit 101, a grouping unit 102, an output unit 103, and a generation unit 104. Each functional component is realized when the CPU 11 reads out an order management program stored in the ROM 12 or the storage 14, expands it in the RAM 13, and executes it.

The reception unit 101 receives customer orders from multiple terminal devices, including an identifier that identifies the area within the customer's store. The reception unit 101 receives orders placed via an order screen from a terminal device that reads a two-dimensional code.

The grouping unit 102 groups multiple orders received within a predetermined period by identifier. The grouping unit 102 groups orders with the same identifier received within a period set according to the number of customers or terminal devices in the area from the time the first ungrouped order was received. The grouping unit 102 extends the period when a customer places their first order in an area compared to when an additional order is placed. The grouping unit 102 extends the period each time an order is received, within a range that does not exceed a predetermined upper limit.

The output unit 103 outputs the grouped orders and two-dimensional codes. "Output" means sending them to another device via the communication interface 17, displaying them on the display unit 16, or the like. The output unit 103 outputs the grouped orders received within a period after the period has elapsed. If the output unit 103 receives orders within the period from the same number of terminal devices as the number of customers corresponding to the identifiers, it may output the grouped orders without waiting for the period to elapse.

The generation unit 104 generates a two-dimensional code that is access information to the order screen and includes the identifier as a parameter.

Next, the operation of the order management system 10 will be described.
4 and 5 are flowcharts showing the flow of order management processing by the order management device 10. The CPU 11 reads out the order management program from the ROM 12 or the storage 14, loads it into the RAM 13, and executes it to perform order management.

Figure 4 is a flowchart showing the order registration process performed by the order management device 10.

In step S101, the CPU 11 accepts an order. The CPU 11 proceeds to step S102.

In step S102, the CPU 11 determines whether the identifier is registered in the identifier table. If the CPU 11 determines that the identifier is not registered in the identifier table (step S102: NO), the CPU 11 proceeds to step S103. If the CPU 11 determines that the identifier is registered in the identifier table (step S102: YES), the CPU 11 proceeds to step S110.
An example of the identifier table of the order management system 10 is shown in Figure 6. The identifier table has fields for storing the identifier, number of customers, registration time, slip output time, new/added, MAC address, and slip control number. The new/added field is a field for storing a new flag or an item flag. The MAC address field and the slip control number field can store multiple values. The MAC address is an example of a value that identifies the terminal device 60.
The processing of identifier A15 occurs immediately after a new order is accepted, and the system is waiting until the time to print the slip. The processing of identifiers B20 and B25 occurs after an additional order has been accepted and the system is waiting until the time to print the slip. The processing of identifiers A03 and A04 occurs after a slip has been printed and the system is waiting for the next order. The order management system 10 deletes identifiers for which transaction processing has been completed from the identifier table.

In step S103, the CPU 11 registers the identifier. That is, if the identifier included in the order does not exist in the identifier table, the CPU 11 adds a row to the identifier table and registers the identifier included in the order. The processing from step S103 to step S109 described below is performed on the row of the identifier included in the order. The CPU 11 proceeds to step S104.

In step S104, the CPU 11 sets a new flag. The CPU 11 proceeds to step S105.

In step S105, the CPU 11 sets the number of customers. The CPU 11 proceeds to step S106.

In step S106, the CPU 11 sets the registration time. The CPU 11 proceeds to step S107.

In step S107, the CPU 11 sets the slip output time. If the new/added item is a new flag, the CPU 11 sets the slip output time to the time obtained by multiplying 30 seconds by the number of customers and adding that value to the registration time. If the new/added item is an addition flag, the CPU 11 sets the slip output time to 30 seconds regardless of the number of customers. The CPU 11 proceeds to step S108.

In step S108, the CPU 11 registers the MAC address. The CPU 11 proceeds to step S109.

In step S109, the CPU 11 registers the slip management number. The CPU 11 then proceeds to step S112.

In step S110, the CPU 11 determines whether the MAC address is registered in the identifier table. If the CPU 11 determines that the MAC address is registered in the identifier table (step S110: YES), the process proceeds to step S111. If the CPU 11 determines that the MAC address is not registered in the identifier table (step S110: NO), the process proceeds to step S108.

In step S111, the CPU 11 registers the slip management number. That is, the CPU 11 registers the slip management number in the row of the identifier table in which the MAC address is registered. The CPU 11 proceeds to step S101.

In step S112, CPU 11 determines whether the registered MAC address is equal to or greater than the number of customers. If CPU 11 determines that the registered MAC address is equal to or greater than the number of customers (step S112: YES), it proceeds to step S113. If CPU 11 determines that the registered MAC address is less than the number of customers (step S112: NO), it proceeds to step S101.

In step S113, the CPU 11 outputs the slip with the slip management number. That is, the CPU 11 outputs the slip with the slip management number for which the registered MAC address is equal to or greater than the number of customers. The CPU 11 proceeds to step S114.

In step S114, the CPU 11 initializes the registration time, slip output time, MAC address, and slip control number. The CPU 11 then proceeds to step S115.

In step S115, the CPU 11 sets the addition flag. The CPU 11 proceeds to step S101.

As described above, by the processing of steps S112 and S113, if the CPU 11 receives orders from at least the same number of terminal devices as the number of customers corresponding to the identifiers within the period, it outputs the grouped orders without waiting for the period to elapse.

Figure 5 is a flowchart showing the flow of the invoice issuance process performed by the order management device 10. The order management device 10 executes the invoice issuance process periodically, for example, every 10 seconds.

In step S201, the CPU 11 assigns 1 to the variable i. The CPU 11 then proceeds to step S202.

In step S202, the CPU 11 checks the i-th identifier in the identifier table. Steps S203 to S207, described below, perform processing on the i-th identifier. The CPU 11 then proceeds to step S203.

In step S203, the CPU 11 determines whether the system time has passed the slip output time. If the CPU 11 determines that the system time has not passed the slip output time (step S203: NO), it proceeds to step S204. If the CPU 11 determines that the system time has passed the slip output time (step S203: YES), it proceeds to step S205.

In step S204, the CPU 11 adds 1 to the variable i. The CPU 11 proceeds to step S208.

In step S205, the CPU 11 outputs the invoice with the invoice management number. That is, it outputs the invoice with the invoice management number for which the system time has passed the invoice output time. The CPU 11 proceeds to step S206.

In step S206, the CPU 11 initializes the registration time, slip output time, MAC address, and slip management number. The CPU 11 then proceeds to step S207.

In step S207, the CPU 11 sets the addition flag. The CPU 11 proceeds to step S202.

In step S208, the CPU 11 determines whether all identifiers registered in the identifier table have been confirmed. If the CPU 11 determines that all identifiers registered in the identifier table have been confirmed (step S208: YES), it terminates the slip issuance process. If the CPU 11 determines that all identifiers registered in the identifier table have not been confirmed (step S208: NO), it proceeds to step S202.

By performing the above-described processing from steps S101 to S111, S203, and S205, the CPU 11 groups multiple orders received within a predetermined period by identifier. The CPU 11 then outputs the grouped orders received within the period after the period has elapsed.

FIG. 7 is an example of a slip in the order management system 1.
Slip 201A is a slip for an order placed at 18:05 by a customer group with identifier A15.
Slip 201B is a slip for an order placed at 18:05 by a customer group with identifier B20.
Slip 201C is a slip for an order placed at 18:05 by a customer group with identifier A15.
Slip 201D is a slip for an order placed at 18:06 by a customer group with identifier A15.
Slip 201E is a slip for an order placed at 18:06 by a customer group with identifier A15.

The order management device 10 groups multiple orders received within a predetermined period by identifier. The order management device 10 then outputs the grouped orders after the period has elapsed. Therefore, the order management device 10 manages slips 201A, 201C, 201D, and 201E as one group, and slip 201B as another group. The order management device 10 then outputs each of the grouped orders after the respective periods have elapsed.

For example, when printing slips consecutively, printer 40 prints blank slip 202 between slips corresponding to orders from different groups. Printer 40 prints blank slip 202 after printing slip 201A, slip 201C, slip 201D, and slip 201E. Then, printer 40 prints slip 201B after printing the blank slip. This makes it easier to recognize groups, making it easier to manage the cooking, serving, and provision of orders for each customer group.
It should be noted that the printing of slips may be performed using a partial cut, in which the slips are not completely separated but are cut at one point.

Figure 8 is an example of a slip for the order management system 1. Figure 8 shows an example in which slips 201A, 201C, 201D, and 201E from Figure 7 above are output as a single slip. In other words, the printer 40 may print grouped orders with the same identifier as a single slip.

Second Embodiment
Next, a second embodiment will be described. In the second embodiment, the operation of the order management system 10 will be described using a flowchart different from that shown in FIGS. 4 and 5. The hardware configuration and functional configuration of the second embodiment are the same as those of the first embodiment. Furthermore, parts with the same configuration and operation as those of the first embodiment will be assigned the same reference numerals and will not be described again.

The operation of the order management system 10 will now be described.
9 and 10 are flowcharts showing the flow of order management processing by the order management system 10.

Figure 9 is a flowchart showing the processing flow executed when a customer visits the store.

In step S301, the CPU 11 accepts an identifier and the number of customers. That is, the CPU 11 accepts the number of customers guided to an area and the identifier of that area from the handheld terminal 50. The CPU 11 may also accept the identifier and the number of customers from the input unit 15. The CPU 11 may also accept the number of terminal devices instead of the number of customers. The CPU 11 proceeds to step S302.

In step S302, the CPU 11 generates and outputs a two-dimensional code. Specifically, the CPU 11 generates a two-dimensional code that is access information to the order screen and includes the received identifier as a parameter. The CPU 11 sends the two-dimensional code to the printer 40 and instructs it to print the two-dimensional code. The CPU 11 proceeds to step S303.

In step S303, CPU 11 determines a period of length according to the number of customers. That is, CPU 11 determines a period for each identifier so that the greater the number of customers, the longer the period is compared to when there are fewer customers. CPU 11 may also determine an upper limit on the total period according to the number of customers. For example, CPU 11 determines the length of the period as follows: 0 minutes if there is one customer, 0.5 minutes if there are two customers, 1 minute if there are three customers, and 5 minutes if there are four or more customers. CPU 11 proceeds to step S304.

In step S304, the CPU 11 executes order processing for each identifier. Specific processing will be described later with reference to FIG. 10. The CPU 11 then terminates the order management processing.

Figure 10 is a flowchart showing the order processing flow executed for each identifier.

In step S401, the CPU 11 determines whether an order has been accepted. If the CPU 11 determines that an order has been accepted (step S401: YES), the process proceeds to step S402. If the CPU 11 determines that an order has not been accepted (step S401: NO), the process proceeds to step S406.

In step S402, CPU 11 determines whether there are any grouped orders. In other words, CPU 11 determines whether orders containing the same identifier are grouped. CPU 11 references the identifier table to determine whether there are any grouped orders. If CPU 11 determines that there are no grouped orders (step S402: YES), it proceeds to step S403. If CPU 11 determines that there are grouped orders (step S402: NO), it proceeds to step S404.

In step S403, the CPU 11 starts a period. That is, the CPU 11 newly registers the identifier included in the order accepted in the processing of step S401 in the identifier table and starts a period (summary) for that identifier. The CPU 11 proceeds to step S405.

In step S404, the CPU 11 extends the period. For the identifier included in the order accepted in the processing of step S401, the CPU 11 extends the period of that identifier. That is, unlike the first embodiment, the order management device 10 extends the period for grouping each time an order is accepted. Note that the extended period may be different from the period determined in the processing of step S303 described above. The CPU 11 may extend the period as long as it does not exceed a predetermined upper limit. The CPU 11 proceeds to step S405.

In step S405, the CPU 11 groups the accepted orders. That is, the CPU 11 groups the orders by identifier. In other words, the CPU 11 adds the accepted order to the group of the identifier included in the order. The CPU 11 proceeds to step S406.

In step S406, the CPU 11 determines whether the period has elapsed. If the CPU 11 determines that the period has elapsed (step S406: YES), the process proceeds to step S407. If the CPU 11 determines that the period has not elapsed (step S406: NO), the process proceeds to step S409.

In step S407, the CPU 11 outputs the grouped orders. For example, the CPU 11 sends the grouped orders to the printer 40 to print the orders. The CPU 11 may also display the grouped orders on the display unit 16. The CPU 11 proceeds to step S408.

In step S408, the CPU 11 ungroups the output orders. For example, if the CPU 11 manages groups by adding the orders to be grouped to a list, it deletes the output orders from the list. The CPU 11 proceeds to step S409.

In step S409, the CPU 11 determines whether the order has been paid for by the payment device 30. If the CPU 11 determines that the order has been paid for (step S409: YES), it terminates order processing. If the CPU 11 determines that the order has not been paid for (step S409: NO), it proceeds to step S401.

As described above, by the processing of steps S401 to S403, if a group for the identifier included in the accepted order has not been created, the CPU 11 creates a group for that identifier. Then, upon creating the group, the CPU 11 starts the period for that identifier. In other words, the CPU 11 starts the period for the identifier included in the first order from the time when the CPU 11 receives the first ungrouped order out of the multiple accepted orders.

Furthermore, by performing the processes of steps S401, S402, and S404 described above, the CPU 11 extends the period each time an order is received.

Furthermore, by the processing of steps S406 and S407 described above, the CPU 11 waits until the period has elapsed for an order to be sent from a terminal device 60 that is capable of sending an order containing the same identifier. The CPU 11 also stores the received order in the ROM 12 or storage 14 until the period has elapsed.

[remarks]
The order management device 10 according to the first and second embodiments has been described above. However, the present disclosure is not limited to the above embodiments. Various improvements and modifications are possible.

In the order management device 10 according to the first embodiment, the slip management number may be configured as a combination of the slip number and the number of orders. The order management device 10 transmits and receives the slip management number to the terminal device 60. In step S109 of FIG. 4, the CPU 11 registers the slip management number and transmits the registered slip management number to the terminal device 60 that sent the order. The terminal device 60 transmits the order to the order management device 10, including a slip management number that is the slip number plus the number of orders. The order management device 10 deletes the slip management number for which a transaction has been made from the identifier table. The order management device 10 deletes from the identifier table an identifier for which all slip management numbers have been deleted.

In step S303 of FIG. 9, CPU 11 may set the length of the period uniformly. Alternatively, in step S403, CPU 11 may start the period from a predetermined time for each identifier. That is, CPU 11 groups and outputs orders received at regular intervals from a predetermined time. For example, CPU 11 groups orders every 5 minutes starting from 12:00 for one identifier, and groups orders every 5 minutes starting from 12:01 for another identifier. This allows the intervals between order outputs to be dispersed.

In step S303 of FIG. 9, the CPU 11 may set a longer period when a customer in the customer group places their first order than when an additional order is placed. In other words, when grouped orders have not been output, the CPU 11 sets a longer period than when grouped orders have been output.

In step S302 of FIG. 9, the CPU 11 may generate a two-dimensional code and send it to the handheld terminal 50 or ordering device. Here, the ordering device is a device (not shown) such as a tablet terminal installed in the area for placing orders. The CPU 11 sends the two-dimensional code to the ordering device located in the area identified by the identifier received in the processing of step S301, and causes the ordering device to display the two-dimensional code. The terminal device 60 reads the two-dimensional code displayed on the handheld terminal 50 or ordering device and accesses the server 20. This allows the terminal device 60 to read the two-dimensional code without having to print it.

10, the CPU 11 may determine that the period for the identifier has elapsed when orders have been received within the period from all terminal devices 60 with the same identifier included in the orders. In other words, when the order management device 10 has received orders within the period from the same number of terminal devices 60 as the number of customers corresponding to the identifier, it outputs the grouped orders for the identifier without waiting for the period to elapse.
For example, the order management device 10 counts the number of terminal devices 60 by receiving a value that identifies the terminal device 60. For example, the terminal device 60 transmits an order including an identifier and a MAC address to the order management device 10. The order management device 10 counts the number of MAC addresses each time an order is received, and determines whether the number of MAC addresses and the number of customers for the same identifier are the same.

In step S301 of FIG. 9, the CPU 11 may add a predetermined value to the number of accepted customers. For example, if the number of accepted customers is 1, the CPU 11 adds 1 as a predetermined value, sets the number of customers to 2, and executes the subsequent processing. This allows, for example, even if a customer is ordering alone, to wait for the order to be output and output additional orders all at once.

The order management device 10 according to each of the above embodiments outputs grouped orders and ungrouped orders when the master and backup are switched. For example, if the order management device 10A is the master device and the order management device 10B is the backup device, when the master and backup are switched, the order management device 10B, which has become the master, outputs all of the orders it holds.

In addition, the order management processing executed by the CPU in each of the above embodiments by loading software (programs) may also be executed by various processors other than the CPU. Examples of processors in this case include PLDs (Programmable Logic Devices) such as FPGAs (Field-Programmable Gate Arrays), whose circuit configuration can be changed after manufacture, and dedicated electrical circuits, such as ASICs (Application Specific Integrated Circuits), which are processors with circuit configurations designed specifically to execute specific processes. Furthermore, the order management processing may be executed by one of these various processors, or by a combination of two or more processors of the same or different types (e.g., multiple FPGAs, or a combination of a CPU and an FPGA). Furthermore, the hardware structure of these various processors is, more specifically, an electrical circuit that combines circuit elements such as semiconductor devices.

In addition, in the above embodiments, the order management program is described as being pre-stored (installed) in computer-readable storage 14, but this is not limited to this. The program may also be provided in a form stored on a non-transitory storage medium such as a CD-ROM (Compact Disk Read Only Memory), a DVD-ROM (Digital Versatile Disk Read Only Memory), or a USB (Universal Serial Bus) memory. The program may also be downloaded from an external device via a network.

1 Order management system 10 Order management device 20 Server 30 Accounting device 40 Printer 50 Handy terminal 60 Terminal devices 201A, 201B, 201C, 201D, 201E Slip 202 Blank slip

Claims (8)

An order management device that communicates with a plurality of terminal devices,
a reception unit that receives orders from the customers from the plurality of terminal devices, the orders including an identifier that identifies one or more customers guided to one area as a unit;
a grouping unit that groups the plurality of orders received within a predetermined period by the identifier;
Including,
The grouping unit sets the period longer when the customer places an order for the first time in the unit than when the customer places an additional order.
Order management device. 2. The order management device according to claim 1, wherein the grouping unit groups the orders received within a period set according to the number of customers or the number of terminal devices in one unit from the time when a first ungrouped order is received, by the identifier. The order management device according to claim 1 or 2 , wherein the grouping unit extends the period each time an order is received within a range not exceeding a predetermined upper limit. The order management device according to claim 1 , further comprising an output unit that outputs the grouped orders received within the period after the period has elapsed. The order management device according to claim 4, wherein the output unit outputs the grouped orders without waiting for the period to elapse if the output unit receives the orders from the terminal devices in a number equal to the number of customers in the unit corresponding to the identifier within the period. a generating unit that generates a two-dimensional code that is access information to an order screen and includes the identifier as a parameter;
The order management device according to claim 1 , wherein the reception unit receives the order placed via the order screen from the terminal device that reads the two-dimensional code. An order management method in an order management device that communicates with a plurality of terminal devices, comprising:
a process of receiving orders from the plurality of terminal devices, the orders including an identifier for identifying one or more customers guided to one area as a unit;
a process of grouping the orders received within a predetermined period by the identifier ;
a process of setting the period longer when the customer places an order for the first time in the unit than when the customer places an additional order;
A computer-implemented order management method. An order management program executed in an order management device that communicates with a plurality of terminal devices,
a process of receiving orders from one or more customers guided to one area from a plurality of terminal devices, the orders including an identifier for identifying the one or more customers as a unit;
a process of grouping the orders received within a predetermined period by the identifier ;
a process of setting the period longer when the customer places an order for the first time in the unit than when the customer places an additional order;
An order management program for causing a computer to execute the above.