Information processing terminals and information processing programs

Abstract

To provide a technique for preventing product registration forgetting and also unauthorized registration.SOLUTION: An information processing terminal according to an embodiment includes a determination unit, a display control unit, an acquisition unit, and a transmission unit. The determination unit determines whether information regarding registration of a product satisfies image capturing conditions. The display control unit causes a display unit to display guidance on automatic image capturing of the product based on determination results by the determination unit. The acquisition unit acquires captured image data of the imaged product based on automatic image capturing of the product. The transmission unit transmits the captured image data acquired by the acquisition unit.SELECTED DRAWING: Figure 17

Description

Technical Field

[0001] Embodiments of the present invention relate to an information processing terminal and an information processing program.

Background Art

[0002] There is already known a transaction processing system in which, when a customer shops at a sales floor where goods are displayed, the customer operates a mobile terminal such as a smartphone or a tablet-type terminal by himself / herself to input data related to the purchased goods.

[0003] This type of transaction processing system processes the accounting of customers who self-enter data related to the purchased goods placed in a shopping basket or the like, that is, so-called self-service customers, using a dedicated self-checkout machine. In such a system, in order to prevent customers from forgetting to register goods or making unauthorized registrations, measures are taken such as having a store clerk confirm at the accounting area the purchased goods placed in the shopping basket or the like by the customer and the registered goods at the time of accounting.

[0004] However, it is difficult to check all customers and all purchased goods against each other. Therefore, measures for preventing forgetting to register and unauthorized registration in advance are required.

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0006] The problem to be solved by the embodiments of the present invention is to provide a technique for preventing forgetting to register goods and unauthorized registration.

Means for Solving the Problems

[0007] In one embodiment, the information processing terminal comprises a determination unit, a display control unit, an acquisition unit, and a transmission unit. The determination unit determines whether the information regarding product registration satisfies the shooting conditions. Based on the determination result of the determination unit, the display control unit displays automatic product shooting guidance on the display unit. The acquisition unit acquires the captured image data of the product based on the automatic product shooting. The transmission unit transmits the captured image data acquired by the acquisition unit. [Brief explanation of the drawing]

[0008] [Figure 1] Figure 1 is a block diagram showing a schematic configuration of a transaction processing system according to one embodiment. [Figure 2] Figure 2 is a perspective view showing an example of a shopping cart according to one embodiment. [Figure 3] Figure 3 is a sequence diagram used to explain the actions a customer takes before making a purchase using the transaction processing system. [Figure 4] Figure 4 is a sequence diagram used to explain the actions of the customer during and before checkout. [Figure 5] Figure 5 is a sequence diagram used to explain the operation of the customer's dedicated payment machine. [Figure 6] Figure 6 is a schematic diagram showing an example of an entry code reading screen displayed on a smartphone according to one embodiment. [Figure 7] Figure 7 is a schematic diagram showing an example of a registration screen displayed on a smartphone according to one embodiment. [Figure 8] Figure 8 is a schematic diagram showing an example of a scanning screen displayed on a smartphone according to one embodiment. [Figure 9] Figure 9 is a schematic diagram showing an example of a registration screen displayed on a smartphone according to one embodiment. [Figure 10] Figure 10 is a schematic diagram showing an example of an accounting screen displayed on a smartphone according to one embodiment. [Figure 11] Figure 11 is a block diagram schematically showing an example of the configuration of a monitoring server according to one embodiment. [Figure 12] FIG. 12 is a block diagram schematically showing a configuration example of a smartphone according to an embodiment. [Figure 13] FIG. 13 is a block diagram schematically showing a configuration example of a monitoring terminal according to an embodiment. [Figure 14] FIG. 14 is a diagram showing a main data structure of a first index file stored in a transaction data storage area according to an embodiment. [Figure 15] FIG. 15 is a diagram showing a main data structure of a first transaction file stored in a transaction data storage area according to an embodiment. [Figure 16] FIG. 16 is a diagram showing a main data structure of photographed image management data stored in a photographed image storage area according to an embodiment. [Figure 17] FIG. 17 is a schematic diagram showing an example of a guidance screen displayed on a smartphone according to an embodiment. [Figure 18] FIG. 18 is a flowchart showing an example of a procedure for information processing by a smartphone according to an embodiment. [Figure 19] FIG. 19 is a schematic diagram showing an example of a photographing guide screen displayed on a smartphone according to an embodiment. [Figure 20] FIG. 20 is a flowchart showing another example of a procedure for information processing by a smartphone according to an embodiment. [Figure 21] FIG. 21 is a schematic diagram showing an example of a registered product details screen displayed on a monitoring terminal according to an embodiment. [Figure 22] FIG. 31 is a schematic diagram showing an example of a registered product confirmation screen displayed on a monitoring terminal according to an embodiment. [Figure 23] FIG. 23 is a schematic diagram showing an example of a registered product confirmation screen displayed on a monitoring terminal according to an embodiment. [Figure 24] FIG. 24 is a flowchart showing an example of a procedure for information processing by a monitoring terminal according to an embodiment.

BEST MODE FOR CARRYING OUT THE INVENTION

[0009] Hereinafter, an embodiment will be described with reference to the drawings. In this embodiment, when a customer purchases a product at a sales floor where products are displayed, the customer operates a smartphone, which is a mobile terminal, by himself / herself to input data related to the purchased product, and accounting is also performed self-service using a dedicated accounting machine. The smartphone is an example of an information processing device operated by the customer. In the following description, the customer may be read as a user, a consumer, or a member.

[0010] [Configuration of Transaction Processing System 100] FIG. 1 is a block diagram showing a schematic configuration of a transaction processing system 100 according to this embodiment. The transaction processing system 100 includes a server system 10 using cloud computing and a POS (Point Of Sales) system 20 constructed in a franchise store. The server system 10 and the POS system 20 enable two-way data communication through a network 30 using the Internet protocol. The network 30 is a wide-area network that uses a public line or a dedicated line as a relay network and a wired LAN (Local Area Network), a wireless LAN, a mobile communication network, a mobile phone communication network, etc. as access networks. Therefore, a smartphone 40 using a mobile phone communication network can access the server system 10 via the network 30.

[0011] A franchise store is a store that has concluded a usage contract with the management company of the server system 10. In FIG. 1, a POS system 20 of one franchise store is shown. Needless to say, the POS systems of other franchise stores are also connected to the network 30 in the same manner. However, the POS systems of other franchise stores are not necessarily of the same configuration as the POS system 20 shown in FIG. 1. There may be cases where a part of the configuration of the POS system differs depending on the franchise store.

[0012] The server system 10 comprises a database server 11, a management server 12, and a virtual POS server 13, with each server connected by a communication line 14. The server system 10 also connects a router 15 to the communication line 14, and connects to the network 30 via this router 15.

[0013] The database server 11 is a computer that provides services for managing the merchant database 111, the member database 112, the first product master 113 for each merchant, etc.

[0014] The merchant database 111 is a collection of merchant records created for each merchant. A merchant record is a data record that records a unique store ID set for each merchant and various data related to that merchant. The data in a merchant record includes the network address and other information necessary for data communication between the merchant and the network 30.

[0015] The member database 112 is a collection of member records created for each consumer who has registered as a member in order to make purchases using the transaction processing system 100. Each member record is a data record that records a unique member ID set for each consumer and various data about that consumer.

[0016] Each member store's first product master 113 is a collection of product records created for each product sold at the corresponding member store. A product record is a data record that records a unique product code assigned to each product and various data related to that product. The data in a product record includes the product name, price, etc. Each first product master 113 is uploaded from the corresponding member store's POS system 20 to the database server 11, for example, at a predetermined time before opening.

[0017] Incidentally, the first product master 113 may be managed by the virtual POS server 13. Alternatively, the management server 12 can manage the merchant database 111 and the member database 112, and the database server 11 can be omitted.

[0018] The management server 12 is a computer that works in cooperation with the database server 11 and the virtual POS server 13 to provide a service that manages information related to customer transactions when customers shop at affiliated stores using the transaction processing system 100. The virtual POS server 13 is a computer that provides a service that virtually registers sales data of products purchased by customers according to the POS application. The main functions of the management server 12 and the virtual POS server 13 will be clarified in the operation description below.

[0019] The POS system 20 comprises a store server 21, an accounting server 22, a monitoring terminal 23, a POS terminal 24, a dedicated accounting machine 25, and a monitoring server 26, all connected via an in-store network 27. The POS system 20 also connects a router 28 to the in-store network 27, and through this router 28, connects to network 30. Furthermore, the POS system 20 connects an access point 29 to the in-store network 27, enabling wireless LAN data communication with mobile devices such as smartphones 40 and tablet terminals via this access point 29.

[0020] The store server 21 is a computer that provides services for managing sales information, product inventory information, and order information of a merchant based on transaction information settled at the merchant where the POS system 20 is installed.

[0021] The store server 21 includes a second product master 211. The second product master 211 is a collection of product records created for each product sold at the affiliated store. A product record is a data record that records a unique product code set for each product and various data related to that product. The data in a product record includes the product name, price, etc. In other words, the second product master 211 becomes the first product master 113 when uploaded to the server system 10. However, if the price, etc., changes during business hours, the change is reflected in the data of the second product master 211. Therefore, the price, etc., may differ between the first product master 113 and the second product master 211 for some products.

[0022] The store server 21 is a computer that provides services to support the member monitoring function of the monitoring terminal 23. The member monitoring function monitors the status of customers who are shopping using the transaction processing system 100. With this member monitoring function, the monitor of the monitoring terminal 23 displays a list of registered products that the customer has entered data for using their smartphone 40 at the sales floor. Registered products are products that the customer has entered data for using their smartphone 40 before payment. Registered products are also simply called products. The monitoring terminal 23 displays monitoring images on its monitor. Monitoring images are images for monitoring information on registered products entered using the smartphone 40, as well as the status of the smartphone 40, etc. Monitoring images include the list of registered products and images of purchased products, etc. Purchased products are products that the customer intends to purchase and has placed in their shopping cart, etc., before payment. The member monitoring function includes a function to compare the customer's registered product information with the purchased products for the monitored target. Monitored targets include products that are suspected of being forgotten to be registered or fraudulently registered, or product registrations. In addition, the monitor displays a warning if an event occurs that should be reported to store staff due to the data entry. Examples of situations that should be reported to store staff include when a customer purchases alcohol or cigarettes with age restrictions, or when a registration error occurs because the product code of the scanned barcode is not set in the second product master 211.

[0023] The accounting server 22 is a computer that provides services to support members' accounting using the dedicated accounting machine 25. The functions of the accounting server 22 will be clarified in the operation description below.

[0024] The POS terminal 24 is primarily an accounting machine for settling transactions with customers who do not use the transaction processing system 100. The POS terminal 24 is operated by a store employee. The POS terminal 24 can also settle transactions with customers who do use the transaction processing system 100. The POS terminal may be a semi-self-service POS terminal, separated into a registration machine and a payment machine, with the registration machine operated by a store employee and the payment machine operated by the customer. The POS terminal may also be a fully self-service POS terminal, where the customer performs both the registration and payment processing themselves.

[0025] The dedicated accounting machine 25 is an accounting machine for settling transactions with customers using the transaction processing system 100. The dedicated accounting machine 25 is operated by the customer. Customers who do not use the transaction processing system 100 cannot settle transactions using the dedicated accounting machine 25.

[0026] The dedicated accounting machine 25 has functions such as scanning an accounting barcode displayed on a smartphone 40 used by a customer using the transaction processing system 100, processing payments for various payment methods such as electronic money, credit cards, and cash, and charging electronic money.

[0027] The monitoring server 26 is a computer that works in conjunction with the server system 10 to monitor information on registered products entered by customers using their smartphones 40 at the sales floor. The monitoring server 26 works in conjunction with the store server 21 to perform information processing to enable the member monitoring function by the monitoring terminal 23. The functions of the monitoring server 26 will be clarified in the operation description below. The monitoring server 26 is an example of an information processing device.

[0028] [Shopping cart structure] Figure 2 is a perspective view showing an example of a cart C according to one embodiment. The cart C comprises a caster section C1 for movement, a handle frame section C2, and a basket support section C3. The caster section C1 has four wheels for smooth movement on the floor. The handle frame section C2 includes a pair of vertical frames C21, C21 erected on the rear wheel side of the caster section C1, and a handle bar C22 connecting the upper ends of these vertical frames C21, C21. The basket support section C3 is located in front of the middle part of the handle frame section C2. The cart C can accommodate a shopping basket BA provided by the store on the basket support section C3 and its lower part.

[0029] A pole C4 is attached to one of the vertical frames C21 of the cart C. A stand 400 for a smartphone 40 is provided at the tip of the pole C4. Consumers using the cart C can place their own smartphone 40 on the stand 400 and shop.

[0030] [Operation of Transaction Processing System 100] Next, we will explain the main operations of the transaction processing system. The operations will be explained in the following order: preparation, before shopping, during shopping, before payment, and payment.

[0031] <Preparation> Consumers who wish to shop at participating stores using the transaction processing system 100 first install a dedicated application program (hereinafter referred to as the shopping app) on their smartphone 40 and register as members. Member registration is performed via the network 30 to the management server 12 of the server system 10. The management server 12 issues a unique member ID to the registered consumer and registers a member record containing that member ID in the member database 112. The management server 12 also notifies the registered consumer's smartphone 40 of the member ID via the network 30. The smartphone 40 stores the member ID in association with the shopping app.

[0032] By registering as a member, consumers become members. Members can register to use electronic money that can be used at participating stores. Registration is performed from a smartphone 40 via the network 30 to the management server 12. The management server 12 records the electronic money ID of the registered electronic money in the member record, which contains the member ID of the member. Note that registration of electronic money is not mandatory.

[0033] <Before shopping (see Figures 3 and 6)> Before entering a participating store, members operate their smartphone 40 to launch the shopping app. When the shopping app is launched, the touch panel screen on the smartphone 40 transitions to the store entry code reading screen Sa (Figure 6). The store entry code reading screen Sa is used to read the store entry code Cin (Figure 3) with the camera installed in the smartphone 40.

[0034] The entry code Cin is available at the entrance of the participating store. For example, the entry code Cin may be printed on paper and posted at the entrance. For example, the entry code Cin may be displayed on a screen placed at the entrance. The entry code Cin is a code representing the settings information of the participating store, for example, using a two-dimensional code system. The settings information includes the store ID set for the participating store, wireless LAN data, etc. The wireless LAN data includes the SSID, password, security information, etc., necessary for the smartphone 40 to connect to the access point 29 using wireless LAN.

[0035] As shown in Figure 6, the entry code reading screen Sa displays a camera activation button Ba. The member touches the camera activation button Ba. This activates the camera on the smartphone 40, and the member points the camera lens at the entry code Cin. The camera scans the entry code Cin.

[0036] When the entry code Cin is scanned, the smartphone 40 sends an entry request command CMa (Figure 3) to the management server 12 via the network 30. The entry request command CMa includes at least the member ID and the store ID contained in the entry code Cin.

[0037] The management server 12 obtains the member ID from the entry request command CMa and performs member authentication (Figure 3, ACT1). Member authentication is performed by checking whether the member ID is managed as a valid member ID. For example, a member record containing the member ID of a consumer who has lost membership status due to reasons such as withdrawal application or fraudulent activity has an invalid flag recorded. If the management server 12 obtains the member ID of a member record with an invalid flag recorded from the entry request command CMa, it denies member authentication. If the management server 12 obtains the member ID of a member record with no invalid flag recorded from the entry request command CMa, it approves member authentication.

[0038] The management server 12 determines whether to approve or deny the member authentication (Figure 3, ACT2). If the member authentication is denied, the management server 12 sends an entry denial command CMb back to the smartphone 40. The entry denial command CMb is sent to the smartphone 40 via the network 30. Upon receiving the entry denial command CMb, the smartphone 40 stops the shopping app. Therefore, the customer cannot perform so-called self-service shopping at the affiliated store, where they operate the smartphone 40 themselves to input data related to the purchased items.

[0039] The management server 12 issues a transaction ID if it approves the member authentication (Figure 3, ACT3). The transaction ID is a unique ID assigned to each purchase, i.e., a transaction of buying and selling goods, each time a member makes a purchase at a participating store. For example, a unique transaction ID is issued by combining the store code, date, and sequential number. The management server 12 associates the member ID and store ID obtained from the entry request command CMa with the issued transaction ID and writes it to the linkage table 70 (Figure 3). In other words, the linkage table 70 is a data table that stores the member ID of a consumer making a self-service purchase, associating it with the store ID of the participating store where the purchase is made and the unique transaction ID issued for that transaction.

[0040] The management server 12 sends an entry approval command CMc to the smartphone 40. The entry approval command CMc is sent to the smartphone 40 via the network 30. Upon receiving the entry approval command CMc, the smartphone 40 connects to the access point 29 via wireless LAN using wireless LAN data obtained from the entry code Cin. Once the smartphone 40 is connected to the access point 29 via wireless LAN, the touch panel screen transitions to the shopping start screen. The shopping start screen prompts the consumer to begin shopping. The shopping start screen displays a shopping start button.

[0041] Meanwhile, the management server 12, which sent the entry approval command CMc, sends a transaction file creation instruction command CMd to the virtual POS server 13. The creation instruction command CMd includes the store ID and transaction ID stored in association with the member ID in the linkage table 70. Upon receiving the creation instruction command CMd, the virtual POS server 13 creates a transaction file 80 (Figure 3) in its storage unit. The virtual POS server 13 then writes the store ID and transaction ID included in the creation instruction command CMd into the transaction file 80. The transaction file 80 is a data file that records the sales data of the goods purchased by the member identified by the transaction ID, and the payment data for the settlement amount of that transaction.

[0042] <Shopping (see Figures 4, 7, 8, and 9)> After viewing the shopping start screen, the member touches the shopping start button. The touch panel screen then transitions to the registration screen Sb (Figure 7). As shown in Figure 7, the registration screen Sb displays the total number of items and the total amount of the items to be registered. However, since the purchased items have not yet been registered, both the total number of items and the total amount are "0". The registration screen Sb also displays the no barcode button Bb, the scan button Bc, and the checkout button Bd. The no barcode button Bb is the button to touch when entering data for items without barcodes. The scan button Bc is the button to touch when entering data for items with barcodes. The checkout button Bd is the button to touch when the shopping is finished and the user wants to proceed to checkout. However, since the items have not yet been registered, the checkout button Bd is disabled. For example, the checkout button Bd is grayed out. The checkout button Bd may also be hidden.

[0043] When a member finds an item they wish to purchase in the sales area where the products are displayed, they check whether the item has a barcode BC (Figure 4). If barcode BC is present, the member touches the scan button Bc. When the scan button Bc is touched, the touch panel screen transitions to the scanning screen Sc (Figure 8). As shown in Figure 8, the scanning screen Sc displays a frame ARa indicating the barcode reading area. It also displays a no-barcode button Bb and a back button Be. The back button Be is touched to cancel the scanning of barcode BC.

[0044] The member operates the smartphone 40 so that the barcode BC of the purchased product is within the frame ARa. When the barcode BC is within the frame ARa, it is scanned by the camera of the smartphone 40.

[0045] The smartphone 40, having scanned the barcode BC, sends a registration request command CMe (Figure 4) to the management server 12 via the wireless LAN. The registration request command CMe includes the member ID and the data of the barcode BC, also known as barcode data. The registration request command CMe is received by the access point 29 and then sent from the router 28 to the management server 12 via the network 30.

[0046] The management server 12 searches the linkage table 70 using the member ID included in the registration request command CMe and retrieves the store ID and transaction ID associated with that member ID. Then, the management server 12 sends a registration request command CMf to the virtual POS server 13, in which the member ID has been replaced with the store ID and transaction ID.

[0047] The virtual POS server 13 obtains the store ID, transaction ID, and barcode data from the registration request command CMf. The virtual POS server 13 then obtains the product code from the barcode data. The virtual POS server 13 searches the first product master 113 of the affiliated store identified by the store ID and obtains the product record containing the product code. The virtual POS server 13 then registers product sales data, consisting of product code, product type, product name, price, number of units sold, sales amount, etc., based on the product data of that product record, in the transaction file 80 which contains the store ID and transaction ID.

[0048] The management server 12 retrieves the transaction file 80 containing the product sales data from the virtual POS server 13. The management server 12 then sends a registration response command CMg (Figure 4) to the smartphone 40, which is the source of the registration request command CMe. The registration response command CMg contains the data from the transaction file 80 retrieved from the virtual POS server 13. The registration response command CMg is sent from the router 15 to the POS system 20 via the network 30, and then from the access point 29 to the smartphone 40.

[0049] Upon receiving the registration response command CMg, the smartphone 40 transitions to the registration screen Sd (Figure 9). The registration screen Sd is displayed when the sales data for the first item, item AAA, has been registered in the transaction file 80. As shown in Figure 9, the registration screen Sd displays the sales price of item AAA, "¥100", and the number of items sold, "1 item". The total number of items becomes "1 item", and the total amount becomes "¥100". The payment button Bd becomes available for input.

[0050] From this point onward, the member touches the scan button Bc to scan the barcode of each additional item purchased. As a result, the management server 12 and the virtual POS server 13 operate in the same manner as described above. Consequently, the registration screen Sd displays the product name, sales price, and number of items sold, as well as the total number of items and the total sales price.

[0051] As mentioned earlier, the sales amount of the product sales data stored in transaction file 80 is calculated based on the price in the first product master 113. This price in the first product master 113 is not reflected even if there is a price change during business hours. Therefore, the sales amount and total amount displayed on the registration screen Sd may differ from the amount based on the current price. For this reason, the sales amount and total amount displayed on the registration screen Sd should be considered merely as reference amounts during the shopping process.

[0052] If the purchased item does not have a barcode, the member touches the "No Barcode" button Bb. A list of items without barcodes is then displayed on the touch panel of the smartphone 40, and the member selects the item they wish to purchase from this list. A registration request command CMe, including the product ID of the purchased item, is then sent to the management server 12. Subsequent operations are the same as when the product's barcode BC is scanned with the smartphone 40.

[0053] <Before payment (see Figures 4 and 10)> When a member finishes shopping at the store and proceeds to checkout, they touch the checkout button Bd on the registration screen Sd. When the checkout button Bd is touched, the smartphone 40 sends a checkout request command CMh (Figure 4) to the management server 12 via the wireless LAN. The checkout request command CMh includes the member ID. The checkout request command CMh is received by the access point 29 and sent from the router 28 to the management server 12 via the network 30.

[0054] The management server 12 issues an accounting code (Figure 4, ACT11). The accounting code is a combination of, for example, a date, time, and a sequential number, and no duplicate accounting codes are issued for at least one business day. The management server 12 generates a first image Ca (Figure 10) (Figure 4, ACT12). The first image Ca is an image of the accounting code converted into a barcode, in other words, an image of the accounting barcode.

[0055] The management server 12 sends an accounting approval command CMi to the smartphone 40, which is the source of the accounting request command CMh. The accounting approval command CMi includes the first image Ca.

[0056] The accounting approval command CMi is sent to the POS system 20 via the network 30, and then transmitted from the access point 29 to the smartphone 40 via wireless LAN. Upon receiving the accounting approval command CMi, the smartphone 40's touch panel screen transitions to the accounting screen Se (Figure 10). As shown in Figure 10, the first image Ca is displayed on the accounting screen Se. The accounting screen Se also displays an exit button Bf. The exit button Bf is the button to touch to cancel the transaction.

[0057] Furthermore, the management server 12 retrieves the store ID and transaction ID stored in the linkage table 70 in association with the member ID obtained from the accounting request command CMh. The management server 12 then retrieves the transaction file 80, which contains the store ID and transaction ID, from the virtual POS server 13. The management server 12 then sends the transaction file 80 and accounting code to the POS system 20 of the affiliated store identified by the store ID. As a result, the transaction file 80 and accounting code data are sent to the store server 21 of the corresponding affiliated store via the network 30. The store server 21 transfers the transaction file 80 and accounting code data received from the management server 12 to the accounting server 22. The accounting server 22 stores the transaction file 80 in memory in association with the accounting code.

[0058] <Accounting (see Figure 5)> After checking the accounting screen Se, members can use the dedicated accounting machine 25 to make payments using various payment methods such as electronic money, credit cards, and cash.

[0059] Figure 5 will be used to explain the operation of accounting using the dedicated accounting machine 25. The member scans the first image Ca on the accounting screen Se, which is the accounting barcode, using the scanner on the dedicated accounting machine 25. Then, the accounting barcode data, also known as barcode data BCD (Figure 5), is transmitted from the dedicated accounting machine 25 to the accounting server 22.

[0060] The accounting server 22 obtains the accounting code from the barcode data BCD (Figure 5, ACT21). The accounting server 22 then retrieves the transaction file 80 associated with the accounting code from its memory (Figure 5, ACT22). The accounting server 22 then sends the transaction file 80 to the dedicated accounting machine 25.

[0061] The dedicated accounting machine 25 recalculates the settlement amount by referring to the second product master 211 managed by the store server 21. Specifically, the dedicated accounting machine 25 retrieves the product code registered in the transaction file 80. Then, the dedicated accounting machine 25 searches the second product master 211 and retrieves the price of the product record containing the product code. The dedicated accounting machine 25 multiplies that price by the number of units sold, which was registered in the transaction file 80 along with the product code, to calculate the sales amount of the purchased product identified by that product code. The dedicated accounting machine 25 performs the above process for all product codes registered in the transaction file 80. Then, the dedicated accounting machine 25 calculates the settlement amount by summing up the sales amounts of all purchased products.

[0062] The dedicated payment machine 25 displays the recalculated payment amount on its screen. It then waits for the customer to select a payment method (Figure 5, ACT32). The recalculated payment amount may differ from the total amount displayed on the smartphone 40. In this case, since the total amount on the smartphone 40 is only a reference amount, the customer will pay the payment amount displayed on the dedicated payment machine 25.

[0063] Members select a payment method. For example, if cash is selected, the dedicated payment machine 25 executes the payment process to receive the settlement amount in cash (Figure 5, ACT33). For example, if a credit card is selected, the dedicated payment machine 25 executes the payment process to receive the settlement amount by credit card. Since these payment processes are well-known, a detailed explanation is omitted here.

[0064] Once payment processing is complete, the dedicated accounting machine 25 sends a payment completion notification command CMj to the accounting server 22. The payment completion notification command CMj contains payment data. For example, in the case of a cash payment, the payment data includes the amount received, the amount of change given, etc. For example, in the case of a credit card payment, the payment data includes the amount paid by credit card, etc.

[0065] The accounting server 22 registers payment data in the transaction file 80. The accounting server 22 also sets an exit status in the transaction file 80. The transaction file 80 with the exit status set is stored in the recording unit of the accounting server 22 or the store server 21.

[0066] [Configuration of monitoring server 26] Figure 11 is a schematic block diagram showing an example configuration of a monitoring server 26 according to one embodiment. The monitoring server 26 includes a processor 261, main memory 262, auxiliary storage unit 263, communication interface 264, and transmission line 265. The processor 261, main memory 262, auxiliary storage unit 263, and communication interface 264 are capable of communicating via the transmission line 265. The monitoring server 26 constitutes a computer with the processor 261, main memory 262, auxiliary storage unit 263, and the transmission line 265 connecting them.

[0067] The processor 261 corresponds to the central part of the computer described above. The processor 261 controls various parts in order to realize various functions as a monitoring server 26 according to the operating system and application programs. The processor 261 is, for example, a CPU (Central Processing Unit).

[0068] Main memory 262 corresponds to the main memory portion of the computer described above. Main memory 262 includes non-volatile memory areas and volatile memory areas. In the non-volatile memory area of ​​main memory 262, the operating system and application programs are stored. Main memory 262 may also store data necessary for the processor to perform processing to control various parts in non-volatile or volatile memory areas. Main memory 262 uses the volatile memory area as a work area where data is rewritten as needed by the processor. For example, the non-volatile memory area is ROM (Read Only Memory). The volatile memory area is RAM (Random Access Memory).

[0069] The auxiliary storage unit 263 corresponds to the auxiliary storage portion of the computer described above. For example, EEPROM (Electric Erasable Programmable Read-Only Memory), HDD (Hard Disk Drive), or SSD (Solid State Drive) can be used as the auxiliary storage unit 263. The auxiliary storage unit 263 stores data used by the processor 261 for various processing tasks, as well as data created by processing performed by the processor 261. The auxiliary storage unit 263 may also store the application programs described above.

[0070] The communication interface 264 communicates data with each component connected to the in-store network 27 according to a predetermined communication protocol. For example, a well-known communication device for LANs can be used as the communication interface 264.

[0071] The transmission line 265 includes an address bus, a data bus, and control signal lines, and transmits data and control signals exchanged between the connected parts.

[0072] The auxiliary storage unit 263 includes a transaction data storage area 2631, a shooting condition storage area 2632, and a captured image storage area 2633.

[0073] The transaction data storage area 2631 stores first transaction data based on data stored in the virtual POS server 13. The first transaction data is an example of information regarding product registration via multiple smartphones 40. Information regarding product registration includes information about products registered via smartphones 40 before payment, and information regarding product registration via smartphones 40. Information regarding products includes information indicating the type of product, the price of the product, and the number of registered items. The type of product includes information indicating age-restricted products such as alcoholic beverages and tobacco. The price indicates the unit price of the product. The number of registered items indicates the total number of products registered by the member. Information regarding product registration includes information regarding product registration operations via smartphones 40 and information regarding the time associated with product registration via smartphones 40. Information regarding product registration operations includes information regarding editing such as adding and deleting registered products, information regarding operations to register products without barcodes, information regarding operations to proceed to accounting, and location information of the place where the product registration operation was performed. Information regarding time includes information indicating the stay time and the time of the previous operation, as described later.

[0074] The first transaction data includes the first index file and the first transaction file. The first transaction data includes data corresponding to the second transaction data stored in each smartphone 40, which will be described later. The first index file is data associated with multiple first transaction files. The first index file is a collection of index file records created for each terminal ID. The first index file includes data corresponding to the second index file stored in each smartphone 40, which will be described later. An index file record is a data record that records the terminal ID, transaction ID, time spent, time of the most recent operation, registered points, status, and accounting machine ID, etc., in association with each other.

[0075] The terminal ID is a unique code set for each smartphone 40 to individually identify each smartphone 40. The transaction ID is a unique code set for each first transaction file to individually identify the first transaction file that records transactions performed using the smartphone 40. The transaction ID is set in the first transaction file each time the first transaction file is created. The transaction ID is associated with the member ID and store ID, similar to the linkage table 70. The time spent indicates the elapsed time since the member logged in. The last operation time indicates the time when the member last operated the smartphone 40. For example, the last operation time indicates the time when the member registered the last product. The status is the terminal status that indicates the state of the smartphone 40. The terminal status can be "Waiting," "Registering," or "Checkout." "Waiting" is the state from when the previous member's checkout is completed until the next member logs in. "Registering" is the state from when the member logs in until the checkout is approved. The state until the checkout is approved is also called the state before the checkout process is performed. "Accounting in Progress" refers to the state from when the accounting is approved until it is completed. The accounting machine ID is a unique code assigned to each accounting machine to identify it individually. The first index file may include information such as the total amount of registered goods, in addition to the items mentioned above. The first index file is linked to the first transaction file using the transaction ID as the key. Details of the first index file will be described later.

[0076] The first transaction file is a collection of transaction file records created for each transaction ID. Each transaction file record is a data record that associates the transaction ID with product sales data. Product sales data includes product code, product type, product name, price, number of units sold, sales amount, etc. The first transaction file may be generated in the same way as transaction file 80. The first transaction file is updated each time a product is registered by a member. Details of the first transaction file will be described later.

[0077] The shooting condition memory area 2632 stores the shooting conditions. The shooting conditions indicate the conditions for taking a photograph of the purchased product using the smartphone 40. The shooting conditions include at least one of the conditions related to the product and the conditions related to product registration. The shooting conditions are the conditions related to the product to be monitored or product registration. Product conditions are the conditions used for comparison with product information. Product conditions include, for example, conditions regarding the number of registered products, price, and type. The condition regarding the number of products may be a single predetermined number, such as "5 points," or it may be a number at regular intervals, such as "every 5 points increase." If the condition regarding the number of products is every 5 points increase, the condition includes cases where the registered number of products is a multiple of 5, such as 5 points, 10 points, or 15 points. The interval does not have to be constant. The interval can be set as appropriate, such as narrowing or widening the interval as the number of registered products increases. The condition regarding the number of products may include, for example, the number of registered products reaching a predetermined number for the first time. The number of registered products reaching a predetermined number for the first time includes, for example, the number of registered products reaching 5 points, 10 points, or 15 points for the first time. The predetermined number includes multiples of 5, such as 5 points, 10 points, or 15 points. The predetermined number may be a number at regular intervals, or it may be a randomly set number. The price requirement is, for example, "1000 yen or more" for high-priced items. The type requirement is, for example, "alcoholic beverages" for items.

[0078] The conditions for product registration include conditions for the product registration operation and conditions for time. The conditions for the product registration operation are conditions that can be compared with information regarding the product registration operation. Conditions for the product registration operation include, for example, conditions for editing such as adding, deleting, or canceling registered products, conditions for registering products without barcodes, conditions for operations that proceed to accounting, and conditions regarding location information where the product registration operation was performed. Conditions for editing include, for example, "adding the number of registered products sold" and "canceling registered products." Conditions for registering products without barcodes include, for example, "the 'no barcode' button was operated." Conditions for operations that proceed to accounting include, for example, "the 'account' button was operated." Conditions regarding location information where the product registration operation was performed include, for example, "the location where the product was registered and the display location of the registered product are different." Conditions for time are conditions that can be compared with information regarding time. Conditions for time include, for example, conditions regarding the duration of stay and conditions regarding the time of the previous operation. Conditions regarding the duration of stay include, for example, "the duration of stay exceeds a certain period of time." The condition regarding the time of the previous operation is, for example, "a certain amount of time must have elapsed since the time of the previous operation." This certain amount of time can be set as appropriate.

[0079] The shooting conditions may be pre-set, or they may be set or updated as appropriate by the store manager or other relevant personnel.

[0080] The captured image storage area 2633 stores captured image management data. The captured image management data includes captured image data taken by the smartphone 40. The captured image data includes image data of products purchased by a member who owns the smartphone 40. The captured image storage area 2633 may store captured image data representing multiple captured images in chronological order. The captured image management data is updated each time captured image data is acquired by the acquisition unit 2612. The captured image storage area 2633 stores captured image management data that associates captured image data with information related to the shooting in which the captured image data was acquired. Information related to the shooting includes information related to shooting conditions such as "5th item," "10th item," etc., information related to the shooting such as the position of the shopping cart, etc. The position of the shopping cart includes information such as the upper or lower shelf of the cart.

[0081] The hardware configuration of the monitoring server 26 is not limited to the configuration described above. The monitoring server 26 may, as appropriate, omit or change the above-described components and add new components.

[0082] [Configuration of 40 Smartphones] Figure 12 is a block diagram schematically showing an example of the configuration of a smartphone 40 according to one embodiment. The smartphone 40 includes a processor 401, main memory 402, auxiliary storage unit 403, touch panel 404, camera 405, audio output device 406, wireless communication unit 407, mobile communication unit 408, and transmission line 409, etc. The processor 401 and the main memory 402, auxiliary storage unit 403, touch panel 404, camera 405, audio output device 406, wireless communication unit 407, and mobile communication unit 408 can communicate with each other via the transmission line 409. The processor 401, main memory 402, and auxiliary storage unit 403 are connected by the transmission line 409, thereby forming a computer for controlling the smartphone 40. The general functions of the processor 401, main memory 402, auxiliary storage unit 403, and transmission line 409 are equivalent to those of the processor 261, main memory 262, auxiliary storage unit 263, and transmission line 265, so their explanation is omitted. The smartphone 40 is an example of an information processing terminal.

[0083] The touch panel 404 functions as an operating device and display device for the smartphone 40. The touch panel 404 is an example of a display unit that displays information, or a notification unit that visually notifies information.

[0084] Camera 405 includes an optical system and an image sensor, and the image sensor generates image data representing the image within the field of view formed by the optical system. Camera 405 is an example of an imaging unit.

[0085] The audio output device 406 is a device capable of outputting sound under the control of the processor 401. The audio output device 406 is an example of an audio output unit that outputs information as sound or a notification unit that notifies information audibly.

[0086] The wireless communication unit 407 exchanges data with the access point 29 via wireless communication in accordance with a wireless communication protocol. For example, a well-known communication device compliant with the IEEE 802.11 standard can be used as the wireless communication unit 407.

[0087] The mobile communication unit 408 is an interface for data communication via the network 30. For example, a well-known communication device for performing data communication via a mobile communication network can be used as the mobile communication unit 408.

[0088] The auxiliary storage unit 403 includes a smartphone POS application 4031, which is one of the information processing programs, a transaction data storage area 4032, and a shooting condition storage area 4033. The auxiliary storage unit 403 is an example of a storage unit.

[0089] The smartphone POS application 4031 is an application program that describes the information processing necessary to enable the smartphone 40 to function as the user interface for the POS system 20. The smartphone POS application 4031 is used in common across multiple smartphones 40.

[0090] The transaction data storage area 4032 stores second transaction data based on data stored in the virtual POS server 13. The second transaction data is an example of information regarding product registration via the smartphone 40. The second transaction data includes a second index file and a second transaction file. The second index file and the second transaction file contain information about products registered by the smartphone 40. The second index file consists of data that associates terminal ID, transaction ID, time spent, time of previous operation, number of registered items, status, accounting machine ID, etc.

[0091] The terminal ID is a unique code set to identify the smartphone 40. The transaction ID is a unique code set for each second transaction file to individually identify the second transaction file that records transactions performed using the smartphone 40. The transaction ID is set in the second transaction file each time a second transaction file is created. The transaction ID is associated with the member ID and store ID, as well as the linkage table 70. The second index file contains index file records from the first index file stored in the transaction data storage area 2631 of the monitoring server 26, which are associated with each smartphone 40 and its corresponding terminal ID.

[0092] The second transaction file consists of data that associates transaction IDs with product sales data. Product sales data includes product code, product type, product name, price, number of units sold, sales amount, etc. The second transaction file may be data generated in the same way as transaction file 80. The second transaction file is updated each time a product is registered by a member. The second transaction file includes transaction file records from the first transaction file stored in the transaction data storage area 2631 of the monitoring server 26, which are associated with the transaction ID corresponding to each smartphone 40.

[0093] The shooting condition storage area 4033 stores the shooting conditions. The shooting conditions are those received from the monitoring server 26. The shooting conditions may be those stored in the shooting condition storage area 2632 of the monitoring server 26, corresponding to the user (customer) of the smartphone 40, the store where the smartphone 40 is used, the time when the smartphone 40 is used, etc. Different shooting conditions may be set based on the store, user, time of entry, etc. The shooting conditions may also be stored in the main memory 402.

[0094] The hardware configuration of the smartphone 40 is not limited to the configuration described above. The smartphone 40 may, as appropriate, omit or change the above-mentioned components and add new components.

[0095] The following describes the various components implemented in the aforementioned processor 401. The processor 401 implements a receiving unit 4010, a determination unit 4011, a display control unit 4012, a shooting control unit 4013, an acquisition unit 4014, a memory control unit 4015, and a transmission unit 4016. Each part implemented in the processor 401 can also be called a function. Each part implemented in the processor 401 can also be said to be implemented in the control unit which includes the processor 401 and the main memory 402.

[0096] The receiving unit 4010 receives the shooting conditions from the monitoring server 26 via the wireless communication unit 407 before the customer starts shopping. Before the customer starts shopping is, for example, before the customer is able to register products. Before the customer starts shopping is, for example, when the smartphone 40 receives the store entry approval command CMc from the management server 12. In this case, the receiving unit 4010 receives the shooting conditions from the monitoring server 26 based on the receipt of the store entry approval command CMc.

[0097] The determination unit 4011 determines whether the second transaction data satisfies the shooting conditions.

[0098] The display control unit 4012 displays automatic product photography guidance on the touch panel 404 based on the determination result of the determination unit 4011. Automatic photography guidance is, for example, a notification indicating that the product will be automatically photographed. Automatic photography guidance is text information such as, for example, "Taking a picture," or "Taking a picture in 5 seconds." Automatic photography guidance may also include notifications in any form, such as symbols, icons, audio, or video. If the automatic photography guidance is audio, the processor 401 outputs the automatic photography guidance to the audio output device 406. If the notification prompting photography is video, the processor 401 outputs the automatic photography guidance to the touch panel 404 and the audio output device 406. Automatic photography guidance may also include a photography guide. The photography guide includes a guide indicating the shooting range. The photography guide may include text information such as, for example, "Move so that the product is within the shooting range." The photography guide includes a guide prompting the user to photograph multiple shopping baskets. The shooting guide may include text information such as, "Is there a shopping basket on the bottom shelf of the cart?", and "We will photograph the bottom shelf basket. Please move the camera so that the bottom shelf basket is within the shooting range." The customer moves their smartphone 40 according to the shooting guide so that the bottom shelf basket is within the shooting range of camera 405.

[0099] The display control unit 4012 may, instead of automatic shooting guidance, display a notification prompting the user to take a picture on the touch panel 404. The notification prompting the user to take a picture may be text information such as "Please take a picture" to encourage the user to take a picture. The notification prompting the user to take a picture may also include any form of notification, such as symbols, icons, audio, or video. If the notification prompting the user to take a picture is audio, the processor 401 outputs instructions regarding the photography of the product to the audio output device 406. If the notification prompting the user to take a picture is video, the processor 401 outputs instructions regarding the photography of the product to both the touch panel 404 and the audio output device 406.

[0100] Based on the determination unit 4011's determination that the second transaction data satisfies the shooting conditions, the shooting control unit 4013 outputs a product shooting instruction to the camera 405. The product shooting instruction is an instruction for the processor 401 to control the camera 405. In response to the product shooting instruction, the processor 401 activates the camera 405 and controls the camera 405 to automatically photograph the product.

[0101] The acquisition unit 4014 acquires image data of the captured product based on the automatic shooting of the product. The acquisition unit 4014 acquires image data of the captured product based on the automatic shooting of the product based on the control of the shooting control unit 4013.

[0102] The memory control unit 4015 stores the captured image data acquired by the acquisition unit 4014 in the auxiliary storage unit 403. The memory control unit 4015 deletes the captured image data when the captured image data is transmitted to the monitoring server 26 by the transmission unit 4016, which will be described later. The memory control unit 4015 retains the captured image data until the captured image data is transmitted to the monitoring server 26 by the transmission unit 4016. The memory control unit 4015 may delete the captured image data after a certain period of time has elapsed since the acquisition of the captured image data. This period of time may be, for example, one day.

[0103] The transmission unit 4016 transmits the captured image data acquired by the acquisition unit 4014 to the monitoring server 26. If the transmission unit 4016 is unable to transmit the captured image data to the monitoring server 26, it retransmits the untransmitted image data to the monitoring server 26. If the auxiliary storage unit 403 has previously acquired image data stored in it, the transmission unit 4016 transmits the previously acquired image data to the monitoring server 26. Previously acquired image data is image data that was acquired in the past but has not been transmitted to the monitoring server 26. Previously acquired image data may be past image data taken during the same transaction, or past image data taken during different transactions. Other transactions may be, for example, different transactions on the same day, or transactions on different days.

[0104] [Configuration of monitoring terminal 23] Figure 13 is a block diagram schematically showing an example of the configuration of a monitoring terminal 23 according to one embodiment. The monitoring terminal 23 includes a processor 231, main memory 232, auxiliary storage unit 233, touch panel 234, audio output device 235, communication interface 236, and transmission line 237. The processor 231, main memory 232, auxiliary storage unit 233, touch panel 234, audio output device 235, and communication interface 236 are able to communicate with each other via the transmission line 237. The processor 231, main memory 232, and auxiliary storage unit 233 are connected via the transmission line 237, thereby forming a computer for controlling the monitoring terminal 23. The general functions of the processor 231, main memory 232, auxiliary storage unit 233, and transmission line 237 are equivalent to those of the processor 261, main memory 262, auxiliary storage unit 263, and transmission line 265, so their explanation is omitted.

[0105] The touch panel 234 functions as an operating device and display device for the monitoring terminal 23. The touch panel 234 is an example of a display unit that displays information, or a notification unit that visually notifies information.

[0106] The audio output device 235 is a device capable of outputting sound under the control of the processor 231. The audio output device 235 is an example of an audio output unit that outputs information as sound or a notification unit that notifies information audibly.

[0107] The communication interface 236 communicates data with each component connected to the in-store network 27 according to a predetermined communication protocol. For example, a well-known communication device for LANs can be used as the communication interface 236.

[0108] The hardware configuration of the monitoring terminal 23 is not limited to the configuration described above. The monitoring terminal 23 may, as appropriate, omit or change the above-described components and add new components.

[0109] The various components implemented in the aforementioned processor 231 will now be described. The processor 231 implements the receiving unit 2310 and the display control unit 2311. Each part implemented in the processor 231 can also be called a function. Each part implemented in the processor 231 can also be said to be implemented in the control unit which includes the processor 231 and the main memory 232.

[0110] The receiving unit 2310 receives captured image data from the captured image storage area 2633 of the monitoring server 26 via the access point 29. The receiving unit 2310 updates the captured image data each time it receives captured image data from the smartphone 40.

[0111] The display control unit 2311 displays an attendant image on the touch panel 234 based on the captured image data. The attendant image includes, for example, a registered product details screen and a registered product confirmation screen. The registered product details screen shows the details of registered products for each customer. The registered product details screen includes, for example, information such as the order in which the products are registered, the product name, the number of registered products, and the price. The registered product confirmation screen shows the image of the photographed product. The registered product confirmation screen includes, for example, a thumbnail image of the photographed product, an enlarged image of the selected product, etc. The display control unit 2311 updates the attendant image each time the captured image data is updated. The display control unit 2311 displays the photographed image based on the captured image data on the touch panel 234 based on the display instructions from the attendant. The term "attendant" may be replaced with "store clerk," "user," or "person."

[0112] The first example of an index file structure is described below. Figure 14 shows the main data structure of the first index file stored in the transaction data storage area 2631 according to one embodiment.

[0113] The first index file includes the following fields: "Terminal ID", "Transaction ID", "Time Spent", "Last Operation Time", "Registered Points", "Status", and "Accounting Machine ID". Each of the multiple terminal IDs is associated with the Transaction ID, Time Spent, Last Operation Time, Registered Points, Status, and Accounting Machine ID as an index file record. For example, smartphone 40 with terminal ID "00001" is associated with transaction ID "1". Smartphone 40 with terminal ID "00001" has a time spent "8 minutes" since login, and a last operation time of "14:10". The registered points by smartphone 40 are "5", and the status is "Registering", meaning accounting processing has not yet been performed. In this example, smartphone 40 with terminal ID "00001" is not associated with an accounting machine because accounting processing has not yet been performed, and therefore the Accounting Machine ID is blank. The information included in the first index file can be set as appropriate. The monitoring server 26 updates the first index file as appropriate. The configuration example of the second index file stored in the transaction data storage area 4032 of the smartphone 40 includes only the index file records related to the corresponding smartphone 40 from the configuration example of the first index file described above. For example, for smartphone 40 with terminal ID "00001", only the index file records associated with terminal ID "00001" are stored in the transaction data storage area 4032.

[0114] The first example of a transaction file structure is described below. Figure 15 shows the main data structure of a first transaction file stored in a transaction data storage area 2631 according to one embodiment.

[0115] The first transaction file includes the following fields: "Transaction ID," "Product Code," "Product Name," "Product Type," "Price," "Quantity Sold," and "Sales Amount." Each of the multiple transaction IDs is associated with the transaction ID, product code, product type, product name, price, quantity sold, and sales amount as a transaction file record. The first index file and the first transaction file are linked using "Transaction ID" as the key. The information contained in the first transaction file can be set as appropriate. The monitoring server 26 updates the first transaction file as appropriate. Note that the example configuration of the second transaction file stored in the transaction data storage area 4032 of the smartphone 40 includes only the information related to the corresponding smartphone 40 from the example configuration of the first transaction file described above. For example, smartphone 40 with terminal ID "00001" stores only the first transaction file record of the "Transaction ID" associated with terminal ID "00001" in the transaction data storage area 4032.

[0116] This section describes an example of the structure of image management data. Figure 16 shows the main data structure of the captured image management data stored in the captured image storage area 2633 according to one embodiment.

[0117] The captured image management data includes a "Transaction ID" field and an "Image" field. The "Image" field is used to set the captured image data. Each of the multiple transaction IDs is associated with the captured image data as a captured image data record. The monitoring server 26 may store the captured image data in the captured image storage area 2633 in chronological order based on the time the captured image data was acquired. The captured image management data is associated with the first index file and the first transaction file using the "Transaction ID" as the key. The monitoring server 26 updates the captured image management data as appropriate each time captured image data is acquired.

[0118] [Guidance screen] Figure 17 is a schematic diagram showing an example of a guidance screen Sf displayed on a smartphone 40 according to one embodiment.

[0119] The smartphone 40 outputs automatic product shooting guidance to the touch panel 404 in response to the meeting of shooting conditions. Figure 17 shows the guidance screen Sf displaying the automatic shooting guidance. As shown in Figure 17, the guidance screen Sf displays a frame ARb indicating the product shooting area and an area ARc indicating the automatic shooting guidance.

[0120] The ARb border is set, for example, to accommodate the entire shopping cart. The member operates the smartphone 40 so that, for example, the purchased items in the shopping cart are within the ARb border. In this example, the smartphone 40 can prompt the member to photograph the items along the ARb border. This allows the smartphone 40 to acquire photographic image data taken within a somewhat consistent range. As a result, variations in the photographic images of the products are reduced. The attendant, who checks the photographic images of the products on the monitoring terminal 23, can easily compare multiple photographic images taken in chronological order.

[0121] Area ARc is, for example, an area that includes a display indicating the timing of automatic shooting. Area ARc may also include, for example, a countdown display until the timing of automatic shooting. The countdown display in Figure 17 includes "5" indicating that it is 5 seconds before the timing of automatic shooting. The display mode of the countdown display changes as time progresses. The countdown display may be a numerical representation, or it may be a display that has different display modes depending on the passage of time, such as symbols, icons, or bars.

[0122] Note that the smartphone 40 does not need to display the ARb border. In this case, the smartphone 40 may automatically detect the area of ​​the shopping cart and set it so that the shopping cart fits within the shooting range of the camera 405.

[0123] The guidance screen Sf may also include a photo button. Members can manually take photos of products by touching the photo button. For example, a member touches the photo button when the purchased product is within the frame ARb. When the member touches the photo button, the camera 405 of the smartphone 40 takes a photo of the purchased product.

[0124] [Smartphone 40 operation] This document explains the procedure for processing information using a smartphone (model 40). The processing procedure described below is merely an example, and each process may be modified as much as possible. Furthermore, depending on the embodiment, steps in the processing procedure described below may be omitted, replaced, or added as appropriate.

[0125] The following processes occur while shopping. The following process is performed by the user (customer) of smartphone 40 before proceeding to the checkout process. The customer reads the code symbol attached to the product displayed in the store via camera 405 and registers the product. The information of the registered product is stored in the virtual POS server 13 each time a product is registered by a member. The information of the registered product is also stored in the transaction data storage area 4032 of smartphone 40, which is linked to the virtual POS server 13. It is assumed that the customer is using smartphone 40 with terminal ID "00001" in Figure 14 to register the product. Smartphone 40 with terminal ID "00001" stores only the transaction data from smartphone 40 with that terminal ID in the transaction data storage area 4032.

[0126] The following example illustrates a case where the shooting conditions relate to the number of items. We assume the condition is set so that the number of registered items reaches a predetermined number initially. The predetermined number is a multiple of 5, such as 5, 10, or 15.

[0127] Figure 18 is a flowchart showing an example of the information processing procedure by a smartphone 40 according to one embodiment. The determination unit 4011 determines whether the second transaction data satisfies the shooting conditions (ACT1). In ACT1, for example, the determination unit 4011 refers to the index file record associated with the terminal ID "00001" stored in the second index file and compares the "registered points" with the conditions regarding the points of the product. If the determination unit 4011 determines that the "registered points" of the product registered in the second index file satisfies the shooting conditions (ACT101:YES), the process transitions from ACT101 to ACT102. If the determination unit 4011 determines that the "registered points" of the product registered in the second index file does not satisfy the shooting conditions (ACT101:NO), the process repeats ACT101.

[0128] For example, the determination unit 4011 compares the registered score "5" with the conditions related to the product score from a second index file associated with the terminal ID "00001". In this example, the determination unit 4011 determines that the "registered score" of the product registered in the second index file satisfies the shooting conditions, and proceeds to YES in ACT101.

[0129] The display control unit 4012 displays automatic product shooting guidance on the touch panel 404 based on the determination result of the determination unit 4011 (ACT102). In ACT102, for example, the display control unit 4012 displays a notification on the touch panel 404 indicating that automatic shooting will begin. The display control unit 4012 may also display a countdown indicating the timing for automatic shooting. If the automatic shooting guidance is voice, the processor 401 outputs the automatic shooting guidance to the voice output device 406. If the automatic shooting guidance is video, the processor 401 outputs the automatic shooting guidance to both the touch panel 404 and the voice output device 406.

[0130] The shooting control unit 4013 controls the camera 405 to photograph the product (ACT103). In ACT103, for example, the shooting control unit 4013 outputs a product photography instruction to the camera 405. The shooting control unit 4013 may photograph the product in response to obtaining a determination result from the determination unit 4011. The shooting control unit 4013 may also photograph the product based on the timing for automatic photography. The timing for automatic photography may be after a predetermined time has elapsed since the automatic photography guidance was displayed. The predetermined time is, for example, 5 seconds. The shooting control unit 4013 may also determine whether or not the product has been photographed by automatic photography. If the shooting control unit 4013 determines that the product has been photographed, the process transitions from ACT103 to ACT104. If the shooting control unit 4013 determines that the product has not been photographed, the process returns from ACT103 to ACT102. In this case, the display control unit 4012 displays the automatic product photography guidance on the touch panel 404. The smartphone 40 may repeat the processes from ACT102 to ACT103 until the product is successfully photographed.

[0131] The smartphone 40 may repeat the processes of ACT102 to ACT103 until all shopping baskets have been photographed. In this case, the display control unit 4012 may display a shooting guide on the touch panel 404 prompting the user to photograph the lower basket if there is a shopping basket on the lower level of the cart. The shooting guide prompting the user to photograph the lower basket may be, for example, "If there is a second basket, please press the 'Photograph Next Basket' button." Figure 19 shows an example of the display of the shooting guide. The shooting guide screen Sfa shown in Figure 19 includes text information indicating the shooting guide, a "Retake Shoot" button Baa, a "Photograph Next Basket" button Bab, and a "Complete" button Bac. The text information includes, for example, information such as "If there is a second basket, please press the 'Photograph Next Basket' button." The "Retake Shoot" button Baa is a button for the customer to redo the photography of the shopping basket. The "Photograph Next Basket" button Bab is a button for photographing the lower basket if there is one on the lower level. The "Complete" button Bac is a button for completing the photography. For example, if there is a basket on the lower level, the customer selects the "Photograph the next basket" button Bab according to the photography guide. In response to the customer selecting the "Photograph the next basket" button Bab, the display control unit 4012 displays a notification on the touch panel 404 indicating that the lower basket will be photographed automatically.

[0132] The acquisition unit 4014 acquires captured image data of the products based on the automatic photography of the products (ACT104). In ACT104, for example, the acquisition unit 4014 acquires captured image data of the products taken by the camera 405. The acquisition unit 4014 acquires additional information regarding the captured image data. The additional information includes information such as the time the image data was taken, the shooting conditions, and the position of the basket. The additional information includes information such as "3:30 PM", "5th registered product", and "upper shelf". The acquisition unit 4014 acquires the first captured image data taken by the camera 405 as the upper shelf image data. The acquisition unit 4014 may also acquire the captured image data taken by the camera 405 as the lower shelf image data when the customer operates the "Shoot the next basket" button.

[0133] The memory control unit 4015 stores the acquired product image data in the auxiliary storage unit 403 (ACT105). In ACT105, for example, the memory control unit 4015 stores the acquired product image data in the auxiliary storage unit 403 in chronological order, associating it with the transaction ID and additional information.

[0134] The transmission unit 4016 transmits the captured image data acquired by the acquisition unit 4014 to the monitoring server 26 (ACT106). In ACT106, for example, the transmission unit 4016 associates the captured image data with the transaction ID and additional information and transmits it to the monitoring server 26. The monitoring server 26 outputs the captured image data, transaction ID, and additional information to the monitoring terminal 23. The monitoring terminal 23 generates an attendant image based on the acquired image data and displays it on the touch panel of the monitoring terminal 23. The monitoring image includes a captured image of the product associated with the transaction data. The monitoring image may include multiple captured images in chronological order based on captured image data taken at different times. The transmission unit 4016 may compress the captured image data and transmit it to the monitoring server 26.

[0135] Furthermore, during a single transaction, the processor 401 repeats the processing of ACT101 to ACT106 each time the second transaction data satisfies the shooting conditions. In this way, if the processor 401 repeats the processing of ACT101 to ACT106 multiple times during a single transaction, the monitoring image can include multiple images in chronological order based on image data captured at different times. In this case, the attendant who checks the captured images of the products on the monitoring terminal 23 can check the changes in the state of the shopping cart in accordance with the increase in the number of registered products. Here, we have explained using the example of a condition related to the number of products, which is "reaching a predetermined number for the first time," but it is not limited to this. For example, if the shooting condition is "reaching a predetermined number," the processor 401 may photograph the product each time the number of registered products reaches the predetermined number. For example, if the predetermined number is "5," the processor 401 may photograph the product when the number of registered products reaches 5, then the product registration is canceled, and then the number of registered products reaches "5" again. Even if the shooting conditions are any of the various conditions mentioned above other than the conditions related to the number of items, the processor 401 repeats the processing of ACT101 to ACT106 each time the second transaction data satisfies the shooting conditions during a single transaction.

[0136] Figure 20 is a flowchart showing another example of the information processing procedure using a smartphone according to one embodiment. The following processes relate to the transmission of captured image data.

[0137] The transmission unit 4016 determines whether the transmission of the captured image data to the monitoring server 26 was successful (ACT201). In ACT201, for example, the transmission unit 4016 determines whether the captured image data was transmitted to the monitoring server 26 within a predetermined time. If the transmission unit 4016 determines that the transmission of the captured image data was successful (ACT201: YES), the process transitions from ACT201 to ACT203. If the transmission unit 4016 determines that the transmission of the captured image data was unsuccessful (ACT201: NO), the process transitions from ACT201 to ACT202. The transmission unit 4016 retransmits the captured image data that could not be transmitted.

[0138] The transmission unit 4016 determines whether the retransmission of the captured image data to the monitoring server 26 was successful (ACT202). In ACT202, for example, the transmission unit 4016 determines whether the captured image data was sent to the monitoring server 26 within a predetermined time. If the transmission unit 4016 determines that the retransmission of the captured image data was successful (ACT202: YES), the process transitions from ACT202 to ACT203. If the transmission unit 4016 determines that the retransmission of the captured image data was unsuccessful (ACT202: NO), the process terminates.

[0139] The transmitting unit 4016 determines whether or not previously acquired image data is stored in the auxiliary storage unit 403 (ACT203). For example, consider a case where the transmission of image data taken when the number of registered points was 10 was successful, but the image data taken when the number of registered points was 5 has not been transmitted to the monitoring server 26. The auxiliary storage unit 403 has the image data taken when the number of registered points was 5 stored in it. The transmitting unit 4016 retrieves the image data taken when the number of registered points was 5 from the auxiliary storage unit 403.

[0140] If the transmitter 4016 determines that previously acquired image data is stored in the auxiliary storage unit 403 (ACT203:YES), the process transitions from ACT13 to ACT14. If the transmitter 4016 determines that previously acquired image data is not stored in the auxiliary storage unit 403 (ACT203:NO), the process transitions from ACT13 to ACT15.

[0141] The transmission unit 4016 transmits the acquired image data to the monitoring server 26 (ACT204). In ACT204, for example, the transmission unit 4016 transmits the image data to the monitoring server 26, associating it with the transaction ID and additional information. The transmission unit 4016 transmits the image data captured when the number of registered points reaches 5 to the monitoring server 26. The monitoring server 26 outputs the image data, transaction ID, and additional information to the monitoring terminal 23. The monitoring terminal 23 updates the attendant image based on the acquired image data.

[0142] The memory control unit 4015 deletes the captured image data transmitted by the transmission unit 4016 from the auxiliary storage unit 403 (ACT205).

[0143] If the transmission unit 4016 determines that the transmission or retransmission of the captured image data to the monitoring server 26 has not been successful, the display control unit 4012 may display a warning message as a pop-up on the touch panel 404. The warning message may include text information such as "Image not transmitted" or "Please call a staff member." The transmission unit 4016 may also determine whether there is any captured image data that failed to transmit when the customer presses the payment button. If the transmission unit 4016 determines that there is any captured image data that failed to transmit, the display control unit 4012 may display a warning message on the touch panel 404. Based on the warning message, the attendant can check the registered product using the monitoring terminal 23. After the attendant's check, the smartphone 40 may perform payment processing. Payment processing may include, for example, accounting processing and display of the accounting code by the smartphone 40.

[0144] [Attendant screen] Figure 21 is a schematic diagram showing an example of a registered product details screen Sg displayed on a monitoring terminal 23 according to one embodiment. The monitoring terminal 23 displays the registered product details screen Sg on the touch panel 234 based on the captured image data acquired from the monitoring server 26. The registered product details screen Sg is an example of an attendant image. The monitoring terminal 23 is used by the attendant.

[0145] The Registered Product Details screen Sg includes registered product information such as the order in which the product was registered, product name, quantity, price, and remarks. The Registered Product Details screen Sg may also be a list of registered product information. The order in which the product was registered indicates the order in which the product was registered by the member. The quantity indicates the number of registered products. The registered product information includes marks Ma and Mb. Mark Ma indicates products that require verification by an attendant, such as age verification products. Mark Mb indicates products that meet the shooting conditions. The Registered Product Details screen Sg includes a confirmation button Bg and an OK button Bh.

[0146] The attendant can view detailed information about the product to which the mark Mb has been assigned by selecting the mark Mb. The detailed information about the product includes, for example, a photograph of the product. In response to the attendant selecting the mark Mb, the monitoring terminal 23 may transition the display screen of the touch panel 234 from the registered product details screen Sg to the registered product confirmation screen. The monitoring terminal 23 may also transition the display screen of the touch panel 234 from the registered product details screen Sg to the registered product confirmation screen in response to the attendant selecting the area where the product name is displayed. The area where the product name is displayed may be the row containing the product name in the registered product details list. The attendant selecting the area where the product name is displayed is equivalent to selecting the record of the registered product. Based on the selection of the record of the registered product, the monitoring terminal 23 may transition the display screen of the touch panel 234 from the registered product details screen Sg to the registered product confirmation screen. In this case, the monitoring terminal 23 displays a photograph taken at a time close to the registration time of the selected registered product in the photograph area ARe of the registered product confirmation screen. In addition, the monitoring terminal 23 may, in response to the attendant selecting mark Ma, transition the display screen of the touch panel 234 from the registered product details screen Sg to the registered product confirmation screen.

[0147] The attendant can return to the original screen from the registered product details screen Sg by selecting the OK button Bh. In response to the attendant selecting the OK button Bh, the monitoring terminal 23 transitions the display screen of the touch panel 234 from the registered product details screen Sg to the original screen (not shown). The original screen may be, for example, an image containing the registration status of multiple members.

[0148] The attendant can view detailed product information by selecting the confirmation button Bg. In response to the attendant selecting the confirmation button Bg, the monitoring terminal 23 transitions the display screen of the touch panel 234 from the registered product details screen Sg to the registered product confirmation screen.

[0149] Figure 22 is a schematic diagram showing an example of a registered product confirmation screen Sh displayed on a monitoring terminal 23 according to one embodiment. The monitoring terminal 23 displays the registered product confirmation screen Sh on the touch panel 234 in response to the attendant selecting mark Mb on the registered product details screen Sg. The monitoring terminal 23 may also display the registered product confirmation screen Sh on the touch panel 234 in response to the selection of the area where the product name is displayed. The registered product confirmation screen Sh is an example of an attendant image. The registered product confirmation screen Sh includes the thumbnail image area ARd and the captured image area ARe. The registered product confirmation screen Sh also includes the back button Bi and the OK button Bj.

[0150] The thumbnail image area ARd includes thumbnail images that are reduced in size from the captured image data of the product. The thumbnail images may include identification information that can identify the captured image data. The identification information may include, for example, the shooting conditions. In the example in Figure 22, each thumbnail image includes the registered number of products as identification information. The identification information may also include information indicating the location in the shopping cart. For example, the identification information may include "5th item," "top row," etc. The identification information may also include information indicating the circumstances under which the image was taken. The circumstances under which the image was taken may include, for example, product cancellation, cancellation correction, checkout, etc. The identification information is included in the additional information related to the captured image data. The monitoring terminal 23 may display the thumbnail image corresponding to the image displayed in the captured image area ARe in a display manner that can be identified. In the example in Figure 22, the monitoring terminal 23 displays the thumbnail image corresponding to the "10th item" image displayed in the captured image area ARe in a display manner that can be identified. The thumbnail image area ARd is not limited to thumbnail images and may include symbols or icons that can identify the captured image.

[0151] The image capture area ARe contains the image taken at the time the selected product was photographed. The image capture area ARe may also contain an enlarged image of the photographed product. The attendant can confirm the image taken at the time the selected product was photographed by looking at the image displayed in the image capture area ARe. The attendant can confirm the number of registered products and the number of products included in the shopping cart by checking the photographed image.

[0152] The attendant can select a thumbnail image contained in the thumbnail image area ARd and display the corresponding captured image in the captured image area ARe. In response to the attendant selecting a thumbnail image, the monitoring terminal 23 displays the corresponding captured image in the captured image area ARe.

[0153] The attendant can return to the previous screen by selecting the back button Bi. The previous screen may be the registered product details screen Sg, or it may be the registered product confirmation screen when a different product selected by the attendant is selected. In response to the attendant selecting the back button Bi, the monitoring terminal 23 transitions the display screen of the touch panel 234 from the registered product confirmation screen Sh to the previous screen.

[0154] The attendant can return from the registered product confirmation screen Sh to the registered product details screen Sg by selecting the OK button Bj. In response to the attendant selecting the OK button Bj, the monitoring terminal 23 transitions the display screen of the touch panel 234 from the registered product confirmation screen Sh to the registered product details screen Sg.

[0155] Figure 23 is a schematic diagram showing an example of a registered product confirmation screen Si displayed on a monitoring terminal 23 according to one embodiment. In response to the attendant selecting the confirmation button Bg on the registered product details screen Sg, the monitoring terminal 23 displays the registered product confirmation screen Si on the touch panel 234. The registered product confirmation screen Si is an example of an attendant image. The registered product confirmation screen Si includes a thumbnail image area ARf and a captured image area ARg, similar to Figure 22. In this example, the monitoring terminal 23 displays the most recent captured image in the captured image area ARg. The registered product confirmation screen Si also includes a back button Bi and an OK button Bj, similar to Figure 22. The most recent captured image is the most recent image in the time series.

[0156] The thumbnail image area ARf, like the thumbnail image area ARd, includes a thumbnail image that is a reduced-size version of the captured image based on the product's captured image data. The monitoring terminal 23 may display the thumbnail image corresponding to the image displayed in the captured image area ARg in a display manner that allows for identification. In the example in Figure 23, the monitoring terminal 23 displays the thumbnail image corresponding to the most recent captured image displayed in the captured image area ARg in a display manner that allows for identification. The thumbnail image area ARf is not limited to thumbnail images and may also include symbols or icons that allow for identification of the captured image.

[0157] The ARg image area contains the most recent captured image. The ARg image area may also contain an enlarged image of the captured image. The attendant can confirm the most recent captured image of the product by looking at the image displayed in the ARg image area. The attendant can confirm the number of registered products and the number of products included in the shopping cart by checking the captured image.

[0158] The attendant can select a thumbnail image contained in the thumbnail image area ARf and display the corresponding captured image in the captured image area ARg. The monitoring terminal 23 responds to the attendant's selection of a thumbnail image by displaying the corresponding captured image in the captured image area ARg.

[0159] [Operation of monitoring terminal 23] The procedure for processing by the monitoring terminal 23 will be explained below. Figure 24 is a flowchart showing an example of the information processing procedure by the monitoring terminal 23 according to one embodiment. The processing procedure described below is merely an example, and each process may be modified as much as possible. Furthermore, depending on the embodiment, steps in the processing procedure described below may be omitted, replaced, or added as appropriate.

[0160] The following processes are performed during the shopping process described above. The receiving unit 2310 receives captured image data from the monitoring server 26 via the in-store network 27. The receiving unit 2310 determines whether the captured image data received from the monitoring server 26 has been updated (ACT301). If the receiving unit 2310 determines that the captured image data has been updated (ACT301: YES), the process transitions from ACT301 to ACT302. If the receiving unit 2310 determines that the captured image data has not been updated (ACT301: NO), the process repeats ACT301.

[0161] The display control unit 2311 updates the attendant image based on the captured image data (ACT302). In ACT302, for example, the display control unit 2311 displays a mark on the registered product details screen indicating that captured image data exists for products that meet the shooting conditions. The mark may be, for example, an icon or a symbol indicating that captured image data exists. The display control unit 2311 is not limited to a mark; any display method that can identify products that meet the shooting conditions is acceptable. The display method includes text decoration such as text color, size, font, enclosed text, brightness or luminance, background color, background brightness or luminance, background pattern, frame color, flashing display, etc.

[0162] The display control unit 2311 determines whether the attendant has entered a display instruction for the registered product confirmation screen (ACT303). The display instruction includes the attendant entering a button or the like to display the registered product confirmation screen on the registered product details screen. The display instruction also includes the attendant selecting an area on the registered product details screen that indicates products that meet the shooting conditions. The area that indicates products that meet the shooting conditions corresponds to the area on the registered product details screen Sg where the product name is displayed, or the mark Mb. The display instruction also includes the attendant selecting a record of the registered product. For example, if the display control unit 2311 determines that a display instruction has been entered (ACT303:YES), the process transitions from ACT303 to ACT304. If the receiving unit 2310 determines that no display instruction has been entered (ACT303:NO), the process ends.

[0163] The display control unit 2311 displays a registered product confirmation screen on the touch panel 234 based on the display instruction (ACT304). In ACT304, for example, the display control unit 2311 displays different registered product confirmation screens on the touch panel 234 according to the display instruction. For example, let's consider the case where the display instruction is the selection of an area indicating a product that meets the shooting conditions. The display control unit 2311 displays a registered product confirmation screen Sh on the touch panel 234 as shown in Figure 22. The registered product confirmation screen includes, for example, thumbnail images of the captured images arranged chronologically in the order in which the shooting conditions were met. The registered product confirmation screen includes an enlarged image of the captured image of the product selected by the attendant. Let's consider the case where the display instruction is the input of a button to display the registered product confirmation screen. The button to display the registered product confirmation screen corresponds to the confirmation button Bg on the registered product details screen Sg. The display control unit 2311 displays a registered product confirmation screen on the touch panel 234 as shown in Figure 23. The registered product confirmation screen may include, for example, thumbnail images of the photographs arranged chronologically in the order in which the shooting conditions were met. The registered product confirmation screen may also include a magnified image of the most recent photograph.

[0164] The monitoring terminal 23 may save captured image data in the auxiliary storage unit 233 and display the attendant image on the touch panel 234 based on the saved captured image data, or it may display the attendant image on the touch panel 234 using the Web client function with the captured image data saved in the monitoring server 26.

[0165] [Effects of Transaction Processing System 100] According to this embodiment, the smartphone 40 can determine whether the information regarding product registration meets the shooting conditions, display automatic product shooting guidance based on the determination result, acquire the captured image data of the product based on the automatic product shooting, and transmit the acquired image data. As a result, the smartphone 40 can automatically photograph the products in the shopping cart when the shooting conditions are met and transmit the captured images to the monitoring server 26. Therefore, the smartphone 40 can remind the customer not to forget to register products or to register them fraudulently. The smartphone 40 can also display automatic product shooting guidance to inform the customer that the products will be photographed. Since the customer knows when the products will be photographed, it is possible to prevent customers from forgetting to register products or registering them fraudulently. In this way, the smartphone 40 can prevent customers from forgetting to register products or registering them fraudulently. The monitoring server 26 can also manage the automatically captured image data. The attendant can confirm the customer's registered products based on the captured images, based on the attendant image displayed on the monitoring terminal 23.

[0166] According to this embodiment, the smartphone 40 can automatically take a picture of a product when the number of registered products reaches a predetermined number for the first time. This allows the smartphone 40 to skip automatic product photography if the same shooting conditions are met multiple times. For example, if the shooting condition is that the number of registered products is 5, and after the number of registered products reaches 5, the customer changes the number of registered products by canceling or otherwise changing them, the smartphone 40 will not take an automatic picture when the number of products reaches 5 again. Therefore, the smartphone 40 can skip the automatic photography process when the same shooting conditions are met multiple times. In addition, the smartphone 40 can eliminate the annoyance that customers feel when automatic photography is performed repeatedly.

[0167] According to this embodiment, the smartphone 40 can receive shooting conditions before the customer starts shopping. This allows the smartphone 40 to set different shooting conditions depending on the store, the customer, the time of entry, etc. Therefore, even if the operation differs from store to store, the smartphone 40 can easily change the settings for shooting conditions.

[0168] According to this embodiment, the smartphone 40 can transmit captured image data stored in its memory unit to the monitoring server 26. This allows the smartphone 40 to retransmit captured image data stored in its memory unit that was not previously transmitted to the monitoring server 26. Therefore, the smartphone 40 can supplement its data by transmitting captured image data on different occasions. The monitoring server 26 can easily manage the captured image data.

[0169] According to this embodiment, the smartphone 40 can transmit captured image data and additional information related to the captured image data to the monitoring server 26. This allows the smartphone 40 to transmit captured image data and information related to shooting, such as shooting conditions, to the monitoring server 26 in association. The monitoring server 26 can manage the captured image data and information related to shooting, such as shooting conditions, in association. The attendant can confirm the customer's registered products based on the captured image and additional information, using the attendant image displayed on the monitoring terminal 23.

[0170] The embodiments of the transaction processing system 100 have been described above, but the embodiments are not limited thereto.

[0171] In this embodiment, the smartphone operated by the customer in the sales area may be a tablet-type terminal attached to a shopping cart. In this case, the tablet-type terminal has a built-in camera or an external camera is connected to it. Furthermore, the smartphone operated by the customer may be a smartphone lent to the customer by the store, or a smartphone owned by the customer personally.

[0172] In this embodiment, we have used a smartphone operated by a customer who has registered as a member as an example, but we are not limited to that. A customer may register products using a smartphone without registering as a member.

[0173] In this embodiment, the server system 10 was constructed using cloud computing. In this regard, the POS system 20 may also include the functionality of the server system 10. That is, it is possible to construct the transaction processing system 100 in a single store.

[0174] In this embodiment, the server system 10 is configured with a database server 11, a management server 12, and a virtual POS server 13. The server system 10 may also be configured with a single server that integrates the functions of the database server 11, the management server 12, and the virtual POS server 13.

[0175] Similarly, in each store's POS system 20, instead of dividing the functions between the store server 21, accounting server 22, and monitoring server 26, the functions of the store server 21, accounting server 22, and monitoring server 26 may be consolidated into a single server.

[0176] In addition, several embodiments of the present invention have been described, but these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be carried out 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 variations are included within the scope of the invention, as well as within the scope of the invention and its equivalents as described in the claims. [Explanation of Symbols]

[0177] 10…Server system, 11…Database server, 12…Management server, 13…Virtual POS server, 14…Communication line, 15…Router, 20…POS system, 21…Store server, 22…Accounting server, 23…Monitoring terminal, 24…POS terminal, 25…Dedicated accounting machine, 26…Monitoring server, 27…In-store network, 28…Router, 29…Access point, 30…Network, 40…Smartphone, 70…Linkage table, 80…Transaction file, 100…Transaction processing system, 111…Franchise database, 112…Member database, 113…First product master 211...Second product master, 231...Processor, 232...Main memory, 233...Auxiliary storage unit, 234...Touch panel, 235...Audio output device, 236...Communication interface, 237...Transmission path, 261...Processor, 262...Main memory, 263...Auxiliary storage unit, 264...Communication interface, 265...Transmission path, 400...Stand, 401...Processor, 402...Main memory, 403...Auxiliary storage unit, 404...Touch panel, 405...Camera, 406...Audio output device, 407...Wireless communication unit, 408...Mobile communication unit T, 409...Transmission line, 2310...Receiver, 2311...Display control unit, 2612...Acquisition unit, 2631...Transaction data storage area, 2632...Shooting condition storage area, 2633...Captured image storage area, 4010...Receiver, 4011...Determination unit, 4012...Display control unit, 4013...Shooting control unit, 4014...Acquisition unit, 4015...Storage control unit, 4016...Transmission unit, 4031...Smartphone POS app, 4032...Transaction data storage area, 4033...Shooting condition storage area, ARa...Frame line, ARB...Frame line, ARC...Area, ARD...Thumbnail image area, ARe...Captured image area, ARF...Thumbnail Image area, ARg... Captured image area, Ba... Camera activation button, Bb... No barcode button, Bc... Scan button, Bd... Checkout button, Be... Back button, Bf... Exit button, Bg... Confirmation button, Bh... OK button, Bi... Back button, Bj... OK button, Baa... Retake button, Bab... Shoot next basket button, Bac... Complete button, C... Cart, C1... Caster section, C2... Handle frame section, C3... Basket support section, C4... Pole, C21... Vertical frame, C22... Handle bar, Ca... First image, Cin... Entry code, CMa... Entry request commandCMb...Entry denial command, CMc...Entry approval command, CMd...Creation instruction command, CMe...Registration request command, CMf...Registration request command, CMg...Registration response command, CMh...Payment request command, CMi...Payment approval command, CMj...Payment completion notification command, Ma...Mark, Mb...Mark, Sa...Entry code reading screen, Sb...Registration in progress screen, Sc...Scanning screen, Sd...Registration in progress screen, Se...Payment screen, Sf...Guidance screen, Sfa...Shooting guide screen, Sg...Registered product details screen, Sh...Registered product confirmation screen, Si...Registered product confirmation screen.

Claims

1. A determination unit that determines whether the information regarding the product registration meets the shooting conditions, A display control unit that displays automatic product shooting guidance on the display unit based on the determination result of the determination unit, Based on the automatic shooting of the aforementioned product, an acquisition unit acquires the captured image data of the product, A transmission unit that transmits the captured image data acquired by the acquisition unit, Equipped with, The aforementioned shooting conditions include the first time that the number of registered products reaches a predetermined number. Information processing terminal.

2. The system further includes a receiving unit that receives the aforementioned shooting conditions before the user starts shopping. The information processing terminal according to claim 1.

3. The transmitting unit transmits the captured image data stored in the storage unit. The information processing terminal according to claim 1.

4. The transmitting unit transmits the captured image data and additional information relating to the captured image data. The information processing terminal according to claim 1.

5. On the computer, A determination function that determines whether the information registered for the product meets the shooting conditions, A display control function that displays automatic product photography guidance based on the judgment result, Based on the automatic shooting of the aforementioned product, an acquisition function is provided to acquire the image data of the photographed product. A transmission function for sending captured image data, An information processing program that enables the execution of, The aforementioned shooting conditions include the first time that the number of registered products reaches a predetermined number. Information processing program.

Images