JP2025021500A - Product sales data processing device, product sales data processing system and program - Google Patents

Abstract

To provide a technology that can prevent a customer from forgetting to receive accessories for a purchased product.
[Solution] A product sales data processing device configured as a mobile terminal includes a product registration unit that acquires identification information of a product to be purchased and registers the product, a payment instruction unit that accepts payment instructions for the registered product and requests payment processing, and a notification unit that, after the payment processing is completed, alerts the user to the possibility of forgetting to pick up any accessories required when consuming the product and notifies the user of the location where the attachments can be picked up.
[Selection diagram] Figure 9

Description

Embodiments of the present invention relate to a product sales data processing device, a product sales data processing system, and a program.

Conventionally, devices that assist with the delivery of accessories such as chopsticks and spoons for purchased products in stores are known (for example, Patent Document 1).

Patent Document 1 discloses a device that prevents store clerks from forgetting to attach accessories to customers. Such devices are applied when making face-to-face sales using POS terminals and the like. Recently, product sales data processing devices that allow customers to register products and make payments by themselves using mobile terminals such as smartphones and tablet terminals are becoming more widespread. When using such product sales data processing devices, customers can carry out payment processing anywhere in the store, so there is a need to provide more reliable guidance to customers to ensure that they do not forget to remove any accessories.

The problem that this invention aims to solve 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 that accompany purchased products.

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 the product to be purchased and registers the product. The payment instruction unit accepts payment instructions related to the registered product and requests payment processing. After the payment processing is completed, the notification unit issues a warning to the user that attachments necessary for consuming the product have been forgotten to be received, and notifies the user of the location to receive the attachments.

FIG. 1 is a schematic diagram of a product sales data processing system according to an embodiment. FIG. 2 is a hardware block diagram showing an example of a hardware configuration of a mobile terminal. FIG. 3 is a diagram illustrating an example of a data structure of the product master. 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 a 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 receiving location guide screen displayed on a mobile terminal. 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. FIG. 9 is a functional block diagram showing an example of a functional configuration of a product sales data processing system. FIG. 10 is a flowchart illustrating an example of a flow of a process performed by the product sales data processing system according to the embodiment. FIG. 11 is a functional block diagram showing the functional configuration of a modified example of the product sales data processing system. FIG. 12 is a diagram showing an example of an attachment receipt confirmation screen displayed on a mobile terminal in the modified example of the product sales data processing system. FIG. 13 is a schematic configuration diagram of a product sales data processing system according to the second embodiment. FIG. 14 is a functional block diagram illustrating an example of a functional configuration of a product sales data processing system according to the second embodiment. FIG. 15 is a flowchart showing an example of the flow of processing performed by the product sales data processing system of the second embodiment. FIG. 16 is a schematic configuration diagram of a product sales data processing system according to the third embodiment. FIG. 17 is a functional block diagram illustrating an example of a functional configuration of a product sales data processing system according to the third embodiment. 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.

(First embodiment)
Hereinafter, a first embodiment will be described in detail with reference to the drawings. Note that the present invention is not limited to the embodiment described below.

(General configuration of product sales data processing system)
The schematic configuration of a product sales data processing system 40 according to an embodiment will be described with reference to Fig. 1. Fig. 1 is a schematic configuration diagram of a product sales data processing system according to an embodiment.

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

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. 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 and performs shopping. The mobile terminal 10 reads identification information that specifies the product to be purchased by the customer 60, registers the product, and transmits product registration information to the server device 30. The mobile terminal 10 also accepts payment instructions related to the registered products and requests payment processing from the server device 30, for example.

In addition, when the product purchased by the customer 60 requires cutlery such as chopsticks and spoons, the mobile terminal 10 warns the customer 60 not to forget to pick up the cutlery and notifies the customer of the location where the cutlery can be picked up when the payment process is completed. The mobile terminal 10 may also inform the customer 60 of the required number of cutlery. Furthermore, when the customer 60 leaves the store without picking up the cutlery, the mobile terminal 10 warns the customer not to forget to pick up the cutlery. Note that the cutlery is not limited to chopsticks and spoons, but may be accessories required when consuming the product, such as knives and forks. In the following description, cutlery is referred to as accessories. In addition to cutlery, accessories in this disclosure also include paper plates, paper napkins, etc. required when consuming the product. Note that the mobile terminal 10 is an example of a product sales data processing device in this disclosure.

The server device 30 manages the product registration information registered on 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 on the mobile terminal 10, and records the membership code, transaction ID, and product registration information in association with each other. Then, when the server device 30 acquires a payment processing request from the mobile terminal 10, it requests the payment processing from a payment server (not shown), and when the payment processing by the payment server is completed, it sends a payment completion notification to the mobile terminal 10.

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.

Network N is an information and communications network such as the Internet or an intranet.

The wireless communication units 12 are connected to the in-store network 14 and installed in multiple locations within the store. The wireless communication units 12 establish wireless communication between the mobile terminals 10 and the server device 30.

The router 13 is a relay device that establishes network communication between the mobile terminal 10 and the server device 30.

(Mobile terminal 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.

The mobile terminal 10 includes a control unit 21, a memory 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.

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 and various tables. The RAM 213 expands control programs and various data when the CPU 211 performs various processes, and functions as a work memory.

The memory unit 22 stores a control program 221, a product master 222, and a product registration file 223.

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.

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

The product registration file 223 is a file in which product information registered for purchase by the customer 60 is registered. The product registration file 223 includes at least the product name, unit price, quantity, and total price.

The display device 23 is equipped with a liquid crystal panel or an organic EL panel, and displays various operation screens and information screens.

The operation device 24 is, for example, a touch panel stacked on the display device 23, which acquires operation information from the customer 60.

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

The speaker 26 outputs beeps, voice guidance, etc. to the customer 60.

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 GPS signals, or a beacon receiver that receives signals from beacons installed in a store.

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

Although the hardware configuration of the server device 30 is not shown, the server device 30 has a computer configuration including a CPU, ROM, RAM, and a storage unit, similar to the mobile terminal 10.

(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.

The product master 222 is a master file for storing and managing information related to all products handled in the store. The contents of the product master 222 are updated on an ongoing basis 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, and keeps the contents of the product master 222 always up to date.

The product master 222 stores product information such as product name, unit price, additional information, and attachment information in association with the product code of the product handled 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 the like. The additional information field may also store image data of the product corresponding to the product code. The attachment information field stores information indicating whether the product requires an attachment and the specific contents of the required attachment (chopsticks, spoon, fork, knife, paper plate, paper napkin, etc.). The product master 222 may store information other than the information shown in FIG. 3.

(Examples of mobile device operation and screen display)
An example of the operation of the mobile terminal 10 will be described with reference to Figs. 4 to 8, taking 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 guide screen displayed on the mobile terminal. Fig. 8 is a diagram showing an example of a notification screen displayed on the mobile terminal when leaving the store without receiving the attachments.

When a customer 60 enters a store, the customer 60 performs a check-in process using the mobile terminal 10. The check-in process is performed, for example, when entering 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 process 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.

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

The attachment reception settings screen displays a reception settings button 81, a no reception settings button 82, and a back button 83.

The Receiving Settings button 81 is a button for setting to receive all attachments. When the Receiving Settings 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 number of attachments assuming that all attachments will be received. In addition, when the Receiving Settings button 81 is pressed, the mobile terminal 10 warns the customer not to forget to receive attachments and notifies the customer of the location where the attachments can be received when the payment process is completed. The mobile terminal 10 may also notify the customer of the required number of attachments. This will be described in more detail later (see Figures 6 and 7).

The "No attachments required" setting button 82 is a button for setting the product 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. In addition, when the payment process is completed, the mobile terminal 10 does not warn the customer about forgetting to receive attachments, nor notify the customer of the location where the attachments can be received.

The back button 83 is a button that exits the attachment receiving settings screen and transitions to, for example, the main menu screen.

The customer 60 picks up the product he or she wishes to purchase and holds the code symbol, such as a barcode, attached to the product up to 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.

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 matched product is registered as product registration information. At this time, the product registration screen shown in FIG. 5 is displayed on the display device 23 of the mobile terminal 10.

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

The product information displayed on the product registration screen includes the product name, a number indicating the registration order of the product, 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.

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 corresponding product and returns the product that was added to the shopping cart 64 to the sales floor.

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

The scroll button 86 is a button for scrolling the displayed product information when multiple products are registered. The scroll buttons 86 are 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 in the upward direction of 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 in the downward direction of 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 and down on the product registration screen.

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, the payment completion screen shown in FIG. 6 is displayed on the display device 23 of the mobile terminal 10.

If the customer 60 has set up the receipt of attachments on the attachment receipt setting screen shown in FIG. 4, the payment completion screen displays a notice of payment completion, the number of attachments 87, a back button 83, a receipt location display button 88, and an attachment receipt completion button 89.

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

Attachment quantity 87 is the quantity of attachments required. It is preferable to notify attachment quantity 87 by type of attachment.

The back button 83 is a button that exits the payment completion screen and transitions to, for example, the main menu screen.

The reception location display button 88 is a button that displays the reception location of the attachments. When the customer 60 does not know the reception location of the attachments, the customer 60 presses the reception location display button 88. When the reception location display button 88 is pressed, the mobile terminal 10 displays the attachment reception location guide screen shown in FIG. 7. Attachments are generally placed near the cash register or at the service counter of the store. However, since a customer using the mobile terminal 10 can perform the payment process at any location in the store, it is expected that the customer will be confused about the reception location of the attachments. In such a case, the customer 60 can receive the attachments reliably by having the mobile terminal 10 display the reception location of the attachments. Note that in this embodiment, the reception location of the attachments is displayed by having the customer 60 press the reception location display button 88, but the reception location of the attachments may be automatically displayed when the payment process is completed.

The attachments receipt completion button 89 is a button that the customer 60 is prompted to press when they have finished receiving the attachments. The customer 60 presses the attachments receipt completion button 89 when they have received the attachments at the attachments receiving location. This causes the mobile terminal 10 to determine that the customer 60 has finished receiving the attachments.

When the pick-up location display button 88 is pressed on the payment completion screen, the display device 23 of the mobile terminal 10 displays the attachment pick-up location information screen shown in FIG. 7.

The attachment receiving location information screen displays the receiving location 90, the attachment quantity 87, an attachment receiving completion button 89, and a back button 83.

The pick-up location 90 is a map showing the pick-up location in the store for the attachment. The current location of the mobile terminal 10 is also displayed in the pick-up location 90. The mobile terminal 10 measures its own current location in the store using the positioning device 27 described above.

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

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

The notification screen displays a message indicating that attachments have been forgotten to be received. The notification screen also displays the number of attachments 87, a reception location display button 88, an attachment reception completion button 89, and a back button 83.

When the notification screen shown in FIG. 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.

When the attachment receipt completion button 89 is not pressed, i.e., when the attachments have 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 attachments), the mobile terminal 10 displays the notification screen shown in FIG. 8.

When customer 60 notices the notification screen, he or she returns to the store to pick up the attached items.

(Functional configuration of product sales data processing system)
The functional configuration of the product 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 product sales data processing system.

(Functional configuration of mobile terminal)
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 the attachment reception setting unit 101, the code information acquisition unit 102, the product registration unit 103, the attachment quantity calculation unit 104, the payment instruction unit 105, the payment completion information acquisition unit 106, the notification unit 107, the attachment reception completion confirmation unit 108, and the current location estimation unit 109 as functional parts shown in Fig. 9. However, some of these functional parts may be handled by the server device 30, not the mobile terminal 10.

The attachment reception setting unit 101 sets whether to receive attachments or not to receive attachments. Specifically, when the attachment reception setting unit 101 detects that the reception setting button 81 displayed on the mobile terminal 10 has been pressed, it sets the unit to receive all attachments that come with the product to be purchased. In addition, when the attachment reception setting unit 101 detects that the no reception setting button 82 displayed on the mobile terminal 10 has been pressed, it sets the unit to not receive any attachments that come with the product to be purchased.

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.

The product registration unit 103 obtains product information 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.

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.

When the payment instruction unit 105 detects that the checkout button 85 displayed on the mobile terminal 10 has been pressed, it requests the server device 30 to perform payment processing. In addition, the payment instruction unit 105 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 the payment.

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.

When the payment process is completed, the notification unit 107 issues a warning to the user not to forget 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.

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

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

(Functional configuration of the 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.

The payment processing unit 301 determines whether a payment processing request has been received from the mobile terminal 10. The payment processing unit 301 also 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 that have been received from the mobile terminal 10.

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.

(Processing flow of 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 flow chart 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 to receive all attachments that come with the product to be purchased.

(Flow of processing performed by a mobile device)
The customer 60 photographs the code symbol affixed to the product to be purchased with the camera 25. The product registration unit 103 then recognizes the product code recorded in the code symbol photographed by the camera 25 and collates 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).

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 determined that the registered product does not require 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.

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.

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

When it is determined in step S14 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).

The payment completion information acquisition unit 106 determines whether payment completion information and information indicating the payment details have been acquired from the server device 30 (step S16). If it is determined that payment completion information and information indicating the 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 the payment details have been acquired from the server device 30 (step S16: No), the determination of step S16 is repeated.

When it is determined in step S16 that payment completion information and information indicating the payment details have been obtained 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.

If it is determined in step S17 that the product purchased by the customer 60 includes a product that requires attachments, the notification unit 107 warns the customer 60 not to forget to receive the attachments and notifies the customer 60 of the location where the attachments can be received (step S18). This ensures that the attachments are received even if the customer 60 issues a payment instruction anywhere in the store (i.e., even if the attachments are not near the customer 60). Furthermore, in step S18, the notification unit 107 may notify the customer of the number of attachments to be received.

The attachments receipt completion confirmation unit 108 determines whether the attachments receipt completion button 89 displayed on the mobile terminal 10 has been pressed (step S19). If it is determined that the attachments receipt completion button 89 has been pressed (step S19: Yes), the mobile terminal 10 ends the process in FIG. 10. On the other hand, if it is not determined that the attachments receipt completion button 89 has been pressed (step S19: No), the process proceeds to step S20.

If it is not determined in step S19 that the attachment receipt completion button 89 has 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 attachments) (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.

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 pick-up location (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.

(Flow of processing performed by the server device)
The payment processing unit 301 judges whether a payment processing request has been received from the mobile terminal 10 (step S31). If it is judged 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 judged that a payment processing request has been received (step S31: No), the process repeats step S31.

When it is determined in step S31 that a payment processing request has been acquired, the payment processing unit 301 requests payment processing from a payment server (not shown) (step S32).

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. 10.

(Modification of the product sales data processing system of the first embodiment)
A modified example of the product 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 product sales data processing system.

The product sales data processing system 40, which is a first variant of the embodiment, asks the customer whether or not he or she would like to receive attachments each time the customer registers a product to be purchased, if the registered product requires attachments.

The product sales data processing system 40, which is a first modified example of the embodiment, includes a mobile terminal 10 and a server device 30.

The mobile terminal 10 has an attachment receipt confirmation unit 110 instead of the attachment receipt setting unit 101 in the functional configuration of the mobile terminal 10 described above (see FIG. 9). The functions of the other functional parts shown in FIG. 11 are as described in FIG. 9.

The attachment receipt confirmation unit 110 obtains information from the customer 60 instructing whether to receive 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 on the mobile terminal 10 to input information to the effect that he or she will receive attachments, the attachment receipt confirmation unit 110 determines that the customer 60 will receive the attachments of the product registered at that time. Also, when the customer 60 performs an operation on the mobile terminal 10 to input information to the effect that he or she will not receive attachments, the attachment receipt confirmation unit 110 determines that the customer 60 will not receive the attachments of the product registered at that time. A specific operation example will be described later (see FIG. 12).

The mobile terminal 10 may further include an attachment reception setting unit 101 in addition to the configuration of FIG. 11. Then, only when the attachment reception setting unit 101 has set the attachment to be received, the attachment reception confirmation unit 110 may confirm whether the customer 60 will receive the attachment when the customer 60 registers a product that requires an attachment.

Furthermore, the attachment reception setting unit 101 may allow the user 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.

(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 with reference to 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.

When a customer 60 who is shopping registers a product that requires an attachment, the display device 23 of the mobile terminal 10 displays the attachment receipt confirmation screen shown in FIG. 12.

The attachment receipt confirmation screen displays a Delete button 84, a Receive button 92, and a No need to receive button 93. The function of the Delete button 84 is as described above.

The receive button 92 is a button that instructs the user 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.

The No Receive button 93 is a button that indicates not to receive any attachments for the currently registered product. When the No 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.

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).

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 showing the configuration of the merchandise sales data processing system according to the second embodiment.

The product sales data processing system 41 includes a mobile terminal 10, an accounting device 50, and a server device 30.

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 acquires identification information that identifies the product that the customer 60 purchases and registers the product. When the product registration is complete, the mobile terminal 10 receives an instruction from the customer 60 and generates code information in which the customer 60's membership number and transaction ID are embedded. 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 own screen. The customer 60 causes the scanner 52 connected to the accounting device 50 to read the code information displayed on the mobile terminal 10, and causes the accounting device 50 to acquire the product registration information from the server device 30.

The accounting device 50 performs a payment process for the product purchased by the customer 60. A scanner 52 is connected to the accounting device 50. The scanner 52 reads the code information displayed on the screen of the mobile terminal 10. The scanner 52 is configured separately from the accounting device 50, but may be configured integrally with the accounting device 50. The accounting 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 registered by the customer 60 using the mobile terminal 10 based on the membership code and transaction ID. The accounting device 50 also accepts instructions on the payment method from the customer 60. When the accounting device 50 accepts an instruction for cash payment from the customer 60, it performs payment by collecting coins or bills using a change machine (not shown) provided in the accounting device 50. In addition, when the accounting device 50 receives an instruction from the customer 60 to make a card payment 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 makes a payment processing request to the server device 30.

Furthermore, when the product purchased by the customer 60 requires attachments, the accounting device 50 warns the customer 60 not to forget to receive the attachments and informs the customer 60 of the location where the attachments can be received when the payment process is completed. The accounting 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 not to forget to receive the attachments if the customer 60 leaves the store without receiving the attachments. That is, in the second embodiment, the accounting device 50 or the mobile terminal 10 is an example of a product sales data processing device in the present disclosure.

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

The server device 30 communicates with the accounting device 50 to request a payment server (not shown) to perform payment processing, such as credit card payment. More specifically, the server device 30 obtains a payment processing request from the accounting device 50. In doing so, the server device 30 obtains from the accounting device 50 the membership code of the customer 60, a transaction ID that uniquely identifies one transaction, and product registration information for the product that is the subject of the payment processing. Then, when the payment is completed, the server device 30 outputs payment completion information to the accounting 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 and the payment details.

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.

(Functional configuration of the product sales data processing system according to the second embodiment)
The functional configuration of the product 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 product sales data processing system of the second embodiment.

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

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.

(Functional configuration of accounting device)
Next, a description will be given of the functional configuration of the transaction device 50. The transaction 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.

The code information reading unit 501 decodes the code information read by the scanner 52 to obtain the customer 60's membership code and transaction ID.

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

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 accounting device 50 itself can perform the payment processing, such as cash payment, it executes the payment processing.

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

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

(Flow of processing performed by the product sales data processing system of the second embodiment)
The flow of processing performed by the product sales data processing system 41 will be described with reference to Fig. 15. Fig. 15 is a flow chart showing an example of the flow of processing performed by the product 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 to receive all attachments that come with the product to be purchased. Fig. 15 also shows the flow of processing when the customer 60 selects credit card payment.

(Flow of processing performed by a mobile device)
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).

(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), the process repeats step S61.

When it is determined in step S61 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).

Next, the payment method acquisition unit 502 acquires the payment method selected by the selection operation of the customer 60 (step S63). In this example, it is assumed that the customer 60 has selected credit card payment.

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 customer 60's membership code, transaction ID, and product registration information.

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 the payment details have been acquired (step S65: Yes), the accounting device 50 ends the process in FIG. 15. On the other hand, if it is not determined that the payment completion information and the payment details have been acquired (step S65: No), step S65 is repeated.

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

(Modification of the second embodiment)
In the second embodiment, when the accounting device 50 receives payment completion information indicating that the payment has been completed from the server device 30, the accounting device 50 may notify the customer 60 of the location where the attachments are to be received and to warn the customer that the attachments have been forgotten. Specifically, the accounting 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 the attachments are placed in a location far from the accounting device 50.

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.

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.

The product sales data processing system 42 includes a mobile terminal 10, an accounting device 50, a store server 56, and a server device 30.

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 that contains a shopping basket 64 and goes shopping. The mobile terminal 10 reads identification information that identifies the product the customer 60 purchases and registers the product. The mobile terminal 10 also accepts a payment instruction for the registered product and transmits the product registration information to the accounting device 50 in addition to a membership code that identifies the customer 60 and a transaction ID that uniquely identifies one transaction.

As described in the first embodiment, when the product purchased by the customer 60 requires attachments, the mobile terminal 10 warns the customer 60 not to forget to receive the attachments and notifies the customer 60 of the location where the attachments can be received when the payment process is completed. The mobile terminal 10 may also inform 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 not to forget to receive the attachments. The mobile terminal 10 is an example of a product sales data processing device in this disclosure.

The accounting device 50 acquires the customer 60's membership code, transaction ID, and product registration information from the mobile terminal 10. The accounting device 50 then performs payment processing for the products purchased by the customer 60. When the accounting device 50 receives an instruction from the customer 60 to make a cash payment, it performs the payment by collecting coins or bills using a change dispenser (not shown) that the accounting device 50 is equipped with. When the accounting device 50 receives an instruction from the customer 60 to make a credit card payment, it outputs the customer 60's membership code, transaction ID, and product registration information to the server device 30 and has the server device 30 perform the payment processing.

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

The accounting 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.

The store server 56 is a repeater for communication between the mobile terminal 10 and the accounting device 50. That is, the membership code, transaction ID, and product registration information of the customer 60 output by the mobile terminal 10 are sent to the accounting device 50 via the store server 56. The store server 56 selects an accounting device 50 that is not being used by the customer 60 from among multiple accounting devices 50, and transmits the membership code, transaction ID, and product registration information to the available accounting device 50. Note that if only one accounting device 50 is placed in the store, the store server 56 does not need to be provided.

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

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, etc.

(Functional configuration of the product sales data processing system according to the third embodiment)
The functional configuration of the product 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 product sales data processing system of the third embodiment.

(Functional configuration of mobile terminal)
First, the functional configuration of the mobile terminal 10 will be described. The mobile terminal 10 has a product registration information output unit 112 instead of the payment instruction unit 105 in comparison with the functional configuration of the mobile terminal 10 described above (see FIG. 9). The actions of the other functional parts shown in FIG. 17 are as described in FIG. 9.

The product registration information output unit 112 outputs the membership code identifying the customer 60, the transaction ID, and the product registration information to the accounting device 50 via the store server 56.

(Functional configuration of accounting device)
Next, the functional configuration of the accounting device 50 will be described. The accounting device 50 has the functional configuration described above (see FIG. 14 ), but with a product registration information acquisition unit 505 instead of the code information reading unit 501. The product registration information acquisition unit 505 acquires the membership code, transaction ID, and product registration information of the customer 60 from the mobile terminal 10 via the store server 56.

The accounting 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.

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

(Processing flow performed by the product sales data processing system of the third embodiment)
The flow of processing performed by the product sales data processing system 42 will be described with reference to Fig. 18. Fig. 18 is a flow chart showing an example of the flow of processing performed by the product sales data processing system of the third embodiment. It is assumed that the customer 60 operates the mobile terminal 10 in advance to set up to receive all attachments that come with the product to be purchased. Fig. 18 also shows the flow of processing when the customer 60 selects credit card payment.

(Flow of processing performed by a mobile device)
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 FIG. 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 membership code, transaction ID, and product registration information of the customer 60 are output to the accounting device 50 (step S85 in FIG. 18).

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

When it is determined in step S101 that the customer 60's membership code, transaction ID, and product registration information have been acquired, the payment method acquisition unit 502 acquires the payment method selected by the customer 60's selection operation (step S102). Note that in this example, it is assumed that the customer 60 has selected credit card payment.

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 customer 60's membership code, transaction ID, and product registration information.

The payment completion information acquisition unit 504 determines whether payment completion information indicating that the 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.

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 the payment details to the mobile terminal 10 (step S105). After that, the accounting device 50 ends the process of FIG. 18.

(Flow of processing 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).

(Modification of the third embodiment)
In the third embodiment, when the accounting device 50 receives payment completion information indicating that the payment has been completed from the server device 30, the accounting device 50 may notify the customer 60 of the location where the attachments are to be received and to warn the customer that the attachments have been forgotten. Specifically, the accounting 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 the attachments are placed in a location far from the accounting device 50.

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.

(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 related to the registered product and requests payment processing, and a notification unit 107 that, after the payment processing is completed, calls attention to the forgetting of attachments necessary for consuming the product and notifies the receiving location of the attachments. Therefore, it is possible to reliably prevent a customer from forgetting to receive attachments for a purchased product.

The mobile terminal 10 of the embodiment (an example of a product sales data processing device) 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 mobile terminal 10 is estimated to be outside the store when no information indicating that the receipt of attachments has been acquired. This makes it possible to more reliably prevent customers from forgetting to receive attachments for purchased products.

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.

The mobile terminal 10 of the embodiment (an example of a product sales data processing device) further includes an attachment receipt confirmation unit 110 that acquires information instructing whether to receive attachments when a product registered by the product registration unit 103 is registered, provided that the product requires attachments, and an attachment quantity calculation unit 104 that adds the required quantity of attachments, provided that the registered product requires attachments, and 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, allowing a more appropriate quantity to be calculated.

In addition, 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, no matter where in the store the payment process is performed, the customer can receive the attachments without getting lost and without worrying about the location where the attachments can be received.

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 new embodiment can be implemented in a variety of 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 included in the scope of the invention and its equivalents as set forth in the claims.

10 Mobile terminal (product sales data processing device)
12 Wireless communication unit 13 Router 14 In-store network 21 Control unit 22 Memory unit 23 Display device 24 Operation device 25 Camera 26 Speaker 27 Positioning device 28 Communication interface 30 Server device 40, 41, 42 Product sales data processing system 50 Accounting device 52 Scanner 60 Customer 62 Shopping cart 64 Shopping basket 81 Receipt setting button 82 No receipt setting button 83 Back button 84 Delete button 85 Accounting button 86 Scroll button 87 Attachment quantity 88 Receipt location display button 89 Attachment receipt completion button 90 Receipt location 91 Beep 92 Receipt button 93 No receipt button 101 Attachment receipt setting unit 102 Code information acquisition unit 103 Product registration unit 104 Attachment quantity calculation unit 105 Settlement instruction unit 106 Payment completion information acquisition unit 107 Notification unit 108 Attachment receipt completion confirmation unit 109 Current location estimation unit 110 Attachment receipt confirmation unit 111 Code information display unit 112 Product registration information output unit 221 Control program 222 Product master 223 Product registration file 501 Code information reading unit 502 Payment method acquisition unit 503 Payment execution instruction unit 504 Payment completion information acquisition unit 505 Product registration information acquisition unit 506 Payment completion information output unit N Network

International Publication No. 2020/189155

Claims (7)

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 a payment instruction for the registered product and requests a payment process;
a notification unit that, after the payment process is completed, calls the user's 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 to receive the attachment;
A product sales data processing device comprising: The product sales data processing device includes:
an attachment receipt completion confirmation unit that acquires information indicating that receipt of the attachment has been completed;
a current location estimation unit that estimates a 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 in which information indicating that the receipt of the attachment has been completed is not acquired.
The product sales data processing device according to claim 1 . 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 to receive the attachment,
The notification unit performs the notification on the condition that a setting to receive the attachment has been made.
3. A product sales data processing device according to claim 1 or 2. The product sales data processing device includes:
an attachment receipt confirmation unit that acquires information instructing whether to receive the attachment when the product registered by the product registration unit is a product that requires 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 comprising:
The attachment quantity calculation unit adds a required quantity of the attachment on condition that information indicating receipt of the attachment is acquired.
3. A product sales data processing device according to claim 1 or 2. When the payment process is completed, the mobile terminal displays a map showing a location where the attachment can be received.
3. A product sales data processing device according to claim 1 or 2. A product sales data processing system comprising a mobile terminal and a server device,
The mobile terminal includes:
a product registration unit that acquires identification information of a product to be purchased and registers the product;
a payment instruction unit that receives a payment instruction for the registered product and requests a payment process;
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, issues a warning to the user that an attachment necessary for consuming the product has been forgotten to be removed and notifies the user of a location to receive the attachment;
Equipped with
The server device includes:
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: 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 a payment instruction for the registered product and requests a payment process;
a notification unit that, after the payment process is completed, calls attention to forgetting to receive an attachment required for consuming the product and notifies a receiving location of the attachment;
A program that makes it work.

Images