System, store terminal, and program

Abstract

To provide a reminder pertaining to a product pick up in a favorable manner.SOLUTION: A system comprises display means, reminding means, and acquisition means. The display means displays a product to be purchased by a customer. The reminding means reminds a customer terminal held by the customer to pick up the product. The display means displays a confirmation screen regarding whether or not a reminder is necessary before the reminder is performed by the reminding means. The acquisition means acquires pick-up information indicating that the product is to be picked up. The display means displays the confirmation screen if a first prescribed time has elapsed without the pick-up information being acquired by the acquisition means since the product becomes available for being picked up.SELECTED DRAWING: Figure 6

Description

Technical Field

[0001] The present invention relates to a system, a store terminal, and a program.

Background Art

[0002] In recent years, in restaurants such as fast food restaurants, it has become popular for customers to place orders from the mobile terminals they carry and pick up the products when they visit the store. In addition, various techniques for prompting customers regarding the pickup of products have been proposed. For example, a technique for giving a privilege related to delivery to customers has been proposed (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, in the prior art, there has been a problem that a customer who has already picked up a product may be prompted regarding the pickup, that is, the prompting may not be performed appropriately.

[0005] The present invention has been made in view of such circumstances, and an object thereof is to provide a technique capable of appropriately performing a prompt regarding the pickup of a product.

Means for Solving the Problems

[0006] In order to solve the above-described problems, a system according to an aspect of the present invention includes display means for displaying a product to be purchased by a customer, and urging means for urging the customer to pick up the product with respect to a customer terminal possessed by the customer. The display means displays a confirmation screen regarding the necessity of the urging before the urging is performed by the urging means. A system characterized by this.

[0007] In order to solve the above-described problems, a store terminal according to another aspect of the present invention includes display means for displaying a product to be purchased by a customer. The display means displays a confirmation screen regarding the necessity of the urging before the customer is urged to pick up the product with respect to a customer terminal possessed by the customer. A store terminal characterized by this.

[0008] In order to solve the above-described problems, a program according to another aspect of the present invention is a program that causes a computer to function as a store terminal. The computer functions as display means for displaying a product to be purchased by a customer. The display means displays a confirmation screen regarding the necessity of the urging before the customer is urged to pick up the product with respect to a customer terminal possessed by the customer. A program characterized by this.

Brief Description of the Drawings

[0009]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Mode for Carrying Out the Invention

[0010] (Embodiment) (Configuration Example of Goods Delivery System St) FIG. 1 is an explanatory diagram showing a configuration example of a goods delivery system St according to an embodiment. The goods delivery system St is introduced, for example, in a food and beverage store. The food and beverage store is, for example, a fast food restaurant or a food court. Also, the goods handled in the food and beverage store related to the goods delivery system St include eat-in goods and takeout goods. Note that the store where the goods delivery system St is introduced is not limited to a food and beverage store. The store may be, for example, any store that delivers reserved goods, such as a supermarket, a home center, a convenience store, various supply stores, etc.

[0011] In FIG. 1, the goods delivery system St includes a management server 1, a store controller 10, a registration settlement device 20, a kitchen terminal 30, a call display 40, and a customer terminal 50. Inside the store, the store controller 10, the registration settlement device 20, the kitchen terminal 30, and the call display 40 are arranged.

[0012] Each device included in the goods delivery system St is communicably connected via a network 60 such as a LAN (Local Area Network), WAN (Wide Area Network), or the Internet. Each device is a computer device equipped with a CPU (Central Processing Unit), ROM (Read Only Memory), RAM (Random Access Memory), a communication unit, and the like.

[0013] The order forms for goods in the goods delivery system St include an online order form in which an order is placed using the customer terminal 50 and an offline order form in which an order is placed using the registration settlement device 20 in the store.

[0014] The management server 1 manages various types of information such as information about customers, information about stores, and information about goods for each store (product master). The management server 1 stores (registers) the goods ordered online and the goods ordered online. The management server 1 is provided with a delivery management DB2. The delivery management DB2 stores delivery management information related to the delivery of goods. The management server 1 may be placed inside the store or outside the store.

[0015] The store controller 10 stores various types of information necessary for transactions. The various types of information include the product master. The product master is a file that stores product information such as product identification information (e.g., JAN (Japanese Article Number) code), product name, and selling price for each product. Also, the product master includes product identification information, product name, unit price of the products subject to measurement (products subject to measurement) for products that require measurement. In addition to the product master, the store controller 10 also stores various types of information such as inventory status, sales history, and deposit and withdrawal records. The store controller 10 may also store customer membership information.

[0016] The registration and settlement device 20 accepts offline orders. In an offline order, a store clerk accepts an order from a customer at the store, and in response to the clerk's operation, product registration processing and product settlement processing are performed. Note that the registration and settlement device 20 may be of the self-service type. In the self-service type, registration processing and settlement processing are performed by the customer's operation. Note that in the self-service type, registration processing may be performed by the clerk's operation and settlement processing may be performed by the customer's operation. Also, in the product delivery system St, a ticket vending device may be used instead of or in addition to the registration and settlement device 20. The ticket vending device is a device that accepts an operation from a customer, performs product registration processing and settlement processing, and issues a food ticket.

[0017] When the settlement is completed, the registration and settlement device 20 issues a receipt (paper receipt). The receipt is printed with a pickup code and a transaction number as identification information for delivery. The pickup code is represented by, for example, a two-dimensional code. The pickup code includes, for example, an order number.

[0018] The customer terminal 50 is a terminal device that accepts online orders. The customer terminal 50 is a portable terminal device held by the customer, such as a smartphone or a tablet terminal. A predetermined application program (hereinafter referred to as the "order app") is installed in the customer terminal 50. When the order app is launched, the customer terminal 50 can communicate with the management server 1 via the network 60 and perform product registration and settlement. The settlement type in the settlement is, for example, the settlement type of a credit card.

[0019] When the online payment is completed, the customer terminal 50 can display a pickup code and a transaction number. In an online order, settlement at the store may be enabled. In this case, the customer terminal 50 can display a settlement code (a code for identifying a transaction) for settlement. When the registration settlement device 20 reads the settlement code displayed on the customer terminal 50, it can inquire about the transaction to the management server 1 based on the read settlement code and perform the settlement process. When the settlement is completed, the customer terminal 50 may be able to display the pickup code based on an instruction from the management server 1.

[0020] In addition, the customer terminal 50 is not limited to receiving operations related to online orders using an order app, and can also receive operations related to online orders using a web browser. Also, the online order may be placed by a non-portable customer terminal 50 such as a desktop personal computer. Also, when an online order is placed by a non-portable customer terminal 50, the pickup code may be printed on a paper medium or the like.

[0021] The kitchen terminal 30 is arranged, for example, in the kitchen and includes a kitchen monitor and a printing unit. The kitchen terminal 30 outputs various information, for example, in response to a cooking instruction from the management server 1. Also, the kitchen terminal 30 includes an operation unit for receiving that the cooking is completed. When the operation unit is pressed, the kitchen terminal 30 transmits information indicating that the cooking is completed to other devices (for example, the registration settlement device 20 and the call display 40) via the management server 1.

[0022] The calling display 40 is arranged at a position where it can be visually recognized by customers in the store. The calling display 40 displays the order number indicating the product for which cooking has been completed. When the customer sees the order number of the ordered product displayed on the calling display 40, the customer goes to a predetermined delivery counter to pick up the product. At this time, the reading unit (scanner or camera) provided in the registration settlement device 20 reads the pickup code printed on the receipt or the pickup code displayed on the customer terminal 50 according to the operation of the store clerk or the customer. When the registration settlement device 20 reads the pickup code, it transmits the reading result of the pickup code (information indicating that the pickup of the product indicated by the order number has been completed) to the management server 1. When the management server 1 receives the reading result, it performs a cancellation process to complete the transaction.

[0023] Note that, for example, in the case of a self-type registration settlement device 20, the product delivery system St may include a transaction status management device. The transaction status management device displays the processing status of the registration settlement device 20 and controls the registration settlement device 20. For example, a store clerk (monitoring store clerk) is arranged at the transaction status management device, and the registration settlement device 20 is monitored by the monitoring store clerk. The status of the registration settlement device 20 is displayed on the transaction status management device. The monitoring store clerk supports the customer operating the registration settlement device 20 and performs age confirmation when an age confirmation product is registered in the registration settlement device 20.

[0024] (Hardware Configuration of Computer Devices) FIG. 2 is a block diagram showing the hardware configuration of the computer of each device included in the product delivery system St. The computer 200 is implemented in the management server 1, the store controller 10, the registration settlement device 20, the kitchen terminal 30, the calling display 40, and the customer terminal 50, respectively.

[0025] The computer 200 includes a processor 201, a main memory 202, a storage 203, and an interface 204. The processor 201 reads out various programs stored in the storage 203, expands them in the main memory 202, and executes processing according to the programs. Further, the processor 201 secures a storage area in the main memory 202 according to the programs. Examples of the processor 201 include a CPU (Central Processing Unit), a GPU (Graphic Processing Unit), and a microprocessor.

[0026] The storage 203 includes, for example, a magnetic disk, a magneto-optical disk, an optical disk, and a semiconductor memory. The storage 203 may be an internal medium directly connected to the bus of the computer 200, or may be an external medium connected to the computer 200 via the interface 204 or a communication line. Further, when this program is distributed to the computer 200 via a communication line, the computer 200 that has received the distribution may expand the program in the main memory 202 and execute the processing.

[0027] For the store controller 10, the registration settlement device 20, the kitchen terminal 30, the call display 40, and the customer terminal 50, an input device and an output device are connected to the computer 200 via the interface 204. The input device includes, for example, a scanner, a camera, a touch panel, operation buttons, a microphone, etc. In the case of the customer terminal 50, the input device includes a GPS (Global Positioning System) unit. The output device includes, for example, a display, a printer, a speaker, etc.

[0028] (Processing from product registration to product delivery) FIG. 3 is a sequence diagram showing an example of the process from the registration of a product to the delivery of the product performed by the product delivery system St. In FIG. 3, the flow from when a certain customer places an order (online order or offline order) until the delivery of the product is completed will be described.

[0029] Step S301: The customer terminal 50 activates the order application according to the customer's operation and receives an online order. When the registration of the product is confirmed in the online order, the customer terminal 50 transmits the order details indicating the registered product to the management server 1.

[0030] Step S302: The registration and settlement device 20 receives an offline order according to the clerk's operation. Step S303: When the settlement for the offline order is completed, the registration and settlement device 20 issues a receipt. The receipt is printed with a pickup code and a transaction number. Also, when the settlement is confirmed, the registration and settlement device 20 transmits the order details indicating the product registered in the offline order to the management server 1.

[0031] Step S304: When the management server 1 receives the order details from the registration and settlement device 20 or the customer terminal 50, it stores the order details. Also, when the management server 1 stores the order details, it transmits the order details received from the customer terminal 50 to the registration and settlement device 20. Further, the management server 1 transmits the order details to the kitchen terminal 30.

[0032] Step S305: The registration and settlement device 20 displays the product indicated by the order details on the display based on the order details received from the management server 1 and the order details indicating the product registered in its own device.

[0033] Step S306: The kitchen terminal 30 outputs an instruction related to the start of cooking the product indicated by the order details to the kitchen display and the kitchen printer. Step S307: When the cooking is completed, the kitchen terminal 30 receives an operation indicating the completion of cooking from the cooking staff. When receiving the completion of cooking for all the products included in the order content, the kitchen terminal 30 sends a cooking completion notice including the order number to the management server 1.

[0034] Step S308: When the management server 1 receives the cooking completion notice from the kitchen terminal 30, it performs registration (cooking completion registration) indicating that the cooking for the product has been completed. Also, the management server 1 gives a display instruction of the order number identifying the product to the calling display 40.

[0035] Step S309: When the calling display 40 receives the display instruction of the order number from the management server 1, it displays the order number. Note that the calling display 40 is not limited to receiving the display instruction of the order number from the management server 1, and may directly receive the display instruction of the order number from the kitchen terminal 30.

[0036] Also, when the management server 1 receives the cooking completion notice from the kitchen terminal 30, it may send information indicating that to the customer terminal 50. In this case, the customer terminal 50 may notify the customer that the cooking has been completed.

[0037] In the store, the customer waits until the order number of the product they ordered is displayed on the calling display 40. When the order number of the product they ordered is displayed on the calling display 40, the customer goes to the delivery counter.

[0038] Step S310: If it is an online order, when the order number of the product they ordered is displayed on the calling display 40, the customer causes the customer terminal 50 to display the pickup code. Step S311: The registration and settlement device 20 reads the pickup code displayed on the receipt or the customer terminal 50. When the registration and settlement device 20 reads the pickup code, it sends the reading result of the pickup code to the management server 1.

[0039] Step S312: When the management server 1 receives the reading result of the collection code, it performs a cancellation process indicating the completion of the transaction for the order. Then, the management server 1 gives an instruction to delete the order number to the call display 40.

[0040] Step S313: When the call display 40 receives an instruction to delete the order number from the management server 1, it deletes the order number from the call display 40. Note that the call display 40 is not limited to receiving an instruction to delete the order number from the management server 1, and may directly receive an instruction to delete the order number from the registration settlement device 20.

[0041] Here, when the customer does not come to pick up the product, if a predetermined time has elapsed since the completion of cooking registration (step S308), the management server 1 can urge the customer terminal 50 to pick up the product. However, there has been a case where a customer who has already picked up the product has been urged to pick up the product.

[0042] Specifically, as shown in step S311 and step S312, when the customer comes to pick up the product, the clerk reads the collection code, and as a result, the cancellation process is performed for the product. However, even though the product has been delivered to the customer, if the clerk forgets to read the collection code, the cancellation process will not be performed. As a result, if a predetermined time has elapsed since the completion of cooking registration, the customer terminal 50 will be urged to pick up the product.

[0043] Such a reminder is not only an unnecessary notice to the customer, but there is also a risk that a malicious customer may go to the delivery counter again and try to receive another product, which may trigger an illegal act or cause trouble between the store and the customer. Thus, there has been a case where the reminder for picking up the product cannot be appropriately performed. Therefore, in this embodiment, the reminder for picking up the product is appropriately performed. Hereinafter, with reference to FIG. 4, the functional configuration of the product delivery system St according to this embodiment will be described.

[0044] (Functional Configuration of the Goods Delivery System St) Next, the functional configuration of the goods delivery system St according to this embodiment will be described. FIG. 4 is an explanatory diagram showing an example of the functional configuration of the goods delivery system St. Hereinafter, an example of prompting for pickup regarding goods ordered online will be described.

[0045] As shown in FIG. 4, the registration settlement device 20 includes functional units such as a display unit 401 (an example of display means), an acquisition unit 402 (an example of acquisition means), a reception unit 403 (an example of reception means and non-prompting reception means), and a settlement unit 404. Each functional unit is realized by a processor 201 (FIG. 2) provided in the registration settlement device 20. That is, by the processor 201 provided in the registration settlement device 20 executing the goods delivery program according to this embodiment, each functional unit is realized.

[0046] The management server 1 includes a prompting unit 411 and a write-off unit (an example of write-off means) (not shown). The prompting unit 411 and the write-off unit are realized by a processor 201 (FIG. 2) provided in the management server 1. That is, by the processor 201 provided in the management server 1 executing the goods delivery program according to this embodiment, the prompting unit 411 and the write-off unit are realized.

[0047] The customer terminal 50 includes a notification unit 421 and a transmission unit 422. Each functional unit is realized by a processor 201 (FIG. 2) provided in the customer terminal 50. That is, by the processor 201 provided in the customer terminal 50 executing the goods delivery program according to this embodiment, the notification unit 421 and the transmission unit 422 are realized.

[0048] The display unit 401 displays the goods purchased by the customer. Specifically, the goods purchased by the customer include the goods received by online order and the goods received by offline order. In the case of an online order, the registration settlement device 20 receives the order content from the management server 1. The display unit 401 displays the goods purchased by the customer based on the order content received from the management server 1.

[0049] In the case of an offline order, the display unit 401 displays the products registered in the device as the products to be purchased by the customer. Note that the display unit 401 is not limited to being provided in the registration settlement device 20, and may be provided in a dedicated display device (for example, a tablet terminal).

[0050] (Reminder for pickup to the customer terminal 50) The reminder unit 411 issues a reminder (hereinafter referred to as "pickup reminder") indicating the pickup of the product to the customer terminal 50. The pickup reminder is to send an instruction to cause the customer terminal 50 to send a notice prompting pickup. In the case of an online order, when a predetermined time has elapsed after the cooking is completed and the customer has not come to pick up the product, the reminder unit 411 issues a pickup reminder to the customer terminal 50.

[0051] When the pickup reminder is issued by the reminder unit 411, the notification unit 421 of the customer terminal 50 issues a notice prompting pickup (hereinafter referred to as "pickup notice"). The pickup notice is, for example, a notice such as "Please come to pick up the product." The pickup notice is issued by display or voice (see Fig. 7).

[0052] (Regarding acquisition of pickup code reading result) The acquisition unit 402 acquires pickup information indicating that the product is to be picked up. The pickup information is, for example, the reading result of the pickup code. Specifically, the acquisition unit 402 acquires the reading result from the reading unit (scanner or camera) provided in the registration settlement device 20 when the reading unit reads the pickup code.

[0053] (Display of reminder confirmation screen for store clerks) The display unit 401 displays a confirmation screen regarding the necessity of pick-up urging (hereinafter referred to as the "urging confirmation screen") before the pick-up urging is performed by the urging unit 411. Specifically, when the pick-up code reading result is not acquired by the acquisition unit 402 within the first predetermined time (for example, 15 minutes) after the pick-up of the product becomes possible, the display unit 401 displays the urging confirmation screen. For example, when a predetermined time (urging confirmation time (FIG. 5)) arrives, the display unit 401 causes the urging confirmation screen to be displayed on a display (for example, the display on the clerk side).

[0054] The display unit 401 displays the urging confirmation screen based on the display instruction of the urging unit 411. The urging unit 411 may transmit the display instruction at the timing of the urging confirmation time, or may transmit timer information indicating the urging confirmation time at the timing of the time when cooking is completed (cooking completion registration time (FIG. 5)).

[0055] (Regarding accepting the necessity of urging) The reception unit 403 accepts a pick-up urging request on the urging confirmation screen. When the reception unit 403 accepts the pick-up urging request, it transmits an urging request indicating that fact to the urging unit 411. When the urging unit 411 receives the urging request, it performs pick-up urging on the customer terminal 50. Also, when the second predetermined time (for example, 10 minutes) has elapsed without the pick-up urging request being accepted by the reception unit 403 from the display of the urging confirmation screen, the urging unit 411 forcibly performs pick-up urging.

[0056] (An example of the delivery management information stored in the delivery management DB2) Here, an example of the delivery management information stored in the delivery management DB2 provided in the management server 1 will be described. FIG. 5 is a diagram showing an example of the delivery management information stored in the delivery management DB2. As shown in FIG. 5, the delivery management DB includes items such as an order number, an order mode, terminal identification information, a cooking completion registration time, an urging confirmation time, a forced urging time, an urging execution time, a pick-up time, and a cancellation flag. When information is input to each item, the delivery management information is stored as a record.

[0057] The order number is identification information assigned to each order, regardless of whether it is an online order or an offline order, and is used to identify each order. The order mode indicates either an offline order, which is an in-store order (product registration by the registration settlement device 20), or an online order, which is an out-of-store order (product registration by the customer terminal 50). The terminal identification information is identification information indicating the destination of the customer terminal 50. The terminal identification information may be, for example, an app ID, a phone number, or an email address. The cooking completion registration time indicates the time when cooking is completed. Specifically, it indicates the time when cooking completion registration (step S308 in FIG. 3) is performed.

[0058] The reminder confirmation time is the time when the reminder confirmation screen 610 (FIG. 6) is displayed on the registration settlement device 20. The reminder confirmation time is the time when a first predetermined time (for example, 15 minutes) has elapsed since the cooking completion registration time. The forced reminder time indicates the time when product pickup reminder is forcibly performed on the reminder confirmation screen 610. The forced reminder time is the time when a second predetermined time (for example, 10 minutes) has elapsed since the reminder confirmation time.

[0059] The reminder execution time indicates the time when a pickup reminder is made to the customer terminal 50. Note that the reminder execution time may be the time when the request button 612 (FIG. 6) is pressed. Also, the time when the request button 612 is pressed may be separately stored in the delivery management DB2.

[0060] The pickup time indicates the time when the product is picked up. Specifically, the pickup time indicates the time when the pickup code reading result is received from the registration settlement device 20 when the pickup code is read by the registration settlement device 20.

[0061] The write-off flag is a flag indicating that the transaction has been completed (the write-off has been completed). The write-off flag is set to on upon receipt of the reading result. If the customer picks up the product immediately after cooking is completed, that is, if the write-off flag is set to on before the reminder confirmation time, the display of the reminder confirmation screen and the pickup reminder are not performed.

[0062] (An example of the reminder confirmation screen displayed on the registration settlement device 20) FIG. 6 is a diagram showing an example of the reminder confirmation screen displayed on the registration settlement device 20. As shown in FIG. 6, a reminder confirmation screen 610 is displayed on the clerk-side display 600 of the registration settlement device 20. The reminder confirmation screen 610 is a confirmation screen regarding the necessity of the pickup reminder and at the same time is a screen for receiving a reminder request.

[0063] The reminder confirmation screen 610 includes an elapsed time 611, a request button 612, and a non-request button 613. The elapsed time 611 indicates the elapsed time since the reminder confirmation screen 610 was displayed. The request button 612 is a button for receiving a pickup reminder request. The non-request button 613 is a button for receiving the acceptance of not requesting a pickup reminder.

[0064] When the reminder confirmation screen 610 is displayed, the clerk visually checks whether the target product has been delivered to the customer by checking the product on the delivery counter and the slip attached to the product. If it is determined as a result of the visual check that the pickup has not been made, the clerk presses the request button 612. Thereby, a pickup reminder is issued to the customer terminal 50 of the customer.

[0065] Note that the pickup reminder may be performed in addition to the case where the request button 612 is pressed. Specifically, the pickup reminder is also performed when the elapsed time 611 indicates a second predetermined time (for example, 10 minutes) without pressing either the request button 612 or the non-request button 613.

[0066] On the other hand, if it is determined that the pickup has been completed as a result of the visual confirmation related to the delivery, that is, if the reminder confirmation screen 610 is displayed because the reading of the pickup code has been forgotten, the store clerk presses the non-request button 613. When the non-request button 613 is pressed, the registration settlement device 20 transmits pickup-completed information indicating that the pickup of the item has been completed to the management server 1. When the management server 1 (write-off section) receives the pickup-completed information, it performs a write-off process for the item. This can reduce the effort of separately launching a screen for the write-off process and performing a write-off operation for the item.

[0067] Also, it is assumed that there may be a situation where the store clerk cannot immediately determine whether the pickup has been completed and the registration settlement device 20 has to deal with other customers. Specifically, it is assumed that there may be a situation where the clerk wants to end the reminder confirmation screen 610 and display the item registration screen. In this case, the store clerk will press the non-request button 613 on the reminder confirmation screen 610.

[0068] In other words, as another condition for pressing the non-request button 613, there may be a case where it is not possible to determine on the spot whether the pickup has been completed and the clerk wants to cancel the reminder confirmation screen 610 to start the registration procedure for the customer in front. In this case, it is necessary to confirm the pickup of the item again (at another timing). Therefore, control is required not to transmit the pickup-completed information to the management server 1 at the timing when the non-request button 613 is pressed. Assuming such a case, when the non-request button 613 is pressed, the registration settlement device 20 displays a selection screen that accepts either one of, for example, "treat the item as picked up" and "hold".

[0069] When "To be put on hold" is selected on the selection screen, the registration settlement device 20 does not execute the immediate write-off process and instead displays a reminder confirmation screen 610 at a separate timing. The separate timing may be the timing when a predetermined time has elapsed (automatic timing) or the timing when a predetermined redisplay button is pressed (manual timing). Also, when "Already picked up for this product" is selected on the selection screen, the registration settlement device 20 may execute the immediate write-off process.

[0070] Note that the reminder confirmation screen 610 is not necessarily displayed across the entire screen of the display 600. The reminder confirmation screen 610 may be displayed in a partial area of the display 600. Also, the reminder confirmation screen 610 may be displayed for each transaction. In the case of multiple transactions, the reminder confirmation screen 610 may be displayed on each of the screens divided by transaction on the display 600.

[0071] (Settlement section 404) The settlement section 404 performs settlement based on the registered products. After the settlement by the settlement section 404 is completed, the display section 401 enables the display of the reminder confirmation screen 610. In other words, while the settlement is being performed by the settlement section 404, the display section 401 does not display the reminder confirmation screen 610. Note that in this embodiment, the registration settlement device 20 includes a registration section for registering products. Even while products are being registered by the product registration section, the display section 401 does not display the reminder confirmation screen 610.

[0072] (An example of a pick-up notice displayed on the customer terminal 50) FIG. 7 is a diagram showing an example of a pickup notice displayed on the customer terminal 50. As shown in FIG. 7, a pickup notice screen 710 is displayed on the display 700 of the customer terminal 50. The pickup notice screen 710 includes a pickup notice 711, a pickup confirmation button 712, a confirmation notice 713, and a picked-up button 714. The pickup notice 711 indicates a notice prompting the pickup of the product. The pickup confirmation button 712 accepts the intention to go for pickup. When the pickup confirmation button 712 is pressed, the customer terminal 50 transmits that fact to the management server 1 (upper device) and closes the pickup notice screen 710.

[0073] The confirmation notice 713 indicates a notice asking whether the product has been picked up. The picked-up button 714 accepts the fact that it has been picked up. When the picked-up button 714 is pressed, the customer terminal 50 closes the pickup notice screen 710. Also, when the picked-up button 714 is pressed, the transmission unit 422 transmits picked-up information indicating that it has been picked up to the management server 1. When the management server 1 receives the picked-up information, it performs a write-off process for the product.

[0074] (Processing after cooking completion) FIG. 8 is a sequence diagram showing an example of the processing after cooking completion performed by the product delivery system St. Step S801: After the cooking of the online-ordered product is completed (after cooking completion registration), the management server 1 waits until 15 minutes (the first predetermined time) elapses without the write-off process being performed. Note that if the pickup code is read within 15 minutes after cooking completion (step S311 in FIG. 3) and the write-off process is performed (step S312 in FIG. 3), the product delivery system St does not perform the series of processes shown in FIG. 8.

[0075] Step S802: When 15 minutes (the first predetermined time) elapses without the write-off process being performed after cooking completion, the management server 1 instructs the registration and settlement device 20 to display the reminder confirmation screen 610. Step S803: When the registration and settlement device 20 receives the instruction to display the reminder confirmation screen 610 from the management server 1, it displays the reminder confirmation screen 610.

[0076] Step S804: The registration settlement device 20 determines whether the request button 612 has been pressed on the reminder confirmation screen 610. If the non-request button 613 is pressed on the reminder confirmation screen 610, the picked-up information is transmitted to the management server 1, and the process proceeds to step S811. Step S805: When the request button 612 is pressed on the reminder confirmation screen 610, the registration settlement device 20 transmits a reminder request to the management server 1.

[0077] Step S806: When the management server 1 receives a reminder request from the registration settlement device 20, it issues a pick-up reminder to the customer terminal 50. Also, after the management server 1 issues a display instruction for the reminder confirmation screen 610, if 10 minutes (the second predetermined time) elapses without either the request button 612 or the non-request button 613 being pressed, the management server 1 issues a pick-up reminder to the customer terminal 50. Specifically, if the management server 1 does not receive a reminder request or picked-up information within 10 minutes (the second predetermined time) after issuing the display instruction for the reminder confirmation screen 610, it issues a pick-up reminder to the customer terminal 50.

[0078] Step S807: When the customer terminal 50 is issued a pick-up reminder by the management server 1, it displays a pick-up notice screen 710 (Figure 7). Step S808: The customer terminal 50 determines whether the pick-up confirmation button 712 has been pressed on the pick-up notice screen 710. If the picked-up button 714 is pressed on the pick-up notice screen 710, the picked-up information is transmitted to the management server 1, and the process proceeds to the process of step S811.

[0079] Step S809: When the pick-up confirmation button 712 is pressed on the pick-up notice screen 710, the customer terminal 50 then displays a pick-up code on the display 700 according to the operation of the customer who has come to pick up the product.

[0080] Step S810: The registration settlement device 20 reads the pick-up code displayed on the customer terminal 50. When the registration settlement device 20 reads the pick-up code, it transmits the read result of the pick-up code to the management server 1. Step S811: When the management server 1 receives the reading result of the collection code, or when it receives the collected information from the registration settlement device 20 or the customer terminal 50, it performs a reconciliation process. After that, the management server 1 issues an instruction to delete the order number to the calling display 40.

[0081] (Goods delivery process performed by the management server 1) Next, with reference to FIGS. 9 and 10, the goods delivery process performed by the management server 1 will be described. FIG. 9 is a flowchart showing an example of the goods delivery process performed by the management server 1. Hereinafter, the process after an online order or an offline order is placed and cooking is started will be described.

[0082] In FIG. 9, the management server 1 determines whether it has received a cooking completion notification from the kitchen terminal 30 (step S901). The management server 1 waits until it receives a cooking completion notification from the kitchen terminal 30 (step S901: NO). When the management server 1 receives a cooking completion notification from the kitchen terminal 30 (step S901: YES), it stores each time (cooking completion registration time, reminder confirmation time, and forced reminder time) in the delivery management DB2 (step S902). Then, the management server 1 starts measuring time (step S903).

[0083] Next, the management server 1 issues a display instruction for the order number to the calling display 40 (step S904). Then, the management server 1 determines whether it has received the reading result of the collection code displayed on the receipt or the customer terminal 50 from the registration settlement device 20 (step S905). When it receives the reading result of the collection code (step S905: YES), the management server 1 stores the collection time in the delivery management DB2 (step S906).

[0084] Then, the management server 1 turns on the reconciliation flag stored in the delivery management DB2 and completes the reconciliation process (step S907). Further, the management server 1 sends an instruction to delete the order number to the calling display 40 (step S908) and ends the series of processes.

[0085] On the other hand, in step S905, when the management server 1 does not receive the reading result of the collection code (step S905: NO), the management server 1 determines whether 15 minutes (the first predetermined time) has elapsed since the start of time measurement in step S903 (step S909). If 15 minutes has not elapsed since the start of time measurement (step S909: NO), the management server 1 returns to step S905. If 15 minutes has elapsed since the start of time measurement (step S909: YES), the management server 1 performs a confirmation process (Figure 10) (step S910) and ends the series of processes.

[0086] (Confirmation process performed by the management server 1) Figure 10 is a flowchart showing an example of the confirmation process performed by the management server 1. In Figure 10, the management server 1 issues an instruction to display the reminder confirmation screen 610 (Figure 6) to the registration settlement device 20 (step S1001). Then, the management server 1 determines whether it has received a reminder request from the registration settlement device 20 when the request button 612 is pressed in the registration settlement device 20 (step S1002).

[0087] When the management server 1 does not receive a reminder request from the registration settlement device 20 (step S1002: NO), the management server 1 determines whether 10 minutes (the second predetermined time) has elapsed after sending the instruction to display the reminder confirmation screen 610 to the registration settlement device 20 (step S1003). If 10 minutes has not elapsed after sending the instruction to display the reminder confirmation screen 610 to the registration settlement device 20 (step S1003: NO), the management server 1 determines whether it has received the collected information from the registration settlement device 20 when the non-request button 613 is pressed in the registration settlement device 20 (step S1004). If it has received the collected information (step S1004: YES), the management server 1 proceeds to step S1011.

[0088] On the other hand, when the management server 1 does not receive the picked-up information (step S1004: NO), it returns to step S1002. Also, in step S1003, when 10 minutes have elapsed after sending a display instruction for the reminder confirmation screen 610 to the registration settlement device 20 (step S1003: YES), the management server 1 gives an instruction to erase the reminder confirmation screen 610 to the registration settlement device 20 (step S1005), and proceeds to step S1006.

[0089] In step S1002, when the management server 1 receives a reminder request from the registration settlement device 20 (step S1002: YES), it issues a pick-up reminder to the customer terminal 50 (step S1006). Then, the management server 1 stores the reminder execution time in the delivery management DB2 (step S1007).

[0090] Note that when the reminder request is based on the pressing of the request button 612, the time when the request button 612 is pressed is stored as the reminder execution time (for example, the delivery management information of order number 1003 in FIG. 5). On the other hand, when the reminder request is based on the elapse of 10 minutes (the second predetermined time), the same time as the forced reminder time is stored as the reminder execution time (for example, the delivery management information of order number 1004 in FIG. 5).

[0091] Next, the management server 1 determines whether it has received the reading result of the pick-up code from the registration settlement device 20 when the pick-up code is read by the registration settlement device 20 (step S1008). When the management server 1 does not receive the reading result of the pick-up code from the registration settlement device 20 (step S1008: NO), it determines whether it has received the picked-up information from the customer terminal 50 when the pick-up confirmation button 712 is pressed on the customer terminal 50 (step S1009).

[0092] When the management server 1 does not receive the picked-up information from the customer terminal 50 (step S1009: NO), it returns to step S1008. On the other hand, when the management server 1 receives the picked-up information from the customer terminal 50 (step S1009: YES), or when it receives the reading result of the pick-up code from the registration settlement device 20 (step S1008: YES), the management server 1 stores the pick-up time in the delivery management DB2 (step S1010).

[0093] Then, the management server 1 turns on the cancellation flag stored in the delivery management DB2 and completes the cancellation process (step S1011). Further, the management server 1 sends an instruction to delete the order number to the calling display 40 (step S1012) and ends the series of processes.

[0094] (Product delivery process performed by the customer terminal 50) Next, FIG. 11 is a flowchart showing an example of the product delivery process performed by the customer terminal 50. Hereinafter, the process after receiving an online order will be described. In FIG. 11, the customer terminal 50 determines whether there is a pick-up reminder from the management server 1 (step S1101). The customer terminal 50 waits until there is a pick-up reminder from the management server 1 (step S1101: NO). When the customer terminal 50 receives a pick-up reminder from the management server 1 (step S1101: YES), it displays the pick-up notification screen 710 (FIG. 7) (step S1102).

[0095] Then, the customer terminal 50 determines whether the picked-up button 714 has been pressed on the pick-up notification screen 710 (step S1103). When the picked-up button 714 has been pressed (step S1103: YES), the customer terminal 50 sends the picked-up information to the management server 1 (step S1104) and ends the series of processes.

[0096] On the other hand, when the picked-up button 714 is not pressed (step S1103: NO), the customer terminal 50 determines whether the pick-up confirmation button 712 has been pressed (step S1105). When the pick-up confirmation button 712 is not pressed (step S1105: NO), the customer terminal 50 returns to step S1103.

[0097] On the other hand, when the pick-up confirmation button 712 is pressed (step S1105: YES), the customer terminal 50 determines whether it has received an instruction to start displaying the pick-up code in response to the operation of the customer who has come to pick up the product thereafter (step S1106). The customer terminal 50 waits until it receives an instruction to start displaying the pick-up code (step S1106: NO). When it receives an instruction to start displaying the pick-up code (step S1106: YES), the customer terminal 50 displays the pick-up code (step S1107) and ends the series of processes.

[0098] (Product delivery process performed by the registration and settlement device 20) Next, FIG. 12 is a flowchart showing an example of the product delivery process performed by the registration and settlement device 20. In FIG. 12, the registration and settlement device 20 determines whether it has received an instruction to display the reminder confirmation screen 610 (FIG. 6) from the management server 1 (step S1201). The registration and settlement device 20 waits until it receives an instruction to display the reminder confirmation screen 610 from the management server 1 (step S1201: NO). When the registration and settlement device 20 receives an instruction to display the reminder confirmation screen 610 from the management server 1 (step S1201: YES), it determines whether the product is being registered (step S1202).

[0099] When the product is being registered (Step S1202: YES), the registration settlement device 20 waits as it is. When the product is not being registered (Step S1202: NO), the registration settlement device 20 determines whether it is in the settlement process (Step S1203). When it is in the settlement process (Step S1203: YES), the registration settlement device 20 waits as it is. When it is not in the settlement process (Step S1203: NO), the registration settlement device 20 displays a reminder confirmation screen 610 (Step S1204). That is, during product registration or settlement, the registration settlement device 20 does not display the reminder confirmation screen 610.

[0100] Then, the registration settlement device 20 determines whether the request button 612 has been pressed on the reminder confirmation screen 610 (Step S1205). When the request button 612 has been pressed on the reminder confirmation screen 610 (Step S1205: YES), the registration settlement device 20 sends a reminder request to the management server 1 (Step S1206) and proceeds to Step S1210.

[0101] When the request button 612 has not been pressed on the reminder confirmation screen 610 (Step S1205: NO), the registration settlement device 20 determines whether the non-request button 613 has been pressed on the reminder confirmation screen 610 (Step S1207). When the non-request button 613 has been pressed on the reminder confirmation screen 610 (Step S1207: YES), the registration settlement device 20 sends the received information to the management server 1 (Step S1208) and proceeds to Step S1210.

[0102] When the non-request button 613 has not been pressed on the reminder confirmation screen 610 (Step S1207: NO), the registration settlement device 20 determines whether it has received an instruction to delete the reminder confirmation screen 610 from the management server 1 (10 minutes have elapsed since the display of the reminder confirmation screen) (Step S1209). When it has not received an instruction to delete the reminder confirmation screen 610 (Step S1209: NO), the registration settlement device 20 returns to Step S1205.

[0103] On the other hand, in step S1209, when a deletion instruction for the reminder confirmation screen 610 is received (step S1209: YES), the registration settlement device 20 deletes the reminder confirmation screen 610 (step S1210) and ends the series of processes.

[0104] As described above, before the registration settlement device 20 according to the present embodiment performs a reminder for picking up a product, it displays a reminder confirmation screen 610 regarding the necessity of the reminder for picking up. As a result, after the clerk confirms the necessity of the reminder for picking up, the reminder for picking up can be performed. Therefore, it is possible to suppress the situation of performing a reminder for picking up for a customer who has already picked up the product. As a result, unnecessary reminders to the customer can be suppressed, so that it is possible to prevent the induction of illegal acts by the customer and to prevent the induction of troubles with the customer. Thus, a suitable reminder can be performed regarding the picking up of the product.

[0105] In addition, when the registration settlement device 20 according to the present embodiment displays the reminder confirmation screen 610 when a first predetermined time (15 minutes) has elapsed without the reading result of the picking-up code being obtained after the product can be picked up. As a result, when 15 minutes have elapsed since the product can be picked up but the picking-up has not been performed, it is possible to notify the clerk to that effect. In addition, since a reminder for picking up can be performed on the customer terminal 50, the customer can be urged to pick up.

[0106] In addition, when a second predetermined time (10 minutes) has elapsed without receiving a request for a reminder for picking up (pressing of the request button 612) from the display of the reminder confirmation screen 610, the registration settlement device 20 according to the present embodiment performs a reminder for picking up. As a result, for example, even when the clerk cannot confirm the reminder confirmation screen 610 during a busy time period and does not receive a request for a reminder for picking up from the clerk, a reminder for picking up can be performed on the customer terminal 50.

[0107] In addition, the registration settlement device 20 according to the present embodiment can display a reminder confirmation screen 610 after the settlement is completed. Therefore, the reminder confirmation screen 610 can be displayed without interfering with the operations related to the settlement. Also, the registration settlement device 20 according to the present embodiment does not display the reminder confirmation screen 610 even during the registration of products. Thus, the reminder confirmation screen 610 can be displayed without interfering with the operations related to the product registration.

[0108] In addition, the registration settlement device 20 according to the present embodiment transmits the received information to the management server 1 by accepting the instruction not to issue a reminder (non-request button 613) on the reminder confirmation screen 610. Thereby, the management server 1 can perform the cancellation process. Also, since the cancellation can be performed without separately launching a screen for the cancellation process and performing the cancellation operation for the product, the labor related to the cancellation can be reduced.

[0109] In addition, the customer terminal 50 according to the present embodiment accepts the instruction that the product has been received (received confirmation button 712) for the receipt notice 711 (FIG. 7) and transmits the received information indicating that fact to the management server 1. Thereby, the management server 1 can perform the cancellation process. Therefore, the transaction can be appropriately completed, and it is possible to suppress the occurrence of reminder for customers who have already received the product.

[0110] (Modification Example of the Embodiment) Next, a modification example of the embodiment will be described. In the following modification examples, the descriptions of the content described in the above-described embodiment will be omitted as appropriate. Also, it is possible to combine the following modification examples and the above-described embodiment respectively.

[0111] (Modification Example 1) First, Modification Example 1 will be described. In the above-described embodiment, an example of delivering a product using the receipt code displayed on the customer terminal 50 in an online order has been described. In Modification Example 1, an example of issuing a paper receipt at the store and using the paper receipt to deliver the product even in an online order will be described.

[0112] In Modification Example 1, the customer terminal 50 is capable of displaying a transaction identification code for issuing a paper receipt. When the registration settlement device 20 reads the transaction identification code displayed on the customer terminal 50, it makes an inquiry about the transaction to the management server 1 based on the read transaction identification code, acquires the transaction details, and issues a paper receipt. A collection code is printed on the paper receipt.

[0113] When the registration settlement device 20 reads the collection code printed on the paper receipt, it transmits the reading result of the collection code to the management server 1. When the management server 1 receives the reading result, it performs a cancellation process and completes the transaction.

[0114] According to Modification Example 1, a paper receipt can also be issued for online orders. Also, at the time of delivering the goods, since the store clerk performs the operation of reading the collection code printed on the paper receipt regardless of whether it is an online order or an offline order, the deterrent effect of forgetting to perform the collection code reading operation (cancellation process) can be improved. Therefore, it is possible to suppress making a collection reminder to a customer who has already picked up the goods.

[0115] (Modification Example 2) Next, Modification Example 2 will be described. In the above-described embodiment, an example of performing a collection reminder confirmation (reminder confirmation screen 610) for goods ordered online has been described. In Modification Example 2, in addition to such a configuration, an example of prompting the collection of goods ordered offline will be described.

[0116] Referring to FIG. 8, as the operation of the goods delivery system St according to Modification Example 2, the processes corresponding to steps S801 to S803 will be described. Step S801: After the cooking of the goods ordered offline is completed (after the cooking completion registration), the management server 1 waits until 15 minutes (the first predetermined time) elapses without the cancellation process. Step S802: When 15 minutes (the first predetermined time) elapses without the cancellation process being performed after the cooking of the offline-ordered product is completed, the management server 1 gives an instruction to the registration settlement device 20 to display a screen prompting the pickup of the product.

[0117] Step S803: When the registration settlement device 20 receives an instruction from the management server 1 to display a screen prompting the pickup of the product, it displays a reminder screen. The reminder screen displays the order number of the offline-ordered product and a message indicating that the pickup has not been made. As a result, the store clerk can call the order number verbally and prompt the customer to pick up the product.

[0118] According to Modification Example 2, even for offline-ordered products, the customer can be prompted to pick them up.

[0119] (Modification Example 3) Next, Modification Example 3 will be described. In the above-described embodiment, an example in which the cancellation process is performed by reading the pickup code has been described. In Modification Example 3, an example in which the cancellation process is performed by operation input instead of or in addition to such a configuration will be described.

[0120] In Modification Example 3, the registration settlement device 20 displays a list screen of products for which pickup has not been completed (unpicked-up product list screen) on the display unit 401. The registration settlement device 20 accepts a selection operation for the product to be picked up from the unpicked-up product list screen. When the operation is accepted, the registration settlement device 20 transmits pickup-completed information to the management server 1, indicating that the product has been picked up. The management server 1 (cancellation unit) may execute a cancellation process for the product when it receives the pickup-completed information from the registration settlement device 20.

[0121] The unpicked-up product list screen displays a transaction number corresponding to the product. The store clerk can search for the product by visually comparing the transaction number displayed on the customer terminal 50 or the receipt printed by the registration settlement device 20 with the transaction number displayed on the unpicked-up product list screen.

[0122] In addition, the list screen of uncollected items may be displayed on a device other than the registration settlement device 20. The other device is, for example, the kitchen terminal 30 (kitchen monitor) or the serving monitor. The serving monitor displays instructions related to serving and items to be served in the kitchen terminal 30 by receiving a cooking completion operation indicating the completion of cooking of the item. The serving monitor receives a serving completion operation indicating the completion of serving. Further, the other device may delete the item from the list by receiving a selection operation from the list screen of uncollected items in the same manner as receiving the completion operation (cooking completion operation or serving completion operation). Further, the other device may transmit collected information to the management server 1. The management server 1 (write-off section) may execute a write-off process by receiving the collected information from the other device and setting the item as having been collected.

[0123] Hereinafter, a summary of the embodiments will be described. [Title of the Invention] System, Store Terminal, and Program [Technical Field] The present invention relates to a system, a store terminal, and a program. [Background Art] In recent years, in restaurants such as fast food restaurants, it has become common for customers to place orders from a mobile terminal they possess and pick up the items when they visit the store. In addition, various techniques for prompting customers to pick up items have been proposed. For example, a technique for granting a privilege related to delivery to customers has been proposed (see, for example, Patent Document 1). [Prior Art Documents] [Patent Documents] [Patent Document 1] Japanese Unexamined Patent Application Publication No. 2016-048494 [Summary of the Invention] [Problems to be Solved by the Invention] However, in the prior art, there has been a problem that, for customers who have already picked up an item, a prompt related to the pick-up may be made, that is, the prompt may not be appropriately made. The present invention has been made in view of such circumstances, and an object thereof is to provide a technique capable of appropriately prompting customers to pick up items.

[0124] [Means for Solving the Problem] (1) To solve the above-described problems, a system according to an aspect of the present invention includes display means for displaying a product that a customer purchases, and urging means for urging the customer to pick up the product with respect to a customer terminal held by the customer. The display means displays a confirmation screen regarding the necessity of the urging before the urging is performed by the urging means. A system characterized by this. According to the above configuration, after confirmation is made by a store clerk regarding the necessity of pick-up urging, pick-up urging can be performed. Therefore, it is possible to suppress performing pick-up urging on a customer who has already picked up the product. Thereby, unnecessary urging to the customer can be suppressed, so that it is possible to prevent the induction of improper behavior by the customer and to prevent the induction of trouble with the customer. Therefore, suitable urging can be performed regarding the pick-up of the product.

[0125] (2) In the configuration of (1) above, acquisition means for acquiring pick-up information indicating that the product is to be picked up is provided. The display means may display the confirmation screen when a first predetermined time has elapsed without the pick-up information being acquired by the acquisition means after the product can be picked up. According to the above configuration, when 15 minutes have elapsed since the product can be picked up and the pick-up has not been performed, it is possible to notify the store clerk to that effect. Further, since pick-up urging can be performed on the customer terminal 50, the customer can be urged to pick up.

[0126] (3) In the configuration of (2) above, reception means for receiving a request for the urging is provided on the confirmation screen. The urging means may perform the urging when a second predetermined time has elapsed without the request for the urging being received by the reception means from the display of the confirmation screen. According to the above configuration, for example, even when a store clerk cannot check the urging confirmation screen 610 and does not receive a request for pick-up urging from the store clerk, such as during a busy time period, pick-up urging can be performed on the customer terminal 50.

[0127] (4) In the configuration of (1) or (2) above, an accounting means for performing accounting based on the commodity may be provided, and the display means may be configured to be able to display the confirmation screen after the accounting by the accounting means is completed. According to the above configuration, the reminder confirmation screen 610 can be displayed without interfering with the operation related to accounting. Also, the registration and accounting device 20 according to the present embodiment does not display the reminder confirmation screen 610 even during the registration of a commodity. For this reason, the reminder confirmation screen 610 can be displayed without interfering with the operation related to the registration of the commodity.

[0128] (5-1) In the configuration of (1) or (2) above, a non-reminder reception means for receiving the non-reminder instruction on the confirmation screen, and a cancellation means for setting the commodity as already taken according to the reception of the non-reminder instruction by the non-reminder reception means may be provided. According to the above configuration, since cancellation can be performed without separately launching a screen for cancellation processing and performing a cancellation operation for the commodity, the labor involved in cancellation can be reduced.

[0129] (5-2) In the configuration of (1) or (2) above, the reminder means may be provided in the upper-level device of the customer terminal, and the customer terminal may be provided with a notification means for performing a notification in response to the reminder, and a transmission means for receiving a message indicating that the commodity has already been taken in response to the notification by the notification means and transmitting the message to the upper-level device. According to the above configuration, the management server 1 can perform cancellation processing. Therefore, the transaction can be appropriately completed, and it is possible to suppress the situation of issuing a reminder to a customer who has already taken the commodity.

[0130] (6) To solve the above problems, a store terminal, which is another aspect of the present invention, includes display means for displaying products purchased by customers. Before the pick-up of the products is urged to the customer, the display means displays a confirmation screen regarding the necessity of such urging to the customer terminal held by the customer. The store terminal is characterized by this. According to the above configuration, after the necessity of pick-up urging is confirmed by a store clerk, pick-up urging can be performed. Therefore, it is possible to suppress performing pick-up urging to a customer who has already picked up the product. As a result, unnecessary urging to the customer can be suppressed, so that it is possible to prevent the inducement of improper behavior by the customer and to prevent the inducement of trouble with the customer. Thus, suitable urging regarding the pick-up of the product can be performed.

[0131] (7) To solve the above problems, a program, which is another aspect of the present invention, is a program that causes a computer to function as a store terminal. The program causes the computer to function as display means for displaying products purchased by customers. Before the pick-up of the products is urged to the customer, the display means displays a confirmation screen regarding the necessity of such urging to the customer terminal held by the customer. The program is characterized by this. According to the above configuration, after the necessity of pick-up urging is confirmed by a store clerk, pick-up urging can be performed. Therefore, it is possible to suppress performing pick-up urging to a customer who has already picked up the product. As a result, unnecessary urging to the customer can be suppressed, so that it is possible to prevent the inducement of improper behavior by the customer and to prevent the inducement of trouble with the customer. Thus, suitable urging regarding the pick-up of the product can be performed.

[0132] Note that all or part of each function (input / output, storage, processing (including judgment)) in the product delivery system St (management server 1, registration settlement device 20, and customer terminal 50) described above may be realized in another device different from the device described as the execution entity of the function.

[0133] Specifically, all or part of each functional unit (see FIG. 4) provided in the management server 1, the registration and settlement device 20, and the customer terminal 50 may be provided in another computer device. For example, all or part of each functional unit may be provided in the management server 1, or may be provided in a computer device other than this. Also, the computer device in which each functional unit is provided is not limited to a plurality of units, and may be one unit. For example, one computer device may be provided with all of each functional unit.

[0134] In relation to the above, the registration and settlement device 20 and the customer terminal 50 may function as so-called thin clients specialized in the input / output interface part with respect to various displays and the like. That is, the registration and settlement device 20 and the customer terminal 50 may receive various inputs (operations of an operator and detections of devices), transmit input information (operation information, detection information, etc.) to the management server 1, receive the processing results of the management server 1 (update screen information, control information of devices, etc.) based on the input information, and perform various outputs (display on a display unit, control of devices).

[0135] Incidentally, a program for implementing the product delivery system St, the management server 1, the registration settlement device 20, and the customer terminal 50 described above may be recorded on a computer-readable storage medium, and the program may be read into and executed by a computer system. Here, the "computer system" shall include hardware such as an OS and peripheral devices. Also, the "computer-readable storage medium" refers to a portable medium such as a USB (Universal Serial Bus) flash memory, an SSD (Solid State Drive), a flexible disk, a magneto-optical disk, a ROM, a CD-ROM, or a storage device such as a hard disk built into a computer system. Furthermore, the "computer-readable storage medium" also includes a volatile memory (RAM) inside a computer system that serves as a server or a client when a program is transmitted via a network such as the Internet or a communication line such as a telephone line, and holds the program for a certain period of time. Also, the above program may be transmitted from a computer system storing the program in a storage device or the like to another computer system via a transmission medium or by a transmission wave in the transmission medium. Here, the "transmission medium" for transmitting the program refers to a medium having a function of transmitting information, such as a network (communication network) such as the Internet or a communication line (communication line) such as a telephone line. Also, the above program may be for realizing a part of the functions described above. Furthermore, it may be a so-called difference file (difference program) that can realize the functions described above in combination with a program already recorded in a computer system.

Explanation of Signs

[0136] St…Product delivery system, 1…Management server, 2…Delivery management DB, 20…Registration settlement device, 30…Kitchen terminal, 40…Call display, 50…Customer terminal, 401…Display unit, 402…Acquisition unit, 403…Reception unit, 404…Settlement unit, 411…Reminder unit, 421…Notification unit, 422…Transmission unit

Claims

1. display means for displaying the products purchased by the customer; prompting means for prompting the customer to pick up the products with respect to the customer terminal possessed by the customer; comprising; before the prompting is performed by the prompting means, the display means displays a confirmation screen regarding the necessity of the prompting; A system characterized by this.

2. acquisition means for acquiring pick-up information indicating that the products are to be picked up; after it becomes possible to pick up the products, when a first predetermined time has elapsed without the pick-up information being acquired by the acquisition means, the display means displays the confirmation screen; The system according to claim 1, characterized by this.

3. reception means for receiving a request for the prompting on the confirmation screen; when a second predetermined time has elapsed without the request for the prompting being received by the reception means from the display of the confirmation screen, the prompting means performs the prompting; The system according to claim 2, characterized by this.

4. settlement means for performing settlement based on the products; after the settlement by the settlement means is completed, the display means enables the display of the confirmation screen; The system according to claim 1 or 2.

5. non-prompting reception means for receiving a refusal to prompt on the confirmation screen; cancellation means for setting the products as having been picked up in response to the non-prompting reception means receiving the refusal to prompt; The system according to claim 1 or 2, characterized by comprising this.

6. display means for displaying the products purchased by the customer; before the customer is prompted to pick up the products with respect to the customer terminal possessed by the customer, the display means displays a confirmation screen regarding the necessity of the prompting; A store terminal characterized by this.

7. A program for causing a computer to function as a store terminal, causing the computer to function as display means for displaying the products purchased by the customer, before the customer is prompted to pick up the products with respect to the customer terminal possessed by the customer, the display means displays a confirmation screen regarding the necessity of the prompting; A program characterized by this.

Images