Sales Management System

Abstract

To provide a sales management system that enables effective control of unauthorized exit from a store and also allows a customer who did not purchase items to exit normally.SOLUTION: A sales management system according to an embodiment includes: a registration device that performs item registration based on the operation of a customer purchasing an item; and a gate device that performs error processing when information indicating that payment for the item registered by the registration device has been completed is not input when a customer passes through the gate device. The registration device includes a reception unit that accepts discontinuance information indicating that the customer discontinues shopping without purchasing the item; and an output unit that outputs passage information for passing through the gate device when the reception unit accepts the discontinuation information. The gate device includes: an input unit to which the passage information output by the output unit is input; and a processing unit that allows the customer to pass through without performing error processing when the passage information is input to the input unit.SELECTED DRAWING: Figure 14

Description

[Technical Field]

[0001] An embodiment of the present invention relates to a sales management system. [Background technology]

[0002] In recent years, supermarkets, mass retailers, and other stores have been reducing their manpower due to labor shortages. For example, an increasing number of stores are introducing systems that allow customers who purchase goods or services (hereinafter collectively referred to as "goods") to register their products and pay at the cash register.

[0003] In such stores, measures are taken to prevent customers from fraudulently leaving the store without paying, such as installing gate devices in the checkout area where the checkout device is installed or at the exit of the store. One known gate device of this type reads a code symbol printed on a receipt issued by the checkout device to check that the customer has completed payment and then allows the customer to pass through (for example, Patent Document 1). Customers who have paid correctly can exit the checkout area or the store normally (hereinafter also referred to as "normal exit") without the gate device performing any abnormal processing.

[0004] In order to effectively prevent customers from leaving the store improperly, some stores have a system in place where all customers who enter the sales floor must pass through a gate device before leaving. However, this system has the problem that customers who enter the sales floor but do not end up purchasing an item cannot pass through the gate device and exit normally because they do not have a receipt. Summary of the Invention [Problem to be solved by the invention]

[0005] The problem to be solved by the present invention is to provide a sales management system that can effectively prevent unauthorized store exits and also allows customers who do not purchase any products to exit normally. [Means for solving the problem]

[0006] A sales management system according to an embodiment includes a registration device that performs product registration based on an operation of a customer who purchases a product, and a gate device that performs error processing if information indicating that payment for a product registered in the registration device has been completed is not input when the customer passes through. The sales management system includes a product registration information storage unit that stores product registration information indicating whether or not a product has been registered based on an operation of the customer. Store server The registration device further comprises a receiving unit that receives cancellation information indicating that the customer will cancel shopping without purchasing a product, and when the receiving unit receives the cancellation information, refers to the product registration information storage unit and stores the registered product information. A check section checks that there are no registered products, and An output unit outputs passage information for passing through the gate device, and the gate device comprises an input unit to which the passage information output by the output unit is input, and a processing unit that allows the customer to pass through without performing error processing when the passage information is input to the input unit. [Brief explanation of the drawings]

[0007] [Figure 1] FIG. 1 is a diagram showing an outline of a sales management system according to the first embodiment. [Figure 2] FIG. 2 is a diagram showing a sales floor of a store that employs the sales system according to the first embodiment. [Figure 3] FIG. 3 is a diagram showing an outline of the operations of a customer from entering a sales floor to leaving the sales floor in the first embodiment. [Figure 4] FIG. 4 is a block diagram showing the hardware configuration of the mobile terminal according to the first embodiment. [Figure 5] FIG. 5 is a block diagram showing the functional configuration of the mobile terminal according to the first embodiment. [Figure 6] FIG. 6 is a block diagram showing the hardware configuration of the gate device in the first embodiment. [Figure 7] FIG. 7 is a block diagram showing the functional configuration of the gate device in the first embodiment. [Figure 8] FIG. 8 is a diagram showing a receipt according to the first embodiment. [Figure 9] FIG. 9 is a block diagram showing the hardware configuration of the store server in the first embodiment. [Figure 10] FIG. 10 is a diagram illustrating the data structure of a status management file stored in the memory unit of the store server in the first embodiment. [Figure 11] FIG. 11 is a diagram showing the data structure of the processing master stored in the memory unit of the store server in the first embodiment. [Figure 12] FIG. 12 is a diagram showing the data structure of a customer fraud degree management file stored in the memory unit of the store server in the first embodiment. [Figure 13] FIG. 13 is a block diagram showing the functional configuration of the store server in the first embodiment. [Figure 14] FIG. 14 is a flowchart showing the flow of processing by the control unit of the mobile terminal in the first embodiment. [Figure 15] FIG. 15 is a flowchart showing the flow of processing by the control unit of the gate device in the first embodiment. [Figure 16] FIG. 16 is a sequence chart showing the flow of operations of the sales management system in the second embodiment. [Figure 17] FIG. 17 is a flowchart showing the flow of processing by the control unit of the mobile terminal in the second embodiment. [Figure 18] FIG. 18 is a sequence chart showing the flow of operations of the sales management system in the third embodiment. [Figure 19] FIG. 19 is a flowchart showing the flow of processing by the control unit of the gate device in the third embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0008] The following describes a sales management system according to an embodiment. Note that the present invention is not limited to the embodiments described below. For example, in this embodiment, a customer-owned mobile terminal, such as a smartphone with a shopping application program installed, is described as an example of a registration device, but the present invention is not limited to this. The registration device may be a tablet terminal provided by the store or a self-service POS (Point of Sales) terminal, as long as product registration is performed by the customer. Furthermore, when a customer passing through the gate device is determined to be exiting improperly, the gate device according to this embodiment outputs an error message by voice or display as error processing, but may also close the door of the gate device with an opening / closing door.

[0009] (First embodiment) A sales management system according to a first embodiment will be described below with reference to the drawings. FIG. 1 is a diagram illustrating an overview of the sales management system 1. The sales management system 1 is applied to a store that sells products, such as a supermarket. The sales management system 1 includes a store server 2, multiple accounting devices 3, multiple gate devices 4, and a mobile terminal 5 carried by a customer. The store server 2, accounting devices 3, and gate devices 4 are connected to each other via a network such as a local area network (LAN) so that they can communicate with each other. The mobile terminal 5 is also connected to the store server 2 and accounting devices 3 via a wireless LAN or the like so that they can communicate with each other. The sales management system 1 may also include a POS terminal where a store clerk performs operations related to product registration and payment, a self-service POS terminal where a customer performs operations related to product registration and payment, or a semi-self-service POS system where a store clerk performs operations related to product registration and a customer performs operations related to payment.

[0010] The store server 2 receives payment information related to payment methods and product information for the products for which the transaction has been processed from the checkout device 3. The store server 2 also receives sales information indicating the sales amount from the checkout device 3. The store server 2 centrally manages the received product information, payment information, sales information, etc., and performs sales management for a single store.

[0011] The store server 2 also acquires customer operation information from the mobile terminal 5 and manages the status of each customer from entry to exit. The customer status managed by the store server 2 includes, for example, entry to the store, execution and cancellation of product registration, payment, and information reading at the gate device. By managing such customer status, it is possible to predict whether a customer will leave the store fraudulently and manage the degree of fraud (the possibility of fraud) for each customer. In a system like this embodiment in which operations for product registration and payment are left to the customer, fraud is likely to occur, so it is useful for a store to manage the degree of fraud for each customer and take measures.

[0012] The checkout device 3 is a so-called self-service checkout device where the customer performs the checkout themselves. Based on transaction information received from the mobile terminal 5, the checkout device 3 executes checkout processing related to payments by cash payment or cashless payment such as credit card payment. Checkout processing is processing for the customer to pay for the products they purchase. In the case of cash payment, checkout processing includes, for example, displaying transaction information, calculating the amount of change, and dispensing the change, while in the case of credit card payment, it includes sending and receiving various information with the payment server of the payment agent. Transaction information is information necessary for the checkout device 3 to execute checkout processing, and includes product information such as the product name and price.

[0013] The gate device 4 is installed at the exit of the sales floor where the checkout device 3 is installed or at the exit of the store (hereinafter collectively referred to as the "sales floor exit"). Customers who enter the sales floor exit the store by passing through the gate device 4 installed at the sales floor exit. When the gate device 4 reads information indicating that the customer has completed payment (hereinafter also referred to as "payment completion information") or information indicating that the customer has stopped shopping and will not purchase any products (hereinafter also referred to as "passing information"), the gate device 4 allows the customer to exit normally. If a customer attempts to pass through without being able to confirm that payment has been completed or that the customer has stopped shopping, the gate device 4 executes error processing. Error processing may include, for example, an audio alert or a notification to a store clerk located in the checkout area. If the gate device 4 has an opening / closing door, the error processing may involve closing the opening / closing door. In this embodiment, the error processing is performed by an audio alert. This is because forcibly preventing the customer from passing through by closing the opening / closing door may cause discomfort to the customer.

[0014] The mobile terminal 5 is a mobile terminal owned by a customer. In this embodiment, the mobile terminal 5 is configured as a smartphone owned by the customer with a shopping application program installed. The mobile terminal 5 is an example of a registration device, and can register products by capturing an image of a code symbol, such as a barcode, attached to a product using a camera. The mobile terminal 5 can send transaction information, including registered product information, to the checkout device 3, allowing the customer to make payment at the checkout device 3. The mobile terminal 5 can also send transaction information and a terminal ID to the store server 2. The terminal ID is information that identifies the mobile terminal owned by the customer. The terminal ID is information that can indirectly identify the customer, and a customer ID previously registered by the store can be used instead of the terminal ID. The mobile terminal 5 can be placed on a placement section provided in the shopping cart SC.

[0015] 2 is a diagram showing an example of a sales floor set up in a store. The sales floor is made up of a product area A and a checkout area B.

[0016] Product area A is an area where customers can move around pushing shopping carts SC to select products to purchase. Product area A has two sales entrances I for customers to enter the sales floor. Also, within product area A, an entry code display unit AA and display shelves AB are installed.

[0017] An entry code display unit AA is installed on each side of each sales floor entrance I. The entry code display unit AA displays, for example, a two-dimensional code for entering the store (hereinafter also referred to as an "entry code"). When a customer entering the sales floor reads the entry code with a mobile terminal 5, an application program installed on the mobile terminal 5 is launched. This enables the mobile terminal 5 to connect to the store network and to send and receive information (data) with the store server 2 and the accounting device 3. A large number of display shelves AB are installed in the product area A. The display shelves AB display the various products sold by the store.

[0018] Checkout area B is an area where customers pay for the products they purchase. Checkout area B is located adjacent to product area A, and customers can move freely between product area A and checkout area B. Checkout area B has two sales floor exits O through which customers who have completed payment can exit the sales floor. Also installed within checkout area B are a checkout device 3, a gate device 4, and a soccer table BA.

[0019] As described above, the checkout device 3 is a self-service checkout device that customers operate themselves to make payments, and multiple checkout devices are installed on both sides and in the center of the checkout area B. The checkout tables BA are installed on both sides of the checkout area B. The checkout tables BA are work tables where items purchased by customers are bagged, etc. The gate devices 4 are installed near each sales floor exit O. The gate devices 4 are equipped with a reading gate 42 and a sensor gate 43.

[0020] The reading gate 42 is located closer to the product area A than the sensor gate 43. The reading gate 42 is equipped with a code reader 44 and a display unit 45 (see FIG. 6 ) that reads information from a barcode printed on a receipt issued by the checkout device 3, a barcode included in an electronic receipt displayed on the display unit of the mobile terminal 5 in a store that uses electronic receipts, or a two-dimensional code for exit (hereinafter also referred to as an "exit code") displayed on the display unit of the mobile terminal 5. The information read by the code reader 44 includes payment completion information indicated by the barcode on the receipt, passage information indicated by the exit code, etc. The display unit 45 displays various information.

[0021] The sensor gate 43 includes a passage sensor 46 that detects customers passing through, and an audio output unit 47 such as a speaker (see FIG. 9 for both). The passage sensor 46 is a sensor that detects customers who have moved from the reading gate 42 side to the sales floor exit O side, and various known sensors can be used. The audio output unit 47 notifies information to customers passing through the gate device 4, customers and store clerks present in the checkout area, etc. The passage sensor 46 may be provided separately from the sensor gate 43, but in this case, the gate device 4 is also configured to include the passage sensor 46.

[0022] Next, the operations of a customer from entering a sales floor to making a purchase and then leaving the sales floor will be described. Fig. 3 is a diagram showing an outline of the operations of a customer from entering a sales floor to leaving the sales floor.

[0023] When a customer enters the sales floor through the sales floor entrance I, they first read the store entry code displayed on the display unit AA with their mobile terminal 5, which has a shopping application program installed (3-1). The customer then moves around the product area A, for example, pushing a shopping cart SC, and uses their mobile terminal 5 to read the barcodes attached to the products they wish to purchase, thereby registering the products (3-2).

[0024] Once product registration for all products to be purchased is complete, the customer moves to checkout area B and transfers transaction information, including the product information registered through product registration, from their mobile terminal 5 to the checkout device 3 (3-3). The customer can transfer the transaction information from their mobile terminal 5 to the checkout device 3, for example, by reading a payment code for transferring transaction data from an image of a barcode displayed on the checkout device 3. The customer then makes payment at the checkout device 3 based on the transaction information. Payment can be made by cash, credit card, electronic money, or the like.

[0025] After completing payment, the customer takes the receipt issued by the checkout device 3 and heads toward the exit O of the sales floor. The receipt includes the name and price of the product purchased by the customer, as well as a barcode indicating that payment has been completed. In other words, the information indicated by the barcode is an example of information indicating that payment has been completed. The receipt may also be an electronic receipt viewable on a mobile terminal 5. The customer has the barcode printed on the receipt read by the reading gate 42 installed at the exit O of the sales floor, and passes through the gate device 4 to exit the sales floor (3-4). This allows the customer to exit the sales floor normally. If the customer attempts to pass through the gate device 4 without having the barcode read, or by having the barcode of a receipt related to a previous transaction read, the gate device 4 executes error processing. The error processing prompts the reading gate 42 to read information for normal exit, for example, by outputting a voice message such as, "Please hold up the barcode on your receipt."

[0026] Next, the store server 2, gate device 4, and mobile terminal 5 that make up the sales management system 1 will be described in detail.

[0027] First, the mobile terminal 5 will be described. Fig. 4 is a block diagram showing the hardware configuration of the mobile terminal 5. The mobile terminal 5 includes a control unit 50, a memory unit 51, a display unit 52, an operation unit 53, an imaging unit 54, and a communication unit 55. The control unit 50, the memory unit 51, the display unit 52, the operation unit 53, the imaging unit 54, and the communication unit 55 are connected to one another via a bus 56 or the like.

[0028] The control unit 50 is configured by a computer including a CPU (Central Processing Unit) 501, a ROM (Read Only Memory) 502, and a RAM (Random Access Memory) 503. The CPU 501, the ROM 502, and the RAM 503 are connected to each other via a bus 56.

[0029] The CPU 501 controls the overall operation of the mobile terminal 5. The ROM 502 stores various programs, such as a program used to drive the CPU 501, and various data. The RAM 503 includes a transaction information storage unit 504. The transaction information storage unit 504 is an area for storing transaction information, including product information acquired from the store server 2 based on an input product code for one transaction. The RAM 503 is also used as a work area for the CPU 501, and loads various programs and data stored in the ROM 502 and the memory unit 51. The control unit 50 executes various control processes for the mobile terminal 5 by the CPU 501 operating in accordance with the control programs stored in the ROM 502 and the memory unit 51 and loaded in the RAM 503.

[0030] The memory unit 51 is configured with a storage medium such as a hard disk drive (HDD) or flash memory, and maintains the stored contents even when the power is cut off. The memory unit 51 stores a control program 511.

[0031] The control program 511 is a shopping application program, etc. The shopping application program causes the mobile terminal 5 to function as a product registration device, and also causes the display unit 52 to display an exit code indicating passing information indicating that the customer has stopped shopping and will not purchase any products.

[0032] The display unit 52 is configured, for example, with a liquid crystal panel, and displays various information. For example, the display unit 52 displays product information of registered products, the total price of registered products, etc. The display unit 52 also displays various information such as an exit code indicating passing information and controls to be operated by the customer.

[0033] The operation unit 53 is configured, for example, by a touch panel provided on the surface of the display unit 52, and inputs information corresponding to the position touched by the user to the control unit 50. When the customer operates an operator displayed on the display unit 52, the operation unit 53 inputs information corresponding to the operator to the control unit 50.

[0034] The imaging unit 54 captures images of the entry code displayed on the entry code display unit AA, the barcode attached to the product, the barcode displayed on the checkout device 3, etc., and inputs the captured image data to the control unit 50. The control unit 50 reads the entry information from the image of the entry code displayed on the entry code display unit AA, reads the product code, which is product identification information that identifies the product, from the image of the barcode attached to the product, and reads the payment code for transferring transaction data from the image of the barcode displayed on the checkout device 3. If the mobile terminal 5 has a function for registering products using so-called object recognition, the imaging unit 54 captures an image of the product's appearance and inputs the image to the control unit 50.

[0035] The communication unit 55 is an interface for communicating with external devices such as the store server 2, the checkout device 3, and the gate device 4. By connecting the control unit 50 to the external devices via the communication unit 55, the control unit 50 can send and receive information (data) to and from the external devices.

[0036] Next, the functional configuration of the control unit 50 of the mobile terminal 5 will be described. Fig. 5 is a block diagram showing the main functional configuration of the control unit 50 of the mobile terminal 5. The control unit 50 functions as an input unit 5001, an acquisition unit 5002, a registration unit 5003, a reception unit 5004, and an output unit 5005 by the CPU 501 operating in accordance with a control program stored in the ROM 502 or memory unit 51. Note that each of these functions may be configured by hardware such as a dedicated circuit.

[0037] Various information is input to the input unit 5001 from the operation unit 53 and the imaging unit 54. For example, number information indicating the number of people in a group of customers who own mobile terminals 5, or cancellation information indicating that a customer will cancel their shopping without purchasing an item, is input to the input unit 5001 from the operation unit 53. In addition, the input unit 5001 receives, from the imaging unit 54, image data of an image of an entry code, image data of a barcode attached to an item, image data of a barcode displayed on the checkout device 3, and the like.

[0038] The input unit 5001 extracts a code symbol such as a barcode or two-dimensional code from the input image data and decodes the code symbol. If the code symbol indicates a product code, the input unit 5001 outputs the product code to the acquisition unit 5002. If the code symbol indicates a payment code, the input unit 5001 outputs the payment code to the output unit 5005.

[0039] The acquisition unit 5002 acquires product information from the store server 2 based on the product code input from the input unit 5001. In detail, the acquisition unit 5002 queries the store server 2 about the product code input from the input unit 5001, and the store server 2 acquires product information extracted from a product master (described later) based on the product code. Note that the product master may be stored in the memory unit 51, and the acquisition unit 5002 may acquire product information from the memory unit 51. The acquisition unit 5002 also acquires various information from the store server 2. For example, the acquisition unit 5002 acquires a status check result from the store server 2. The status check result will be described in detail in the second and third embodiments.

[0040] The registration unit 5003 executes product registration by registering the product information acquired by the acquisition unit 5002 in the transaction information storage unit 504. The product information may include a product code.

[0041] The reception unit 5004 receives cancellation information indicating that the customer will cancel the shopping without purchasing the product. Specifically, the reception unit 5004 receives cancellation information input by the customer from the operation unit 53 to the input unit 5001, that is, information indicating that the customer will cancel the shopping without purchasing the product.

[0042] When the reception unit 5004 receives the cancellation information, the output unit 5005 outputs passing information for passing through the gate device 4. Specifically, when the reception unit 5004 receives the cancellation information, the output unit 5005 outputs the passing information to the display unit 52. The passing information is information for displaying an exit code on the display unit 52. The output unit 5005 may also output the passing information to an external device such as the accounting device 3. In this case, the exit code is printed by a printer provided in the external device such as the accounting device 3.

[0043] Furthermore, output unit 5005 outputs various information to checkout device 3. For example, when a payment code is input from input unit 5001, or when a transaction information transfer instruction is input from operation unit 53 via input unit 5001, output unit 5005 transmits the transaction information stored in transaction information storage unit 504, the terminal ID, and the number of people information input to input unit 5001 to checkout device 3.

[0044] Furthermore, the output unit 5005 outputs various information to the store server 2. For example, the output unit 5005 outputs the terminal ID of the mobile terminal 5 and status information indicating the operation content of the mobile terminal 5 to the store server 2. The status information is registration information indicating that product registration has been executed on the mobile terminal 5, cancellation information indicating that product registration has been cancelled, etc.

[0045] Next, the gate device 4 will be described. Fig. 6 is a block diagram showing the hardware configuration of the gate device 4. The gate device 4 includes a control unit 40, a memory unit 41, a code reader 44, a display unit 45, a passage sensor 46, an audio output unit 47, and a communication unit 48. The code reader 44 and the display unit 45 are provided in the reading gate 42. The passage sensor 46 and the audio output unit 47 are provided in the sensor gate 43. The control unit 40, the memory unit 41, the code reader 44, the display unit 45, the passage sensor 46, the audio output unit 47, and the communication unit 48 are connected to one another via a bus 49, etc.

[0046] The control unit 40 is configured by a computer including a CPU 401, a ROM 402, and a RAM 403. The CPU 401, the ROM 402, and the RAM 403 are connected to one another via a bus 49.

[0047] The CPU 401 controls the overall operation of the gate device 4. The ROM 402 stores various programs, such as a program used to drive the CPU 401, and various data. The RAM 403 is used as a work area for the CPU 401, and loads various programs and data stored in the ROM 402 and the memory unit 41. The control unit 40 executes various control processes for the gate device 4 by the CPU 401 operating in accordance with the control programs stored in the ROM 402 and the memory unit 41 and loaded in the RAM 403.

[0048] The memory unit 41 is configured with a storage medium such as a HDD or flash memory, and maintains its stored contents even when the power is cut off. The memory unit 41 stores a control program 411.

[0049] The control program 411 includes a program for reading payment completion information, number of people information, and passage information from the code symbol, a program for detecting the number of people passing through the sensor gate 43 based on the sensor information of the passage sensor 46, and a program for executing error processing.

[0050] The code reader 44 reads information from the code symbol printed on the receipt issued by the accounting device 3 and the code symbol displayed on the display unit 52 of the mobile terminal 5. The code reader 44 decodes the recognized code symbol and reads payment completion information, number of people information, and passage information. Note that the code symbol recognized by the code reader 44 may be decoded by the control unit 40.

[0051] FIG. 8 shows an example of a receipt on which a barcode, which is a code symbol, is printed. The receipt has a transaction information area X and a barcode area Y. The transaction information area X prints the product name, price, subtotal (which is the total of the prices), tax, and total amount of the product purchased by the customer. The barcode area Y prints a barcode indicating information including payment completion information and number of people.

[0052] The barcode printed in the barcode area Y indicates transaction completion information such as a transaction number, number of people, and terminal ID.

[0053] Returning to Fig. 6, the hardware of the gate device 4 will be described. The display unit 45 is configured with, for example, a liquid crystal panel, and displays various information. For example, the display unit 45 displays a countdown of the number of people who can pass through the gate device 4 based on the number of people information read by the code reader 44 and the number of people detected by the passage sensor 46.

[0054] Passage sensor 46 detects people exiting the sales floor by passing through sensor gate 43. As passage sensor 46, a widely known sensor such as a sensor that optically detects people passing through sensor gate 43 can be used.

[0055] The audio output unit 47 is composed of a speaker or the like, and notifies information to customers passing through the gate device 4 and other customers in the checkout area B. For example, when the code reader 44 reads the number of people information, the audio output unit 47 notifies those around it of the number of people indicated by the number of people information as the number of people allowed to pass.

[0056] The communication unit 48 is an interface for communicating with external devices such as the store server 2, the checkout device 3, and the mobile terminal 5. By connecting to the external devices via the communication unit 48, the control unit 40 can send and receive information (data) with the external devices.

[0057] Next, the functional configuration of the control unit 40 of the gate device 4 will be described. Fig. 7 is a block diagram showing the main functional configuration of the control unit 40 of the gate device 4. The control unit 40 functions as an input unit 4001, a check unit 4002, a detection unit 4003, and a processing unit 4004 by the CPU 401 operating in accordance with a control program stored in the ROM 402 or memory unit 41. Note that each of these functions may be configured by hardware such as a dedicated circuit.

[0058] The input unit 4001 receives the passing information output by the output unit 5005 of the mobile terminal 5. Specifically, the passing information read by the code reader 44 from the store exit code displayed on the display unit 52 of the mobile terminal 5 is input to the input unit 4001 from the code reader 44. The number of people information and terminal ID included in the store exit code are also input to the input unit 4001. The input unit 4001 also receives the payment completion information, number of people information, terminal ID, etc. read by the code reader 44 from the barcode printed on the receipt.

[0059] The check unit 4002 checks whether the payment completion information entered into the input unit 4001 is correct. For example, the check unit 4002 checks the transaction completion information by inquiring of the store server 2 as to whether the transaction number entered into the input unit 4001 as the payment completion information relates to a transaction at the store. Furthermore, the check unit 4002 checks, based on the terminal ID entered into the input unit 4001 together with the passing information, whether the product is registered on the mobile terminal 5 identified by the terminal ID. In other words, the check unit 4002 checks whether the mobile terminal 5 displaying the store exit code indicating the passing information is a mobile terminal 5 on which the product is not registered, i.e., the mobile terminal 5 of a customer who will not purchase the product. For example, the check unit 4002 checks whether the product is registered on the mobile terminal 5 displaying the store exit code indicating the passing information by inquiring of the store server 2, which stores terminal IDs and operation statuses in association with each other. The gate device 4 does not necessarily need to include the check unit 4002; however, including the check unit 4002 can improve the effectiveness of preventing fraudulent store exits.

[0060] The detection unit 4003 detects the number of customers passing through the gate device 4. Specifically, the detection unit 4003 detects the number of people passing through the gate device 4 and leaving the sales floor, based on the output of the passage sensor 46.

[0061] When passing information is input to the input unit 4001, the processing unit 4004 allows the customer to pass through without performing error processing. Specifically, when passing information is input to the input unit 4001, the processing unit 4004 allows the customer to exit the sales floor normally without performing error processing such as issuing a notification urging the reader gate 42 to read information for normal exit. The processing unit 4004 also allows the customer to exit normally when payment completion information is input to the input unit 4001. If a customer attempts to pass through the sensor gate 43 without inputting either passing information or payment completion information to the input unit 4001, the processing unit 4004 notifies the customer by outputting a message from the display unit 45 or the audio output unit 47 urging the customer to read information for normal exit. This notification is an example of error processing.

[0062] Furthermore, processing unit 4004 outputs the number of people indicated by the number of people information input to input unit 4001 as the number of people allowed to pass for the payment completion information or passing information input to input unit 4001 from display unit 45 and audio output unit 47. Furthermore, processing unit 4004 executes the same error processing as above when the number of people passing detected by detection unit 4003 as the number of people passing for the payment completion information or passing information exceeds the number indicated by the number of people information.

[0063] Next, the store server 2 will be described. Fig. 9 is a block diagram showing the hardware configuration of the store server 2. The store server 2 includes a control unit 20, a memory unit 21, a display unit 22, an operation unit 23, and a communication unit 24. The control unit 20, the memory unit 21, the display unit 22, the operation unit 23, and the communication unit 24 are connected to one another via a bus 25 or the like.

[0064] The control unit 20 is configured by a computer including a CPU 201, a ROM 202, and a RAM 203. The CPU 201, the ROM 202, and the RAM 203 are connected to one another via a bus 25.

[0065] The CPU 201 controls the overall operation of the store server 2. The ROM 202 stores various programs, such as programs used to drive the CPU 201, and various data. The RAM 203 is used as a work area for the CPU 201, and loads various programs and data stored in the ROM 202 and the memory unit 21. The control unit 20 executes various control processes for the store server 2 by the CPU 201 operating in accordance with the control programs stored in the ROM 202 and the memory unit 21 and loaded in the RAM 203.

[0066] The memory unit 21 is configured with a storage medium such as a HDD or flash memory, and maintains its stored contents even when the power is turned off. The memory unit 21 stores a control program 411, a product master 212, a status management file 213, a process master 214, and a customer fraud degree management file 215.

[0067] The control program 211 is a program for managing the status of a customer, a program for managing the degree of fraud of the customer based on the customer's status, and the like.

[0068] The product master 212 is a master file that stores information about products handled by the store. The product master 212 associates product codes that identify products with product information such as product names and prices. Because the products handled by the store change daily, the product master 212 is updated as appropriate by the store.

[0069] The status management file 213 is a file that manages the status of customers who enter the sales floor. The status management file 213 is updated each time the store server 2 acquires status information indicating the customer's operations from the mobile terminal 5, the checkout device 3, and the gate device 4. FIG. 10 is a diagram showing the data structure of the status management file 213. The status management file 213 associates information indicating the terminal ID, entry, registration, payment, and gate reading within the time limit. The status management file 213 may also associate other information in addition to the above information. For example, the status management file 213 may associate a shopping cancellation flag, which records whether the customer has canceled their purchase, with the above information.

[0070] The terminal ID field stores a terminal ID that identifies the mobile terminal 5 owned by the customer. When the customer reads the store entry code displayed on the store entry code display area AA with the mobile terminal 5, the mobile terminal 5 transmits the terminal ID to the store server 2. The store server 2 registers the received terminal ID. The terminal ID may be registered in advance based on information from the customer.

[0071] The store entry item is registered with information indicating whether or not the customer has entered the store. "Completed" is registered in the store entry item when the terminal ID is registered. If the terminal ID is registered in advance, "Completed" is registered in the store entry item when the customer enters the sales floor and the store server 2 receives the terminal ID from the mobile terminal 5.

[0072] The registration item registers information indicating whether a valid product registration has been made on the mobile terminal 5. A valid product registration is a product registration that has not been canceled. When a valid product registration has been made on the mobile terminal 5, in other words, when product information has been registered in the transaction information storage unit 504 of the mobile terminal 5, "Completed" is registered in the registration item. For example, when a customer registers one product, the mobile terminal 5 transmits registration information indicating that the product registration has been made to the store server 2. The store server 2 registers "Completed" in the registration item based on the received registration information. Furthermore, when the customer cancels the product registration, the mobile terminal 5 transmits cancellation information indicating that the product registration has been canceled to the store server 2. The store server 2 rewrites the registration item from "Completed" to "Not yet" based on the received cancellation information. Note that the store server 2 can determine whether all product registrations made on the mobile terminal 5 have been canceled by acquiring the product codes of the products that are the subject of the registration information and cancellation information from the mobile terminal 5. Even if the store server 2 receives cancellation information, it does not rewrite the registration item from "Done" to "Not yet" if all product registrations executed on the mobile terminal 5 have not been canceled. The status management file 213 is an example of a product registration information storage unit that stores product registration information indicating whether or not a product has been registered based on a customer's operation.

[0073] The payment item contains information indicating whether payment has been made for the transaction information stored in the transaction information storage unit 504 of the mobile terminal 5. When the mobile terminal 5 transfers the transaction information stored in the transaction information storage unit 504 and the terminal ID to the checkout device 3, it sends payment processing information indicating that payment has been made along with the terminal ID to the store server 2. The store server 2 registers "Completed" in the payment item based on the received payment processing information. The payment processing information received by the store server 2 may also be sent from the checkout device 3 when the checkout process is completed at that device.

[0074] The "Gate reading within time" field contains information indicating whether the gate device 4 successfully read the payment completion information or the passing information within a specified time after the customer entered the sales floor. The specified time is the maximum time a customer is expected to stay in the sales floor and is set by the store. When the gate device 4 reads the terminal ID and payment completion information from the barcode on the receipt, or the terminal ID and passing information from the mobile terminal 5, the gate device 4 sends the terminal ID and reading processing information indicating that the reading was successful to the store server 2. The store server 2 registers "Completed" in the "Gate reading within time" field based on the received reading processing information.

[0075] The information registered in each of the above-mentioned items of store entry, registration, payment, and gate reading within the hours can be said to be status information indicating the status of the customer in the sales area.

[0076] The process master 214 is a master file that defines the process content for updating the customer fraud degree management file according to the customer's status pattern. Fig. 11 is a diagram showing the data structure of the process master 214. The process master 214 associates information indicating the pattern number, store entry, registration, payment, gate reading within hours, status, and process.

[0077] In the item "Pattern No.", a number specifying the status pattern of a customer in a sales area is registered.

[0078] The information registered in each of the items indicating the status pattern, such as store entry, registration, payment, and gate reading within hours, is as described above, so a duplicated explanation will be omitted.

[0079] The status field contains information indicating the customer's status assumed for the corresponding status pattern. In pattern No. 1, store entry, registration, payment, and time-limited gate reading are all "completed," and it is assumed that the customer registered their product after entering the store, made payment, had the payment completion information read by gate device 4, and then left the sales floor, so this is set to "normal." In pattern No. 2, it is assumed that payment was completed but the customer did not exit the gate device 4 correctly (for example, exited through sales floor entrance I), so this is set to "operation error."

[0080] In pattern No. 3, it is assumed that the customer did not pay for the registered product and did not exit through the gate device 4 properly, so "unauthorized exit" is set.

[0081] In pattern No. 4, it is assumed that the customer entered the sales floor but did not register any products, or after canceling all product registrations, had the gate device 4 read the passing information and then left the sales floor, so "shopping canceled" is set. In pattern No. 5, it is assumed that the customer entered the sales floor but did not register any products, or after canceling all product registrations, did not exit the sales floor correctly through the gate device 4, so "operation error" is set.

[0082] The processing item stores information indicating the content of updates to the customer fraud degree management file 215 according to the corresponding status pattern. In pattern No. 1 and pattern No. 4, the customer is not found to have engaged in fraudulent activity and is recognized to have performed the correct operation. In this case, the "number of times entering the store" in the customer fraud degree management file 215 is incremented and updated. In pattern No. 2 and pattern No. 5, the customer is not found to have engaged in fraudulent activity, but the customer's operation or behavior is recognized to be inconsistent with the operation of the sales management system 1. In this case, the "number of operation errors" in the customer fraud degree management file 215 is incremented and updated. In pattern No. 3, the customer is suspected of engaging in fraudulent activity. In this case, the "number of times requiring caution" in the customer fraud degree management file 215 is incremented and updated.

[0083] The customer fraud degree management file 215 is a file that manages the degree of fraud of a customer, in other words, the possibility of fraud, according to the customer's status pattern. The customer fraud degree management file 215 is updated every time a customer visits the store. FIG. 12 is a diagram showing the data structure of the customer fraud degree management file 215. The customer fraud degree management file 215 associates information indicating the terminal ID, the number of times the customer has entered the store, the number of times an operation error has occurred, and the number of times caution is required.

[0084] The terminal ID field stores the terminal ID that identifies the mobile terminal 5 owned by the customer. The number of store visits field stores information indicating the number of store visits where no fraudulent activity was suspected and where correct operations were performed. The number of operation errors field stores information indicating the number of purchases where no fraudulent activity was detected but where correct operations or actions were not performed. The number of times requiring caution field stores information indicating the number of purchases where fraudulent activity was suspected.

[0085] By managing the degree of fraudulence of customers using the customer fraud degree management file 215, a store can take various measures against customer fraud. For example, if the number of caution counts for a specific terminal ID exceeds a certain value, the store can instruct store staff to strengthen fraud monitoring when a customer who owns a mobile terminal 5 identified by that terminal ID visits the store. Also, if the number of caution counts for a specific terminal ID exceeds a set number that is equal to or greater than the certain number, the store can take measures such as refusing to allow a customer who owns a mobile terminal 5 identified by that terminal ID to make a purchase.

[0086] A system that leaves product registration and payment operations to the customer, in other words, a system in which customers shop without the intervention of a store clerk, presupposes trust in the customer, but it is also true that customer fraud is likely to occur. Unnecessarily strengthening monitoring of customer fraud by installing multiple security cameras and deploying multiple security guards, for example, can cause customers to feel uncomfortable and lead to a decrease in customer numbers. By managing the degree of customer fraud based on customer status in this embodiment, it is possible to take measures against customer fraud while minimizing customer discomfort.

[0087] Returning to Figure 9, the hardware configuration of the store server 2 will now be described. The display unit 22 is configured, for example, as an LCD panel, and displays various information. The operation unit 23 is configured, for example, as a keyboard or touch panel, and is operated by a store clerk. The communication unit 24 is an interface for communicating with external devices such as the checkout device 3, gate device 4, and mobile terminal 5. By connecting to the external devices via the communication unit 24, the control unit 20 can send and receive information (data) with the external devices.

[0088] Next, the functional configuration of the control unit 20 of the store server 2 will be described. Fig. 13 is a block diagram showing the main functional configuration of the control unit 20 of the store server 2. The control unit 20 functions as an input unit 2001, a status management unit 2002, and an output unit 2003 by the CPU 201 operating in accordance with a control program stored in the ROM 202 or memory unit 21. Note that each of these functions may be configured using hardware such as a dedicated circuit.

[0089] The input unit 2001 receives various types of information from the checkout device 3, gate device 4, and mobile terminal 5. For example, the input unit 2001 receives product information for the product for which the checkout process has been completed, payment information related to the payment method, and the like from the checkout device 3. When the gate device 4 reads payment completion information or passage information, the input unit 2001 receives the terminal ID and reading processing information indicating that the reading was successful from the gate device 4. The input unit 2001 also receives the terminal ID and status information indicating the customer's operation from the mobile terminal 5. The status information includes registration information indicating that a product registration operation has been performed on the mobile terminal 5, cancellation information indicating that the product registration has been canceled, and payment processing information indicating that transaction information has been sent to the checkout device 3.

[0090] The status management unit 2002 manages the status in the sales floor for each mobile terminal 5, in other words, for each customer. For example, the status management unit 2002 updates the status management file 213 based on the status information input to the input unit 2001. The status management unit 2002 also updates the customer fraud degree management file 215 based on the information registered in the status management file 213.

[0091] The output unit 2003 outputs various information to the gate device 4, the portable terminal 5, etc. For example, the output unit 2003 outputs the status check result to the gate device 4 or the portable terminal 5. The status check result will be described in detail in the second and third embodiments.

[0092] Next, a description will be given of the processing executed by the mobile terminal 5 in this embodiment. Fig. 14 is a flowchart showing the flow of processing by the control unit 50 of the mobile terminal 5 in this embodiment.

[0093] First, when a customer captures an image of the entry code on the entry code display section AA with the mobile terminal 5, the input section 5001 reads entry information indicating that the customer has entered the store based on the input image data (S1). Once the entry information has been read, the control section 50 starts a shopping application program (S2). Next, the output section 5005 transmits the terminal ID and the entry information to the store server 2 (S3).

[0094] Thereafter, the control unit 50 determines whether a product barcode indicating a product code has been input to the input unit 5001 (S4). When a product barcode has been input (Y in S4), the acquisition unit 5002 acquires product information from the store server 2 based on the product code read by the input unit 5001 (S5). In detail, the acquisition unit 5002 transmits the product code and a request for product information corresponding to the product code to the store server 2, and receives the product information from the store server 2.

[0095] Next, the registration unit 5003 executes product registration by registering (storing) the product information acquired by the acquisition unit 5002 in the transaction information storage unit 504 (S6). The output unit 5005 transmits the terminal ID and registration information to the store server 2 (S7). The control unit 50 then determines whether information indicating the end of product registration has been entered into the input unit 5001 (S8). If information indicating the end of product registration has been entered (Y in S8), the control unit 50 determines whether customer count information indicating the number of customers has been entered into the input unit 5001 (S9). If no customer count information has been entered (N in S9), the control unit 50 returns to the processing of S9 and waits. If customer count information has been entered (Y in S9), the control unit 50 determines whether a checkout instruction has been entered into the input unit 5001 (S10). If no checkout instruction has been entered (N in S10), the control unit 50 returns to the processing of S10 and waits.

[0096] When a payment instruction is input (Y in S10), the output unit 5005 outputs the terminal ID, the transaction information stored in the transaction information storage unit 504, and the number of people information input to the input unit 5001 to the checkout device 3 (S11), and then sends the terminal ID and payment processing information indicating that the payment has been completed to the store server 2 (S12). At this time, the transaction information stored in the transaction information storage unit 504 is cleared. The control unit 50 then terminates processing. When the customer completes payment at the checkout device 3, the checkout device 3 issues a receipt with a code symbol printed on it indicating that the payment has been completed. The customer can exit the sales floor normally by having the gate device 4 read the code symbol printed on the receipt. Note that when the customer completes payment at the checkout device 3, a code symbol indicating that the payment has been completed may be displayed on the mobile terminal 5 based on the output from the checkout device 3. The code symbol may be displayed as part of an electronic receipt or separately from the transaction information.

[0097] If a product barcode is not input in the process of S4 (N in S4), the control unit 50 determines whether the reception unit 5004 has received cancellation information indicating that the purchase has been canceled (S13). If not (N in S13), the control unit 50 returns to the process of S4. If cancellation information is received (Y in S13), the control unit 50 determines whether transaction information is stored in the transaction information storage unit 504 (S14). If transaction information is stored (Y in S14), the control unit 50 clears the transaction information stored in the transaction information storage unit 504 (S15) and determines whether information on the number of people has been entered into the input unit 5001 (S16). As a result, when the reception unit 5004 receives cancellation information, the information registered for the product at that time is cleared. Note that if transaction information is not stored in the process of S14 (N in S14), the control unit 50 skips the process of S15 and proceeds to the process of S16.

[0098] If the number of people information is not input (N in S16), the control unit 50 returns to the process of S16 and waits. If the number of people information is input (Y in S16), the control unit 50 displays an exit code on the display unit 52 (S17) and ends the process. In this embodiment, when the reception unit 5004 receives the cancellation information, the control unit 50 clears the transaction information stored in the transaction information storage unit 504 at that time, but the exit code may be displayed without clearing the transaction information.

[0099] Furthermore, if the product registration is not completed in the process of S8 (N in S8), the control unit 50 determines whether information to cancel the already executed product registration has been input to the input unit 5001 (S18). If no information has been input (N in S18), the control unit 50 returns to the process of S4. If information to cancel the product registration has been input (Y in S18), the registration unit 5003 cancels the product registration of the product specified by the input information (S19). Next, the output unit 5005 transmits the terminal ID and the cancellation information to the store server 2 (S20). At this time, the output unit 5005 also transmits the product code of the product whose registration is to be canceled to the store server 2. Then, the control unit 50 proceeds to the process of S4.

[0100] Through the above process, the mobile terminal 5 functions as a product registration device, and if a customer abandons shopping without purchasing a product, it displays an exit code for normal exit through the gate device 4. The mobile terminal 5 also transmits status information such as registration information, cancellation information, and payment processing information to the store server 2.

[0101] Next, a description will be given of the processing executed by the gate device 4. Fig. 15 is a flowchart showing the flow of processing by the control unit 40 of the gate device 4.

[0102] The control unit 40 determines whether code information has been input to the input unit 4001 (S31), and if not (N in S31), returns to the processing of S31 and waits. When code information has been input to the input unit 4001 (Y in S31), the check unit 4002 checks whether the input code information is store-exit OK information that allows the customer to exit normally (S32). Specifically, it determines whether the code information input to the input unit 4001 is payment completion information or passing information.

[0103] If the code information input to the input unit 4001 indicates that it is OK to leave the store (Y in S32), the processing unit 4004 causes the audio output unit 47 to output audio guiding people through the gate device 4 (S33). Next, the detection unit 4003 starts counting up the number of people passing through the sensor gate 43 (S34). The processing unit 4004 controls the display unit 45 to display a countdown of the number of people who can pass based on the number of people information input to the input unit 4001 and the number of people passing detected by the detection unit 4003 (S35).

[0104] Next, the control unit 40 determines whether or not the customer who has had the code reader 44 read the payment completion information or the passage information is within the permitted passage time, in other words, whether or not a predetermined time has passed since the passage guidance was output by voice in the processing of S33 (S36). If the customer is within the permitted passage time (Y in S36), the control unit 40 determines whether or not the number of people detected by the detection unit 4003 exceeds the permitted passage number (S37).

[0105] If the number of people detected by the detection unit 4003 exceeds the allowable number of people to pass (Y in S37), the processing unit 4004 outputs error information to the audio output unit 47 (S38). This causes the audio output unit 47 to output an error message such as "Please hold the barcode over the code reader." Next, the detection unit 3003 stops counting up the number of people detected (S39). Then, the control unit 40 transmits the payment completion information or passage information, the terminal ID read by the code reader 44, and reading processing information indicating that reading was successful to the store server 2 (S40), and ends the processing.

[0106] In the process of S32, if the code information input to the input unit 4001 does not include payment completion information or passing information (N in S32), the processing unit 4004 controls the display unit 45 to display an error message (S41). The error message may, for example, say, "Please hold the barcode on the receipt issued upon payment over the code reader." Then, the control unit 40 ends the process.

[0107] Furthermore, in the process of S36, if it is not within the passable time (N in S36), the control unit 40 skips the process of S37 and proceeds to the process of S38. In the process of S37, if the number of people detected by the detection unit 4003 does not exceed the passable number of people (N in S37), the control unit 40 determines whether the number of people detected by the detection unit 4003 is the same as the passable number of people (S42). If the detected number of people and the passable number of people are the same (Y in S42), the control unit 40 proceeds to the process of S39, and if the detected number of people and the passable number of people are not the same (N in S42), the control unit 40 returns to the process of S35.

[0108] Through the above process, gate device 4 allows customers who have completed payment to pass through gate device 4 and exit the sales floor normally, and executes error processing to prevent customers who have not completed payment from exiting the sales floor improperly if they attempt to pass through gate device 4. Gate device 4 also allows customers who cancel their shopping and do not purchase any products to pass through gate device 4 and exit the sales floor normally.

[0109] According to the sales management system 1 of the first embodiment, it is possible to effectively prevent customers who enter the sales floor from leaving the store fraudulently, and also to allow customers who do not purchase any products to leave normally. Therefore, the sales management system 1 of the first embodiment has the advantage of being able to ensure convenience for customers while preventing fraudulent behavior by customers.

[0110] (Second embodiment) Next, a second embodiment will be described. The second embodiment differs from the first embodiment in that, when the mobile terminal 5 displays the store exit code, it checks whether no product registrations have been made on the mobile terminal 5 or whether all product registrations have been cancelled, based on the customer's operation status managed by the store server 2. Hereinafter, explanations of configurations and functions similar to those of the first embodiment may be omitted. This is to avoid unnecessary redundancy in the following explanation and to make it easier for those skilled in the art to understand.

[0111] The operation of the sales management system 1 of the second embodiment will be described below. Fig. 16 is a sequence chart showing the flow of operations when a customer who has registered a product on the mobile terminal 5, then cancelled the product registration and displayed an exit code on the mobile terminal 5, passes through the gate device 4 and exits the sales floor normally.

[0112] First, a customer enters the store, and the mobile terminal 5 reads the store entry information from the store entry code displayed on the store entry code display area AA (S51). The mobile terminal 5 starts a shopping application program (S52) and transmits the terminal ID and store entry information to the store server 2 (S53). The store server 2 starts status management based on the received terminal ID and store entry information (S54). Specifically, the store server 2 registers the received terminal ID in the status management file 213, and also registers "Completed" in the store entry item.

[0113] Next, when the mobile terminal 5 reads the product code (S55), it transmits the terminal ID, registration information indicating that the product has been registered, and the read product code to the store server 2 (S56). The store server 2 registers "Completed" in the registration item corresponding to the received terminal ID in the status management file 213, and updates the status management file 213 (S57). The store server 2 also references the product master 212 to extract product information corresponding to the received product code (S58), and transmits the extracted product information to the mobile terminal 5 (S59).

[0114] The mobile terminal 5 executes product registration based on the received product information (S60). If the customer cancels the purchase of a registered product for some reason, information indicating cancellation of the product registration is input to the mobile terminal 5 (S61). The mobile terminal 5 transmits the terminal ID, cancellation information, and the product code of the product whose registration is to be canceled to the store server 2 (S62). The store server 2 updates the status management file 213 by rewriting the registration item corresponding to the received terminal ID from "Completed" to "Not yet" as necessary (S63).

[0115] After that, when cancellation information indicating the customer's purchase is cancelled is input to the mobile terminal 5 (S64), the mobile terminal 5 transmits the terminal ID and a status check request to the store server 2 (S65). The status check request, when the cancellation information is input to the mobile terminal 5, requests the store server 2 to check whether any product registrations were performed on the mobile terminal 5 after the customer entered the sales floor or whether all product registrations performed have been cancelled. By receiving the check results, the mobile terminal 5 prevents the display of an exit code when the customer has not cancelled the product registrations and returned the products. This further reduces fraudulent behavior by customers. The check for the absence of registered products may be performed by checking whether product information is stored in the transaction information storage unit 504. In this case, the transaction information storage unit 504 can be considered an example of a product registration information storage unit that stores product registration information indicating the presence or absence of registered products based on customer operations.

[0116] The store server 2 performs a status check (S66) and sends the check result to the mobile terminal 5 (S67). If a shopping cancellation flag that records whether or not the above-mentioned shopping cancellation operation has been performed is set in the status management file 213, the store server 2 may perform a status check based on the registration information of the shopping cancellation flag. In this case, if a shopping cancellation input is made to the mobile terminal 5, the customer can exit normally. If the check result indicates that there are no registered products, the mobile terminal 5 displays an exit code (S6). In other words, when the mobile terminal 5 receives the cancellation information, it displays the exit code on the condition that there are no registered products.

[0117] When the store exit code is displayed on the mobile terminal 5, the customer has the gate device 4 read the store exit code (S69). The gate device 4 that has read the store exit code outputs a voice message to guide the customer through the store (S70) and transmits the terminal ID and store exit information to the store server 2 (S71). The store server 2 updates the status management file 213 by registering "Done" in the "Gate Passage Within Time Read" field that corresponds to the received terminal ID in the status management file 213, and also updates the customer misconduct level management file 215 by adding the number of store entries that corresponds to the terminal ID in the customer misconduct level management file 215 (S72). Next, the store server 2 clears each status information item that corresponds to the received terminal ID in the status management file 213 (S73).

[0118] Next, the processing executed by the mobile terminal 5 in this embodiment will be described. Fig. 17 is a flowchart showing the flow of processing by the control unit 50 of the mobile terminal 5 in this embodiment. Note that since many of the processes are the same as those in the first embodiment, the same reference numerals as in Fig. 14 are used for the processes that are the same as those in the first embodiment, and the description thereof may be omitted.

[0119] When the reception unit 5004 receives the cancellation information (Y in S13), the output unit 5005 transmits the terminal ID and a status check request to the store server 2 (S81). Then, the acquisition unit 5002 acquires the check result from the store server 2 as a response to the status check request (S82).

[0120] The control unit 50 determines whether the check result indicates that it is OK to leave the store (S83). In other words, the control unit 50 determines whether the check result indicates that there are no products registered in the mobile terminal 5. If the check result indicates that it is OK to leave the store (Y in S83), the control unit 50 proceeds to the process of S16. If the check result does not indicate that it is OK to leave the store (N in S83), the control unit 50 determines whether information indicating cancellation of transaction information has been input, in other words, whether the customer has input an instruction to cancel the shopping and delete the product information registered up to that point (S84). If information indicating cancellation of transaction information has been input (Y in S84), the control unit 50 clears the transaction information stored in the transaction information storage unit 504 (S85) and proceeds to the process of S16. This allows the transaction information stored in the transaction information storage unit 504 to be cleared all at once if the customer who cancels the shopping forgets to cancel the product information they registered. In addition, in the process of S83, if it is not OK to leave the store (N in S83, it may proceed to the process of S18. If information indicating cancellation of transaction information is not input (N in S84), the control unit 50 returns to the process of S4.

[0121] Through the above processing, when the receiving unit 5004 receives cancellation information, the output unit 5005 refers to the product registration information storage unit (status management file 213) and outputs passing information on the condition that there are no registered products.

[0122] According to the sales management system 1 of the second embodiment, the mobile terminal 5 performs a status check when displaying the store exit code, and displays the exit code only if there are no registered products. Therefore, in addition to the advantages of the sales management system 1 of the first embodiment, it has the advantage of being able to further prevent customers from fraudulently leaving the store.

[0123] (Third embodiment) Next, a third embodiment will be described. The third embodiment differs from the first and second embodiments in that, when the gate device 4 reads the store exit code displayed on the mobile terminal 5, it checks whether there are no product registrations on the mobile terminal 5 or whether all product registrations have been canceled. Hereinafter, explanations of configurations and functions similar to those of the first or second embodiment may be omitted. This is to avoid unnecessary redundancy in the following explanation and to make it easier for those skilled in the art to understand.

[0124] The operation of the sales management system 1 of the third embodiment will be described. Fig. 18 is a sequence chart showing the flow of operations when a customer who has registered a product on the mobile terminal 5, then cancelled the product registration and displayed an exit code on the mobile terminal 5, passes through the gate device 4 and exits the sales floor normally. Note that many of the processes are the same as those in the second embodiment, and therefore processes similar to those in the second embodiment are given the same reference numerals as in Fig. 16, and descriptions thereof may be omitted.

[0125] When cancellation information indicating that the shopping is to be cancelled is input (S64), the mobile terminal 5 displays a store exit code without performing a status check (S68). Then, when the gate device 4 reads the store exit code displayed on the mobile terminal 5 (S69), it transmits the terminal ID and a status check request to the store server 2 (S91).

[0126] The store server 2 performs a status check (S66) and updates the status (S72). That is, the store server 2 updates the status management file 213 by registering "Done" in the item for "Gate Passage Read Within Time" that corresponds to the received terminal ID in the status management file 213. The store server 2 also updates the customer fraud degree management file 215 by adding the number of store entries that corresponds to the terminal ID in the customer fraud degree management file 215. Next, the store server 2 clears each piece of status information that corresponds to the received terminal ID in the status management file 213 (S73) and transmits the check results to the gate device 4 (S92).

[0127] If the check result indicates that there is no registered product, the gate device 4 outputs a voice message to guide the customer through the gate (S70).

[0128] In addition to the status check, the store server 2 may also confirm that there are no products in the shopping cart SC of the customer who has stopped shopping, using the following method.

[0129] For example, a sensor and a control unit are provided to detect whether the shopping cart SC contains any products. The sensor may be a camera that captures an image of the storage compartment of the shopping cart SC or a weight sensor that detects the weight of the products stored in the storage compartment. The sensor and control unit are connected to the store server 2 via a wireless LAN or the like so as to be able to communicate with each other.

[0130] 18, when the store server 2 receives a status check request, it acquires sensor information from the sensor of the shopping cart SC. If the acquired sensor information is predetermined information and the status check shows that no products have been registered on the mobile terminal 5, the store server 2 outputs information indicating that it is OK to leave the store to the gate device 4 in the process of S92. The predetermined information is information indicating that no products are stored in the storage compartment of the shopping cart SC.

[0131] By adopting such a configuration, it is possible to more reliably prevent fraudulent behavior by customers. In the above-described embodiment, when a product registration is cancelled, the registered product is considered to have been returned from the shopping cart SC to the sales floor, and normal exit is permitted. In addition, normal exit is permitted only after confirmation that the product has actually been returned.

[0132] Next, the processing executed by the gate device 4 in this embodiment will be described. Fig. 19 is a flowchart showing the flow of processing by the control unit 40 of the gate device 4 in this embodiment. Note that since many of the processes are the same as those in the first embodiment, the same reference numerals as in Fig. 15 are used for processes that are the same as those in the first embodiment, and descriptions thereof may be omitted.

[0133] When code information is input to the input unit 4001 (Y in S31), the control unit 40 determines whether the input code information is a store exit code (S101). If it is a store exit code (Y in S101), the processing unit 4004 transmits the terminal ID included in the store exit code and a status check request to the store server 2.

[0134] The control unit 40 acquires the check result from the store server 2 in response to the status check request (S103), and proceeds to the processing of S32. The processing from S32 onwards is the same as in the first embodiment. Note that in the processing of S101, if the code information input to the input unit 4001 is not a store exit code (N in S101), for example, if it is a barcode indicating payment completion information, the control unit 40 skips the processing of S102 and S103 and proceeds to the processing of S32.

[0135] As a result of the above processing, when an exit code is entered into the input unit 4001, the processing unit 404 refers to the status management file 213, which is the registration information storage unit, and allows the customer to pass through without performing error processing, provided that there are no registered products.

[0136] According to the sales management system 1 of the third embodiment, when an exit code is entered into the gate device 4, a status check is performed, and the gate device 4 allows the customer to pass through without executing error processing on the condition that there are no registered products. Therefore, as with the second embodiment, in addition to the advantages of the sales management system 1 of the first embodiment, it has the advantage of being able to further prevent customers from fraudulently leaving the store.

[0137] As described above, the sales management system of the above embodiment is a sales system comprising a registration device that registers products based on the operations of a customer who purchases the products, and a gate device that executes error processing if information indicating that payment for the product registered in the registration device has been completed is not input when a customer passes through.The registration device comprises a reception unit that receives cancellation information indicating that the customer will stop shopping without purchasing the product, and an output unit that outputs passing information for passing through the gate device when the reception unit receives the cancellation information.The gate device comprises an input unit that receives the passing information output by the output unit, and a processing unit that allows the customer to pass through without executing error processing when the passing information is input to the input unit.

[0138] This allows customers who enter the sales floor but abandon their shopping without purchasing any products to pass through the gate device 4 and exit the sales floor normally. Therefore, the sales management system of the above embodiment has the advantage of being able to ensure customer convenience while preventing fraudulent behavior by customers.

[0139] In addition, the sales management system of the above embodiment further includes a product registration information storage unit that stores product registration information indicating whether or not a product has been registered based on customer operation, and when the reception unit receives cancellation information, the output unit of the registration device refers to the product registration information storage unit and outputs passing information on the condition that there is no product registered.

[0140] This prevents the mobile terminal 5 from outputting the passage information when the product registration is not canceled and the product is not returned. Therefore, the sales management system of the above embodiment can further prevent fraudulent behavior by customers.

[0141] Furthermore, the sales management system of the above embodiment further includes a product registration information storage unit that stores product registration information indicating whether or not a product has been registered based on the customer's operation, and when passage information is input into the input unit, the processing unit of the gate device refers to the product registration information storage unit and, on the condition that there is no product registered, allows the customer to pass through without performing error processing.

[0142] As a result, the gate device 4 executes error processing when a customer attempts to leave the sales floor without canceling the product registration and returning the product. Therefore, the sales management system of the above embodiment can further prevent fraudulent behavior by customers.

[0143] Moreover, the product registration information storage unit of the sales management system of the above embodiment is a status management file that manages the customer status based on the operation of the registration device.

[0144] This allows the status management file stored for managing customer status to be utilized as a configuration for checking whether there are any registered products after cancellation information is input to the registration device, thereby simplifying the configuration for checking whether there are any registered products after cancellation information is input to the registration device.

[0145] In addition, the registration device of the sales management system of the above embodiment is a portable terminal carried by the customer, and the output unit displays a code symbol indicating the passing information on the display unit of the portable terminal.

[0146] This allows product registration and display of the code symbol indicating the passing information to be completed on the mobile terminal, and does not require the customer to print out the code symbol indicating the passing information at an accounting device, etc. This prevents a decrease in customer convenience.

[0147] In each of the above embodiments, the control programs executed by the store server 2, checkout device 3, gate device 4, and mobile terminal 5 may be provided by being recorded on a computer-readable recording medium such as a CD-ROM. Also, the control programs executed by the store server 2, checkout device 3, gate device 4, and mobile terminal 5 in each of the above embodiments may be stored on a computer connected to a network such as the Internet and provided by being downloaded via the network, or may be provided via a network such as the Internet.

[0148] Although the embodiment of the present invention has been described above, this embodiment is presented as an example and is not intended to limit the scope of the invention. This embodiment can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention.

[0149] For example, in each of the above embodiments, product information stored upon product registration is stored in the transaction information unit 504 of the mobile terminal 5, but it may also be stored in the store server 2. Specifically, when the mobile terminal 5 reads a product code, it transmits the product code and the terminal ID to the store server 2. The store server 2 reads product information corresponding to the received product code from the product master 212 and stores the read product information in association with the terminal ID. Furthermore, when the store server 2 receives information indicating registration cancellation, the terminal ID, and the product code from the mobile terminal 5, it clears the corresponding product information. In other words, the store server 2 may manage product information for each terminal ID of a product whose product code has been read by the mobile terminal 5. Even in this case, product information is registered based on the operation of the mobile terminal 5, so the mobile terminal 5 can be said to be a registration device.

[0150] Furthermore, when information indicating a shopping cancellation is input to the mobile terminal 5 and it is determined whether transaction information is stored (for example, S14 in FIG. 14), the mobile terminal 5 obtains information on whether transaction information is stored from the store server 2. The transaction information is input to the checkout device 3 from the store server 2. Specifically, when a terminal ID is input to the checkout device 3, the checkout device 3 obtains the transaction information corresponding to that terminal ID from the store server 2. [Explanation of symbols]

[0151] 1 Sales management system 4 Gate device 5. Mobile terminal (registration device) 213 Status management file (product registration information storage section) 504 Transaction information storage unit (product registration information storage unit) 4001 Input section 4004 Processing section 5004 Reception 5005 Output section [Prior art documents] [Patent documents]

[0152] [Patent Document 1] Japanese Patent Application Laid-Open No. 2017-187911

Claims

1. A sales management system having a registration device that performs product registration based on an operation of a customer who purchases a product, and a gate device that performs error processing when information indicating that payment for a product registered in the registration device has been completed is not input when the customer passes through, The sales management system further includes a store server including a product registration information storage unit that stores product registration information indicating whether or not a product has been registered based on a customer's operation, The registration device a reception unit that receives cancellation information indicating that the customer will cancel shopping without purchasing the product; a check unit that, when the reception unit receives the cancellation information, refers to the product registration information storage unit and checks whether there is any product registered; an output unit that outputs passing information for passing through the gate device on the condition that there is no registered product, The gate device is an input unit to which the passing information output by the output unit is input; a processing unit that allows the customer to pass without performing error processing when the passage information is input to the input unit; A sales management system equipped with:

2. A sales management system having a registration device that performs product registration based on an operation of a customer who purchases a product, and a gate device that performs error processing when information indicating that payment for a product registered in the registration device has been completed is not input when the customer passes through, The sales management system further includes a store server including a product registration information storage unit that stores product registration information indicating whether or not a product has been registered based on a customer's operation, The registration device a reception unit that receives cancellation information indicating that the customer will cancel shopping without purchasing the product; an output unit that outputs passage information for passing through the gate device when the reception unit receives the cancellation information, The gate device is an input unit to which the passing information output by the output unit is input; a check unit that, when the passing information is input to the input unit, refers to the product registration information storage unit and checks whether there is any product registered; a processing unit that allows the customer to pass without executing error processing on the condition that there is no registered product; A sales management system equipped with:

3. A sales management system having a registration device that performs product registration based on an operation of a customer who purchases a product, and a gate device that performs error processing when information indicating that payment for a product registered in the registration device has been completed is not input when the customer passes through, The registration device a product registration information storage unit that stores product registration information indicating whether or not a product has been registered based on a customer's operation; a reception unit that receives cancellation information indicating that the customer will cancel shopping without purchasing the product; a check unit that, when the reception unit receives the cancellation information, refers to the product registration information storage unit and checks whether there is any product registered; an output unit that outputs passing information for passing through the gate device on the condition that there is no registered product, The gate device is an input unit to which the passing information output by the output unit is input; a processing unit that allows the customer to pass without performing error processing when the passage information is input to the input unit; A sales management system equipped with:

4. the product registration information storage unit is a status management file that manages the customer's status based on the operation of the registration device; The sales management system according to claim 1 or 2.

5. The registration device is a mobile terminal carried by a customer, the output unit displays a code symbol indicating the passing information on a display unit of the portable terminal. The sales management system according to any one of claims 1 to 4.

Images