Data processing device and control program thereof

Abstract

To make it possible to find out a mismatch between an actually purchased commodity by a consumer and a commodity registered as a purchased item of the consumer.SOLUTION: A data processing device recognizes a purchase action or a return action of a commodity by a consumer. The data processing device identifies the consumer who has made a purchase or return action. The data processing device subtracts data of the commodity from a consumer's purchase list identified as having performed the return action once the return action of the commodity is recognized. When data of the purchase list becomes an abnormal value by subtracting the data of the commodity from the purchase list, the data processing device executes an abnormality processing.SELECTED DRAWING: Figure 3

Description

[Technical field]

[0001] An embodiment of the present invention relates to a data processing device and a control program therefor. [Background technology]

[0002] In recent years, various store systems have been proposed that automatically register products purchased by consumers based on their behavior in the store, eliminating the need to register products at checkout. One such system is a store system that identifies a consumer who takes a product near a shelf when the product is taken from the shelf as the purchaser of that product. For example, by introducing this type of store system in convenience stores and small kiosks, it is possible to realize unmanned stores.

[0003] In the above store system, when an item is returned to a shelf, the consumer who returns the item near that shelf is identified as the returner. However, if multiple consumers take out or return items at almost the same time near the same shelf, there is a risk of an error in identifying the purchaser or returner. If an error occurs, a discrepancy will occur between the item that the consumer actually purchased and the item registered as the consumer's purchased item. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Publication No. 08-190672 [Patent Document 2] JP 2000-123086 A Summary of the Invention [Problem to be solved by the invention]

[0005] The problem to be solved by the embodiments of the present invention is to provide a data processing device that can eliminate inconsistencies between products actually purchased by a consumer and products registered as the consumer's purchased items. [Means for solving the problem]

[0006] In one embodiment, the data processing device includes a recognition means, an identification means, a purchase processing means, a return processing means, and an abnormality processing means. The recognition means recognizes a consumer's product purchasing behavior or return behavior. The identification means identifies the consumer who has performed the purchasing behavior or return behavior. When the recognition means recognizes a product purchasing behavior, the purchase processing means adds data of the product to a purchase list of the consumer identified by the identification means as having performed the purchasing behavior. When the recognition means recognizes a product return behavior, the return processing means subtracts data of the product from the purchase list of the consumer identified by the identification means as having performed the return behavior. The abnormality processing means executes abnormality processing when subtracting data of the product from the purchase list causes data of the purchase list to become abnormal. [Brief description of the drawings]

[0007] [Figure 1] FIG. 2 is a schematic diagram showing a shelf used in the store system according to an embodiment, viewed from the front. [Diagram 2] A schematic diagram of the shelf seen from above. [Diagram 3] FIG. 2 is a block diagram showing a schematic configuration of the store system. [Figure 4] FIG. 4 is a schematic diagram showing an example of a data structure of a product data file. [Diagram 5] FIG. 4 is a schematic diagram showing an example of a data structure of a trace file. [Figure 6] FIG. 4 is a schematic diagram showing an example of a data structure of an association table; [Figure 7] FIG. 4 is a schematic diagram showing an example of a data structure of a purchase list. [Figure 8] FIG. 2 is a block diagram showing the hardware configuration of a shelf control device. [Figure 9] 11 is a flowchart showing an operation procedure of a tracking processing unit. [Figure 10] 4 is a flowchart showing the operation procedure of a personal authentication processing unit. [Figure 11]11 is a flowchart showing an operation procedure of a merchandise monitoring processing unit. [Figure 12] 11 is a flowchart showing an operation procedure of a behavior monitoring processing unit. [Figure 13] 13 is a flowchart showing an operation procedure of an integrated processing unit that receives an authentication notification command. [Figure 14] 11 is a flowchart showing an operation procedure of an integrated processing unit that receives a hand reaching notification command. [Figure 15] 15 is a flowchart showing the procedure of the purchasing process in FIG. 14 . [Figure 16] 15 is a flowchart showing the procedure of the return processing in FIG. 14. [Figure 17] 17 is a flow chart showing the procedure for single-person processing in FIG. 16. [Figure 18] 17 is a flowchart showing the procedure of multiple person processing in FIG. 16; [Figure 19] 13 is a flowchart showing an operation procedure of an integrated processing unit that receives an exit notification command. [Figure 20] 11 is a flowchart showing the operation procedure of a sales management device to which a purchase notification command has been input. [Figure 21] 11 is a flowchart showing the operation procedure of a sales management device to which a return notification command has been input. [Figure 22] 13 is a flowchart showing the operation procedure of a sales management device to which a temporary return notification command has been input. [Figure 23] 13 is a flowchart showing an operation procedure of a sales management device to which a payment permission notification command is input. [Figure 24] 13 is a flowchart showing the operation procedure of the sales management device when a payment confirmation notification command is input. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] Hereinafter, an embodiment of a data processing device will be described with reference to the drawings. In this embodiment, an example is provided of a data processing device in a store system 100 (see FIG. 3) that automatically registers products purchased by consumers by utilizing technology to identify a consumer who takes the action of removing a product near a shelf 10 (see FIG. 1 and FIG. 2) when the product is removed from the shelf 10 as the purchaser of the product.

[0009] First, the shelf 10 used in the store system 100 will be described with reference to FIGS. Fig. 1 is a schematic diagram of shelf 10 as viewed from the front, and Fig. 2 is a schematic diagram of shelf 10 as viewed from above. As shown in Fig. 1, shelf 10 has three levels, divided vertically by two shelf boards. On each level, two types of products are displayed in separate sections. As an example, product A and product B are displayed side by side on the top level, product C and product D are displayed side by side on the middle level, and product E and product F are displayed side by side on the bottom level.

[0010] Hereinafter, the section on the top left where product A is displayed will be referred to as section 201, the section on the top right where product B is displayed as section 202, the section on the middle left where product C is displayed as section 203, the section on the middle right where product D is displayed as section 204, the section on the bottom left where product E is displayed as section 205, and the section on the bottom right where product F is displayed as section 206.

[0011] An item monitoring sensor 1 is attached to each of the sections 201-206 on each level. The item monitoring sensor 1 is a sensor for monitoring an increase or decrease in weight associated with the movement of an item. In this embodiment, a weight sensor capable of measuring the total weight of the items displayed in the corresponding section 201-206 is used as the item monitoring sensor 1.

[0012] 1 and 2, two tracking sensors 21, 22 and one behavior monitoring sensor 3 are attached to the top of the shelf 10. The tracking sensors 21, 22 are attached separately to the left and right sides of the shelf 10. The behavior monitoring sensor 3 is attached to the front side of the shelf 10 along the width direction of the shelf 10 and approximately parallel to the floor surface.

[0013] The tracking sensors 21 and 22 are sensors for tracking the movement of consumers in a rectangular area 111 surrounded by a first boundary line 101 virtually drawn by a two-dot chain line in Fig. 2. Hereinafter, the area 111 will be referred to as a tracking area 111. In this embodiment, camera sensors such as an RGB camera, an IR camera, and an infrared camera capable of capturing images within the tracking area 111 are used as the tracking sensors 21 and 22. Note that the number of tracking sensors 21 and 22 is not limited to two.

[0014] The behavior monitoring sensor 3 is a sensor for monitoring the behavior of a consumer in a rectangular area 112 surrounded by a second boundary line 102 virtually drawn by a dashed line in FIG. 2 with respect to the shelf 10. Specifically, the behavior monitoring sensor 3 monitors the behavior of a consumer in the area 112 reaching out to the shelf 10 and retracting the hand. Hereinafter, the action of reaching out is referred to as a reaching action, and the action of retracting the hand is referred to as a hand-returning action. The area 112 is an area where a consumer is estimated to be located when taking out products A to F from the shelf 10. Hereinafter, the area 112 is referred to as a purchase area 112. The purchase area 112 is inside the tracking area 111. In this embodiment, a TOF (Time of Flight) sensor, a laser radar, or the like is used as the behavior monitoring sensor 3. The number of behavior monitoring sensors 3 is not limited to one.

[0015] As shown in FIG. 1 and FIG. 2, personal authentication devices 41 and 42 are attached to both sides of the shelf 10. The personal authentication devices 41 and 42 are devices for personal authentication of consumers. Consumers who use the store register as members in advance. Member registration is possible by installing a dedicated application program in a user terminal TM (see FIG. 3) such as a smartphone or tablet terminal. By registering as a member, a member ID unique to the consumer is set in the user terminal TM. Hereinafter, this application program is referred to as a shopping application. When the shopping application is started in the user terminal TM in which the member ID is set, a code representing the member ID is displayed on the display of the user terminal TM. The code is expressed, for example, by a barcode system or a two-dimensional code system. The personal authentication devices 41 and 42 are equipped with a reader for reading this code. The number of personal authentication devices 41 and 42 is not limited to two. Furthermore, the installation locations of the personal authentication devices 41 and 42 are not limited to both sides of the shelf 10.

[0016] 2, circular areas 113, 114 surrounded by a third boundary line 103 drawn virtually by a dashed line are areas where a consumer is assumed to enter in order to have the reader of the personal authentication devices 41, 42 read the member ID code displayed on the display of the user terminal TM. Hereinafter, these areas 113, 114 will be referred to as authentication areas 113, 114. The authentication areas 113, 114 are located inside the tracking area 111.

[0017] A fourth boundary line 104 is set between the first boundary line 101 and the second boundary line 102. In FIG. 2, the fourth boundary line 104 is virtually drawn by a dashed line. The store system 100 starts tracking when a consumer enters the tracking area 111. When the consumer enters the fourth boundary line 104 from outside to inside, the store system 100 sets a tracking ID to the consumer. When the consumer moves from inside to outside the fourth boundary line 104 and then goes outside the first boundary line 101, the store system 100 ends tracking of the consumer.

[0018] The first to fourth boundary lines 101 to 104 may be strips having a predetermined width instead of lines. The tracking area 111 and the purchase area 112 may be areas having a shape other than a rectangle. The authentication areas 113 and 114 may be areas having a shape other than a circle.

[0019] The shelf 10 is an example of a product display location. The number of tiers of the shelf 10 and the number of products displayed on each tier are arbitrary. In short, it is sufficient that the shelf has multiple sections in which products are displayed by type, and each section is provided with a product monitoring sensor 1. Therefore, the display location is not limited to a shelf, and may be a display stand, a display case, a display space, etc.

[0020] The tracking sensors 21, 22, the behavior monitoring sensor 3, and the personal authentication devices 41, 42 do not necessarily have to be provided on the shelf 10. For example, the tracking sensors 21, 22 or the behavior monitoring sensor 3 may be provided on the ceiling of a store. The tracking sensors 21, 22 may be provided in a location where they can track the movement of consumers in the tracking area 111. The behavior monitoring sensor 3 may be provided in a location where they can monitor the behavior of consumers in the purchasing area 112 with respect to the shelf 10. The personal authentication devices 41, 42 may be provided, for example, near the entrance of the store.

[0021] Next, the configuration of the store system 100 will be described with reference to FIGS. 3 is a block diagram showing the main parts of the store system 100. The store system 100 includes a shelf control device 6, a sales management device 7, a member server 8, and a payment server 9. The store system 100 interconnects the shelf control device 6, the sales management device 7, the member server 8, and the payment server 9 via a communication network NW such as a LAN (Local Area Network). The store system 100 is capable of wireless communication with a user terminal TM carried by a consumer who visits the store, via an access point AP of the communication network NW.

[0022] The member server 8 manages a member database 81 for storing information related to consumers who have registered as members. The member database 81 stores, in association with each consumer's member ID, the name of the consumer, terminal information of the user terminal TM carried by the consumer, information related to payment registered by the consumer, a validity flag, and the like. The terminal information includes information such as a communication address required for communication with the user terminal TM via the communication network NW. The information related to payment includes information required for card payment using a credit card, an electronic money card, or the like, or electronic payment using a barcode, a two-dimensional code, or the like. The validity flag is one-bit data for identifying whether or not a member ID is valid. In this embodiment, the validity flag of a valid member ID is set to "1", and the validity flag of an invalid member ID is set to "0". For example, the validity flag associated with the member ID of a consumer who has lost membership is set to "0".

[0023] The payment server 9 is a server for carrying out payment processing such as the above-mentioned card payment, electronic payment, etc. The payment server 9 may be connected to a POS (Point Of Sales) terminal and carry out payment processing via the POS terminal. Well-known processing can be applied as is for the payment processing. Therefore, a detailed description will be omitted.

[0024] The shelf control device 6 is an example of a data processing device. The shelf control device 6 has a product data file 61.

[0025] The product data file 61 stores data related to each of the products A to F displayed on the shelf 10. An example of the data structure of the product data file 61 is shown in FIG. 4. As shown in the figure, the product data file 61 stores the product name, unit weight, and sensor number in association with the product code of each of the products A to F. Although not shown, the unit price is also stored in the product data file 61. The unit weight is the weight per product. The sensor number is a number for identifying the product monitoring sensors 1 provided in the sections 201 to 206 of the shelf 10 in which the product is displayed. Each product monitoring sensor 1 is assigned a unique sensor number. Note that the data stored in the product data file 61 is not limited to the above-mentioned items. Data of other items may be stored in the product data file 61.

[0026] The shelf control device 6 has functions as a tracking processing unit 62 , a personal authentication processing unit 63 , a merchandise monitoring processing unit 64 , a behavior monitoring processing unit 65 , a voice synthesis unit 66 and an integration processing unit 67 . The tracking processing unit 62 captures image data from the tracking sensors 21 and 22. The tracking processing unit 62 analyzes this image data and tracks the movement of consumers who are in the tracking area 111. The tracking processing unit 62 stores the movement data for each consumer in a tracking file 68.

[0027] An example of the data structure of the tracking file 68 is shown in FIG. 5. As shown in the figure, the tracking file 68 has an area of ​​a tracking ID, an area of ​​a flow line data 681, and an area of ​​a monitoring flag. The tracking ID is a unique code set by the tracking processing unit 62 to identify the consumer to be tracked. The flow line data 681 describes the tracking position information indicating the location of the consumer to be tracked and the time at that time in a chronological order. The tracking position information is expressed in XY plane coordinates with the origin O(0,0) being the point at the lower left corner of the tracking area 111 in FIG. 2, for example. The monitoring flag is 1-bit data for identifying whether the consumer to be tracked has moved from the inside to the outside of the fourth boundary line 104. In this embodiment, the monitoring flag stored in the tracking file 68 of the consumer who has moved from the inside to the outside of the fourth boundary line 104 is set to "1", and the monitoring flags stored in the other tracking files 68 are set to "0".

[0028] The personal authentication processing unit 63 takes in the data read by the readers of the personal authentication devices 41, 42 and performs processing related to personal authentication of the consumer. The personal authentication processing unit 63 performs processing related to personal authentication in cooperation with the integrated processing unit 67. The personal authentication processing unit 63 outputs the authentication result to the personal authentication devices 41, 42. The personal authentication devices 41, 42 have a function of notifying the authentication result. For example, the personal authentication devices 41, 42 are equipped with a display device and display the authentication result on the display device.

[0029] The merchandise monitoring processing unit 64 takes in weight data from the merchandise monitoring sensor 1. Based on this weight data, the merchandise monitoring processing unit 64 monitors the status of each of the merchandise A-F displayed on the shelf 10. Specifically, when the weight data from the merchandise monitoring sensor 1 decreases, the merchandise monitoring processing unit 64 recognizes that an item has been removed from the section in which the merchandise monitoring sensor 1 is provided. When the weight data from the merchandise monitoring sensor 1 increases, the merchandise monitoring processing unit 64 recognizes that an item has been placed in the section in which the merchandise monitoring sensor 1 is provided. The recognition result by the merchandise monitoring processing unit 64 is provided to the integrated processing unit 67.

[0030] The behavior monitoring processing unit 65 takes in an output signal from the behavior monitoring sensor 3. Based on this output signal, the behavior monitoring processing unit 65 monitors the behavior of the consumer in the purchasing area 112 with respect to the shelf 10. Specifically, when the behavior monitoring sensor 3 detects the consumer's hand inserted into the shelf 10, the behavior monitoring processing unit 65 recognizes this as a reaching behavior, and when the hand is no longer detected, recognizes this as a hand-returning behavior. The recognition result by the behavior monitoring processing unit 65 is provided to the integration processing unit 67. At that time, behavior position information of the point where the behavior monitoring sensor 3 detected the hand is also provided to the integration processing unit 67. The behavior position information is represented by an X coordinate indicating the distance from the origin O of the XY plane coordinates described above, and a Z coordinate indicating the height from the floor surface.

[0031] The voice synthesis unit 66 is connected to the speaker 5. The voice synthesis unit 66 synthesizes voice data under the control of the integrated processing unit 67 and outputs it to the speaker 5. As a result, a voice is emitted from the speaker 5. The speaker 5 is installed near the shelf 10. The speaker 5 may be installed, for example, in a waiting area for a store clerk. Alternatively, the speaker 5 may be built into a terminal carried by the store clerk, and the voice synthesized by the voice synthesis unit 66 may be emitted from the speaker 5. In this case, the voice data synthesized by the voice synthesis unit 66 is transmitted to the access point AP via the communication network NW, and is further transmitted to the store clerk's mobile terminal via wireless communication.

[0032] The integration processing unit 67 cooperates with the merchandise data file 61, the tracking processing unit 62, the personal authentication processing unit 63, the merchandise monitoring processing unit 64, the behavior monitoring processing unit 65, and the voice synthesis unit 66 to perform data processing required for the store system 100. One of the data processing operations is a process of associating a consumer who has been successfully authenticated by the personal authentication processing unit 63 with a consumer whose movement path is being tracked by the tracking processing unit 62. The integration processing unit 67 has an association table 69 as a data table used in this process.

[0033] An example of the data structure of the association table 69 is shown in Fig. 6. As shown in the figure, the association table 69 has an area for storing a consumer's member ID and a tracking ID set for that consumer in association with each other.

[0034] One of the data processes executed by the integrated processing unit 67 is a process for identifying the consumer's behavior with respect to a product based on the tracking results of the tracking processing unit 62 and the monitoring results of the behavior monitoring processing unit 65. Based on the consumer's behavior identified in this process, the integrated processing unit 67 outputs a purchase notification command or a return notification command to the sales management device 7. The purchase notification command and the return notification command will be made clear in the operation explanation given below.

[0035] The sales management device 7 is equipped with a purchase list 71. The purchase list 71 is created for each consumer. An example of the data structure of the purchase list 71 is shown in FIG. 7. As shown in the figure, the purchase list 71 stores the purchased product data of a consumer in association with the consumer's member ID. The purchased product data includes the following items: product code, product name, unit price, quantity, amount, temporary registration flag, and other member ID. The amount is calculated by multiplying the unit price and the quantity. The purchased product data may include items other than the above items.

[0036] When the sales management device 7 receives the purchase notification command, it registers the purchased item data in the purchase list 71. When the sales management device 7 receives the return notification command, it corrects the corresponding purchased item data.

[0037] The provisional registration flag is one-bit data for identifying whether the corresponding purchased product data is provisionally registered data or not. In this embodiment, the provisional registration flag for provisionally registered data is set to "1", and the provisional registration flag for non-provisionally registered data, i.e., fully registered data, is set to "0". If the corresponding purchased product data is provisionally registered, the member ID of another related consumer is added to the purchase list 71 as a different member ID.

[0038] 8 is a block diagram showing the hardware configuration of the shelf control device 6. The shelf control device 6 includes a processor 601, a main memory 602, an auxiliary storage device 603, a clock 604, a communication interface 605, an I / O interface 606, and a system transmission path 607. The processor 601, the main memory 602, the auxiliary storage device 603, the clock 604, the communication interface 605, and the I / O interface 606 are each connected to the system transmission path 607. The system transmission path 607 includes an address bus, a data bus, a control signal line, and the like. In the shelf control device 6, the processor 601, the main memory 602, and the auxiliary storage device 603 are connected by the system transmission path 607 to form a computer for controlling the shelf control device 6.

[0039] The processor 601 corresponds to the central part of the computer. The processor 601 controls each part to realize various functions of the shelf control device 6 according to an operating system or an application program. The processor 601 is, for example, a CPU (Central Processing Unit).

[0040] The main memory 602 corresponds to the main storage portion of the computer. The main memory 602 includes a nonvolatile memory area and a volatile memory area. The main memory 602 stores an operating system or an application program in the nonvolatile memory area. The main memory 602 stores data required for the processor 601 to execute processes for controlling each part in the volatile memory area. The main memory 602 also uses the volatile memory area as a work area where data is appropriately rewritten by the processor 601. The nonvolatile memory area is, for example, a ROM (Read Only Memory). The volatile memory area is, for example, a RAM (Random Access Memory).

[0041] The auxiliary storage device 603 corresponds to the auxiliary storage portion of the computer. As the auxiliary storage device 603, for example, a well-known storage device such as an EEPROM (Electric Erasable Programmable Read-Only Memory), an HDD (Hard Disc Drive), or an SSD (Solid State Drive) is used alone or in combination. The auxiliary storage device 603 stores data used by the processor 601 when performing various processes and data generated by the processes in the processor 601. The auxiliary storage device 603 may also store an application program.

[0042] The main memory 602 or the auxiliary storage device 603 is used as a storage area for the tracking file 68, the association table 69, and the product data file 61 described above.

[0043] The clock 604 functions as a time information source for the shelf control device 6. The processor 601 keeps track of the current date and time based on the time information kept by the clock 604.

[0044] The communication interface 605 is a circuit for performing data communication with other devices connected via the communication network NW. The other devices include the sales management device 7, the member server 8, the payment server 9, and the like.

[0045] The I / O interface 606 is a circuit for transmitting and receiving data signals between the merchandise monitoring sensor 1, the tracking sensors 21 and 22, the behavior monitoring sensor 3, the personal authentication devices 41 and 42, and the speaker 5 described above.

[0046] The shelf control device 6 having such a configuration is provided, for example, on the top or back surface of the shelf 10. The shelf control device 6 is connected to the communication network NW by wired communication or wireless communication.

[0047] The computer mainly including the processor 601 performs data processing according to a control program installed in the main memory 602 or the auxiliary storage device 603, thereby realizing the functions of the tracking processing unit 62, the personal authentication processing unit 63, the merchandise monitoring processing unit 64, the behavior monitoring processing unit 65, the voice synthesis unit 66, and the integration processing unit 67. Next, the main operations of the tracking processing unit 62, the personal authentication processing unit 63, the merchandise monitoring processing unit 64, the behavior monitoring processing unit 65, the voice synthesis unit 66, and the integration processing unit 67 will be explained using the flowcharts shown in Figs. 9 to 24. The functions of each unit will become clear from these explanations of the operations. Note that the following explanation is an example. As long as similar results are obtained, the procedures and the like are not particularly limited.

[0048] Incidentally, there is no particular limitation on the method for installing the control program in the main memory 602 or the auxiliary storage device 603. The control program can be recorded on a removable recording medium, or distributed by communication via a network, and installed in the main memory 602 or the auxiliary storage device 603. The recording medium may be in any form, such as a CD-ROM or memory card, as long as it can store the program and is readable by the device.

[0049] First, the operation of the tracking processing unit 62 will be described with reference to FIG. The tracking processing unit 62 waits for a person, ACT101, to cross the first boundary line 101 and enter the tracking area 111. Incidentally, the person who enters the tracking area 111 may be not only a consumer but also a store employee such as a store clerk. However, for the sake of convenience, the person is limited to a consumer here. Therefore, hereinafter, the person is referred to as a consumer.

[0050] When the tracking processing unit 62 detects that the consumer has entered the tracking area 111 based on the image data captured by the tracking sensors 21 and 22, the tracking processing unit 62 judges YES in ACT 101 and proceeds to ACT 102. The tracking processing unit 62 starts tracking the consumer in ACT 102. Hereinafter, the tracked consumer is referred to as consumer SA.

[0051] The tracking processing unit 62 checks whether the consumer SA crosses the fourth boundary line 104 and enters the tracking area 111 inside the fourth boundary line 104 in ACT103. If the consumer SA has not entered the tracking area 111 inside the fourth boundary line 104, the tracking processing unit 62 judges NO in ACT103 and proceeds to ACT104. The tracking processing unit 62 checks whether the consumer SA crosses the first boundary line 101 and exits the tracking area 111 in ACT104. If the consumer SA has not exited the tracking area 111, the tracking processing unit 62 judges NO in ACT104 and returns to ACT103. Here, the tracking processing unit 62 waits for the consumer SA to enter the tracking area 111 inside the fourth boundary line 104 or exit the tracking area 111 in ACT103 and ACT104.

[0052] In the standby state of ACT103 and ACT104, if the consumer SA exits the tracking area 111 without entering the tracking area 111 inside the fourth boundary line 104, the tracking processing unit 62 judges YES in ACT104 and proceeds to ACT105. The tracking processing unit 62 ends tracking of the consumer SA in ACT105. Thus, the tracking processing unit 62 ends the operation of the procedure shown in the flowchart of FIG.

[0053] In the standby state of ACT103 and ACT104, when the consumer SA enters the tracing area 111 inside the fourth boundary line 104, the tracing processing unit 62 judges YES in ACT103 and proceeds to ACT106. The tracing processing unit 62 assigns a unique tracing ID to the consumer SA in ACT106. Then, the tracing processing unit 62 creates a tracing file 68 in which the tracing ID is described in ACT107. At this time, the tracing processing unit 62 sets the monitoring flag to "0". Hereinafter, the tracing file 68 in which the tracing ID of the consumer SA is described is referred to as a tracing file 680.

[0054] The tracing processing unit 62 acquires the time measured by the clock 604 as ACT 108. The tracing processing unit 62 acquires the current tracing position information of the consumer SA as ACT 109. The tracing processing unit 62 stores the flow line data in which the time and the tracing position information are associated in the tracing file 680 as ACT 110.

[0055] The tracing processing unit 62 checks the monitoring flag of the tracing file 680 in ACT111. At this time, the monitoring flag is "0". Therefore, the tracing processing unit 62 judges NO in ACT111 and proceeds to ACT112. The tracing processing unit 62 checks whether the consumer SA has crossed the fourth boundary line 104 and exited into the tracing area 111 outside the fourth boundary line 104 in ACT112. If the consumer SA has not exited into the tracing area 111 outside the fourth boundary line 104, the tracing processing unit 62 judges NO in ACT112 and returns to ACT108. Then, the tracing processing unit 62 executes the processing from ACT108 onwards in the same manner as described above. That is, the tracing processing unit 62 stores in the tracing file 680 the movement line data consisting of the time measured by the clock 604 and the tracing position information of the consumer SA at that time.

[0056] The tracing processing unit 62 repeatedly executes the process of storing the movement line data in the tracing file 680 until the consumer SA exits into the tracing area 111 outside the fourth boundary line 104. Then, when the consumer SA exits into the tracing area 111 outside the fourth boundary line 104, the tracing processing unit 62 judges YES in ACT112 and proceeds to ACT113. The tracing processing unit 62 changes the monitoring flag in the tracing file 680 to "1" in ACT113. Then, the tracing processing unit 62 returns to ACT108 and executes the processes from ACT108 onwards again. At this time, the monitoring flag is "1". Therefore, the tracing processing unit 62 judges YES in ACT111 and proceeds to ACT114.

[0057] The tracking processing unit 62 checks whether the consumer SA has exited the tracking area 111 in ACT114. If the consumer SA has not exited the tracking area 111, the tracking processing unit 62 judges NO in ACT114 and proceeds to ACT115. The tracking processing unit 62 checks whether the consumer SA has crossed the fourth boundary line 104 again and returned to the tracking area 111 inside the fourth boundary line 104 in ACT115. If the consumer SA has not returned to the tracking area 111 inside the fourth boundary line 104, the tracking processing unit 62 judges NO in ACT115 and returns to ACT114. Here, the tracking processing unit 62 waits for the consumer SA to exit the tracking area 111 or return to the tracking area 111 inside the fourth boundary line 104 in ACT114 and ACT115.

[0058] In the standby state of ACT114 and ACT115, if the consumer SA returns to the tracing area 111 inside the fourth boundary line 104, the tracing processing unit 62 judges YES in ACT115 and proceeds to ACT116. The tracing processing unit 62 changes the monitoring flag of the tracing file 680 to "0" in ACT116. Then, the tracing processing unit 62 returns to the processing of ACT108. Therefore, the tracing processing unit 62 repeatedly executes the processing of ACT108 to ACT112 until the consumer SA exits again into the tracing area 111 outside the fourth boundary line 104.

[0059] In the standby state of ACT114 and ACT115, if the consumer SA exits outside the tracking area 111, the tracking processing unit 62 judges YES in ACT114 and proceeds to ACT117. The tracking processing unit 62 ends tracking of the consumer SA in ACT117. The tracking processing unit 62 outputs an exit notification command to the integrated processing unit 67 in ACT118. The exit notification command includes the member ID of the tracking file 680. Thus, the tracking processing unit 62 ends the operation of the procedure shown in the flowchart of FIG. 9.

[0060] In this way, the tracing processing unit 62 assigns a unique tracing ID to the consumer SA when the consumer SA enters inside the fourth boundary line 104 of the tracing area 111. Then, the tracing processing unit 62 creates a tracing file 680 in which the tracing ID is described.

[0061] The tracking processing unit 62 starts tracking the consumer SA. Then, the tracking processing unit 62 continues tracking until the consumer SA exits the tracking area 111. When the consumer SA exits the tracking area 111, the tracking processing unit 62 ends tracking of the consumer. During that time, the tracking processing unit 62 stores the movement line data of the consumer SA in the tracking file 680. When the consumer SA exits the tracking area 111, the tracking processing unit 62 outputs an exit notification command to the integrated processing unit 67. The operation of the integrated processing unit 67 that has received the exit notification command will be described later with reference to FIG. 19.

[0062] Next, the operation of the personal authentication processing unit 63 will be described with reference to FIG. The personal authentication processing unit 63 waits for the data for personal authentication to be read by the readers of the personal authentication devices 41 and 42 as ACT201.

[0063] Before purchasing a product, the consumer SA needs to be personally authenticated as a member. To this end, the consumer SA starts up a shopping application installed in the user terminal TM. When the shopping application starts up, a member ID code is displayed on the display of the user terminal TM. The consumer SA then has the code read by a reader of one of the personal authentication devices 41, 42. Then, data indicated by the code is output from the personal authentication devices 41, 42 to the personal authentication processing unit 63. A device ID for identifying the personal authentication devices 41, 42 is added to this data.

[0064] When data is input from the personal authentication devices 41, 42, the personal authentication processing unit 63 judges whether the data represents a member ID code. If the data represents a member ID code, the personal authentication processing unit 63 judges YES in ACT201 and proceeds to ACT202. The personal authentication processing unit 63 acquires the device ID added to the data in ACT202. The personal authentication processing unit 63 acquires the member ID from the data in ACT203. The personal authentication processing unit 63 outputs an authentication notification command to the integrated processing unit 67 in ACT204. The authentication notification command includes the device ID acquired in the processing of ACT202 and the member ID acquired in the processing of ACT203.

[0065] Here, the operation of the integrated processing unit 67 upon receiving the authentication notification command will be described with reference to FIG. The integration processing unit 67 acquires the device ID from the authentication notification command as ACT 501. Then, the integration processing unit 67 selects the authentication areas 113, 114 specified from the device ID as ACT 502. For example, when the device ID is that of the personal authentication device 41, the integration processing unit 67 selects the authentication area 113. For example, when the device ID is that of the personal authentication device 42, the integration processing unit 67 selects the authentication area 114. Here, assuming that the authentication area 113 has been selected as an example, the operation of the integration processing unit 67 will be described.

[0066] The integration processing unit 67 acquires the number of consumers present in the authentication area 113 as ACT503. Specifically, the integration processing unit 67 cooperates with the tracking processing unit 62 to search for a tracking file 68 that stores movement line data in which tracking position information corresponding to the time when the authentication notification command was output matches the authentication position information for the authentication area 113. The number of corresponding tracking files 68 indicates the number of consumers present in the authentication area 113. The authentication position information is a collection of XY plane coordinates in the authentication area 113. The authentication position information for the authentication area 113 and the authentication position information for the authentication area 113 are set in advance in the auxiliary storage device 603.

[0067] The integration processing unit 67 checks whether the number of consumers in the authentication area 113 is one in ACT504. If the number of consumers is one, that is, if only consumer SA is in the authentication area 113, the integration processing unit 67 judges YES in ACT504 and proceeds to ACT505. The integration processing unit 67 acquires the member ID from the authentication notification command in ACT505. Then, the integration processing unit 67 transmits an authentication request command to the member server 8. The authentication request command includes the member ID acquired in the processing of ACT505, that is, the member ID of consumer SA.

[0068] The member server 8 determines the validity of the member ID. Specifically, the member server 8 searches the member database 81 for the member ID included in the authentication request command. As a result, if the validity flag corresponding to the member ID is "1", the member server 8 determines that the member ID is valid. If the validity flag corresponding to the member ID is "0", the member server 8 determines that the member ID is invalid. The member server 8 returns the result of the member ID validity determination to the integration processing unit 67.

[0069] The integration processing unit 67 checks the validity of the member ID in ACT507. If the member server 8 determines that the member ID is valid, the integration processing unit 67 determines YES in ACT507 and proceeds to ACT508. The integration processing unit 67 acquires a tracking ID from the tracking file 680 of the consumer SA in the authentication area 113 in ACT508. That is, the integration processing unit 67 acquires a tracking ID from the tracking file 68 that stores movement line data in which tracking position information corresponding to the time when the authentication notification command was output matches the authentication position information for the authentication area 113. Then, the integration processing unit 67 associates the tracking ID acquired in the process of ACT508 with the member ID acquired in the process of ACT505 and stores them in the association table 69 in ACT509.

[0070] The integrated processing unit 67 instructs the sales management device 7 to create a purchase list 71 as ACT510. This instruction causes the sales management device 7 to create a purchase list 71 identified by the member ID acquired in the processing of ACT505. Hereinafter, the purchase list 71 identified by the member ID of the consumer SA is referred to as a purchase list 711. The integrated processing unit 67 outputs an approval response command as ACT 511 to the personal authentication processing unit 63 .

[0071] On the other hand, in ACT504, if there is no consumer in the authentication area 113, or if there are two or more consumers, the integration processing unit 67 judges NO and proceeds to ACT512. Also, if it is determined in ACT507 that the consumer is not a valid member, the integration processing unit 67 also judges NO and proceeds to ACT512. The integration processing unit 67 outputs an error response command to the personal authentication processing unit 63 in ACT512.

[0072] When the integrated processing unit 67 outputs an approval response command or an error response command to the personal authentication processing unit 63, the operation of the procedure shown in the flowchart of FIG. 13 ends.

[0073] Returning to the explanation of Figure 10. The personal authentication processing unit 63, which has output the authentication notification command in ACT204, waits for a response command from the integrated processing unit 67 in ACT205. If an approval response command is input here, the personal authentication processing unit 63 judges YES in ACT205 and proceeds to ACT206. In ACT206, the personal authentication processing unit 63 controls the personal authentication device 41 in the authentication area 113 so that the personal authentication device 41 notifies the user that authentication has been successful. Through this control, for example, a message such as "Authentication has been successful. Please start shopping" is displayed on the display device of the personal authentication device 41.

[0074] On the other hand, if an error response command is input, the personal authentication processing unit 63 judges NO in ACT205 and proceeds to ACT207. In ACT207, the personal authentication processing unit 63 controls the personal authentication device 41 so that the personal authentication device 41 in the authentication area 113 notifies the user that the authentication has failed. By this control, for example, a message saying "Authentication has failed" is displayed on the display device of the personal authentication device 41. With this, the personal authentication processing unit 63 ends the operation of the procedure shown in the flowchart of FIG.

[0075] In this way, when consumer SA, for example, enters authentication area 113 and has his / her member ID read by the reader of personal authentication device 41, personal authentication processing unit 63 outputs an authentication notification command to integration processing unit 67. In response to this authentication notification command, integration processing unit 67 obtains the number of consumers present in authentication area 113. If the number is one, integration processing unit 67 cooperates with member server 8 to determine the validity of the member ID. Then, if the validity of the member ID is approved, integration processing unit 67 outputs an acceptance response command to personal authentication processing unit 63. Having received the acceptance response command, personal authentication processing unit 63 notifies personal authentication device 41 of successful authentication.

[0076] On the other hand, if the validity of the member ID is not confirmed, the integrated processing unit 67 outputs an error response command to the personal authentication processing unit 63. In response to this error response command, the personal authentication processing unit 63 notifies the personal authentication device 41 of the failure of authentication. Furthermore, if the number of consumers in authentication area 113 is more than one, integrated processing unit 67 does not determine the validity of the member ID. In this case as well, integrated processing unit 67 outputs an error response command to personal authentication processing unit 63. In response to this error response command, personal authentication processing unit 63 notifies via personal authentication device 41 that authentication has failed.

[0077] For example, if only consumer SA is present in authentication area 113, the consumer who can have his / her member ID read by the reader of personal authentication device 41 is limited to consumer SA. Therefore, the member ID read by the reader can be associated with the tracking ID assigned to consumer SA. On the other hand, if another consumer SB other than consumer SA is present in authentication area 113, the consumer who can have his / her member ID read by the reader of personal authentication device 41 is not limited to consumer SA. Consumer SB can also have his / her member ID read by the reader. Therefore, if there is more than one consumer in authentication area 113, integration processing unit 67 does not determine the validity of the member ID. As a result, the member ID is not erroneously associated with the tracking ID.

[0078] Consumer SA who has successfully passed personal authentication using his / her member ID can purchase products A to F displayed on shelf 10. For example, when purchasing product A displayed in section 201 of shelf 10, consumer SA removes product A from section 201. Hereinafter, such behavior of consumer SA is referred to as purchasing behavior. Furthermore, when consumer SA decides not to purchase product A that he / she has removed, consumer SA returns product A to its original section 201. Hereinafter, such behavior of consumer SA is referred to as return behavior. In response to purchasing behavior or return behavior, the shelf control device 6 can register the purchased product data of the consumer SA in the purchase list 711 by having the product monitoring processing unit 64, behavior monitoring processing unit 65, and integrated processing unit 67 operate in cooperation with each other.

[0079] First, the operation of the merchandise surveillance processing unit 64 will be described with reference to FIG. In addition, in purchasing behavior, the act of Consumer SA taking out multiple items at the same time is prohibited. In return behavior, the act of Consumer SA taking out the item or another item without removing the hand that put the item back is also prohibited. Incidentally, the act of Consumer SA taking out and returning multiple items of the same item at the same time is permitted.

[0080] The product monitoring processing unit 64 waits for a weight change to be detected by the product monitoring sensor 1 as ACT 301. For example, when consumer SA performs a purchasing action on product A, the product monitoring sensor 1 in section 201 detects a weight change in the decreasing direction. For example, when consumer SA performs a returning action on product A, the product monitoring sensor 1 in section 201 detects a weight change in the increasing direction.

[0081] When the merchandise monitoring sensor 1 detects a weight change, the merchandise monitoring processing unit 64 judges YES in ACT 301 and proceeds to ACT 302. The merchandise monitoring processing unit 64 acquires the sensor number of the merchandise monitoring sensor 1 that detected the weight change in ACT 302. In this case, the merchandise monitoring processing unit 64 acquires the sensor number of the merchandise monitoring sensor 1 installed in the section 201, for example, "001."

[0082] The merchandise monitoring processing unit 64 determines whether a weight change in the direction of a decrease or an increase has been detected by the merchandise monitoring sensor 1 in ACT 303. If a weight change in the direction of a decrease has been detected, the merchandise monitoring processing unit 64 determines YES in ACT 304 and proceeds to ACT 305. The merchandise monitoring processing unit 64 outputs a decrease notification command to the integrated processing unit 67 in ACT 305.

[0083] If an increasing weight change is detected, the merchandise monitoring processing unit 64 judges NO in ACT 304 and proceeds to ACT 306. The merchandise monitoring processing unit 64 outputs an increase notification command to the integrated processing unit 67 in ACT 306.

[0084] The decrease notification command or the increase notification command includes the sensor number acquired in the process of ACT 302 and the weight change amount calculated in the process of ACT 303. With the above, the merchandise monitoring processing unit 64 ends the operation of the procedure shown in the flowchart of FIG.

[0085] Next, the operation of the behavior monitoring processing unit 65 will be described with reference to FIG. The behavior monitoring processing unit 65 waits for the behavior monitoring sensor 3 to detect the hand of the consumer SA in ACT401. When the consumer SA in the purchasing area 112 reaches out for the shelf 10, the hand is detected by the behavior monitoring sensor 3. When the hand is detected, the behavior monitoring processing unit 65 judges YES in ACT401 and proceeds to ACT402. The behavior monitoring processing unit 65 acquires behavioral position information of the point where the hand of the consumer SA was detected in ACT402. Then, the behavior monitoring processing unit 65 outputs a hand reaching notification command to the integration processing unit 67 in ACT403. The hand reaching notification command includes the behavioral position information acquired in the processing of ACT402.

[0086] The behavior monitoring processing unit 65 waits for the hand of the consumer SA to be undetected in ACT404. When the behavior monitoring sensor 3 no longer detects the hand of the consumer SA, the behavior monitoring processing unit 65 judges YES in ACT404 and proceeds to ACT405. The behavior monitoring processing unit 65 outputs a hand-return notification command to the integrated processing unit 67 in ACT405. The hand-return notification command also includes the behavior position information acquired in the processing of ACT402.

[0087] In this way, when consumer SA reaches out to the shelf 10 to take out product A from section 201, first, the hand of consumer SA is detected by the behavior monitoring sensor 3. Upon detection of this hand, a reaching out notification command is output from the behavior monitoring processing unit 65 to the integrated processing unit 67. The reaching out notification command includes behavior position information indicating the position where consumer SA's hand was detected.

[0088] Next, when consumer SA picks up just one item A from section 201, a weight change in the decreasing direction is detected by item monitoring sensor 1 in section 201. This weight change causes item monitoring processing unit 64 to output a weight reduction notification command to integrated processing unit 67. The weight reduction notification command includes the sensor number of item monitoring sensor 1 that detected the weight change and the amount of weight change. The amount of weight change matches the unit weight of item A. Incidentally, if consumer SA picks up two items A together from section 201, the amount of weight change matches twice the unit weight of item A.

[0089] Thereafter, when consumer SA removes his / her hand holding product A from the shelf 10, consumer SA's hand that had been detected by the behavior monitoring sensor 3 is no longer detected. This non-detection of the hand causes the behavior monitoring processing unit 65 to output a hand-return notification command to the integrated processing unit 67. The hand-return notification command also includes behavior position information indicating the position where consumer SA's hand was detected.

[0090] On the other hand, if the consumer SA reaches his / her hand toward the shelf 10 while holding the product A in order to cancel the purchase of the product A, a reaching-hand notification command is first output from the behavior monitoring processing unit 65 to the integrated processing unit 67.

[0091] Next, when consumer SA returns product A to section 201, an increasing weight change is detected by the product monitoring sensor 1 in section 201. This weight change causes the product monitoring processing unit 64 to output an increase notification command to the integrated processing unit 67. The increase notification command includes the sensor number of the product monitoring sensor 1 that detected the weight change and the amount of weight change. The amount of weight change matches the unit weight of product A. Incidentally, if consumer SA returns two products A together to section 201, the amount of weight change matches twice the unit weight of product A.

[0092] Thereafter, when the consumer SA withdraws his / her hand from the shelf 10, the behavior monitoring processing unit 65 outputs a hand-return notification command to the integrated processing unit 67.

[0093] In this way, with respect to the purchasing behavior of the consumer SA, first, a reach notification command is output from the behavior monitoring processing unit 65 to the integrated processing unit 67. Next, a decrease notification command is output from the product monitoring processing unit 64 to the integrated processing unit 67. After that, a return notification command is output from the behavior monitoring processing unit 65 to the integrated processing unit 67.

[0094] If the consumer SA withdraws his / her hand without picking up the product, the decrease notification command is not output. In other words, a reach-out notification command is output, followed by a return-hand notification command.

[0095] On the other hand, in response to the return behavior of the consumer SA, first, a reach out notification command is output from the behavior monitoring processing unit 65 to the integrated processing unit 67. Next, an increase notification command is output from the product monitoring processing unit 64 to the integrated processing unit 67. After that, a return notification command is output from the behavior monitoring processing unit 65 to the integrated processing unit 67.

[0096] It should be noted that the increase notification command is not output if the consumer SA withdraws his / her hand without returning the product to the shelf 10. In other words, a reach notification command is output, followed by a return notification command.

[0097] Also, in a purchasing behavior, if the consumer SA returns the product to the shelf 10 without retracting the hand that lifted the product, various commands are output from the behavior monitoring processing unit 65 and the product monitoring processing unit 64 to the integrated processing unit 67 in the following order. First, the behavior monitoring processing unit 65 outputs a reach notification command to the integrated processing unit 67. Next, the product monitoring processing unit 64 outputs a decrease notification command to the integrated processing unit 67. Next, the product monitoring processing unit 64 outputs an increase notification command to the integrated processing unit 67. After that, the behavior monitoring processing unit 65 outputs a put back notification command to the integrated processing unit 67. Incidentally, if the consumer SA returns the product to the same section, the sensor numbers included in the decrease notification command and the increase notification command will match. However, if the consumer SA returns the product to a different section, the sensor numbers included in the decrease notification command and the increase notification command will differ.

[0098] In this way, in response to a consumer's purchasing behavior or return behavior, a reaching notification command is always output from the behavior monitoring processing unit 65 to the integrated processing unit 67. Here, the operation of the integrated processing unit 67 that has received the reaching notification command will be described with reference to FIG.

[0099] The integrated processing unit 67 acquires action location information from the hand reaching notification command as ACT 521. Then, the integrated processing unit 67 stores the action location information as ACT 522. The action location information is stored in, for example, the main memory 602. The action location information may also be stored in the auxiliary storage device 603.

[0100] The integration processing unit 67 checks whether or not a decrease notification command has been input in ACT523. If a decrease notification command has not been input, the integration processing unit 67 judges NO in ACT523 and proceeds to ACT524. The integration processing unit 67 checks whether or not an increase notification command has been input in ACT524. If an increase notification command has not been input, the integration processing unit 67 judges NO in ACT524 and proceeds to ACT525. The integration processing unit 67 checks whether or not a return notification command has been input in ACT525. If a return notification command has not been input, the integration processing unit 67 returns to ACT523. Here, the integration processing unit 67 waits for a decrease notification command, an increase notification command, or a return notification command to be input in ACT523 to ACT525.

[0101] If a hand-back notification command is input in the standby state of ACT523 to ACT525, the integration processing unit 67 judges YES in ACT525 and proceeds to ACT526. The integration processing unit 67 clears the action position information in ACT526. Thus, the integration processing unit 67 ends the operation of the procedure shown in the flowchart of FIG.

[0102] In this way, the integrated processing unit 67 does not execute any special processing if it receives a reach out notification command but receives a return notification command without receiving a decrease notification command or an increase notification command. In other words, if the consumer SA who has made a purchase withdraws his / her hand without picking up the product, or if the consumer SA who has returned the product withdraws his / her hand without putting it back, the integrated processing unit 67 does not execute any special processing.

[0103] In the standby state of ACT523 to ACT525, if a decrease notification command is input, the integration processing unit 67 judges YES in ACT523 and proceeds to ACT527. The integration processing unit 67 checks whether an increase notification command is input in ACT527. If an increase notification command is not input, the integration processing unit 67 judges NO in ACT527 and proceeds to ACT528. The integration processing unit 67 checks whether a return notification command is input in ACT528. If a return notification command is not input, the integration processing unit 67 judges NO in ACT528 and returns to ACT527. Here, the integration processing unit 67 waits for an increase notification command to be input or a return notification command to be input in ACT527 and ACT528.

[0104] When an increase notification command is input in the standby state of ACT527 and ACT528, the integration processing unit 67 judges YES in ACT527 and returns to ACT523. That is, the integration processing unit 67 returns to the standby state of ACT523 to ACT525.

[0105] If a return notification command is input during the standby state of ACT527 and ACT528, the integrated processing unit 67 judges YES in ACT528 and proceeds to ACT529. The integrated processing unit 67 executes a purchasing process in ACT529. Details of the purchasing process will be described later. When the purchasing process is completed, the integrated processing unit 67 ends the operation of the procedure shown in the flowchart of FIG.

[0106] In this way, the integrated processing unit 67 executes the purchase process when it inputs the reach notification command, the decrease notification command, and then the return notification command. That is, when the consumer SA performs a purchase action, the integrated processing unit 67 executes the purchase process.

[0107] The integrated processing unit 67 does not execute any special processing if it inputs a decrease notification command after inputting a reach notification command, and further inputs a return notification command after inputting an increase notification command. In other words, if the consumer SA immediately puts back the product he or she was holding and withdraws his or her hand, the integrated processing unit 67 does not execute any special processing.

[0108] In the standby state of ACT523 to ACT525, if an increase notification command is input, the integration processing unit 67 judges YES in ACT524 and proceeds to ACT530. The integration processing unit 67 waits for a return notification command in ACT530. Then, when a return notification command is input, the integration processing unit 67 judges YES in ACT530 and proceeds to ACT531. The integration processing unit 67 executes a return processing in ACT531. Details of the return processing will be described later. When the return processing is completed, the integration processing unit 67 ends the operation of the procedure shown in the flowchart of FIG.

[0109] In this way, the integrated processing unit 67 executes the return processing when it inputs the reach notification command, the increase notification command, and then the return notification command. That is, when the consumer SA performs the return behavior, the integrated processing unit 67 executes the return processing.

[0110] 15 is a flow chart showing the main steps of the purchasing process. When the integrated processing unit 67 starts the purchasing process, it counts the number M of consumers in the purchasing area 112 as ACT541. Specifically, the integrated processing unit 67 counts the number of tracing files 68 stored in the tracing processing unit 62, in which the tracing position information of the movement line data corresponding to the current time coincides with the purchasing position information for the purchasing area 112. The number of corresponding tracing files 68 is the number M of consumers in the purchasing area 112. The purchasing position information is a collection of XY plane coordinates in the purchasing area 112. The purchasing position information for the purchasing area 112 is set in advance in the auxiliary storage device 603.

[0111] The integrated processing unit 67 checks whether the number M of consumers in the purchasing area 112 is 0 in ACT542. If the number M is 0, there is a possibility that a consumer who cannot be tracked by the tracking processing unit 62 has removed a product from the shelf 10. In this case, the integrated processing unit 67 judges YES in ACT542 and proceeds to ACT543. The integrated processing unit 67 outputs voice data of a tracking error to the voice synthesis unit 66 in ACT543. As a result, the voice synthesis unit 66 synthesizes a voice indicating a tracking error. Then, a voice such as "An error has occurred and shopping cannot be performed" is output from the speaker 5. Then, the integrated processing unit 67 ends the purchasing process.

[0112] If the number M of consumers in the purchasing area 112 is not 0, the integration processing unit 67 judges NO in ACT542 and proceeds to ACT544. In ACT544, the integration processing unit 67 checks whether the number M of consumers in the purchasing area 112 is 1. If there is only one tracking file 68 in which the tracking position information of the movement line data corresponding to the current time matches the purchase position information, the number M is 1. Hereinafter, this tracking file 68 is referred to as the target tracking file 68. For example, if there is only one consumer SA in the purchasing area 112, the tracking file 680 is the target tracking file 680.

[0113] If the number M of consumers in the purchasing area 112 is 1, the integration processing unit 67 determines YES in ACT 544 and proceeds to ACT 545. In ACT 545, the integration processing unit 67 obtains tracking position information of the flow line data corresponding to the current time from the target tracking file 680.

[0114] The integration processing unit 67 checks whether or not the consumer SA tracked by the tracking ID described in the target tracking file 680 can make a purchase based on the tracking location information and the behavioral location information stored in the processing of ACT522 in FIG. 14 as ACT546. Specifically, the integration processing unit 67 checks whether or not the consumer SA in the location specified by the tracking location information can reach out and take out a product from the location specified by the behavioral location information. If the action of taking out the product is not possible, the integration processing unit 67 determines that the purchase is not possible. The integration processing unit 67 determines NO in ACT546 and proceeds to ACT543. The integration processing unit 67 outputs voice data of a tracking error to the voice synthesis unit 66 as ACT543. Thus, the integration processing unit 67 ends the purchase processing.

[0115] If purchasing behavior is possible, the integration processing unit 67 judges YES in ACT 546 and proceeds to ACT 547. The integration processing unit 67 acquires a tracking ID from the target tracking file 680 in ACT 547.

[0116] Next, the integration processing unit 67 searches the association table 69 in ACT548 to check whether the tracking ID is associated with a member ID. If the tracking ID is not associated with a member ID, it is presumed that a consumer whose member ID is not approved has made a purchase. In this case, the integration processing unit 67 judges NO in ACT548 and proceeds to ACT549. The integration processing unit 67 outputs voice data of an authentication error to the voice synthesis unit 66 in ACT549. As a result, the voice synthesis unit 66 synthesizes a voice indicating an authentication error. Then, a voice such as "Your member ID has not been authenticated" is output from the speaker 5. Then, the integration processing unit 67 ends the purchase process.

[0117] If a member ID is associated with the tracking ID, the integration processing unit 67 judges YES in ACT 548 and proceeds to ACT 550. The integration processing unit 67 acquires the member ID associated with the tracking ID in ACT 550. The integration processing unit 67 also acquires the sensor number from the decrease notification command in ACT 551. The decrease notification command was received from the merchandise monitoring sensor 1 in ACT 523 of FIG. 14.

[0118] The integration processing unit 67 reads the product data, including the product code, product name, and unit weight, stored together with the sensor number from the product data file 61 as ACT552. Furthermore, the integration processing unit 67 calculates the number of purchased items as ACT553. Specifically, the integration processing unit 67 obtains the amount of weight change from the decrease notification command. The integration processing unit 67 then divides the amount of weight change by the unit weight. As a result, if the value in the first decimal place is "1", it is rounded down, and if it is "9", it is rounded up, to calculate the number of purchased items.

[0119] It should be noted that if the value in the first decimal place is between "2" and "8", the number of purchased items cannot be calculated. In this regard, the number of purchased items may be calculated by rounding down when the value in the first decimal place is "1" or "2" and rounding up when the value is "8" or "9". Alternatively, if the weight change amount cannot be divisible by the unit weight, the number of purchased items may be calculated as being unable to be calculated. Usually, each product is displayed correctly in its section on the shelf 10. Therefore, since the weight change amount is divisible by the unit weight, the number of purchased items will not be unable to be calculated.

[0120] The integrated processing unit 67 outputs a purchase notification command to the sales management device 7 as ACT 554. The purchase notification command includes the member ID acquired in the process of ACT 550, the product code, product name, and unit price of the product data read in the process of ACT 552, and the purchase quantity calculated in the process of ACT 553. The integrated processing unit 67 ends the purchase process.

[0121] On the other hand, if there are two or more object tracking files 68, that is, if the number M of consumers in the purchasing area 112 is two or more, the integration processing unit 67 judges NO in ACT544 and proceeds to ACT555. In ACT555, the integration processing unit 67 acquires tracking position information of the movement line data corresponding to the current time from all the object tracking files 68.

[0122] The integrated processing unit 67 counts the number N of consumers capable of purchasing behavior based on the tracking location information acquired from the target tracking file 68 as ACT556 and the behavioral location information stored in the processing of ACT522 in Fig. 14. Specifically, the integrated processing unit 67 checks for each target tracking file 68 whether or not a consumer in a location specified by the tracking location information can reach out and take out a product from the location specified by the behavioral location information. The integrated processing unit 67 then counts the number of target tracking files 68 determined to be capable of taking out a product as the number N of consumers capable of purchasing behavior.

[0123] The integration processing unit 67 checks whether the number N of consumers who can make a purchase is 0 in ACT 557. If the number N is 0, the integration processing unit 67 judges YES in ACT 557 and proceeds to ACT 543. Then, the integration processing unit 67 executes the process of ACT 543 in the same manner as described above. Then, the integration processing unit 67 ends the purchase process.

[0124] If the number N of consumers capable of purchasing is not 0, the integration processing unit 67 judges NO in ACT557 and proceeds to ACT558. The integration processing unit 67 checks whether the number N of consumers capable of purchasing is 1 in ACT558. If the number N is 1, it can be determined that this one consumer has performed a purchasing action. The integration processing unit 67 judges YES in ACT558 and proceeds to ACT547. The integration processing unit 67 then executes the processing of ACT547 to ACT554 in the same manner as described above. The integration processing unit 67 then ends the purchasing process.

[0125] If the number N of consumers capable of purchasing is two or more, the purchaser cannot be identified. The integrated processing unit 67 determines NO in ACT 558 and proceeds to ACT 559. The integrated processing unit 67 outputs voice data of the purchase error to the voice synthesis unit 66 in ACT 559 (notification means). As a result, the voice synthesis unit 66 synthesizes a voice indicating the purchase error. Then, a voice such as "An error has occurred because the purchaser cannot be identified" is output from the speaker 5. Then, the integrated processing unit 67 ends the purchase process.

[0126] In this case, the integrated processing unit 67 does not output a purchase notification command to the sales management device 7. In other words, the integrated processing unit 67 has a notification means for notifying the occurrence of a purchase error without adding the product data to the purchase list when it cannot identify the consumer who made the purchase. Therefore, since product data that cannot identify the purchaser is not added to the purchase list, inconsistencies between the actual purchased items and the registered purchased items can be prevented before settlement. Not changing the purchase list also improves processing efficiency.

[0127] However, since the consumer still has the product in hand, the error may be reported and the store clerk may also be notified. For example, the store clerk may output information indicating that the purchaser cannot be identified to a terminal operated by the store clerk. By doing so, an error notification is issued from the terminal, allowing the store clerk to deal with the error appropriately. This can prevent problems such as consumers taking back products that are not registered.

[0128] In this embodiment, when the number M of consumers in the purchasing area 112 is two or more, the number N of consumers who are capable of purchasing is obtained. However, when the number M of consumers in the purchasing area 112 is two or more, an error may be notified without adding the product data to the purchasing list.

[0129] In this way, the integrated processing unit 67 executes purchasing processing for the purchasing behavior of the consumer, thereby identifying one consumer in the purchasing area 112 as the purchaser of the product taken out from the shelf 10. Then, the integrated processing unit 67 transmits to the sales management device 7 a purchase notification command including the member ID of the consumer identified as the purchaser and data on the purchased product.

[0130] Next, the operation of the sales management device 7 that has received the purchase notification command will be described with reference to FIG. The sales management device 7 acquires the member ID from the purchase notification command in ACT701. The sales management device 7 also creates purchased item data based on the item data included in the purchase notification command, that is, the item code, item name, unit price, and purchased quantity in ACT702. The sales management device 7 then sets the provisional registration flag of the purchased item data to "0" in ACT703. The sales management device 7 adds the purchased item data to the purchase list 71, which has the member ID acquired in the processing of ACT701 set in it, in ACT704. With this, the sales management device 7 ends the operation of the procedure shown in the flowchart of FIG. 20.

[0131] In this way, the sales management device 7 adds purchased item data to the purchase list 71 with the member ID included in the purchase notification command set thereto every time the sales management device 7 receives a purchase notification command from the integrated processing unit 67. At this time, the provisional registration flag of the purchased item data is "0".

[0132] Here, the integrated processing unit 67, which executes purchase processing in cooperation with the tracking processing unit 62, the product monitoring processing unit 64, and the behavior monitoring processing unit 65, has the functions of a recognition means for recognizing product purchasing behavior by consumers, a specification means for specifying the consumer who performed the purchasing behavior, and a purchase processing means. That is, when the integrated processing unit 67 recognizes a product purchasing behavior and specifies the consumer who performed the purchasing behavior, it outputs a purchase notification command to the sales management device 7 to add the data of the product to the purchase list of that consumer.

[0133] 16 is a flow chart showing the main steps of the return processing. When the integrated processing unit 67 starts the return processing, it counts the number of consumers M in the purchasing area 112 in ACT561. The integrated processing unit 67 counts the number of consumers M in the purchasing area 112 in the same manner as the processing in ACT541 of the purchase processing. However, in this case, the purchasing area 112 is an area where a consumer is estimated to be located when returning any of the products A to F to the shelf 10. The number of consumers M is the number of consumers in the area where the consumer is estimated to be located when returning the product. Therefore, the processing of counting the number of consumers M corresponds to one embodiment of a number of people acquiring means that acquires the number of consumers in the area where the consumer is estimated to be located when returning the product when a return behavior is recognized.

[0134] The integrated processing unit 67 checks whether the number M of consumers in the purchasing area 112 is 0 in ACT 562. If the number M is 0, the integrated processing unit 67 determines YES in ACT 562 and proceeds to ACT 563. The integrated processing unit 67 outputs voice data of a tracking error to the voice synthesis unit 66 in ACT 563. As a result, the voice synthesis unit 66 synthesizes a voice indicating a tracking error. Then, a voice such as "An error has occurred and you cannot make a purchase" is output from the speaker 5. Then, the integrated processing unit 67 ends the return process.

[0135] If the number M of consumers in the purchasing area 112 is not 0, the integration processing unit 67 judges NO in ACT 562 and proceeds to ACT 564. In ACT 564, the integration processing unit 67 checks whether the number M of consumers in the purchasing area 112 is 1 or not.

[0136] When the number M of consumers in the purchase area 112 is one, the integration processing unit 67 judges YES in ACT564 and proceeds to ACT565. The integration processing unit 67 acquires tracking position information of the movement line data corresponding to the current time from the target tracking file 68 in ACT565. The integration processing unit 67 checks whether or not the return behavior of the consumer tracked by the tracking ID described in the target tracking file 68 is possible based on the tracking position information and the behavior position information stored in the processing of ACT522 of FIG. 14 in ACT566. Specifically, the integration processing unit 67 checks whether or not the consumer in the location specified by the tracking position information can reach out and return the product from the location specified by the behavior position information. If the behavior of returning the product is impossible, the integration processing unit 67 judges that the return behavior is impossible. In that case, the integration processing unit 67 judges NO in ACT566 and proceeds to ACT563. The integration processing unit 67 outputs voice data of a tracking error to the voice synthesis unit 66 in ACT563. Then, the integrated processing unit 67 ends the return processing.

[0137] If the return action is possible, the integration processing unit 67 judges YES in ACT566 and proceeds to ACT567. The integration processing unit 67 acquires a tracking ID from the target tracking file 68 in ACT567. Then, the integration processing unit 67 searches the association table 69 in ACT568 to confirm whether the tracking ID is associated with a member ID. If the tracking ID is not associated with a member ID, the integration processing unit 67 outputs voice data of an authentication error to the voice synthesis unit 66 in ACT569. This causes the voice synthesis unit 66 to synthesize a voice indicating an authentication error. Then, a voice such as "Your member ID has not been authenticated" is output from the speaker 5. Then, the integration processing unit 67 ends the return processing.

[0138] If the member ID is associated with the tracking ID, the integration processing unit 67 judges YES in ACT568 and proceeds to ACT570. The integration processing unit 67 executes one-person processing in ACT570.

[0139] FIG. 17 is a flow chart showing the main steps of single-person processing. The integration processing unit 67 acquires the member ID associated with the tracking ID in ACT 581. The integration processing unit 67 also acquires the sensor number from the increase notification command in ACT 582. The increase notification command was received from the merchandise monitoring sensor 1 in ACT 524 of FIG.

[0140] The integration processing unit 67 reads the product data, including the product code, product name, and unit weight, stored together with the sensor number from the product data file 61 as ACT583. Furthermore, the integration processing unit 67 calculates the number of returned items P as ACT584. Specifically, the integration processing unit 67 obtains the amount of weight change from the increase notification command. The integration processing unit 67 then divides the amount of weight change by the unit weight. As a result, if the value in the first decimal place is "1", it is rounded down, and if it is "9", it is rounded up, to calculate the number of returned items P.

[0141] In addition, if the value in the first decimal place is between "2" and "8," the number of returned items P cannot be calculated. In this regard, the number of returned items P may be calculated by rounding down when the value in the first decimal place is "1" or "2," and rounding up when the value is "8" or "9." Alternatively, if the amount of weight change cannot be divided by the unit weight, the number of returned items P may be calculated by rounding down when the value in the first decimal place is "1" or "2," and rounding up when the value is "8" or "9." Alternatively, the number of returned items P may be calculated by rounding up when the amount of weight change cannot be divided by the unit weight.

[0142] The integrated processing unit 67 determines whether or not the number of returned items P could be calculated as ACT585. If the number of returned items P cannot be calculated, it is considered that the consumer has returned the item to the section containing another item with a different unit weight. For example, as shown in FIG. 4, when item A, which has a unit weight of 500 grams, is returned to section 203 in which item C is displayed, the unit weight of item C is 600 grams, so the quotient is 0.83. Similarly, when item A is returned to section 205 in which item E is displayed, the unit weight of item E is 800 grams, so the quotient is 0.625. Therefore, the number of returned items P cannot be calculated in either case.

[0143] If the number of returned items P cannot be calculated, the integration processing unit 67 judges NO in ACT585 and proceeds to ACT586. The integration processing unit 67 outputs voice data of a wrong return error to the voice synthesis unit 66 in ACT586. As a result, the voice synthesis unit 66 synthesizes a voice indicating a wrong return error. Then, a voice such as "The product is being returned to the wrong place" is output from the speaker 5. Then, the integration processing unit 67 ends the single-person process.

[0144] If the return quantity P can be calculated, the integrated processing unit 67 judges YES in ACT585 and proceeds to ACT587. The integrated processing unit 67 outputs a purchase quantity request command to the sales management device 7 in ACT587. The purchase quantity request command includes the member ID acquired in the process of ACT581 and the product code of the product data acquired in the process of ACT583.

[0145] The sales management device 7, which has received the purchase quantity request command, detects the purchase quantity Q stored in association with the product code from the purchase list 71 in which the member ID is set, and responds to the integrated processing unit 67. At this time, if the data for the product code is not stored in the purchase list 71, the sales management device 7 responds with "0" as the purchase quantity Q.

[0146] The integration processing unit 67, which has output the purchase quantity request command, waits for the purchase quantity Q to be responded to in ACT 588. When the purchase quantity Q is responded to, the integration processing unit 67 subtracts the returned quantity P from the purchase quantity Q in ACT 589 to calculate a difference value R. The integration processing unit 67 checks whether the difference value R is negative in ACT 590.

[0147] For example, assume that consumer SA has taken out product A from shelf 10 but has not taken out product B. In this case, data on product A (number of purchased items = 1) is stored in consumer SA's purchase list 711, but data on product B is not stored. Now, assume that consumer SA mistakenly returns product A to section 202 for product B. In that case, since the unit weights of products A and B are equal, the number of returned items P is calculated as "1". However, since data on product B is not stored in purchase list 711, the number of purchased items Q is "0". Therefore, the difference value R is "-1". Incidentally, if consumer SA had returned product A to section 201, the number of purchased items Q would have been "1", and so the difference value R would have been "0".

[0148] If the difference value R is negative, the integration processing unit 67 judges YES in ACT 590 and proceeds to ACT 586. The integration processing unit 67 outputs voice data with a return error to the voice synthesis unit 66. Thus, the integration processing unit 67 ends the one-person processing.

[0149] If the difference value R is equal to or greater than "0" or "1", the integration processing unit 67 judges NO in ACT590 and proceeds to ACT591. The integration processing unit 67 outputs a return notification command to the sales management device 7 in ACT591. The return notification command includes the member ID acquired in the process of ACT581, the product code, product name and unit price of the product data read in the process of ACT583, and the number of returned items P calculated in the process of ACT584. Then, the integration processing unit 67 ends the single-person process.

[0150] In this way, the processes of ACT581, ACT582, ACT583, ACT584, and ACT591 correspond to a return processing means which, when the number of people is one, identifies the consumer who performed the return behavior and subtracts the data of the returned product from the purchase list of the purchased items of that consumer.

[0151] In the case of single-person processing, since there is a high possibility that the consumer who returned the product is the consumer who intended to purchase the product, the return notification command may be output without checking for mistakes such as returning the product.

[0152] Returning to the explanation of Figure 16. If the number M of consumers in the purchasing area 112 is two or more, the integration processing unit 67 judges NO in ACT564 and proceeds to ACT571. In ACT571, the integration processing unit 67 acquires tracking position information of movement line data corresponding to the current time from all of the target tracking files 68. In ACT572, the integration processing unit 67 counts the number N of consumers who are capable of returning goods, based on the tracking position information acquired from the target tracking files 68 and the behavioral position information stored in ACT522 of FIG.

[0153] In other words, the number of people N includes consumers who have returned products and consumers who have not. The number of people N is the number of consumers who are capable of returning products among the consumers in the area where the consumer is estimated to be located when returning the product. Therefore, counting the number of people N is equivalent to obtaining the number of consumers in the area who are capable of returning products.

[0154] The integration processing unit 67 checks whether the number N of consumers who can perform return behavior is 0 in ACT 573. If the number N is 0, the integration processing unit 67 judges YES in ACT 573 and proceeds to ACT 563. The integration processing unit 67 outputs voice data of a tracking error to the voice synthesis unit 66 in ACT 563. Then, the integration processing unit 67 ends the return processing.

[0155] If the number N of consumers capable of returning the product is not 0, the integration processing unit 67 judges NO in ACT573 and proceeds to ACT574. In ACT574, the integration processing unit 67 checks whether the number N of consumers capable of returning the product is 1. If the number N is 1, the one consumer can be identified as the returner. The integration processing unit 67 judges YES in ACT574 and proceeds to ACT567. The integration processing unit 67 then executes the processes of ACT567 to ACT570 in the same manner as described above.

[0156] If the number N of consumers who can perform return behavior is 2 or more, the returner cannot be identified. The integration processing unit 67 determines NO in ACT574 and proceeds to ACT575. The integration processing unit 67 executes multiple person processing in ACT575.

[0157] FIG. 18 is a flow chart showing the main steps of the multiple person processing. The integration processing unit 67 acquires the sensor number from the return notification command in ACT 601. Then, the integration processing unit 67 reads the product data, such as the product code, product name, and unit weight, stored together with the sensor number from the product data file 61 in ACT 602. The integration processing unit 67 calculates the number of returned items P in ACT 603. The integration processing unit 67 calculates the number of returned items P in the same manner as the processing in ACT 584 for single-person processing.

[0158] The integration processing unit 67 checks whether the number of returned items P has been calculated in ACT604. If the number of returned items P cannot be calculated, the integration processing unit 67 judges NO in ACT604 and proceeds to ACT605. The integration processing unit 67 outputs voice data of a wrong return error to the voice synthesis unit 66 in ACT605. As a result, the voice synthesis unit 66 synthesizes a voice indicating a wrong return error. Then, a voice such as "The product is being returned to the wrong place" is output from the speaker 5. Then, the integration processing unit 67 ends the multi-person processing.

[0159] If the number of returned items P can be calculated, the integration processing unit 67 determines YES in ACT604 and proceeds to ACT606. The integration processing unit 67 determines one of the N consumers who are capable of returning the goods in the purchasing area 112 as the returner in ACT606. For example, the integration processing unit 67 determines the consumer whose tracking location information is closest to the coordinate position specified by the behavioral location information as the returner. The integration processing unit 67 acquires the member ID associated with the tracking ID of the returner in ACT607.

[0160] The integrated processing unit 67 outputs a purchase quantity request command to the sales management device 7 in ACT608. The purchase quantity request command includes the member ID acquired in the process of ACT607 and the product code of the product data acquired in the process of ACT602.

[0161] Upon receiving the purchase quantity request command, the sales management device 7 detects the purchase quantity Q stored in association with the product code from the purchase list 71 in which the member ID is set, as described above, and responds to the integrated processing unit 67.

[0162] The integration processing unit 67 waits for the purchase quantity Q to be responded to in ACT609. When the purchase quantity Q is responded to, the integration processing unit 67 subtracts the return quantity P from the purchase quantity Q to calculate a difference value R in ACT610. The integration processing unit 67 checks whether the difference value R is negative in ACT611. If the difference value R is equal to or greater than "0" or "1", the integration processing unit 67 judges NO in ACT611 and proceeds to ACT612. The integration processing unit 67 outputs a return notification command to the sales management device 7 in ACT612. Then, the integration processing unit 67 ends the multiple user processing.

[0163] In this way, even if there are multiple consumers who are capable of returning goods, it is possible to eliminate inconsistencies between the goods actually purchased by the consumer and the goods registered in the purchase list as the consumer's purchase items before payment. That is, one of the multiple consumers who are capable of returning goods is determined to be the returner. It is confirmed that returns are possible based on the number of purchases and the number of returns of the consumer identified as the returner. A return notification command is output to the sales management device 7 to notify that the number of returns will be subtracted from the number of purchases. By executing this process before payment, the above-mentioned effects are achieved.

[0164] If the difference value R is negative, the integration processing unit 67 judges YES in ACT611 and proceeds to ACT613. In ACT613, the integration processing unit 67 checks whether the number N of consumers who can perform return behavior is 2. If the number N is 2, the integration processing unit 67 judges YES in ACT613 and proceeds to ACT614.

[0165] If the difference value R is negative, the consumer determined to be a returner in the processing of ACT606 is not a returner. Therefore, if there are two candidates for returners, the other one is determined to be a returner. That is, the integration processing unit 67 acquires the member ID associated with the tracking ID of the other consumer in ACT614. Then, the integration processing unit 67 outputs a purchase quantity request command to the sales management device 7 in ACT615. The purchase quantity request command includes the member ID acquired in the processing of ACT614 and the product code of the product data acquired in the processing of ACT602.

[0166] Upon receiving the purchase quantity request command, the sales management device 7 detects the purchase quantity Q stored in association with the product code from the purchase list 71 in which the member ID is set, as described above, and responds to the integrated processing unit 67.

[0167] The integration processing unit 67 waits for the purchase quantity Q to be responded to in ACT616. When the purchase quantity Q is responded to, the integration processing unit 67 subtracts the return quantity P from the purchase quantity Q to calculate a difference value R in ACT617. The integration processing unit 67 checks whether the difference value R is negative in ACT618. If the difference value R is equal to or greater than "0" or "1", the integration processing unit 67 judges NO in ACT618 and proceeds to ACT612. The integration processing unit 67 outputs a return notification command to the sales management device 7 in ACT612. Then, the integration processing unit 67 ends the multiple user processing.

[0168] If the difference value R is negative, the integration processing unit 67 judges YES in ACT 618 and proceeds to ACT 605. The integration processing unit 67 outputs voice data indicating a return error to the voice synthesis unit 66 in ACT 605. Thus, the integration processing unit 67 ends the multiple name processing.

[0169] If the number N of consumers who can perform return behavior is 3 or more, the returner cannot be identified. The integrated processing unit 67 judges NO in ACT613 and proceeds to ACT619.

[0170] The integrated processing unit 67 may determine, for the number N of consumers capable of returning goods, the consumers whose tracking location information is closest to the coordinate location specified by the behavioral location information, as the returner one by one in order. For example, the integrated processing unit 67 executes the processes of ACT606 to ACT611 for the relevant consumers. However, if the number N is large, it takes time to process the number N. Therefore, the process of determining one of multiple consumers capable of returning goods as the returner is limited to a predetermined number of times. For example, if the number N is a threshold of up to two people, and if the number exceeds that, return registration is performed as a provisional registration for all consumers capable of returning goods.

[0171] The integrated processing unit 67 acquires the member IDs of all consumers who are capable of returning goods in ACT619. Then, the integrated processing unit 67 outputs a provisional return notification command to the sales management device 7 in ACT620. The provisional return notification command includes all member IDs acquired in the process of ACT619, the product code, product name, and unit price of the product data read in the process of ACT602, and the number of returned items P calculated in the process of ACT603. In this way, the processes in ACT619 and ACT620 correspond to an abnormality processing means for executing an abnormality process when there are multiple people.

[0172] The integrated processing unit 67 outputs, as ACT 621, voice data to the voice synthesis unit 66 indicating that the return registration has been provisionally registered. As a result, the voice synthesis unit 66 synthesizes a voice indicating that the return registration has been provisionally registered. Then, the speaker 5 outputs a voice such as "The return data has been provisionally registered. Please inform a store clerk." Then, the integrated processing unit 67 ends the multi-person processing. When the single person processing or multiple person processing is completed in this manner, the integrated processing unit 67 ends the return processing.

[0173] In addition to outputting the provisional registration as voice data in ACT 621, information indicating that the provisional registration has occurred may be output to a terminal operated by a store clerk. By doing so, a notification that the provisional registration has occurred is issued from the terminal, allowing the store clerk to deal with the provisional registration appropriately.

[0174] Furthermore, the abnormality processing in which the returner cannot be identified may be performed in the following situations. For example, it may be performed in response to determining that the number M of consumers in the purchasing area 112 is two or more. That is, all consumers in the purchasing area 112 may be provisionally registered. Alternatively, in response to determining that the number N of consumers in the purchasing area 112 who are capable of returning an item is two or more, all consumers who are capable of returning an item may be provisionally registered without determining one of the N consumers who are capable of returning an item as the returner. Either of these corresponds to performing the abnormality processing when a return behavior is recognized and there is more than one consumer in the area where the returner is estimated to be located when returning the item.

[0175] In this way, the integrated processing unit 67 executes return processing for the consumer's return behavior, thereby identifying one consumer in the purchasing area 112 as a returner who has returned a product to the shelf 10. The integrated processing unit 67 then checks whether or not the consumer identified as the returner has purchased the product that he or she has returned to the shelf, that is, the returned product. If the consumer has purchased a returned product, that is, if the difference value R obtained by subtracting the returned product number P from the purchased product number Q is equal to or greater than 0, the integrated processing unit 67 sends a return notification command to the sales management device 7, which includes the member ID of the consumer identified as the returner and data on the returned product.

[0176] On the other hand, if the consumer has not purchased a returned product, that is, if the difference value R obtained by subtracting the number of returned products P from the number of purchased products Q is negative, the integration processing unit 67 notifies an error of wrong return.

[0177] If there are two consumers in the purchasing area 112 and it is determined that the first consumer has not purchased a returned product, the processing unit 67 checks whether the second consumer has purchased a returned product. If the second consumer has purchased a returned product, that is, if the difference R obtained by subtracting the number of returned products P from the number of purchased products Q is equal to or greater than 0, the integration processing unit 67 sends a return notification command including the member ID of the second consumer and data on the returned product to the sales management device 7.

[0178] On the other hand, if the second consumer also did not purchase the returned product, that is, if the difference value R obtained by subtracting the returned quantity P from the purchased quantity Q is negative, the integrated processing unit 67 notifies an incorrect return error.

[0179] Furthermore, if there are three or more consumers in the purchasing area 112, the integrated processing unit 67 transmits to the sales management device 7 a provisional return notification command including the member ID of each consumer and data on the returned product.

[0180] Next, the operation of the sales management device 7 that receives the return notification command or the temporary return notification command will be described with reference to FIGS. 21 and 22. FIG. 21 is a flow chart showing the operation procedure of the sales management device 7 that has received a return notification command. The sales management device 7 acquires the member ID from the return notification command as ACT711. The sales management device 7 creates returned product data as ACT712 based on the product data included in the return notification command, that is, the product code, product name, unit price, and the number of returned items P. The returned product data is the purchased product data replaced with the number of returned items P.

[0181] The sales management device 7 selects, in ACT 713, purchased product data whose product code matches the returned product data from the purchase list 71 in which the member ID acquired in the processing of ACT 701 is set. Then, in ACT 714, the sales management device 7 subtracts the return quantity P of the returned product data from the purchase quantity of the selected purchased product data. With this, the sales management device 7 ends the operation of the procedure shown in the flowchart of FIG.

[0182] In this way, when the sales management device 7 receives a return notification command from the integrated processing unit 67, it subtracts the purchased quantity of the purchased item data related to the returned item in the purchase list 71 for which the member ID included in the return notification command is set by the returned item quantity P. At this time, the provisional registration flag of the purchased item data after subtracting the purchased quantity is "0".

[0183] 22 is a flow chart showing the operation procedure of the sales management device 7 that receives a provisional registration notification command. The sales management device 7 creates a list of member IDs included in the provisional registration notification command in ACT721. Hereinafter, this list will be referred to as the member ID list. The sales management device 7 counts the number V of member IDs included in the member ID list in ACT722. The sales management device 7 also resets the addition counter W to "0" in ACT723. Next, the sales management device 7 counts up the addition counter W by "1" in ACT724. The sales management device 7 then checks whether the addition counter W has exceeded the number V in ACT725.

[0184] If the count W does not exceed the number V, the sales management device 7 acquires the Wth member ID from the member ID list as ACT726. The Wth "W" is the value of the count W. The sales management device 7 subtracts the product data included in the provisional return notification command from the purchase list 71 in which the Wth member ID is set as ACT727. Specifically, if the purchase list 71 contains purchased product data of the product code contained in the provisional return notification command, the sales management device 7 subtracts the purchased quantity of the purchased product data by the returned quantity P contained in the provisional return notification command. If the purchase list 71 does not contain purchased product data of the product code, the sales management device 7 creates purchased product data based on the product code, product name, unit price, and returned quantity P contained in the purchase notification command. In this case, the returned quantity P is included in the purchased product data as a negative purchased quantity. The sales management device 7 adds the purchased product data to the purchase list 71.

[0185] The sales management device 7 sets the provisional registration flag of the purchased item data in which the purchased quantity has been subtracted by the returned item quantity P or the purchased item data including a negative purchased quantity to "1" as ACT728. In addition, the sales management device 7 sets the member ID of another person registered in the member ID list in the other person member ID area of ​​the purchased item data as ACT729.

[0186] After that, the sales management device 7 returns to the process of ACT724. The sales management device 7 further counts up the counting counter W by "1". Then, if it is confirmed that the counting counter W does not exceed the number V, the sales management device 7 executes the processes of ACT726 to ACT729 again.

[0187] In this way, the sales management device 7 repeatedly executes the processes of ACT724 to ACT729 until the counting counter W exceeds several V. If the counting counter W exceeds several V, the sales management device 7 judges YES in ACT725 and proceeds to ACT730. The sales management device 7 clears the member ID list. With this, the sales management device 7 ends the process of receiving the temporary return notification command.

[0188] In this way, when the sales management device 7 receives the provisional registration notification command from the integrated processing unit 67, the data of the returned goods is subtracted from each purchase list 71 in which all the member IDs included in the provisional registration notification command are set. The provisional registration flag of the purchased goods data from which the data of the returned goods has been subtracted becomes "1".

[0189] The integrated processing unit 67, which executes return processing in cooperation with the tracking processing unit 62, the product monitoring processing unit 64, and the behavior monitoring processing unit 65, has the functions of a recognition means for recognizing a product return behavior by a consumer, an identification means for identifying the consumer who performed the return behavior, a return processing means, and an abnormality processing means. That is, when the integrated processing unit 67 recognizes a product return behavior and identifies the consumer who performed the return behavior, it outputs a return notification command to the sales management device 7 for deducting the data of the product from the purchase list 71 of that consumer. However, if deducting the data of the product from the purchase list 71 causes the data of the purchase list 71 to become an abnormal value, the integrated processing unit 67 does not output the return notification command. The integrated processing unit 67 executes abnormality processing.

[0190] Specifically, when the difference value R between the number of purchased items Q and the number of returned items P is negative, that is, when the number of purchased items after subtracting the number of returned items P becomes negative, the data in the purchase list 71 becomes an abnormal value. When the integrated processing unit 67 judges YES in ACT590 of the single-person processing, it executes the processing of ACT586. That is, when a second consumer who performed the return behavior is not identified other than the first consumer identified by the identification means, the integrated processing unit 67 executes the processing of notifying the user of the wrong return location as the abnormality processing.

[0191] Furthermore, if the integration processing unit 67 judges YES in ACT611 of the multiple consumer processing and then judges YES in ACT613, it executes the processing of ACT614 to ACT618. If the integration processing unit 67 judges NO in ACT618, it executes the processing of ACT612. That is, if only one second consumer is identified, the integration processing unit 67 checks whether subtracting the data of the product from the purchase list 71 of the second consumer will cause the data of the purchase list 71 to become an abnormal value. If the data is not an abnormal value, the integration processing unit 67 executes the processing of subtracting the data of the product from the purchase list of the second consumer as an abnormality processing.

[0192] Moreover, when the integrated processing unit 67 judges NO in ACT613 of the multiple-person processing, it executes the processing of ACT619 to ACT621. That is, when multiple second consumers are identified, the integrated processing unit 67 cooperates with the sales management device 7 to subtract the data of the corresponding product from the purchase list 71 of each second consumer, and executes a process indicating that the data after subtraction is provisional data as an abnormality process.

[0193] Next, the operation of the integrated processing unit 67 upon receiving an exit notification command will be described with reference to the flowchart of FIG. The integration processing unit 67 acquires a tracking ID from the exit notification command in ACT631. In ACT632, the integration processing unit 67 searches the association table 69 to check whether a member ID is associated with the tracking ID. If a member ID is not associated, the consumer managed by the tracking ID is a consumer who left the store without undergoing personal authentication. Therefore, the integration processing unit 67 judges NO in ACT632 and ends this process.

[0194] If a member ID is associated with the tracking ID, the integration processing unit 67 determines YES in ACT 632 and proceeds to ACT 633. The integration processing unit 67 acquires the member ID associated with the tracking ID in ACT 633. Then, the integration processing unit 67 makes a confirmation request to the sales management device 7 for the purchase list 71 in which the member ID is set in ACT 634.

[0195] In response to this confirmation request, the sales management device 7 confirms whether or not purchased product data with the provisional registration flag set to "1" exists in the purchase list 71 in which the member ID is set. Hereinafter, purchased product data with the provisional registration flag set to "1" will be referred to as provisional purchased product data. Then, the sales management device 7 responds with the confirmation result to the integrated processing unit 67.

[0196] The integration processing unit 67 determines whether or not temporary purchase product data exists in the purchase list 71 in which the member ID is set in ACT635. If temporary purchase product data does not exist, the integration processing unit 67 determines NO in ACT635 and proceeds to ACT636. The integration processing unit 67 outputs a payment permission notification command to the sales management device 7 in ACT636. The payment permission notification command includes the member ID acquired in the processing of ACT633.

[0197] On the other hand, if the provisionally purchased product data exists, the integration processing unit 67 judges YES in ACT635 and proceeds to ACT637. The integration processing unit 67 outputs a payment confirmation notification command to the sales management device 7 in ACT637. The payment confirmation notification command includes the member ID acquired in the processing of ACT633. When the integrated processing unit 67 outputs the payment permission notification command or the payment confirmation notification command, the operation of the procedure shown in the flowchart of FIG. 19 ends.

[0198] In this way, when the integrated processing unit 67 receives an exit notification command, it determines that a payment instruction has been made. The integrated processing unit 67 then outputs a payment permission notification to the sales management device 7 for consumers whose purchase list 71 does not contain purchased product data with a provisional registration flag of "1". In response, the integrated processing unit 67 outputs a payment confirmation notification to the sales management device 7 for consumers whose purchase list 71 contains purchased product data with a provisional registration flag of "1".

[0199] 23 is a flow chart showing the operation of the sales management device 7 that has received the payment permission notification command. The sales management device 7 acquires the member ID from the payment permission notification command as ACT 741. The sales management device 7 selects the purchase list 71 in which the member ID is set as ACT 742. The sales management device 7 also requests, from the member server 8 as ACT 743, information related to the payment registered by the consumer identified by the member ID.

[0200] In response to this request, the member server 8 searches the member database 81 to obtain the payment-related information registered by the consumer, and returns the information to the sales management device 7. The sales management device 7 waits for a response of information related to the payment in ACT744. When there is a response of information related to the payment from the member server 8, the sales management device 7 judges YES in ACT744 and proceeds to ACT745. The sales management device 7 outputs the purchased product data registered in the purchase list 71 together with the information related to the payment to the payment server 9 in ACT745, and requests payment. In response to this request, the payment server 9 executes a payment process. For example, if the information related to the payment is information related to a credit card payment, a credit card payment process is executed. For example, if the information related to the payment is information necessary for electronic payment using a barcode, two-dimensional code, or the like, a payment process by electronic payment is executed. With this, the sales management device 7 ends the process for the payment permission notification command.

[0201] 24 is a flow chart showing the operation of the sales management device 7 that has received a payment confirmation notification command. The sales management device 7 acquires the member ID from the payment confirmation notification command as ACT 751. The sales management device 7 selects the purchase list 71 in which the member ID is set as ACT 752. The sales management device 7 also requests information related to the user terminal TM of the consumer identified by the member ID from the member server 8 as ACT 753.

[0202] In response to this request, the member server 8 searches the member database 81 to obtain the terminal information registered by the consumer, and returns the information to the sales management device 7. The sales management device 7 waits for a response of the terminal information in ACT 754. When the member server 8 responds with the terminal information, the sales management device 7 judges YES in ACT 754 and proceeds to ACT 755. The sales management device 7 communicates with the user terminal TM specified by the terminal information in ACT 755, and makes a request to confirm the purchase quantity of the provisionally purchased product data.

[0203] In response to this confirmation request, the touch panel of the user terminal TM displays the product name and purchased quantity of the provisionally purchased product data. The consumer confirms whether or not they have purchased the displayed number of products. If they have purchased the purchased number, the consumer performs an operation to notify the sales management device 7 that the purchased quantity is correct. If they have not purchased the displayed product or if the purchased quantity is incorrect, the consumer corrects the purchased quantity. In other words, if they have not purchased the product, the consumer sets the purchased quantity to "0". If the purchased quantity is incorrect, the consumer corrects it to the correct quantity.

[0204] The sales management device 7 waits in ACT756 for a notification that the purchased quantity is correct or for the purchased quantity to be corrected. If the purchased quantity has been corrected, the sales management device 7 judges NO in ACT756 and proceeds to ACT757. The sales management device 7 corrects the purchase list 71 in ACT757. Specifically, the sales management device 7 changes the purchased quantity of the corresponding purchased product data to the corrected quantity and sets the provisional registration flag to "0". Thereafter, the sales management device 7 proceeds to the processing of ACT743 in FIG. 23. The sales management device 7 then executes the processing of ACT743 to ACT745 in the same manner as described above.

[0205] If the notification that the purchased quantity is correct is received, the sales management device 7 judges YES in ACT756 and proceeds to ACT758. The sales management device 7 sets the provisional registration flag of the corresponding purchased product data to "0" in ACT758. The sales management device 7 also acquires the other member ID of the corresponding purchased product data in ACT759. Then, the sales management device 7 corrects the purchase list 71 in which the other member ID is set in ACT760. Specifically, the sales management device 7 returns the purchased product data registered in the other person's purchase list 71 with the provisional registration flag set to "1" to the state before the provisional registration flag was set to "1". Then, the sales management device 7 sets the provisional registration flag to "0". Thereafter, the sales management device 7 proceeds to the processing of ACT743 in FIG. 23. Then, the sales management device 7 executes the processing of ACT743 to ACT745 in the same manner as described above.

[0206] Here, the integrated processing unit 67 cooperates with the sales management device 7 to function as a payment control means. That is, in response to a payment instruction, the integrated processing unit 67 checks with the sales management device 7 whether or not there is provisional purchase product data in the consumer's purchase list 71. If there is no data indicated as provisional data, that is, no provisional purchase product data, the integrated processing unit 67 outputs a payment permission notice to the sales management device 7. As a result, the purchase list data is sent from the sales management device 7 to the payment server 9, and the payment process is executed.

[0207] On the other hand, if temporary purchased product data exists, the integrated processing unit 67 outputs a payment confirmation notice to the sales management device 7. As a result, the sales management device 7 executes a process to have the consumer confirm the purchase quantity of the temporary purchased product data. Then, when confirmation of the purchase quantity is completed, the sales management device 7 transmits the purchase list data to the payment server 9, and the payment process is executed.

[0208] This concludes the explanation of the operation of the store system 100. The store system 100 of this embodiment can provide the following advantageous effects. First, assume that when consumer SA returns product A to the shelf 10, he or she mistakenly returns it to the section 203 of product C, which has a different unit weight. In this case, the integrated processing unit 67 judges NO in ACT 585 of the single-person processing shown in FIG. 17. Alternatively, it judges NO in ACT 604 of the multiple-person processing shown in FIG. 18. As a result, a voice such as "The product is being returned to the wrong place" is output from the speaker 5. Therefore, the mistake of returning a product to a section of another product with a different unit weight can be easily discovered.

[0209] Next, suppose that consumer SA returns product A to the section 202 for product B, which has the same unit weight. In this case, the process is divided according to the number of consumers who can return the product in the purchasing area 112. If the number of consumers is one, the integrated processing unit 67 executes the process of ACT587 to ACT590 of the one-person process shown in FIG. 17. Here, if it is assumed that consumer SA did not purchase product B, the difference value R calculated in ACT589 becomes negative. As a result, the integrated processing unit 67 judges YES in ACT590, and outputs a voice from the speaker 5, such as "The product is being returned to the wrong place." Therefore, the mistake of returning a product to a section for another product with the same unit weight can be easily discovered.

[0210] On the other hand, if consumer SB is present in addition to consumer SA as a consumer capable of returning the product, the integrated processing unit 67 executes the processing of ACT606 to ACT618 of the multi-person processing shown in Fig. 18. If it is assumed that neither consumer SA nor consumer SB has purchased product B, the difference value R calculated in ACT610 and ACT618 will be negative. As a result, the integrated processing unit 67 judges YES in ACT618, and outputs a voice such as "The product is being returned to the wrong place" from the speaker 5. This makes it easy to discover the mistake of returning a product to a section of another product with the same unit weight.

[0211] Next, assume that there are consumers SA and SB who are capable of returning the product, and that consumer SB returns the product B to the section 202. In this case, if consumer SA is closer to the section 202 than consumer SB, the integrated processing unit 67 first identifies consumer SA as the returner in ACT606 of the multiple person processing. If it is assumed here that consumer SA has not purchased product B, the integrated processing unit 67 judges YES in ACT611 of the multiple person processing, and also judges YES in ACT613, and proceeds to ACT614. In ACT614, consumer SB is identified as the returner. As a result, ACT618 is judged as NO, and a return notification command is output to the sales management device 7. Thus, the purchased product data of product B is subtracted by the number of returned items from the purchase list 712 of consumer SB.

[0212] Next, assume that there are consumers SA, SB, and SC who are able to perform return behavior, and that consumer SB performs return behavior of returning only one purchased item B to the section 202. In this case, if consumer SA is closest to section 202, the integrated processing unit 67 first identifies consumer SA as the returner in ACT606 of the multiple person processing. Here, if it is assumed that consumer SA did not purchase item B, the integrated processing unit 67 judges YES in ACT611 of the multiple person processing, judges NO in ACT613, and executes the processing of ACT619 to ACT621. As a result, purchased item data with the purchased number of item B set to "-1" is provisionally registered in the purchase list 711 of consumer SA. Also, purchased item data with the purchased number of item B set to "0" is provisionally registered in the purchase list 712 of consumer SB. Also, if it is assumed that consumer SC purchased two items B, purchased item data with the purchased number of item B set to "1" is provisionally registered in the purchase list 713 of consumer SC.

[0213] Thereafter, for example, it is assumed that consumer SA is the first to leave tracking area 111. Then, a screen is displayed on consumer SA's user terminal TM, prompting the consumer to confirm whether the number of purchased items of product B is "-1" or not. In this case, since the actual number of purchased items is "0", consumer SA corrects the number of purchased items to "0". The payment server 9 executes payment processing based on the data of purchase list 711 with the corrected number of purchased items.

[0214] Next, suppose that consumer SB leaves the tracking area 111. Then, a screen is displayed on consumer SB's user terminal TM, asking whether the number of purchased items of product B is "0". In this case, since the actual number of purchased items is "0", consumer SB does not modify the number of purchased items. The payment server 9 executes the payment process based on the data in the purchase list 712. At this time, the number of purchased items in the purchased item data of product B stored in consumer SC's purchase list 713 is returned from "1" to "2". The provisional registration flag of this purchased item data becomes "0". Therefore, if consumer SC subsequently leaves the tracking area 111, the payment server 9 executes the payment process based on the data in the purchase list 713.

[0215] As described above in detail, according to this embodiment, the mistake of returning a product to a section of another product can be easily found. In addition, the number of returned items can be reduced from the purchase list of the consumer who performed the return action. It is also possible to identify whether or not the return process has been completed from the purchase list data. It is also possible to prevent payment from being made with a purchase list including temporary data. Furthermore, if the purchaser cannot be identified, the purchase list is not changed. Therefore, it is possible to prevent inconsistencies between the actual purchased items and the purchased items in the purchase list before payment. Furthermore, it is possible to prevent inconsistencies in the purchase list data due to the return of a product. If it is difficult to identify the returner, it is also possible to prevent inconsistencies in the purchase list data due to the return of a product. It is also possible to narrow down the number of consumers who performed the return action. Therefore, it is possible to eliminate inconsistencies between the products actually purchased by the consumer and the products registered as the purchased items of that consumer.

[0216] A modification of this embodiment will now be described. The tracking processing unit 62 analyzes the image data captured from the tracking sensors 21 and 22 to track the movement of the consumer in the tracking area 111. The tracking processing unit 62 may track the movement of the consumer based on information from a receiver that receives a beacon transmitted from a transmitter carried by the consumer.

[0217] The personal authentication processing unit 63 may authenticate the consumer by biometric authentication. In this case, the personal authentication devices 41 and 42 are devices that read biometric information such as a face, an iris, or a fingerprint.

[0218] The product monitoring processing unit 64 may monitor the movement of the product from images captured by the camera. In this case, it is possible to detect that the product has been returned to the wrong place based on the similarity between the image of the product captured by the camera and a preset image of the product. The merchandise monitoring sensor 1 may detect an increase or decrease in the quantity of merchandise on display. In this case, when the quantity data from the merchandise monitoring sensor 1 decreases, the merchandise monitoring processing unit 64 recognizes that a merchandise has been removed from the section in which the merchandise monitoring sensor 1 is installed. When the quantity data from the merchandise monitoring sensor 1 increases, the merchandise monitoring processing unit 64 recognizes that a merchandise has been placed in the section in which the merchandise monitoring sensor 1 is installed.

[0219] An image processing unit may be used instead of the voice synthesis unit 66, and notification may be made by displaying an image. Alternatively, notification may be made by using both voice and image.

[0220] In this embodiment, the integrated processing unit 67 executes the process shown in the flowchart of Fig. 19 in response to an exit notification command. In this regard, when the integrated processing unit 67 receives a payment notification command including a member ID from a POS terminal connected to the communication network, the integrated processing unit 67 may execute the process from ACT632 in Fig. 19 onwards.

[0221] In this embodiment, the shelf control device 6 is exemplified as the data processing device. The data processing device is not limited to the shelf control device 6 having the configuration shown in FIG. 3. For example, the data processing device may be configured by connecting a first computer device including a tracking processing unit 62, a personal authentication processing unit 63, a product monitoring processing unit 64, and a behavior monitoring processing unit 65 and a second computer device including an integrated processing unit 67 and a voice synthesis unit 66 via a communication network. Alternatively, the first computer device may be further subdivided, or the voice synthesis unit 66 may be excluded from the second computer device.

[0222] Furthermore, the shelf control device 6 recognizes purchasing behavior and return behavior for products displayed on the shelf 10. From the viewpoint of product hygiene, the shelf 10 may be divided into shelves for displaying products only for purchase and shelves for displaying products only for return. In this case, the shelf control device for displaying products only for purchase has a function related to purchase. On the other hand, the shelf control device (data processing device) for displaying products only for return has a function related to return. The configuration of the shelf for displaying products only for return may be the same as that of the shelf 10 described in this embodiment, and may be, for example, disposed inside the fourth boundary line 104 next to the shelf for displaying products only for purchase.

[0223] Although several other embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be implemented 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 of the invention and the scope of the invention and its equivalents described in the claims. The invention as originally claimed in the present application is set forth below. [1] A data processing device comprising: a recognition means for recognizing a consumer's product purchasing behavior or product return behavior; an identification means for identifying a consumer who has performed the purchasing behavior or product return behavior; a purchase processing means for, when a product purchasing behavior is recognized by the recognition means, adding data of the product to a purchase list of the consumer identified by the identification means as having performed the purchasing behavior; a return processing means for, when a product return behavior is recognized by the recognition means, subtracting data of the product from the purchase list of the consumer identified by the identification means as having performed the return behavior; and an abnormality processing means for executing abnormality processing if the data in the purchase list becomes an abnormal value due to the subtraction of the data of the product from the purchasing list. [2] The data processing device described in Appendix [1], wherein the abnormality processing means executes a process of notifying an incorrect return location as abnormality processing when a second consumer who has performed return behavior other than the first consumer identified by the identification means is not identified. [3] A data processing device as described in appendix [1] or [2], wherein when a second consumer who has performed return behavior other than the first consumer identified by the identification means is identified, the abnormality processing means checks whether subtracting the data of the product from the purchasing list of the second consumer would result in an abnormal value in the purchasing list, and if the data is not abnormal, executes a process of subtracting the data of the product from the purchasing list of the second consumer as abnormality processing. [4] A data processing device as described in Appendix [3], wherein when multiple second consumers who have performed return behavior are identified other than the first consumer identified by the identification means, the abnormality processing means subtracts the data of the relevant product from the purchase list of each second consumer and executes a process indicating that the data after subtraction is provisional data as abnormality processing. [5] A data processing device as described in appendix [4], further comprising a payment control means for, in response to a payment instruction, checking whether data indicated as temporary data is present in the consumer's purchase list, and allowing payment if such data is not present. [6] A data processing device as described in appendix [1], further comprising an alarm means for, when the identification means is unable to identify the consumer who performed the purchasing behavior, notifying the occurrence of a purchasing error without adding the product data to a purchasing list. [7] A data processing device comprising: a recognition means for recognizing a consumer's return of a product; an identification means for identifying the consumer who has performed the return behavior; a return processing means for subtracting data of the returned product from a purchasing list of the consumer identified by the identification means when the recognition means recognizes the return behavior of the product; and an abnormality processing means for executing abnormality processing if the data of the product in the purchasing list becomes an abnormal value as a result of subtracting the data of the product from the purchasing list. [8] A data processing device comprising: a recognition means for recognizing a consumer's return behavior; a determination means for identifying the consumer who has performed the return behavior; a number of consumers acquisition means for, when the return behavior is recognized by the recognition means, acquiring the number of consumers in the area where the consumer is estimated to be located when returning the product; a return processing means for, when the number of consumers is one, identifying the consumer who has performed the return behavior using the determination means and subtracting the data of the returned product from the consumer's purchasing list; and an abnormality processing means for, when the number of consumers is multiple, executing abnormality processing. [9] The data processing device according to claim [8], wherein the number of consumers acquisition means acquires the number of consumers in the area who are capable of returning products.

[10] A control program for causing a computer as a data processing device to function as: recognition means for recognizing a consumer's product purchasing behavior or product return behavior; identification means for identifying the consumer who has performed the purchasing behavior or product return behavior; purchase processing means for, when a product purchasing behavior is recognized by the recognition means, adding data of the product to a purchase list of the consumer identified by the identification means as having performed the purchasing behavior; return processing means for, when a product return behavior is recognized by the recognition means, subtracting data of the product from the purchase list of the consumer identified by the identification means as having performed the return behavior; and abnormality processing means for executing abnormality processing when the data of the product in the purchase list becomes an abnormal value due to the subtraction of the data of the product from the purchasing list. [Explanation of symbols]

[0224] 1...product monitoring sensor, 21, 22...tracking sensor, 3...behavior monitoring sensor, 41, 42...personal authentication device, 5...speaker, 6...shelf control device, 7...sales management device, 8...membership server, 9...payment server, 10...shelf, 61...product data file, 62...tracking processing unit, 63...personal authentication processing unit, 64...product monitoring processing unit, 65...behavior monitoring processing unit, 66...voice synthesis unit, 67...integration processing unit, 68...tracking file, 69...association table, 71...purchase list, 81...membership database, 100...store system.

Claims

1. A recognition means for recognizing a consumer's product purchasing behavior or return behavior; A means for identifying a consumer who has performed the purchasing behavior or the returning behavior; a purchase processing means for adding data of the product to a purchase list of the consumer identified by the identification means as having engaged in the purchasing behavior of the product when the purchasing behavior of the product is recognized by the recognition means; a return processing means for, when the recognition means recognizes a return behavior of a product, deducting data of the product from a purchase list of the consumer identified by the identification means as having performed the return behavior; an abnormality processing means for, when subtracting the data of the product from the purchase list causes the data of the purchase list to become abnormal, and if a second consumer who has returned the product other than the first consumer specified by the identification means is not identified, executing a process to notify that the return location is incorrect, and, when a second consumer who has returned the product other than the first consumer is identified, confirming whether subtracting the data of the product from the purchase list of the second consumer causes the data of the purchase list to become abnormal, and if it does not, executing a process to subtract the data of the product from the purchase list of the second consumer; A data processing device comprising:

2. 2. A data processing device as described in claim 1, wherein the abnormality processing means executes a process to notify an incorrect return location when the data of the product in question becomes abnormal by subtracting the data of the purchase list of the second consumer.

3. The data processing device according to claim 1, wherein the abnormality processing means, when multiple second consumers who have performed return behavior other than the first consumer identified by the identification means are identified, subtracts the data of the relevant product from the purchasing list of each second consumer and executes a process indicating that the data after subtraction is provisional data.

4. a payment control means for checking whether or not the data indicated as provisional data exists in the consumer's purchase list in response to a payment instruction, and allowing the payment if the data does not exist; The data processing apparatus of claim 3 further comprising:

5. a notification means for notifying the occurrence of a purchase error without adding the data of the product to a purchase list when the identification means is unable to identify the consumer who made the purchase; The data processing apparatus of claim 1 further comprising:

6. A recognition means for recognizing a consumer's product purchasing behavior or return behavior; A means for identifying a consumer who has performed the purchasing behavior or the returning behavior; a purchase processing means for adding data of the product to a purchase list of the consumer identified by the identification means as having engaged in the purchasing behavior of the product when the purchasing behavior of the product is recognized by the recognition means; a return processing means for, when the recognition means recognizes a return behavior of a product, deducting data of the product from a purchase list of the consumer identified by the identification means as having performed the return behavior; an abnormality processing means for, when the data of the purchase list becomes abnormal as a result of subtracting the data of the product from the purchase list, executing a process of notifying an incorrect return location if a second consumer who has returned the product other than the first consumer identified by the identification means is not identified, and, when a second consumer who has returned the product other than the first consumer is identified, subtracting the data of the product from the purchase lists of the first consumer and the second consumer, respectively, and executing a process of indicating that the data after subtraction is provisional data; A data processing device comprising:

7. A recognition means for recognizing a product return behavior by a consumer; A means for identifying a consumer who has performed the return behavior; a return processing means for subtracting data of the returned product from the purchase list of the consumer identified by the identification means when the recognition means recognizes a product return behavior; an abnormality processing means for, when subtracting the data of the product from the purchase list causes the data of the purchase list to become abnormal, executing a process to notify an incorrect return location if a second consumer who has returned the product other than the first consumer specified by the identification means is not identified, and, when a second consumer who has returned the product other than the first consumer is identified, confirming whether subtracting the data of the product from the purchase list of the second consumer causes the data of the purchase list to become abnormal, and, if not, executing a process to subtract the data of the product from the purchase list of the second consumer; A data processing device comprising:

8. A number acquisition means for acquiring the number of consumers in an area in which the consumer is estimated to be located when returning the product when the recognition means recognizes a return behavior; The data processing apparatus according to claim 1 or 7, further comprising:

9. 9. The data processing device according to claim 8, wherein said number-of-consumers acquiring means acquires the number of consumers in said area who are capable of returning the product.

10. A computer as a data processing device A recognition means for recognizing a consumer's purchase or return behavior; A means for identifying a consumer who has performed the purchasing behavior or return behavior; a purchase processing means for adding data of the product to a purchase list of the consumer identified by the identification means as having engaged in the purchasing behavior of the product when the purchasing behavior of the product is recognized by the recognition means; a return processing means for, when the recognition means recognizes a return behavior of a product, deducting data of the product from a purchase list of the consumer identified by the identification means as having performed the return behavior; and an abnormality processing means for, when the data of the purchase list becomes an abnormal value by subtracting the data of the product from the purchase list, executing a process to notify an incorrect return location if a second consumer who has performed return behavior other than the first consumer identified by the identification means is not identified, and, when a second consumer who has performed return behavior other than the first consumer is identified, confirming whether the data of the purchase list becomes an abnormal value by subtracting the data of the product from the purchase list of the second consumer, and, when it does not become an abnormal value, executing a process to subtract the data of the product from the purchase list of the second consumer; A control program that functions as a

Images