JP2022136369A - server terminal - Google Patents

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

There is an application for exception to loss of novelty

The present invention relates to a server terminal that collects and manages orders from multiple ordering platforms.

Traditionally, in the food and beverage industry, the form of service provision has diversified, including eat-in, delivery and takeout, and users have requested using their own ordering apps (e.g., Uber Eats (registered trademark) and Demae-can (registered trademark). Ordering food and drinks from restaurants is spreading and becoming established.

For example, a reservation order processing system capable of reliably processing reservation orders is disclosed (Patent Document 1).

Japanese Patent Application Laid-Open No. 2020-201804

However, although Patent Literature 1 discloses a technology capable of timely processing in-store orders and pre-orders and outputting cooking instruction slips, it does not deal with processing multiple order forms for the same store. Although disclosed, it does not correspond to orders from multiple ordering platforms.

Accordingly, it is an object of the present invention to implement a method of aggregating and managing orders from multiple order platforms.

A server terminal according to one aspect of the present invention, comprising: an order receiving unit that receives order information from one or a plurality of take-out or delivery service terminals; and generates slip information based on the order information. A server terminal having a slip generation unit and an information transmission unit that transmits the slip information to a store terminal related to a restaurant, wherein the order information includes user information related to the ordering user, order details and quantity. menu information related to the service terminal, service identification information identifying the service related to the service terminal, and order type information related to the type of delivery or takeout, and the slip information includes at least menu information and service identification information .

According to the present invention, a method of aggregating and managing orders from multiple ordering platforms can be implemented.

1 is a block configuration diagram showing an order management system according to a first embodiment of the present invention; FIG. 2 is a functional block configuration diagram showing a server terminal 100 of FIG. 1; FIG. 2 is a functional block configuration diagram showing a store terminal 300 of FIG. 1; FIG. 4 is a schematic diagram showing an example of service information stored in the server 100; FIG. 4 is a schematic diagram showing an example of order information stored in the server 100; FIG. 4 is a schematic diagram showing an example of slip information stored in the server 100; FIG. 4 is an example of a flowchart relating to an order management method executed in the server terminal 100 according to the first embodiment of the present invention; 3 is an example of a flowchart relating to a slip management method executed in the store terminal 300 according to the first embodiment of the present invention. It is an example of an order management screen displayed on the store terminal 300 according to the first embodiment of the present invention. It is an example of a slip output in the store terminal 300 according to the first embodiment of the present invention.

BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, embodiments of the present invention will be described with reference to the drawings. It should be noted that the embodiments described below do not unduly limit the content of the present disclosure described in the claims. Also, not all the components shown in the embodiments are essential components of the present disclosure.

(Embodiment 1)
<Configuration>
FIG. 1 is a block configuration diagram showing an order management system according to the first embodiment of the invention. This operation system 1 accepts take-out and/or delivery orders from restaurants (associated with store terminals 300A and 300B) from user terminals 400A and 400B (hereinafter collectively referred to as "user terminals 400"). Service terminals 200A and 200B (hereinafter collectively referred to as "service terminals 200") that operate an order platform, a server terminal 100 that receives orders from the service terminals 200 and collectively manages them, It has store terminals 300A and 300B (hereinafter, collectively referred to as "store terminals 300") that accept orders.

The server terminal 100, the service terminal 200 and the store terminal 300 are connected via a network NW. The network NW includes the Internet, an intranet, a wireless LAN (Local Area Network), a WAN (Wide Area Network), and the like.

The server terminal 100, the service terminal 200, and the store terminal 300 may be general-purpose computers such as workstations and personal computers, or may be logically realized by cloud computing. . In the present embodiment, one server terminal is exemplified for convenience of explanation, but the present invention is not limited to this, and a plurality of server terminals may be used. In particular, store terminal 300 may be configured as a POS terminal in addition to the above.

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

In this embodiment, the system 1 has a server terminal 100, a service terminal 200, and a store terminal 300, and each user of the service terminal 200 and the store terminal 300 uses each terminal to access the server terminal 100. Although described as a configuration for performing an operation, the server terminal 100 may be configured as a stand-alone, and the server terminal itself may be provided with a function for each user to perform an operation.

FIG. 2 is a functional block configuration diagram of the server terminal 100 of FIG. The server terminal 100 includes a communication section 110 , a storage section 120 and a control section 130 .

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

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

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), and the like. be done. As the functions of the control unit 130, an order information reception 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 information transmission to the service terminal 200 or the store terminal 300. and an information transmission unit 133 that transmits the The order information reception unit 131, the slip information generation unit 132, and the information transmission unit 133 are activated by a program stored in the storage unit 120 and executed by the server terminal 100, which is a computer (electronic computer).

The order information receiving unit 131 receives the order information from the service terminal 200 when the user terminal 400 places an order for a menu or the like for a restaurant via an application provided by the service provider of the service terminal 200. Received via unit 110 .

The slip information generation unit 132 performs processing for generating slip information based on the received order information.

The information transmission unit 133 performs processing for transmitting order information and slip information to the store terminal 300 .

FIG. 3 is a functional block configuration diagram showing the store terminal 300 of FIG. The store terminal 300 includes a communication section 310 , a display operation section 320 , a storage section 330 and a control section 340 .

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.

The display operation unit 320 is a user interface used by the owner to input instructions and display text, images, etc. according to input data from the control unit 340. The store terminal 300 is configured by a personal computer. When the store terminal 300 is a tablet terminal, it is composed of a display, a keyboard, and a mouse. The display operation unit 320 is activated by a control program stored in the storage unit 330 and executed by the store terminal 300, which is a computer (electronic calculator).

The storage unit 330 stores programs for executing various control processes and functions in the control unit 340, order information, slip information, input data, and the like, and is composed of RAM, ROM, and the like. Further, the storage unit 330 temporarily stores communication contents with the server terminal 100 .

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

Also, the store terminal 300 is connected to an output device 500 such as a printer that outputs a slip based on the slip information via a wired or wireless network.

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

The service information 1000 shown in FIG. 4 stores various data related to service providers of service terminals. FIG. 4 shows an example of one service provider (the provider identified by the service ID "10001") for convenience of explanation, but information of a plurality of service providers can be stored. Various data related to the service provider, for example, basic information of the service operated by the service provider (service name, business name, address, contact information, etc.), order information received from the service provider (order user information, order menu information, order type information, accounting information, status information, etc.), but is not limited to this.

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

The order information 2000 shown in FIG. 5 stores various data related to menu orders received from the service terminal 200 . FIG. 5 shows an example of one order (order identified by order ID "20001") for convenience of explanation, but information on a plurality of orders can be stored. Various data related to an order include, for example, information on the service that received the order, information on the ordering user, information on the store where the order was placed (store name, address, contact information, etc.), information on the order menu (order content, quantity, toppings, cutlery information, etc.), order type information (delivery, takeout, eat-in, etc.), accounting information (accounting amount, accounting completed/uncompleted, payment method), order status information (preparing (cooking) ), has been picked up, is being delivered, has been delivered, etc.), but is not limited to this.

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

The slip information 3000 shown in FIG. 6 stores slip information related to slips generated based on order information and output via the store terminal 300 . For convenience of explanation, FIG. 6 shows an example of slip information associated with one slip (the slip identified by the slip ID "30001"), but information on a plurality of slips can be stored. As the slip information 3000, for example, for the slip identified by the slip ID "30001", information on the service for which the order was received, information on the order menu (order details, quantity, toppings, information on cutlery, etc.), and information on the type of order. (type of delivery, takeout, eat-in, etc.), accounting information (accounting amount, accounting completed/uncompleted, payment method), order status information (preparing (cooking), picked up, etc.) It is possible, but not limited to this.

<Process flow>
The flow of processing of the order management method executed by the system 1 of this embodiment will be described with reference to FIG. FIG. 7 is an example of a flow chart relating to the order management method according to the first embodiment of the present invention.

Here, in order to use this system 1, the service provider and the store operator access the server terminal 100 using the Internet browsers of the service terminal 200 and the store terminal 300, and the server terminal 100 operates the Register for services as a service provider or store operator through a prescribed procedure for services. The service provider can use the service by receiving authentication information such as an ID and a password and logging in to the service through the service terminal 200 after being authenticated. 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.

First, as the process of step S<b>101 , the information reception unit 131 of the control unit 130 of the server terminal 100 receives menu order information from the service terminal 200 . For example, as the contents included in the order information, as shown in the information included in the order management screen displayed on the store terminal 300 in FIG. Information about the ordering user (e.g. "K Ichiro", information about the store where the order was placed (e.g. "ABC Curry"), information about the order menu (e.g. "chicken curry", quantity (one), toppings (fukujinzuke, sauce ), taste (medium spicy)), accounting information (for example, accounting amount “1140 yen”), order status information (for example, “preparing”), etc., but are not limited thereto. , the received order information is stored in the service information storage unit 121 and the order information storage unit 122 of the storage unit 120, respectively.

Subsequently, as the process of 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, as slip information, the information included in the slip output from the store terminal in FIG. information (e.g., service provider name "OVER EATS" or service ID), information about order menu (e.g., "chicken curry", quantity (one), toppings (fukujinzuke, sauce), taste (medium spicy), etc.) , order type information (delivery, take-out, eat-in, etc.), accounting information (for example, accounting amount "1140 yen"), and the like, but are not limited to these. The slip information generation unit 132 stores the generated slip information in the slip information storage unit 123 of the storage unit 120 .

Subsequently, as the process of step S103, the information transmission 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.

FIG. 8 is an example of a flowchart relating to the slip management method executed in the store terminal 300 according to the first embodiment of the present invention.

First, as the process of 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 order information displayed on the user interface screen of the store terminal 300. As shown in FIG. Order information includes information that identifies delivery/takeout order service providers, and stores can centrally manage user orders via multiple service providers (order platforms) using a single order management application. can be confirmed. In addition, although not shown, it is also possible to display the order type such as delivery or take-out. etc. can be identified, order management can be easily performed.

Subsequently, as the process of step S202, the control unit 340 of the store terminal 300 displays the received order information via the display operation unit 320 and/or sends the slip information to the output device 500 such as a printer as a paper medium. output as FIG. 10 shows a slip printed from the output device 500 connected to the shop terminal 300. As shown in FIG. Information that identifies one of a plurality of service providers (order platforms) is printed on the slip, and although not shown, it is also possible to print the order type such as delivery or takeout, etc. In addition, delivery and take-out customers can immediately grasp the contents of the order by looking at the slip and collect the provided food and drink.

Although the disclosed embodiments have been described above, they can be implemented in various other forms, and can be implemented with various omissions, substitutions, and modifications. These embodiments, modifications, omissions, substitutions and modifications are included within the technical scope of the claims and their equivalents.

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 (5)

an order reception unit that receives order information from one or more takeout or delivery service terminals;
a slip generation unit that generates slip information based on the order information;
A server terminal having an information transmission unit that transmits the slip information to a store terminal related to a restaurant,
The order information includes user information related to the ordering user, menu information related to order details and quantity, service identification information identifying services related to the service terminal, and order type information related to the type of delivery or takeout. including
The server terminal, wherein the slip information includes at least menu information and service identification information. 2. The server terminal according to claim 1, wherein said order information further includes accounting information related to whether or not an ordering user has completed accounting, and said slip information includes said accounting information. 2. The server terminal according to claim 1, wherein said slip information further includes said order type information. 2. The server terminal according to claim 1, wherein said slip information includes link information for guiding to a web page providing questionnaires related to said order details, said service and/or said eating and drinking establishment. . 2. The server terminal according to claim 1, wherein said slip information further includes said user information.

Images