Monitoring terminal and its program

Abstract

To reduce a load on a server, even if there is an error in data input via a mobile terminal, by correcting the error without discarding the data.SOLUTION: A store system includes a server and a store terminal. The server receives data based on purchased commodities input in a plurality of mobile terminals. The server stores the received data based on the purchased commodities. The store terminal acquires, from the stored data, the data based on the purchased commodity input in any one of the mobile terminals. The store terminal instructs correction of the acquired data. The server executes the instructed correction concerning the data to be stored.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present embodiment relates to a store system. [Background technology]

[0002] There is a store system that simplifies the input operation of data at the time of payment by having consumers operate a mobile terminal to input data based on the purchased item. However, the data input via a mobile terminal is not always correct. For example, an item may be registered with a selling price different from that on the price tag, or the set discount may not be applied correctly. In such cases, in the current store system, the data input via the mobile terminal is discarded. The data is re-entered into the payment machine by a store clerk. At this time, the store clerk performs processing such as changing the selling price and setting the discount amount for the erroneous data. Conventionally, this was done, and the load on the server required to process the data input via the mobile terminal was wasted. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2017-117299 A Summary of the Invention [Problem to be solved by the invention]

[0004] The problem that the embodiment of the present invention aims to solve is to provide a store system that can correct errors in data entered via a mobile terminal without discarding the data, thereby reducing the load on the server for data processing. [Means for solving the problem]

[0005] In one embodiment, the store system includes a server and a store terminal. The server has a receiving means, a storage means, and a correction means. The receiving means receives data based on purchased items input by each of a plurality of mobile terminals. The storage means stores the data based on the purchased items received by the receiving means. The correction means executes corrections to the data stored by the storage means as instructed by a correction instruction means described below. The store terminal has an acquiring means and a correction instruction means. The acquiring means acquires data based on the purchased items input by any of the mobile terminals from the data stored in the storage means. The correction instruction means instructs correction of the data acquired by the acquiring means. [Brief description of the drawings]

[0006] [Figure 1] FIG. 1 is a block diagram illustrating an embodiment of a store system. [Diagram 2] FIG. 2 is a block diagram showing the main circuit configuration of a mobile terminal. [Diagram 3] FIG. 2 is a block diagram showing a main circuit configuration of a monitoring terminal. [Figure 4] FIG. 2 is a block diagram showing the main circuit configuration of a virtual POS server. [Diagram 5] FIG. 2 is a block diagram showing the main circuit configuration of a terminal controller. [Figure 6] FIG. 4 is a schematic diagram showing the data structure of a transaction information file. [Figure 7] FIG. 4 is a schematic diagram showing the data structure of a mobile information file. [Figure 8] 1 is a flowchart showing the main information processing steps executed by a processor of a mobile terminal. [Figure 9] 11 is a flowchart showing the procedure of a usage start notification command receiving process executed by a processor of the terminal controller; [Figure 10] 11 is a flowchart showing the procedure of a product registration notification command receiving process executed by a processor of the terminal controller. [Figure 11] 11 is a flowchart showing the procedure of accounting notification command reception processing executed by the processor of the terminal controller. [Figure 12]11 is a flowchart showing the procedure of a usage start request command receiving process executed by a processor of the virtual POS server; [Figure 13] 11 is a flowchart showing a procedure of a product registration request command receiving process executed by a processor of the virtual POS server; [Figure 14] 11 is a flowchart showing the procedure of a transaction request command receiving process executed by a processor of the virtual POS server. [Figure 15] 4 is a flowchart showing a procedure of main information processing executed by a processor of the monitoring terminal. [Figure 16] 4 is a flowchart showing a procedure of main information processing executed by a processor of the monitoring terminal. [Figure 17] 4 is a flowchart showing a procedure of main information processing executed by a processor of the monitoring terminal. [Figure 18] 11 is a flowchart showing the procedure of a modification notification command receiving process executed by a processor of the terminal controller; [Figure 19] 11 is a flowchart showing the procedure of a modification request command receiving process executed by a processor of the virtual POS server. [Figure 20] FIG. 13 is a diagram showing an example of a monitoring screen displayed on a mobile terminal. [Figure 21] FIG. 4 is a diagram showing an example of a status display section displayed on a mobile terminal. [Figure 22] FIG. 13 is a diagram showing an example of an image including a list displayed on a mobile terminal. [Diagram 23] FIG. 13 is a diagram showing an example of an edit pop-up image displayed on a mobile terminal. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0007] Hereinafter, an embodiment of a store system will be described with reference to the drawings. In this embodiment, a store system is exemplified in which a consumer using a shopping cart operates a mobile terminal attached to the cart to input data based on purchased items.

[0008] 1 is a block diagram showing an outline of an embodiment of a store system 100. The store system 100 includes a store server 10, a virtual POS server 20, a payment machine 30, a terminal controller 40, an access point 50, a mobile terminal 60, a monitoring terminal 70, and a communication network 80. The communication network 80 is a wired LAN (Local Area Network). In other words, the store server 10, the virtual POS server 20, the payment machine 30, the terminal controller 40, and the access point 50 are each connected to a communication cable to form the communication network 80. The communication network 80 may be a wireless LAN.

[0009] The access point 50 is a device that constitutes a wireless LAN together with the mobile terminal 60 and the monitoring terminal 70. The access point 50 serves as a relay point for data exchanged between the mobile terminal 60 or the monitoring terminal 70 connected via the wireless LAN and each device connected via the wired LAN. The number of access points 50 is not limited to one. Two or more access points 50 may be connected to the communication network 80, taking into consideration the size, layout, etc. of the store.

[0010] The mobile terminal 60 is a portable electronic device for supporting the shopping behavior of a consumer in a store in which the store system 100 is configured. The mobile terminal 60 is typically operated by a consumer. The mobile terminal 60 is attached to, for example, a shopping cart when used. The mobile terminal 60 may be lent to a consumer by the store and carried by the consumer. The mobile terminal 60 may also be an information terminal such as a smartphone or tablet terminal owned by the consumer.

[0011] 2 is a block diagram showing the main circuit configuration of the mobile terminal 60. The mobile terminal 60 includes a processor 61, a main memory 62, an auxiliary storage device 63, a wireless device 64, a touch panel 65, a scanner 66, and a system transmission path 67. The system transmission path 67 includes an address bus, a data bus, a control signal line, and the like. The mobile terminal 60 connects the processor 61, the main memory 62, the auxiliary storage device 63, the wireless device 64, the touch panel 65, and the scanner 66 to the system transmission path 67. In the mobile terminal 60, the processor 61, the main memory 62, the auxiliary storage device 63, and the system transmission path 67 that connects them together constitute a computer.

[0012] The processor 61 corresponds to the central part of the computer. The processor 61 controls each part to realize various functions of the mobile terminal 60 according to an operating system or an application program. The processor 61 is, for example, a CPU (Central Processing Unit).

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

[0014] The auxiliary storage device 63 corresponds to the auxiliary storage portion of the computer. For example, an EEPROM (Electric Erasable Programmable Read-Only Memory), an HDD (Hard Disc Drive), or an SSD (Solid State Drive) can be the auxiliary storage device 63. The auxiliary storage device 63 stores data used by the processor 61 in performing various processes, or data created by the processes in the processor 61. The auxiliary storage device 63 may also store the application programs described above.

[0015] The wireless device 64 is a device for wirelessly communicating data with the access point 50 via a wireless LAN.

[0016] The touch panel 65 is a device that functions as both an input device and a display device for the mobile terminal 60. The touch panel 65 displays various images. The touch panel 65 detects a touch position on the displayed image and outputs the touch position information to the processor 61.

[0017] The scanner 66 is a device used to read barcodes. The scanner 66 may be a device that optically reads barcodes by scanning with laser light, or may be a device that reads barcodes by processing an image including the barcode captured by a camera.

[0018] The mobile terminal 60 has installed the shopping support program APL1 in the auxiliary storage device 63 as a type of application program. The method for installing the shopping support program APL1 in the auxiliary storage device 63 is not particularly limited. The shopping support program APL1 can be recorded on a removable recording medium, or distributed by communication via a network, and installed in the auxiliary storage device 63. The recording medium may be in any form, such as a CD-ROM or memory card, as long as it can store a program and is readable by the device. The shopping support program APL1 may be installed in the main memory 62.

[0019] The monitoring terminal 70 is an electronic device for monitoring the operating state of the mobile terminal 60. The monitoring terminal 70 may monitor the operating state of the payment machine 30 together with the mobile terminal 60. The monitoring terminal 70 is typically operated by a store clerk called an attendant. The monitoring terminal 70 is used by being placed at a location where the attendant waits. The monitoring terminal 70 may be a portable electronic device that the attendant can take out. The monitoring terminal 70 is an example of a store terminal.

[0020] 3 is a block diagram showing the main circuit configuration of the monitoring terminal 70. The monitoring terminal 70 includes a processor 71, a main memory 72, an auxiliary storage device 73, a wireless device 74, a touch panel 75, a scanner 76, and a system transmission path 77. The system transmission path 77 includes an address bus, a data bus, a control signal line, and the like. The monitoring terminal 70 connects the processor 71, the main memory 72, the auxiliary storage device 73, the wireless device 74, the touch panel 75, and the scanner 76 to the system transmission path 77. In the monitoring terminal 70, the processor 71, the main memory 72, the auxiliary storage device 73, and the system transmission path 77 that connects them together constitute a computer.

[0021] The explanations for the processor 71, main memory 72, auxiliary memory device 73, wireless device 74, touch panel 75 and scanner 76 overlap with the explanations for the processor 61, main memory 62, auxiliary memory device 63, wireless device 64, touch panel 65 and scanner 66 for the mobile terminal 60, so they will not be explained here.

[0022] The monitoring terminal 70 has the monitoring assistance program APL2 installed in the auxiliary storage device 73 as one type of application program. The method of installing the monitoring assistance program APL2 in the auxiliary storage device 73 is not particularly limited. The same method as that for the shopping assistance program APL1 can be applied as is. The monitoring assistance program APL2 may be installed in the main memory 72.

[0023] The accounting machine 30 is a terminal for settling commercial transactions with consumers. The accounting machine 30 obtains accounting data for commercial transactions from the virtual POS server 20 and settles the commercial transactions based on the accounting data. The accounting machine 30 can settle commercial transactions using well-known payment methods such as cash payment, credit card payment, electronic money payment, points payment, and code payment (also called mobile payment or smartphone payment, etc.).

[0024] The payment machine 30 may be a manned payment machine in which a store clerk inputs payment information, or a self-service payment machine in which a consumer inputs payment information. The store system 100 may be equipped with both manned and self-service payment machines, or may be equipped with only one of them. A conventionally known POS terminal may be used as the manned payment machine. A conventionally known self-service or semi-self-service payment machine may be used as the self-service payment machine.

[0025] The store server 10 supports the overall operation of the store. To support this, the store server 10 manages various databases such as a product database, a membership database, and the like.

[0026] A product database is a collection of product records that describe data on each product sold in a store. A product record is made up of data items such as product code, product name, price, and discount information. A product code is a unique identification code assigned to each product in order to identify each product individually. Each product is affixed with a barcode that indicates the product code. Discount information is information related to product discounts, such as the discount amount and discount rate.

[0027] The membership database is a collection of membership records that describe data on consumers who have registered as point members, etc., i.e., so-called members. Membership records include data items such as a membership code and accumulated points. A membership code is a unique identification code assigned to each member in order to identify each member. Accumulated points are the accumulated points given to a consumer member in commercial transactions with that member.

[0028] The virtual POS server 20 cooperates with the mobile terminal 60 to support the operation of a known POS terminal. That is, the virtual POS server 20 performs registration processing of purchased items based on data input from the touch panel 65 or scanner 66 of the mobile terminal 60. The data of purchased items registered by the virtual POS server 20 is displayed on the touch panel 65 of the mobile terminal 60.

[0029] 4 is a block diagram showing the main circuit configuration of the virtual POS server 20. The virtual POS 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. The virtual POS server 20 connects the processor 21, the main memory 22, the auxiliary storage device 23, and the communication interface 24 to the system transmission path 25. In the virtual POS server 20, a computer is configured by the processor 21, the main memory 22, the auxiliary storage device 23, and the system transmission path 25 that connects them.

[0030] The explanations for the processor 21, main memory 22, and auxiliary storage device 23 overlap with the explanations for the processor 61, main memory 62, and auxiliary storage device 63 for the mobile terminal 60, and therefore will not be repeated here.

[0031] The communication interface 24 is a circuit for performing data communication between each unit connected via the communication network 80 .

[0032] The virtual POS server 20 configured as above forms a storage area for storing a plurality of transaction information files TFL in the auxiliary storage device 23. The data structure of the transaction information file TFL will be described later.

[0033] The terminal controller 40 controls the operation of the mobile terminal 60 and the monitoring terminal 70, which are connected by wireless LAN via the access point 50. The terminal controller 40 causes the mobile terminal 60 to function as an input / output interface of a POS terminal by sending and receiving data commands to and from the mobile terminal 60 on which the shopping support program APL1 is executed. The terminal controller 40 causes the monitoring terminal 70 to function as a status monitoring device for the mobile terminal 60 by sending and receiving data commands to and from the monitoring terminal 70 on which the monitoring support program APL2 is executed.

[0034] 5 is a block diagram showing the main circuit configuration of the terminal controller 40. The terminal controller 40 includes a processor 41, a main memory 42, an auxiliary storage device 43, a communication interface 44, and a system transmission path 45. The system transmission path 45 includes an address bus, a data bus, a control signal line, and the like. The terminal controller 40 connects the processor 41, the main memory 42, the auxiliary storage device 43, and the communication interface 44 to the system transmission path 45. In the terminal controller 40, the processor 41, the main memory 42, the auxiliary storage device 43, and the system transmission path 45 that connects them together constitute a computer.

[0035] The explanation of the processor 41, main memory 42, and auxiliary storage device 43 overlaps with the explanation of the processor 61, main memory 62, and auxiliary storage device 63 for the mobile terminal 60, so the explanation will be omitted here.

[0036] The communication interface 44 is a circuit for performing data communication between each unit connected via the communication network 80 .

[0037] The terminal controller 40 thus configured forms a storage area for saving a plurality of mobile information files MFL in the auxiliary storage device 23. The data structure of the mobile information file MFL will be described later.

[0038] FIG. 6 is a schematic diagram showing the data structure of the transaction information file TFL. As shown in the figure, the transaction information file TFL is composed of an area A1 for writing a terminal ID, an area A2 for storing multiple registration data, and an area A3 for storing a first status S1. The terminal ID is a unique code set in the main memory 62 or the auxiliary storage device 63 to individually identify each mobile terminal 60. The registration data is normal registration data. The normal registration data is composed of data items such as product code, product name, price, number of items, discount amount, and error flag. The error flag is "0". The first status S1 is information for identifying the state of the transaction information file TFL. The states of the transaction information file TFL include a first state before the start of product registration, a second state after the start of product registration, a third state after the declaration of checkout, and a fourth state after the end of checkout. In this embodiment, the first status S1 representing the first state is set to "0", the first status S1 representing the second state is set to "1", the first status S1 representing the third state is set to "2", and the first status S1 representing the fourth state is set to "3".

[0039] FIG. 7 is a schematic diagram showing the data structure of the mobile information file MFL. As shown in the figure, the mobile information file MFL is composed of an area B1 for writing a terminal ID, an area B2 for storing a plurality of registration data, and an area B3 for storing a second status S2. The registration data includes error registration data in addition to the normal registration data described above. The error registration data is composed of barcode data and each item data of an error flag. The error flag is "1". The second status S2 is information for identifying the state of the mobile information file MFL. The state of the mobile information file MFL also has first to fourth states, similar to the transaction information file TFL. In this embodiment, the second status S2 representing the first state is set to "0", the second status S2 representing the second state is set to "1", the second status S2 representing the third state is set to "2", and the second status S2 representing the fourth state is set to "3".

[0040] FIG. 8 is a flow chart showing the main information processing procedure executed by the processor 61 of the mobile terminal 60 according to the shopping support program APL1. FIG. 9 to FIG. 11 are flow charts showing the information processing procedure executed by the processor 41 of the terminal controller 40 in response to the information processing of the mobile terminal 60. FIG. 12 to FIG. 14 are flow charts showing the information processing procedure executed by the processor 21 of the virtual POS server 20 in response to the information processing of the terminal controller 40. Hereinafter, using these flow charts, the operation of the store system 100 from when a consumer uses the mobile terminal 60 to input data based on the purchased item to when the purchase of the purchased item is completed will be described. Note that the operation described below is an example. The procedure is not particularly limited as long as the same result is obtained.

[0041] First, a consumer starts up the mobile terminal 60 before starting shopping. The mobile terminal 60 is attached to, for example, a shopping cart. When the mobile terminal 60 starts up, the processor 61 starts information processing of the procedure shown in the flowchart of FIG. 8. The processor 61 waits for a declaration of start of use as ACT101. For example, the processor 61 causes the touch panel 65 to display a start shopping button. The processor 61 then waits for the start shopping button to be touched.

[0042] The consumer touches the shopping start button. In response to this touch input, the processor 61 determines YES in ACT101 and proceeds to ACT102. The processor 61 controls the wireless device 64 to perform a start-of-use notification in ACT102. This control causes the wireless device 64 to wirelessly transmit a start-of-use notification command. The start-of-use notification command is received by the access point 50 connected by wireless LAN, and transmitted to the terminal controller 40 via the communication network 80. The start-of-use notification command includes the terminal ID set in the mobile terminal 60.

[0043] When the processor 41 of the terminal controller 40 receives the start-of-use notification command via the communication interface 44, it starts information processing according to the procedure shown in the flowchart of Fig. 9. The processor 41 controls the communication interface 44 to make a start-of-use request as ACT201. This control causes the communication interface 44 to output the start-of-use request command. The start-of-use request command is transmitted to the virtual POS server 20 via the communication network 80. The start-of-use request command includes the terminal ID detected from the start-of-use notification command.

[0044] When the processor 21 of the virtual POS server 20 receives the start-of-use request command via the communication interface 24, it starts information processing according to the procedure shown in the flowchart of Fig. 12. The processor 21 detects the terminal ID from the start-of-use request command in ACT 301. Then, the processor 21 determines whether the mobile terminal 60 identified by the terminal ID can be used in ACT 302.

[0045] Specifically, the processor 21 searches the transaction information file TFL for a transaction information file TFL in which the terminal ID is set in area A1 and the first status S1 is other than "3". A transaction information file TFL in which the first status S1 is other than "3" corresponds to a mobile terminal 60 for which a declaration of start of use has been made but the transaction has not been completed. Therefore, if a corresponding transaction information file TFL is detected, the processor 21 determines that the mobile terminal 60 cannot be used. If a corresponding transaction information file TFL cannot be detected, the processor 21 determines that the mobile terminal 60 can be used.

[0046] When it is determined that the mobile terminal 60 is unavailable, the processor 21 determines NO in ACT 302 and proceeds to ACT 303. In ACT 303, the processor 21 controls the communication interface 24 to send a rejection response.

[0047] If it is determined that the mobile terminal 60 is usable, the processor 21 determines YES in ACT302 and proceeds to ACT304. The processor 21 creates a transaction information file TFL in the auxiliary storage device 23 in ACT304. Then, the processor 21 sets the terminal ID detected from the usage start request command in area A1 of the transaction information file TFL in ACT305. The processor 21 also sets the first status S1 of the transaction information file TFL to "0" in ACT306. Furthermore, the processor 21 controls the communication interface 24 to send an authorization response in ACT307.

[0048] Under the control of ACT303 or ACT307, a refusal response command or a permission response command is output from the communication interface 24. The refusal response command or the permission response command is transmitted to the terminal controller 40 via the communication network 80. The refusal response command or the permission response command includes the terminal ID detected from the start-of-use request command.

[0049] Returning to the explanation of Figure 9. The processor 41 of the terminal controller 40 that has made the usage start request waits for a permission response command in ACT 202. If a refusal response command is received via the communication interface 204, the processor 41 judges NO in ACT 202 and proceeds to ACT 203. The processor 41 controls the communication interface 44 to send a refusal notice in ACT 203.

[0050] On the other hand, if a permission response command is received, the processor 41 determines YES in ACT202 and proceeds to ACT204. The processor 41 creates a mobile information file MFL in the auxiliary storage device 43 in ACT204. Then, the processor 41 sets the terminal ID detected from the permission response command in area B1 of the mobile information file MFL in ACT205. The processor 41 also sets the second status S2 of the mobile information file MFL to "0" in ACT206. Furthermore, the processor 41 controls the communication interface 44 to issue a permission notification in ACT207.

[0051] Under the control of ACT203 or ACT207, a rejection notification command or a permission notification command is output from the communication interface 44. The rejection notification command or the permission notification command is wirelessly transmitted from the access point 50 via the communication network 80. The rejection notification command or the permission notification command includes the terminal ID detected from the rejection response command or the permission response command. The rejection notification command or the permission notification command wirelessly transmitted from the access point 50 is received by the mobile terminal 60 in which the terminal ID included in the command is set.

[0052] Returning to the explanation of Figure 8. The processor 61 of the mobile terminal 60 that issued the usage start notification waits for a permission notification command in ACT103. If a rejection notification command is received via the wireless device 64, the processor 61 determines NO in ACT103. The processor 61 ends the processing for the usage start declaration as an error. Therefore, the consumer cannot use the mobile terminal 60. For example, the consumer replaces the shopping cart and issues a usage start declaration to the mobile terminal 60 of the replaced cart.

[0053] On the other hand, if a permission notification command is received, the processor 61 determines YES in ACT103 and proceeds to ACT104. The processor 61 displays a registration screen on the touch panel 65 in ACT104. The registration screen has a details area for displaying the product name, price, number, discount amount, etc. of the purchased product, and a total area for displaying the total number of purchased products, total amount, etc. The registration screen also displays a checkout button that allows the consumer to declare a move to checkout. The checkout button is an example of an operator reproduced on the screen of the touch panel 65 by software. The layout of the registration screen is not particularly limited.

[0054] The processor 61 of the mobile terminal 60 that has displayed the registration screen determines whether or not product registration has been accepted in ACT105. If product registration has not been accepted, the processor 61 determines NO in ACT105 and proceeds to ACT106. The processor 61 checks whether or not an update notification command has been received in ACT106. If an update notification command has not been received, the processor 61 determines NO in ACT106 and proceeds to ACT107. The processor 61 checks whether or not an accounting declaration has been accepted in ACT107. If an accounting declaration has not been accepted, the processor 61 determines NO in ACT107 and returns to ACT105. Here, the processor 61 waits in ACT105 to ACT107 for product registration to be performed, for an update notification command to be received, or for an accounting declaration to be made.

[0055] After checking the registration screen, each time a consumer purchases an item at the sales floor, the consumer has the bar code of the purchased item read by the scanner 66 and then places the item in the shopping cart.

[0056] When the barcode is read by the scanner 66, the processor 61, which is in a standby state in ACT105 to ACT107, determines that the product has been registered. The processor 61 determines YES in ACT105 and proceeds to ACT108. The processor 61 controls the wireless device 64 to perform a product registration notification in ACT108. By this control, a product registration notification command is wirelessly transmitted from the wireless device 64. The product registration notification command is transmitted to the terminal controller 40 via the access point 50. The product registration notification command includes the data of the barcode read by the scanner 66 and the terminal ID of the mobile terminal 60.

[0057] When the processor 41 of the terminal controller 40 receives a product registration notification command via the communication interface 44, it starts information processing of the procedure shown in the flowchart of Fig. 10. The processor 41 detects the terminal ID from the product registration notification command in ACT211. Then, the processor 41 checks whether the second status S2 of the mobile information file MFL in which the terminal ID is set is "0" or "1" in ACT212. If the second status S2 of the mobile information file MFL is other than "0" or "1", the processor 41 judges NO in ACT212. The processor 41 ends the processing for the product registration notification as an error.

[0058] If the second status S2 of the mobile information file MFL is "0" or "1", the processor 41 determines YES in ACT212 and proceeds to ACT213. The processor 41 controls the communication interface 44 to make a product registration request in ACT213. This control causes the communication interface 44 to output a product registration request command. The product registration request command is transmitted to the virtual POS server 20 via the communication network 80. The product registration request command includes the barcode data and the terminal ID detected from the product registration notification command. In the following, the mobile information file MFL whose second status S2 is "0" or "1" is referred to as a registered mobile information file MFL1.

[0059] When the processor 21 of the virtual POS server 20 receives a product registration request command via the communication interface 24, it starts information processing according to the procedure shown in the flow chart of Fig. 13. The processor 21 detects the terminal ID from the product registration request command in ACT311. Then, the processor 21 checks whether the first status S1 of the transaction information file TFL in which the terminal ID is set is "0" or "1" in ACT312. If the first status S1 of the transaction information file TFL is other than "0" or "1", the processor 21 judges NO in ACT312. The processor 21 ends the processing for the product registration request as an error.

[0060] If the first status S1 of the transaction information file TFL is "0" or "1", the processor 21 judges YES in ACT312 and proceeds to ACT313. In ACT313, the processor 21 queries the store server 10 for product data using the barcode data detected from the product registration request command. In the following, the transaction information file TFL with the first status S1 of "0" or "1" is referred to as the registered transaction information file TFL1.

[0061] In response to the inquiry about product data, the processor 11 of the store server 10 checks whether the barcode data is a product code. If it is a product code, the processor 11 searches the product database for that product code. If the processor 11 finds a product record that includes that product code, it sends a normal response command to the virtual POS server 20. The normal response command includes product data such as the product code, product name, price, and discount information that constitute the product record.

[0062] On the other hand, if the corresponding product record cannot be found after searching the product database, or if the barcode data is not a product code, the processor 11 sends an error response command to the virtual POS server 20. In addition to the product code barcode, a product may have a barcode attached thereto to identify, for example, the manufacturer or manufacturing company. If a consumer mistakenly reads such a barcode, the processor 11 sends an error response command to the virtual POS server 20. The error response command includes the barcode data detected from the product registration request command.

[0063] The processor 21 of the virtual POS server 20 that made the inquiry about the product data waits for a normal response command in ACT314. If an error response command is received via the communication interface 24, the processor 21 judges NO in ACT314 and proceeds to ACT315. The processor 21 generates error registration data in ACT315. The error registration data includes the barcode data detected from the error response command and an error flag of "1". After generating the error registration data, the processor 21 proceeds to ACT320. The processing of ACT320 will be described later.

[0064] On the other hand, when a normal response command is received via the communication interface 24, the processor 21 determines YES in ACT 314 and proceeds to ACT 316. The processor 21 generates normal registration data in ACT 316. The normal registration data includes the product data detected from the normal response command and an error flag of "0".

[0065] Having generated the normal registration data, the processor 21 registers the normal registration data in the registered transaction information file TFL1 in ACT317. The processor 21 also checks whether the first status S1 in the registered transaction information file TFL1 is "0" in ACT318. If the first status S1 is "0", the processor 21 judges YES in ACT318 and proceeds to ACT319. The processor 21 changes the first status S1 from "0" to "1" in ACT319. If the first status S1 has already been changed to "1", the processor 21 judges NO in ACT318 and skips the processing of ACT319.

[0066] When the process of ACT319 is completed or skipped, the processor 21 proceeds to ACT320. The processor 21 controls the communication interface 24 to transmit the registration data to the terminal controller 40 in ACT320. This control causes the communication interface 24 to output normal registration data or error registration data. The normal registration data or error registration data is transmitted to the terminal controller 40 via the communication network 80.

[0067] Returning to the explanation of Figure 10. The processor 41 of the terminal controller 40 that transmitted the product registration request command waits for registration data in ACT214. When normal registration data or error registration data is received via the communication interface 44, the processor 41 judges YES in ACT214 and proceeds to ACT215. The processor 41 registers the normal registration data or error registration data in the registration mobile information file MFL1 in ACT215. The processor 41 also checks whether the second status S2 of the registration mobile information file MFL1 is "0" in ACT216. If the second status S2 is "0", the processor 41 judges YES in ACT216 and proceeds to ACT217. The processor 21 changes the second status S2 from "0" to "1" in ACT217. If the second status S2 has already been changed to "1", the processor 41 judges NO in ACT216 and skips the processing in ACT217.

[0068] When the process of ACT217 is completed or skipped, the processor 41 proceeds to ACT218. The processor 21 controls the communication interface 24 to transmit an update notification command in ACT218. This control causes the update notification command to be output from the communication interface 24. The update notification command is wirelessly transmitted from the access point 50 via the communication network 80. The update notification command includes data of the registered mobile information file MFL1 and the terminal ID detected from the product registration notification command. The update notification command wirelessly transmitted from the access point 50 is received by the mobile terminal 60 to which the terminal ID included in the command is set.

[0069] Returning to the explanation of Figure 8. The processor 61 of the mobile terminal 60 that controlled the transmission of the product registration notification command returns to the standby state of ACT105 to ACT107. When the processor 61 receives the update notification command via the wireless device 64 in this standby state, the processor 61 judges YES in ACT106 and proceeds to ACT109. The processor 61 detects the data of the mobile information file MFL from the update notification command in ACT109. The processor 61 then updates the registration screen based on the data in ACT110. That is, for normal registration data, the processor 61 updates the registration screen so that the product name, price, points, discount amount, etc. are displayed in the details area. The processor 61 also updates the total points and total amount in the total area. For erroneous registration data, the processor 61 updates the registration screen so that data indicating the error content is displayed in the details area. In this way, the processor 61, having finished updating the registration screen, returns to the standby state of ACT105 to ACT107.

[0070] In this way, a consumer who uses a mobile terminal 60 to shop first starts up the mobile terminal 60. Then, in the virtual POS server 20, a transaction information file TFL in which the terminal ID of the mobile terminal 60 is set is created. In the terminal controller 40, a mobile information file MFL in which the same terminal ID is set is created.

[0071] Next, the consumer reads the barcode of the purchased item with the scanner 66 of the mobile terminal 60. This barcode data is then sent to the virtual POS server 20 via the terminal controller 40. If the barcode data indicates the item code of the purchased item, the virtual POS server 20 generates normal registration data for the purchased item. This normal registration data is then stored in the transaction information file TFL. On the other hand, if the barcode data does not indicate the item code of the purchased item, for example, the virtual POS server 20 generates error registration data. The error registration data is not stored in the transaction information file TFL.

[0072] The normal registration data or error registration data generated by the virtual POS server 20 is transmitted to the terminal controller 40. In the terminal controller 40, the normal registration data and error registration data are stored in a mobile information file MFL. Then, the data in the mobile information file MFL is transmitted to the mobile terminal 60. In the mobile terminal 60, a list of the registration data stored in the mobile information file MFL is displayed on the touch panel 65.

[0073] Therefore, the consumer can check the price, discount amount, etc. of the purchased item from the list displayed on the touch panel 65. The consumer can also check if a registration error has occurred.

[0074] Now, if a consumer has no problems with the price or discount amount of the purchased item and no registration errors have occurred, they touch the Checkout button on the registration screen when they have finished shopping. When the Checkout button is touched, the processor 61 of the mobile terminal 60 determines YES in ACT 107 and proceeds to ACT 111. The processor 61 controls the wireless device 64 to issue a billing notification in ACT 111. This control causes the wireless device 64 to wirelessly transmit an billing notification command. The billing notification command is transmitted to the terminal controller 40 via the access point 50. The billing notification command includes the terminal ID of the mobile terminal 60.

[0075] When the processor 41 of the terminal controller 40 receives an accounting notification command via the communications interface 44, it begins information processing according to the procedure shown in the flowchart of Figure 11. The processor 41 detects the terminal ID from the accounting notification command in ACT221. The processor 41 then checks whether the second status S2 of the mobile information file MFL in which the terminal ID is set is "1" in ACT222. If the second status S2 of the mobile information file MFL is other than "1", the processor 41 determines NO in ACT222. The processor 41 ends processing for the accounting notification with an error.

[0076] If the second status S2 of the mobile information file MFL is "1", the processor 41 judges YES in ACT222 and proceeds to ACT223. The processor 41 changes the second status S2 of this mobile information file MFL from "1" to "2". The processor 41 also controls the communications interface 44 to make a transaction request in ACT224. This control causes a transaction request command to be output from the communications interface 44. The transaction request command is sent to the virtual POS server 20 via the communications network 80. The transaction request command includes the terminal ID detected from the transaction notification command. Note that below, the mobile information file MFL in which the second status S2 has been changed from "1" to "2" is referred to as the transaction mobile information file MFL2.

[0077] When the processor 21 of the virtual POS server 20 receives a transaction request command via the communications interface 24, it begins information processing according to the procedure shown in the flow chart of Figure 14. The processor 21 detects the terminal ID from the transaction request command in ACT331. The processor 21 then checks whether the first status S1 of the transaction information file TFL in which the terminal ID is set is "1" in ACT332. If the first status S1 of the transaction information file TFL is other than "1", the processor 21 determines NO in ACT332. The processor 21 ends processing of the transaction request as an error.

[0078] If the first status S1 of the transaction information file TFL is "1", the processor 21 judges YES in ACT332 and proceeds to ACT333. The processor 21 changes the first status S1 of the transaction information file TFL from "1" to "2" in ACT333. Note that hereinafter, the transaction information file TFL in which the first status S1 has been changed from "1" to "2" is referred to as the accounting transaction information file TFL2.

[0079] The processor 21 controls the communication interface 24 to issue an accounting authorization notification as ACT334. This control causes an accounting authorization notification command to be output from the communication interface 24. The accounting authorization notification command is transmitted to the terminal controller 40 via the communication network 80. The accounting authorization notification command includes the terminal ID detected from the accounting request command.

[0080] Returning to the explanation of Figure 11. The processor 41 of the terminal controller 40 that sent the accounting request command waits for an accounting authorization notification command in ACT225. When the accounting authorization notification command is received via the communication interface 44, the processor 41 judges YES in ACT225 and proceeds to ACT226. The processor 41 controls the communication interface 24 to issue an accounting execution notification in ACT226. This control causes the accounting execution notification command to be output from the communication interface 24. The accounting execution notification command is wirelessly transmitted from the access point 50 via the communication network 80. The accounting execution notification command includes the terminal ID detected from the accounting notification command. The accounting execution notification command wirelessly transmitted from the access point 50 is received by the mobile terminal 60 to which the terminal ID included in the command is set.

[0081] Returning to the explanation of Figure 8. The processor 61 of the mobile terminal 60 that issued the billing notification waits for a billing execution notification in ACT 112. When the billing execution notification command is received via the wireless device 64, the processor 61 determines YES in ACT 112 and proceeds to ACT 113. In ACT 113, the processor 61 causes a barcode indicating the terminal ID to be displayed on the touch panel 65. With this, the processor 61 ends the information processing for the usage start declaration.

[0082] After confirming that the barcode is displayed on the touch panel 65, the consumer approaches the payment machine 30. The consumer then has the payment machine 30 use a scanner to read the barcode displayed on the touch panel 65. The barcode data read by the payment machine 30 is output to the store server 10.

[0083] Returning to the explanation of Figure 14. The processor 21 of the virtual POS server 20 that sent the transaction permission notification command controls the communications interface 24 to send the data in the transaction information file TFL2 to the store server 10 as ACT335. This control causes the data in the transaction information file TFL2 to be output from the communications interface 24. This data is then sent to the store server 10 via the communications network 80.

[0084] The store server 10 temporarily stores the data in the transaction information file TFL2 received from the virtual POS server 20. Then, when the store server 10 obtains barcode data from the payment machine 30, it searches for the transaction information file TFL2 in which the terminal ID represented by the barcode is set. The store server 10 outputs the corresponding data in the transaction information file TFL2 to the payment machine 30. The payment machine 30 executes payment processing for the products purchased by the consumer based on the data in the transaction information file TFL2. When payment processing at the payment machine 30 is completed, the store server 10 outputs an end of payment command to the virtual POS server 20.

[0085] The processor 21 waits for an accounting end command in ACT336. When the processor 21 receives the accounting end command via the communications interface 24, it determines YES in ACT336 and proceeds to ACT337. The processor 21 changes the first status S1 in the accounting transaction information file TFL2 from "2" to "3" in ACT337. The processor 21 also controls the communications interface 24 to send an accounting end notification in ACT338. This control causes the communications interface 24 to output an accounting end notification command. The accounting end notification command is sent to the terminal controller 40 via the communications network 80. The accounting end notification command includes the terminal ID detected from the accounting request command.

[0086] Returning to the explanation of Figure 11. The processor 41 of the terminal controller 40 that issued the accounting execution notification waits for an accounting end notification command in ACT227. When the accounting end notification command is received via the communications interface 44, the processor 41 determines YES in ACT227 and proceeds to ACT228. In ACT228, the processor 41 changes the second status S2 of the accounting mobile information file MFL2 from "2" to "3." With this, the processor 41 ends the accounting notification command reception process.

[0087] In this way, consumers who have no problems with the price, discount amount, etc. of the purchased item and who have not encountered any registration errors can use the payment machine 30 to make payment for the purchased item by having the scanner of the payment machine 30 read the barcode displayed on the touch panel 65 of the mobile terminal 60.

[0088] However, if a consumer notices that the price of the purchased product is different from that on the price tag, or that the discount amount is incorrect, in most cases, he or she will notify a store clerk called an attendant before making the payment. The same applies to consumers who have experienced a registration error. The store clerk who receives such a notice will then use the monitoring terminal 70 to correct the error in the registered data. Next, the operation of correcting an error in registered data using the monitoring terminal 70 will be described with reference to Figures 15 to 23.

[0089] 15 to 17 are flow charts showing the main information processing procedures executed by the processor 71 of the monitoring terminal 70 in accordance with the monitoring support program APL2. FIG. 18 is a flow chart showing the information processing procedures executed by the processor 41 of the terminal controller 40 in response to the information processing of the monitoring terminal 70. FIG. 19 is a flow chart showing the information processing procedures executed by the processor 21 of the virtual POS server 20 in response to the information processing of the terminal controller 40. FIG. 20 to 23 are examples of various images displayed on the touch panel 75 of the monitoring terminal 70. Note that the operation described below is an example. The procedures are not particularly limited as long as similar results are obtained.

[0090] First, the processor 71 of the monitoring terminal 70 collects the mobile information file MFL from the terminal controller 40 as ACT401. Specifically, the processor 71 controls the wireless device 74 to collect the mobile information file. By this control, a collection command is wirelessly transmitted from the wireless device 74. The collection command is received by the access point 50 connected by wireless LAN and transmitted to the terminal controller 40 via the communication network 80. The processor 41 of the terminal controller 40, which receives the collection command via the communication interface 44, acquires all the mobile information files MFL whose second status S2 is other than "3" from among the mobile information files MFL stored in the auxiliary storage device 43. Then, the processor 41 controls the communication interface 44 to transmit the acquired mobile information file MFL to the monitoring terminal 70. By this control, the data of the mobile information file MFL is output from the communication interface 44. This data is wirelessly transmitted via the access point 50 and received by the monitoring terminal 70.

[0091] Once the mobile information file MFL has been collected from the terminal controller 40 in this manner, the processor 71 stores the mobile information file MFL as ACT 402. The mobile information file MFL may be stored in a volatile memory area of ​​the main memory 72, or in the auxiliary storage device 73. Hereinafter, the collected mobile information file MFL will be referred to as collected mobile information file MFL3.

[0092] The processor 71 generates image data for the monitoring screen SC1 (see FIG. 20) based on the data in the collected mobile information file MFL3 as ACT 403. Then, the processor 71 outputs the image data to the touch panel 75 to display the monitoring screen SC1.

[0093] FIG. 20 is a display example of the monitoring screen SC1. As shown in the figure, the monitoring screen SC1 displays a status display area 90 of the mobile terminal 60 and a next page button BT1. A total of 15 status display sections Tx are arranged in a matrix of 5 rows and 3 columns in the status display area 90. Incidentally, "x" in the status display section Tx indicates an integer of 1 or more. The next page button BT1 is an image of a button that instructs switching the status display section Tx (T1 to T15) displayed in the status display area 90 to the next status display section Tx (T16 to T30). After switching the status display area 90 to the next status display section Tx (T16 to T30), the next page button B becomes a previous page button. Alternatively, the previous page button is displayed alongside the next page button B. The previous page button is an image of a button that instructs returning the other status display sections Tx (T16 to T30) displayed in the status display area 90 to the original status display section Tx (T1 to T15). Such next page button B and previous page button are one example of operators reproduced by software on the screen of touch panel 75. The layout of monitoring screen SC1 is not particularly limited.

[0094] Each of the multiple status display sections Tx displayed in the status display area 90 corresponds to one mobile terminal 60. FIG. 21 is an example of a display of the status display unit Tx. As an example, the status display unit Tx displays the terminal ID "MBxx" of the corresponding mobile terminal 60. The status display unit Tx displays a first mark M1 that identifies whether the corresponding mobile terminal 60 is waiting, registering, or checking out. The first mark M1 lights up "Waiting" when the second status S2 of the collected mobile information file MFL3 in which the terminal ID of the corresponding mobile terminal 60 is set is "0" indicating the first state before product registration begins. The first mark M1 lights up "Registering" when the second status S2 is "1" indicating the second state after product registration begins. The first mark M1 lights up "Checking out" when the second status S2 is "2" indicating the third state after the checkout declaration. Note that a mobile information file MFL in which the second status S2 is "3" indicating the fourth state after the checkout is completed has not been collected. Therefore, the status display section Tx corresponding to the terminal ID of the mobile information file MFL is not displayed in the status display area 90.

[0095] The status display unit Tx further displays a second mark M2, a third mark M3, and a fourth mark MC4. The second mark M2 lights up when error registration data of a product registration error is stored in the collected mobile information file MFL3. The third mark M3 lights up when error registration data of a discount error is stored. The fourth mark MC4 lights up when normal registration data of a product with an age restriction is stored. Note that the types of marks displayed on the status display unit Tx are not limited to the first mark M1 to the fourth mark N4 described above.

[0096] Now, when the attendant store clerk who is the operator of the monitoring terminal 70 receives, for example, a request from a consumer to correct registered data, the attendant recognizes the terminal ID of the mobile terminal 60 that the consumer is using to register the product. For example, the touch panel 65 of each mobile terminal 60 displays the terminal ID set in that mobile terminal 60, so the store clerk recognizes the terminal ID of the mobile terminal 60 from this display.

[0097] The store clerk who recognizes the terminal ID searches for the status display section Tx1 that displays the terminal ID among the multiple status display sections Tx displayed in the status display area 90. When the store clerk finds the corresponding status display section Tx1, the store clerk touches the status display section Tx1. In this way, the store clerk specifies the mobile terminal 60 that registered the registration data that the consumer requested to be corrected.

[0098] Returning to the explanation of Figure 15. The processor 71 of the monitoring terminal 70 displaying the monitoring screen SC1 waits for the mobile terminal 60 to be designated in ACT404. When the processor 71 detects that the mobile terminal 60 has been designated by the operation of the store clerk described above, the processor 71 judges YES in ACT404 and proceeds to ACT405. The processor 71 acquires the terminal ID of the designated mobile terminal 60 in ACT405. Then, the processor 71 checks the second status S2 of the collected mobile information file MFL3 in which the terminal ID is set in ACT406. Here, if the second status S2 is "1", the processor 71 causes the touch panel 75 to display a list LS1 (see FIG. 22) of registered data registered in the area B2.

[0099] FIG. 22 is a display example of an image SC2 including a list LS1. In the image SC2, a status display section Tx of a specified mobile terminal 60 and a list LS1 of registered data by the mobile terminal 60 are displayed. In the list LS1, for normally registered data, the product name, number of items, and price are displayed. For erroneously registered data, information indicating the error content is displayed. Also, a selection button BT2 is displayed in association with each registered data. Also, in the image SC2, an add button BT3 and an end button BT4 are displayed. The selection button BT2, the add button BT3, and the end button BT4 are examples of operators reproduced on the screen of the touch panel 75 by software. The layout of the image SC2 is not particularly limited.

[0100] Now, if the clerk who has checked list LS1 receives a request from the consumer to modify the registered data, he / she touches the Select button BT2 associated with that registered data. If the clerk receives a request to register a new product, he / she touches the Add button BT3. When the clerk has finished checking list LS1, he / she touches the End button BT4.

[0101] Returning to the explanation of Figure 15.

[0102] The processor 71 of the monitoring terminal 70 displaying the image SC2 checks whether the selection button BT2 has been touched in ACT408. If the selection button BT2 has not been touched, the processor 71 judges NO in ACT408 and proceeds to ACT409. The processor 71 checks whether the addition button BT3 has been touched in ACT409. If the addition button BT3 has not been touched, the processor 71 judges NO in ACT409 and proceeds to ACT410. The processor 71 checks whether the end button BT4 has been touched in ACT410. If the end button BT4 has not been touched, the processor 71 judges NO in ACT410 and returns to ACT408. Here, the processor 71 waits for the selection button BT2, the addition button BT3, or the end button BT4 to be touched in ACT408 to ACT410.

[0103] When the selection button BT2 is touched in the standby state of ACT408 to ACT410, the processor 71 judges YES in ACT408 and proceeds to ACT421 in Fig. 16. In ACT421, the processor 71 checks whether the registered data associated with the selection button BT2 is normal registered data or erroneous registered data. If the registered data is normal registered data, the processor 71 judges YES in ACT421 and proceeds to ACT422. In ACT422, the processor 71 displays an edit pop-up image SC3 (see Fig. 23) on the touch panel 75.

[0104] FIG. 23 is an example of a display of an edit pop-up image SC3. As shown in the figure, the edit pop-up image SC3 displays the product name of the normally registered data selected by the selection button BT2. The edit pop-up image SC3 also displays an edit area ED1 for the quantity, unit price, discount amount, and amount. The edit area ED1 displays the quantity (points), unit price (price), discount amount, and amount of the normally registered data. Incidentally, the amount is the amount obtained by multiplying the unit price by the quantity minus the discount amount. Furthermore, the edit area ED1 displays a confirm button BT5 and a cancel button BT6. The confirm button BT5 and the cancel button BT6 are examples of controls reproduced on the screen of the touch panel 75 by software. The layout of the edit pop-up image SC3 is not particularly limited.

[0105] For example, if a consumer points out that the price in the normally registered data is incorrect and the clerk is able to confirm the error, the clerk operates the touch panel 75 to correct the unit price in the editing area ED1 to the correct amount. Specifically, when the unit price area in the editing area ED1 is touched, a numeric keypad button is displayed, and the clerk operates the numeric keypad button to input the correct unit price in the unit price area. Similarly, if a consumer points out that the discount amount in the normally registered data is incorrect and the clerk is able to confirm the error, the clerk operates the touch panel 75 to correct the discount amount in the editing area ED1 to the correct amount. Then, when the clerk has finished correcting the editing area ED1, he touches the Confirm button BT5. On the other hand, if the consumer requests the cancellation of the normally registered data, the clerk touches the Cancel button BT6.

[0106] Returning to the explanation of Figure 16. The processor 71 of the monitoring terminal 70 displaying the edit pop-up image SC3 checks whether the Cancel button BT6 has been touched in ACT423. If the Cancel button BT6 has not been touched, the processor 71 judges NO in ACT423 and proceeds to ACT424. The processor 71 checks whether the Confirm button BT5 has been touched in ACT424. If the Confirm button BT5 has not been touched, the processor 71 judges NO in ACT424 and returns to ACT423. Here, the processor 71 waits for the Cancel button BT6 or the Confirm button BT5 to be touched in ACT423 and ACT424.

[0107] If the confirmation button BT5 is touched in the standby state of ACT423 and ACT424, the processor 71 judges YES in ACT424 and proceeds to ACT425. The processor 71 edits the normally registered data in ACT425. That is, for example, if the unit price in the editing area ED1 is corrected, the processor 71 rewrites the price of the corresponding normally registered data to the corrected amount. For example, if the discount amount in the editing area ED1 is corrected, the processor 71 rewrites the discount amount of the corresponding normally registered data to the corrected amount. After that, the processor 71 proceeds to ACT427. The processing of ACT427 will be described later.

[0108] On the other hand, if the registered data associated with the touched selection button BT2 is erroneous registered data, the processor 71 judges NO in ACT421. Also, if the cancel button BT6 of the edit pop-up image SC3 is touched, the processor 71 judges YES in ACT423. In either case, the processor 71 proceeds to ACT426. The processor 71 deletes the registered data in ACT426. That is, if the registered data associated with the selection button BT2 is erroneous registered data, the processor 71 deletes the erroneous registered data from the collected mobile information file MFL3. Similarly, if the cancel button BT6 is touched, the normal registered data associated with the selection button BT2 is deleted from the collected mobile information file MFL3. After that, the processor 71 proceeds to ACT427.

[0109] The processor 71 controls the wireless device 74 to perform a modification notification as ACT427. This control causes the wireless device 74 to wirelessly transmit a modification notification command. The modification notification command is received by the access point 50 connected by wireless LAN, and is transmitted to the terminal controller 40 via the communication network 80. The modification notification command includes data of the collected mobile information file MFL3 in which the registration data has been edited.

[0110] When the processor 41 of the terminal controller 40 receives the modification notification command via the communication interface 44, it starts information processing according to the procedure shown in the flowchart of Fig. 18. The processor 41 acquires registration data from the collected mobile information file MFL3 included in the modification notification command in ACT231. Then, the processor 41 acquires registration data in the mobile information file MFL in which the same terminal ID as that of the collected mobile information file MFL3 is set in ACT232 so that the registration data matches the registration data acquired from the collected mobile information file MFL3.

[0111] When the modification of the mobile information file MFL is completed, the processor 41 checks whether or not there has been any modification to change the normal registration data in ACT 233. If there has been no modification to change the normal registration data, the processor 41 judges NO in ACT 233 and ends the process of receiving the modification notification command.

[0112] On the other hand, if there is a correction to change the normally registered data, the processor 41 determines YES in ACT233 and proceeds to ACT234. The processor 41 controls the communication interface 44 to make a correction request. The processor 41 then ends the process of receiving the correction notification command. This control causes a correction request command to be output from the communication interface 44. The correction request command is transmitted to the virtual POS server 20 via the communication network 80. The correction request command includes the data of the mobile information file MFL in which the normally registered data has been changed.

[0113] When the processor 21 of the virtual POS server 20 receives the modification request command via the communication interface 24, it starts information processing according to the procedure shown in the flowchart of Fig. 19. In ACT341, the processor 21 acquires the normal registration data from the mobile information file MFL included in the modification request command. Then, in ACT342, the processor 21 modifies the normal registration data in the transaction information file TFL in which the same terminal ID as that mobile information file MFL is set so that it matches the normal registration data acquired from the mobile information file MFL. With this, the processor 21 ends the process of receiving the modification request command.

[0114] In this way, when the registration data stored in the mobile information file MFL is modified in the monitoring terminal 70, the modification is reflected in the same mobile information file MFL stored in the terminal controller 40. Also, when the normal registration data is modified, the modification is also reflected in the transaction information file TFL stored in the virtual POS server 20.

[0115] Returning to the explanation of Figure 15. In the standby state of ACT408 to ACT410, when the add button BT3 is touched, the processor 71 judges YES in ACT409 and proceeds to ACT431 in Fig. 17. The processor 71 waits for product registration in ACT431.

[0116] A store clerk who receives a product registration request from a consumer operates the scanner 76 to read the barcode attached to the product. When the barcode is read by the scanner 76, the processor 71 determines YES in ACT431 and proceeds to ACT432. The processor 61 controls the wireless device 74 to perform a product registration notification in ACT432. By this control, a product registration notification command is wirelessly transmitted from the wireless device 74. The product registration notification command is transmitted to the terminal controller 40 via the access point 50. The product registration notification command includes the data of the barcode read by the scanner 76 and the terminal ID associated with the specified status display unit Tx.

[0117] The processor 41 of the terminal controller 40, which has received the product registration notification command, similarly executes the processes of ACT211 to ACT218 described with reference to Fig. 10. Also, the processor 21 of the virtual POS server 20, which has received the product registration request command output from the terminal controller 40 in ACT213, similarly executes the processes of ACT311 to ACT320 described with reference to Fig. 13.

[0118] Therefore, when the barcode of a product is scanned by the monitoring terminal 70, normal registration data generated based on the barcode data is added to the transaction information file TFL and the mobile information file MFL of the specified terminal ID.

[0119] In the standby state of ACT408 to ACT410, if the end button BT4 is touched, the processor 71 determines YES in ACT410 and proceeds to ACT411. The processor 71 erases the image SC2 in ACT411. Then, the processor 71 returns to ACT401.

[0120] As is clear from the above description, the terminal controller 40 and the virtual POS server 20 each include a receiving means. That is, the terminal controller 40 receives a product registration notification command transmitted from the mobile terminal 60 via the communication interface 44. The product registration notification command includes barcode data as data based on the purchased product. The virtual POS server 20 receives a product registration request command transmitted from the terminal controller 40 via the communication interface 24. The product registration request command also includes barcode data as data based on the purchased product.

[0121] The virtual POS server 20 is equipped with a generating means. That is, the virtual POS server 20 generates normal registration data or error registration data based on the barcode data. The normal registration data includes the product name, price, number, discount amount, etc. of the purchased product. The normal registration data is an example of product sales data. The error registration data includes barcode data. The error registration data is an example of data based on the purchased product that did not result in the generation of product sales data.

[0122] The virtual POS server 20 includes a first storage means, and the terminal controller 40 includes a second storage means. That is, the virtual POS server 20 stores the normally registered data in a transaction information file TFL. The terminal controller 40 stores the normally registered data and the erroneous registered data in a mobile information file MFL.

[0123] The monitoring terminal 70 constitutes an acquisition means. That is, the monitoring terminal 70 acquires, from the data stored in the mobile information file MFL, product sales data generated based on data based on purchased products inputted by any of the mobile terminals 60 and data based on purchased products that did not result in the generation of product sales data.

[0124] The monitoring terminal 70 constitutes a selection means. That is, the monitoring terminal 70 accepts a selection input of a status display section Tx displayed on the monitoring screen SC1 via the touch panel 75, and selects the mobile terminal 60 corresponding to that status display section Tx.

[0125] The monitoring terminal 70 constitutes a display means. That is, when a status display section Tx is selected, the monitoring terminal 70 displays on the touch panel 75 an image SC2 including a list LX1 of normal registration data and error registration data generated from data based on the purchased product inputted by the mobile terminal 60 corresponding to the status display section Tx.

[0126] The monitoring terminal 70 constitutes a correction instruction means. That is, the monitoring terminal 70 displays an edit pop-up image SC3 on the touch panel 75 and accepts correction of the normal registration data or the error registration data displayed in the list LX1. Then, the monitoring terminal 70 outputs a correction notification command to the terminal controller 40 to instruct the correction.

[0127] The terminal controller 40 and the virtual POS server 20 are provided with a correction means. That is, the terminal controller 40 corrects the normal registration data or the erroneous registration data stored in the mobile information file MFL in accordance with the correction notification command. The terminal controller 40 also outputs a correction request command to the virtual POS server 20. The virtual POS server 20 corrects the normal registration data in the transaction information file TFL in accordance with the correction request command.

[0128] The monitoring terminal 70 is equipped with an input means. That is, the monitoring terminal 70 inputs the barcode data read by the scanner 76 as data based on the purchased product. The monitoring terminal 70 then outputs a product registration notification command including the input data to the terminal controller 40.

[0129] The terminal controller 40 and the virtual POS server 20 are provided with an adding means. That is, the terminal controller 40 adds normal registration data to the mobile information file MFL in accordance with the product registration notification command. The terminal controller 40 also outputs a product registration request command to the virtual POS server 20. The virtual POS server 20 adds normal registration data to the transaction information file TFL in accordance with the product registration request command.

[0130] According to the store system 100 equipped with the monitoring terminal 70, terminal controller 40 and virtual POS server 20 having such a configuration, even if there is an error in the data entered by the consumer via the mobile terminal 60, the store clerk can correct the error by operating the monitoring terminal 70 without discarding the data. Therefore, it is possible to reduce the load on the terminal controller 40 and the virtual POS server 20, which process the data entered via the mobile terminal 60.

[0131] In addition, since it is no longer necessary for consumers or store clerks to re-enter data into the payment device 30, the processing time required for payment is shortened and the personnel burden is also reduced, resulting in more efficient store management.

[0132] Although the embodiment of the store system 100 has been described above, the embodiment is not limited to this. In the above embodiment, the server of the store system 100 is constituted by the terminal controller 40 and the virtual POS server 20. The server is not limited to such a configuration. For example, the functions of the terminal controller 40 and the virtual POS server 20 may be realized by one server. In this case, the mobile information file MFL and the transaction information file TFL may be consolidated into the mobile information file MFL. In this case, in the accounting machine 30, if the mobile information file MFL contains error registration data, the settlement process may be regarded as an error. By doing so, a store system consisting of a server equipped with a receiving means, a generating means, a storing means, and a correcting means, and a monitoring terminal 70 equipped with an acquiring means and a correcting instruction means can be realized. In addition, a store system 100 in which the monitoring terminal 70 is equipped with a selecting means and an inputting means, and the server is equipped with an adding means can also be realized. In addition, a store system 100 in which the monitoring terminal 70 is equipped with a displaying means can also be realized.

[0133] Also, the generating means is not necessarily required. That is, the server receives data based on purchased items inputted by each of the multiple mobile terminals 60, and stores it in the mobile information file MFL. The monitoring terminal 70 acquires data based on purchased items inputted by any of the mobile terminals 60 from the data stored in the mobile information file MFL, and instructs the data to be corrected. The server executes the instructed correction of the data stored in the mobile information file MFL. Even in a store system configured in this way, if there is an error in the data inputted via the mobile terminal 60, the error can be corrected without discarding the data, and the load on the server for data processing can be reduced.

[0134] In the above embodiment, the identification information of the mobile terminal 60 set in the mobile information file MFL and the transaction information file TFL is the terminal ID. The identification information is not limited to the terminal ID. For example, a unique identification code arbitrarily generated by the terminal controller 40 upon receiving a usage start notification from the mobile terminal 60 may be temporarily used as the identification information of the mobile terminal 60.

[0135] The input device constituting the input means of the monitoring terminal 70 is not limited to the scanner 76. The input means may be constituted by an input device such as a touch panel, a keyboard, or an RFID reader.

[0136] Although several other embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included within the scope of the invention and the scope of the invention and its equivalents described in the claims. The invention as originally claimed in the present application is set forth below. [1] A server including a receiving means for receiving data based on purchased items inputted by a plurality of mobile terminals and a storage means for storing the data based on the purchased items received by the receiving means; a store terminal including an acquisition means for acquiring data based on the purchased items inputted by any one of the mobile terminals from the data stored in the storage means, and a correction instruction means for instructing correction of the data acquired by the acquisition means; the server further comprises a correction means for executing the correction instructed by the correction instructing means on the data stored by the storage means. [2] The store system described in Appendix [1], wherein the store terminal further comprises a selection means for selecting the mobile terminal and an input means for inputting data based on purchased items, and the server further comprises an addition means for adding the data based on purchased items input by the input means to the storage means as data based on purchased items input from the mobile terminal selected by the selection means. [3] The store system described in Appendix [2], wherein the store terminal further includes a display means for displaying a list of data based on the purchased items inputted on the mobile terminal selected by the selection means, and the correction instruction means instructs correction of the data displayed on the list. [4] A store system including: a server comprising: a receiving means for receiving data based on purchased goods input by each of a plurality of mobile terminals; a generating means for generating product sales data based on the data based on the purchased goods received by the receiving means; a first storage means for storing the product sales data generated by the generating means; and a second storage means for storing the product sales data generated by the generating means and data based on the purchased goods that did not result in the generation of the product sales data; and a store terminal comprising: an acquiring means for acquiring, from the data stored in the second storage means, product sales data generated based on data based on purchased goods input by any of the mobile terminals and data based on purchased goods that did not result in the generation of the product sales data; and a correction instruction means for instructing correction of the product sales data or the data based on purchased goods acquired by the acquiring means, wherein the server further comprises a correction means for executing corrections instructed by the correction instruction means on the data stored in the first storage means and the second storage means. [5] The store system described in Appendix [4], wherein the store terminal further comprises a selection means for selecting the mobile terminal and an input means for inputting data based on purchased items, and the server further comprises an addition means for adding product sales data generated based on the data based on purchased items input by the input means to the first storage means and the second storage means as data generated from the data based on purchased items input from the mobile terminal selected by the selection means. [6] The store terminal further includes a display means for displaying a list of product sales data generated from data based on purchased products inputted at the mobile terminal selected by the selection means and data based on purchased products that did not result in the generation of product sales data, and the correction instruction means instructs correction of the data displayed in the list, in the store system described in Appendix [5]. [Explanation of symbols]

[0137] 10...store server, 20...virtual POS server, 21,41,61,71...processor, 22,42,62,72...main memory, 23,43,63,73...auxiliary storage device, 24,44...communication interface, 30...accounting machine, 40...terminal controller, 50...access point, 60...mobile terminal, 64,74...wireless device, 65,75...touch panel, 66,76...scanner, 70...monitoring terminal, 100...store system, MFL...mobile information file, TFL...transaction information file.

Claims

1. A server and a store terminal constituting a store system, the server having a plurality of mobile information files generated for each of a plurality of mobile terminals, storing in each mobile information file merchandise sales data generated based on data based on purchased merchandise inputted at a corresponding mobile terminal and data based on purchased merchandise that did not result in the generation of merchandise sales data, a collection means for collecting the plurality of mobile information files from the server; a first display means for displaying a monitoring screen on which the plurality of mobile terminals can be individually designated based on the collected data of the plurality of mobile information files; a second display means for displaying, when any one of the mobile terminals is designated on the monitoring screen, a list of the product sales data stored in the mobile information file corresponding to the designated mobile terminal and data based on the purchased product that did not result in the generation of the product sales data; a correction means for accepting a correction to the product sales data when the product sales data is selected from the list, and correcting the product sales data stored in the collected mobile information file when the correction is confirmed; a deletion means for deleting data based on the purchased product from the collected mobile information file when the data based on the purchased product is selected from the list; a modification transmission means for transmitting to the server the mobile information file in which the product sales data has been modified by the modification means or in which data based on the purchased product has been deleted by the deletion means; A store terminal equipped with the above.

2. An input means for inputting data based on purchased goods; an additional transmission means for transmitting, when any one of the mobile terminals is designated on the monitoring screen and data based on the purchased item is input via the input means, a command to the server to notify the designated mobile terminal that product sales data created from the data based on the purchased item should be added to the mobile information file generated for the designated mobile terminal; The store terminal according to claim 1, further comprising:

3. the mobile information file includes a status identifying whether the status is before or after completion of a transaction; The store terminal according to claim 1 , wherein said collection means collects from said server a mobile information file representing the state before completion of said transaction.

4. The mobile information file further includes a status identifying whether the state is before the start of product registration or after the start of product registration, The store terminal of claim 3, wherein the second display means displays a list of product sales data stored in the mobile information file corresponding to the mobile terminal specified on the monitoring screen when the mobile information file is in a state after product registration has begun and data based on purchased products that did not result in the generation of product sales data.

5. A server having a plurality of mobile information files generated for each of a plurality of mobile terminals, storing in each mobile information file merchandise sales data generated based on data based on purchased merchandise inputted at a corresponding mobile terminal and data based on purchased merchandise that did not result in the generation of merchandise sales data, and a computer of a store terminal constituting a store system, a collection means for collecting the plurality of mobile information files from the server; a first display means for displaying a monitoring screen on which the plurality of mobile terminals can be individually designated based on the collected data of the plurality of mobile information files; a second display means for displaying, when any one of the mobile terminals is designated on the monitoring screen, a list of the merchandise sales data stored in the mobile information file corresponding to the designated mobile terminal and data based on purchased merchandise that did not result in the generation of the merchandise sales data; a correction means for accepting a correction to the merchandise sales data when the merchandise sales data is selected from the list, and correcting the merchandise sales data stored in the collected mobile information file when the correction is confirmed; a deletion means for deleting data based on the purchased product from the collected mobile information file when the data based on the purchased product is selected from the list; and a modification transmission means for transmitting to the server the mobile information file in which the product sales data has been modified by the modification means or in which the data based on the purchased product has been deleted by the deletion means; A program to function as a

Images