Program, product sales data processing device

Abstract

To provide service using a portable terminal which can be easily used even by a beginner.SOLUTION: A program allows a computer to function as a commodity sales data processing device. The program allows the computer to function as: imaging means for imaging a commodity to be purchased; guiding means for guiding a procedure to an operator using guide images for guiding the procedure; and display means for enabling a captured image by the imaging means to be displayed. The display means displays a part or all of a first guide image as one of the guide images on a captured image display area for displaying the captured image. The guide means completes the guide using the first guide image on the basis of predetermined conditions.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a program and a product sales data processing device.

Background Art

[0002] A self-service system in which customers themselves register products using a mobile terminal has been proposed. On the other hand, systems that display guidance for products to be imaged are known (see, for example, Patent Document 1).

Prior Art Literature

Patent Literature

[0003]

Patent Document 1

Summary of the Invention

Problem to be Solved by the Invention

[0004] However, there are also customers who are not accustomed to the self-service system as described above. Systems such as those described above cannot support such customers as described above.

[0005] The present invention has been made in view of such circumstances, and an object of the present invention is to provide a technology that enables even beginners to easily use services using a mobile terminal.

Means for Solving the Problem

[0006] One aspect of the present invention for solving the above-mentioned problems is a program for causing a computer to function as a product sales data processing device, wherein the computer functions as an imaging means for capturing images of products to be purchased, a guidance means for guiding an operator through a procedure using guidance images, and a display means capable of displaying the images captured by the imaging means, wherein the display means displays part or all of a first guidance image, which is one of the guidance images, in an imaging image display area for displaying the captured images, and the guidance means terminates the guidance using the first guidance image based on predetermined conditions. [Brief explanation of the drawing]

[0007] [Figure 1] This is a conceptual diagram of a network used to explain the sales system. [Figure 2] This is an example of a cloud server configuration. [Figure 3] This is an example of information stored on a cloud server. [Figure 4] This is an example of a mobile device configuration. [Figure 5] This is an example of a payment processing system configuration. [Figure 6] This is an example of how it looks on a mobile device. [Figure 7] This is an example of how it looks on a mobile device. [Figure 8] This is an example of how it looks on a mobile device. [Figure 9] This is an example of how it looks on a mobile device. [Figure 10] This is an example of how it's displayed on a mobile device. [Figure 11] This is a sequence diagram illustrating an example of processing between a mobile device and a cloud server. [Figure 12] This is a sequence diagram illustrating an example of processing between a mobile device and a cloud server. [Figure 13] This is a sequence diagram illustrating an example of processing between a mobile device and a cloud server. [Figure 14] This is a sequence diagram illustrating an example of processing between a mobile device and a cloud server. [Figure 15]This is a sequence diagram illustrating an example of processing between a mobile device and a cloud server. [Figure 16] This is a sequence diagram showing an example of processing involving a payment device, a mobile terminal, and a cloud server. [Modes for carrying out the invention]

[0008] Figure 1 is a conceptual diagram of a network illustrating the sales system 1 of this embodiment. The sales system 1 shown in Figure 1 includes a headquarters server 10, a cloud server 20, a store controller 30 (e.g., a server), a transaction status management device 40 (e.g., a personal computer), a settlement device 50, a registration settlement device 51, and a mobile terminal 60.

[0009] The store controller 30, transaction status management device 40, settlement device 50, and registration settlement device 51 are connected via LAN 19 (either wired or wireless) to enable communication. The sales system 1 can be installed in various types of stores (supermarkets, convenience stores, drugstores, home centers, consumer electronics stores, etc.).

[0010] In Figure 1, the number of each device (terminal) is illustrative. For example, in Figure 1, "..." is shown to the right of the transaction status management device 40, but the number of transaction status management devices 40 installed in one store only needs to be one or more. Also, for example, in Figure 1, two mobile terminals 60 are shown, but the number of mobile terminals 60 used in the store will vary depending on the number of customers.

[0011] Sales system 1 provides a self-service (hereinafter sometimes referred to as Service A) in which customers register products using a mobile terminal 60 and make payments using a payment device 50. In other words, Service A is a self-service in which customers register products and make payments themselves, but they use a mobile terminal 60 for product registration and a payment device 50 for payment.

[0012] Furthermore, in addition to Service A, the sales system 1 also provides other services. For example, as other services, the sales system 1 can provide a service in a mode where a customer registers and settles products using a registered settlement device 51, and a service in a mode where a clerk registers products using a registration device (not shown) and a customer performs settlement using a settlement device (not shown).

[0013] The headquarter server 10 is installed outside the store (for example, at the head office, a data center, etc.) and is a server that manages the entire sales system 1. The headquarter server 10 stores, for example, various types of information necessary for operating services including Service A (for example, product masters, special sale files, etc.) and service performance information at the store (for example, sales performance information, product sales performance information, etc.). The headquarter server 10 communicates with the cloud server 20 and the store controller 30. The headquarter server 10 may communicate with other devices (for example, the transaction status management device 40, the settlement device 50, etc.). The headquarter server 10 may be configured of a plurality of servers.

[0014] The cloud server 20 is installed outside the store (for example, at a data center, etc.) and is a server that provides Service A. The cloud server 20 stores, for example, various types of information necessary for operating Service A (for example, product masters, transaction information (also referred to as cart information), etc.). The cloud server 20 communicates with the headquarter server 10 and the mobile terminal 60. The cloud server 20 may communicate with other devices (for example, the store controller 30, the transaction status management device 40, etc.). The cloud server 20 may be configured of a plurality of servers.

[0015] The store controller 30 is a device that controls the part related to the relevant store in the sales system 1. The store controller 30 communicates with each device in the LAN 19 (for example, the settlement device 50, etc.) and each device outside the LAN 19 (for example, the headquarter server 10). For example, the store controller 30 receives product masters and special sale files from the headquarter server 10 and supplies them to the settlement device 50.

[0016] The transaction status management device 40 is primarily a device that manages (monitors and controls) each device within the LAN 19. For example, the transaction status management device 40 communicates with each device within the LAN 19 and monitors the processing status, operating status, etc., of each device within the LAN 19. The transaction status management device 40 may also communicate with devices outside the LAN 19 (for example, the headquarters server 10, the cloud server 20) (either directly or via the store controller 30). For example, the transaction status management device 40 may refer to transaction information (cart information) stored in the cloud server 20.

[0017] The mobile terminal 60 is used when registering products in Service A. In other words, customers use the mobile terminal 60 when registering products in Service A.

[0018] The mobile terminal 60 may be owned by the customer (member) using Service A, or it may be lent by the store. In this embodiment, the mobile terminal 60 will be described as being owned by the customer using Service A. In this embodiment, the mobile terminal 60 executes a predetermined application program (hereinafter sometimes referred to as a specific app) and registers products in Service A. In other words, a customer who intends to use Service A installs the specific app on their mobile terminal 60 in advance and starts the specific app before using Service A. The mobile terminal 60 may also access a predetermined server (for example, a cloud server 20 or a dedicated server (not shown), etc.), download the specific app from the server, and install it.

[0019] Furthermore, in this embodiment, the mobile terminal 60 is described as being used while attached to a shopping cart (not shown). For example, a shopping cart equipped with a mobile terminal holder for setting the mobile terminal 60, in addition to a shopping basket holder for setting the shopping basket, is prepared near the entrance or exit of the store (or the entrance if the entrance and exit are separate). When a customer using service A arrives at the store, they set the shopping basket in the shopping basket holder of the shopping cart, set the mobile terminal 60 in the mobile terminal holder, and proceed into the store.

[0020] The payment device 50 is used when settling payments in service A. In other words, customers use the payment device 50 when settling payments for items they have registered using their mobile terminal 60.

[0021] The registration and settlement device 51 is primarily used by customers. The registration and settlement device 51 comprises a scanner unit and a settlement unit, and is used for registering and settling payments for goods.

[0022] Figure 2 shows an example configuration of the cloud server 20. The cloud server 20 comprises a CPU 201, a ROM 202, a RAM 203, and a hard disk 204. These components can communicate with each other via a bus.

[0023] The CPU 201 is a central processing unit that controls the operation of the cloud server 20 by reading and executing programs stored in the ROM 202. ROM202 is read-only memory that stores various types of information used by the CPU201, including programs. RAM203 is a read / write memory that stores various types of information as main memory. For example, RAM203 stores information read from ROM202 and hard disk 204, information obtained from external sources, and information generated during processing. The hard disk 204 stores various types of information (see, for example, Figure 3) as an auxiliary storage device. For example, the hard disk 204 may store programs executed by the CPU 201 instead of the ROM 202. Alternatively, the hard disk 204 may store information read from the ROM 202, information acquired from external sources, information generated during processing, etc., instead of the RAM 203. The communications unit 215 transmits and receives information with other devices (for example, the mobile terminal 60, the headquarters server 10, etc.).

[0024] Figure 3 shows an example of information stored in the cloud server 20. Figure 3(A) shows an example of transaction information (cart information) stored in the cloud server 20. The cloud server 20 generates transaction information at the start of a transaction. The cloud server 20 also updates the transaction information as the transaction progresses. The transaction information shown in Figure 3(A) includes transaction identification information (cart identification information), transaction start date and time, transaction end date and time, member identification information, and registered product information.

[0025] Transaction identification information is identification information that uniquely identifies transaction information. For example, transaction identification information may consist of store identification information, a date, and a serial number (e.g., a store-specific serial number for each date). The transaction start date and time is the start date and time of the transaction (e.g., the date and time the cart information was generated, or the date and time the product was registered (the date and time the registration information (product 1) in Figure 3(A) was recorded)). The transaction end date and time is the end date and time of the transaction (e.g., the date and time the settlement was completed).

[0026] Member identification information is information that uniquely identifies a customer (member). Member identification information may be determined when a specific application is downloaded. For example, member identification information may be generated (numbered) by a predetermined server (cloud server 20, dedicated server). For example, the predetermined server may generate member identification information when it receives a request from a mobile terminal 60 to download a specific application. If the dedicated server generates member identification information, the dedicated server may notify the cloud server 20 of the member identification information. As another example, member identification information may be determined by the customer. For example, it may be entered by the customer when the mobile terminal 60 sends a request to the predetermined server to download a specific application (after which the predetermined server confirms that it does not overlap with other member identification information). If the dedicated server obtains member identification information, the dedicated server may notify the cloud server 20 of the member identification information.

[0027] Furthermore, the mobile terminal 60 may store member identification information. For example, if the member identification information is generated by a predetermined server, the mobile terminal 60 may receive and store the member identification information from the predetermined server. Also, for example, if the member identification information is entered by the member, the mobile terminal 60 may store the member identification information entered by the member.

[0028] The registration information (total) is updated each time a product is registered. The registration information (total) includes the number of items, subtotal amount, etc. The registration information (product N; N is an integer) is the registration information for N items. The registration information (product N) includes the product code, product name, quantity, price, etc.

[0029] Figure 3(B) shows an example of member performance information stored by the cloud server 20. The cloud server 20 generates member performance information, for example, after determining member identification information. The cloud server 20 also updates the member performance information, for example, each time a transaction is made using service A. The member performance information shown in Figure 3(B) includes transaction identification information, the number of times the app has been launched, the date and time of the first app launch, and the date and time of the previous app launch.

[0030] As mentioned above, member identification information is information that uniquely identifies a customer (member). App launch count is the number of times a specific app has been launched. The initial value for the app launch count is "0 (times)". First app launch date is the date and time of the first launch of the specific app (the date and time the specific app was first launched). Last app launch date is the date and time of the last launch of the specific app (the date and time the specific app was last launched (most recent launch date and time)).

[0031] Furthermore, member performance information may include information other than that described above. For example, member performance information may include the number of points, member rank, date of the previous (most recent) purchase (which may be the date of the previous purchase using Service A), frequency of visits within a specified period (which may be the frequency of visits and use of Service A), and total purchase amount within a specified period (which may be the total purchase amount using Service A).

[0032] The information stored by the cloud server 20 is not limited to product master data (not shown), transaction information (Figure 3(A)), and member performance information (Figure 3(B)). For example, the cloud server 20 may store (generate, update) member master data. For example, in a request to download a specific application, the cloud server 20 may acquire information identifying the mobile terminal 60 (e.g., MAC address, telephone number, etc.) and information entered by the customer (e.g., name, date of birth, address, gender, etc.), and store (generate) member master data based on the acquired information. If the dedicated server acquires the above information, the dedicated server may supply the acquired information to the cloud server 20, and the cloud server 20 may store (generate) member master data based on the supplied information. Alternatively, the headquarters server 10 may store member master data instead of or in addition to the cloud server 20.

[0033] Figure 4 shows an example configuration of a mobile terminal 60. The mobile terminal 60 comprises a CPU 301, ROM 302, RAM 303, storage 304, display unit 305, audio output unit (speaker, speaker terminal) 314, communication unit 315, imaging unit (camera) 316, and audio input unit (microphone, microphone terminal) 318. These components can communicate with each other via a bus.

[0034] The CPU 301 is a central processing unit that controls the operation of the mobile terminal 60 by reading and executing programs stored in the ROM 302 and programs stored in the storage 304 (for example, specific downloaded applications). For example, when the imaging unit 316 is capturing a barcode attached to a product, the CPU 301 extracts feature points from the captured image (the image acquired as a through image (live view)) captured by the imaging unit 316 and recognizes the barcode as an object. ROM302 is read-only memory that stores various types of information used by the CPU301, including programs. RAM303 is a read / write memory that stores various types of information as main memory. For example, RAM303 stores information read from ROM302 and storage304, information obtained from external sources, and information generated during processing. Storage 304 stores various types of information (for example, specific applications) as an auxiliary storage device. Instead of RAM 303, storage 304 may store information read from ROM 302, information acquired from external sources, information generated during processing, etc.

[0035] The display unit 305 is a touch display that displays various information and accepts various inputs. The voice output unit 314 outputs sound. For example, the voice output unit 314 outputs confirmation sounds, warning sounds, voice guidance, etc. In addition, the voice output unit 314 may output ringtones and the other party's voice in relation to a call. Furthermore, the voice output unit 314 may output the string (wording) of the guidance in voice in conjunction with the display (display timing) of each screen related to guidance (guidance information) (tutorial screen, menu screen, initial registration screen, settlement 2D code display screen, settlement 2D code reading completion screen, transaction completion screen, status confirmation screen, etc.). If the screen is maintained for a certain period of time, the voice guidance may be repeated at regular intervals (the number of repetitions may be limited to a predetermined number (for example, 1 to 2 times)). If the guidance is written in a foreign language, the voice guidance may be provided in that foreign language.

[0036] The communication unit 315 transmits and receives information with other devices (for example, the cloud server 20). The communication unit 315 may also transmit and receive voice information with other mobile terminals 60, etc., in connection with calls. The communication by the communication unit 315 may be wireless communication using methods specified by the International Telecommunication Union (ITU) (4G, 5G, etc.) or wireless communication using methods specified by wireless LAN organizations (Wi-Fi®, etc.). The imaging unit 316 takes images. For example, the imaging unit 316 takes images of various codes (e.g., barcodes, 2D codes). The voice input unit 318 receives voice input. For example, the voice input unit 318 receives voice input for operations performed using voice recognition. The voice input unit 318 also receives voice input to be sent to the other party in relation to a call.

[0037] The mobile terminal 60 may further include a positioning unit (GPS function), a motion detection unit (e.g., an acceleration sensor, an angular velocity sensor, etc.), a short-range wireless communication unit (Bluetooth®, an infrared sensor, etc.).

[0038] Figure 5 shows an example configuration of the payment device 50. The payment device 50 includes a CPU 101, a ROM 102, a RAM 103, a hard disk 104, a display unit 105, a scanner unit 106, a card payment unit (non-cash payment unit) 108, a change dispenser (cash payment unit) 109, a printing unit 113, an audio output unit 114, a communication unit 115, an imaging unit 116, and a signpost 117. These components can communicate with each other via a bus.

[0039] The CPU 101 is a central processing unit that controls the operation of the settlement device 50 by reading and executing programs stored in the ROM 102. ROM102 is read-only memory that stores various types of information used by the CPU101, including programs. RAM103 is a read / write memory that stores various types of information as main memory. For example, RAM103 stores information read from ROM102 and hard disk 104, information obtained from external sources, and information generated during processing. The hard disk 104 stores various types of information as an auxiliary storage device. For example, instead of the ROM 102, the hard disk 104 may store programs executed by the CPU 101. Alternatively, instead of the RAM 103, it may store information read from the ROM 102, information acquired from external sources, information generated during processing, etc. Note that a storage device such as an SSD (Solid State Drive) may be provided instead of the hard disk 104. The display unit 105 is a touch display that displays various information and accepts various inputs.

[0040] The scanner unit 106 optically reads various types of information. Specifically, the scanner unit 106 scans the code (2D code GA631 for payment (described later)) displayed on the mobile terminal 60 and reads the information necessary for payment processing. The scanner unit 106 may also scan codes attached to gift certificates (vouchers, coupons, discount vouchers) and various cards (e.g., membership cards, point cards, etc.) and read the information contained therein. The scanner unit 106 may also scan codes attached to employee name tags, etc., and read employee codes. The scanner unit 106 may also scan codes attached to products and read product codes (JAN codes, etc.).

[0041] The card payment unit 108 is a payment mechanism that accepts various types of cards (credit cards, prepaid cards such as transportation cards, cash cards for debit payments, point cards for point payments, etc.). The card payment unit 108 includes a card recognition unit (reading unit), a display unit, and an operation unit, but it is sufficient if it includes at least a card recognition unit. The card recognition unit may recognize various types of cards (e.g., point cards, membership cards, shareholder cards, etc.) for purposes such as granting benefits or discounts. The change dispenser 109 is a cash payment mechanism that has an input slot for banknotes and coins, and an output slot for banknotes and coins. It calculates the amount to be inserted into the input slot, calculates the change amount which is the difference between the inserted amount and the purchase price, and dispenses the change from the output slot. When banknotes or coins are inserted into the input slot, this is detected by a sensor (detection of the insertion, detection of the number of coins of each denomination, etc.).

[0042] The printing unit 113 prints and issues various media (receipts, etc.). The audio output unit 114 outputs sound. For example, the audio output unit 114 outputs confirmation sounds, warning sounds, voice guidance, etc. The communication unit 115 transmits and receives information with other devices (for example, the store controller 30, the transaction status management device 40, etc.). The imaging unit 116, for example, images the customer. The payment device 50 may be equipped with two or more imaging units 116, and may simultaneously image the face and hands (near the input and output slots of the change machine 109). The sign pole 117 has a light-emitting part at its tip, and various information (such as calling for staff, operating status, etc.) is communicated by the way the light-emitting part is illuminated.

[0043] The payment device 50 may further include a key operation unit consisting of various keys (buttons). The payment device 50 may also further include a sensor (such as a motion sensor) for detecting the presence of a person. Furthermore, the payment device 50 may further include a sensor for detecting when any of the media printed or issued by the printing unit 113 has been removed (taken out).

[0044] (Displayed on mobile device 60) The following describes the display on the mobile terminal 60. Figures 6 to 9 are examples of the display on the mobile terminal 60. Figure 10 shows the display on the mobile terminal 60, etc. Figures 6 to 10 (excluding Figure 10(D)) show the screens related to service A in order after the launch of a specific application. Specifically, if this is the first launch of the specific application, the mobile terminal 60 will display the following after the launch of the specific application: Figure 6(A) → Figure 6(B) → Figure 6(C) → Figure 6(D) → Figure 7(A) → Figure 7(B) → Figure 7(C) → Figure 7(D) → Figure 8(A) → Figure 8(B) → Figure 8(C) → Figure 8(D) → Figure 9(A) → Figure 9(B) → Figure 9(C) → Figure 9(D) → Figure 10(A) → Figure 10(B) → Figure 10(C). If this is the second or subsequent launch of the specific application, the mobile terminal 60 will display the following after launching the specific application: Figure 6(D) → Figure 7(A) → Figure 7(B) → Figure 7(C) → Figure 7(D) → Figure 8(A) → Figure 8(B) → Figure 8(C) → Figure 8(D) → Figure 9(A) → Figure 9(B) → Figure 9(C) → Figure 9(D) → Figure 10(A) → Figure 10(B) → Figure 10(C).

[0045] Figures 6(A) to 6(C) are the tutorial screens for Service A. Figure 6(D) is the menu screen (start screen) for Service A. The tutorial screen is displayed when this particular application is launched for the first time, but it is not displayed when this particular application is launched for the second time or later.

[0046] (If this is the first time the specific app has been launched) If this is the first time the specific application is launched, the mobile device 60 will sequentially display the tutorial screens shown in Figures 6(A) to 6(C), and then display the menu screen shown in Figure 6(D).

[0047] The tutorial screen shown in Figure 6(A) is the first tutorial screen displayed when this particular application is launched for the first time. In other words, when a member launches the specific application and it is the first time, the mobile terminal 60 displays the tutorial screen shown in Figure 6(A). The tutorial screen shown in Figure 6(A) displays image GA601a and message MS602a introducing the shopping (concept) of service A. The tutorial screen shown in Figure 6(A) (and similarly the tutorial screen shown in Figure 6(B)) also has a "Next" button BT603.

[0048] The tutorial screen shown in Figure 6(B) is displayed following the tutorial screen shown in Figure 6(A). When a member presses the Next button BT603 on the tutorial screen shown in Figure 6(A), the mobile terminal 60 displays a tutorial screen as shown in Figure 6(B). The tutorial screen shown in Figure 6(B) displays an image GA601b and a message MS602b introducing shopping (product registration) using Service A.

[0049] The tutorial screen shown in Figure 6(C) is displayed following the tutorial screen shown in Figure 6(B). When a member operates the Next button BT603 on the tutorial screen shown in Figure 6(B), the mobile terminal 60 displays the tutorial screen shown in Figure 6(C). The tutorial screen shown in Figure 6(C) displays an image GA601c and a message MS602c that introduce the shopping (payment) process using Service A. The tutorial screen shown in Figure 6(C) also has a Service Start button BT604 that declares the start of the service.

[0050] Images GA601a to GA601c may be collectively referred to as tutorial image GA601. Similarly, messages MS602a to MS602c may be collectively referred to as message MS602.

[0051] The menu screen shown in Figure 6(D) is displayed following the tutorial screen. When a member operates the service start button BT604 on the tutorial screen shown in Figure 6(C), the mobile terminal 60 displays a menu screen as shown in Figure 6(D). The menu screen shown in Figure 6(D) contains various buttons related to service A. For example, the menu screen shown in Figure 6(D) contains a shopping start button BT610 to declare the start of shopping. Note that the "Member Number" on the menu screen shown in Figure 6(D) is member identification information.

[0052] (If this is the second or subsequent launch of the specific app) If this is the second or subsequent launch of the specific application, the mobile terminal 60 will display the menu screen shown in Figure 6(D) without displaying the tutorial screen shown in Figures 6(A) to 6(C). In other words, if a member launches the specific application and this is the second or subsequent launch, the mobile terminal 60 will first display the menu screen shown in Figure 6(D).

[0053] Figures 7(A) to 9(C) show the registration screens. The registration screen shown in Figure 7(A) is displayed after the menu screen shown in Figure 6(D). When a member operates the shopping start button BT610 on the menu screen shown in Figure 6(D), the mobile terminal 60 displays the registration screen shown in Figure 7(A). The registration screen shown in Figure 7(B) is displayed after the registration screen shown in Figure 7(A). If a predetermined time (e.g., 0.5 seconds) elapses without an item being registered (without the barcode attached to the item being read) on the registration screen shown in Figure 7(A), the mobile terminal 60 displays the registration screen shown in Figure 7(B). The registration screen shown in Figure 7(C) is displayed after the registration screen shown in Figure 7(B). If a predetermined time (e.g., 0.5 seconds) elapses without an item being registered on the registration screen shown in Figure 7(B), the mobile terminal 60 displays the registration screen shown in Figure 7(C).

[0054] Furthermore, if a predetermined time (e.g., 0.5 seconds) elapses without a product being registered on the registration screen shown in Figure 7(C), the mobile terminal 60 displays the initial registration screen shown in Figure 7(A). Similarly, if another predetermined time elapses, it displays the initial registration screen shown in Figure 7(B). Similarly, if another predetermined time elapses, it displays the initial registration screen shown in Figure 7(C). Similarly, if another predetermined time elapses, it displays the initial registration screen shown in Figure 7(A) (and so on). In other words, the mobile terminal 60 repeatedly displays the product scan guide image GA624 (described later) on the initial registration screen (described later).

[0055] The registration screens shown in Figures 7(A) to 7(C) (and similarly in Figure 7(D)) represent the registration screen when no products have been registered yet (before the first product has been registered). In the following explanation, the registration screen when no products have been registered will sometimes be referred to as the initial registration screen to distinguish it from the registration screen when one or more products have already been registered.

[0056] The top of the registration screen is the image display area HR621, which primarily displays the captured image. The central part of the image display area HR621 is the barcode reading area (a rectangular area in the center displaying the message "Please hold the barcode over the scanner"), which is suitable for reading barcodes. The bottom of the registration screen is the registration information display area HR622, which primarily displays the product registration information. The very bottom of the registration screen is the related information display area HR623, which displays other related information.

[0057] The initial registration screen explains how to register a product. For example, the initial registration screens shown in Figures 7(A) to 7(C) display images (images GA624a, GA624b, and GA624c) that explain how to register a product. Image GA624a of the initial registration screen shown in Figure 7(A) shows how to bring the barcode attached to the product close to the mobile terminal 60 (the mobile terminal 60 set in the mobile terminal holder) so that the barcode attached to the product is captured by the mobile terminal 60. Image GA624b of the initial registration screen shown in Figure 7(B) shows the process of capturing the barcode. Image GA624c of the initial registration screen shown in Figure 7(C) shows the barcode being read. Images GA624a to GA624c are sometimes collectively referred to as product scan guide images GA624.

[0058] As shown in Figures 7(A) to 7(C), the mobile terminal 60 displays the product scan guide image GA624 at a position that spans the captured image display area HR621 and the registered information display area HR622 (in front of both the captured image display area HR621 and the registered information display area HR622). More specifically, the mobile terminal 60 displays the product scan guide image GA624 such that the upper part of the product scan guide image GA624 is positioned in front of the area of ​​the captured image display area HR621 below the barcode reading area, and the remaining part of the product scan guide image GA624 is positioned in front of the area of ​​the registered information display area HR622 excluding the lower area. The top of the product scan guide image GA624 has a bubble-like shape. The bubble in the product scan guide image GA624 points to the barcode reading area of ​​the captured image display area HR621 (symbol f in Figure 7(A)).

[0059] Members can have the barcode attached to the product scanned regardless of which of the initial registration screens shown in Figures 7(A) to 7(C) is displayed (i.e., regardless of which of images GA624a to GA624c is displayed).

[0060] Figure 7(D) shows the initial registration screen when XX bread is being imaged as the first product item. In the image display area HR621 (barcode reading area) of the initial registration screen shown in Figure 7(D), the barcode attached to XX bread is displayed as a pass-through image. Note that Figure 7(D) is an example of a member having the barcode read on the initial registration screen shown in Figure 7(C) (while image GA624c is displayed), but as mentioned above, members can also have the barcode read on the initial registration screen shown in Figure 7(A) (while image GA624a is displayed) and the initial registration screen shown in Figure 7(B) (while image GA624b is displayed).

[0061] The registration screen shown in Figure 8(A) is displayed following the initial registration screen shown in Figure 7(D). Specifically, the registration screen shown in Figure 8(A) is the registration screen after the registration of one product item (XX Bread) has been completed. In the registration information display area HR622 of the registration screen shown in Figure 8(A), the product name "XX Bread", quantity "1", and price "¥220" are displayed (symbol a). In addition, the approximate total "1 item ¥220" is displayed in the registration information display area HR622 (symbol b). Furthermore, in front of the captured image display area HR621 of the registration screen shown in Figure 8(A), a small screen SG625 showing the product name "XX Bread" and price "¥220" is displayed.

[0062] The process from the initial registration screen shown in Figure 7(D) to the display of the registration screen shown in Figure 8(A) will be explained below. The mobile terminal 60 sends the product code obtained from the barcode to the cloud server 20. The cloud server 20 refers to the product master and obtains the product name "○○ Bread" and price "¥220" based on the product code. The cloud server 20 stores the product code, product name "○○ Bread", quantity "1", price "¥220", etc. as registration information in the transaction information for that transaction. The cloud server 20 also sends the registration information (product name "○○ Bread", price "¥220", etc.) to the mobile terminal 60. The mobile terminal 60 displays the registration information received from the cloud server 20 in the registration information display area HR622 and the small screen SG625.

[0063] Furthermore, the mobile terminal 60 displays some of the registration information (quantity) as a quantity button. The quantity button is used to change the quantity. In addition, after registering a product (one product item), the mobile terminal 60 displays a button BT626 to indicate that product registration is complete and the user is proceeding to checkout (payment).

[0064] The registration screen shown in Figure 8(B) is displayed following the registration screen shown in Figure 8(A). If a predetermined time (for example, 2 seconds) has elapsed on the registration screen shown in Figure 8(A), the mobile terminal 60 displays the registration screen shown in Figure 8(B). On the registration screen shown in Figure 8(B), the small screen SG625 that was displayed on the registration screen shown in Figure 8(A) has been erased. Also, the registration screen shown in Figure 8(B) displays an image GA627 explaining the button BT626 to proceed to payment (with the message "Touch here to proceed to payment").

[0065] The registration screen shown in Figure 8(C) is the registration screen that appears after a further time has passed since the registration screen shown in Figure 8(B). In the registration screens shown in Figures 7(D) to 8(B), the image capture display area HR621 displayed the XX bread as a pass-through image, but it is not displayed in the image capture display area HR621 of the registration screen shown in Figure 8(C). In other words, since the registration of XX bread is complete, when a member adds XX bread to their cart, the XX bread moves outside the imaging range of the imaging unit 316, and the mobile terminal 60 displays the registration screen shown in Figure 8(C). Note that if a member adds XX bread to their cart before the small screen SG625 is erased (while it is displayed), the state of the registration screen shown in Figure 8(B) will not occur, and the transition will be from Figure 8(A) to Figure 8(C).

[0066] The registration screen shown in Figure 8(C) does not show any images of products, similar to the initial registration screens shown in Figures 7(A) to 7(C). However, unlike the initial registration screens shown in Figures 7(A) to 7(C), the registration screen in Figure 8(C) does not display the product scan guide image GA624, which explains how to register products. In other words, the mobile terminal 60 displays an image (product scan guide image GA624) explaining how to register products on the registration screen (initial registration screen) when no products have been registered yet, but does not display an image explaining how to register products on the registration screen when one or more products have already been registered.

[0067] Figure 8(D) shows the registration screen when XX Oolong Tea is being imaged as the second product item. In the image display area HR621 (barcode reading area) of the registration screen shown in Figure 8(D), the barcode attached to XX Oolong Tea is displayed as a pass-through image.

[0068] The registration screen shown in Figure 9(A) is displayed following the registration screen shown in Figure 8(D). Specifically, the registration screen shown in Figure 9(A) is the registration screen after the registration of two items (Oolong Tea) has been completed. In the registration information display area HR622 of the registration screen shown in Figure 9(A), the product name "Oolong Tea", quantity "1", and price "¥150" are additionally displayed. The updated estimated total "2 items ¥370" is also displayed in the registration information display area HR622. In addition, a small screen SG625 showing the product name "Oolong Tea" and price "¥150" is displayed in front of the captured image display area HR621 of the registration screen shown in Figure 9(A).

[0069] The registration screen shown in Figure 9(B) is displayed following the registration screen shown in Figure 9(A). If a predetermined time (for example, 2 seconds) has elapsed on the registration screen shown in Figure 9(A), the mobile terminal 60 displays the registration screen shown in Figure 9(B).

[0070] The registration screen shown in Figure 9(C) is the registration screen that appears after a further time has passed since the registration screen shown in Figure 9(B). In the registration screens shown in Figures 8(D) to 9(B), the image capture display area HR621 displayed "Oolong Tea" as a pass-through image, but it is not displayed in the image capture display area HR621 of the registration screen shown in Figure 9(C). Note that if the member adds "Oolong Tea" to the cart (shopping basket) before the small screen SG625 is erased (while it is displayed), the state of the registration screen shown in Figure 9(B) will not occur, and the transition will be from Figure 9(A) to Figure 9(C).

[0071] Figures 9(D), 10(A), and 10(B) show the payment 2D code display screens. The payment 2D code display screen shown in Figure 9(D) is displayed, for example, following the registration screen shown in Figure 9(C). When a member operates the button BT626 to proceed to payment on the registration screen shown in Figure 9(C), the mobile terminal 60 displays the payment 2D code display screen as shown in Figure 9(D). The payment 2D code display screen shown in Figure 10(A) is displayed following the payment 2D code display screen shown in Figure 9(D). If a predetermined time (e.g., 0.5 seconds) elapses without the payment 2D code GA631 (described later) being read by the payment device 50 on the payment 2D code display screen shown in Figure 9(D), the mobile terminal 60 displays the payment 2D code display screen as shown in Figure 10(A). The payment 2D code display screen shown in Figure 10(B) is displayed following the payment 2D code display screen shown in Figure 10(A). If a predetermined time (e.g., 0.5 seconds) elapses without the payment device 50 reading the payment 2D code GA631 (described later) on the payment 2D code display screen shown in Figure 10(A), the mobile terminal 60 displays the payment 2D code display screen as shown in Figure 10(B).

[0072] Furthermore, if a predetermined time has elapsed without the payment device 50 reading the payment 2D code GA631 (described later) on the payment 2D code display screen shown in Figure 10(B), the mobile terminal 60 will display the payment 2D code display screen shown in Figure 9(D). Similarly, if another predetermined time has elapsed, the payment 2D code display screen shown in Figure 10(A) will be displayed. Similarly, if another predetermined time has elapsed, the initial registration screen shown in Figure 10(B) will be displayed. Similarly, if another predetermined time has elapsed, the initial registration screen shown in Figure 9(D) will be displayed (and so on). In other words, the mobile terminal 60 repeatedly displays the payment 2D code scan guide image GA633 (described later) on the payment 2D code display screen, on the initial registration screen (described later), and on the payment 2D code display screen.

[0073] The payment QR code display screen shows the payment QR code GA631 and the message MS632. The payment QR code display screen also has a "Return to Shopping" button BT639. When the "Return to Shopping" button BT639 is pressed, the mobile terminal 60 displays the registration screen (the registration screen immediately before pressing the "Return to Shopping" button BT639).

[0074] The settlement 2D code GA631 is a 2D code representing the information necessary to execute the settlement process. For example, the settlement 2D code GA631 is a 2D code representing transaction identification information that identifies the transaction information of a particular transaction from among multiple transaction information stored on the cloud server 20. However, the information to be 2D coded does not have to be transaction identification information, as long as the transaction information of the transaction can be obtained after reading. For example, the settlement 2D code GA631 may be a 2D code representing the location information of the transaction information of the transaction (storage location within the sales system 1, such as a URI (Uniform Resource Identifier)).

[0075] Furthermore, the payment 2D code display screen displays images (images GA633a, GA633b, and GA633c) that explain how to have the payment device 50 read the payment 2D code GA631. Image GA633a in Figure 9(D) shows the payment 2D code GA631 displayed on the display unit 305. Image GA633b in Figure 10(A) shows how to bring the payment 2D code GA631 closer to the payment device 50 (scanner unit 106) so that it can be read. Image GA633c in Figure 10(B) shows how to change the angle of the payment 2D code GA631 (mobile terminal 60) so that it can be read by the payment device 50 (scanner unit 106). Images GA633a to GA633c are sometimes collectively referred to as payment 2D code scan guide images GA633.

[0076] As shown in Figures 9(D) to 10(B), in the payment 2D code display screen, the payment 2D code scan guide image GA633 is displayed below the payment 2D code GA631. Since the payment 2D code scan guide image GA633, which occupies a relatively large area, is displayed below the payment 2D code GA631 (towards the wrist, towards the hand), members can have the payment device 50 read the payment 2D code GA631 without strain (using natural movements, for example, without twisting the wrist too much, from an ergonomic standpoint).

[0077] Members can have the payment device 50 read the payment code GA631 regardless of which of the two-dimensional payment code display screens shown in Figures 9(D) to 10(B) is displayed (i.e., regardless of which of images GA633a to GA633c is displayed).

[0078] Figure 10(C) shows the screen indicating that the payment 2D code has been read. The payment 2D code reading completion screen shown in Figure 10(C) is displayed following the payment 2D code display screen. When a member has the payment device 50 read the payment 2D code GA631 displayed on the payment 2D code display screen, the mobile terminal 60 displays the payment 2D code reading completion screen as shown in Figure 10(C). The payment 2D code reading completion screen shown in Figure 10(C) displays a message indicating that the payment machine (payment device 50) has read the payment code (payment 2D code GA631) and a message indicating that payment should be made at the payment machine.

[0079] (Display on payment device 50) When the payment device 50 is in standby mode, it displays an initial screen (not shown). The initial screen displays a message instructing the user to scan the payment 2D code GA631 displayed on the mobile terminal 60, and an image explaining how to scan the payment 2D code GA631 displayed on the mobile terminal 60 (for example, an image similar to the payment 2D code scan guide image GA633). The initial screen may also include buttons for calling a store clerk, checking the balance, and switching languages. The store clerk call button is for calling a store clerk. The balance check button is for checking the balance of various cards. The language switch button is for switching the display (text) on the payment device 50 from Japanese to another language (English, etc.).

[0080] When the settlement device 50 reads the settlement 2D code GA631, it retrieves transaction information from the cloud server 20 and displays a product list screen as shown in Figure 10(D). The product list screen has a product list display area, a price range product quantity display area, and a total display area. The product list display area is for displaying a list of products to be settled. In the example shown in Figure 10(D), XX bread and XX oolong tea are displayed. The price range product quantity display area is for displaying the number of products in each price range (1000 yen or more, 500 yen or more but less than 1000 yen, 200 yen or more but less than 500 yen, and less than 200 yen) of the product to be settled. In the example shown in Figure 10(D), 1 is displayed for the number of products in the 200 yen or more but less than 500 yen range, and 1 is displayed for the number of products less than 200 yen. The total display area is for displaying the total of the transaction. In the example in Figure 10(D), the total score is displayed as 2, and the estimated total amount is 370 yen.

[0081] The product list screen also includes a call button for a store clerk and a checkout button. The checkout button is used to confirm that there are no problems with the items displayed on the product list screen and to proceed with the transaction. When the checkout button is pressed, the payment device 50 displays, for example, a payment type selection screen (not shown).

[0082] (Operation of mobile devices such as the 60 series) Figure 11 is a sequence diagram showing an example of processing by the mobile terminal 60 and the cloud server 20. Specifically, Figure 11 shows an example of processing by the mobile terminal 60 and the cloud server 20 from the time the mobile terminal 60 launches a specific application until the menu screen is displayed. In Figure 11 (and similarly in Figures 12, 13, 14, and 15), the left side shows the processing of the mobile terminal 60, and the right side shows the processing of the cloud server 20. It is assumed that this is the first time the specific application has been launched on the mobile terminal 60 (it is the initial launch). In other words, at the start of the flowchart in Figure 11, the member history information stored in the cloud server 20 (Figure 3(B)) is assumed to contain "0 (times)" as the number of times the application has been launched, corresponding to the member identification information of the member using the mobile terminal 60.

[0083] Step S1: The mobile device 60 launches a specific application based on the member's actions. For example, when a specific application is downloaded, the mobile device 60 displays a launch icon on the screen, and launches the specific application based on the member's interaction with that launch icon. Step S2: The mobile terminal 60 sends app launch information that notifies (reports) that a specific app has been launched. The app launch information includes member identification information.

[0084] Step S3: Cloud server 20 receives application launch information. Step S4: The cloud server 20 determines that this is the first time the specific application has been launched. Specifically, the cloud server 20 refers to the application launch count corresponding to the member identification information included in the application launch information. Since the application launch count is "0", the cloud server 20 determines that this is the first time the specific application has been launched.

[0085] Step S5: The cloud server 20 sends instructions to display the tutorial screen. In other words, if the cloud server 20 determines that this is the first time the specific application has been launched (i.e., it determines that this is the first launch), it sends instructions to display the tutorial screen. If the cloud server 20 determines that this is not the first time the specific application has been launched (i.e., it determines that this is the second or subsequent launch), it sends instructions to display the menu screen (Step S31 in Figure 12).

[0086] Step S6: The mobile device 60 receives instructions to display the tutorial screen. Step S7: The mobile terminal 60 displays the tutorial screen. That is, the mobile terminal 60 displays the tutorial screen based on the instructions from the cloud server 20 (information instructing the display of the tutorial screen) (Figures 6(A) to 6(C)). The screen information related to the tutorial screen (and similarly, screen information related to other screens displayed by the mobile terminal 60) is stored by the mobile terminal 60 as part of a specific application or as information attached to a specific application. Step S8: The mobile terminal 60 receives an operation from the member to instruct them to start the service. For example, the mobile terminal 60 receives an operation of the service start button BT604 on the tutorial screen shown in Figure 6(C). Step S9: The mobile terminal 60 transmits service activation instruction information to notify (report) that an operation to initiate the service has been performed. The service activation instruction information includes member identification information.

[0087] Step S10: The cloud server 20 receives service start instruction information. Step S11: The cloud server 20 sends information to instruct the display of the menu screen. In other words, when the cloud server 20 receives service start instruction information, it sends information to instruct the display of the menu screen. Furthermore, as described above, the cloud server 20 also sends information to instruct the display of the menu screen if it determines that this is not the first time that a particular application has been launched (i.e., if it determines that this is the second or subsequent launch) (Step S31 in Figure 12). Step S12: The cloud server 20 updates the app launch count. Specifically, the cloud server 20 adds 1 to the app launch count corresponding to the member identification information (updating it from "0 (times)" to "1 (times)"). The cloud server 20 also stores the current date and time as the date and time of the first app launch and the date and time of the previous app launch corresponding to the member identification information.

[0088] Step S13: The mobile terminal 60 receives information to instruct the display of the menu screen. Step S14: The mobile terminal 60 displays a menu screen instead of the tutorial screen (clears the tutorial screen). In other words, the mobile terminal 60 displays a menu screen based on instructions from the cloud server 20 (information instructing the display of the menu screen) (Figure 6(D)). The mobile terminal 60 may also obtain information to be displayed on the menu screen (for example, the number of points) from the cloud server 20 and display it on the menu screen.

[0089] Figure 12 is a sequence diagram showing an example of processing by the mobile terminal 60 and the cloud server 20. Specifically, Figure 12 shows an example of processing by the mobile terminal 60 and the cloud server 20 from the time the mobile terminal 60 launches a specific application until the menu screen is displayed. It is assumed that this is not the first time the specific application has been launched on the mobile terminal 60 (it is the second or subsequent launch). In other words, at the start of the flowchart in Figure 12, the member history information (Figure 3(B)) stored in the cloud server 20 is assumed to contain a value other than "0 (times)" as the number of times the application has been launched, corresponding to the member identification information of the member using the mobile terminal 60.

[0090] Step S21: The mobile terminal 60 launches a specific application based on the member's operation, similar to step S1 in Figure 11. Step S22: The mobile terminal 60 sends application launch information, similar to step S2 in Figure 11.

[0091] Step S23: The cloud server 20 receives application launch information, similar to step S3 in Figure 11. Step S24: The cloud server 20 determines that this is not the first time the specific application has been launched. Specifically, the cloud server 20 refers to the number of times the application has been launched corresponding to the member identification information included in the application launch information. Since the number of times the application has been launched is not "0", the cloud server 20 determines that this is not the first time the specific application has been launched.

[0092] Step S31: The cloud server 20 sends a message instructing it to display the menu screen. In other words, if the cloud server 20 determines that this is not the first time the specific application has been launched (i.e., it determines that this is the second or subsequent launch), it sends a message instructing it to display the menu screen. If the cloud server 20 determines that this is the first time the specific application has been launched (i.e., it determines that this is the initial launch), it sends a message instructing it to display the tutorial screen (Step S5 in Figure 11). The cloud server 20 also sends a message instructing it to display the menu screen when it receives a service start instruction (Step S11 in Figure 11). Step S32: The cloud server 20 updates the app launch count. Specifically, the cloud server 20 adds 1 to the app launch count corresponding to the member identification information. The cloud server 20 also stores the current date and time as the date and time of the last app launch corresponding to the member identification information.

[0093] Step S33: The mobile terminal 60 receives display instruction information for the menu screen, similar to step S13 in Figure 11. Step S34: The mobile terminal 60 displays the menu screen, similar to step S14 in Figure 11 (Figure 6(D)). Thus, if it is the second or subsequent launch of a particular application, the mobile terminal 60 displays the menu screen without displaying the tutorial screen.

[0094] Figure 13 is a sequence diagram showing an example of processing by the mobile terminal 60 and the cloud server 20. Specifically, Figure 13 shows an example of processing by the mobile terminal 60 and the cloud server 20, following the process in Figure 11 or Figure 12, from when the mobile terminal 60 receives the operation to start shopping until the initial registration screen is displayed. At the start of the flowchart in Figure 13, the mobile terminal 60 is assumed to be displaying the menu screen.

[0095] Step S40: The mobile terminal 60 accepts the operation to start shopping. For example, the mobile terminal 60 accepts the operation of the start shopping button BT610 on the menu screen shown in Figure 6(D). Step S41: The mobile terminal 60 transmits shopping start instruction information to notify (report) that an operation to start shopping has been performed. The shopping start instruction information includes member identification information.

[0096] Step S42: The cloud server 20 receives the shopping start instruction information. Step S43: The cloud server 20 generates (assigns) transaction identification information. The cloud server 20 also generates transaction information for the transaction (the registration information ("product 1," etc.) is empty).

[0097] Step S44: The cloud server 20 determines that product item 1 has not yet been registered. For example, the cloud server 20 determines that product item 1 has not yet been registered because the transaction information for that transaction does not contain "Registration Information (Product 1)". Step S45: The cloud server 20 transmits the display instruction information for the initial registration screen and the transaction identification information to identify the transaction. In other words, if the cloud server 20 determines that a product item has not yet been registered, it transmits the display instruction information for the initial registration screen and the transaction identification information to identify the transaction. If the cloud server 20 determines that a product item has already been registered, it transmits the display instruction information for the registration screen (not the initial registration screen) (steps S53 and S63 in Figure 14).

[0098] Step S46: The mobile terminal 60 receives the display instruction information for the initial registration screen and the transaction identification information. Step S47: The mobile terminal 60 stores the transaction identification information. The mobile terminal 60 may erase the transaction identification information when the transaction is completed (when settlement is completed in the settlement device 50). Step S48: The mobile terminal 60 displays the initial registration screen instead of the menu screen. The mobile terminal 60 also displays the product scan guide image GA624 in front of the initial registration screen. In other words, the mobile terminal 60 displays the initial registration screen based on the instructions from the cloud server 20 (information on the display of the initial registration screen) and displays the product scan guide image GA624 in front of the initial registration screen (Figures 7(A) to 7(C)). The mobile terminal 60 may store the product scan guide image GA624 as part of a specific application or as information attached to a specific application and display it in front of the initial registration screen. Alternatively, the mobile terminal 60 may obtain the product scan guide image GA624 from the cloud server 20 and display it in front of the initial registration screen.

[0099] Figure 14 is a sequence diagram showing an example of processing by the mobile terminal 60 and the cloud server 20. Specifically, Figure 14 shows an example of processing that follows Figure 13, from when the mobile terminal 60 reads the barcode attached to one product item until the operation to proceed to checkout is performed. At the start of the flowchart in Figure 14, the mobile terminal 60 is assumed to be displaying the initial registration screen.

[0100] Step S50: The mobile terminal 60 reads the barcode attached to one of the products. Specifically, as shown in Figure 7(D), the mobile terminal 60 reads the barcode by taking an image of the barcode attached to the product. The mobile terminal 60 obtains the product code of the product from the barcode. Step S51: The mobile terminal 60 transmits the transaction identification information for the transaction and the product code for the product.

[0101] Step S52: The cloud server 20 receives the transaction identification information and product code. Step S53: The cloud server 20 updates the transaction information for the transaction. Specifically, the cloud server 20 identifies the product based on the received product code and stores the product information for that product in "Registered Information (Product 1)". The cloud server 20 also stores the product information (price) for that product in "Registered Information (Total)". Step S54: The cloud server 20 determines that product 1 is already registered. For example, the cloud server 20 determines that product 1 is already registered because the transaction information for that transaction contains "Registration Information (Product 1)". Step S55: The cloud server 20 sends display instruction information for the registration screen (not the initial registration screen). In other words, if the cloud server 20 determines that one product item has already been registered, it sends display instruction information for the registration screen (not the initial registration screen).

[0102] Step S56: The mobile terminal 60 receives instructions to display a registration screen (not the initial registration screen). Step S57: The mobile terminal 60 displays the registration screen (updates the displayed content). In other words, the mobile terminal 60 displays the registration screen based on the instructions from the cloud server 20 (information on the display of the registration screen) (Figures 8(A) to 8(C)). As shown in Figures 8(A) to 8(C), the mobile terminal 60 does not display (clears) the product scan guide image GA624 on the registration screen. The mobile terminal 60 obtains the information to be displayed on the registration screen (for example, product name, price) from the cloud server 20 and displays it on the registration screen.

[0103] Furthermore, after step S57 (and step S67 described later), it is also possible to read the barcodes attached to the second and subsequent items (the second item, the third item, etc.) (step S60), and it is also possible to accept the operation to proceed to checkout (operation of the button BT626 to proceed to checkout) (step S68).

[0104] Step S60: The mobile terminal 60 reads the barcodes attached to the second and subsequent items. Specifically, as shown in Figure 8(D), the mobile terminal 60 reads the barcodes by imaging the barcodes attached to the items. The mobile terminal 60 obtains the product code of the item from the barcode. Step S61: The mobile terminal 60 transmits the transaction identification information for the transaction and the product code for the product, similar to step S51.

[0105] Step S62: The cloud server 20 receives transaction identification information and product code, similar to step S52. Step S63: The cloud server 20 updates the transaction information for the transaction. Specifically, the cloud server 20 identifies the product based on the received product code and stores the product information for that product in "Registered Information (Product N (where N is N items))". The cloud server 20 also adds the product information (price) for that product to "Registered Information (Total)". Step S64: Cloud server 20 determines, as in step S54, that product item 1 is already registered. Step S65: The cloud server 20 sends display instruction information for the registration screen (not the initial registration screen), similar to step S55.

[0106] Step S66: The mobile terminal 60 receives instructions to display a registration screen (not the initial registration screen), similar to step S56. Step S67: The mobile terminal 60 displays the registration screen (updates the displayed content) as in step S57. In other words, the product scan guide image GA624 is not displayed (remains hidden).

[0107] Step S68: The mobile terminal 60 accepts the operation to proceed to checkout. Specifically, the mobile terminal 60 accepts the operation of the button BT626 to proceed to checkout.

[0108] Figure 15 is a sequence diagram showing an example of processing by the mobile terminal 60 and the cloud server 20. Specifically, Figure 15 shows an example of processing by the mobile terminal 60 and the cloud server 20, following the process in Figure 14, from when the mobile terminal 60 receives an operation to proceed to checkout until the 2D code display screen for settlement is displayed. At the start of the flowchart in Figure 15, it is assumed that the mobile terminal 60 has received an operation to proceed to checkout (operation of the "Proceed to Checkout" button BT626).

[0109] Step S69: The mobile terminal 60 transmits accounting instruction information to notify (report) that an operation has been performed to instruct the user to proceed to accounting. The accounting instruction information includes transaction identification information.

[0110] Step S70: The cloud server 20 receives accounting instruction information. Step S71: The cloud server 20 generates a two-dimensional code GA631 for settlement. Step S72: The cloud server 20 transmits display instruction information for the settlement 2D code display screen.

[0111] Step S73: The mobile terminal 60 receives display instruction information for the payment 2D code display screen. Step S74: The mobile terminal 60 displays a payment QR code display screen instead of the registration screen (clearing the registration screen). In other words, the mobile terminal 60 displays the payment QR code display screen based on instructions from the cloud server 20 (display instruction information for the payment QR code display screen) (Figures 9(D) to 10(B)). The mobile terminal 60 obtains the information to be displayed on the payment QR code display screen (for example, the payment QR code GA631) from the cloud server 20 and displays it on the payment QR code display screen.

[0112] Figure 16 is a sequence diagram showing an example of processing by the payment device 50, the cloud server 20, and the mobile terminal 60. Specifically, Figure 16 shows an example of processing by the payment device 50, the cloud server 20, and the mobile terminal 60 from the time the payment device 50 reads the payment 2D code GA631 until it displays the product list screen (until the mobile terminal 60 displays the payment 2D code reading completion screen). The left side of Figure 16 shows the processing of the payment device 50, the center shows the processing of the cloud server 20, and the right side shows the processing of the mobile terminal 60.

[0113] Step S80: The settlement device 50 reads the settlement 2D code GA631 displayed on the settlement 2D code display screen of the mobile terminal 60. The settlement device 50 obtains transaction identification information from the settlement 2D code GA631 to identify the transaction information of the transaction. Step S81: The settlement device 50 transmits transaction information request information requesting transaction information for the transaction in question. The transaction information request information includes transaction identification information that identifies the transaction in question. Step S82: The cloud server 20 receives transaction information request information.

[0114] Step S83: The cloud server 20 transmits the transaction information for the transaction. Step S84: The settlement device 50 receives and stores the transaction information for the transaction. Step S85: The settlement device 50 displays a product list screen based on the transaction information (Figure 10(D)).

[0115] Step S86: The cloud server 20 sends instructions to display the payment 2D code reading completion screen.

[0116] Step S87: The mobile terminal 60 receives instructions to display the payment 2D code reading completion screen. Step S88: The mobile terminal 60 displays a payment 2D code reading completion screen instead of the payment 2D code display screen (clearing the payment 2D code display screen). In other words, the mobile terminal 60 displays the payment 2D code reading completion screen based on the instructions from the cloud server 20 (information instructing the display of the payment 2D code reading completion screen) (Figure 10(C)).

[0117] As described above, the embodiment allows even beginners to use the device easily. For example, guidance images (tutorial image GA601, product scan guide image GA624, payment 2D code scan guide image GA633) are displayed as guidance (guide information) to guide the user through the procedures (operations, movements) of the mobile terminal 60, so even beginners can easily operate the mobile terminal 60. Image GA627 may also be one of the images that guide the user through the procedures.

[0118] In the above embodiment, guidance on how to register a product (product scan guide image GA624) is displayed at the time the product is actually registered (Figure 7). Because the guidance on how to register a product is displayed at the time the product is actually registered, customers can learn how to register a product more efficiently than if it were displayed in a situation other than the actual product registration (for example, the tutorial screen shown in Figures 6(A) to 6(C) or the menu screen shown in Figure 6(D)). In other words, because the guidance is provided at the appropriate time rather than being provided (presented) in advance, customers can efficiently learn how to register a product by practicing (registering a product) while looking at the guidance. Also, because the necessary information is presented at a good pace, it is less stressful for the customer. In this respect, if the guidance were provided in advance, the customer would have to remember the content of the guidance provided in advance until the time they needed it, or they would have to switch pages or perform other operations to check the content of the guidance provided in advance when the time came, which would be stressful for the customer.

[0119] Furthermore, in the above embodiment, the area for displaying the captured image (captured image display area HR621) and the area for displaying the product registration information (registration information display area HR622) are provided on the same screen (Figures 7 to 9). This allows customers to register products comfortably (realizing a comfortable shopping experience for customers). In this respect, if the area for displaying the captured image and the area for displaying the product registration information were not provided on the same screen, but rather the area for displaying the captured image was provided on one screen and the area for displaying the product registration information was provided on another screen, then each time a product is registered, a screen transition would occur, either automatically or based on the customer's will (instruction). Whether the screen transition occurs automatically each time a product is registered or based on the customer's will, the screen transition is likely to cause visual fatigue to the customer. Moreover, if the screen transition occurs based on the customer's will, the customer will also need to operate buttons or other controls, which is burdensome or at least inconvenient. In any case, it will hinder a comfortable shopping experience to some extent. On the other hand, in this embodiment, since the area for displaying the captured image and the area for displaying the product registration information are provided on the same screen, the above-mentioned problems do not occur, and a comfortable shopping experience can be realized.

[0120] From the perspective of creating a comfortable shopping experience, it is necessary to be mindful of information overload, which can lead to difficulty in viewing and information overload. Providing all the guidance needed for each stage of a series of steps in one stage simultaneously would result in information overload. Therefore, in the above embodiment, the guidance needed for each stage is provided at each stage. The timing of removing (or hiding) guidance that is no longer needed is also important. In the above embodiment, the product scan guide image GA624 is removed immediately after the product is scanned (Figure 7(D) → Figure 8(A)), or the product scan guide image GA624 is hidden from the second item onwards (Figure 8(C)).

[0121] (Variations, etc.) Although embodiments have been described above, the configuration of the equipment, the data configuration, the processing flow, the display and output methods, etc., can be changed as appropriate, for example, as shown in (1), (2), ... below. Furthermore, (1), (2), ... below can be combined in any way as appropriate.

[0122] (1) In the above embodiment, an example was described in which the tutorial screen (tutorial image GA601) is advanced based on an operation (operation of the next button BT603), but the tutorial screen may be advanced based on other conditions. For example, the tutorial screen may be advanced based on the passage of time, similar to the product scan guide image GA624 and the settlement 2D code scan guide image GA633.

[0123] (2) In the above embodiment, an example was described in which the presence or absence (or necessity) of displaying a tutorial screen (tutorial image GA601, etc.) is determined based on whether or not it is the first time the specific application is launched. However, the number of times the presence or absence of the tutorial screen is determined is not limited to the first time. For example, the tutorial screen may be displayed up to the third launch, and then not displayed from the fourth launch onwards.

[0124] (3) In the above embodiment, an example was described in which three types of tutorial images GA601 (images GA601a, GA601b, and GA601c) were displayed on the tutorial screen, but there are no more than three types of tutorial images GA601. In other words, one type of tutorial image GA601 may always be displayed on the tutorial screen, or two or four or more types of tutorial images GA601 may be displayed sequentially on the tutorial screen.

[0125] (4) In the above embodiment, the amount of information provided (guided) when displaying the tutorial screen is constant, but the amount of information provided may vary depending on the tutorial screen. For example, related to (2) and (3) above, depending on the conditions (how many times it has been launched, member attributes, purchase history, etc.), the service may be explained at a normal level using a normal number (e.g., 3 types) of tutorial images GA601, the service may be explained at a more detailed level than the normal level using a large number (e.g., 5 types) of tutorial images GA601, or the service may be explained at a more concise level than the normal level using a small number (e.g., 1 type) of tutorial images GA601.

[0126] (5) In the above embodiment, an example was described in which the launch of a specific application is determined based on the time when the specific application was installed (downloaded, etc.) in relation to whether or not the tutorial screen is displayed. However, the launch of the current specific application may be determined based on other points in time. For example, instead of or in addition to the time when the specific application was installed, if a predetermined period (e.g., 3 months) has passed since the previous launch without the application being launched, the launch of the current specific application may be determined based on the time when that predetermined period has elapsed. In other words, if the specific application has been launched in the past but has not been launched for some time (i.e., it has been a long time since the last launch), the tutorial screen (tutorial image GA601, etc.) may be displayed. The same applies when determining whether it is the second or subsequent launch, not just the first launch. Also, for example, instead of or in addition to the time when the specific application was installed or the time when the predetermined period has elapsed, if the specific application has been updated (e.g., a function has been added, the UI has been changed), the launch of the current specific application may be determined based on the time when that update was performed.

[0127] (6) In the above embodiment, an example was described in which the display of a tutorial screen is determined based on the launch history of a specific application (specifically, the number of past launches). However, conditions may be set for the launch history of a specific application. For example, conditions may be set regarding the launch time of a specific application. For example, if a specific application is launched at a predetermined time (for example, during the store's business hours), that launch may be counted as a launch, but if the specific application is launched at a time other than the predetermined time, that launch may not be counted as a launch. Also, for example, conditions may be set regarding the launch location of a specific application. For example, if a specific application is launched at a predetermined location (for example, inside the store or on the store's premises), that launch may be counted as a launch, but if the specific application is launched at a location other than the predetermined location, that launch may not be counted as a launch. The launch location may be determined by GPS. Also, if the mobile terminal 60 is connected to the store's wireless LAN, it may be determined that the mobile terminal 60 is at the predetermined location. Furthermore, launches may be counted as launches only if the specific application is launched at the predetermined time and location.

[0128] (7) In the above embodiment, an example was described in which the presence or absence of the tutorial screen is determined based on the launch history of a specific application (specifically, the number of past launches), but the presence or absence of the tutorial screen may also be determined based on other conditions. For example, the presence or absence of the tutorial screen may be determined as shown in (a) to (c) below. (a) The decision of whether or not to display the tutorial screen is made based on the display history of the tutorial screen (for example, the number of times the first image GA601a has been displayed in the past, and the number of times the last image GA601b has been displayed in the past). (b) The decision on whether or not to display the tutorial screen is based on the barcode reading history (number of readings) of the product, or the product registration history (number of registered products). (c) The system determines whether or not to display the tutorial screen based on the transaction completion record of Service A (for example, the number of settlements completed at settlement device 50).

[0129] (8) In the above embodiment, the screens that the mobile terminal 60 displays on the display unit 305 were described as a tutorial screen (Figures 6(A) to 6(C)), a menu screen (Figure 6(D)), an initial registration screen (Figures 7(A) to 7(D)), a registration screen (Figures 8(A) to 9(C)), a payment 2D code display screen (Figures 9(D), 10(A), 10(B)), and a payment 2D code reading completion screen (Figure 10(C)). However, the screens that the mobile terminal 60 displays are not limited to the above screens.

[0130] (Transaction completion screen) The mobile terminal 60 may display a transaction completion screen (not shown) that notifies the user that the transaction has been completed. For example, when the settlement device 50 completes the settlement process (for example, when the receipt printed and issued by the printing unit 113 is removed), it sends information to the cloud server 20 indicating that the settlement process has been completed. When the cloud server 20 receives this information from the settlement device 50, it sends instructions to the mobile terminal 60 to display the transaction completion screen. When the mobile terminal 60 receives these instructions from the cloud server 20, it may display the transaction completion screen. The mobile terminal 60 may also display images (animations, slides) on the transaction completion screen (and the status confirmation screen) as it does on other screens.

[0131] In configurations where a transaction completion screen is not displayed (i.e., the final display in a transaction is the settlement 2D code reading completion screen), the mobile terminal 60 may display on the settlement 2D code reading completion screen that the operation by the mobile terminal 60 is complete or that the role of the mobile terminal 60 in the transaction is complete. For example, the mobile terminal 60 may display a message on the settlement 2D code reading completion screen such as, "Thank you. The operation on the mobile terminal 60 is complete, so you can put it away. Subsequent transactions will be handled by the settlement device. Please proceed with settlement processing on the settlement device." The mobile terminal 60 may also transition from the settlement 2D code reading completion screen to a menu screen. For example, the mobile terminal 60 may display a message such as "The operation on the mobile terminal 60 is complete. Returning to the menu screen. Subsequent transactions will be handled by the settlement device. Please proceed with settlement processing at the settlement device." on the settlement 2D code reading completion screen instead of the message described above, and automatically transition from the settlement 2D code reading completion screen to the menu screen after a predetermined time has elapsed. Alternatively, for example, the settlement 2D code reading completion screen may display a message such as "The operation on the mobile terminal 60 is complete. Do you want to return to the menu screen?" on the settlement 2D code reading completion screen instead of the message described above, and provide a button to confirm whether to return to the menu screen. If the user presses the return button, the system may transition from the settlement 2D code reading completion screen to the menu screen.

[0132] In the configuration where the transaction completion screen is displayed (i.e., the final display in a transaction is the transaction completion screen), the mobile terminal 60 may display on the settlement 2D code reading completion screen that the operation by the mobile terminal 60 is complete and that it will notify the user of the transaction completion separately after the transaction is completed, and on the transaction completion screen, it may display that the mobile terminal 60's role in the transaction is complete, including confirmation of the transaction completion (settlement completion). For example, the mobile terminal 60 may display a message such as "Thank you. The operation on the mobile terminal 60 is complete. Subsequent transactions will be handled by the settlement device. Please proceed with settlement processing at the settlement device. A message will be displayed after the transaction is completed." on the settlement 2D code reading completion screen, and a message such as "The transaction is complete, so you can put it away." on the transaction completion screen. The mobile terminal 60 may also transition from the transaction completion screen to a menu screen. For example, the mobile terminal 60 may display a message such as "Transaction completed. Returning to the menu screen." on the transaction completion screen instead of the message described above, and automatically transition from the transaction completion screen to the menu screen after a predetermined time has elapsed. Alternatively, for example, the transaction completion screen may display a message such as "Transaction completed. Do you want to return to the menu screen?" on the transaction completion screen instead of the message described above, and provide a button to confirm whether or not to return to the menu screen. If the user presses the button to return, the terminal may transition from the transaction completion screen to the menu screen.

[0133] The mobile terminal 60 may display a message indicating that settlement is in progress at the settlement device 50 (for example, a message such as "Settlement in progress at the settlement device"). For example, from the time the mobile terminal 60 receives the instruction to display the settlement 2D code reading completion screen (Figure 16) until it receives the instruction to display the transaction completion screen, it may display a message indicating that settlement is in progress at the settlement device 50 on the settlement 2D code reading completion screen.

[0134] Instead of the mobile terminal 60 displaying that payment is in progress at the payment device 50, or in addition to that, the payment device 50 itself may display that payment is in progress. For example, the payment device 50 may, upon reading the payment 2D code GA631, display a message (which may be an animation or slide) such as, "We will now begin processing your payment. You may put away your mobile terminal." This provides the customer with an opportunity to put away their mobile terminal 60.

[0135] Furthermore, the settlement device 50 may display a message indicating that settlement has been completed. For example, the settlement device 50 may display a message (which may be an animation or slide) such as "Settlement processing is complete" based on the condition that change or receipts are removed (detection of removal of change, detection of removal of receipts, etc.). In the configuration in which the mobile terminal 60 displays a transaction completion screen, the settlement device 50 may display a message (which may be an animation or slide) such as "Settlement processing is complete. Transaction completion will also be notified to the mobile terminal 60."

[0136] Furthermore, if the mobile terminal 60 is not owned by the customer (customer mobile terminal) but is a loaned item provided by the store to the customer (store mobile terminal, loaned mobile terminal), or if it is a shopping cart such as a charging cart (described later), the payment device 50 may display information regarding return or charging. For example, if it is a loaned mobile terminal 60, the payment device 50 may display a message (which may be an animation or slide) such as, "Please return the loaned terminal to the charging station. Please check the screen of the loaned terminal for return instructions (charging instructions)." Also, if it is a charging cart (described later), the payment device 50 may display a message (which may be an animation or slide) such as, "Please return the cart to the designated location. Please check the screen of the cart for return instructions (charging instructions)."

[0137] In other words, the payment device 50 can use different messages depending on whether the mobile terminal 60 is a customer mobile terminal or a store mobile terminal. Furthermore, by storing information that identifies the store mobile terminal (for example, a unique subscriber ID or MAC address) in a location accessible to the payment device 50 (which may be within its own device or in another device), the payment device 50 may determine whether the mobile terminal 60 being used (used for product registration) is a customer mobile terminal or a store mobile terminal.

[0138] As described above, since necessary messages (guidance) are displayed on both the mobile terminal 60 and the payment device 50, customers can concentrate on operating one device (terminal) at a time. In other words, customers no longer need to pay attention to both devices (terminals), reducing their burden. Consequently, this leads to shorter processing times (such as payment times) and enables more efficient operation for the store.

[0139] (Status confirmation screen) The mobile terminal 60 may display a status confirmation screen (not shown) to check the status. As explained earlier, the mobile terminal 60 may be equipped with a motion detection unit, but for example, the mobile terminal 60 may display the status confirmation screen if there is no movement and no operation for a predetermined period of time. The status confirmation screen may display a message prompting action (for example, registering a product, interrupting a transaction, etc.).

[0140] (9) In the above embodiment, the language of the tutorial screen (message MS602, etc.) is Japanese, but it may be displayed in a foreign language. For example, it may be possible to specify (set) the language when downloading (or installing) a specific application or after downloading (or installing) it, and the tutorial screen may be displayed in the specified language. The same applies to the language of the menu screen, registration screen (including the initial registration screen and product scan guide image GA624), settlement 2D code display screen, settlement 2D code reading completion screen, transaction completion screen, and status confirmation screen.

[0141] (10) In the above embodiment, an example was described in which the initial registration screen (product scan guide image GA624) is advanced based on the passage of time, but the initial registration screen may be advanced based on other conditions. For example, the initial registration screen may be advanced based on operations, similar to the tutorial screen (tutorial image GA601).

[0142] (11) In the above embodiment, an example was described in which three types (image GA624a, image GA624b, and image GA624c) of product scan guide images GA624 are displayed on the initial registration screen. However, there are no more than three types of product scan guide images GA624. In other words, one type of product scan guide image GA624 may always be displayed on the initial registration screen, or two or four or more types of product scan guide images GA624 may be displayed sequentially on the initial registration screen.

[0143] (12) In the above embodiment, an example was described in which the product scan guide image GA624 is displayed on the initial registration screen, but not on registration screens other than the initial registration screen. In other words, in the above embodiment, an example was described in which the presence or absence (necessity) of displaying the product scan guide image GA624 is determined based on whether or not it is the first scan (of an item) in the transaction. However, the number of times the presence or absence of displaying the product scan guide image GA624 is determined is not limited to the first scan (of an item). For example, the product scan guide image GA624 may be displayed up to the third scan (of an item), and then not displayed from the fourth scan (of an item) onward.

[0144] (13) In the above embodiment, an example was described in which the product scan guide image GA624 is displayed on the initial registration screen. In other words, in the above embodiment, an example was described in which the product scan guide image GA624 is always displayed when it is the first time (item) in the transaction. However, there may be cases in which the product scan guide image GA624 is not displayed when it is the first time (item) in the transaction. For example, the presence or absence of the product scan guide image GA624 may be determined as shown in (a) to (c) below. (a) The display of the product scan guide image GA624 will be determined based on whether this transaction is the first time the specific application has been launched. In other words, it will only be displayed on the first launch. (b) The display of the product scan guide image GA624 is determined based on the barcode reading record (number of readings) or the product registration record (number of registered products). In other words, it is displayed only if the record falls below a predetermined number of readings (number of products). (c) The display of the product scan guide image GA624 is determined based on the transaction completion record of Service A (for example, the number of settlements completed at the settlement device 50). In other words, it is displayed only if the record is less than a predetermined number.

[0145] (14) In the above embodiment, an example was described in which the product scan guide image GA624 is displayed on the initial registration screen in a position that spans the captured image display area HR621 and the registration information display area HR622 (in front of the captured image display area HR621 and the registration information display area HR622). Specifically, an example was described in which the product scan guide image GA624 is displayed such that the upper part of the product scan guide image GA624 is located in front of the area of ​​the captured image display area HR621 below the barcode reading area, and the remaining part of the product scan guide image GA624 is located in front of the area of ​​the registration information display area HR622 excluding the lower area (Figures 7(A) to 7(C)). However, the display manner of the product scan guide image GA624 is not limited to this. For example, the product scan guide image GA624 may be displayed as shown in (a) and (b) below. (a) The entire product scan guide image GA624 is displayed in front of the captured image display area HR621 (i.e., the product scan guide image GA624 is not displayed in front of the registration information display area HR622). For example, by making the product scan guide image GA624 smaller than in the example shown in Figure 7(A), the entire product scan guide image GA624 is displayed in front of the captured image display area HR621 (the area excluding the barcode reading area (for example, the area below the barcode reading area)). The position of the barcode reading area in the captured image display area HR621 may be higher than in the example shown in Figure 7(A). The captured image display area HR621 may also be made wider than in the example shown in Figure 7(A) (the registration information display area HR622 may be made narrower). (b) Display the product scan guide image GA624 in front of the captured image display area HR621, the registered information display area HR622, and the related information display area HR633 (that is, display a portion of the product scan guide image GA624 in front of the related information display area HR633). For example, by making the product scan guide image GA624 larger than in the example shown in Figure 7(A), etc., or by making the related information display area HR633 wider than in the example shown in Figure 7(A), etc., the product scan guide image GA624 is displayed in front of the captured image display area HR621, the registered information display area HR622, and the related information display area HR633.

[0146] (15) In the above embodiment, an example was described in which the registration screen (including the initial registration screen) is configured to include an image capture display area HR621, a registration information display area HR622, and a related information display area HR633. However, the configuration of the registration screen (including the initial registration screen) is not limited to this. For example, the registration screen (including the initial registration screen) may be configured as shown in (a) and (b) below. (a) The registration screen is provided with an image display area HR621 and a registration information display area HR622 (the related information display area HR633 is not provided). In this configuration, buttons may be placed on the registration screen, and information that would be displayed in the related information display area HR633 based on the operation of these buttons may be displayed on a separate screen (or a small screen on the registration screen). (b) The registration screen is provided with only the captured image display area HR621 (the registration information display area HR622 and the related information display area HR633 are not provided). In this configuration, when a barcode is read, registration information similar to that displayed in the registration information display area HR622 may be displayed on a separate screen. The screen provided with only the captured image display area HR621 may be called the first registration screen, and the separate screen (the screen that displays registration information similar to that displayed in the registration information display area HR622) may be called the second registration screen. For example, the mobile terminal 60 may switch from the first registration screen to the second registration screen in response to barcode reading, and switch from the second registration screen to the first registration screen in response to operation. The mobile terminal 60 may also switch from the first registration screen to the second registration screen in response to operation, either in lieu of or in addition to barcode reading.

[0147] (16) In the above embodiment, an example was described in which the registration screen (including the initial registration screen) is configured to include an image capture display area HR621, a registration information display area HR622, and a related information display area HR633. However, the entire display area of ​​the registration screen (including the initial registration screen) may be referred to as the imaging area. In other words, if the through image captured by the imaging unit 316 is displayed in at least a part of the display area of ​​the display unit 305 (the image capture display area HR621 in the above embodiment), the entire display area of ​​the display unit 305 (the image capture display area HR621, the registration information display area HR622, and the related information display area HR633 in the above embodiment) may be referred to as the imaging area. In other words, in this embodiment, the lower part of the registration screen may be considered as a state in which the through image on the back is hidden by the front registration information display area HR622 and the related information display area HR633.

[0148] (17) In the above embodiment, an example was described in which the settlement 2D code display screen (settlement 2D code scan guide image GA633) is advanced based on the passage of time, but the initial registration screen may be advanced based on other conditions. For example, the settlement 2D code display screen may be advanced based on operations, similar to the tutorial screen (tutorial image GA601).

[0149] (18) In the above embodiment, an example was described in which three types (image GA633a, image GA633b, image GA633c) of product scan guide images GA624 are displayed on the settlement 2D code display screen. However, there are no more than three types of settlement 2D code scan guide images GA633. In other words, one type of settlement 2D code scan guide image GA633 may always be displayed on the settlement 2D code display screen, or two or four or more types of settlement 2D code scan guide images GA633 may be displayed sequentially on the settlement 2D code display screen.

[0150] (19) In the above embodiment, an example was described in which the two-dimensional code GA631 for settlement is displayed below the message MS632 on the settlement two-dimensional code display screen. However, the two-dimensional code GA631 for settlement may also be displayed above the message MS632. In other words, if the two-dimensional code scan guide image GA633 for settlement, which occupies a relatively large area on the settlement two-dimensional code display screen, is displayed below (towards the wrist, towards the hand) the two-dimensional code GA631 for settlement, the member can easily have the settlement device 50 read the two-dimensional code GA631.

[0151] (20) Related to (19) above, in the case of a mobile terminal 60 in which the display unit 305 is elongated (aspect ratio (vertical:horizontal) is, for example, 21:9), even if the payment 2D code scan guide image GA633 is displayed below the payment 2D code GA631, the distance between the top edge of the payment 2D code display screen and the top edge of the payment 2D code GA631 may be long. Therefore, in the case of a mobile terminal 60 in which the display unit 305 is elongated, the payment 2D code GA631 may be positioned so as to be closer to the top edge of the payment 2D code display screen, thereby shortening the above distance. In other words, regardless of the model (type) of the mobile terminal 60, the layout of the payment 2D code display screen may be changed according to the type of mobile terminal 60 so that members can have the payment device 50 read the payment 2D code GA631 without difficulty. Specifically, the longer and narrower the mobile terminal 60, the more likely it is that the position of the payment 2D code scan guide image GA633 on the payment 2D code display screen will be shifted towards the top.

[0152] (21) In the above embodiment, it was explained that the mobile terminal 60 may be equipped with a motion detection unit. However, when the payment 2D code display screen is displayed, the rotation of the payment 2D code display screen (change between portrait and landscape orientation) by an acceleration sensor (gyro sensor) may be prohibited (i.e., it may always be displayed in portrait orientation as shown in Figure 9(D), etc., regardless of movement). This prevents the payment 2D code display screen from rotating unnecessarily, allowing the member to have the payment device 50 read the payment 2D code GA631 without difficulty. Note that the rotation control of the screen (not limited to the payment 2D code display screen; the entire screen) by the acceleration sensor may be prohibited on the condition that the application (specific application) is launched.

[0153] (22) Although not shown in the above embodiment, information related to settlement (such as the total amount) may be displayed on the settlement 2D code display screen. For example, the mobile terminal 60 may display the estimated total "2 items ¥370" on the settlement 2D code display screen shown in Figures 9(D) to 10(B). The total amount, etc., may be displayed below the settlement 2D code GA631 (between the settlement 2D code GA631 and the settlement 2D code scan guide image GA633, or between the settlement 2D code scan guide image GA633 and the "return to shopping" button BT639) on the settlement 2D code display screen.

[0154] (23) Although not shown in the above embodiment, a staff call button may be displayed on the payment 2D code display screen. The staff call button may be displayed, for example, below the payment 2D code GA631 (for example, between the payment 2D code scan guide image GA633 and the return to shopping button BT639, below the return to shopping button BT639). When the staff call button is pressed, the staff may be able to identify the mobile terminal 60 related to the staff call. For example, the mobile terminal 60 may transmit staff call information (including member identification information, etc.) based on the operation of the staff call button, and the staff call information may be received by the terminal carried by the staff or the transaction status management device 40 (for example, received via the cloud server 20 or the headquarters server 10) and the mobile terminal 60 related to the staff call may be identified (location information may be transmitted by the mobile terminal 60). The mobile terminal 60 may always display the staff call button on the payment 2D code display screen, or it may display the staff call button after a predetermined time (for example, 30 seconds) has elapsed since the start of the payment 2D code display screen (or after the operation of the "Proceed to Payment" button BT626 located on the registration screen) (it may be displayed in a manner that makes it inoperable before the predetermined time has elapsed and in a manner that makes it operable after the time has elapsed).

[0155] (24) In the above embodiment, an example was described in which the cloud server 20 generates the settlement 2D code GA631, but the mobile terminal 60 may also generate it. That is, when the mobile terminal 60 receives an operation to declare that it has finished registering products and will proceed to checkout (operation of the button BT626 to proceed to checkout on the registration screen), it may generate the settlement 2D code GA631 based on the transaction identification information. In addition, a device other than the cloud server 20 or the mobile terminal 60 may generate the settlement 2D code GA631 based on a request from the mobile terminal 60.

[0156] (25) In the above embodiment, an example was described in which the cloud server 20 determines whether or not it is the first time (1st time) that a particular application is launched, but the mobile terminal 60 may also make the determination. For example, when the mobile terminal 60 launches a particular application, it may query the cloud server 20 for the number of times the application has been launched (obtain the number of launches information) and determine whether or not this launch is the first launch. Alternatively, for example, the mobile terminal 60 itself may store (keep) the number of times the application has been launched, and when the particular application is launched, it may refer to the number of times the application has been launched that it has stored and determine whether or not this launch is the first launch.

[0157] (26) In the above embodiment, an example was described in which the mobile terminal 60 displays the tutorial screen based on instructions from the cloud server 20 (instruction information to display the tutorial screen). However, the mobile terminal 60 may also display the tutorial screen based on its own judgment (control). For example, as also related to (25) above, the mobile terminal 60 may determine whether this is the first time the application is launched when it is launched, and if it determines that it is the first time, it may display the tutorial screen.

[0158] (27) In the above embodiment, an example was described in which the mobile terminal 60 displays the menu screen based on instructions from the cloud server 20 (information instructing the display of the menu screen). However, the mobile terminal 60 may also display the menu screen based on its own judgment (control). For example, as also related to (25) and (26) above, the mobile terminal 60 may determine whether the current launch is the first launch when a particular application is launched, and if it determines that it is not the first launch, it may display the menu screen. Alternatively, for example, the mobile terminal 60 may determine whether it has received an operation to instruct the start of a service (operation of the service start button BT604 on the tutorial screen), and if it determines that it has received the operation, it may display the menu screen instead of the tutorial screen.

[0159] (28) In the above embodiment, an example was described in which the cloud server 20 determines whether or not product item 1 has already been registered, but the mobile terminal 60 may also make the determination. For example, the mobile terminal 60 may refer to the product information it stores (product information obtained from the cloud server 20 after reading the product) and determine whether or not product item 1 has already been registered.

[0160] (29) In the above embodiment, an example was described in which the decision to display the initial registration screen (product scan guide image GA624) is made based on whether or not a product item has already been registered. However, the decision may be made based on other conditions. For example, the decision may be made as shown in (a) and (b) below. (a) When the cloud server 20 receives a shopping start instruction (step S42 in Figure 13), it decides to display the initial registration screen (product scan guide image GA624). When the cloud server 20 receives a product code, etc. (steps S52, S62 in Figure 14), it decides not to display the initial registration screen (product scan guide image GA624) (it decides to simply display the registration screen). (b) When the mobile terminal 60 receives an operation to declare the start of shopping (operation of the start shopping button BT610 on the menu screen) (step S40 in Figure 13), it decides to display the initial registration screen (product scan guide image GA624). When the mobile terminal 60 reads a product code (steps S50, S60 in Figure 14), it decides not to display the initial registration screen (product scan guide image GA624) (it decides to simply display the registration screen). (a) above describes a mode in which the mobile terminal 60 displays the initial registration screen (product scan guide image GA624) and the registration screen based on instructions from the cloud server 20. (b) above describes a mode in which the mobile terminal 60 displays the initial registration screen (product scan guide image GA624) and the registration screen based on its own judgment.

[0161] (30) In the above embodiment, an example was described in which the mobile terminal 60 displays the payment 2D code display screen based on instructions from the cloud server 20 (display instruction information for the payment 2D code display screen). However, the mobile terminal 60 may also display the payment 2D code display screen based on its own judgment (control). For example, the mobile terminal 60 may determine whether or not to accept an operation to declare that it has finished registering products and will proceed to checkout (operation of the "Proceed to Checkout" button BT626 on the registration screen), and if it determines that the operation has been accepted, it may display the payment 2D code display screen instead of the registration screen.

[0162] (31) In the above embodiment, an example was described in which the mobile terminal 60 stores screen information and displays a screen based on the screen information it stores. However, the mobile terminal 60 does not need to store screen information. For example, the mobile terminal 60 may display various screens based on screen information generated (updated) by the cloud server 20 without storing screen information. As an example, the tutorial screen will be described. The process shown in steps S5 to S7 of Figure 11 may operate as follows: The cloud server 20 generates screen information for the tutorial screen and sends it to the mobile terminal 60. The mobile terminal 60 displays the tutorial screen based on the screen information received from the cloud server 20. As another example, the initial registration screen will be described. The process shown in steps S45 to S47 of Figure 13 may operate as follows: The cloud server 20 generates screen information for the initial registration screen (product information etc. is empty) and sends the generated image information to the mobile terminal 60 together with the product scan guide image GA624. The mobile terminal 60 displays the initial registration screen based on screen information received from the cloud server 20, and displays the product scan guide image GA624 in front of the initial registration screen. The tutorial screen, registration screen, and other screens may be provided by the cloud server 20 and may be web pages that the mobile terminal 60 browses. The format of images such as the product scan guide image GA624 is not restricted, but may be, for example, GIF (animated GIF). Image playback (display) may be after downloading or during download (streaming playback).

[0163] (32) In the above embodiment, an example was described in which the tutorial screen (tutorial image GA601) is erased when the menu screen is displayed (step S14 in Figure 11), the initial registration screen (product scan guide image GA624) is erased when the registration screen is displayed (step S57 in Figure 14), and the payment 2D code display screen (payment 2D code scan guide image GA633) is erased when the payment 2D code reading completion screen is displayed (step S88 in Figure 16). In other words, in the above embodiment, an example was described in which the guidance images (tutorial image GA601, product scan guide image GA624, payment 2D code scan guide image GA633) are erased from the screen when the need for guidance is eliminated or weakened. However, the example of erasing the guidance images is not limited to erasing the guidance images, as long as the guidance is effectively stopped. For example, instead of erasing the guidance images, the guidance images may be displayed in a smaller size (for example, as icons). Alternatively, instead of displaying the guidance image in a small size, or in addition to doing so, the guidance image may be displayed in an inconspicuous location.

[0164] (33) In the above embodiment, an example of using the mobile terminal 60 attached to a shopping cart was described, but it is not necessary to attach the mobile terminal 60 to a shopping cart. For example, the mobile terminal 60 may be used while being held in the hand. Note that some of the images (for example, image GA601b in Figure 6(B) and image GA624a in Figure 7(A)) are images that are appropriate for the use of the mobile terminal 60 attached to a shopping cart, so if the mobile terminal 60 is to be used while being held in the hand, use the image that is appropriate for the use while being held in the hand.

[0165] (34) In the above embodiment, the mobile terminal 60 was mainly described as being owned by the customer (customer mobile terminal), but as mentioned above, it may also be a loaned item provided by the store to the customer (store mobile terminal). By storing information that identifies the mobile terminal 60 provided by the store (store mobile terminal) (for example, a subscriber-specific ID or MAC address), it may be possible to distinguish whether the mobile terminal 60 being used or used is a store mobile terminal or not (i.e., whether it is a customer mobile terminal or a store mobile terminal). In the case of a store mobile terminal, the user may be prompted to enter a membership number to determine whether it is the first time it is activated or a subsequent activation.

[0166] (35) In the above embodiment, an example was described in which a customer registers products using a mobile terminal 60, but it does not have to be a mobile terminal 60 as long as it is a mobile (portable) device that can register products at the product display location. For example, products may be registered using a tablet terminal (owned or loaned) or a shopping cart equipped with a display unit (or a display unit that can be attached to or detached from a shopping cart). In other words, the shopping cart (a shopping cart equipped with a display unit, or a shopping cart with a display unit that can be attached to or detached from a shopping cart) may display a tutorial screen (Figures 6(A) to 6(C)), a menu screen (Figure 6(D)), an initial registration screen (Figures 7(A) to 7(D)), a registration screen (Figures 8(A) to 9(C)), a 2D code display screen for settlement (Figures 9(D), 10(A), 10(B)), a 2D code reading completion screen for settlement (Figure 10(C)), a transaction completion screen (not shown), and a status confirmation screen (not shown). The above-mentioned shopping cart (a shopping cart equipped with a display unit, or a shopping cart with a detachable display unit) may have the same configuration as the mobile terminal 60 (the configuration shown in Figure 4) (each component of the said configuration may be detachable).

[0167] The above-mentioned shopping cart (a shopping cart equipped with a display unit, or a shopping cart with a detachable display unit) may also be equipped with an electronic tag recognition unit that recognizes information from electronic tags (hereinafter referred to as an electronic tag recognition cart). Furthermore, the above-mentioned shopping cart (which may also be an electronic tag recognition cart) may be equipped with a battery (a battery that powers the display unit or display unit) and be rechargeable (hereinafter referred to as a rechargeable cart). Rechargeable carts are charged, for example, at a cart storage area (a place where at least one of the lending or return of shopping carts takes place). For example, a charging device (charging equipment) may be installed at the cart storage area, and rechargeable carts may be charged by the charging device. The charging method (system) may be contact (contact charging) or non-contact (non-contact charging). In the case of contact charging, for example, a cable or the like is connected to the rechargeable cart to perform the charging. The cart storage area shall be provided with the same number of cables, etc. as the number of rechargeable carts that can be stored (the maximum number of carts waiting before lending) (if storage locations are set, they shall be arranged in each storage location). In the case of contactless charging, for example, a contactless charging system (power supply (transmitting) unit, power receiving (receiving) unit) is installed on both the charging cart side and the cart storage area (charging equipment) side. Power is transmitted from the power supply unit on the cart storage area side and received by the power receiving unit on the charging cart side to perform charging. The cart storage area may be equipped with the same number of power supply units as the number of charging carts that can be stored, as in the case of contact charging, and arranged so that power supply and power receiving are in pairs, or a large power supply unit capable of transmitting power to multiple charging carts (power receiving units) at once may be installed. The retrieval and return of charging carts and the charging of charging carts (contact charging, contactless charging) at the cart storage area may be performed by store staff or by customers (at the request of the store). If charging is entrusted to the customer, store staff may periodically check the charging status (whether it is charging correctly, etc.).

[0168] In the case of shopping carts that do not have a battery (shopping carts that are not rechargeable; these may also be electronic tag recognition carts), charging of the display unit or indicator may be performed on the display unit or indicator. Unlike shopping carts equipped with detachable indicators, in the case of shopping carts equipped with non-detachable display units, if charging is performed on the display unit, it can be understood that charging is performed on a part of the shopping cart (the display unit), so shopping carts equipped with rechargeable display units may be called "rechargeable carts."

[0169] If the customer is responsible for returning the charging cart, the customer may be informed about the return process. For example, the charging cart (the charging cart's program) may display guidance (information) regarding the return on its display unit (or indicator) once the transaction information has been transferred to the payment device 50 (the payment device 50 has read the 2D code GA631 for payment) or once payment has been completed at the payment device 50. As an example, the charging cart may display guidance on returning the cart to the cart collection point on its display unit (or indicator) on the payment device 50 after the 2D code reading is complete (Figure 10(C)) or on the transaction completion screen (not shown). The guidance may include map information (floor information) indicating the return destination (cart collection point). The same applies to shopping carts that do not have batteries (they may also be electronic tag recognition carts).

[0170] If the charging of the charging cart is left to the customer, information regarding charging may be provided to the customer. For example, the charging cart (the charging cart's program) may display guidance (information) regarding charging on its display unit (or indicator) once transaction information has been transferred to the payment device 50 or payment has been completed at the payment device 50. As an example, the charging cart may display guidance on how to connect cables, etc., or guidance on how to perform contactless charging on its display unit (or indicator) on the payment 2D code reading completion screen or the transaction completion screen.

[0171] Guidance on how to connect cables, etc., may, for example, provide guidance on one or more of the following (a) to (c). (a) Available cables, etc. For example, the first (nearest) cable, etc. that is not currently in use among the multiple cables, etc. available at the cart storage area. (b) Method of connecting cables, etc. For example, regarding the port for cables, etc., for example, where the port is located on the charging cart, the direction in which to insert it, and the depth. (c) Confirmation that the cables, etc., are properly connected (that charging has started). For example, the cart device displays on the screen that it is supplying power. Alternatively, the cart device is equipped with a light-emitting unit (LED) that indicates that it is supplying power, and the light-emitting unit displays that it is supplying power. Furthermore, as also related to (c) above, the cart storage area may install LEDs corresponding to each cable, etc. (for example, one on each cable, etc.) to allow confirmation that power is being supplied.

[0172] Guidance on contactless charging methods may, for example, provide instructions for one or more of the following (a) to (c): (a) Available parking area. For example, the nearest unused parking area among the multiple parking areas (places where each charging cart can be charged wirelessly) set up at the cart collection point. (b) Stopping position. Stopping position (positioning) within the stopping area. (c) Confirm that the parking position is appropriate (that charging has started) (similar to the guidance on how to connect cables, etc.) Furthermore, in relation to (b) above, in the case of contactless power supply, since there is no physical connection, for example, a "△" illustration may be placed on the power supply unit, and a "▽" illustration corresponding to the "△" on the power supply unit may be placed on the power receiving unit, and the display unit (or indicator) may instruct the user to stop so that the vertices of the "▽" and "△" overlap. Since the actual illustrations are also displayed on the screen, the customer can intuitively understand the stopping position.

[0173] The same applies if the mobile terminal 60 is not owned by the customer (customer mobile terminal) but is a loaned item provided by the store to the customer (store mobile terminal, loaned mobile terminal). While it is anticipated that the customer will be responsible for returning the loaned mobile terminal 60, if the customer is responsible for returning the loaned mobile terminal 60, guidance on how to return the loaned mobile terminal 60 may be displayed, for example, on the payment QR code reading completion screen or the transaction completion screen, similar to the case where the customer is responsible for returning the charging cart. This guidance may include map information (floor information) indicating the return location (return location, return device, etc.). Furthermore, if the customer is responsible for charging the loaned mobile terminal 60, guidance on how to charge the loaned mobile terminal 60 may be displayed, for example, on the payment QR code reading completion screen or the transaction completion screen, similar to the case where the customer is responsible for charging the charging cart. The above guidance may also include operational information showing how to charge the device (such as how to operate the charging device, which is a return device).

[0174] By displaying guidance (information) like the above, store staff can reduce the burden of cumbersome tasks such as collecting and charging charging carts and portable rental devices, enabling store operations with fewer people.

[0175] (36) In the above embodiment, the transaction status management device 40 was described as a device that mainly manages (monitors and controls) each device within the LAN 19, but the transaction status management device 40 may also manage (monitors and controls) the cart storage area, etc. That is, the transaction status management device 40 may be able to communicate with devices installed in the cart storage area, or with the shopping carts themselves that are present in the cart storage area, and for example, the number of shopping carts present in the cart storage area (regardless of whether they are electronic tag recognition carts or charging carts) (the number of waiting carts if the cart storage area is a lending / returning place or a lending place) may be displayed on the management screen. In addition, if the shopping carts are charging carts, the transaction status management device 40 may also display on the management screen the charging status (battery level, etc.) of each charging cart in the cart storage area, the number of charging carts that can be lent out (charging carts with a battery level above a certain value), etc. The transaction status management device 40 may display, in addition to or instead of, the charging status of each charging cart in the cart collection area, the charging status of charging carts in the store (on loan) on its management screen. In this case, the charging carts may transmit information about their battery level to the transaction status management device 40 via wireless communication. The transaction status management device 40 may also similarly manage (monitor and control) the return locations (return devices, charging devices) for the loaned mobile terminals 60.

[0176] (37) The transaction status management device 40 may display operation history information for each device. For example, the transaction status management device 40 may display operation history information for each device in the LAN 19, mobile terminals 60 (including loaned mobile terminals 60), and shopping carts (which may be electronic tag recognition carts or charging carts). The operation history includes, for example, the start time of use, the registration time for each product, the registration completion time, the settlement start time, the settlement end time, the transaction completion time, the loan time if the mobile terminal 60 is a loaned item, the return time, information regarding screen transitions, information regarding operations (including changes in product registration quantities, etc.), and product registration information. The operation history information includes both history information regarding the operations of completed transactions and history information regarding the operations of transactions before completion (currently ongoing) (operations of the transaction up to the present). Therefore, a store employee (monitoring employee) can use the transaction status management device 40 to check, for example, which screen a particular mobile terminal 60 (a particular customer) has been on and for how long.

[0177] (38) The transaction status management device 40 may remotely control the display of guidance information on mobile terminals 60 (including loaned mobile terminals 60), shopping carts (which may be electronic tag recognition carts or charging carts), etc. In other words, the mobile terminals 60, etc. may display guidance information in accordance with the remote control by the transaction status management device 40. For example, the transaction status management device 40 may accept an operation to select (specify) a target device (customer) or a target guidance (type of guidance), and based on the selection operation by the store clerk, it may transmit information to the selected terminal to display the selected guidance.

[0178] According to (37) and (38) above, for example, a store employee can use the transaction status management device 40 to estimate the situation of each customer (each device) (such as the situation in which they are having trouble) and provide appropriate guidance to the customer who needs it via remote operation. In other words, multiple customers can be efficiently supported (guided) at a predetermined location (one location if there is only one transaction status management device 40). The transaction status management device 40 may also, as guidance (or separately from guidance), transmit map information (floor information) that clearly shows the location of the service counter and the installation location of the transaction status management device 40 to the customer (device) who needs it, and guide the customer. The mobile terminal 60, etc., may also, regardless of whether it transmits information, display map information based on the customer's operation (for example, operation of the help button) so that the customer can check the location of the service counter, etc. as appropriate. The mobile terminal 60, etc., may store map information and display the stored map information based on the customer's operation, or it may request map information from the transaction status management device 40 based on the customer's operation and display it. In the former case, the mobile terminal 60, etc., may notify the transaction status management device 40 that the help button or similar operation has been performed.

[0179] <Summary of Embodiments> [Technical field] This invention relates to a program and a product sales data processing device. [Background technology] A self-service system has been proposed in which customers register products themselves using a mobile device. On the other hand, a system that displays guidance about the product being imaged is known (see, for example, Patent Document 1). [Prior art document] [Patent] [Patent Document 1] Japanese Unexamined Patent Publication No. 2015-53030 [Overview of the prefecture] [Problems the invention aims to solve] However, some customers are unfamiliar with the self-service systems described above. Such systems cannot support these customers. This invention was made in view of these circumstances, and aims to provide a technology that enables even beginners to easily use services via mobile devices. [Means for solving the problem]

[0180] (1) A program that causes a computer to function as a product sales data processing device (e.g., a mobile terminal 60, a shopping cart, etc.), wherein the computer functions as an imaging means (e.g., an imaging unit 316) for imaging products to be purchased, a guidance means for guiding the operator through procedures using guidance images (e.g., a tutorial image GA601, a product scan guide image GA624, a two-dimensional code scan guide image GA633, and an image GA627), and a display means (e.g., a display unit 305) capable of displaying the images captured by the imaging means, wherein the display means displays part or all of a first guidance image (e.g., a product scan guide image GA624), which is one of the guidance images, in an imaging image display area (e.g., an imaging image display area HR621) for displaying the captured images, and the guidance means terminates the guidance using the first guidance image based on predetermined conditions (e.g., registration of one product item). According to program (1), even beginners can easily use it.

[0181] (2) The program according to (1) is characterized in that the display means is capable of displaying detailed information of the product to be purchased, and displays the first guide image (for example, product scan guide image GA624) across the detailed information display area (for example, registration information display area HR622) for displaying the detailed information and the captured image display area (for example, captured image display area HR621). According to program (2), even beginners can easily use it.

[0182] (3) The program according to (1) or (2), characterized in that the computer functions as an operation receiving means (for example, a button BT626 to proceed to payment) that can receive an operation to proceed to payment, and the operation receiving means does not receive the operation before the guidance using the first guidance image is completed (see Figure 7(D)), and accepts the operation after the guidance using the first guidance image is completed (see Figure 8(A)). According to program (3), even beginners can easily use it.

[0183] (4) The display means is capable of displaying a settlement code (for example, a settlement two-dimensional code GA631) for settling the purchase of the goods, and when the settlement code is displayed, a second guide image (for example, a settlement two-dimensional code scan guide image GA633) which is different from the first guide image (for example, a product scan guide image GA624) is displayed below the settlement code, characterized in that the program is as described in any one of (1)1 to (3). According to program (4), even beginners can easily use it.

[0184] (5) The program according to any one of (1) to (4), wherein the guidance image is displayed on a mobile terminal (e.g., mobile terminal 60) used by a customer purchasing a product, and the guidance means is characterized in that it changes the manner of guidance using the guidance image (e.g., tutorial image GA601) based on the number of times the customer has used the mobile terminal (e.g., the number of times it has been launched). According to the program in (5), a guide image can be displayed appropriately.

[0185] (6) A product sales data processing device (for example, a mobile terminal 60, a shopping cart, etc.) comprising: an imaging means for imaging the product to be purchased; a guidance means for guiding the operator through the procedure using guidance images; and a display means capable of displaying the image captured by the imaging means, wherein the display means displays part or all of a first guidance image, which is one of the guidance images, in an imaging image display area for displaying the image, and the guidance means terminates the guidance using the first guidance image based on predetermined conditions. According to the product sales data processing device in (6), even beginners can easily use it.

[0186] (7) A program that causes a computer to function as a product sales data processing device (for example, a mobile terminal 60, a shopping cart, etc.), wherein the computer functions as an imaging means for capturing images of products and a display means for displaying guidance images to guide the operator through the procedure, the display means overlays part or all of the guidance image onto the image being captured by the imaging means (see Figure 7(D)), and the guidance of the procedure by the guidance image terminates based on predetermined conditions. According to program (7), even beginners can easily use it.

[0187] Furthermore, the functions of each of the devices described above (headquarters server 10, store controller 30, transaction status management device 40, settlement device 50, registration settlement device 51, mobile terminal 60, shopping cart, etc.) may be realized by recording a program (for example, a specific application in the case of the mobile terminal 60, etc.) on a computer-readable recording medium, loading the program recorded on this recording medium into a computer system, and executing it to perform the processing of each of the above devices. Here, "loading the program recorded on the recording medium into a computer system and executing it" includes installing the program into the computer system. Here, "computer system" includes hardware such as the OS and peripheral devices. Also, "computer system" may include multiple computer devices connected via a network including communication lines such as the Internet, WAN, LAN, and dedicated lines. Also, "computer-readable recording medium" refers to portable media such as flexible disks, magneto-optical disks, ROMs, CD-ROMs, and storage devices such as hard disks built into the computer system. Thus, the recording medium storing the program may also be a non-transient recording medium such as a CD-ROM. Also, the recording medium includes internal or external recording media that can be accessed from a distribution server for distributing the program. The program code stored on the distribution server's recording medium may be different from the program code in an executable format on the terminal device. In other words, as long as it can be downloaded from the distribution server and installed in an executable format on the terminal device, the format in which it is stored on the distribution server is irrelevant. Furthermore, the program may be divided into multiple parts, downloaded at different times and then combined on the terminal device, and each of the divided programs may be distributed by a different distribution server. In addition, "computer-readable recording medium" includes volatile memory (RAM) within computer systems that act as servers or clients when a program is transmitted over a network, which retains the program for a certain period of time. Moreover, the above program may be intended to implement only a part of the functions described above.Furthermore, the above-mentioned functions may be realized in combination with programs already recorded in the computer system, such as so-called differential files (differential programs). [Explanation of Symbols]

[0188] 1…Sales system 10… Headquarters Server 20…Cloud Server 30…Store Controller 40... Transaction status management device 50…Payment device 51...Registration and settlement device 60… Mobile devices

Claims

1. A program that makes a computer function as a product sales data processing device, The aforementioned computer, imaging means for imaging products, Display means capable of displaying the image captured by the imaging means, Registration means for registering products captured by the imaging means, A means of declaring that product registration has been completed and that the payment process will proceed. To make it function as, The aforementioned display means is It is possible to guide the operator through the procedure by displaying a guide image on a screen different from the screen that displays the captured image. The system displays a first guidance image, one of the aforementioned guidance images, to guide the user through the product registration process. Once the guidance on the registration process is complete, it displays a second guidance image, another of the aforementioned guidance images, to guide the user through the checkout process. Along with the second guidance image, it displays an operator for proceeding to product registration using the registration means. A program characterized by the following features.

2. The aforementioned display means is The manner of guidance using the guidance image is varied based on the number of times the operator uses the product sales data processing device. The program according to feature 1.

3. An imaging means for photographing products, A display means capable of displaying the image captured by the aforementioned imaging means, A registration means for registering products captured by the imaging means, Equipped with, The aforementioned display means is It is possible to guide the operator through the procedure by displaying a guide image on a screen different from the screen that displays the captured image. The system displays a first guidance image, one of the aforementioned guidance images, to guide the user through the product registration process. Once the guidance on the registration process is complete, it displays a second guidance image, another of the aforementioned guidance images, to guide the user through the checkout process. Along with the second guidance image, it displays an operator for proceeding to product registration using the registration means. A product sales data processing device characterized by the following features.

Images