Store system

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] Embodiments of the present invention relate to a store system.

Background Art

[0002] There is a store system that simplifies the data input operation at the time of accounting by having a consumer operate a mobile terminal to input data based on purchased goods. However, the data input via the mobile terminal is not always correct. For example, a product may be registered at a selling price different from the price tag, or a 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 accounting machine by a store clerk. At this time, the store clerk performs processes such as changing the selling price and setting the discount amount for the incorrect data. Conventionally, since it has been dealt with in this way, the load on the server required for processing the data input via the mobile terminal has been wasted.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] The problem to be solved by the embodiments of the present invention is to provide a store system that can correct errors without discarding the data even when there are errors in the data input via the mobile terminal, and can reduce the load required for server data processing.

Means for Solving the Problems

[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 goods respectively input by a plurality of mobile terminals. The storage means stores the data based on the purchased goods received by the receiving means. The correction means executes the correction instructed by a correction instruction means described later on the data stored by the storage means. The store terminal has an acquisition means and a correction instruction means. The acquisition means acquires data based on the purchased goods input by any one of the mobile terminals from the data stored by the storage means. The correction instruction means instructs the correction of the data acquired by the acquisition means.

Brief Description of Drawings

[0006]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Embodiments for Carrying Out the Invention

[0007] Hereinafter, embodiments of the store system will be described with reference to the drawings. In the present embodiment, a store system is exemplified in which a consumer using a shopping cart operates a mobile terminal attached to the cart and inputs data based on the products they purchase.

[0008] FIG. 1 is a block diagram schematically showing an embodiment of a store system 100. The store system 100 includes a store server 10, a virtual POS server 20, a cash register 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). That is, the store server 10, the virtual POS server 20, the cash register 30, the terminal controller 40, and the access point 50 are respectively connected to a communication cable to constitute 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 data relay point for data exchanged between the mobile terminal 60 or the monitoring terminal 70 connected by wireless LAN and each device connected by wired LAN. The number of access points 50 is not limited to one. Considering the scale, layout, etc. of the store, two or more access points 50 may be connected to the communication network 80.

[0010] The mobile terminal 60 is a portable electronic device for assisting the shopping behavior of consumers in the store where the store system 100 is configured. Typically, the consumer is the operator of the mobile terminal 60. The mobile terminal 60 is used, for example, when attached to a shopping cart. The mobile terminal 60 may be lent by the store to the consumer for the consumer to carry. The mobile terminal 60 may be an information terminal such as a smartphone or a tablet terminal owned by the consumer.

[0011] FIG. 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, control signal lines, 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, a computer is constituted by the processor 61, the main memory 62, and the auxiliary storage device 63, and the system transmission path 67 that connects them.

[0012] The processor 61 corresponds to the central part of the above computer. The processor 61 controls each part in order to realize various functions as 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 part of the above computer. The main memory 62 includes a non-volatile memory area and a volatile memory area. The main memory 62 stores an operating system or an application program in the non-volatile memory area. The main memory 62 stores data necessary for the processor 61 to execute processing for controlling each part in the volatile memory area. The above data may also be stored in the non-volatile 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 non-volatile 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 part of the above computer. For example, an EEPROM (registered trademark) (Electric Erasable Programmable Read-Only Memory), an HDD (Hard Disc Drive), or an SSD (Solid State Drive) etc. can be the auxiliary storage device 63. The auxiliary storage device 63 stores data used when the processor 61 performs various processes, or data created by the processes in the processor 61 etc. The auxiliary storage device 63 may store the above application program.

[0015] The wireless device 64 is a device for performing wireless communication of data with the access point 50 via a wireless LAN.

[0016] The touch panel 65 is a device that serves as both an input device and a display device of the mobile terminal 60. The touch panel 65 displays various images. And the touch panel 65 detects the touch position with respect to the displayed image, and outputs the touch position information to the processor 61.

[0017] The scanner 66 is a device used for reading barcodes. The scanner 66 may be a device that optically reads barcodes by scanning with a laser beam, or may be a device that reads barcodes by processing an image including a barcode photographed 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 via network communication and then installed in the auxiliary storage device 63. The recording medium can be in any form as long as it can store the program and is readable by the device, such as a CD-ROM, memory card, etc. The installation destination of the shopping support program APL1 may be 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 accounting machine 30 together with the mobile terminal 60. Typically, the operator of the monitoring terminal 70 is a store clerk called an attendant. The monitoring terminal 70 is placed and used at the location where the attendant waits. The monitoring terminal 70 may be a portable electronic device that can be carried out by the attendant. The monitoring terminal 70 is an example of a store terminal.

[0020] Figure 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, control signal lines, etc. 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, a computer is configured by the processor 71, the main memory 72, and the auxiliary storage device 73, and the system transmission path 77 connecting them.

[0021] The descriptions of the processor 71, main memory 72, auxiliary storage device 73, wireless device 74, touch panel 75, and scanner 76 are the same as those of the processor 61, main memory 62, auxiliary storage device 63, wireless device 64, touch panel 65, and scanner 66 for the mobile terminal 60, so the descriptions here are omitted.

[0022] The monitoring terminal 70 installs a monitoring support program APL2 as a type of application program in the auxiliary storage device 73. The method of installing the monitoring support program APL2 in the auxiliary storage device 73 is not particularly limited either. The same method as that for the shopping support program APL1 can be directly applied. The installation destination of the monitoring support program APL2 may also be the main memory 72.

[0023] The accounting machine 30 is a terminal for settling commercial transactions with consumers. The accounting machine 30 acquires accounting data of 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 by well-known settlement methods such as cash settlement, credit card settlement, electronic money settlement, point settlement, code settlement (also referred to as mobile settlement or smartphone settlement, etc.).

[0024] The accounting machine 30 includes a manned accounting machine for a store clerk to input information for settlement and a self-service accounting machine for a consumer to input information for settlement. The store system 100 may be equipped with both a manned accounting machine and a self-service accounting machine, or may be equipped with only one of them. As the manned accounting machine, a conventionally well-known POS terminal can be applied. As the self-service accounting machine, a conventionally well-known self-service or semi-self-service type accounting machine can be applied.

[0025] The store server 10 supports all aspects of store operations. For this support, the store server 10 manages various databases such as a product database and a member database.

[0026] The product database is an aggregate of product records that describe the data of each product sold in the store. A product record is composed of data items such as a product code, product name, price, discount information, etc. The product code is a unique identification code set for each product to individually identify each product. Each product is attached with a barcode indicating the product code. The discount information is information regarding product discounts such as the discount amount and discount rate.

[0027] The member database is an aggregate of member records that describe data regarding consumers who have registered as members such as point members, so-called members. The member record includes data items such as a member code and cumulative points. The member code is a unique identification code set for each member to identify each member. The cumulative points are the accumulation of points given to the consumer who is that member in business transactions with the member.

[0028] The virtual POS server 20 provides support to make it appear as if a well-known POS terminal is operating by collaborating with the mobile terminal 60. That is, the virtual POS server 20 performs a registration process for purchased products based on data input from the touch panel 65 or scanner 66 of the mobile terminal 60. The data of the purchased products registered by the virtual POS server 20 is displayed on the touch panel 65 of the mobile terminal 60.

[0029] Figure 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, control signal lines, 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, and the auxiliary storage device 23, and the system transmission path 25 that connects them.

[0030] The descriptions of the processor 21, the main memory 22, and the auxiliary storage device 23 are redundant with the descriptions of the processor 61, the main memory 62, and the auxiliary storage device 63 for the mobile terminal 60, so the descriptions here are omitted.

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

[0032] The virtual POS server 20 with such a configuration 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 operations of the mobile terminal 60 and the monitoring terminal 70 connected via the wireless LAN through the access point 50. The terminal controller 40 causes the mobile terminal 60 to function as an input / output interface of the POS terminal by exchanging data commands with the mobile terminal 60 in which the shopping support program APL1 is being executed. The terminal controller 40 can cause the monitoring terminal 70 to function as a state monitoring device of the mobile terminal 60 by exchanging data commands with the monitoring terminal 70 in which the monitoring support program APL2 is being executed.

[0034] FIG. 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, control signal lines, 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, a computer is configured by the processor 41, the main memory 42, and the auxiliary storage device 43, and the system transmission path 45 connecting them.

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

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

[0037] The terminal controller 40 with such a configuration forms a storage area for storing 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 describing the terminal ID, an area A2 for storing a plurality of registration data, and an area A3 for storing the 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 item data for each of a product code, a product name, a price, a score, a discount amount, and an 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 accounting declaration, and a fourth state after the accounting end. In the present 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 describing the terminal ID, an area B2 for storing a plurality of registered data, and an area B3 for storing the second status S2. The registered data includes error registered data in addition to the normal registered data described above. The error registered data is composed of each item data of barcode data and 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 flowchart showing the main information processing procedure executed by the processor 61 of the mobile terminal 60 according to the shopping support program APL1. FIGS. 9 to 11 are flowcharts 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. FIGS. 12 to 14 are flowcharts 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 flowcharts, the operation of the store system 100 until a consumer inputs data based on the purchased goods using the mobile terminal 60 and completes the accounting of the purchased goods will be described. Note that the operation described below is an example. If the same result can be obtained, the procedure and the like are not particularly limited.

[0041] First, the consumer activates the mobile terminal 60 before starting shopping. The mobile terminal 60 is attached to, for example, a shopping cart. When the mobile terminal 60 is activated, the processor 61 starts information processing of the procedure shown in the flowchart of FIG. 8. The processor 61 waits for a usage start declaration as ACT101. For example, the processor 61 causes the touch panel 65 to display a shopping start button. Then the processor 61 waits for the shopping start 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 issue a usage start notification as ACT102. By this control, a usage start notification command is wirelessly transmitted from the wireless device 64. The usage start notification command is received by the access point 50 connected via a wireless LAN and transmitted to the terminal controller 40 via the communication network 80. The usage start notification command includes the terminal ID set in the mobile terminal 60.

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

[0044] When the processor 21 of the virtual POS server 20 receives the usage start request command via the communication interface 24, it starts information processing of the procedure shown in the flowchart of FIG. 12. The processor 21 detects the terminal ID from the usage start request command as ACT301. Then the processor 21 determines the usability of the mobile terminal 60 identified by the terminal ID as ACT302.

[0045] Specifically, the processor 21 searches in the transaction information file TFL to determine whether there is a transaction information file TFL in which the terminal ID is set in area A1 and the first status S1 is other than "3". The transaction information file TFL with the first status S1 other than "3" corresponds to the mobile terminal 60 for which the start-of-use declaration has been made but the accounting has not ended. Therefore, when a corresponding transaction information file TFL is detected, the processor 21 determines that the mobile terminal 60 is unavailable. If a corresponding transaction information file TFL cannot be detected, the processor 21 determines that the mobile terminal 60 is available.

[0046] When it is determined that the mobile terminal 60 is unavailable, the processor 21 determines NO in ACT302 and proceeds to ACT303. The processor 21 controls the communication interface 24 to send a rejection response as ACT303.

[0047] When it is determined that the mobile terminal 60 is available, 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 as ACT304. Then, the processor 21 sets the terminal ID detected from the start-of-use request command in area A1 of the transaction information file TFL as ACT305. The processor 21 also sets the first status S1 of the transaction information file TFL to "0" as ACT306. Further, the processor 21 controls the communication interface 24 to send an approval response as ACT307.

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

[0049] Return to the description of FIG. 9. The processor 41 of the terminal controller 40 that has made a start - of - use request is waiting for a permission response command as ACT202. Here, when a rejection response command is received via the communication interface 204, the processor 41 determines NO in ACT202 and proceeds to ACT203. The processor 41 controls the communication interface 44 to issue a rejection notice as ACT203.

[0050] On the other hand, when 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 as ACT204. Then the processor 41 sets the terminal ID detected from the permission response command in area B1 of the mobile information file MFL as ACT205. Also, the processor 41 sets the second status S2 of the mobile information file MFL to "0" as ACT206. Furthermore, the processor 41 controls the communication interface 44 to issue a permission notice as ACT207.

[0051] By the control of ACT203 or ACT207, a rejection notice command or a permission notice command is output from the communication interface 44. The rejection notice command or the permission notice command is wirelessly transmitted from the access point 50 via the communication network 80. The rejection notice command or the permission notice command includes the terminal ID detected from the rejection response command or the permission response command. The rejection notice command or the permission notice 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] Return to the description of FIG. 8. The processor 61 of the mobile terminal 60 that has sent a usage start notification is waiting for an approval notification command as ACT103. Here, when a rejection notification command is received via the wireless device 64, the processor 61 determines NO in ACT103. The processor 61 ends the process for the usage start declaration as an error. Therefore, the consumer cannot use the mobile terminal 60. For example, the consumer exchanges the shopping cart and makes a usage start declaration for the mobile terminal 60 of the exchanged cart.

[0053] On the other hand, when an approval notification command is received, the processor 61 determines YES in ACT103 and proceeds to ACT104. The processor 61 causes the touch panel 65 to display a registration screen as ACT104. The registration screen includes a details area for displaying the product name, price, points, discount amount, etc. of the purchased products, and a total area for displaying the total points, total amount, etc. of the purchased products. Also, an accounting button for the consumer to declare a transition to accounting is displayed on the registration screen. The accounting button is an example of an operator reproduced on the screen of the touch panel 65 by software. Note that 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 product registration has been accepted as ACT105. If product registration has not been accepted, the processor 61 determines NO in ACT105 and proceeds to ACT106. The processor 61 checks whether an update notification command has been received as ACT106. If the update notification command has not been received, the processor 61 determines NO in ACT106 and proceeds to ACT107. The processor 61 checks whether an accounting declaration has been received as ACT107. If the accounting declaration has not been received, 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, an update notification command to be received, or an accounting declaration to be made.

[0055] Upon checking the registration screen, each time a consumer obtains a purchased product at the store, they have the barcode of the purchased product scanned by the scanner 66 and then put it into the shopping cart.

[0056] When the barcode is read by the scanner 66, the processor 61 in the standby state of ACT105 to ACT107 determines that there is product registration. The processor 61 determines YES in ACT105 and proceeds to ACT108. The processor 61 controls the wireless device 64 to send a product registration notification as 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 barcode data 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 the product registration notification command via the communication interface 44, it starts the 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 as ACT211. Then the processor 41 checks whether the second status S2 of the mobile information file MFL with the terminal ID set is "0" or "1" as ACT212. When the second status S2 of the mobile information file MFL is other than "0" or "1", the processor 41 determines NO in ACT212. The processor 41 ends the processing for the product registration notification as an error.

[0058] When 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 issue a product registration request as ACT213. By this control, a product registration request command is output from the communication interface 44. 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 detected from the product registration notification command and the terminal ID. Hereinafter, the mobile information file MFL with the second status S2 being "0" or "1" is referred to as the 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 the information processing of the procedure shown in the flowchart of FIG. 13. The processor 21 detects the terminal ID from the product registration request command as ACT311. Then the processor 21 checks whether the first status S1 of the transaction information file TFL with the terminal ID set is "0" or "1" as ACT312. When the first status S1 of the transaction information file TFL is other than "0" or "1", the processor 21 determines NO in ACT312. The processor 21 ends the processing for the product registration request as an error.

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

[0061] In response to an 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 using that product code. When the processor 11 detects a product record containing the 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, discount information, etc. that make up the product record.

[0062] On the other hand, if the product database is searched but no corresponding product record is detected, 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 barcode of the product code, products may be attached with barcodes for identifying, for example, the producer, manufacturing company, etc. If a consumer accidentally 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 product data is waiting for a normal response command as ACT314. Here, if an error response command is received via the communication interface 24, the processor 21 determines NO in ACT314 and proceeds to ACT315. The processor 21 generates error registration data as ACT315. The error registration data includes the barcode data detected from the error response command and an error flag of "1". The processor 21 that generated the error registration data proceeds to ACT320. The processing of ACT320 will be described later.

[0064] On the one hand, when the processor 21 receives a normal response command via the communication interface 24, it determines YES in ACT314 and proceeds to ACT316. The processor 21 generates normal registration data as ACT316. The normal registration data includes product data detected from the normal response command and an error flag of "0".

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

[0066] After finishing the process of ACT319 or skipping the process of ACT319, the processor 21 proceeds to ACT320. The processor 21 controls the communication interface 24 to send the registration data to the terminal controller 40 as ACT320. By this control, normal registration data or error registration data is output from the communication interface 24. The normal registration data or error registration data is sent to the terminal controller 40 via the communication network 80.

[0067] Return to the description of FIG. 10. The processor 41 of the terminal controller 40 that has sent the product registration request command is waiting for registration data as ACT214. When normal registration data or error registration data is received via the communication interface 44, the processor 41 determines YES in ACT214 and proceeds to ACT215. The processor 41 registers the normal registration data or error registration data as ACT215 in the registration mobile information file MFL1. Also, the processor 41 checks as ACT216 whether the second status S2 of the registration mobile information file MFL1 is "0" or not. If the second status S2 is "0", the processor 41 determines YES in ACT216 and proceeds to ACT217. The processor 21 changes the second status S2 from "0" to "1" as ACT217. If the second status S2 has already been changed to "1", the processor 41 determines NO in ACT216 and skips the process of ACT217.

[0068] After finishing the process of ACT217 or skipping the process of ACT217, the processor 41 proceeds to ACT218. The processor 21 controls the communication interface 24 to send an update notification command as ACT218. By this control, the update notification command is 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 the data of the registration 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 with the terminal ID set in the command.

[0069] Return to the description of FIG. 8. The processor 61 of the mobile terminal 60 that controls the transmission of the product registration notification command returns to the waiting states of ACT105 to ACT107. In this waiting state, when an update notification command is received via the wireless device 64, the processor 61 determines YES in ACT106 and proceeds to ACT109. The processor 61 detects the data of the mobile information file MFL from the update notification command as ACT109. Then, based on that data, the processor 61 updates the registration screen as 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. Also, the processor 61 updates the total points and total amount in the total area. For error registration data, the processor 61 updates the registration screen so that data indicating the error content is displayed in the details area. Thus, after finishing updating the registration screen, the processor 61 returns to the waiting states of ACT105 to ACT107.

[0070] In this way, a consumer who shops using the mobile terminal 60 first activates the mobile terminal 60. Then, in the virtual POS server 20, a transaction information file TFL with the terminal ID of the mobile terminal 60 set is created. In the terminal controller 40, a mobile information file MFL with the same terminal ID set is created.

[0071] Next, the consumer reads the barcode of the purchased product with the scanner 66 of the mobile terminal 60. Then, this barcode data is transmitted to the virtual POS server 20 via the terminal controller 40. Here, if the barcode data indicates the product code of the purchased product, the virtual POS server 20 generates normal registration data related to the purchased product. And this normal registration data is stored in the transaction information file TFL. On the contrary, for example, if the barcode data does not indicate the product code of the purchased product, 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 the error registration data are stored in the 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 of the purchased product, the discount amount, etc. from the list displayed on the touch panel 65. The consumer can also check that a registration error has occurred.

[0074] Now, a consumer who has no problem with the price of the purchased product, the discount amount, etc. and has no registration error, after finishing shopping, touches the accounting button on the registration screen. When the accounting button is touched, the processor 61 of the mobile terminal 60 determines YES in ACT107 and proceeds to ACT111. The processor 61 controls the wireless device 64 to perform an accounting notification as ACT111. By this control, an accounting notification command is wirelessly transmitted from the wireless device 64. The accounting notification command is transmitted to the terminal controller 40 via the access point 50. The accounting notification command includes the terminal ID of the mobile terminal 60.

[0075] When the processor 41 of the terminal controller 40 receives the accounting notification command via the communication interface 44, it starts the information processing of the procedure shown in the flowchart of FIG. 11. The processor 41 detects the terminal ID from the accounting notification command as ACT221. Then, the processor 41 checks whether the second status S2 of the mobile information file MFL in which the terminal ID is set is "1" as ACT222. When 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 the processing for the accounting notification as an error.

[0076] When the second status S2 of the mobile information file MFL is “1”, the processor 41 determines 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”. Also, the processor 41 controls the communication interface 44 to issue an accounting request as ACT224. By this control, an accounting request command is output from the communication interface 44. The accounting request command is transmitted to the virtual POS server 20 via the communication network 80. The accounting request command includes the terminal ID detected from the accounting notification command. Hereinafter, the mobile information file MFL with the second status S2 changed from “1” to “2” is referred to as the accounting mobile information file MFL2.

[0077] When the processor 21 of the virtual POS server 20 receives an accounting request command via the communication interface 24, it starts the information processing of the procedure shown in the flowchart of FIG. 14. The processor 21 detects the terminal ID from the accounting request command as ACT331. Then, the processor 21 checks whether the first status S1 of the transaction information file TFL with the terminal ID set is “1” as ACT332. When 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 the processing for the accounting request as an error.

[0078] When the first status S1 of the transaction information file TFL is “1”, the processor 21 determines 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” as ACT333. Hereinafter, the transaction information file TFL with the first status S1 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 permission notice as ACT334. Through this control, an accounting permission notice command is output from the communication interface 24. The accounting permission notice command is transmitted to the terminal controller 40 via the communication network 80. The accounting permission notice command includes the terminal ID detected from the accounting request command.

[0080] Return to the description of FIG. 11. The processor 41 of the terminal controller 40 that sent the accounting request command waits for the accounting permission notice command as ACT225. When receiving the accounting permission notice command via the communication interface 44, the processor 41 determines YES in ACT225 and proceeds to ACT226. The processor 41 controls the communication interface 24 to issue an accounting execution notice as ACT226. Through this control, an accounting execution notice command is output from the communication interface 24. The accounting execution notice command is wirelessly transmitted from the access point 50 via the communication network 80. The accounting execution notice command includes the terminal ID detected from the accounting notice command. The accounting execution notice command wirelessly transmitted from the access point 50 is received by the mobile terminal 60 with the terminal ID set in the command.

[0081] Return to the description of FIG. 8. The processor 61 of the mobile terminal 60 that issued the accounting notice waits for the accounting execution notice as ACT112. When receiving the accounting execution notice command via the wireless device 64, the processor 61 determines YES in ACT112 and proceeds to ACT113. The processor 61 causes a barcode indicating the terminal ID to be displayed on the touch panel 65 as ACT113. Thus, the processor 61 ends the information processing for the usage start declaration.

[0082] Consumers who have confirmed that a barcode is displayed on the touch panel 65 head towards the accounting machine 30. Then, the consumer causes the barcode displayed on the touch panel 65 to be read by the scanner provided in the accounting machine 30. The barcode data read by the accounting machine 30 is output to the store server 10.

[0083] Return to the description of FIG. 14. The processor 21 of the virtual POS server 20 that has transmitted the accounting permission notification command controls the communication interface 24 so as to transmit the data of the accounting transaction information file TFL2 to the store server 10 as ACT335. By this control, the data of the accounting transaction information file TFL2 is output from the communication interface 24. This data is transmitted to the store server 10 via the communication network 80.

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

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

[0086] Return to the description of FIG. 11. The processor 41 of the terminal controller 40 that issued the accounting execution notification waits for an accounting end notification command as ACT227. When the processor 41 receives the accounting end notification command via the communication interface 44, it determines YES in ACT227 and proceeds to ACT228. The processor 41 changes the second status S2 of the accounting mobile information file MFL2 from "2" to "3" as ACT228. Thus, the processor 41 ends the reception process of the accounting notification command.

[0087] In this way, a consumer without problems such as the price of the purchased goods, discount amount, etc. and without registration errors can use the accounting machine 30 to settle the purchased goods by having the barcode displayed on the touch panel 65 of the mobile terminal 60 read by the scanner of the accounting machine 30.

[0088] However, consumers who notice that the price of the purchased item is different from the price tag or that the discount amount is different will generally inform the store clerk, who is called an attendant, before checkout. The same applies to consumers who have encountered a registration error. The store clerk who receives such a notice will use the monitoring terminal 70 to correct the error in the registration data. Next, the operation of correcting the error in the registration data using the monitoring terminal 70 will be described with reference to FIGS. 15 to 23.

[0089] FIGS. 15 to 17 are flowcharts showing the main information processing procedures executed by the processor 71 of the monitoring terminal 70 according to the monitoring support program APL2. FIG. 18 is a flowchart showing the information processing procedure 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 flowchart 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. FIGS. 20 to 23 are examples of various images displayed on the touch panel 75 of the monitoring terminal 70. Note that the operations described below are examples. The procedures and the like are not particularly limited as long as the same results can be 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 via a wireless LAN and transmitted to the terminal controller 40 via the communication network 80. The processor 41 of the terminal controller 40 that has received the collection command via the communication interface 44 collectively acquires 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] Thus, if the mobile information file MFL is collected from the terminal controller 40, the processor 71 stores the mobile information file MFL as ACT402. The storage destination of the mobile information file MFL may be the volatile memory area of the main memory 72 or the auxiliary storage device 73. Hereinafter, the collected mobile information file MFL will be referred to as the collected mobile information file MFL3.

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

[0093] FIG. 20 is an example of a display of the monitoring screen SC1. As shown in the figure, on the monitoring screen SC1, a status display area 90 of the mobile terminal 60 and a next page button BT1 are displayed. In the status display area 90, a total of 15 status display parts Tx are arranged in a 5-row × 3-column matrix. Incidentally, "x" in the status display part Tx indicates an integer of 1 or more. The next page button BT1 is an image of a button instructing to switch the status display parts Tx (T1 to T15) displayed in the status display area 90 to the next status display parts Tx (T16 to T30). After switching the status display area 90 to the next status display parts Tx (T16 to T30), the next page button B becomes the previous page button. Alternatively, the previous page button is displayed next to the next page button B. The previous page button is an image of a button instructing to return the other status display parts Tx (T16 to T30) displayed in the status display area 90 to the original status display parts Tx (T1 to T15). Such a next page button B and previous page button are an example of operators reproduced on the screen of the touch panel 75 by software. Note that the layout of the monitoring screen SC1 is not particularly limited.

[0094] Each of the plurality of status display parts 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 for identifying whether the corresponding mobile terminal 60 is in a standby state, a registration state, or a checkout state, respectively. 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 the start of product registration, "Standby" lights up for the first mark M1. When the second status S2 is "1" indicating the second state after the start of product registration, "Registering" lights up for the first mark M1. When the second status S2 is "2" indicating the third state after the checkout declaration, "Checking out" lights up for the first mark M1. Note that the mobile information file MFL in which the second status S2 indicates "3" of the fourth state after the checkout is completed is not collected. Therefore, the status display unit 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 a store clerk in charge of an attendant who is an operator of the monitoring terminal 70 receives a request to modify registration data, for example, from a consumer, the store clerk recognizes the terminal ID of the mobile terminal 60 used by the consumer for product registration. For example, on the touch panel 65 of each mobile terminal 60, the terminal ID set for the mobile terminal 60 is displayed, so the store clerk recognizes the terminal ID of the mobile terminal 60 from this display.

[0097] The store clerk who has recognized the terminal ID searches for the status display unit Tx1 on which the terminal ID is displayed from among the plurality of status display units Tx displayed in the status display area 90. When the corresponding status display unit Tx1 is found, the store clerk touches the status display unit Tx1. Then, the store clerk designates the mobile terminal 60 in which the registration data requested for correction by the consumer has been registered.

[0098] Return to the description of FIG. 15. The processor 71 of the monitoring terminal 70 that has displayed the monitoring screen SC1 is waiting for the mobile terminal 60 to be designated as ACT404. When the processor 71 detects that the mobile terminal 60 has been designated by the operation of the store clerk described above, it determines YES in ACT404 and proceeds to ACT405. The processor 71 acquires the terminal ID of the designated mobile terminal 60 as ACT405. Then, the processor 71 checks the second status S2 of the collected mobile information file MFL3 in which the terminal ID is set as ACT406. Here, when the second status S2 is "1", the processor 71 causes the list LS1 (see FIG. 22) of the registration data registered in the area B2 to be displayed on the touch panel 75.

[0099] FIG. 22 is an example of a display of an image SC2 including the list LS1. In the image SC2, the status display unit Tx of the designated mobile terminal 60 and the list LS1 of the registration data by the mobile terminal 60 are displayed. In the list LS1, for the normal registration data, the product name, score, and price are displayed. For the error registration data, information indicating the error content is displayed. Also, a selection button BT2 is displayed in association with each registration data. Further, an addition button BT3 and an end button BT4 are also displayed in the image SC2. Such selection buttons BT2, addition button BT3, and end button BT4 are an example of an operator reproduced on the screen of the touch panel 75 by software. Note that the layout of the image SC2 is not particularly limited.

[0100] Now, when a store employee who has checked the list LS1 receives a request from a consumer to modify registration data, the employee touches the selection button BT2 associated with the registration data. Also, when the store employee receives a request for new product registration, the employee touches the add button BT3. When the store employee finishes checking the list LS1, the employee touches the end button BT4.

[0101] Return to the description of FIG. 15.

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

[0103] In the waiting state of ACT408 to ACT410, when the selection button BT2 is touched, the processor 71 determines YES in ACT408 and proceeds to ACT421 in FIG. 16. The processor 71 checks whether the registration data associated with the selection button BT2 is normal registration data or error registration data as ACT421. If the registration data is normal registration data, the processor 71 determines YES in ACT421 and proceeds to ACT422. The processor 71 causes the edit popup image SC3 (see FIG. 23) to be displayed on the touch panel 75 as ACT422.

[0104] Figure 23 shows an example of the display of the editing pop-up image SC3. As shown in the figure, the product name of the normal registration data selected by the selection button BT2 is displayed in the editing pop-up image SC3. In addition, an editing area ED1 for quantity, unit price, discount amount, and total amount is displayed in the editing pop-up image SC3. And in the editing area ED1, the quantity (number of items), unit price (price), discount amount, and total amount of the normal registration data are displayed. Incidentally, the total amount is the amount obtained by subtracting the discount amount from the amount obtained by multiplying the unit price by the quantity. Further, an OK button BT5 and a cancel button BT6 are displayed in the editing area ED1. Such an OK button BT5 and cancel button BT6 are an example of operators reproduced on the screen of the touch panel 75 by software. Note that the layout of the editing pop-up image SC3 is not particularly limited.

[0105] For example, when the store clerk receives a notice from the consumer that the price in the normal registration data is incorrect and can confirm the error, the store 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, the numeric keypad buttons are displayed, so the store clerk operates the numeric keypad buttons to enter the correct unit price into the unit price area. Similarly, when the store clerk receives a notice from the consumer that the discount amount in the normal registration data is incorrect and can confirm the error, the store clerk operates the touch panel 75 to correct the discount amount in the editing area ED1 to the correct amount. And after finishing the correction in the editing area ED1, the store clerk touches the OK button BT5. On the other hand, when the store clerk receives a cancellation request for the normal registration data from the consumer, the store clerk touches the cancel button BT6.

[0106] Return to the description of FIG. 16. The processor 71 of the monitoring terminal 70 that has displayed the editing popup image SC3 checks whether the cancel button BT6 has been touched as ACT423. If the cancel button BT6 has not been touched, the processor 71 determines NO in ACT423 and proceeds to ACT424. The processor 71 checks whether the confirmation button BT5 has been touched as ACT424. If the confirmation button BT5 has not been touched, the processor 71 determines NO in ACT424 and returns to ACT423. Here, the processor 71 waits for the cancel button BT6 to be touched or the confirmation button BT5 to be touched in ACT423 and ACT424.

[0107] In the waiting state of ACT423 and ACT424, if the confirmation button BT5 is touched, the processor 71 determines YES in ACT424 and proceeds to ACT425. The processor 71 edits the normal registration data as ACT425. That is, for example, when the unit price in the editing area ED1 is corrected, the processor 71 rewrites the price of the corresponding normal registration data to the corrected amount. For example, when the discount amount in the editing area ED1 is corrected, the processor 71 rewrites the discount amount of the corresponding normal registration data to the corrected amount. Then, 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 error-registered data, the processor 71 determines NO in ACT421. Also, if the cancel button BT6 of the edit popup image SC3 is touched, the processor 71 determines YES in ACT423. And in either case, the processor 71 proceeds to ACT426. The processor 71 deletes the registered data as ACT426. That is, if the registered data associated with the selection button BT2 is error-registered data, the processor 71 deletes that error-registered data from the collection 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 collection mobile information file MFL3. After that, the processor 71 proceeds to ACT427.

[0109] The processor 71 controls the wireless device 74 to perform a correction notification as ACT427. By this control, a correction notification command is wirelessly transmitted from the wireless device 74. The correction notification command is received by the access point 50 connected by a wireless LAN and transmitted to the terminal controller 40 via the communication network 80. The correction notification command includes the data of the collection mobile information file MFL3 in which the registered data is edited.

[0110] When the processor 41 of the terminal controller 40 receives the correction notification command via the communication interface 44, it starts the information processing of the procedure shown in the flowchart of FIG. 18. The processor 41 acquires the registered data from the collection mobile information file MFL3 included in the correction notification command as ACT231. Then the processor 41 corrects the registered data of the mobile information file MFL with the same terminal ID set as that of the collection mobile information file MFL3 to match the registered data acquired from the collection mobile information file MFL3 as ACT232.

[0111] After finishing the modification of the mobile information file MFL, the processor 41 checks whether there is a modification to change the normal registration data as ACT233. If there is no modification to change the normal registration data, the processor 41 determines NO in ACT233 and ends the reception process of the modification notification command.

[0112] On the other hand, if there is a modification to change the normal registration data, the processor 41 determines YES in ACT233 and proceeds to ACT234. The processor 41 controls the communication interface 44 to issue a modification request. Thus, the processor 41 ends the reception process of the modification notification command. With this control, a modification request command is output from the communication interface 44. The modification request command is transmitted to the virtual POS server 20 via the communication network 80. The modification request command includes the data of the mobile information file MFL whose normal registration 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 the information processing of the procedure shown in the flowchart of FIG. 19. The processor 21, as ACT341, acquires the normal registration data from the mobile information file MFL included in the modification request command. Then, the processor 21, as ACT342, modifies the normal registration data of the transaction information file TFL with the same terminal ID set as that of the mobile information file MFL to match the normal registration data acquired from the mobile information file MFL. Thus, the processor 21 ends the reception process of 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 content 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 content is reflected in the transaction information file TFL stored in the virtual POS server 20.

[0115] Return to the description of FIG. 15. When the additional button BT3 is touched in the standby state of ACT408 to ACT410, the processor 71 determines YES in ACT409 and proceeds to ACT431 in FIG. 17. The processor 71 waits for product registration as ACT431.

[0116] A store clerk who has received a product registration request from a consumer reads the barcode attached to the product using the scanner 76. 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 send a product registration notification as 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 barcode data read by the scanner 76 and the terminal ID associated with the designated status display unit Tx.

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

[0118] Therefore, when the barcode of a product is scanned at the monitoring terminal 70, the 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 designated terminal ID, respectively.

[0119] When the end button BT4 is touched in the standby state of ACT408 to ACT410, the processor 71 determines YES in ACT410 and proceeds to ACT411. The processor 71 erases the image SC2 as 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 are provided with receiving means. That is, the terminal controller 40 receives the 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 the 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 provided with 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, points, discount amount, etc. of the purchased product. The normal registration data is an example of product sales data. The error registration data includes the barcode data. The error registration data is an example of data based on the purchased product for which product sales data could not be generated.

[0122] The virtual POS server 20 is provided with first storage means, and the terminal controller 40 is provided with second storage means. That is, the virtual POS server 20 stores the normal registration data in the transaction information file TFL. The terminal controller 40 stores the normal registration data and the error registration data in the mobile information file MFL.

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

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

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

[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 the correction of the normal registration data or error registration data displayed in the list LX1. Then, the monitoring terminal 70 outputs a correction notification command to the terminal controller 40 to give a correction instruction.

[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 error registration data stored in the mobile information file MFL according to the correction notification command. Also, the terminal controller 40 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 according to the correction request command.

[0128] The monitoring terminal 70 is provided with input means. That is, the monitoring terminal 70 inputs the data of the barcode read by the scanner 76 as data based on the purchased goods. Then, the monitoring terminal 70 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 additional means. That is, the terminal controller 40 adds normal registration data to the mobile information file MFL according to the product registration notification command. Also, the terminal controller 40 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 according to the product registration request command.

[0130] According to the store system 100 including the monitoring terminal 70, the terminal controller 40, and the virtual POS server 20 having such a configuration, even if there is an error in the data input by the consumer via the mobile terminal 60, the store clerk can operate the monitoring terminal 70 to correct the error without discarding the data. Therefore, the load required for data processing of the terminal controller 40 and the virtual POS server 20 that process the data input via the mobile terminal 60 can be reduced.

[0131] Also, since there is no need for the consumer or the store clerk to re-enter the data into the cash register 30, the processing time required for accounting is also shortened. Also, the human load is reduced. Therefore, efficient store operation can be achieved.

[0132] As described above, the embodiments of the store system 100 have been described, but such embodiments are not limited thereto. In the above-described embodiment, the server of the store system 100 is configured 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 aggregated into the mobile information file MFL. In that case, in the accounting machine 30, if error registration data is included in the mobile information file MFL, the settlement process may be regarded as an error. By doing so, a store system can be realized that includes a server having a receiving means, a generating means, a storage means, and a correcting means, and a monitoring terminal 70 having an acquiring means and a correction instruction means. Also, a store system 100 in which the monitoring terminal 70 has a selection means and an input means and the server has an adding means can be realized. Furthermore, a store system 100 in which the monitoring terminal 70 has a display means can be realized.

[0133] Also, the generating means is not necessarily required. That is, the server receives data based on the purchased goods input by each of the plurality of mobile terminals 60 and stores it in the mobile information file MFL. The monitoring terminal 70 acquires data based on the purchased goods input by any one of the mobile terminals 60 from the data stored in the mobile information file MFL and instructs a correction. The server executes the instructed correction on the data stored in the mobile information file MFL. Even in a store system having such a configuration, when there is an error in the data input via the mobile terminal 60, the error can be corrected without discarding the data, and the load required for data processing of the server can be reduced.

[0134] In the above-described 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 that has received 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, an RFID reader, or the like.

[0136] In addition, although some embodiments of the present invention have been described, these embodiments are presented by way of example and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the gist of the invention. These embodiments and their modifications are included in the scope of the invention and are included in the invention described in the claims and the equivalent scope thereof.

Explanation of Reference Numerals

[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. Receiving means for receiving data based on purchased goods respectively input by a plurality of mobile terminals; Storage means for storing data based on the purchased goods received by the receiving means; A server comprising: Obtaining means for obtaining data based on the purchased goods input by any one of the mobile terminals from the data stored in the storage means; Modification instruction means for instructing modification of the data obtained by the obtaining means; A store terminal comprising: Including The server Further comprises modification means for executing the modification instructed by the modification instruction means on the data stored by the storage means, A store system.

2. The store terminal Selection means for selecting the mobile terminal; Input means for inputting data based on the purchased goods; Further comprising The server Further comprises adding means for adding the data based on the purchased goods input by the input means as the data based on the purchased goods input from the mobile terminal selected by the selection means to the storage means, The store system according to Claim 1.

3. The store terminal Display means for displaying a list of data based on the purchased goods input by the mobile terminal selected by the selection means; Further comprising The modification instruction means instructs modification of the data displayed in the list, The store system according to Claim 2.

4. Receiving means for receiving data based on purchased goods respectively input by a plurality of mobile terminals; Generating means for generating product sales data based on the data based on the purchased goods received by the receiving means; First storage means for storing the product sales data generated by the generating means; Second storage means for storing the product sales data generated by the generating means and the data based on the purchased goods for which the generation of the product sales data did not reach; A server comprising: Obtaining means for obtaining the product sales data generated based on the data based on the purchased goods input by any one of the mobile terminals and the data based on the purchased goods for which the generation of the product sales data did not reach from the data stored in the second storage means; Modification instruction means for instructing modification of the product sales data or the data based on the purchased goods obtained by the obtaining means; A store terminal comprising: Including The server For the data stored by the first storage means and the second storage means, a correction means for executing the correction instructed by the correction instruction means; A store system further comprising.

5. The store terminal is A selection means for selecting the mobile terminal; An input means for inputting data based on the purchased goods; Further comprising The server is Additional means for adding the product sales data generated based on the data of the purchased goods input by the input means to the first storage means and the second storage means as the data generated based on the data of the purchased goods input from the mobile terminal selected by the selection means; The store system according to claim 4, further comprising.

6. The store terminal is Display means for displaying a list of product sales data generated from the data of the purchased goods input by the mobile terminal selected by the selection means and the data of the purchased goods that did not lead to the generation of the product sales data; Further comprising The correction instruction means instructs the correction of the data displayed in the list. The store system according to claim 5.

Images