Server terminal

Abstract

To provide a server terminal which aggregates and manages orders from a plurality of ordering platforms.SOLUTION: In a system 1, a plurality of service terminals operating ordering platforms which receive takeout and / or delivery orders of restaurants from a plurality of user terminals, a server terminal, and a plurality of shop terminals are connected via a network. The server terminal includes: an order receiving unit which receives order information from one or a plurality of takeout or delivery service terminals; a slip generation unit which generates slip information on the basis of the order information; and an information transmission unit which transmits the slip information to store terminals related to the restaurants. The order information contains user information related to ordering users, menu information related to the contents and quantity of the order, service identification information for identifying a service related to the service terminal, and order type information related to the type of the delivery or takeout. The slip information contains at least the menu information and the service identification information.SELECTED DRAWING: Figure 7

Description

[Technical Field]

[0001] The present invention relates to a server terminal that aggregates and manages orders from multiple ordering platforms. [Background technology]

[0002] In the food and beverage industry, the types of services provided have become more diverse, including dine-in, delivery, and take-out, and it has become common for users to order food and beverages from their desired restaurants using their own ordering apps (e.g., Uber Eats (registered trademark) and Demae-can (registered trademark)).

[0003] For example, a reservation order processing system that can reliably process reservation orders has been disclosed (Patent Document 1). [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Publication No. 2020-201804 Summary of the Invention [Problem to be solved by the invention]

[0005] However, although Patent Document 1 discloses technology that enables in-store orders and advance orders to be processed in a timely manner and cooking instruction slips to be output, while it discloses processing of multiple order types for the same store, it does not accommodate orders from multiple ordering platforms.

[0006] Therefore, an object of the present invention is to realize a method for aggregating and managing orders from multiple ordering platforms. [Means for solving the problem]

[0007] In one aspect of the present invention, there is provided a server terminal having an order receiving unit that receives order information from one or more takeout or delivery service terminals, an invoice generation unit that generates invoice information based on the order information, and an information transmission unit that transmits the invoice information to a store terminal associated with a food and beverage store, wherein the order information includes user information associated with the ordering user, menu information associated with the order content and quantity, service identification information that identifies a service associated with the service terminal, and order type information associated with the type of delivery or takeout, and the invoice information includes at least the menu information and the service identification information. [Effects of the Invention]

[0008] The present invention provides a method for aggregating and managing orders from multiple ordering platforms. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is a block diagram showing an order management system according to a first embodiment of the present invention; [Figure 2] FIG. 2 is a functional block diagram showing the server terminal 100 of FIG. [Figure 3] 2 is a functional block diagram showing the store terminal 300 of FIG. 1. FIG. [Figure 4] 2 is a schematic diagram showing an example of service information stored in the server 100. FIG. [Figure 5] 2 is a schematic diagram showing an example of order information stored in the server 100. FIG. [Figure 6] 2 is a schematic diagram showing an example of slip information stored in the server 100. FIG. [Figure 7] 1 is an example of a flowchart relating to an order management method executed in a server terminal 100 according to the first embodiment of the present invention. [Figure 8] 10 is an example of a flowchart relating to a slip management method executed in a store terminal 300 according to the first embodiment of the present invention. [Figure 9]10 is an example of an order management screen displayed on a store terminal 300 according to the first embodiment of the present invention. [Figure 10] 10 is an example of a slip output by a store terminal 300 according to the first embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, embodiments of the present invention will be described with reference to the drawings. Note that the embodiments described below do not unduly limit the content of the present disclosure described in the claims. Furthermore, not all of the components shown in the embodiments are necessarily essential components of the present disclosure.

[0011] (Embodiment 1) <Configuration> 1 is a block diagram showing an order management system according to a first embodiment of the present invention. This operation system 1 includes service terminals 200A and 200B (hereinafter collectively referred to as "service terminals 200") that operate an order platform that accepts takeout and / or delivery orders from affiliated restaurants (associated with store terminals 300A and 300B) from user terminals 400A and 400B (hereinafter collectively referred to as "user terminals 400"), a server terminal 100 that accepts and centrally manages orders from the service terminals 200, and store terminals 300A and 300B (hereinafter collectively referred to as "store terminals 300") that accept orders from the server terminal 100.

[0012] The server terminal 100, the service terminal 200, and the store terminal 300 are connected via a network NW. The network NW is configured by the Internet, an intranet, a wireless LAN (Local Area Network), a WAN (Wide Area Network), or the like.

[0013] The server terminal 100, the service terminal 200, and the store terminal 300 may be, for example, a general-purpose computer such as a workstation or a personal computer, or may be logically realized by cloud computing. In this embodiment, for convenience of explanation, one server terminal is illustrated, but this is not limited to this and multiple servers may be used. In particular, the store terminal 300 may be configured as a POS terminal in addition to the above.

[0014] The user terminal 400 is, for example, an information processing device such as a personal computer or a tablet terminal, but may also be configured as a smartphone, a mobile phone, a PDA, or the like.

[0015] In this embodiment, the system 1 is described as having a server terminal 100, a service terminal 200, and a store terminal 300, and users of the service terminal 200 and the store terminal 300 use their respective terminals to perform operations on the server terminal 100; however, the server terminal 100 may be configured as a standalone unit, and the server terminal itself may have the functionality for each user to perform operations.

[0016] Fig. 2 is a functional block configuration diagram of the server terminal 100 of Fig. 1. The server terminal 100 includes a communication unit 110, a storage unit 120, and a control unit .

[0017] The communication unit 110 is a communication interface for communicating with the service terminal 200 and the store terminal 300 via the network NW, and communication is performed according to a communication protocol such as TCP / IP (Transmission Control Protocol / Internet Protocol).

[0018] The storage unit 120 stores input data and other information for executing various control processes and functions within the control unit 130, and is composed of RAM (Random Access Memory), ROM (Read Only Memory), and other components. The storage unit 120 also includes a service information storage unit 121 for storing various data related to the service provider of the service terminal, an order information storage unit 122 for storing various data related to menu orders received from the service terminal 200, and a slip information storage unit 123 for storing slip information generated based on the order information and related to slips output via the store terminal 300. The storage unit 120 can also temporarily store data communicated with the service terminal 200 and the store terminal 300. A database (not shown) for storing various data may be constructed outside the storage unit 120.

[0019] The control unit 130 controls the overall operation of the server terminal 100 by executing programs stored in the storage unit 120, and is composed of a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), etc. The functions of the control unit 130 include an order information receiving unit 131 that receives order information from the service terminal 200, a slip information generation unit 132 that generates slip information based on the order information, and an information transmission unit 133 that transmits information to the service terminal 200 or the store terminal 300. The order information receiving unit 131, slip information generation unit 132, and information transmission unit 133 are activated by programs stored in the storage unit 120 and executed by the server terminal 100, which is a computer (electronic calculator).

[0020] When the user terminal 400 places an order for a menu or the like with a restaurant via an application or the like provided by the service provider of the service terminal 200, the order information receiving unit 131 receives the order information from the service terminal 200 via the communication unit 110.

[0021] The slip information generation unit 132 performs processing to generate slip information based on the received order information.

[0022] The information transmitting unit 133 performs processing to transmit order information and slip information to the store terminal 300 .

[0023] Fig. 3 is a functional block diagram showing the store terminal 300 of Fig. 1. The store terminal 300 includes a communication unit 310, a display operation unit 320, a storage unit 330, and a control unit 340.

[0024] The communication unit 310 is a communication interface for communicating with the server terminal 100 via the network NW, and communication is performed according to a communication protocol such as TCP / IP.

[0025] The display operation unit 320 is a user interface used by the owner to input instructions and display text, images, etc. in accordance with input data from the control unit 340, and is composed of a display, keyboard, and mouse if the store terminal 300 is configured as a personal computer, and is composed of a touch panel, etc. if the store terminal 300 is configured as a tablet terminal. This display operation unit 320 is started up by a control program stored in the storage unit 330 and executed by the store terminal 300, which is a computer (electronic calculator).

[0026] The storage unit 330 stores programs for executing various control processes and functions in the control unit 340, order information, slip information, input data, etc., and is composed of RAM, ROM, etc. The storage unit 330 also temporarily stores the contents of communications with the server terminal 100.

[0027] The control unit 340 controls the overall operation of the store terminal 300 by executing the programs stored in the storage unit 330, and is composed of a CPU, a GPU, and the like.

[0028] The store terminal 300 is also connected via a wired or wireless network to an output device 500 such as a printer that outputs slips based on slip information.

[0029] FIG. 4 is a schematic diagram showing an example of service information stored in the server 100. As shown in FIG.

[0030] Service information 1000 shown in Fig. 4 stores various data related to the service provider of the service terminal. For ease of explanation, Fig. 4 shows an example of one service provider (the provider identified by the service ID "10001"), but information on multiple service providers can be stored. The various data related to the service provider can include, but is not limited to, basic information about the service operated by the service provider (service name, provider name, address, contact information, etc.), order information received from the service provider (ordering user information, ordered menu information, order type information, accounting information, status information, etc.), etc.

[0031] FIG. 5 is a schematic diagram showing an example of order information stored in the server 100. As shown in FIG.

[0032] The order information 2000 shown in FIG. 5 stores various data related to menu orders received from the service terminal 200. For ease of explanation, FIG. 5 shows an example of one order (the order identified by the order ID "20001"), but information on multiple orders can be stored. The various data related to the order can include, for example, information about the service for which the order was received, information about the ordering user, information about the store to which the order was placed (store name, address, contact information, etc.), information about the ordered menu (order details, quantity, toppings, cutlery, etc.), information about the order type (delivery, takeout, eat-in, etc.), accounting information (amount of the bill, whether the bill is paid or not, payment method), order status information (preparing (cooking), picked up, being delivered, delivered, etc.), etc., but is not limited to this.

[0033] FIG. 6 is a schematic diagram showing an example of slip information stored in the server 100. As shown in FIG.

[0034] The slip information 3000 shown in FIG. 6 is generated based on order information and stores slip information related to a slip output via the store terminal 300. For ease of explanation, FIG. 6 shows an example of slip information linked to one slip (a slip identified by slip ID "30001"), but information related to multiple slips can be stored. For example, slip information 3000 can include, for the slip identified by slip ID "30001," information about the service ordered, information about the ordered menu (order details, quantity, toppings, cutlery, etc.), information about the order type (delivery, takeout, eat-in, etc.), transaction information (amount of transaction, whether transaction is completed or not, payment method), order status information (preparing (cooking), picked up, etc.), but is not limited to this.

[0035] <Processing flow> The processing flow of the order management method executed by the system 1 of this embodiment will be described with reference to Fig. 7. Fig. 7 is an example of a flowchart relating to the order management method according to the first embodiment of the present invention.

[0036] To use this system 1, the service provider and the store operator access the server terminal 100 using the internet browser of the service terminal 200 or the store terminal 300, respectively, and register for the service as the service provider or the store operator after going through a predetermined procedure for the service operated by the server terminal 100. The service provider receives authentication information such as an ID and password, and becomes able to use the service by logging in to the service via the service terminal 200 after authentication. After this authentication, a predetermined user interface is provided via a web screen or the like, and the process proceeds to step S101 shown in FIG. 7.

[0037] First, in the process of step S101, the information receiving unit 131 of the control unit 130 of the server terminal 100 receives menu order information from the service terminal 200. For example, as shown in the information included in the order management screen displayed on the store terminal 300 in FIG. 9 , the order information may include, but is not limited to, information about the service for which the order was received (including the service ID "10004" etc.), information about the ordering user (e.g., "K Ichiro"), information about the store to which the order was received (e.g., "ABC Curry"), information about the ordered menu (e.g., "chicken curry", quantity (one), toppings (fukujinzuke pickles, sauce), flavor (medium spicy)), billing information (e.g., bill amount "1,140 yen"), and order status information (e.g., "preparing") The information receiving unit 131 stores the received order information in the service information storage unit 121 and order information storage unit 122 of the memory unit 120, respectively.

[0038] Next, in step S102, the slip information generation unit 132 of the control unit 130 of the server terminal 100 generates slip information based on the received order information. The slip information generation unit 132 generates slip information based on the order information stored in the order information storage unit 122. For example, slip information included in the slip output from the store terminal in FIG. 10 may include, but is not limited to, an order ID (e.g., "20004"), order time (e.g., "1:07 PM"), information about the service for which the order was received (e.g., the name of the service provider "OVER EATS" or the service ID), information about the ordered menu (e.g., "chicken curry," quantity (one), toppings (fukujinzuke, sauce), flavor (medium spicy), etc.), information about the type of order (delivery, takeout, eat-in, etc.), and billing information (e.g., the billing amount "1,140 yen") The slip information generation unit 132 stores the generated slip information in the slip information storage unit 123 of the memory unit 120.

[0039] Next, in the process of step S103, the information transmitting unit 133 of the control unit 130 of the server terminal 100 transmits the order information and / or the slip information to the store terminal 300 of the order destination.

[0040] FIG. 8 is an example of a flowchart of a slip management method executed by the store terminal 300 according to the first embodiment of the present invention.

[0041] First, in step S201, the control unit 340 of the store terminal 300 receives the order information and / or slip information from the server terminal 100 via the network NW and the communication unit 310. The control unit 340 stores the received order information and / or slip information in the storage unit 320. FIG. 9 shows the order information displayed on the user interface screen of the store terminal 300. The order information includes information identifying the delivery / takeout ordering service provider, allowing the store to centrally check user orders placed through multiple service providers (ordering platforms) using a single order management application. Although not shown, it is also possible to display the order type, such as delivery or takeout, so that store personnel responsible for order management can instantly identify the ordering service provider, the order type, and other menu information, thereby facilitating order management.

[0042] Next, in step S202, the control unit 340 of the store terminal 300 displays the received order information via the display operation unit 320 and / or outputs receipt information as a paper medium to the output device 500, such as a printer. FIG. 10 shows a receipt printed from the output device 500 connected to the store terminal 300. Information identifying one of multiple service providers (ordering platforms) is printed on the receipt, and although not shown, it is also possible to stamp the order type, such as delivery or takeout, making it easier for store staff, such as cooks, to process the order and also allowing delivery or takeout customers to immediately understand the order details by looking at the receipt and collect the food and drink that has been provided.

[0043] Although the embodiments of the present disclosure have been described above, they can be implemented in various other forms, and various omissions, substitutions, and modifications can be made. These embodiments, modifications, and omissions, substitutions, and modifications are included in the technical scope of the claims and their equivalents. [Explanation of symbols]

[0044] 1 System 100 Server terminal, 110 Communication unit, 120 Storage unit, 130 Control unit, 200 Service terminal, 300 Store terminal, 400 User terminal, NW network

Claims

1. An order receiving unit that receives order information from a service terminal that can receive orders for takeout and delivery of food and beverages from a restaurant from an ordering user; a slip generation unit that generates slip information based on the order information; an information sending unit that sends the slip information to a store terminal associated with the eating and drinking establishment, The order information includes user information related to the ordering user, menu information related to the order content and quantity, service identification information for identifying a service related to the service terminal, and Order type information related to an order type selected by the ordering user from options including delivery or takeout, The slip information includes at least order type information, menu information, and service identification information.

2. A server terminal as described in claim 1, wherein the order type information includes information on the order type selected by the ordering user from options including delivery, takeout, or eat-in.

3. A server terminal as described in claim 1, wherein the order information includes information regarding toppings for food and beverages.

4. A server terminal as described in claim 1, wherein the order information includes information regarding the taste of food and beverages.

5. 2. The server terminal according to claim 1, wherein the order information further includes transaction information relating to whether the ordering user has completed or not completed a transaction, and the slip information includes the transaction information.

6. 2. The server terminal according to claim 1, wherein the slip information further includes the order type information.

7. 2. A server terminal according to claim 1, wherein the slip information includes link information for directing the user to a web page that provides a questionnaire related to the order details, the service, and / or the restaurant.

8. 2. The server terminal according to claim 1, wherein the slip information further includes the user information.

Images