Product sales system, server, information processing method and information processing program
The product sales system allows shoppers to register products that are not allowed to be sold by using a terminal and server configuration to manage lists, reducing staff intervention and ensuring accurate accounting.
Patent Information
- Application Number
- JP2023033860
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2023-03-06
- Publication Date
- 2024-12-16
- Estimated Expiration
- 2038-03-05
AI Technical Summary
Existing product sales systems fail to allow shoppers to continue registering products that are not allowed to be sold, leading to inefficiencies and burdens on store staff due to the need for manual intervention.
A product sales system with an information terminal and server configuration that includes a first control means to manage product lists, allowing shoppers to register products, a second control means for shopper cancellations, and a third control means for store clerk interventions, ensuring permitted products are listed and unpermitted products are managed separately.
Enables shoppers to register products without staff intervention, with unpermitted products being managed in a dummy list, reducing staff burden and ensuring accurate accounting based on permitted products.
Smart Images

Figure 0007600287000001 
Figure 0007600287000002 
Figure 0007600287000003
Abstract
Description
[Technical field]
[0001] An embodiment of the present invention relates to a product sales system. , SERVER, INFORMATION PROCESSING METHOD AND INFORMATION PROCESSING PROGRAM Regarding. [Background technology]
[0002] 2. Description of the Related Art A system has been proposed in which a shopper uses a portable information terminal, such as an information terminal mounted on a cart or other such trolley, in the sales area of a store to register the purchase of an item that the shopper has decided to purchase. In such a system, for example, if a product that is not set as a product for sale in the system is mistakenly displayed in the sales area and a shopper selects such a product as one to purchase, an error has traditionally been reported.
[0003] Furthermore, such errors may require a store clerk to deal with them each time they occur, which places a burden on the store clerk and may cause shoppers to wait. In view of these circumstances, it has been desired that even if a product that is not permitted for sale is designated as a purchase target, the shopper be able to continue registering the product to be purchased. [Prior art documents] [Patent documents]
[0004] [Patent Document 1] JP 2011-108010 A 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 product sales system that allows a shopper to continue registering a product to be purchased even if a product that is not permitted for sale is specified as a purchase target. , SERVER, INFORMATION PROCESSING METHOD AND INFORMATION PROCESSING PROGRAM The purpose of this project is to provide [Means for solving the problem]
[0006] The product sales system of the embodiment includes an information terminal having an input means for inputting identification information for identifying a product and a first display, and a server capable of communicating with the information terminal. The server includes a first control means, a first reception means, a second control means, a third control means, a second reception means, and a fourth control means. Each time the identification information is input by the input means while the customer is walking around the sales floor, the first control means attempts to acquire first information related to the product identified by the identification information, and generates a registration screen including a list of the acquired first information on the first display. The first reception means accepts a cancellation instruction from the customer regarding the first information shown in the list included in the registration screen displayed on the first display. When the first reception means accepts the cancellation instruction, the second control means generates a registration screen in which second information indicating that the item has been canceled is added to the item for which the cancellation instruction was issued in the list included in the registration screen displayed on the first display. The third control means, when it is determined from the first information related to the product identified by the identification information input by the input means that the sale of the product is not permitted, displays third information indicating that the product is not permitted for sale, and the first information and the second information included in a list included in the registration screen displayed on the first display device, and is configured to display a display screen separate from the information terminal. Monitoring terminal The fourth control means updates the screen displayed on the second display when the second reception means receives the cancellation instruction. [Brief description of the drawings]
[0007] [Figure 1] 1 is an overall configuration diagram of a product sales system according to an embodiment. [Diagram 2] FIG. 2 is a schematic diagram showing an example of a layout of a store in which the product sales system shown in FIG. 1 has been installed. [Diagram 3] FIG. 2 is a block diagram showing a main circuit configuration of a first server in FIG. [Figure 4]FIG. 4 is a schematic diagram showing the main data structure of a data record for each product stored in the product database in FIG. 3 . [Diagram 5] FIG. 4 is a schematic diagram showing the main data structure of a data record for each member stored in the member database in FIG. 3. [Figure 6] 4 is a schematic diagram showing the main data structure of a data record for each piece of information stored in the sales promotion database in FIG. 3. [Figure 7] 2 is a block diagram showing a main circuit configuration of a second server in FIG. 1; [Figure 8] FIG. 8 is a schematic diagram showing the main data structure of a data record per cart included in the cart management database in FIG. 7. [Figure 9] 8 is a schematic diagram showing the main data structure of a data record per transaction machine contained in the transaction machine management database in FIG. 7 . [Figure 10] FIG. 2 is a block diagram showing a main circuit configuration of the information terminal in FIG. [Figure 11] FIG. 2 is a perspective view showing an example of the appearance of a cart. [Figure 12] 2 is a block diagram showing a main circuit configuration of the monitoring terminal in FIG. 1; [Figure 13] 8 is a flowchart of information processing performed by a processor in FIG. 7 in cooperation with an information terminal. [Figure 14] 8 is a flowchart of information processing performed by a processor in FIG. 7 in cooperation with an information terminal. [Figure 15] FIG. 4 is a schematic diagram showing a data structure of a product list. [Figure 16] FIG. 4 is a schematic diagram showing the data structure of a dummy list. [Figure 17] FIG. 13 is a schematic diagram showing the data structure of a product list after updating in response to the cancellation of a purchase registration. [Figure 18] FIG. [Figure 19] 8 is a flowchart of information processing performed by the processor in FIG. 7 in cooperation with the accounting machine. [Figure 20] 8 is a flowchart of information processing performed by a processor in FIG. 7 in cooperation with a monitoring terminal. [Figure 21]FIG. 4 is a diagram showing the configuration of a list screen. [Figure 22] FIG. 4 is a diagram showing the configuration of a list screen. [Diagram 23] FIG. 4 is a diagram showing the configuration of a list screen. [Figure 24] FIG. [Diagram 25] FIG. 13 is a schematic diagram showing the data structure of a dummy list after updating due to cancellation. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0008] Hereinafter, a product sales system in which the registration of purchased products is performed in response to the operation of an information terminal by a shopper, and the payment for the purchased products is also performed in response to the operation of a cash register by the shopper, will be described with reference to the drawings.
[0009] FIG. 1 is a diagram showing the overall configuration of a product sales system according to this embodiment. The product sales system 100 includes a first server 10, a second server 20, a POS (point-of-sale) terminal 30, a payment machine 40, an information terminal 50, and a monitoring terminal 60. The first server 10, the second server 20, the POS terminal 30, and the payment machine 40 are connected to a network 70 such as a LAN (local area network).
[0010] Both the information terminal 50 and the monitoring terminal 60 are equipped with wireless units. An access point 80 is connected to the network 70. The information terminal 50 and the monitoring terminal 60 are capable of communicating with each device connected to the network 70 via wireless communication with the access point 80.
[0011] Although FIG. 1 shows one each of the POS terminal 30, the accounting machine 40, the information terminal 50, the monitoring terminal 60, and the access point 80, two or more of each may be provided. The first server 10 and the second server 20 do not necessarily have to be connected to the network 70. For example, the network 70 may be connected to the Internet via a gateway, and at least one of the first server 10 and the second server 20 may be connected to the Internet. At least one of the first server 10 and the second server 20 may be realized by distributed processing by multiple servers. In this case, the multiple servers that perform distributed processing do not need to be connected to the network 70, as long as the servers that perform information processing in cooperation with each other can communicate with each other in some way. Also, a single server that has the functions of the first server 10 and the second server 20 may be provided in place of the first server 10 and the second server 20.
[0012] FIG. 2 is a schematic diagram showing an example of the layout of a store in which the product sales system 100 is installed. The information terminal 50 is temporarily operated by a shopper M1 who is shopping in the store. The information terminal 50 is attached to, for example, a shopping cart (hereinafter simply referred to as cart) C. The shopper M1 pushes the cart C around the sales floor and places the products he or she wishes to purchase directly on the cart C or in a basket placed on the cart C. At this time, the shopper M1 operates the information terminal 50 to register the products as purchased products. Then, when the shopper M1 has finished selecting all the products he or she wishes to purchase, he or she goes to the cashier G2 and pays for them. After this, the shopper M1 bags the products on a cashier counter SU as necessary.
[0013] The checkout counter G1 is provided with a POS terminal 30. The checkout counter G1 is also provided with a stationary scanner SC. A handheld scanner may be provided instead of or in addition to the scanner SC. When the cashier M2 causes the scanner SC to scan the barcodes of the purchased items one by one, the POS terminal 30 registers the item ID (identifier) indicated on the barcode as the item ID of the purchased item. The POS terminal 30 calculates the price of the purchased items and settles the price according to an operation by an operator through an exchange between the cashier M2 and the shopper M1 regarding the payment of the price. Payment can be made using cash, credit cards, electronic money, points, gift certificates, and other vouchers. It is also possible to configure a store without providing the checkout counter G1.
[0014] A payment machine 40 is installed in the payment counter G2. Data on purchased items registered by the information terminal 50 is managed by the second server 20. The payment machine 40 obtains data on purchased items for one transaction managed by the second server 20 and calculates the price for the purchased items. The payment machine 40 then settles the price in response to operations by the shopper M1. Payment can be made using cash, credit card, electronic money, points, etc. The price may also be calculated by the second server 20. In this case, instead of the payment machine 40, a payment machine with a function to settle the price calculated by the second server 20, that is, a function to only perform payment-related processes of the transaction, may be used.
[0015] An attendant counter AT is installed near the accounting corner G2. As described above, in a store that has introduced the product sales system 100, the customer M1 can operate the information terminal 50 and the accounting machine 40 to consistently perform the process from registering the purchased product to paying for it without the intervention of a store clerk. In the following, this mechanism is referred to as a cart POS service. However, when providing this cart POS service, there may be a situation where the intervention of a store clerk is unavoidable. For example, there is a case where a specialized salesperson must provide information to a shopper M1 who purchases medicines. In addition, there is a case where the information on a discount sticker is forgotten to be entered into the information terminal 50, and the regular price is registered. There may also be a case where an error occurs in the accounting machine 40, such as a coin jam or receipt paper running out.
[0016] In order to quickly respond to such events, a store clerk in charge of customer service, a so-called attendant M3, is always present at the attendant counter AT. The attendant counter AT is also equipped with a monitoring terminal 60. The attendant M3 can use the monitoring terminal 60 to monitor the status of each information terminal 50 and the payment machine 40.
[0017] Next, the configurations of the first server 10, the second server 20, the information terminal 50, and the monitoring terminal 60 will be described. Note that an existing POS terminal called a face-to-face type can be used as the POS terminal 30 as is. Also, the accounting machine 40 is similar to an existing accounting machine used in a semi-self-service product sales system. Therefore, a description of the configurations of the POS terminal 30 and the accounting machine 40 will be omitted.
[0018] FIG. 3 is a block diagram showing the main circuit configuration of the first server 10. As shown in FIG. The first server 10 includes a processor 11, a main memory 12, an auxiliary storage device 13, a communication interface 14, and a system transmission path 15. The system transmission path 15 includes an address bus, a data bus, a control signal line, etc., and is connected to the processor 11, the main memory 12, the auxiliary storage device 13, and the communication interface 14. The processor 11, the main memory 12, the auxiliary storage device 13, and the system transmission path 15 that connects them together constitute a computer that executes information processing to realize various functions as the first server 10.
[0019] The processor 11 corresponds to the central part of the computer. The processor 11 executes information processing for realizing various functions of the first server 10 according to information processing programs such as an operating system, middleware, and application programs. The processor 11 is, for example, a CPU (central processing unit).
[0020] The main memory 12 corresponds to the main storage portion of the computer. The main memory 12 includes a nonvolatile memory area and a volatile memory area. The main memory 12 stores at least a part of the information processing program in the nonvolatile memory area. The main memory 12 may also store data required for the processor 11 to execute processes for controlling each part in the nonvolatile or volatile memory area. The main memory 12 uses the volatile memory area as a work area where data is appropriately rewritten by the processor 11. For example, the nonvolatile memory area is ROM (read only memory). The volatile memory area is RAM (random access memory).
[0021] The auxiliary storage device 13 corresponds to the auxiliary storage portion of the computer. For example, an EEPROM (electric erasable programmable read-only memory), a HDD (hard disk drive), or an SSD (solid state drive) is used as the auxiliary storage device 13. The auxiliary storage device 13 stores data used by the processor 11 when performing various processes and data created by the processes in the processor 11. The auxiliary storage device 13 may also store a part of the information processing program. The communication interface 14 performs data communication with each unit connected to the network 70 in accordance with a predetermined communication protocol.
[0022] Part of the storage area of the auxiliary storage device 1 is used as a product database 131, a member database 132, and a sales promotion database 133. FIG. 4 is a schematic diagram showing the main data structure of a data record 131R for each product stored in the product database 131. As shown in FIG. 4 is included in the product database 131 in association with each of a plurality of products sold in the store. The data records 131R related to products newly starting to be sold in the store are added by the processor 11 in response to an operation by the manager or the like of the product sales system 100. The data records 131R are deleted by the processor 11 in response to an operation by the manager or the like when the sale of the associated products is to be discontinued. The data records 131R are updated by the processor 11 in response to an instruction by the manager or the like when the sales conditions of the associated products are changed. The data record 131R includes fields F1, F2, F3, F4, F5, F6, and F7.
[0023] In the field F1, a product ID is set, which is a unique code for distinguishing the associated product from other products. In the field F2, a product name is set, which is a name given to the associated product. In the field F3, a sales price per unit of the associated product is set. In the field F4, a classification name is set, which is a name given to the classification to which the associated product belongs. The classification is predefined so that multiple types of products belong to it. For example, a classification with the classification name "apple" is defined as including various products with product names such as "Fuji", "Jonagold", and "Red Delicious". In the field F5, a promotion ID is set, which is a code for identifying a promotional measure for the associated product. The promotional measure is, for example, granting the right to participate in a campaign for the purchase of the product, discounting the selling price when the product is purchased, discounting the selling price when the product is purchased together with other products, issuing a coupon for the purchase of the product, and the like. Incidentally, if the implementation of a promotional measure is not defined for the associated product, a null value is set in the field F5. In this embodiment, one promotional information item can be associated with one product, but two or more promotional information items may be associated with one product. In field F6, a restriction flag is set as 1-bit information for identifying whether the associated product is an age-restricted product such as alcoholic beverages or tobacco. In this embodiment, if there is an age restriction, "1" is set in field F6, and if there is no age restriction, "0" is set in field F6. In field F7, the sales period of the associated product is set. For example, if a best-before date is set for the associated product, the date of the best-before date is set in field F7. Also, for example, if the associated product is planned to be sold for a limited time, the start date and end date of the sales period are set in field F7.
[0024] FIG. 5 is a schematic diagram showing the main data structure of a data record 132R for each member stored in the member database 132. As shown in FIG. The member database 132 includes a data record 132R having a structure as shown in Fig. 5, associated with each member who has registered to use the cart POS service. The data record 132R is added by the processor 11 based on data sent for member registration from an information terminal (not shown), for example. The data record 132R is deleted by the processor 11 based on data sent for cancellation from the information terminal, for example. The data record 132R is updated by the processor 11 based on data sent for changes from the information terminal. The data record 132R is updated by the processor 11 upon receiving a notification that a product has been purchased by the associated member. The data record 132R includes fields F11, F12, and F13.
[0025] Field F11 is set with a member ID, which is a unique code set to identify the associated member. The member possesses a recording medium on which the member ID is recorded. The recording medium is, for example, a magnetic card, a contact IC (Integrated Circuit) card, a contactless IC card, a smartphone, etc. Field F12 is set with personal identification data for identifying the associated member. Examples of personal identification data include name, date of birth, gender, address, contact phone number, etc. Field F13 is set with purchase history data indicating the purchase history of what the associated member purchased and when.
[0026] FIG. 6 is a schematic diagram showing the main data structure of a data record 133R for each piece of information stored in the sales promotion database 133. As shown in FIG. A data record 133R having a structure as shown in Fig. 6 is included in the sales promotion database 133 in association with each of a plurality of sales promotion measures that may be implemented in a store. The data record 133R is added by the processor 11 in response to an operation by a manager or the like of the product sales system 100, for example, when a new sales promotion measure is introduced in the store. The data record 133R is deleted by the processor 11 in response to an operation by the manager or the like, for example, when a sales promotion measure is no longer implemented in the store. The data record 133R is updated by the processor 11 in response to an operation by the manager or the like, for example, when the content of the sales promotion measure is changed. The data record 133R includes fields F21 and F22.
[0027] A promotion ID, which is a unique code for identifying the associated promotional measure, is set in field F21. One of the promotion IDs set in fields F21 of the data records 133R is set in field F5 of the data record 131R described above. Promotion data indicating the content of the associated promotional measure is set in field F22.
[0028] FIG. 7 is a block diagram showing the main circuit configuration of the second server 20. As shown in FIG. The second server 20 includes a processor 21, a main memory 22, an auxiliary storage device 23, a communication interface 24, and a system transmission path 25. The system transmission path 25 includes an address bus, a data bus, a control signal line, etc., and the processor 21, the main memory 22, the auxiliary storage device 23, and the communication interface 24 are connected to the system transmission path 25. The processor 21, the main memory 22, the auxiliary storage device 23, and the system transmission path 25 connecting them constitute a computer that executes information processing to realize various functions of the second server 20. The functions of the processor 21, the main memory 22, the auxiliary storage device 23, and the communication interface 24 are generally the same as those of the processor 11, the main memory 12, the auxiliary storage device 13, and the communication interface 14, so that a description thereof will be omitted.
[0029] A part of the memory area of the auxiliary memory device 23 is used as a cart management database 231 and an accounting machine management database 232 . FIG. 8 is a schematic diagram showing the main data structure of the data record per cart 231R contained in the cart management database 231. As shown in FIG. 8 is associated with each cart C used in the store and is included in the cart management database 231. The data record 231R includes fields F31, F32, F33, F34, and F35.
[0030] In the field F31, a terminal ID, which is a unique code for identifying the information terminal 50 attached to the associated cart C, is set. In the field F32, a cart name, which is a name given to the associated cart C, is set. In the field F33, a transaction ID, which will be described later, is set when the associated cart C is being used by the shopper M1. In the field F34, a membership ID of the shopper M1 is set when the associated cart C is being used by the shopper M1. In the field F35, a current operation stage of the associated cart C is set. The operation stage is a stage that defines in which state the cart C is being used in a series of operations related to a transaction in the cart POS service, by dividing the series of operations into several stages. In this embodiment, the operation stage corresponding to the state in which the cart C is not being used is set to "standby". In addition, the operation stage corresponding to the state in which the cart C is being used to register the purchase of a product is set to "registering". In addition, the operation stage corresponding to the state in which the price of the product registered for purchase using the cart C is being paid for is set to "payment". In the field F33, one of these stages is set.
[0031] The data record 231R is added by the processor 21 in response to an instruction from an operator or the like when the product sales system 100 is introduced to a store. The data record 231R is added by the processor 21 in response to an instruction from a manager or the like of the product sales system 100 when, for example, a new cart C is started to be used. The data record 231R is added by the processor 21 in response to an instruction from the manager or the like when, for example, the associated cart C is discarded. The data record 231R is updated by the processor 21 in response to an instruction from the manager or the like, for example, when the management form for the associated cart C is changed. The data record 231R is updated by the processor 21 in response to a change in the usage situation by the shopper M1 for the associated cart C. The contents of the fields F31 and F32 of the data record 231R are set when the data record 231R is added or updated as described above. The contents of the fields F33, F34, and F35 are appropriately set by the processor 21.
[0032] FIG. 9 is a schematic diagram showing the main data structure of the data record 232R per transaction machine contained in the transaction machine management database 232. As shown in FIG. A data record 232R having a structure as shown in FIG. 9 is included in the payment machine management database 232 in association with each payment machine 40 used in the store. The data record 232R is added by the processor 21 in response to an instruction from an operator or the like when, for example, the product sales system 100 is introduced into the store. The data record 231R is added by the processor 21 in response to an instruction from an installer of the payment machine 40 or a manager of the product sales system 100 when, for example, a new payment machine 40 is installed in the store. The data record 231R is added by the processor 21 in response to an instruction from a installer of the payment machine 40 or the above-mentioned manager or the like when, for example, the associated payment machine 40 is removed from the store. The data record 231R is updated by the processor 21 in response to an instruction from the above-mentioned manager or the like, for example, when the management form for the associated payment machine 40 is changed. The data record 231R is updated by the processor 21 in response to a change in the operating status for the associated payment machine 40. And data record 232R includes fields F41, F42, F43, F44, F45 and F46.
[0033] In the field F41, a payment machine ID, which is a unique code for identifying the associated payment machine 40, is set. In the field F42, a payment machine name, which is a name given to the associated payment machine 40, is set. In the field F43, the current operation stage of the associated payment machine 40 is set. The operation stage is a state in which the payment machine 40 is in a series of steps related to the payment of the purchased goods, and is determined by dividing the above series of steps into several stages. In this embodiment, the operation stage corresponding to the state in which the payment machine 40 is not processing for the payment is set to "idle". Also, the operation stage corresponding to the state in which the payment machine 40 is processing for the payment is set to "payment in progress". In the field F44, a call flag is set as 1-bit information for indicating whether the associated payment machine 40 is in a state in which a clerk is being called. In this embodiment, "1" is set in the field F44 when the associated payment machine 40 is in a state in which a clerk is being called, and "0" is set when the associated payment machine 40 is not in the said state. In the field F45, a refill flag is set as 1-bit information for indicating whether the associated payment machine 40 needs to be refilled with coins. In this embodiment, a "1" is set in field F45 if a state requires currency replenishment, and a "0" is set if this state does not require currency replenishment. A collection flag is set in field F46 as 1-bit information indicating whether or not currency needs to be collected from the associated accounting machine 40. In this embodiment, a "1" is set in field F46 if a state requires currency collection, and a "0" is set if this state does not require currency collection.
[0034] FIG. 10 is a block diagram showing the main circuit configuration of the information terminal 50. As shown in FIG. The information terminal 50 includes a processor 51, a main memory 52, an auxiliary storage device 53, a wireless unit 54, a touch panel 55, a scanner 56, a reader 57, and a system transmission path 58. The system transmission path 58 includes an address bus, a data bus, a control signal line, and the like, and the processor 51, the main memory 52, the auxiliary storage device 53, the wireless unit 54, the touch panel 55, the scanner 56, and the reader 57 are connected to the system transmission path 58. The processor 51, the main memory 52, and the auxiliary storage device 53, and the system transmission path 58 connecting them, constitute a computer that executes information processing to realize various functions of the information terminal 50. The functions of the processor 51, the main memory 52, and the auxiliary storage device 53 are roughly equivalent to those of the processor 11, the main memory 12, and the auxiliary storage device 13, and therefore will not be described here.
[0035] The wireless unit 54 performs data communication with each component connected to the network 70 via wireless communication with the access point 80 in accordance with a predetermined wireless communication protocol. The touch panel 55 is a device that functions as both an input device and a display device for the information terminal 50. The touch panel 55 is used to input various instructions from an operator such as the shopper M1 and data designated by the operator. The touch panel 55 displays any screen under the instruction of the processor 51.
[0036] The scanner 56 has a camera as an imaging unit, and reads a code symbol such as a barcode or a two-dimensional data code from an image captured by the camera. Reader 57 reads data such as a member ID recorded on a recording medium. Therefore, reader 57 is a magnetic card reader when the recording medium is a magnetic card, and is an IC card reader when the recording medium is a contact IC card. Also, in the case of a recording medium that uses RFID (radio frequency identification), such as a contactless IC card or a smartphone, an RFID reader is used as reader 57.
[0037] It is assumed that the information terminal 50 uses devices provided in a general-purpose tablet terminal as the processor 51, the main memory 52, the auxiliary storage device 53, the wireless unit 54, and the touch panel 55. In other words, in this case, the information terminal 50 is configured by connecting a scanner 56 and a reader 57 to a general-purpose tablet terminal.
[0038] FIG. 11 is a perspective view showing an example of the appearance of the cart C. The cart C is equipped with caster members C1 for mobility, a handle frame member C2, and a basket receiving member C3.
[0039] The caster portion C1 has four wheels for smooth movement on the floor surface. The handle frame portion C2 includes a pair of vertical frames C21, C21 and a handle bar C22. The vertical frames C21, C21 are erected above the two wheels of the caster portion C1. The handle bar C22 connects the upper ends of the vertical frames C21, C21. The basket receiving portion C3 is provided horizontally from a midpoint of the handle frame portion C2. The basket receiving portion C3 holds a shopping basket BA for storing merchandise. The caster portion C1 also holds the shopping basket BA thereon.
[0040] Typically, a shopper M1, who is located closer to the viewer in Fig. 11 than the handle frame portion C2, pushes the cart C while gripping the handle bar C22. In other words, the direction in which the basket receiving portion C3 protrudes relative to the handle frame portion C2 is the forward direction of the cart C.
[0041] A scanner 56 is attached to the middle of the handlebar C22. A pole C4 is attached to one of the vertical frames C21 so that its tip is located above the handlebar C22. The above-mentioned tablet terminal TM is attached to the tip of the pole C4 with the screen of the touch panel 55 facing the opposite direction to the forward direction. A reader 57 is attached to the tablet terminal TM. In FIG. 11, the reader 57 is a magnetic card reader. The card slit of the reader 57 faces the same direction as the screen of the touch panel 55. A battery BT is attached between the vertical frames C21, C21 on the lower end side of the handle frame portion C2. The battery BT is a driving power source for the tablet terminal TM and the scanner 56.
[0042] FIG. 12 is a block diagram showing the main circuit configuration of the monitoring terminal 60. As shown in FIG. The monitoring terminal 60 includes a processor 61, a main memory 62, an auxiliary storage device 63, a wireless unit 64, a touch panel 65, and a system transmission path 66. The system transmission path 66 includes an address bus, a data bus, a control signal line, and the like, and the processor 61, the main memory 62, the auxiliary storage device 63, the wireless unit 64, and the touch panel 65 are connected to the system transmission path 66. The processor 61, the main memory 62, the auxiliary storage device 63, and the system transmission path 66 connecting them constitute a computer that executes information processing to realize various functions of the monitoring terminal 60. The functions of the processor 61, the main memory 62, the auxiliary storage device 63, the wireless unit 64, and the touch panel 65 are generally the same as those of the processor 11, the main memory 12, the auxiliary storage device 13, the wireless unit 54, and the touch panel 55, and therefore will not be described here. The monitoring terminal 60 may be any of various information processing devices, such as a tablet terminal, a notebook computer, or a desktop computer.
[0043] Next, a description will be given of the operation of the product sales system 100 configured as above. Note that the multiple information processes described below are merely examples, and the process order and process contents can be changed as appropriate as long as similar results can be obtained. The information terminal 50 attached to the cart C placed in the cart storage area is in a standby state. In the information terminal 50 in this standby state, the processor 51 waits for a login operation to be performed.
[0044] When a shopper M1, who is a member, starts shopping using the cart POS service, he or she removes the cart C from the cart area and performs a predetermined login operation, such as having the reader 57 provided in the information terminal 50 read data such as the member ID recorded on a recording medium. Then, the processor 51 in the information terminal 50 accesses the first server 10 and authenticates the member by, for example, referring to the member database 132. If the authentication is successful, the processor 51 requests the second server 20 to establish a session. At this time, the processor 41 notifies the second server of the above-mentioned member ID at the same time as the request for session establishment or in response to the session being established.
[0045] When the processor 21 in the second server 20 receives the request via the communication interface 24 and is notified of the request by the communication interface 24, the processor 21 starts information processing as described below. The processor 21 executes the processes described below in parallel in response to requests from each of the multiple information terminals 50. However, the following description will be given of information processing for only one information terminal 50.
[0046] 13 and 14 are flowcharts of information processing performed by the processor 21 in cooperation with the information terminal 50. The processor 21 executes the information processing based on an information processing program stored in the main memory 22 or the auxiliary storage device 23.
[0047] In Act 1, the processor 21 establishes a session for data communication via the LAN 70 with the requesting information terminal 50. This session can be established using existing communication technology as is. The processor 21 uses this session to communicate with the requesting information terminal 50 in the various processes that follow in Figs. 13 and 14. In the explanation of the information processing shown in Figs. 13 and 14, when "information terminal 50" is simply mentioned, this refers to the information terminal 50 with which the session has been established. At this time, the processor 21 updates the data record 231R in which the terminal ID of the information terminal 50 is set in field F31. Specifically, the processor 21 sets a transaction ID in field F33 that is determined not to overlap with transaction IDs given to other transactions in order to identify each transaction. The processor 21 also sets the member ID notified from the information terminal 50 in field F34 as described above. The processor 21 also rewrites field F35 to "registering".
[0048] In Act 2, the processor 21 generates a registration screen to be displayed on the information terminal 50, and transmits screen data representing the registration screen to the information terminal 50. The registration screen is a GUI (graphical user interface) screen that allows the shopper M1 to check the registration status of the purchased item and accepts instructions from the shopper M1. Details of the registration screen will be described later. When various screen data, including but not limited to the registration screen, is received by the wireless unit 54 in the information terminal 50, the processor 51 causes the touch panel 55 to display the screen represented by the screen data. In Act 3, the processor 21 waits for the product code to be notified.
[0049] The shopper M1, pushing the cart C started up as described above, walks around the store looking for a product to be purchased. When he finds a product to be purchased, he takes it out of the display area and places it on the cart C. At this time, the shopper M1 instructs the scanner 56 to read the code symbol displayed on the product, or touches a button on the touch panel 55 associated with the product, to register the product as a purchased product. Then, the processor 51 of the information terminal 50 determines the product ID of the product in response to the instruction. In other words, the information terminal 50 corresponds to a first terminal that obtains the product ID. Then, the processor 51 notifies the second server 20 of the product ID. Specifically, the processor 51 causes the wireless unit 54 to wirelessly transmit notification data in a predetermined format including the determined product ID to the second server 20. Then, the notification data is transmitted to the second server 20 via the access point 80 and the network 70, and is received by the communication interface 24. In addition, requests, notifications, responses, etc. between each device in the operation described below are realized by transmitting and receiving predetermined data according to each purpose via the network 70 in the same manner as described above, but detailed description thereof will be omitted below. In response to the notification data being received by the communication interface 24 in this manner, the processor 21 judges "Yes" in Act 3 and proceeds to Act 4.
[0050] In Act 4, the processor 21 checks whether the notified product ID is registered in the product database 131. Specifically, the processor 21 extracts the product ID from the notification data received by the communication interface 24, and requests the first server 10 to make an inquiry about the product ID. When the processor 11 in the first server 10 receives this request, the processor 11 checks whether the product database 131 contains a data record 131R in which the corresponding product ID is set in the field F1. If the corresponding data record 131R exists, the processor 11 transmits the data record 131R to the second server 20 as a response to the inquiry request. However, the processor 11 may transmit only a part of the data contained in the data record 131R, or may additionally transmit data not contained in the data record 131R. If the corresponding data record 131R does not exist, the processor 11 notifies the second server 20 of "not registered" as a response to the inquiry request. If the data record 131R is transmitted as a response, the processor 21 in the second server 20 judges "Yes" in Act 4 and proceeds to Act 5.
[0051] In Act 5, the processor 21 acquires the transmitted data record 131R as product data related to the specified product. The processor 21 stores the product data in the main memory 22 or the auxiliary storage device 23.
[0052] In Act 6, the processor 21 checks whether the sale of the specified product is permitted based on the product data acquired in Act 5. Here, the processor 21 checks whether the sale of the product is permitted based on whether a condition for permitting the sale or a condition for prohibiting the sale, which is predetermined for each product, is satisfied. For example, when a sales period is set in the field F7 of the product data, the processor 21 determines that the sale is not permitted if the sales period does not include the current time. In addition, the processor 21 determines that the sale is not permitted if, for example, the restriction flag set in the field F6 of the product data is "1" and the shopper M1 is under 20 years old. The processor 21 queries the first server 10 and refers to the data record 132R in the member database 132 in which the member ID acquired in Act 1 is set in the field F11. The processor 21 then checks the age of the shopper M1 based on the individual identification data set in the field F12 of the data record 132R. The product data may include a field for setting another condition, and when a condition is set in that field, the processor 21 may determine whether or not the sale is permitted depending on whether or not the condition is satisfied. For example, for products that require an explanation from an authorized person, such as some medicines, a field for setting a flag indicating whether or not an explanation is required may be included in advance in the product data. Then, when the flag set in that field indicates that an explanation is required, the processor 21 determines that the sale is not permitted. If the sale is permitted, the processor 21 determines Yes in Act 6 and proceeds to Act 7.
[0053] In Act 7, the processor 21 updates the product list to include the product ID notified from the information terminal 50 as described above. The product list is stored in the main memory 22 or the auxiliary storage device 23. When the processor 21 performs Act 7 for the first time after starting the information processing shown in FIG. 13, the processor 21 generates a new product list and stores it in the main memory 22 or the auxiliary storage device 23. Here, the product list is a list of purchased products. The processor 21 may execute a plurality of the information processing shown in FIG. 13 and FIG. 14 in parallel, and therefore a plurality of product lists relating to a plurality of transactions may be stored in the main memory 22 or the auxiliary storage device 23.
[0054] Fig. 15 is a schematic diagram showing the data structure of a product list, showing the structure of a product list L1 as an example in which five products have already been registered as purchased products. The product list L1 shown in FIG. 15 includes fields F51, F52, F53, F54, F55, F56, F57, F58, and F59. The processor 21 sets the same transaction ID in the field F51 as that set in the field F33 of the data record 231R when the session is established in Act 1. The processor 21 sets the terminal ID of the information terminal 50 in the field F52. The processor 21 sets the member ID acquired in the session establishment in Act 1 in the field F53. The processor 21 sets the product data acquired in Act 5 as described above in each field from field F54 onwards. However, the product list newly generated when the processor 21 performs Act 7 for the first time after starting the information processing shown in FIG. 13 does not include fields F55-F59 in the product list L1. Then, when the processor 21 executes Act 7 again as described later, the processor 21 adds the fields in which the product data acquired in Act 5 immediately before that is set to the product list one by one. As described above, the product list includes the product ID as a product identifier only when the sale of the product identified by the product ID is permitted, and corresponds to the first list.
[0055] When the processor 21 finishes updating the product list, it proceeds to Act 8. If the processor 21 receives a "not registered" notification for the product ID notified from the information terminal 50 as a response to the inquiry request, it judges "No" in Act 4, skips Act 5-Act 7, and proceeds to Act 8. That is, if the specified product is not registered in the product database 131, the processor 21 does not add the product to the product list. It is a rule that all data records 131R associated with each product displayed in the store are included in the product database 131. However, due to a maintenance error in the product database 131, it may happen that the product is displayed in the store, but the data record 131R associated with the product is not included in the product database 131. In such a case, when the corresponding product is specified as a purchase target, the processor 21 judges "No" in Act 4. According to the above principle, a product whose associated data record 131R is not included in the product database 131 can be said to be a product that the product sales system 100 does not permit to be sold.
[0056] Also, if the processor 21 determines in Act 6 that sales are not permitted, it determines No in Act 6, skips Act 7, and proceeds to Act 8. In other words, the processor 21 does not add product data related to the specified product to the product list in these cases. In other words, when sales of the specified product are not permitted, the processor 21 does not add the product to the product list. That is, the processor 21 does not add products that are not registered in the product database 131 and products that are not permitted to be sold based on predetermined conditions to the product list as products that are not permitted to be sold. Note that there may be products that are actually displayed in the sales area of a store as products that are permitted to be sold, but that are not registered in the product database 131 due to a mistake or the like. That is, in this embodiment, a "product that is not permitted to be sold" is a product that is not managed as a product for sale in the product sales system 100, and has no relation to whether or not the product is actually sold in a store, etc.
[0057] In Act 8, the processor 21 updates the dummy list. The dummy list is stored in the main memory 22 or the auxiliary storage device 23. When performing Act 8 for the first time after starting the information processing shown in FIG. 13, the processor 21 generates a new dummy list and stores it in the main memory 22 or the auxiliary storage device 23.
[0058] Fig. 16 is a schematic diagram showing the data structure of a dummy list, in which Fig. 16 shows the structure of a dummy list L2 as an example when the product list is in the state shown in Fig. 15. The dummy list L2 shown in FIG. 16 includes fields F61, F62, F63, F64, F65, F66, F67, and F68. In each field, the processor 21 sets the product data when the product data has been acquired in Act 5 as described above, and in a case where the product data has not been acquired because Act 5 has been skipped, the processor 21 sets the product ID notified from the information terminal 50. The processor 21 may set the product data in each field after deleting some of the data contained therein.
[0059] However, when the processor 21 performs Act 8 for the first time after starting the information processing shown in Fig. 13, the newly generated product list will not include fields F62-F68 in the dummy list L2. Then, when the processor 21 executes Act 8 again as described below, the processor 21 adds to the dummy list one by one the fields in which the product data acquired in Act 5 immediately before or the notified product ID is set. Thus, the dummy list is a list that shows the product data or product ID for all products designated as purchase targets, regardless of whether the sale of the products is permitted or not.
[0060] As described above, the dummy list includes product IDs as product identifiers, regardless of whether the sale of the products identified by the product IDs is permitted or not, and corresponds to the second list. The main memory 22 or the auxiliary storage device 23 stores the dummy list corresponding to the second list and the product list corresponding to the first list, and functions as a storage means. Note that in this embodiment, among the products related to the product IDs or product data included in the dummy list, it is possible to distinguish products that are not permitted for sale as products different from the products related to the product data included in the product list.
[0061] 14, the processor 21 creates a registration screen and transmits the registration screen to the information terminal 50. The registration screen will be described later.
[0062] In Act 10, the processor 21 checks whether or not a new product ID has been notified from the information terminal 50. If the notification has not been made, the processor 21 determines that the result is No and proceeds to Act 11. In Act 11, the processor 21 checks whether the product list has been updated by a separate process described later. If the product list has not been updated, the processor 21 determines the result as No and proceeds to Act 12.
[0063] In Act 12, the processor 21 checks whether a cancellation instruction has been issued to exclude a product registered as a purchase product from the purchase target. If the cancellation instruction has not been issued, the processor 21 determines that the cancellation instruction is No and proceeds to Act 13. In Act 13, the processor 21 checks whether or not a payment instruction has been given to proceed to payment. If no such instruction has been given, the processor 21 determines that the payment is not required and returns to Act 10. Thus, in Act10-Act13, the processor 21 waits for any of notification of a product ID, updating of the product list, a cancellation instruction, and a checkout instruction.
[0064] If the shopper M1 purchases multiple products, he / she repeats the above-mentioned operation to sequentially specify the multiple products. Then, the processor 51 of the information terminal 50 notifies the second server 20 of the product ID of the product each time the product is specified. Then, in the second server 20, the processor 21 judges "Yes" in Act 10 when a new product ID is notified in this way, and returns to Act 4 in FIG. 13. Then, the processor 21 repeats Act 4 and subsequent steps in the same manner as described above. Thus, when product specification is repeated as described above, the processor 21 updates the dummy list to include a field in which product data or product ID related to the specified product is set. Furthermore, if the sale of the newly specified product is permitted, the processor 21 adds a field in which product data of the product is set to the product list.
[0065] The product list L1 shown in FIG. 15 and the dummy list L2 shown in FIG. 16 show the state after the processor 21 executes Act 8 seven times. More specifically, this is the state after eight products with product names "AAA", "BBB", "CCC", "DDD", "EEE", "EEE", "FFF", and "GGG" are designated as purchase targets in that order. The sale of products with product names "AAA", "CCC", "EEE", "FFF", and "GGG" is permitted. The product with the product name "BBB" was not registered in the product database 131, so the product data of this product is not included in the product list, and the product ID of the dummy list is set in field F62. The product with the product name "DDD" was registered in the product database 131, but sales were not permitted, so the product data of this product is not included in the product list, and the product data of the dummy list is set in field F64.
[0066] When the shopper M1 wishes to cancel the purchase of a product that has been registered as a purchase target, the shopper M1 touches the button BU1 displayed for the product on the registration screen. In response to this, the processor 51 notifies the second server 20 that a cancellation instruction has been issued, in such a manner that the product ID of the product to be canceled can be identified. Note that the display of the registration screen SC1 on the information terminal 50 and the notification to the second server 20 that the button BU1 has been touched can be realized, for example, by the functions of an existing web browser. When the processor 21 in the second server 20 receives the above notification, it judges Yes in Act 12 and proceeds to Act 14. In Act 14, the processor 21 updates the product list to indicate that the purchase registration for the product designated for cancellation has been cancelled.
[0067] Fig. 17 is a schematic diagram showing the data structure of a product list after updating due to the cancellation of a purchase registration. However, Fig. 17 shows the structure of product list L3 as an example when a product with the product name "CCC" is cancelled from the product list L1 shown in Fig. 15.
[0068] 17, a field F71 is added after the field F55. The processor 21 sets a cancellation flag in this field F71 to indicate that the purchase registration of the product related to the product data set in the previous field F55 has been cancelled. In this embodiment, the cancellation flag is set to "1". The processor 21 then returns to the standby state of Act10-Act13.
[0069] Meanwhile, when the processor 21 is in a standby state from Act 10 to Act 13, the touch panel 55 of the information terminal 50 displays a registration screen based on the screen data transmitted in Act 9.
[0070] Fig. 18 is a diagram showing a registration screen, in which Fig. 18 shows an example of a registration screen SC1 based on the dummy list L2 shown in Fig. 16 and the product list L3 shown in Fig. 18. The processor 21 displays a list TA1 of products shown in the dummy list L2 on the registration screen SC1. In the list TA1, the processor 21 displays product names in rows for products whose product data is included in the dummy list L2, and product IDs for products whose product IDs are included in the dummy list L2. For products whose product data is included in the product list L3, the processor 21 displays the registered quantity and sales price of the product in columns for the product name. In the list TA1, the processor 21 marks the product name, registered quantity, and sales price corresponding to the product data immediately before the cancellation flag included in the product list L3 with a strikethrough. The processor 21 arranges icon areas IA1 in rows of the list TA1. Although not shown, the processor 21 displays icons corresponding to the associated products in the icon area IA1 as necessary. The processor 21 arranges the button BU1 in each row of the list TA1 corresponding to the product data included in the product list L3 and not having a cancellation flag added. The operation of the shopper M1 touching the button BU1 is the operation for issuing the cancellation instruction described above.
[0071] For products whose product IDs are included in the dummy list L2, the processor 21 displays the character string "Product registration error" before the product ID, and also displays a guidance message saying "A cashier will check this at the time of payment." The processor 21 displays a button BU2 for issuing accounting instructions on the registration screen SC1.
[0072] When the shopper M1 has finished registering all the products to be purchased, he / she touches the button BU2 to instruct the shopper to make a payment. The processor 51 then notifies the second server 20 of this fact. When the processor 21 in the second server 20 receives this notification, it judges "Yes" in Act 13 and proceeds to Act 15.
[0073] In Act 15, processor 21 generates a checkout guide screen to be displayed on information terminal 50, and transmits screen data representing the checkout guide screen to information terminal 50. Processor 21 displays a code symbol representing the transaction ID on the checkout guide screen. Processor 21 also displays at least one of a text message and an image on the checkout guide screen to guide shopper M1 to read the code symbol using a scanner provided on checkout machine 40 in order to start checkout. When the screen data showing the checkout information screen is transmitted to the information terminal 50, the processor 51 causes the touch panel 55 to display the checkout information screen based on the screen data.
[0074] Customer M1 pushes cart C to checkout counter G2, and uses a scanner installed in an available checkout machine 40 to read the code symbol displayed on the checkout information screen. In response, checkout machine 40 requests second server 20 to establish a session.
[0075] Now, in the second server 20, when the processor 21 receives the above request via the communication interface 24 and is notified of this by the communication interface 24, it starts information processing as described below. The processor 21 executes the information processing described below in parallel in response to requests from each of the multiple payment machines 40. However, the following describes information processing for only one payment machine 40. The processor 21 is also capable of executing the information processing described below while executing the information processing shown in Figures 13 and 14.
[0076] 19 is a flowchart of information processing performed by the processor 21 in cooperation with the payment apparatus 40. The processor 21 executes the information processing based on an information processing program stored in the main memory 22 or the auxiliary storage device 23.
[0077] In Act 21, the processor 21 establishes a session for data communication via the LAN 70 with the requesting accounting machine 40. The processor 21 then uses this session to communicate with the requesting accounting machine 40 in the various processes that follow in Figure 19. Furthermore, in the explanation of the information processing shown in Figure 19, when "accounting machine 40" is simply mentioned, this refers to the accounting machine 40 with which the session has been established.
[0078] When the session is established, the payment device 40 notifies the second server 20 of the transaction ID indicated in the read code symbol. In Act 22, the processor 21 acquires the notified transaction ID.
[0079] In Act 23, processor 21 transmits to payment machine 40 a product list in which the acquired transaction ID is set in the first field from among the product lists stored in main memory 22 or auxiliary storage device 23. At this time, processor 21 updates data record 231R in which the same terminal ID as that set in the second field of the transmitted product list is set in field F31, by rewriting field F35 to "payment in progress". Processor 21 also updates data record 232R in which the payment machine ID of payment machine 40 is set in field F41, by rewriting field F43 to "payment in progress". Prior to this rewrite, field F43 was "idle".
[0080] When the payment machine 40 receives the product list, it calculates the payment amount based on the product data included in the product list and executes a payment process to settle this payment amount. This payment process may be similar to that performed by another existing payment machine. Then, when the payment machine 40 has completed the payment, it notifies the second server 20 to that effect. In this way, the payment machine 40 settles the price of the transaction based on the product list as the first list. In this way, the payment machine functions as a payment means.
[0081] In the second server 20, after transmitting the product list in Act 23 as described above, the processor 21 proceeds to Act 24. In Act 24, the processor 21 waits for the completion of the payment based on the transmitted product list. If the payment device 40 notifies the processor 21 that the payment has been completed, the processor 21 judges the result as Yes and proceeds to Act 25. In Act 25, the processor 21 deletes from the main memory 22 or the auxiliary storage device 23 the product list and the dummy list in which the transaction ID acquired in Act 22 is set in the top field.
[0082] In Act 26, processor 21 terminates the session established in Act 21. Then, processor 21 ends the information processing. At this time, processor 21 updates data record 231R in which the same terminal ID as that set in the second field of the transmitted product list is set in field F31, by rewriting field F35 to "standby". Processor 21 also updates data record 232R in which the accounting machine ID of accounting machine 40 is set in field F41, by rewriting field F43 to "idle".
[0083] If the payment is completed as described above, the processor 21 judges "Yes" in Act 16 in FIG. 14 and proceeds to Act 17. In Act 17, the processor 21 terminates the session with the information terminal 50. Then, the processor 21 ends the information processing shown in FIGS. With the above, one transaction using one cart C is completed.
[0084] Incidentally, in the second server 20, when the monitoring terminal 60 accesses the second server 20 in response to the operation of the attendant M3, the processor 21 starts information processing as described below. The processor 21 executes the processing described below in parallel in response to accesses from each of the multiple monitoring terminals 60. However, the following description will be given of information processing for only one monitoring terminal 60.
[0085] Fig. 20 is a flowchart of information processing performed by the processor 21 in cooperation with the monitoring terminal 60. The processor 21 executes the information processing based on an information processing program stored in the main memory 22 or the auxiliary storage device 23. The processor 21 can execute the information processing described below while executing the information processing shown in Figs. 13 and 14 and further the information processing shown in Fig. 19.
[0086] In Act 31, the processor 21 establishes a session for data communication via the LAN 70 with the access source monitoring terminal 60. The processor 21 then uses this session to communicate with the request source monitoring terminal 60 in the various processes that follow in Fig. 20. In addition, in the explanation of the information processing shown in Fig. 20, when "monitoring terminal 60" is simply mentioned, this refers to the monitoring terminal 60 with which the session has been established.
[0087] In Act 32, the processor 21 generates a list screen to be displayed on the monitoring terminal 60, and transmits screen data representing the list screen to the monitoring terminal 60. The list screen represents the operating status of the payment machine 40 and the information terminal 50 as a list, and is a GUI screen for receiving instructions from the attendant M3.
[0088] 21, 22 and 23 are diagrams showing the configuration of the list screen SC2. As shown in Fig. 21, the list screen SC2 has a form in which multiple window areas WA1 are arranged. In the example of Fig. 21, 18 window areas WA1 are arranged in a matrix of 3 columns x 6 rows. Note that in Fig. 21, images shown inside the window areas WA1 are omitted. Then, the processor 21 generates a list screen SC2 by placing a status image IM1 as shown in Figure 22, which shows an outline of the operating status of the payment machine 40, or a status image IM2 as shown in Figure 23, which shows an outline of the operating status of the cart C, in each of the window areas WA1.
[0089] The situation image IM1 includes a string LS1. The situation image IM1 may also include indicators IN1, IN2, IN3, IN4, and IN5. One status image IM1 corresponds to one payment machine 40. The character string LS1 indicates the name of the corresponding payment machine 40. For this reason, the processor 21 makes the character string LS1 different for each of the multiple status images IM1, such as "payment machine 2" or "payment machine 3."
[0090] Indicator IN1 indicates that the corresponding payment machine 40 is calling a store clerk. Indicator IN2 indicates that the corresponding payment machine 40 is in a state where change needs to be replenished. Indicator IN3 indicates that the corresponding payment machine 40 is in a state where change needs to be collected. Indicator IN4 indicates that the corresponding payment machine 40 is waiting for the start of a payment process. Indicator IN5 indicates that the corresponding payment machine 40 is currently performing a payment process.
[0091] The processor 21 appropriately activates the indicators IN1, IN2, and IN3 according to the operation status of the corresponding payment machine 40. The processor 21 activates either the indicator IN4 or IN5 according to the operation status of the corresponding payment machine 40. Specifically, the processor 21 generates a status image IM1 for each of the data records 232R included in the payment machine management database 232. The processor 21 activates the indicator IN1 when "1" is set in the field F44, the indicator IN2 when "1" is set in the field F45, and the indicator IN3 when "1" is set in the field F46. The processor 21 updates the data record 232R so that the fields F44, F45, and F46 represent the current operation status of the payment machine 40 based on the notification from the payment machine 40. The processor 21 also activates the indicator IN4 when the stage set in the field F43 is "idle" and the indicator IN5 when it is "payment in progress". The processor 21 makes the indicators that are not active invisible or displays them in gray.
[0092] The processor 21 arranges the status images IM1 in order from the upper left window area WA1 downwards. That is, if three payment machines 40 are included as shown in Fig. 2, the processor 21 arranges three status images IM1 corresponding to these three payment machines 40 in three window areas WA1 from the upper left to the two below. The processor 21 then arranges status images IM2 corresponding to each of the carts C in the other window areas WA1.
[0093] The situation image IM2 includes character strings LS11 and LS12 and a plurality of icon areas IA11. In the example of Fig. 23, six icon areas IA11 are included. The situation image IM2 may also include indicators IN11, IN12, and IN13. One situation image IM2 corresponds to one cart C. The character string LS11 indicates the name of the corresponding cart C. The processor 21 sets the character string set in the field F32 of the data record 231R associated with the corresponding cart C as the character string LS11. Therefore, the processor 21 makes the character string LS11 different for each of the multiple situation images IM2, such as "TB02" or "TB03". The character string LS12 indicates the member ID of the shopper M1 who logs in from the information terminal 50 provided in the corresponding cart C. The processor 21 generates the character string LS12 by adding the character string indicating the member ID set in the field F34 of the data record 231R associated with the corresponding cart C to the end of the character string "member ID:".
[0094] The icon area IA11 is an area for arranging icons representing the operating status of the corresponding cart C and the information terminal 50 provided in the cart C. When there is a product registered in the dummy list but not registered in the product list, a predetermined warning icon is arranged in one of the icon areas IA11 to indicate that fact. For example, the processor 21 determines that the warning icon should be displayed when the number of fields in which product data is set in the product list does not match the number of fields in which product data or product IDs are set in the dummy list. Note that a description of what other icons are arranged in the icon area IA11 and how they are arranged will be omitted.
[0095] The indicator IN11 indicates that the information terminal 50 provided in the corresponding cart C is in a standby state. The indicator IN12 indicates that the information terminal 50 provided in the corresponding cart C is in a state in which a purchase is being registered. The indicator IN13 indicates that the transaction registered in the information terminal 50 provided in the corresponding cart C is being settled.
[0096] The processor 21 activates one of the indicators IN11, IN12, and IN13 based on the field F35 of the data record 231R associated with the corresponding cart C. Specifically, the processor 21 generates a status image IM2 for each of the data records 231R included in the cart management database 231. The processor 21 then activates the indicator IN11 when the stage set in the field F35 is "waiting", the indicator IN12 when the stage is "registering", and the indicator IN13 when the stage is "checkout". The processor 21 makes the indicators that are not to be activated invisible or grays them out.
[0097] When the screen data showing the list screen as described above is transmitted to the monitoring terminal 60, the processor 61 displays the list screen on the touch panel 65 in accordance with this screen data. This allows the attendant M3 to visually check the list screen and monitor the general status of the payment machine 40 and the carts C. If it becomes necessary to check the details of the purchase registration for any of the carts C, the attendant M3 touches the status image IM2 corresponding to that cart C. In response to this, the processor 61 notifies the second server 20 that the status image IM2 has been touched so that it is possible to identify which status image IM2 has been touched. The display of the list screen SC2 on the monitoring terminal 60 and the notification to the second server 20 that the status image IM2 has been touched can be realized, for example, by the functions of an existing web browser.
[0098] After transmitting the screen data representing the list screen, the processor 21 in the second server 20 proceeds to Act 33. In Act 33, the processor 21 waits for an instruction to display details. Then, in response to the notification that the situation image IM2 has been touched as described above, the processor 21 determines "Yes" in Act 33 and proceeds to Act 34.
[0099] In Act 34, the processor 21 generates a details screen to be displayed on the monitoring terminal 60, and transmits screen data representing the details screen to the monitoring terminal 60. The details screen is a GUI screen that represents in detail the contents of the purchase registration performed on the information terminal 50 provided on one cart C, and is used to receive instructions from the attendant M3.
[0100] Fig. 24 is a diagram showing a details screen. However, Fig. 24 shows a details screen SC3 as an example based on the dummy list L2 shown in Fig. 16 and the product list L3 shown in Fig. 17. In other words, the details screen SC3 is generated when the registration screen SC1 shown in Fig. 18 is displayed on the touch panel 55 of the information terminal 50. In Fig. 24, the same display elements as those shown in Fig. 18 and Fig. 23 are given the same reference numerals, and detailed explanations thereof will be omitted.
[0101] The processor 21 displays the character strings LS11 and LS12, the icon area IA11, and the indicators IN11, IN12, and IN13 displayed in the situation image IM2 touched to instruct the display of details in a line above the details screen SC3 as shown in the figure. The processor 21 displays the icons displayed in the touched situation image IM2 in the icon area IS11 as they are. The processor 21 displays the list TA1 in the center of the details screen SC3. However, the processor 21 does not display the guide message "The cashier will check at the time of payment" on the details screen SC3. The processor 21 arranges the icon areas IA1 in line with each row of the list TA1. The processor 21 displays a warning icon, which is predetermined to indicate that the product ID is not registered in the product database 131, in the icon area IA1 aligned with the row that displays the product ID as the product name. The processor 21 displays a warning icon according to the reason for not allowing the sale in the icon area IA1 aligned with the row corresponding to the product data included in the dummy list L2 and not included in the product list L3. The warning icon is an icon that is predefined to warn of, for example, "expired," "age restriction," or "out of sales period." Thus, by sending such a detailed screen SC3, the monitoring terminal 60 as the notification destination is notified that the product code of the product that is not permitted for sale is stored in the main memory 22 or the auxiliary storage device 23 as the storage means. In other words, the monitoring terminal 60 is the notification destination, and is a terminal different from the information terminal 50 as the first terminal, and corresponds to the second terminal. Thus, the processor 21 executes information processing based on the information processing program, and the computer with the processor 21 as the central part functions as the notification means. The processor 21 places the button BU1 in each row of the list TA1, in a row corresponding to the product data included in the product list L3 and not added with a cancellation flag, or in a row corresponding to the product data or product ID included in the dummy list L2. The processor 21 places the transaction information area AA1 and the buttons BU11 and BU12 below the list TA1 as shown in the figure.In the example of FIG. 24, transaction information area AA1 indicates the total number of registered purchased items, the discount amount for the set discount, and the payment amount for the registered purchased items.
[0102] When the screen data showing the detailed screen SC3 as described above is transmitted to the monitoring terminal 60, the processor 61 displays the detailed screen SC3 on the touch panel 65 in accordance with the screen data. This allows the attendant M3 to visually check the detailed screen SC3 and to confirm in detail the status of the purchase registration at the specified one of the information terminals 50. The attendant M3 can also confirm which products are placed in the cart C for which the purchase registration has not been completed because the sale is not permitted. After confirming these conditions, the attendant M3 speaks to the shopper M1 and takes appropriate measures. For example, the measures are to collect the products placed in the cart C for which the sale is not permitted. For example, the measures are to perform an operation to register the purchase as a genuine sale product. If it is a mistake that the product is not registered in the product database 131 and the sale is actually permitted, the latter measures are appropriate.
[0103] After transmitting the screen data representing the details screen, the processor 21 in the second server 20 proceeds to Act 35. In Act 35, the processor 21 checks whether or not a list display has been instructed. If the instruction has not been given, the processor 21 determines that the answer is No and proceeds to Act 36. In Act 36, the processor 21 checks whether the dummy list referred to when generating the details screen in Act 34 has been updated. If the dummy list has not been updated, the processor 21 determines that the list has not been updated (No) and proceeds to Act 37. In Act 37, the processor 21 checks whether or not a cancellation instruction has been issued. If the instruction has not been issued, the processor 21 determines that the cancellation instruction has been issued as No, and returns to Act 35. Thus, in Act 35 to Act 37, the processor 21 waits for an instruction to display the list, or an instruction to update or cancel the dummy list.
[0104] When the attendant M3 collects a product that is not permitted to be sold, the attendant M3 touches the button BU1 displayed on the detail screen SC3 in association with the product. The attendant M3 can also instruct the cancellation of a product registered as a purchase target in response to a request from the shopper M1 by touching the button BU1 displayed in association with the product. When the attendant M3 collects all of the products that are not permitted to be sold, if multiple products are included, the attendant M3 touches the button BU12 displayed on the detail screen SC3. In response to the touching of the button BU1 or the button BU12, the processor 61 notifies the second server 20 that the cancellation has been instructed, in such a manner that the product IDs of the products to be canceled can be identified. However, when the button BU12 is touched, the processor 61 notifies the second server 20 that the cancellation is to be performed in an identifiable manner, rather than making a specific product ID identifiable. When the processor 21 in the second server 20 receives the notification, the processor 21 judges "Yes" in Act 37 and proceeds to Act 38.
[0105] In Act 38, if an instruction has been given to cancel a product registered as a purchase target, the processor 21 updates the product list in the same manner as in Act 14 in FIG. In Act 39, the processor 21 updates the dummy list to indicate that the process for the product designated for cancellation has been completed.
[0106] Fig. 25 is a schematic diagram showing the data structure of a dummy list after updating due to cancellation. However, Fig. 25 shows the structure of a dummy list L4 as an example when a cancellation instruction is given for a product with the product name "BBB" in a situation where the dummy list is the dummy list L2 shown in Fig. 16. In the dummy list L4 shown in FIG. 25, a field F81 is added after the field F62. The processor 21 sets a cancellation flag in this field F81 to indicate that the product identified by the product ID set in the immediately preceding field F62 has been collected. In this embodiment, the cancellation flag is set to "1". When the cancellation is to be performed in a "lump" manner, the processor 21 adds a cancellation flag after all of the fields in which the product ID is set in the dummy list and the fields in which product data that is included in the dummy list but not in the product list is set. Then, the processor 21 repeats the process from Act 34 onwards. That is, the processor 21 updates the details screen to display the contents of the updated product list and the dummy list, and then returns to the standby state of Act 35-Act 37. As a result, the product ID or product data set in the field immediately preceding the field in which the cancellation flag is set is invalidated. In the registration screen displayed on the information terminal 50, the button BU1 is not displayed in association with a product that is not permitted to be sold. Therefore, a request for invalidation is received from the monitoring terminal 60 as the second terminal, but not from the information terminal 50 as the first terminal. Thus, the processor 21 executes information processing based on the information processing program, and the computer having the processor 21 as the central part functions as an invalidation means. Note that invalidation of the product ID or product data may be performed by deleting the product ID or product data itself.
[0107] The dummy list referred to when generating the details screen in Act 34 may be updated by executing Act 8 in Fig. 13. In this case, the processor 21 judges "Yes" in Act 36 and repeats the process from Act 34 onwards. That is, the processor 21 updates the details screen to show the contents of the updated dummy list, and then returns to the standby mode of Act 35-Act 37.
[0108] When the attendant M3 finishes checking the detail screen and wants to check the list screen again, he / she touches the button BU11. In response to this, the processor 61 notifies the second server 20 that the list display has been instructed. When the processor 21 in the second server 20 receives the notification, it judges "Yes" in Act 35 and returns to Act 32.
[0109] As described above, even if the products to be registered as purchase items include products that are not permitted for sale, shopper M1 can continue with the registration operation without the involvement of a store clerk.
[0110] Since the operation of designating an item that is not permitted for sale as a product to be purchased is not regarded as an error, such an item will be placed on cart C as a purchased item. However, attendant M3 is notified by the display of the details screen on monitoring terminal 60 that an attempt has been made to register an item that is not permitted for sale as a product to be purchased, that is, that such an item may be placed on cart C. This enables attendant M3 to take appropriate measures, such as collecting the item or taking procedures to sell it.
[0111] In addition, all products designated as items to be purchased are registered in a dummy list, and those designated as items to be purchased that are permitted for sale are registered in a separate product list.Then, at the time of checkout, the payment amount is calculated based on the product list.Therefore, products that are not permitted for sale and that are artificially registered only in the dummy list are not subject to checkout, and products that are not permitted for sale because they are not desirable to sell are not sold.
[0112] Furthermore, the registration of an item that is not permitted for sale in the dummy list cannot be cancelled by an instruction from the information terminal 50 by the shopper M1. This ensures that the attendant M3 is notified that an item that is not permitted for sale was present on the sales floor. This enables the attendant M3 to take action such as updating the item database 131 or collecting the item that is not permitted for sale but remains on the sales floor, or to instruct another person to take such action.
[0113] This embodiment can be modified in various ways as follows. All products designated as items to be purchased may be registered in a product list, and each product may be distinguished as to whether it is permitted for sale or not by managing the product list using, for example, a flag.
[0114] At least one of the product list and the dummy list may be stored in the main memory 52 or the auxiliary storage device 53 provided in the information terminal 50, for example.
[0115] At least one of the product list and the dummy list may be generated and updated by a processor 51 provided in the information terminal 50.
[0116] The processor 51 in the information terminal 50 may obtain the product list and the dummy list from the second server 20, and then generate the registration screen.
[0117] The processor 61 in the monitoring terminal 60 may obtain the product list and the dummy list from the second server 20, and then generate a details screen.
[0118] Each type of data record may have additional fields added or may omit some fields.
[0119] The information terminal 50 may be hand-held by the shopper M1 without being attached to the cart C. Furthermore, the information terminal 50 may not be installed in the store, but may be a terminal such as a smartphone carried by the shopper M1.
[0120] The processor 21 may instruct the monitoring terminal 60 to execute an alarm action when the product list transmitted as Act 23 in Fig. 19 is paired with a dummy list in which products not permitted for sale are registered. In this case, the monitoring terminal 60 executes an alarm action such as outputting an alarm sound in response to the instruction. In this way, even if the attendant M3 is too busy to fully check the list screen and the details screen, it is possible to make the attendant M3 recognize that it is necessary to take the above-mentioned measures.
[0121] The list screen and the details screen may be displayed on the POS terminal 30 or any other terminal. In other words, the notification destination is not limited to the monitoring terminal 60 installed at the attendant counter AT, and may be any terminal installed at any location.
[0122] The method of distinguishing whether or not the sale of a product identified by a product ID included in the dummy list is permitted can be changed as desired. For example, the dummy list may include product data for products permitted for sale, and may include only product IDs for products not permitted for sale. Alternatively, a flag indicating whether or not the sale is permitted may be set in association with each product ID included in the dummy list. In these cases, product data for products permitted for sale may be extracted from the dummy list, without creating a separate product list, and accounting may be performed based on the corresponding product data.
[0123] The method for making it possible to confirm whether or not the sale of each product is permitted on the details screen can be changed as desired. For example, the product name may be displayed for products that are permitted for sale, and the product ID may be displayed for products that are not permitted for sale. Also, for example, the display color may be changed depending on whether or not the product is permitted for sale.
[0124] Each function realized by the processor 21 through information processing can be realized in part or in whole by hardware that executes information processing not based on a program, such as a logic circuit, etc. Also, each of the above functions can be realized by combining the above hardware, such as the logic circuit, with software control.
[0125] Although some embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included in the scope and spirit of the invention, and are included in the scope of the invention and its equivalents described in the claims. The invention as originally claimed in the present application is set forth below. [Appendix 1] A storage means for storing a list including a product identifier for identifying a product that a purchaser has decided to purchase, regardless of whether the sale of the product identified by the product identifier is permitted or not, and capable of distinguishing whether the sale of the product identified by the product identifier is permitted or not; a notification means for notifying a predetermined notification destination when a product code of a product that is not permitted to be sold is included in the list stored by the storage means; A product sales system equipped with the above. [Supplementary Note 2] The storage means stores a first list including the product identifier only when the sale of the product identified by the product identifier is permitted, and a second list including the product identifier regardless of whether the sale of the product identified by the product identifier is permitted. Item 1. A product sales system as described in appendix 1. [Appendix 3] Accounting means for accounting for the transaction price based on said first list; The product sales system according to claim 2, further comprising: [Appendix 4] The storage means stores the product identifier acquired by the first terminal; The notification means sets a second terminal other than the first terminal as the notification destination. A product sales system described in any one of Appendix 1 to Appendix 3. [Appendix 5] An invalidation means for invalidating the product identifiers that identify products that are not permitted to be sold among the product identifiers stored in the storage means in response to a request from the second terminal, and not accepting a request from the first terminal regarding the invalidation; The product sales system according to claim 4, further comprising: [Explanation of symbols]
[0126] 10...first server, 20...second server, 30...POS terminal, 40...accounting machine, 50...information terminal, 60...monitoring terminal, 70...network, 80...access point, 100...product sales system, 11,21,51,61...processor, 12,22,52,62...main memory, 13,23,53,63...auxiliary storage device, 14,24...communication interface, 15,25,58,66...system transmission path, 54,64...wireless unit, 55,65...touch panel, 56...scanner, 57...reader, 131...product database, 132...membership database, 133...sales promotion database, 231...cart management database, 232...accounting machine management database.
Claims
1. A product sales system comprising: an information terminal having an input means for inputting identification information for identifying a product and a first display; and a server capable of communicating with the information terminal, The server, a first control means for generating a registration screen for displaying on the first display device a registration screen including a list of first information items that have been successfully acquired, the registration screen being generated each time identification information is input by the input means while the customer is walking around the sales floor, the first control means being configured to attempt to acquire first information items related to the product identified by the identification information, the registration screen including a list of first information items that have been successfully acquired; a first reception means for receiving a cancellation instruction from a customer regarding the first information displayed in the list included in the registration screen displayed on the first display device; a second control means for generating, when the first reception means receives a cancellation instruction, a registration screen in which second information indicating that the cancellation instruction has been received has been added to the target of the cancellation instruction in the list included in the registration screen displayed on the first display; a third control means for generating a screen to be displayed on a second display provided on a monitoring terminal other than the information terminal, the screen including third information indicating that the sale of the product is not permitted and the first information and second information included in the list included in the registration screen displayed on the first display when it is determined from first information related to the product identified by the identification information input by the input means that the sale of the product is not permitted; a second reception means for receiving a cancellation instruction from a store clerk regarding third information included in the screen displayed on the second display; a fourth control means for updating the screen displayed on the second display when a cancellation instruction is received by the second reception means; A product sales system equipped with the above.
2. the input means inputs the identification information for identifying a commodity in response to the customer's operation on the information terminal while walking around the sales floor, even if the first control means is unable to acquire first information relating to a commodity identified by the already input identification information and the second acceptance means has not accepted a cancellation instruction from a store clerk relating to third information relating to the commodity for which the first information has not been acquired; The product sales system according to claim 1.
3. the third information included in the screen displayed on the second display device includes the identification information input by the input means and information indicating that the first information related to the product identified by the identification information could not be acquired; The product sales system according to claim 1 or 2.
4. the second reception means receives a cancellation instruction related to third information included in the screen displayed on the second display device by an operation of the monitoring terminal; The product sales system according to any one of claims 1 to 3.
5. The server, a fifth control means for not receiving, from the information terminal, a cancellation instruction regarding the third information displayed on the second display; The product sales system according to claim 1 , further comprising:
6. when the first control means determines, from the first information related to the product identified by the identification information input by the input means, that the sale of the product is not permitted, the first control means includes third information in the registration screen, and does not include an operator for instructing the cancellation of the third information in the registration screen, thereby making it impossible for the customer to cancel the third information while being able to input identification information while walking around the sales floor. The product sales system according to any one of claims 1 to 5.
7. The first information includes a product name and a price, The second information is a strikethrough that cancels a character string representing the product name and price. The product sales system according to any one of claims 1 to 6.
8. the first reception means displays an operator associated with each of the first information included in the list included in the registration screen generated by the first control means, and receives a cancellation instruction related to the first information associated with the operated operator. The product sales system according to any one of claims 1 to 7.
9. A server capable of communicating with an information terminal having an input means for inputting identification information for identifying a product and a first display, a first control means for generating a registration screen for displaying on the first display device a registration screen including a list of first information items that have been successfully acquired, the registration screen being generated each time identification information is input by the input means while the customer is walking around the sales floor, the first control means being configured to attempt to acquire first information items related to the product identified by the identification information, the registration screen including a list of first information items that have been successfully acquired; a first reception means for receiving a cancellation instruction from a customer regarding the first information displayed in the list included in the registration screen displayed on the first display device; a second control means for generating, when the first reception means receives a cancellation instruction, a registration screen in which second information indicating that the cancellation instruction has been received has been added to the target of the cancellation instruction in the list included in the registration screen displayed on the first display; a third control means for generating a screen to be displayed on a second display provided on a monitoring terminal other than the information terminal, the screen including third information indicating that the sale of the product is not permitted and the first information and second information included in the list included in the registration screen displayed on the first display when it is determined from first information related to the product identified by the identification information input by the input means that the sale of the product is not permitted; a second reception means for receiving a cancellation instruction from a store clerk regarding third information included in the screen displayed on the second display; a fourth control means for updating the screen displayed on the second display when a cancellation instruction is received by the second reception means; A server equipped with
10. An information processing method using an information terminal having an input means for inputting identification information for identifying a product and a first display, and a computer provided in a server capable of communicating with the information terminal, comprising: each time identification information is input by the input means while the customer is going around the sales floor, an attempt is made to acquire first information related to the product identified by the identification information, and a registration screen including a list of the acquired first information is generated to be displayed on the first display; accepting a cancellation instruction from a customer regarding the first information displayed in the list included in the registration screen displayed on the first display; when a cancel instruction regarding first information is received, a registration screen is generated in which second information indicating that the information has been canceled is added to the target of the cancel instruction in the list included in the registration screen displayed on the first display device; when it is determined from first information related to a product identified by the identification information input by said input means that the sale of said product is not permitted, a screen is generated to be displayed on a second display provided on a monitoring terminal separate from said information terminal, said screen including third information indicating that the sale of said product is not permitted and the first information and second information included in the list included in said registration screen displayed on said first display; receiving a cancellation instruction from a store clerk regarding third information included in the screen displayed on the second display device; when a cancel instruction regarding the third information is received, updating the screen displayed on the second display device; Information processing methods.
11. A computer provided in a server capable of communicating with an information terminal having an input means for inputting identification information for identifying a product and a first display device, a first control means for generating a registration screen for displaying on the first display device a registration screen including a list of first information items that have been successfully acquired, the registration screen being generated each time identification information is input by the input means while the customer is walking around the sales floor, the first control means being configured to attempt to acquire first information items related to the product identified by the identification information, the registration screen including a list of first information items that have been successfully acquired; a first reception means for receiving a cancellation instruction from a customer regarding the first information displayed in the list included in the registration screen displayed on the first display device; a second control means for generating, when the first reception means receives a cancellation instruction, a registration screen in which second information indicating that the cancellation instruction has been received has been added to the target of the cancellation instruction in the list included in the registration screen displayed on the first display; a third control means for generating a screen to be displayed on a second display provided on a monitoring terminal other than the information terminal, the screen including third information indicating that the sale of the product is not permitted and the first information and second information included in the list included in the registration screen displayed on the first display when it is determined from first information related to the product identified by the identification information input by the input means that the sale of the product is not permitted; a second reception means for receiving a cancellation instruction from a store clerk regarding third information included in the screen displayed on the second display; a fourth control means for updating the screen displayed on the second display when a cancellation instruction is received by the second reception means; An information processing program that enables the system to function as such.
Citation Information
Patent Citations
Pos system provided with self-retrieving function
JP1995065239A
Pos system
JP1995152963A
Sales support apparatus, sales support system, commodity cart, and sales support method
JP2011108010A
