Product sales data processing device, product sales data processing system and program

Abstract

To provide a technique capable of preventing a customer from forgetting to receive an attachment of a purchased commodity.SOLUTION: This commodity sales data processing device configured as a portable terminal comprises: a commodity registration unit that acquires identification information about a commodity to be purchased and registers the commodity; a settlement instruction unit that receives an instruction of settlement regarding the registered commodity and requests a settlement process; and a notification unit that, after completion of the settlement process, warns against forgetting to receive an attachment necessary for consuming the commodity and notifies a customer of a receiving place of the attachment.SELECTED DRAWING: Figure 9

Description

[Technical Field]

[0001] An embodiment of the present invention relates to a merchandise sales data processing device, a merchandise sales data processing system, and a program. [Background technology]

[0002] BACKGROUND ART Conventionally, devices that assist in the delivery of accessories such as chopsticks and spoons to be used with purchased products in stores are known (for example, Patent Document 1).

[0003] Patent Document 1 discloses a device that prevents store clerks from forgetting to attach accessories to products. Such devices are used when conducting face-to-face sales using a POS terminal or the like. Recently, product sales data processing devices that allow customers to register products and make payments themselves using a mobile device such as a smartphone or tablet terminal have become popular. When using such product sales data processing devices, customers can perform payment processing anywhere in the store, so it has been necessary to provide more reliable guidance to customers to ensure that they do not forget to remove any accessories. Summary of the Invention [Problem to be solved by the invention]

[0004] The problem to be solved by the present invention is to provide a product sales data processing device, a product sales data processing system, and a program that can prevent customers from forgetting to receive accessories for purchased products. [Means for solving the problem]

[0005] The product sales data processing device of the embodiment is configured as a mobile terminal and includes a product registration unit, a payment instruction unit, and a notification unit. The product registration unit acquires identification information of a product to be purchased and registers the product. The payment instruction unit accepts payment instructions for the registered product and requests payment processing. After the payment processing is completed, the notification unit warns the user that attachments required for consuming the product have been forgotten and notifies the user of the location where the attachments can be received. [Brief explanation of the drawings]

[0006] [Figure 1] FIG. 1 is a schematic configuration diagram of a product sales data processing system according to an embodiment. [Figure 2] FIG. 2 is a hardware block diagram illustrating an example of a hardware configuration of a mobile terminal. [Figure 3] FIG. 3 is a diagram illustrating an example of a data structure of the product master. [Figure 4] FIG. 4 is a diagram showing an example of an attachment reception setting screen displayed on the mobile terminal. [Figure 5] FIG. 5 is a diagram showing an example of a product registration screen displayed on the mobile terminal. [Figure 6] FIG. 6 is a diagram showing an example of a payment completion screen displayed on the mobile terminal. [Figure 7] FIG. 7 is a diagram showing an example of an attachment receiving location guide screen displayed on the mobile terminal. [Figure 8] FIG. 8 is a diagram showing an example of a notification screen displayed on the mobile terminal when a customer leaves the store without receiving any attachments. [Figure 9] FIG. 9 is a functional block diagram illustrating an example of the functional configuration of the product sales data processing system. [Figure 10] FIG. 10 is a flowchart illustrating an example of the flow of processing performed by the product sales data processing system according to the embodiment. [Figure 11] FIG. 11 is a functional block diagram showing the functional configuration of a modified example of the product sales data processing system. [Figure 12] FIG. 12 is a diagram showing an example of an attachment receipt confirmation screen displayed on a mobile terminal in a modified example of the product sales data processing system. [Figure 13] FIG. 13 is a schematic configuration diagram of a product sales data processing system according to the second embodiment. [Figure 14] FIG. 14 is a functional block diagram illustrating an example of the functional configuration of a product sales data processing system according to the second embodiment. [Figure 15]FIG. 15 is a flowchart illustrating an example of the flow of processing performed by the product sales data processing system of the second embodiment. [Figure 16] FIG. 16 is a schematic configuration diagram of a product sales data processing system according to the third embodiment. [Figure 17] FIG. 17 is a functional block diagram illustrating an example of the functional configuration of a product sales data processing system according to the third embodiment. [Figure 18] FIG. 18 is a flowchart showing an example of the flow of processing performed by the product sales data processing system of the third embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0007] (First embodiment) The first embodiment will be described in detail below with reference to the drawings. However, the present invention is not limited to the embodiment described below.

[0008] (Outline of product sales data processing system) The general configuration of a merchandise sales data processing system 40 according to an embodiment will be described with reference to Fig. 1. Fig. 1 is a diagram showing the general configuration of a merchandise sales data processing system according to an embodiment.

[0009] The product sales data processing system 40 includes a mobile terminal 10 and a server device 30.

[0010] The mobile terminal 10 is a smartphone, tablet terminal, or the like owned by the customer 60. Alternatively, the mobile terminal 10 may be loaned to the customer 60 by a store. A payment app that registers products to be purchased and performs payment is installed in advance on the mobile terminal 10. The customer 60 attaches the mobile terminal 10 to a shopping cart 62 that contains a shopping basket 64 to make a purchase. The mobile terminal 10 reads identification information that identifies the products to be purchased by the customer 60, registers the products, and transmits product registration information to the server device 30. The mobile terminal 10 also accepts payment instructions for the registered products and requests payment processing from the server device 30, for example.

[0011] Furthermore, when the product purchased by the customer 60 requires cutlery such as chopsticks and spoons, the mobile terminal 10, upon completion of the payment process, warns the customer 60 that they have forgotten to collect the cutlery and notifies them of the location where the cutlery can be collected. The mobile terminal 10 may also inform the customer 60 of the required number of cutlery. Furthermore, if the customer 60 leaves the store without collecting the cutlery, the mobile terminal 10 warns the customer 60 that they have forgotten to collect the cutlery. Note that cutlery is not limited to chopsticks and spoons, but may also be accessories required for consuming the product, such as knives and forks. In the following description, cutlery is referred to as accessories. In the present disclosure, accessories include not only cutlery but also paper plates, paper napkins, and the like required for consuming the product. Note that the mobile terminal 10 is an example of a product sales data processing device in the present disclosure.

[0012] The server device 30 manages the product registration information registered in the mobile terminal 10 by communicating with the mobile terminal 10. More specifically, the server device 30 acquires from the mobile terminal 10 the membership code of the customer 60, a transaction ID that uniquely identifies one transaction, and the product registration information registered in the mobile terminal 10, and records the membership code, transaction ID, and product registration information in association with each other. When the server device 30 acquires a payment processing request from the mobile terminal 10, it requests a payment server (not shown) to perform the payment processing, and when the payment processing by the payment server is completed, it sends a payment completion notification to the mobile terminal 10.

[0013] The mobile terminal 10 and the server device 30 communicate with each other via the network N, the router 13, and the wireless communication unit 12.

[0014] The network N is an information and communication network such as the Internet or an intranet.

[0015] A plurality of wireless communication units 12 are installed in the store and connected to the in-store network 14. The wireless communication units 12 establish wireless communication between the mobile terminals 10 and the server device 30.

[0016] The router 13 is a relay device for establishing network communication between the mobile terminal 10 and the server device 30 .

[0017] (Mobile device hardware configuration) The hardware configuration of the mobile terminal 10 will be described with reference to Fig. 2. Fig. 2 is a hardware block diagram showing an example of the hardware configuration of the mobile terminal.

[0018] The mobile terminal 10 includes a control unit 21, a storage unit 22, and peripheral devices such as a display device 23, an operation device 24, a camera 25, a speaker 26, a positioning device 27, and a communication interface 28.

[0019] The control unit 21 includes a CPU (Central Processing Unit) 211, a ROM (Read Only Memory) 212, and a RAM (Random Access Memory) 213. The CPU 211 is the main controller. The ROM 212 stores various fixed data, various tables, etc. The RAM 213 functions as a work memory, expanding control programs and various data when the CPU 211 performs various processes.

[0020] The storage unit 22 stores a control program 221, a product master 222, and a product registration file 223.

[0021] The control program 221 is a program executed by the CPU 211. The CPU 211, ROM 212, RAM 213, and storage unit 22 are connected to one another via an internal bus, and the control unit 21 causes the CPU 211 to load the control program 221 stored in the storage unit 22 and various data stored in the ROM 212 into the RAM 213 and operate them. In this way, the control unit 21 executes various control processes.

[0022] The product master 222 is a master file in which product information of products handled in a store is registered. The detailed structure of the product master 222 will be described later in detail (see FIG. 3).

[0023] The product registration file 223 is a file that stores product information registered for purchase by the customer 60. The product registration file 223 includes at least the product name, unit price, quantity, and total price.

[0024] The display device 23 includes a liquid crystal panel or an organic EL panel, and displays various operation screens and information screens.

[0025] The operation device 24 is, for example, a touch panel that is stacked on the display device 23 and that acquires operation information from the customer 60 .

[0026] Camera 25 is a camera equipped with an imaging element such as a CCD or C-MOS, which photographs a code symbol such as a barcode attached to a product purchased by customer 60. Note that instead of camera 25, mobile terminal 10 may have a scanner (not shown) configured separately from mobile terminal 10 read the code symbol and acquire the product code from the scanner.

[0027] The speaker 26 outputs beeps, guide voices, etc. to the customer 60.

[0028] The positioning device 27 measures the current position of the mobile terminal 10. The positioning device 27 is, for example, a GPS receiver that receives a GPS signal, or a beacon receiver that receives a signal from a beacon installed in a store.

[0029] The communication interface 28 is a communication adapter that enables wireless communication between the mobile terminal 10 and the wireless communication unit 12.

[0030] Although the hardware configuration of the server device 30 is not shown, the server device 30 has the same computer configuration as the mobile terminal 10, including a CPU, a ROM, a RAM, and a storage unit.

[0031] (Product Master Structure) The structure of the product master 222 will be described with reference to Fig. 3. Fig. 3 is a diagram showing an example of the data structure of the product master.

[0032] The product master 222 is a master file for storing and managing information on all products handled in the store. The contents of the product master 222 are updated successively in response to product replacements, price changes, etc., so the mobile terminal 10 obtains update information for the product master from a store server (not shown) or the like to keep the contents of the product master 222 always up to date.

[0033] The product master 222 stores product information such as product name, unit price, additional information, and accessory information in association with the product codes of products sold in the store. The product name field stores the name of the product corresponding to the product code. The unit price field stores the unit price of the product corresponding to the product code. The additional information field stores additional information about the product corresponding to the product code. For example, the type of product is stored in the additional information field. If the product is clothing, the additional information field stores the size, color, design, material, brand, and so on. The additional information field may also store image data of the product corresponding to the product code. The accessory information field stores information indicating whether the product requires accessories and the specific details of the required accessories (chopsticks, spoon, fork, knife, paper plate, paper napkin, etc.). The product master 222 may store information other than the information shown in FIG. 3.

[0034] (Example of mobile device operation and screen display) 4 to 8, an example of the operation of the mobile terminal 10 will be described with reference to examples of screens displayed on the display device 23. FIG. 4 is a diagram showing an example of an attachment reception setting screen displayed on the mobile terminal. FIG. 5 is a diagram showing an example of a product registration screen displayed on the mobile terminal. FIG. 6 is a diagram showing an example of a payment completion screen displayed on the mobile terminal. FIG. 7 is a diagram showing an example of an attachment reception location guidance screen displayed on the mobile terminal. FIG. 8 is a diagram showing an example of a notification screen displayed on the mobile terminal when you leave the store without receiving any attachments.

[0035] When a customer 60 enters a store, the customer 60 performs check-in processing using the mobile terminal 10. The check-in processing is performed, for example, when the customer enters the store by having the mobile terminal 10 perform short-range wireless communication with a check-in terminal (not shown) installed in the store. When the check-in processing is performed, the check-in terminal reads the customer 60's membership code from the mobile terminal 10. The check-in terminal then issues a transaction ID that uniquely identifies the transaction and outputs it to the mobile terminal 10. By obtaining the transaction ID, the mobile terminal 10 is ready to start shopping.

[0036] When the customer 60 is ready to start shopping, the customer 60 selects "Attachment Receipt Settings" from the main menu (not shown) displayed on the display device 23 of the mobile terminal 10. At this time, the attachment receipt setting screen shown in FIG. 4 is displayed on the display device 23 of the mobile terminal 10.

[0037] The attachment reception setting screen displays a reception setting button 81, a no reception setting button 82, and a back button 83.

[0038] The receiving setting button 81 is a button for setting to receive all attachments. When the receiving setting button 81 is pressed, if the product registered by the customer 60 is a product that requires attachments, the mobile terminal 10 calculates the required quantity of attachments assuming that all attachments will be received. Furthermore, when the receiving setting button 81 is pressed, the mobile terminal 10, upon completion of the payment process, issues a warning to the customer that attachments have been forgotten to be received and notifies the customer of the location where the attachments can be received. Furthermore, the mobile terminal 10 may notify the customer of the required quantity of attachments. This will be described in more detail below (see FIGS. 6 and 7).

[0039] The "no attachments required" setting button 82 is a button for setting not to receive any attachments. When the "no attachments required" setting button 82 is pressed, even if the product registered by the customer 60 is a product that requires attachments, the mobile terminal 10 does not calculate the required quantity of attachments, assuming that none of the attachments will be received. Furthermore, when the payment process is completed, the mobile terminal 10 does not warn the customer that attachments have been forgotten to be received, nor notify the customer of the location where the attachments can be received.

[0040] The back button 83 is a button for exiting the attachment reception setting screen and transitioning to, for example, the main menu screen.

[0041] The customer 60 picks up the product to be purchased and holds up a code symbol, such as a barcode, attached to the product over the camera 25 of the mobile terminal 10. The mobile terminal 10 then reads the code symbol that appears in the image of the product captured by the camera 25. The code symbol contains a product code that uniquely identifies the product.

[0042] The mobile terminal 10 uniquely identifies the product purchased by the customer 60 by comparing the read product code with the product master 222. Then, the product information of the compared product is registered as product registration information. At this time, the display device 23 of the mobile terminal 10 displays a product registration screen shown in FIG. 5.

[0043] The product registration screen displays registered product information, a delete button 84 for deleting the registered product information, a checkout button 85, and a scroll button 86.

[0044] The product information displayed on the product registration screen includes the product name, a number indicating the order in which the product was registered, the purchase quantity, the price, the number of products, and the total amount. As shown in Fig. 5, the display device 23 of the mobile terminal 10 displays the latest registration information for a predetermined number of registered products. The product information displayed on the display device 23 is stored in the product registration file 223 described above.

[0045] The delete button 84 is displayed for each registered product. If the customer 60 wishes to cancel the purchase of a registered product, the customer 60 presses the delete button 84 for the product in question and returns the product that was added to the shopping cart 64 to the sales floor.

[0046] The checkout button 85 is a button that ends the product registration and instructs the start of payment. When the checkout button 85 is pressed, the mobile terminal 10 outputs the product registration file 223 to the server device 30.

[0047] The scroll button 86 is a button for scrolling the displayed product information when multiple products are registered. The scroll button 86 is displayed at the top and bottom of the product information, for example, as shown in FIG. 5. When the scroll button 86 at the top of the product registration information is pressed, the product information displayed on the display device 23 is scrolled upward on the screen. When the scroll button 86 at the bottom of the product registration information is pressed, the product information displayed on the display device 23 is scrolled downward on the screen. This allows the customer 60 to check product information that is not displayed on the screen. Note that instead of using the scroll button 86, the product information may be scrolled by swiping up or down on the product registration screen.

[0048] When the payment process is completed, the server device 30 outputs payment completion information to the mobile terminal 10. Then, when the mobile terminal 10 acquires the payment completion information from the server device 30, a payment completion screen shown in FIG. 6 is displayed on the display device 23 of the mobile terminal 10.

[0049] If the customer 60 has set up the receipt of attachments on the attachment receipt setting screen shown in Figure 4, the payment completion screen will display a notice that payment has been completed, the number of attachments 87, a back button 83, a receipt location display button 88, and an attachment receipt completion button 89.

[0050] The notice of payment completion includes a notice indicating that the payment has been completed and details of the payment (number of items and total amount). The notice of payment completion may also include the payment method.

[0051] The attachment quantity 87 is the quantity of the necessary attachments. It is desirable to notify the attachment quantity 87 for each type of attachment.

[0052] The back button 83 is a button for exiting the payment completion screen and transitioning to, for example, the main menu screen.

[0053] The pickup location display button 88 is a button that displays the pickup location for the attachments. If the customer 60 does not know where to pick up the attachments, he or she presses the pickup location display button 88. When the pickup location display button 88 is pressed, the mobile terminal 10 displays the attachment pickup location guide screen shown in FIG. 7. Attachments are generally placed near the cash register or at the service counter in a store. However, because a customer using the mobile terminal 10 can perform payment processing anywhere in the store, it is expected that the customer may be confused about where to pick up the attachments. In such a case, by having the mobile terminal 10 display the pickup location for the attachments, the customer 60 can reliably receive the attachments. Note that in this embodiment, the pickup location for the attachments is displayed by having the customer 60 press the pickup location display button 88. However, the pickup location for the attachments may be automatically displayed when the payment processing is completed.

[0054] The attachment reception completion button 89 is a button that the customer 60 is prompted to press when the reception of the attachments is complete. When the customer 60 receives the attachments at the attachment reception location, the customer 60 presses the attachment reception completion button 89. This causes the mobile terminal 10 to determine that the customer 60 has completed the reception of the attachments.

[0055] When the receiving location display button 88 is pressed on the payment completion screen, the display device 23 of the mobile terminal 10 displays the attachment receiving location guide screen shown in FIG.

[0056] The attachment receiving location guide screen displays a receiving location 90, an attachment quantity 87, an attachment receiving completion button 89, and a back button 83.

[0057] The pickup location 90 is a map showing the pickup location in the store where the attachment can be received. The pickup location 90 also displays the current location of the mobile terminal 10. The mobile terminal 10 measures its own current location in the store using the positioning device 27 described above.

[0058] The attachment quantity 87, attachment receipt completion button 89, and back button 83 are as described above.

[0059] When the customer 60 leaves the store without receiving the attachment, a notification screen shown in FIG. 8 is displayed on the display device 23 of the mobile terminal 10.

[0060] The notification screen displays a message indicating that the attachments have been forgotten. The notification screen also displays the number of attachments 87, a pickup location display button 88, an attachment pickup completion button 89, and a back button 83.

[0061] 8 is displayed, a beep 91 is output from the speaker 26. Note that instead of the beep 91, a voice message may be output, or a vibrator (not shown) provided in the mobile terminal 10 may be vibrated.

[0062] In addition, when the attachment reception completion button 89 is not pressed, i.e., when the attachment has not been received, and the current location of the mobile terminal 10 moves away from the pre-set store location (i.e., when the customer 60 leaves the store without receiving the attachment), the mobile terminal 10 displays the notification screen shown in Figure 8.

[0063] When the customer 60 notices the notification screen, he or she returns to the store to pick up the attached item.

[0064] (Functional configuration of product sales data processing system) The functional configuration of the merchandise sales data processing system 40 will be described with reference to Fig. 9. Fig. 9 is a functional block diagram showing an example of the functional configuration of the merchandise sales data processing system.

[0065] (Functional configuration of mobile device) First, the functional configuration of the mobile terminal 10 will be described. The control unit 21 of the mobile terminal 10 reads out the control program 221, deploys it in the RAM 213, and executes it to realize, as functional units, an attachment reception setting unit 101, a code information acquisition unit 102, a product registration unit 103, an attachment quantity calculation unit 104, a payment instruction unit 105, a payment completion information acquisition unit 106, a notification unit 107, an attachment reception completion confirmation unit 108, and a current location estimation unit 109, all of which are shown in Fig. 9. However, some of these functional units may be handled by the server device 30, rather than the mobile terminal 10.

[0066] The attachment reception setting unit 101 sets whether to receive attachments or not to receive attachments. Specifically, when detecting that a reception setting button 81 displayed on the mobile terminal 10 has been pressed, the attachment reception setting unit 101 sets to receive all attachments that come with the product to be purchased. Also, when detecting that a reception not required setting button 82 displayed on the mobile terminal 10 has been pressed, the attachment reception setting unit 101 sets to not receive any attachments that come with the product to be purchased.

[0067] The code information acquisition unit 102 causes the camera 25 to read a code symbol such as a barcode or two-dimensional code attached to a product purchased by a customer. The code information acquisition unit 102 also acquires the product code by decoding the information recorded in the code symbol. The code information acquisition unit 102 may also cause a scanner configured separately from the mobile terminal 10 to read the code symbol.

[0068] The product registration unit 103 acquires product information to be purchased by the customer 60 from the product master 222 based on the product code, and registers the product information in the product registration file 223 .

[0069] The attachment quantity calculation unit 104 adds the required quantity of attachments on the condition that the product registered by the product registration unit 103 requires attachments when consuming the product.

[0070] When the payment instruction unit 105 detects that the checkout button 85 displayed on the mobile terminal 10 has been pressed, it requests payment processing from the server device 30. The payment instruction unit 105 also outputs to the server device 30 a membership code that uniquely identifies the customer 60, a transaction ID that uniquely identifies one transaction, and product registration information that is the subject of payment.

[0071] The payment completion information acquisition unit 106 acquires information indicating that the payment process has been completed from the server device 30. The payment completion information acquisition unit 106 also acquires information indicating the details of the payment from the server device 30.

[0072] When the payment process is completed, the notification unit 107 issues a warning to the user that they have forgotten to receive the attachments and notifies the user of the location where the attachments can be received. The notification unit 107 may also notify the user of the required number of attachments.

[0073] The attachment reception completion confirmation unit 108 acquires information indicating that the reception of the attachments has been completed. Specifically, the attachment reception completion confirmation unit 108 determines that the reception of the attachments has been completed when it detects that the attachment reception completion button 89 displayed on the mobile terminal 10 has been pressed.

[0074] The current location estimation unit 109 estimates the current location of the mobile terminal 10.

[0075] (Functional configuration of server device) Next, a description will be given of the functional configuration of the server device 30. The server device 30 executes a control program (not shown) to realize a payment processing unit 301 and a payment completion information output unit 302 shown in Fig. 9 as functional parts.

[0076] The payment processing unit 301 determines whether a payment processing request has been received from the mobile terminal 10. Furthermore, the payment processing unit 301 requests a payment server (not shown) to perform payment processing related to the product registration information that is the subject of payment, based on the membership code and transaction ID of the customer 60 received from the mobile terminal 10.

[0077] The payment completion information output unit 302 outputs to the mobile terminal 10 information indicating that the payment process has been completed and information indicating the details of the payment.

[0078] (Processing flow performed by the product sales data processing system) The flow of processing performed by the product sales data processing system 40 will be described with reference to Fig. 10. Fig. 10 is a flowchart showing an example of the flow of processing performed by the product sales data processing system of the embodiment. It is assumed that the customer 60 operates the mobile terminal 10 in advance to set up the mobile terminal 10 to receive all attachments that come with the product to be purchased.

[0079] (Processing flow performed by mobile devices) The customer 60 causes the camera 25 to capture an image of the code symbol attached to the product to be purchased. The product registration unit 103 then recognizes the product code recorded in the code symbol captured by the camera 25 and compares it with the product master 222, thereby registering the product information of the product purchased by the customer 60 in the product registration file 223 (step S11).

[0080] The attachment quantity calculation unit 104 determines whether the registered product requires attachments (step S12). If it is determined that the registered product requires attachments (step S12: Yes), the process proceeds to step S13. On the other hand, if it is not determined that the registered product requires attachments (step S12: No), the process proceeds to step S14. The attachment quantity calculation unit 104 refers to the product master 222 to determine whether the product corresponding to the product code of the registered product requires attachments.

[0081] If it is determined in step S12 that the registered product requires an attachment, the attachment quantity calculation unit 104 adds the quantity of the attachment (step S13). The addition of the attachment is performed for each type of attachment required. For example, if the product purchased by the customer 60 requires a spoon, the attachment quantity calculation unit 104 adds the quantity of the spoon. Then, the process proceeds to step S14.

[0082] If it is determined in step S12 that the recorded product does not require any accessories, or following step S13, the payment instruction unit 105 determines whether a payment instruction has been received from the customer 60 (step S14). If it is determined that a payment instruction has been received from the customer 60 (step S14: Yes), the process proceeds to step S15. On the other hand, if it is not determined that a payment instruction has been received from the customer 60 (step S14: No), the process returns to step S11. Note that the payment instruction unit 105 determines that a payment instruction has been received from the customer 60 when it detects that the checkout button 85 displayed on the mobile terminal 10 has been pressed.

[0083] In step S14, if it is determined that a payment instruction has been received from the customer 60, the payment instruction unit 105 makes a payment processing request to the server device 30 by outputting the customer 60's membership code, transaction ID, and product registration information (step S15).

[0084] The payment completion information acquisition unit 106 determines whether payment completion information and information indicating payment details have been acquired from the server device 30 (step S16). If it is determined that payment completion information and information indicating payment details have been acquired from the server device 30 (step S16: Yes), the process proceeds to step S17. On the other hand, if it is not determined that payment completion information and information indicating payment details have been acquired from the server device 30 (step S16: No), the determination in step S16 is repeated.

[0085] In step S16, when it is determined that payment completion information and information indicating payment details have been acquired from the server device 30, the attachment quantity calculation unit 104 determines whether any of the products purchased by the customer 60 require attachments (step S17). If it is determined that any of the products purchased by the customer 60 require attachments (step S17: Yes), the process proceeds to step S18. On the other hand, if it is not determined that any of the products purchased by the customer 60 require attachments (step S17: No), the mobile terminal 10 ends the process of FIG. 10.

[0086] In step S17, if it is determined that the products purchased by customer 60 include products that require attachments, notification unit 107 warns customer 60 that he or she has forgotten to receive the attachments and notifies the customer of the location where the attachments can be received (step S18). This ensures that the attachments are received even if customer 60 issues a payment instruction anywhere in the store (i.e., even if the attachments are not near customer 60). Furthermore, in step S18, notification unit 107 may notify the customer of the number of attachments to be received.

[0087] The attachment reception completion confirmation unit 108 determines whether the attachment reception completion button 89 displayed on the mobile terminal 10 has been pressed (step S19). If it is determined that the attachment reception completion button 89 has been pressed (step S19: Yes), the mobile terminal 10 ends the processing in Fig. 10. On the other hand, if it is not determined that the attachment reception completion button 89 has been pressed (step S19: No), the processing proceeds to step S20.

[0088] If it is determined in step S19 that the attachment reception completion button 89 has not been pressed, the current location estimation unit 109 determines whether the mobile terminal 10 is outside the store (i.e., whether the customer 60 has left the store without receiving the attachment) (step S20). If it is determined that the mobile terminal 10 is outside the store (step S20: Yes), the process proceeds to step S21. On the other hand, if it is not determined that the mobile terminal 10 is outside the store (step S20: No), the process returns to step S19.

[0089] If it is determined in step S20 that the mobile terminal 10 is outside the store, the notification unit 107 issues a warning to the customer 60 not to forget to pick up the attachments and notifies the customer of the location to pick up the attachments (step S21). This ensures that the customer 60 can pick up the attachments even if the customer 60 leaves the store without picking up the attachments. Then, the process returns to step S19.

[0090] (Processing flow performed by the server device) The payment processing unit 301 determines whether a payment processing request has been received from the mobile terminal 10 (step S31). If it is determined that a payment processing request has been received (step S31: Yes), the process proceeds to step S32. On the other hand, if it is not determined that a payment processing request has been received (step S31: No), step S31 is repeated.

[0091] If it is determined in step S31 that a payment processing request has been acquired, the payment processing unit 301 requests a payment server (not shown) to perform payment processing (step S32).

[0092] When the payment process is completed, the payment completion information output unit 302 outputs information indicating that the payment process is completed and information indicating the payment details to the mobile terminal 10 (step S33). After that, the server device 30 ends the process of FIG.

[0093] (Modification of the product sales data processing system of the first embodiment) A modified example of the merchandise sales data processing system will be described with reference to Fig. 11. Fig. 11 is a functional block diagram showing the functional configuration of the modified example of the merchandise sales data processing system.

[0094] The product sales data processing system 40, which is a first variant of the embodiment, asks the customer whether or not they want to receive attachments each time they register a product to be purchased, if the registered product requires attachments.

[0095] A product sales data processing system 40 according to a first modified example of the embodiment includes a mobile terminal 10 and a server device 30.

[0096] The mobile terminal 10 has the same functional configuration as the mobile terminal 10 described above (see FIG. 9), except that it has an attachment receipt confirmation unit 110 instead of the attachment receipt setting unit 101. The functions of the other functional parts shown in FIG. 11 are the same as those described in FIG. 9.

[0097] The attachment receipt confirmation unit 110 acquires information from the customer 60 instructing whether or not to receive attachments when a product is registered, provided that the product registered by the product registration unit 103 is a product that requires attachments. Specifically, when the customer 60 performs an operation to input information to the mobile terminal 10 that indicates that attachments will be received, the attachment receipt confirmation unit 110 determines that the customer 60 will receive the attachments for the product registered at that time. Furthermore, when the customer 60 performs an operation to input information to the mobile terminal 10 that indicates that attachments will not be received, the attachment receipt confirmation unit 110 determines that the customer 60 will not receive the attachments for the product registered at that time. A specific operation example will be described later (see FIG. 12).

[0098] 11, the mobile terminal 10 may further include an attachment reception setting unit 101. Then, only when the attachment reception setting unit 101 has set that attachments will be received, the attachment reception confirmation unit 110 may confirm whether or not the customer 60 will receive the attachments when the customer 60 registers a product that requires attachments.

[0099] Furthermore, the attachment reception setting unit 101 may allow the customer 60 to select either "No confirmation required at registration" or "Confirm at registration" after the reception setting button 81 is pressed on the attachment reception setting screen shown in Fig. 4. When the customer 60 selects "No confirmation required at registration," the operation described in the first embodiment may be performed, and when the customer 60 selects "Confirm at registration," the operation described in the modified example of the first embodiment may be performed.

[0100] (Explanation of the confirmation screen when registering a product) An attachment receipt confirmation screen displayed at the time of product registration in a modified example of the product sales data processing system will be described using Fig. 12. Fig. 12 is a diagram showing an example of an attachment receipt confirmation screen displayed on a mobile terminal in a modified example of the product sales data processing system.

[0101] When a customer 60 who is shopping registers a product that requires an attachment, an attachment reception confirmation screen shown in FIG. 12 is displayed on the display device 23 of the mobile terminal 10.

[0102] The attachment receipt confirmation screen displays a delete button 84, a receive button 92, and a no-receive button 93. The function of the delete button 84 is as described above.

[0103] The receive button 92 is a button for instructing to receive attachments for the currently registered product. When the receive button 92 is pressed, the attachment quantity calculation unit 104 of the mobile terminal 10 adds the required quantity of attachments for the currently registered product.

[0104] The "No need to receive" button 93 is a button for instructing not to receive attachments for the currently registered product. When the "No need to receive" button 93 is pressed, the attachment quantity calculation unit 104 of the mobile terminal 10 does not add the required quantity of attachments for the currently registered product.

[0105] Then, when payment is completed after all products have been registered, the required quantity of attachments held by the attachment quantity calculation unit 104 at that time is displayed in the attachment quantity 87 field on the payment completion screen (see Figure 6).

[0106] (Second embodiment) A merchandise sales data processing system 41 according to the second embodiment will be described with reference to Fig. 13. Fig. 13 is a schematic diagram of the merchandise sales data processing system according to the second embodiment.

[0107] The product sales data processing system 41 includes a mobile terminal 10, a checkout device 50, and a server device 30.

[0108] The mobile terminal 10 is a smartphone, tablet terminal, or the like carried by the customer 60. The mobile terminal 10 may also be loaned to the customer 60 by a store. The customer 60 attaches the mobile terminal 10 to a shopping cart 62 containing a shopping basket 64 to make a purchase. The mobile terminal 10 acquires identification information that identifies the product the customer 60 intends to purchase and registers the product. After product registration is complete, the mobile terminal 10, in response to an instruction from the customer 60, generates code information that embeds the customer 60's membership number and transaction ID. The code information is a barcode, a two-dimensional code, or the like. The mobile terminal 10 then displays the generated code information on its screen. The customer 60 has the scanner 52 connected to the checkout device 50 read the code information displayed on the mobile terminal 10, and has the checkout device 50 acquire the product registration information from the server device 30.

[0109] The checkout device 50 performs payment processing for the products purchased by the customer 60. A scanner 52 is connected to the checkout device 50. The scanner 52 reads code information displayed on the screen of the mobile terminal 10. The scanner 52 is configured separately from the checkout device 50, but it may also be configured integrally with the checkout device 50. The checkout device 50 also decodes the code information obtained from the scanner 52 into the customer 60's membership code and transaction ID, and obtains from the server device 30 the product registration information that the customer 60 registered using the mobile terminal 10 based on the membership code and transaction ID. The checkout device 50 also accepts instructions from the customer 60 regarding the payment method. When the checkout device 50 accepts an instruction to pay in cash from the customer 60, it performs payment by receiving coins or banknotes using its own change dispenser (not shown). In addition, when the accounting device 50 receives a card payment instruction from the customer 60 to pay by credit card or the like, it outputs the customer 60's membership code, transaction ID, and product registration information to the server device 30 and requests the server device 30 to process the payment.

[0110] Furthermore, if the product purchased by the customer 60 requires attachments, the checkout device 50, upon completion of the payment process, warns the customer 60 that they have forgotten to receive the attachments and notifies them of the location where they can be received. The checkout device 50 may also inform the customer 60 of the required number of attachments. Meanwhile, as described in the first embodiment, the mobile terminal 10 warns the customer 60 that they have forgotten to receive the attachments if the customer 60 leaves the store without receiving the attachments. That is, in the second embodiment, the checkout device 50 or the mobile terminal 10 is an example of a product sales data processing device of the present disclosure.

[0111] The payment methods used by the checkout device 50 are not limited to cash and credit card payments. The checkout device 50 can also support other payment methods, such as point payments, in which points awarded according to the purchase amount at the store are used to pay for products, electronic money payments, in which payments are made using electronic money charged to an IC card or mobile terminal 10, code payments, in which payments are made by reading barcodes or two-dimensional codes, and virtual currency payments using blockchain technology. Depending on the selected payment method, the checkout device 50 determines whether to process the payment itself or have the server device 30 process the payment.

[0112] The server device 30 communicates with the checkout device 50 to request payment processing, such as credit card payment, from a payment server (not shown). More specifically, the server device 30 receives a payment processing request from the checkout device 50. In doing so, the server device 30 receives from the checkout device 50 the customer 60's membership code, a transaction ID that uniquely identifies each transaction, and product registration information for the product that is the subject of the payment processing. When the payment is completed, the server device 30 outputs payment completion information to the checkout device 50 indicating that the payment has been completed. The server device 30 is also electrically connected to the mobile terminal 10, and when the payment is completed, it outputs payment completion information to the mobile terminal 10 indicating that the payment has been completed, along with the payment details.

[0113] The mobile terminal 10 and the server device 30 are electrically connected via a network N, a router 13, and a wireless communication unit 12. The accounting device 50 and the server device 30 are also connected via the network N.

[0114] (Functional configuration of the product sales data processing system according to the second embodiment) The functional configuration of the merchandise sales data processing system 41 will be described with reference to Fig. 14. Fig. 14 is a functional block diagram showing an example of the functional configuration of the merchandise sales data processing system of the second embodiment.

[0115] (Functional configuration of mobile device) First, a description will be given of the functional configuration of the mobile terminal 10. The mobile terminal 10 has the same functional configuration as the mobile terminal 10 described above (see FIG. 9), but has a code information display unit 111 instead of the payment instruction unit 105. The actions of the other functional parts shown in FIG. 14 are as described in FIG. 9.

[0116] The code information display unit 111 generates code information including a membership code that uniquely identifies the customer 60 and a transaction ID that uniquely identifies one transaction. The code information display unit 111 also displays the generated code information on the display device 23 of the mobile terminal 10.

[0117] (Functional configuration of accounting device) Next, we will explain the functional configuration of the checkout device 50. The checkout device 50 comprises a code information reading unit 501, a payment method acquisition unit 502, a payment execution instruction unit 503, and a payment completion information acquisition unit 504.

[0118] The code information reading unit 501 decodes the code information read by the scanner 52 and obtains the customer 60's membership code and transaction ID.

[0119] The payment method acquisition unit 502 accepts the selection of the payment method by the customer 60 through a selection operation.

[0120] The payment execution instruction unit 503 sends a payment processing request to the server device 30 using the payment method selected by the customer 60. Note that if the checkout device 50 itself can perform the payment processing, such as cash payment, the payment processing is executed.

[0121] The payment completion information acquisition unit 504 acquires, from the server device 30, payment completion information indicating that the payment has been completed.

[0122] (Functional configuration of server device) The functional configuration of the server device 30 is as described in the first embodiment (see FIG. 9). However, whereas in the first embodiment the server device 30 communicates only with the mobile terminal 10, the server device 30 of this embodiment communicates with the checkout device 50 in addition to the mobile terminal 10.

[0123] (Flow of processing performed by the product sales data processing system of the second embodiment) The flow of processing performed by the merchandise sales data processing system 41 will be described using Figure 15. Figure 15 is a flowchart showing an example of the flow of processing performed by the merchandise sales data processing system of the second embodiment. It is assumed that the customer 60 operates the mobile terminal 10 in advance to set up the receiving of all attachments that come with the merchandise to be purchased. Figure 15 also shows the flow of processing when the customer 60 selects credit card payment.

[0124] (Processing flow performed by mobile devices) The processing flow performed by the mobile terminal 10 differs from the processing flow performed by the mobile terminal 10 described in the first embodiment (see Figure 10) only in that, in step S15, instead of outputting a payment processing request to the server device, code information including a membership code that uniquely identifies the customer 60 and a transaction ID is displayed on the display device 23 of the mobile terminal 10 (step S45 in Figure 15).

[0125] (Processing flow performed by accounting device) The code information reading unit 501 determines whether the code information has been read from the mobile terminal 10 (step S61). If it is determined that the code information has been read (step S61: Yes), the process proceeds to step S62. On the other hand, if it is not determined that the code information has been read (step S61: No), step S61 is repeated.

[0126] In step S61, if it is determined that the code information has been read, the code information reading unit 501 decodes the read code information into the customer 60's membership code and transaction ID, and obtains the product registration information that the customer 60 is attempting to purchase from the server device 30 based on the membership code and transaction ID (step S62).

[0127] Next, the payment method acquisition unit 502 acquires the payment method selected by the selection operation of the customer 60 (step S63). It is assumed here that the customer 60 has selected credit card payment.

[0128] The payment execution instruction unit 503 instructs the server device 30 to execute the payment (step S64). At this time, the payment execution instruction unit 503 outputs a payment processing request to the server device 30, including the membership code of the customer 60, the transaction ID, and the product registration information.

[0129] The payment completion information acquisition unit 504 determines whether payment completion information indicating that the payment has been completed and the payment details have been acquired from the server device 30 (step S65). If it is determined that the payment completion information and payment details have been acquired (step S65: Yes), the checkout device 50 ends the processing in Figure 15. On the other hand, if it is determined that the payment completion information and payment details have not been acquired (step S65: No), step S65 is repeated.

[0130] (Processing flow performed by the server device) The processing flow performed by server device 30 is the same as the processing flow performed by server device 30 described in the first embodiment (see FIG. 10). However, the difference is that while in the first embodiment server device 30 communicates only with mobile terminal 10, in this embodiment server device 30 communicates with mobile terminal 10 and accounting device 50.

[0131] (Modification of the second embodiment) In the second embodiment, when the checkout device 50 receives payment completion information from the server device 30 indicating that the payment has been completed, the checkout device 50 may warn the customer 60 about forgetting to receive the attachments and provide information about where to receive the attachments. Specifically, the checkout device 50 displays the notification screen shown in FIG. 8 on the touch panel. This allows the customer 60 to reliably receive the attachments even if they are placed far from the checkout device 50.

[0132] In this case, the mobile terminal 10 may not warn the customer 60 about forgetting to pick up the attachments when the payment is completed, and may warn the customer 60 about forgetting to pick up the attachments and provide the location to pick up the attachments only if the customer 60 leaves the store without picking up the attachments.

[0133] (Third embodiment) A merchandise sales data processing system 42 according to the third embodiment will be described with reference to Fig. 16. Fig. 16 is a schematic diagram of the merchandise sales data processing system according to the third embodiment.

[0134] The product sales data processing system 42 includes a mobile terminal 10, a checkout device 50, a store server 56, and a server device 30.

[0135] The mobile terminal 10 is a smartphone, tablet terminal, or the like, owned by the customer 60. The mobile terminal 10 may also be loaned to the customer 60 by the store. The customer 60 attaches the mobile terminal 10 to a shopping cart 62 containing a shopping basket 64 to make a purchase. The mobile terminal 10 reads identification information that identifies the product that the customer 60 is purchasing and registers the product. The mobile terminal 10 also receives a payment instruction for the registered product and transmits the product registration information to the checkout device 50, along with a membership code that identifies the customer 60 and a transaction ID that uniquely identifies the transaction.

[0136] Furthermore, as described in the first embodiment, when the product purchased by the customer 60 requires attachments, the mobile terminal 10 warns the customer 60 that he / she has forgotten to receive the attachments and notifies the customer 60 of the location where the attachments can be received, upon completion of the payment process. The mobile terminal 10 may also notify the customer 60 of the required number of attachments. Furthermore, when the customer 60 leaves the store without receiving the attachments, the mobile terminal 10 warns the customer 60 that he / she has forgotten to receive the attachments. The mobile terminal 10 is an example of a product sales data processing device in the present disclosure.

[0137] The checkout device 50 acquires the customer 60's membership code, transaction ID, and product registration information from the mobile terminal 10. The checkout device 50 then performs payment processing for the products purchased by the customer 60. When the checkout device 50 receives a cash payment instruction from the customer 60, it performs payment by receiving coins or bills using its own change dispenser (not shown). When the checkout device 50 receives a credit card payment instruction from the customer 60, it outputs the customer 60's membership code, transaction ID, and product registration information to the server device 30, causing the server device 30 to perform payment processing.

[0138] The payment methods used by the checkout device 50 are not limited to cash and credit card payments. The checkout device 50 can also support other payment methods, such as point payments, in which points awarded according to the purchase amount at the store are used to pay for products, electronic money payments, in which payments are made using electronic money charged to an IC card or mobile terminal 10, code payments, in which payments are made by reading barcodes or two-dimensional codes, and virtual currency payments using blockchain technology. Depending on the selected payment method, the checkout device 50 determines whether to process the payment itself or have the server device 30 process the payment.

[0139] The checkout device 50 also outputs information indicating that the payment has been completed and the details of the payment to the mobile terminal 10 via the store server 56.

[0140] The store server 56 is a repeater used when the mobile terminal 10 and the checkout device 50 communicate with each other. In other words, the customer's 60 membership code, transaction ID, and product registration information output by the mobile terminal 10 are sent to the checkout device 50 via the store server 56. The store server 56 selects an unoccupied checkout device 50 from among the multiple checkout devices 50, and transmits the membership code, transaction ID, and product registration information to the available checkout device 50. Note that if only one checkout device 50 is installed in the store, the store server 56 may not be installed.

[0141] The server device 30 communicates with the checkout device 50 to request payment processing, such as credit card payment, from a payment server (not shown). More specifically, the server device 30 receives a payment processing request from the checkout device 50. In doing so, the server device 30 receives from the checkout device 50 the customer 60's membership code, transaction ID, and product registration information for the item to be processed. When the payment is complete, the server device 30 outputs payment completion information to the checkout device 50 indicating that the payment has been completed. Note that the server device 30 may also communicate with the checkout device 50 via the store server 56.

[0142] The mobile terminal 10 and the store server 56 are electrically connected via a wireless communication unit 12. The accounting device 50, the store server 56, and the server device 30 are connected via a router 13 and a network N. The accounting device 50 and the store server 56 are also connected via an in-store network or the like.

[0143] (Functional configuration of the product sales data processing system according to the third embodiment) The functional configuration of the merchandise sales data processing system 42 will be described with reference to Fig. 17. Fig. 17 is a functional block diagram showing an example of the functional configuration of the merchandise sales data processing system of the third embodiment.

[0144] (Functional configuration of mobile device) First, we will explain the functional configuration of the mobile terminal 10. Compared to the functional configuration of the mobile terminal 10 described above (see FIG. 9), the mobile terminal 10 has a product registration information output unit 112 instead of the payment instruction unit 105. The actions of the other functional parts shown in FIG. 17 are as described in FIG. 9.

[0145] The product registration information output unit 112 outputs, via the store server 56, to the checkout device 50, a membership code that identifies the customer 60, a transaction ID, and product registration information.

[0146] (Functional configuration of accounting device) Next, we will explain the functional configuration of the checkout device 50. In the functional configuration described above (see FIG. 14), the checkout device 50 has a product registration information acquisition unit 505 instead of the code information reading unit 501. The product registration information acquisition unit 505 acquires the customer 60's membership code, transaction ID, and product registration information from the mobile terminal 10 via the store server 56.

[0147] The checkout device 50 further includes a payment completion information output unit 506. The payment completion information output unit 506 outputs to the mobile terminal 10 payment completion information indicating that the payment has been completed, and information indicating the details of the payment.

[0148] (Functional configuration of server device) The functional configuration of the server device 30 is as described in the first embodiment (see FIG. 9). However, whereas in the first embodiment the server device 30 communicates only with the mobile terminal 10, the server device 30 of this embodiment communicates with the checkout device 50 in addition to the mobile terminal 10.

[0149] (Flow of processing performed by the product sales data processing system of the third embodiment) The flow of processing performed by the merchandise sales data processing system 42 will be described using Figure 18. Figure 18 is a flowchart showing an example of the flow of processing performed by the merchandise sales data processing system of the third embodiment. It is assumed that the customer 60 has previously operated the mobile terminal 10 to set up the system to receive all attachments that come with the merchandise to be purchased. Figure 18 also shows the flow of processing when the customer 60 selects credit card payment.

[0150] (Processing flow performed by mobile devices) The processing flow performed by the mobile terminal 10 differs from the processing flow performed by the mobile terminal 10 described in the second embodiment (see Figure 15) only in that in step S45, instead of displaying code information on the mobile terminal 10 and having the accounting device 50 read the code information, the customer 60's membership code, transaction ID, and product registration information are output to the accounting device 50 (step S85 in Figure 18).

[0151] (Processing flow performed by accounting device) The product registration information acquisition unit 505 determines whether the customer 60's membership code, transaction ID, and product registration information have been acquired from the mobile terminal 10 (step S101). If it is determined that the customer 60's identification information and product registration information have been acquired (step S101: Yes), the process proceeds to step S102. On the other hand, if it is not determined that the customer 60's identification information and product registration information have been acquired (step S101: No), step S101 is repeated.

[0152] In step S101, when it is determined that the membership code, transaction ID, and product registration information of the customer 60 have been acquired, the payment method acquisition unit 502 acquires the payment method selected by the selection operation of the customer 60 (step S102). Here, it is assumed that the customer 60 has selected credit card payment.

[0153] The payment execution instruction unit 503 instructs the server device 30 to execute the payment (step S103). At this time, the payment execution instruction unit 503 outputs a payment processing request to the server device 30, including the membership code of the customer 60, the transaction ID, and the product registration information.

[0154] The payment completion information acquisition unit 504 determines whether payment completion information indicating that payment has been completed has been acquired from the server device 30 (step S104). If it is determined that payment completion information has been acquired (step S104: Yes), the process proceeds to step S105. On the other hand, if it is not determined that payment completion information has been acquired (step S104: No), step S104 is repeated.

[0155] If it is determined in step S104 that payment completion information has been acquired, the payment completion information output unit 506 outputs the payment completion information and payment details to the mobile terminal 10 (step S105). After that, the checkout device 50 ends the processing in FIG.

[0156] (Processing flow performed by the server device) The flow of the process performed by the server device 30 is the same as the flow of the process performed by the server device 30 described in the second embodiment (see FIG. 15).

[0157] (Modification of the third embodiment) In the third embodiment, when the checkout device 50 receives payment completion information from the server device 30 indicating that the payment has been completed, the checkout device 50 may warn the customer 60 about forgetting to receive the attachments and provide information about where to receive the attachments. Specifically, the checkout device 50 displays the notification screen shown in FIG. 8 on the touch panel. This allows the customer 60 to reliably receive the attachments even if they are placed far from the checkout device 50.

[0158] In this case, the mobile terminal 10 may not warn the customer 60 about forgetting to pick up the attachments when the payment is completed, and may warn the customer 60 about forgetting to pick up the attachments and provide the location to pick up the attachments only if the customer 60 leaves the store without picking up the attachments.

[0159] (Effects of the embodiment) As described above, the mobile terminal 10 (an example of a product sales data processing device) of the embodiment includes a product registration unit 103 that acquires identification information of a product to be purchased and registers the product, a payment instruction unit 105 that accepts payment instructions for the registered product and requests payment processing, and a notification unit 107 that, after the payment processing is completed, warns the customer against forgetting to receive accessories required for consuming the product and notifies the customer of the location where the accessories can be received. Therefore, it is possible to reliably prevent the customer from forgetting to receive accessories for the purchased product.

[0160] Moreover, the mobile terminal 10 (an example of a product sales data processing device) of the embodiment further includes an attachment receipt completion confirmation unit 108 that acquires information indicating that the receipt of attachments has been completed, and a current location estimation unit 109 that estimates the location of the mobile terminal 10 in the store, and the notification unit 107 issues a notification on the condition that the information indicating that the receipt of attachments has been completed is not acquired and it is estimated that the mobile terminal 10 is outside the store. Therefore, it is possible to more reliably prevent customers from forgetting to receive attachments for purchased products.

[0161] Furthermore, the mobile terminal 10 (an example of a product sales data processing device) of the embodiment further includes an attachment reception setting unit 101 for setting whether to receive attachments or not, and the notification unit 107 issues a notification on the condition that the setting to receive attachments has been made. Therefore, it is possible to prevent unnecessary notifications from being issued to customers who have no intention of receiving attachments.

[0162] Furthermore, the mobile terminal 10 (an example of a product sales data processing device) of the embodiment further includes an attachment receipt confirmation unit 110 that acquires information instructing whether to receive attachments when a product is registered, provided that the product registered by the product registration unit 103 is a product that requires attachments, and an attachment quantity calculation unit 104 that adds the required quantity of attachments, provided that the registered product requires attachments. The attachment quantity calculation unit 104 adds the required quantity of attachments, provided that information indicating that attachments will be received has been acquired. Therefore, the customer can select whether to receive attachments for each product that requires attachments, thereby allowing a more appropriate receipt quantity to be calculated.

[0163] Furthermore, the mobile terminal 10 (an example of a product sales data processing device) of the embodiment displays a map showing the location where the attachments can be received when the payment process is completed. Therefore, the customer can receive the attachments without getting lost no matter where in the store the payment process is performed.

[0164] Although the embodiments of the present invention have been described above, these embodiments are merely examples and are not intended to limit the scope of the invention. This novel embodiment can be embodied in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included within the scope and spirit of the invention, and are also included in the inventions and their equivalents as defined in the claims. [Explanation of symbols]

[0165] 10 Mobile terminal (product sales data processing device) 12 Wireless communication unit 13 Router 14 In-store network 21 Control section 22 Memory section 23 Display Devices 24 Operating Devices 25 Camera 26 Speaker 27 Positioning Devices 28 Communication Interface 30 Server device 40, 41, 42 Product sales data processing system 50 Accounting Device 52 Scanner 60 customers 62 Shopping Cart 64 Shopping Cart 81 Receipt setting button 82 No receipt setting button 83 Back button 84 Delete button 85 Checkout button 86 Scroll button 87 Attachment quantity 88 Pickup location display button 89 Attachment receipt completion button 90 Pick-up location 91 beeps 92 Receive button 93 No receipt required button 101 Attachment receiving setting section 102 Code information acquisition unit 103 Product Registration Department 104 Attachment Quantity Calculation Department 105 Payment Instruction Section 106 Payment completion information acquisition unit 107 Information Department 108 Attachment receipt completion confirmation section 109 Current position estimation section 110 Attachment Receipt Confirmation Section 111 Code information display section 112 Product registration information output section 221 Control Program 222 Product Master 223 Product Registration File 501 Code information reading unit 502 Payment Method Acquisition Department 503 Payment execution instruction unit 504 Payment completion information acquisition unit 505 Product Registration Information Acquisition Department 506 Payment completion information output section N Network [Prior art documents] [Patent documents]

[0166] [Patent Document 1] International Publication No. 2020 / 189155

Claims

1. A product sales data processing device configured as a mobile terminal, a product registration unit that acquires identification information of a product to be purchased and registers the product; a payment instruction unit that receives payment instructions for the registered products and requests payment processing; a notification unit that, after the payment process is completed, draws attention to the fact that an attachment necessary for consuming the product has been forgotten to be received and notifies the user of a location where the attachment can be received; A product sales data processing device comprising:

2. The product sales data processing device includes: an attachment reception completion confirmation unit that acquires information indicating that reception of the attachment has been completed; a current location estimation unit that estimates the location of the mobile terminal in the store, the notification unit issues the notification on the condition that the mobile terminal is estimated to be outside the store in a state where information indicating that the attachment has been received has not been acquired. The product sales data processing device according to claim 1 .

3. The product sales data processing device includes: The device further includes an attachment reception setting unit for setting whether to receive the attachment or not, The notification unit issues the notification on the condition that a setting to receive the attachment has been made.

3. The product sales data processing device according to claim 1.

4. The product sales data processing device includes: an attachment receipt confirmation unit that, when the product registered by the product registration unit is a product that requires the attachment, acquires information instructing whether or not to receive the attachment; an attachment quantity calculation unit that adds a required quantity of the attachment on the condition that the registered product requires the attachment; Further provided with the attachment quantity calculation unit adds the required quantity of the attachment on the condition that information indicating that the attachment will be received is acquired; 3. The product sales data processing device according to claim 1.

5. When the payment process is completed, the mobile terminal displays a map showing the location where the attachment can be received.

3. The product sales data processing device according to claim 1.

6. A product sales data processing system including a mobile terminal and a server device, The mobile terminal a product registration unit that acquires identification information of a product to be purchased and registers the product; a payment instruction unit that receives payment instructions for the registered products and requests payment processing; a payment completion information acquisition unit that acquires information indicating that payment has been completed; a notification unit that, after the payment process is completed, warns the user that an attachment necessary for consuming the product has been forgotten and notifies the user of a location where the attachment can be received; Equipped with The server device a payment processing unit that receives the payment processing request and requests payment processing for the registered product; a payment completion information output unit that outputs information indicating that the payment process has been completed to the mobile terminal; A product sales data processing system comprising:

7. A computer that controls a product sales data processing device configured as a mobile terminal, a product registration unit that acquires identification information of a product to be purchased and registers the product; a payment instruction unit that receives payment instructions for the registered products and requests payment processing; a notification unit that, after the payment process is completed, warns the user that an attachment necessary for consuming the product has been forgotten and notifies the user of a location where the attachment can be received; A program that makes it work.

Images