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 technology]

[0002] A self-service system has been proposed in which customers themselves can register products using a mobile terminal. Meanwhile, a system that displays guidance about a product that is the subject of an image capture is also known (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

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

[0004] However, there are some customers who are not familiar with the self-service system described above, and the system described above cannot support such customers.

[0005] The present invention has been made in consideration of the above circumstances, and aims to provide a technique that enables even beginners to easily use services that use mobile terminals. [Means for solving the problem]

[0006] One aspect of the present invention for solving the above-mentioned problems is a program that causes a computer to function as a product sales data processing device, causing the computer to function as an imaging means for imaging the product to be purchased, a guidance means for guiding an operator through a procedure using a guidance image that guides the operator through the procedure, and a display means capable of displaying an 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 image capture image display area for displaying the image capture image, and the guidance means terminates the guidance using the first guide image based on a predetermined condition. [Brief description of the drawings]

[0007] [Figure 1] FIG. 1 is a conceptual diagram of a network for explaining a sales system. [Diagram 2] 2 is a configuration example of a cloud server. [Diagram 3] 1 is an example of information stored in a cloud server. [Figure 4] 2 is a configuration example of a mobile terminal. [Diagram 5] 2 is a configuration example of a settlement device. [Figure 6] 13 is a display example of a mobile terminal. [Figure 7] 13 is a display example of a mobile terminal. [Figure 8] 13 is a display example of a mobile terminal. [Figure 9] 13 is a display example of a mobile terminal. [Figure 10] 13 is a display example of a mobile terminal, etc. [Figure 11] FIG. 11 is a sequence diagram showing an example of processing by a mobile terminal and a cloud server. [Figure 12] FIG. 11 is a sequence diagram showing an example of processing by a mobile terminal and a cloud server. [Figure 13] FIG. 11 is a sequence diagram showing an example of processing by a mobile terminal and a cloud server. [Figure 14] FIG. 11 is a sequence diagram showing an example of processing by a mobile terminal and a cloud server. [Figure 15]FIG. 11 is a sequence diagram showing an example of processing by a mobile terminal and a cloud server. [Figure 16] A sequence diagram showing an example of processing by the settlement device, the mobile terminal, and the cloud server. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

[0009] The store controller 30, the transaction status management device 40, the settlement device 50, and the registration settlement device 51 are communicatively connected via a LAN 19 (which may be wired or wireless). The sales system 1 can be introduced in various stores (supermarkets, convenience stores, drug stores, home centers, home appliance retailers, etc.).

[0010] In Fig. 1, the number of each device (terminal) is an example. For example, in Fig. 1, "..." is illustrated to the right of the transaction status management device 40, but the number of transaction status management devices 40 installed in one store may be one or more. Also, for example, in Fig. 1, two mobile terminals 60 are illustrated, but the number of mobile terminals 60 used in the store changes depending on the number of customers.

[0011] Sales system 1 provides a self-service (hereinafter, sometimes referred to as service A) in which a customer uses a mobile terminal 60 to register a product and uses a settlement device 50 to settle the payment. In other words, service A is a self-service in which a customer registers a product and settles the payment by himself / herself, using mobile terminal 60 for product registration and using settlement device 50 for settlement.

[0012] Furthermore, the sales system 1 provides other services in addition to the service A. For example, as other services, the sales system 1 can provide a service in which a customer uses the registration and settlement device 51 to register and settle an item, or a service in which a store clerk uses a registration device (not shown) to register an item, and the customer uses a settlement device (not shown) to settle the item.

[0013] The headquarters server 10 is installed outside the store (e.g., at a head office or a data center) and is a server that manages the entire sales system 1. The headquarters server 10 stores, for example, various information (e.g., product master, special sale file, etc.) necessary for the operation of services including service A, and performance information of services in the store (e.g., sales performance information, product sales performance information, etc.). The headquarters server 10 communicates with the cloud server 20 and the store controller 30. The headquarters server 10 may communicate with other devices (e.g., a transaction status management device 40, a settlement device 50, etc.). The headquarters server 10 may be composed of multiple servers.

[0014] Cloud server 20 is a server installed outside a store (e.g., in a data center, etc.) and provides service A. Cloud server 20 stores, for example, various information required for the operation of service A (e.g., product master, transaction information (also referred to as cart information), etc.). Cloud server 20 communicates with headquarters server 10 and mobile terminal 60. Cloud server 20 may also communicate with other devices (e.g., store controller 30, transaction status management device 40, etc.). Cloud server 20 may be composed of multiple servers.

[0015] The store controller 30 is a device that controls the part of the sales system 1 that is related to the store. The store controller 30 communicates with each device in the LAN 19 (e.g., the settlement device 50, etc.) and each device outside the LAN 19 (e.g., the headquarters server 10). For example, the store controller 30 receives a product master and a sale file from the headquarters server 10 and provides them to the settlement device 50.

[0016] The transaction status management device 40 is a device that mainly manages (monitors and controls) each device in the LAN 19. For example, the transaction status management device 40 communicates with each device in the LAN 19 and monitors the processing status, operation status, etc. of each device in the LAN 19. The transaction status management device 40 may also communicate with each device outside the LAN 19 (e.g., the head office server 10, the cloud server 20) (it may communicate 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 a terminal used when registering a product in the service A. In other words, the customer uses the mobile terminal 60 when registering a product in the service A.

[0018] The mobile terminal 60 may be owned by a customer (member) who uses service A, or may be loaned by the store. In this embodiment, the mobile terminal 60 is described as being owned by a customer who uses service A. In this embodiment, the mobile terminal 60 executes a predetermined application program (hereinafter, may be referred to as a specific app) and registers a product in service A. In other words, a customer who intends to use service A installs the specific app in advance on his / her mobile terminal 60, and starts the specific app before using service A. Note that the mobile terminal 60 may access a predetermined server (e.g., cloud server 20 or a dedicated server (not shown), etc.), download the specific app from the server, and install it.

[0019] 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 is prepared near the entrance / exit of the store (or the entrance if the entrance and exit are separate) that includes a shopping basket installation section for installing a shopping basket and a mobile terminal installation section (holder) for setting the mobile terminal 60. When a customer who uses service A comes to the store, he or she sets the shopping basket in the shopping basket installation section of the shopping cart, sets the mobile terminal 60 in the mobile terminal installation section, and proceeds into the store.

[0020] The settlement device 50 is a device used when making a settlement in service A. In other words, the customer uses the settlement device 50 when making a settlement for the product registered using the mobile terminal 60.

[0021] The registration and settlement device 51 is mainly used by customers. The registration and settlement device 51 includes a scanner unit and a settlement unit, and is used for registering and settling products.

[0022] 2 shows an example of the configuration of cloud server 20. Cloud server 20 includes a CPU 201, a ROM 202, a RAM 203, and a hard disk 204. These 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 . The ROM 202 is a read-only memory, and stores various types of information used by the CPU 201, including programs. The RAM 203 is a read / write memory and stores various information as a main storage device, for example, information read from the ROM 202 or the hard disk 204, information acquired from the outside, information generated during processing, and the like. The hard disk 204 stores various information (for example, see FIG. 3) as an auxiliary storage device. The hard disk 204 may store, for example, a program executed by the CPU 201 instead of the ROM 202. The hard disk 204 may also store, instead of the RAM 203, information read from the ROM 202, information acquired from the outside, information generated during processing, and the like. The communication unit 215 transmits and receives information to and from other devices (eg, the mobile terminal 60, the head office server 10, etc.).

[0024] FIG. 3 is an example of information stored in cloud server 20. FIG. 3(A) is an example of transaction information (cart information) stored in cloud server 20. Cloud server 20 generates transaction information at the start of a transaction. Cloud server 20 also updates the transaction information as the transaction progresses. The transaction information shown in FIG. 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] The transaction identification information is identification information that uniquely identifies the transaction information. For example, the transaction identification information may be composed of store identification information, a date, and a serial number (e.g., a store-specific and date-specific serial number). The transaction start date and time is the date and time when the transaction started (e.g., the date and time when the cart information was generated, or the date and time when one item of product was registered (the date and time when the registered information (product 1) in FIG. 3(A) was stored)). The transaction end date and time is the date and time when the transaction ended (e.g., the date and time when payment was completed).

[0026] The member identification information is information that uniquely identifies a customer (member). The member identification information may be determined when a specific application is downloaded. As an example, the member identification information may be generated (numbered) by a specific server (cloud server 20, dedicated server). For example, the specific server may generate the member identification information when it receives a request to download a specific application from the mobile terminal 60. When the dedicated server generates the member identification information, the dedicated server may notify the cloud server 20 of the member identification information. As another example, the member identification information may be determined by a customer. For example, the mobile terminal 60 may be input by the customer when transmitting a request to download a specific application to the specific server (after transmission, the specific server confirms that the member identification information does not overlap with other member identification information). When the dedicated server acquires the member identification information, the dedicated server may notify the cloud server 20 of the member identification information.

[0027] Note that mobile terminal 60 may store member identification information. For example, if member identification information is generated by a specified server, mobile terminal 60 may receive and store member identification information from the specified server. Also, for example, if member identification information is input by a member, mobile terminal 60 may store member identification information input by the member.

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

[0029] Fig. 3(B) is an example of member record information stored by cloud server 20. Cloud server 20 generates member record information, for example, after determining member identification information. Cloud server 20 also updates the member record information, for example, every time a transaction is made using service A. The member record information shown in Fig. 3(B) includes transaction identification information, the number of times the app was launched, the first time the app was launched, and the last time the app was launched.

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

[0031] The member record information may include information other than the above information. For example, the member record information may include the number of points, the member rank, the last (most recent) purchase date (which may be the last purchase date for service A), the frequency of store visits within a specified period (which may be the frequency of store visits and use of service A), and the total purchase amount within a specified period (which may be the total purchase amount for service A).

[0032] The information stored by the cloud server 20 is not limited to the product master (not shown), the transaction information (FIG. 3(A)), and the member performance information (FIG. 3(B)). For example, the cloud server 20 may store (generate, update) the member master. For example, the cloud server 20 may acquire information identifying the mobile terminal 60 (e.g., MAC address, phone number, etc.) and information input by the customer (e.g., name, date of birth, address, gender, etc.) in a request for downloading a specific application, and store (generate) the member master based on the acquired information. When 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) the member master based on the supplied information. Instead of or in addition to the cloud server 20, the head office server 10 may store the member master.

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

[0034] CPU 301 is a central processing unit, and controls the operation of mobile terminal 60 by reading and executing programs stored in ROM 302 and programs (e.g., a downloaded specific application) stored in storage 304. For example, when imaging unit 316 captures an image of a barcode attached to a product, CPU 301 extracts feature points in the captured image (image acquired as a through image (live view)) captured by imaging unit 316, and recognizes the barcode, which is an object. The ROM 302 is a read-only memory, and stores various types of information used by the CPU 301, including programs. The RAM 303 is a read / write memory and stores various information as a main storage device, for example, information read from the ROM 302 or the storage 304, information acquired from the outside, information generated during processing, and the like. The storage 304 stores various information (for example, a specific application) as an auxiliary storage device. The storage 304 may store information read from the ROM 302, information acquired from the outside, information generated during processing, etc., in place of the RAM 303.

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

[0036] The communication unit 315 transmits and receives information to and from other devices (for example, the cloud server 20). The communication unit 315 may also transmit and receive voice information to and from other mobile terminals 60 and the like in relation to a call. Note that the communication by the communication unit 315 may be wireless communication according to a method stipulated by the International Telecommunication Union (ITU) (4G, 5G, etc.), or wireless communication according to a method stipulated by a wireless LAN organization (Wi-Fi (registered trademark), etc.). The imaging unit 316 captures an image. For example, the imaging unit 316 captures an image of various codes (for example, a barcode or a two-dimensional code). The voice input unit 318 inputs voice. For example, the voice input unit 318 inputs voice for operations using voice recognition. The voice input unit 318 also inputs voice related to a call to be transmitted to the other party.

[0037] The mobile terminal 60 may further include a position measurement unit (GPS function), a motion determination unit (for example, an acceleration sensor, an angular velocity sensor, etc.), a short-range wireless communication unit (Bluetooth (registered trademark), an infrared sensor), etc.

[0038] 5 is a configuration example of settlement device 50. Settlement device 50 includes a CPU 101, ROM 102, RAM 103, hard disk 104, display unit 105, scanner unit 106, card settlement unit (non-cash settlement unit) 108, change machine (cash settlement unit) 109, printing unit 113, audio output unit 114, communication unit 115, imaging unit 116, and sign pole 117. These can communicate with each other via a bus.

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

[0040] The scanner unit 106 optically reads various information. Specifically, the scanner unit 106 scans a code (a two-dimensional code for settlement GA631 (described later)) displayed on the display unit of the mobile terminal 60, and reads information necessary for settlement processing. The scanner unit 106 may also scan codes attached to gift certificates (gift certificates, coupons, and complimentary coupons) and various cards (e.g., membership cards, point cards, etc.) and read the respective information. The scanner unit 106 may also scan codes attached to the name tags of store clerks, etc., and read store clerk 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 uses various 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 that the card payment unit 108 includes at least the card recognition unit. The card recognition unit may recognize various cards (e.g., point cards, membership cards, stockholder cards, etc.) for the purpose of providing benefits, discounts, etc. The change machine 109 is a cash settlement mechanism, which has an input port for banknotes and coins, and an output port for banknotes and coins, calculates the amount of money inserted into the input port, calculates the change amount, which is the difference between the input amount and the purchase amount, and outputs the change from the output port. When banknotes or coins are inserted into the input port, they are detected by a sensor (detecting that they have been inserted, detecting the number of coins by denomination, etc.).

[0042] The printing unit 113 prints and issues various media (receipts, etc.). The audio output unit 114 outputs audio. For example, the audio output unit 114 outputs a confirmation sound, a warning sound, audio guidance, and the like. The communication unit 115 transmits and receives information to and from other devices (for example, the store controller 30, the transaction status management device 40, etc.). The imaging unit 116, for example, captures an image of the customer. The settlement device 50 may include two or more imaging units 116, and simultaneously capture images of the face and hands (near the insertion slot and ejection slot of the change machine 109). The sign pole 117 has a light emitting part at the tip, and notifies various information (such as calling a store clerk, operating status, etc.) depending on the light emitting state of the light emitting part.

[0043] The settlement device 50 may further include a key operation unit consisting of various keys (buttons). The settlement device 50 may further include a sensor (such as a human presence sensor) that detects the presence of a person. The settlement device 50 may further include a sensor that detects when various media printed and issued by the printing unit 113 have been removed (pulled out).

[0044] (Display on mobile terminal 60) The display on the mobile terminal 60 will be described below. Figs. 6 to 9 are examples of the display on the mobile terminal 60. Fig. 10 is a display on the mobile terminal 60 and the like. Figs. 6 to 10 (excluding Fig. 10(D)) sequentially show screens related to service A after a specific application is started. Specifically, when the current start of the specific application is the first time (first time), the mobile terminal 60 displays the following screens after the start of the specific application: Fig. 6(A) → Fig. 6(B) → Fig. 6(C) → Fig. 6(D) → Fig. 7(A) → Fig. 7(B) → Fig. 7(C) → Fig. 7(D) → Fig. 8(A) → Fig. 8(B) → Fig. 8(C) → Fig. 8(D) → Fig. 9(A) → Fig. 9(B) → Fig. 9(C) → Fig. 9(D) → Fig. 10(A) → Fig. 10(B) → Fig. 10(C). If this is the second or subsequent launch of a specific app, after launching the specific app, mobile terminal 60 will display the following order: 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] Fig. 6(A) to Fig. 6(C) are tutorial screens for service A. Fig. 6(D) is a menu screen (start screen) for service A. The tutorial screen is displayed if this is the first (first) launch of a specific app, but is not displayed if this is not the first launch of a specific app (if this is the second or subsequent launch).

[0046] (If this is the first launch of a particular app) If this is the first time that a particular app is launched, the mobile terminal 60 displays tutorial screens such as those shown in Figures 6(A) to 6(C) in order, and then displays a menu screen such as that shown in Figure 6(D).

[0047] The tutorial screen shown in Fig. 6(A) is the tutorial screen that is displayed first when the current launch of the specific application is the first launch. In other words, when a member launches a specific application and this launch is the first launch, the mobile terminal 60 displays the tutorial screen as shown in Fig. 6(A). The tutorial screen shown in Fig. 6(A) displays an image GA601a and a message MS602a that introduce shopping (concept) by service A. In addition, a next button BT603 is arranged on the tutorial screen shown in Fig. 6(A) (similar to the tutorial screen shown in Fig. 6(B)).

[0048] The tutorial screen shown in Fig. 6(B) is displayed following the tutorial screen shown in Fig. 6(A). When a member operates the Next button BT603 on the tutorial screen shown in Fig. 6(A), the mobile terminal 60 displays the tutorial screen as shown in Fig. 6(B). On the tutorial screen shown in Fig. 6(B), an image GA601b and a message MS602b are displayed, which introduce shopping (product registration section) using service A.

[0049] The tutorial screen shown in Fig. 6(C) is displayed following the tutorial screen shown in Fig. 6(B). When a member operates the Next button BT603 on the tutorial screen shown in Fig. 6(B), the mobile terminal 60 displays the tutorial screen as shown in Fig. 6(C). On the tutorial screen shown in Fig. 6(C), an image GA601c and a message MS602c are displayed, which introduce shopping (the checkout part) using service A. Also, on the tutorial screen shown in Fig. 6(C), a service start button BT604 that announces the start of the service is arranged.

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

[0051] The menu screen shown in Fig. 6(D) is displayed following the tutorial screen. When a member operates the service start button BT604 on the tutorial screen shown in Fig. 6(C), the mobile terminal 60 displays a menu screen as shown in Fig. 6(D). Various buttons related to service A are arranged on the menu screen shown in Fig. 6(D). For example, a shopping start button BT610 that declares the start of shopping is arranged on the menu screen shown in Fig. 6(D). It should be noted that the "member number" on the menu screen shown in Fig. 6(D) is member identification information.

[0052] (If this is the second or subsequent launch of a specific app) If the current launch of the specific app is the second or subsequent launch, the mobile terminal 60 does not display the tutorial screen as shown in Figures 6(A) to 6(C), but displays a menu screen as shown in Figure 6(D). In other words, when a member launches a specific app and this launch is the second or subsequent launch, the mobile terminal 60 first displays the menu screen as shown in Figure 6(D).

[0053] 7(A) to 9(C) are registration screens. The registration screen shown in FIG. 7(A) is displayed following the menu screen shown in FIG. 6(D). When a member operates the shopping start button BT610 on the menu screen shown in FIG. 6(D), the mobile terminal 60 displays the registration screen shown in FIG. 7(A). The registration screen shown in FIG. 7(B) is displayed following the registration screen shown in FIG. 7(A). If a predetermined time (e.g., 0.5 seconds) has elapsed without a product being registered on the registration screen shown in FIG. 7(A) (without reading the barcode attached to the product), the mobile terminal 60 displays the registration screen shown in FIG. 7(B). The registration screen shown in FIG. 7(C) is displayed following the registration screen shown in FIG. 7(B). If a predetermined time (e.g., 0.5 seconds) has elapsed on the registration screen shown in FIG. 7(B) without a product being registered, the mobile terminal 60 displays the registration screen shown in FIG. 7(C). If a predetermined time (e.g., 0.5 seconds) has elapsed on the registration screen shown in FIG. 7(B), the mobile terminal 60 displays the registration screen shown in FIG. 7(C).

[0054] Furthermore, when a predetermined time (e.g., 0.5 seconds) has elapsed without a product being registered on the registration screen shown in Fig. 7(C), the mobile terminal 60 displays the initial registration screen shown in Fig. 7(A), and similarly, when a further predetermined time has elapsed, the mobile terminal 60 displays the initial registration screen shown in Fig. 7(B), and similarly, when a further predetermined time has elapsed, the mobile terminal 60 displays the initial registration screen shown in Fig. 7(C), and similarly, when a further predetermined time has elapsed, the mobile terminal 60 displays the initial registration screen shown in Fig. 7(A) (hereinafter the same). In other words, the mobile terminal 60 repeatedly displays a 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) (as well as the registration screen shown in Figure 7(D)) are registration screens in a state where no products have been registered yet (before the registration of one product). In the following explanation, the registration screen in a state where no products have been registered yet may be referred to as an initial registration screen to distinguish it from a registration screen in a state where one or more products have already been registered.

[0056] The upper part of the registration screen is a captured image display area HR621 that mainly displays a captured image. The center of the captured image display area HR621 is a barcode reading area suitable for reading barcodes (a rectangular area with a message "Please hold the barcode over the display area" displayed in the center). The lower part of the registration screen is a registration information display area HR622 that mainly displays product registration information. The bottom part of the registration screen is a related information display area HR623 that displays other related information.

[0057] The initial registration screen explains how to register a product. For example, the initial registration screens shown in Figs. 7(A) to 7(C) display images (image GA624a, image GA624b, image GA624c) explaining how to register a product. The image GA624a of the initial registration screen shown in Fig. 7(A) shows a state in which a barcode attached to a product is brought close to the mobile terminal 60 so that the barcode attached to the product is imaged by the mobile terminal 60 (the mobile terminal 60 set in the mobile terminal installation section (holder)). The image GA624b of the initial registration screen shown in Fig. 7(B) shows a state in which the barcode is imaged. The image GA624c of the initial registration screen shown in Fig. 7(C) shows a state in which the barcode is read. Note that the images GA624a to GA624c may be collectively referred to as a product scan guide image GA624.

[0058] As shown in Fig. 7(A) to Fig. 7(C), the mobile terminal 60 displays the product scan guide image GA624 at a position straddling the captured image display area HR621 and the registered information display area HR622 (in front of 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 located in front of the area below the barcode reading area of ​​the captured image display area HR621, and the remaining part of the product scan guide image GA624 is located in front of the area excluding the lower area of ​​the registered information display area HR622. The upper part of the product scan guide image GA624 is shaped like a balloon. The product scan guide image GA624 points to the barcode reading area of ​​the captured image display area HR621 with the balloon (symbol f in Fig. 7(A)).

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

[0060] Fig. 7(D) is an initial registration screen when XX bread is imaged as the first item. In the image display area HR621 (barcode reading area) of the initial registration screen shown in Fig. 7(D), the barcode attached to XX bread is displayed as a through image. Note that Fig. 7(D) is an example in which the member reads the barcode on the initial registration screen shown in Fig. 7(C) (while image GA624c is displayed), but as described above, the member can also read the barcode on the initial registration screen shown in Fig. 7(A) (while image GA624a is displayed) or the initial registration screen shown in Fig. 7(B) (while image GA624b is displayed).

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

[0062] A flow from the initial registration screen shown in FIG. 7(D) to the display of the registration screen shown in FIG. 8(A) will be described. The mobile terminal 60 transmits the product code acquired from the barcode to the cloud server 20. The cloud server 20 refers to the product master and acquires the product name "XXX bread" and the price "¥220" based on the product code. The cloud server 20 stores the product code, the product name "XXX bread", the quantity "1", the price "¥220", etc. as registration information in the transaction information of the transaction. The cloud server 20 also transmits the registration information (product name "XXX 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 or the small screen SG625.

[0063] The mobile terminal 60 displays a part of the registration information (quantity) as a quantity button. The quantity button is a button for changing the quantity. After registering a product (one item of product), the mobile terminal 60 also displays an operable Proceed to Checkout button BT626 which declares that the product registration has been completed and that the user is to proceed to checkout (payment).

[0064] The registration screen shown in Fig. 8(B) is displayed following the registration screen shown in Fig. 8(A). When a predetermined time (e.g., 2 seconds) has elapsed on the registration screen shown in Fig. 8(A), the mobile terminal 60 displays a registration screen as shown in Fig. 8(B). On the registration screen shown in Fig. 8(B), the small screen SG625 displayed on the registration screen shown in Fig. 8(A) has been erased. Also, on the registration screen shown in Fig. 8(B), an image GA627 (message "Touch here to proceed to payment") explaining the button BT626 to proceed to checkout is displayed.

[0065] The registration screen shown in FIG. 8(C) is a registration screen after further time has passed since the registration screen shown in FIG. 8(B). In the captured image display area HR621 of the registration screen shown in FIG. 7(D) to FIG. 8(B), the XX bread was displayed as a through image, but it is not displayed in the captured image display area HR621 of the registration screen shown in FIG. 8(C). In other words, when the member puts the XX bread in the cart (shopping basket) after the registration of the XX bread is completed, the XX bread moves out of the imaging range of the imaging unit 316, so the mobile terminal 60 displays the registration screen as shown in FIG. 8(C). Note that if the member puts the XX bread in the cart (shopping basket) before the small screen SG625 is erased (during display), the state of the registration screen shown in FIG. 8(B) does not occur, so the state transitions from FIG. 8(A) to FIG. 8(C).

[0066] The registration screen shown in Fig. 8(C) does not capture an image of a product, like the initial registration screens shown in Fig. 7(A) to Fig. 7(C), but unlike the initial registration screens shown in Fig. 7(A) to Fig. 7(C), the registration screen shown in Fig. 8(C) does not display a product scan guide image GA624 explaining how to register a product. In other words, when no product has been registered yet, the mobile terminal 60 displays an image (product scan guide image GA624) explaining how to register a product on the registration screen (initial registration screen), but does not display an image explaining how to register a product on the registration screen when one or more products have already been registered.

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

[0068] The registration screen shown in Fig. 9(A) is displayed following the registration screen shown in Fig. 8(D). Specifically, the registration screen shown in Fig. 9(A) is a registration screen after the registration of the second item (XX Oolong Tea) is completed. The product name "XX Oolong Tea", the quantity "1", and the price "¥150" are additionally displayed in the registration information display area HR622 of the registration screen shown in Fig. 9(A). 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 "XX Oolong Tea" and the price "¥150" is displayed in front of the captured image display area HR621 of the registration screen shown in Fig. 9(A).

[0069] The registration screen shown in Fig. 9(B) is displayed following the registration screen shown in Fig. 9(A). When a predetermined time (e.g., 2 seconds) has elapsed on the registration screen shown in Fig. 9(A), the mobile terminal 60 displays the registration screen as shown in Fig. 9(B).

[0070] The registration screen shown in Fig. 9(C) is a registration screen after further time has passed since the registration screen shown in Fig. 9(B). In the captured image display area HR621 of the registration screen shown in Fig. 8(D) to Fig. 9(B), XX Oolong Tea was displayed as a through image, but it is not displayed in the captured image display area HR621 of the registration screen shown in Fig. 9(C). Note that if the member puts XX Oolong Tea in the cart (shopping basket) before the small screen SG625 is erased (during display), the state of the registration screen shown in Fig. 9(B) does not occur, so the screen transitions from Fig. 9(A) to Fig. 9(C).

[0071] 9(D), 10(A) and 10(B) are two-dimensional code display screens for payment. The two-dimensional code display screen for payment shown in FIG. 9(D) is displayed, for example, following the registration screen shown in FIG. 9(C). When the member operates the button BT626 for proceeding to checkout on the registration screen shown in FIG. 9(C), the mobile terminal 60 displays the two-dimensional code display screen for payment as shown in FIG. 9(D). The two-dimensional code display screen for payment shown in FIG. 10(A) is displayed following the two-dimensional code display screen for payment as shown in FIG. 9(D). When a predetermined time (for example, 0.5 seconds) has elapsed on the two-dimensional code display screen for payment shown in FIG. 9(D) without the settlement device 50 reading the two-dimensional code GA631 (described later), the mobile terminal 60 displays the two-dimensional code display screen for payment as shown in FIG. 10(A). The settlement two-dimensional code display screen shown in Fig. 10(B) is displayed following the settlement two-dimensional code display screen shown in Fig. 10(A). If a predetermined time (e.g., 0.5 seconds) has elapsed without the settlement device 50 reading the settlement two-dimensional code GA631 (described below) on the settlement two-dimensional code display screen shown in Fig. 10(A), the mobile terminal 60 will display the settlement two-dimensional code display screen as shown in Fig. 10(B).

[0072] Furthermore, when a predetermined time has elapsed without the settlement device 50 reading the settlement two-dimensional code GA631 (described later) on the settlement two-dimensional code display screen shown in Fig. 10(B), the mobile terminal 60 displays the settlement two-dimensional code display screen shown in Fig. 9(D), and when a further predetermined time has elapsed, the mobile terminal 60 displays the settlement two-dimensional code display screen shown in Fig. 10(A), and when a further predetermined time has elapsed, the mobile terminal 60 displays the initial registration screen shown in Fig. 10(B), and when a further predetermined time has elapsed, the mobile terminal 60 displays the settlement two-dimensional code scan guide image GA633 (described later) on the initial registration screen (described later) on the settlement two-dimensional code display screen.

[0073] The settlement two-dimensional code display screen displays a settlement two-dimensional code GA631 and a message MS632. In addition, a Return to Shopping button BT639 is arranged on the settlement two-dimensional code display screen. When the Return to Shopping button BT639 is operated, the mobile terminal 60 displays a registration screen (the registration screen displayed immediately before the Return to Shopping button BT639 is operated).

[0074] The two-dimensional settlement code GA631 is a two-dimensional code of information required to execute settlement processing. For example, the two-dimensional settlement code GA631 is a two-dimensional code of transaction identification information that identifies transaction information of the transaction from among multiple pieces of transaction information stored in the cloud server 20. Note that the information that is two-dimensionally 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 two-dimensional settlement code GA631 may be a two-dimensional code of location information of the transaction information of the transaction (a storage location within the sales system 1, such as a Uniform Resource Identifier (URI)).

[0075] Also, on the settlement two-dimensional code display screen, images (image GA633a, image GA633b, image GA633c) are displayed that explain how to make the settlement two-dimensional code GA631 be read by the settlement device 50. Image GA633a shown in FIG. 9(D) shows the state in which the settlement two-dimensional code GA631 is displayed on the display unit 305. Image GA633b shown in FIG. 10(A) shows the state in which the settlement two-dimensional code GA631 is brought closer to the settlement device 50 so that it can be read by the settlement device 50 (scanner unit 106). Image GA633c shown in FIG. 10(B) shows the state in which the angle of the settlement two-dimensional code GA631 (mobile terminal 60) is changed so that it can be read by the settlement device 50 (scanner unit 106). Note that images GA633a to GA633c may be collectively referred to as settlement two-dimensional code scan guide images GA633.

[0076] As shown in Figures 9(D) to 10(B), on the settlement two-dimensional code display screen, the settlement two-dimensional code scan guide image GA633 is displayed below the settlement two-dimensional code GA631. Since the settlement two-dimensional code scan guide image GA633, which occupies a relatively large area, is displayed below (towards the wrist, closer to the hand) than the settlement two-dimensional code GA631, the member can have the settlement device 50 read the settlement two-dimensional code GA631 without strain (ergonomically, for example, with a natural movement without twisting the wrist too much).

[0077] A member can have the settlement device 50 read the settlement two-dimensional code GA631 regardless of which of the settlement two-dimensional 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] Fig. 10(C) is the settlement two-dimensional code reading completion screen. The settlement two-dimensional code reading completion screen shown in Fig. 10(C) is displayed following the settlement two-dimensional code display screen. When the member has the settlement device 50 read the settlement two-dimensional code GA631 displayed on the settlement two-dimensional code display screen, the mobile terminal 60 displays a settlement two-dimensional code reading completion screen as shown in Fig. 10(C). The settlement two-dimensional code reading completion screen shown in Fig. 10(C) displays a message that the settlement machine (settlement device 50) has read the billing code (settlement two-dimensional code GA631) and a message that the member should settle the bill at the settlement machine.

[0079] (Display of settlement device 50) The settlement device 50 displays an initial screen (not shown) during standby. On the initial screen, a message to read the settlement two-dimensional code GA631 displayed on the mobile terminal 60 and an image explaining how to read the settlement two-dimensional code GA631 displayed on the mobile terminal 60 (for example, an image similar to the settlement two-dimensional code scan guide image GA633) are displayed. Note that the initial screen may also include a store clerk call button, a balance inquiry button, a language switching button, and the like. The store clerk call button is a button for calling a store clerk. The balance inquiry button is a button for inquiring about the balances of various cards. The language switching button is a button for switching the display (text) on the settlement device 50 from Japanese to another language (English, etc.).

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

[0081] In addition, the product list screen has a button to call a store clerk and a checkout button. The checkout button is a button for confirming that there are no problems with the contents displayed on the product list screen and for proceeding with the process. When the checkout button is operated, the settlement device 50 displays, for example, a payment type selection screen (not shown).

[0082] (Operation of the mobile terminal 60, etc.) FIG. 11 is a sequence diagram showing an example of the processing of the mobile terminal 60 and the cloud server 20. Specifically, FIG. 11 shows an example of the processing of the mobile terminal 60 and the cloud server 20 from when the mobile terminal 60 starts a specific application to when a menu screen is displayed. The left side of FIG. 11 (also in FIG. 12, FIG. 13, FIG. 14, and FIG. 15) 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 that the specific application has been started on the mobile terminal 60 (initial start). In other words, at the start of the flowchart in FIG. 11, it is assumed that "0 (times)" is stored in the member record information (FIG. 3(B)) stored in the cloud server 20 as the number of times the application is started, which corresponds to the member identification information of the member who uses the mobile terminal 60.

[0083] Step S1: The mobile terminal 60 starts a specific application based on a member's operation. For example, the mobile terminal 60 displays an icon for starting the specific application on the screen when the specific application is downloaded, and starts the specific application based on the member's operation of the icon for starting the specific application. Step S2: The mobile terminal 60 transmits application start-up information notifying (reporting) that a specific application has been started. The application start-up information includes the member identification information.

[0084] Step S3: The cloud server 20 receives the application start-up information. Step S4: Cloud server 20 determines that this is the first time the specific application has been launched. Specifically, cloud server 20 refers to the number of times the application has been launched that corresponds to the member identification information included in the application launch information. Cloud server 20 determines that this is the first time the specific application has been launched because the number of times the application has been launched is "0 times."

[0085] Step S5: Cloud server 20 transmits display instruction information for a tutorial screen. That is, if cloud server 20 determines that this is the first time that a specific application has been launched (if it is determined that this is the first time that the application has been launched), it transmits display instruction information for a tutorial screen. Note that if cloud server 20 determines that this is not the first time that a specific application has been launched (if it is determined that this is the second or subsequent time that the application has been launched), it transmits display instruction information for a menu screen (step S31 in FIG. 12).

[0086] Step S6: The mobile terminal 60 receives the instruction to display the tutorial screen. Step S7: The mobile terminal 60 displays a tutorial screen. That is, the mobile terminal 60 displays the tutorial screen based on an instruction (tutorial screen display instruction information) from the cloud server 20 (FIGS. 6(A) to 6(C)). Note that the screen information on the tutorial screen (the same applies to screen information on other screens displayed by the mobile terminal 60) is stored in the mobile terminal 60 as part of a specific application or information associated with a specific application. Step S8: The mobile terminal 60 accepts an operation to instruct the member to start the service. For example, the mobile terminal 60 accepts an operation of the service start button BT604 on the tutorial screen shown in FIG. Step S9: The mobile terminal 60 transmits service start instruction information for notifying (reporting) that an operation to instruct the start of a service has been performed. The service start instruction information includes the member identification information.

[0087] Step S10: The cloud server 20 receives the service start instruction information. Step S11: Cloud server 20 transmits display instruction information for a menu screen. That is, when cloud server 20 receives service start instruction information, it transmits display instruction information for a menu screen. As described above, cloud server 20 also transmits display instruction information for a menu screen when it determines that this is not the first time that a specific application has been launched (when it determines that the application has been launched for the second or subsequent time) (step S31 in FIG. 12). Step S12: Cloud server 20 updates the number of times the application is launched. Specifically, cloud server 20 adds 1 to the number of times the application is launched corresponding to the member identification information (updates it from "0 (times)" to "1 (times)"). Cloud server 20 further stores the current date and time as the first application launch date and time and the previous application launch date and time corresponding to the member identification information.

[0088] Step S13: The mobile terminal 60 receives the menu screen display instruction information. Step S14: The mobile terminal 60 displays a menu screen instead of the tutorial screen (deletes the tutorial screen). That is, the mobile terminal 60 displays the menu screen based on an instruction from the cloud server 20 (information instructing the display of the menu screen) (FIG. 6(D)). Note that the mobile terminal 60 may obtain information to be displayed on the menu screen (e.g., the number of points) from the cloud server 20 and display it on the menu screen.

[0089] Fig. 12 is a sequence diagram showing an example of the processing of the mobile terminal 60 and the cloud server 20. Specifically, Fig. 12 shows an example of the processing of the mobile terminal 60 and the cloud server 20 from when the mobile terminal 60 launches a specific application to when it displays a menu screen. It is assumed that this is not the first time that 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 Fig. 12, it is assumed that the member record information (Fig. 3(B)) stored in the cloud server 20 stores a value other than "0 (times)" as the number of times the application has been launched, which corresponds to the member identification information of the member using the mobile terminal 60.

[0090] Step S21: The mobile terminal 60 starts up a specific application based on the member's operation, similar to step S1 in FIG. Step S22: The mobile terminal 60 transmits application start information in the same manner as in step S2 of FIG.

[0091] Step S23: The cloud server 20 receives the application start-up information, similarly to step S3 in FIG. Step S24: Cloud server 20 determines that this is not the first time that the specific application has been launched. Specifically, cloud server 20 refers to the number of times that the application has been launched that corresponds to the member identification information included in the application launch information. Cloud server 20 determines that this is not the first time that the specific application has been launched because the number of times that the application has been launched is not "0 times."

[0092] Step S31: Cloud server 20 transmits display instruction information for a menu screen. That is, when cloud server 20 determines that this is not the first time that a specific application has been launched (when it determines that this is the second or subsequent launch), it transmits display instruction information for a menu screen. Note that when cloud server 20 determines that this is the first time that a specific application has been launched (when it determines that this is the first launch), it transmits display instruction information for a tutorial screen (step S5 in FIG. 11). Also, when cloud server 20 receives service start instruction information, it transmits display instruction information for a menu screen (step S11 in FIG. 11). Step S32: Cloud server 20 updates the number of times the application is started. Specifically, cloud server 20 adds 1 to the number of times the application is started that corresponds to the member identification information. Cloud server 20 further stores the current date and time as the date and time of the previous application start that corresponds to the member identification information.

[0093] Step S33: The mobile terminal 60 receives the display instruction information for the menu screen, similarly to step S13 in FIG. Step S34: The mobile terminal 60 displays the menu screen (FIG. 6(D)) in the same manner as in step S14 of Fig. 11. In this manner, when the specific application is launched for the second or subsequent time, the mobile terminal 60 displays the menu screen without displaying the tutorial screen.

[0094] Fig. 13 is a sequence diagram showing an example of the processing of the mobile terminal 60 and the cloud server 20. Specifically, Fig. 13 is a process following Fig. 11 or 12, and shows an example of the processing of the mobile terminal 60 and the cloud server 20 from when the mobile terminal 60 accepts an operation to start shopping to when it displays an initial registration screen. It is assumed that the mobile terminal 60 is displaying a menu screen at the start of the flowchart in Fig. 13.

[0095] Step S40: The mobile terminal 60 accepts an operation to start shopping. For example, the mobile terminal 60 accepts an operation of the Start Shopping button BT610 on the menu screen shown in FIG. Step S41: The mobile terminal 60 transmits shopping start instruction information that notifies (reports) that an operation to instruct the user to start shopping has been performed. The shopping start instruction information includes the member identification information.

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

[0097] Step S44: The cloud server 20 determines that the first product item has not yet been registered. For example, the cloud server 20 determines that the first product item has not yet been registered because the transaction information of the transaction does not store "Registration Information (Product 1)." Step S45: Cloud server 20 transmits display instruction information for an initial registration screen and transaction identification information for identifying the transaction. In other words, if cloud server 20 determines that one product item has not yet been registered, it transmits display instruction information for an initial registration screen and transaction identification information for identifying the transaction. Note that if cloud server 20 determines that one product item has already been registered, it transmits display instruction information for a registration screen (not the initial registration screen) (steps S53 and S63 in FIG. 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. When the transaction is completed (when the settlement at the settlement device 50 is completed), the mobile terminal 60 may erase the transaction identification information. 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 on top of the initial registration screen. That is, the mobile terminal 60 displays the initial registration screen based on an instruction from the cloud server 20 (display instruction information for the initial registration screen), and displays the product scan guide image GA624 on top of the initial registration screen (FIGS. 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 associated with a specific application, and display it on top of the initial registration screen. The mobile terminal 60 may also obtain the product scan guide image GA624 from the cloud server 20, and display it on top of the initial registration screen.

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

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

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

[0102] Step S56: The mobile terminal 60 receives display instruction information for a registration screen (not an initial registration screen). Step S57: The mobile terminal 60 displays the registration screen (updates the display contents). That is, the mobile terminal 60 displays the registration screen based on an instruction from the cloud server 20 (registration screen display instruction information) (FIGS. 8(A) to 8(C)). As shown in FIG. 8(A) to FIG. 8(C), the mobile terminal 60 does not display (deletes) the product scan guide image GA624 on the registration screen. Note that the mobile terminal 60 obtains information to be displayed on the registration screen (e.g., product name, price) from the cloud server 20 and displays it on the registration screen.

[0103] After step S57 (as well as step S67 described below), it is also possible to read the barcodes on the second and subsequent items (the second item, the third item, ...) (step S60), and it is also possible to accept an operation to proceed to checkout (operation of the Proceed to Checkout button BT626) (step S68).

[0104] Step S60: The mobile terminal 60 reads the barcodes attached to the second and subsequent products. Specifically, the mobile terminal 60 reads the barcodes by capturing an image of the barcodes attached to the products as shown in Fig. 8(D). The mobile terminal 60 obtains the product code of the product from the barcode. Step S61: As in step S51, the mobile terminal 60 transmits the transaction identification information of the transaction and the product code of the product.

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

[0106] Step S66: The mobile terminal 60 receives display instruction information for a registration screen (not an initial registration screen) in the same manner as in step S56. Step S67: The mobile terminal 60 displays the registration screen (updates the display contents) in the same manner as in step S57. That is, the product scan guide image GA624 is not displayed (remains hidden).

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

[0108] Figure 15 is a sequence diagram showing an example of the processing of the mobile terminal 60 and cloud server 20. Specifically, Figure 15 is a process following Figure 14, and shows an example of the processing of the mobile terminal 60 and cloud server 20 from when the mobile terminal 60 accepts an operation to proceed to checkout until the display of the two-dimensional code display screen for payment. It is assumed that at the start of the flowchart in Figure 15, the mobile terminal 60 has accepted an operation to proceed to checkout (operation of the Proceed to Checkout button BT626).

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

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

[0111] Step S73: The mobile terminal 60 receives the display instruction information for the settlement two-dimensional code display screen. Step S74: The mobile terminal 60 displays a settlement two-dimensional code display screen instead of the registration screen (deletes the registration screen). That is, the mobile terminal 60 displays the settlement two-dimensional code display screen based on an instruction from the cloud server 20 (display instruction information for the settlement two-dimensional code display screen) (FIGS. 9(D) to 10(B)). The mobile terminal 60 obtains information to be displayed on the settlement two-dimensional code display screen (for example, the settlement two-dimensional code GA631) from the cloud server 20 and displays it on the settlement two-dimensional code display screen.

[0112] Fig. 16 is a sequence diagram showing an example of the processing of the settlement device 50, cloud server 20, and mobile terminal 60. Specifically, Fig. 16 shows an example of the processing of the settlement device 50, cloud server 20, and mobile terminal 60 from when the settlement device 50 reads the settlement two-dimensional code GA631 until it displays a product list screen (until the mobile terminal 60 displays a screen indicating that the settlement two-dimensional code has been read). The left side of Fig. 16 shows the processing of the settlement 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 two-dimensional code GA631 displayed on the settlement two-dimensional code display screen by the mobile terminal 60. The settlement device 50 obtains transaction identification information that identifies the transaction information of the transaction from the settlement two-dimensional code GA631. Step S81: The settlement device 50 transmits transaction information request information for requesting transaction information of the transaction. The transaction information request information includes transaction identification information for identifying the transaction. Step S82: The cloud server 20 receives the transaction information request information.

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

[0115] Step S86: The cloud server 20 transmits display instruction information for a settlement two-dimensional code reading completion screen.

[0116] Step S87: The mobile terminal 60 receives the display instruction information for the settlement two-dimensional code reading completion screen. Step S88: The mobile terminal 60 displays a screen indicating that the two-dimensional code has been read for settlement instead of the screen indicating the two-dimensional code has been read for settlement (the screen indicating the two-dimensional code has been erased). That is, the mobile terminal 60 displays a screen indicating that the two-dimensional code has been read for settlement based on an instruction from the cloud server 20 (information indicating that the two-dimensional code has been read for settlement screen) (FIG. 10(C)).

[0117] The above describes the embodiment, but according to the embodiment, even beginners can easily use it. For example, since guide images (tutorial image GA601, product scan guide image GA624, and checkout two-dimensional code scan guide image GA633) are displayed as guidance (guide information) for guiding the procedure (operation, movement) of the mobile terminal 60, even beginners can easily operate the mobile terminal 60. Note that the image GA627 may also be one of the images for guiding the procedure.

[0118] In the above embodiment, the guidance (product scan guide image GA624) on the product registration method is displayed in the scene where the product is actually registered (FIG. 7). Since the guidance on the product registration method is displayed in the scene where the product is actually registered, the customer can learn the product registration method more efficiently than when the guidance is displayed in a scene where the product is not actually registered (for example, the tutorial screens shown in FIGS. 6(A) to 6(C) or the menu screen shown in FIG. 6(D)). In other words, since the guidance is not provided (presented) in advance but is provided at the appropriate time, the customer can practice (register the product) while watching the guidance and efficiently learn the product registration method. In addition, since the necessary information is presented at a good pace, the customer is less stressed. In this regard, if the guidance is provided in advance, the customer has to remember the contents of the guidance provided in advance until the necessary scene, or when the necessary scene occurs, the customer has to check the contents of the guidance provided in advance by performing an operation such as switching pages, which causes a lot of stress for the customer.

[0119] 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 (FIGS. 7 to 9). This allows the customer to comfortably register the product (realizing a comfortable shopping experience for the customer). In this regard, if the area for displaying the captured image and the area for displaying the product registration information are provided on one screen and the area for displaying the product registration information is provided on the other screen, rather than providing the area for displaying the captured image and the area for displaying the product registration information on the same screen, a screen transition occurs between the two screens automatically or based on the customer's intention (instruction) every time a product is registered. Whether the screen transition occurs automatically every time a product is registered or based on the customer's intention, the screen transition is likely to cause visual fatigue for the customer, and further, when the screen transition occurs based on the customer's intention, the customer is required to operate a button or the like, which is a burden or at least troublesome. In any case, this hinders a comfortable shopping experience to a certain extent. On the other hand, in the embodiment, an area for displaying a captured image and an area for displaying product registration information are provided on the same screen, so that the problems described above do not occur and a comfortable shopping experience can be achieved.

[0120] From the viewpoint of realizing a comfortable shopping experience, attention must be paid to information overload, which can lead to poor visibility and indigestion. If each guidance required for each scene in a series of steps is provided simultaneously in one scene, information overload will occur. Therefore, in the above embodiment, each guidance required for each scene is provided in each scene. In addition, the timing of erasing (or hiding) guidance that is no longer necessary is also important. In the above embodiment, the product scan guide image GA624 is erased immediately after scanning the product (FIG. 7(D)→FIG. 8(A)), or the product scan guide image GA624 is hidden from the second item onwards (FIG. 8(C)).

[0121] (Variations, etc.) Although the embodiment has been described above, the device configuration, data configuration, processing flow, display and output aspects, etc. can be appropriately changed, for example, as shown in the following (1), (2), .... In addition, the following (1), (2), ... may be appropriately combined with each other.

[0122] (1) In the above embodiment, an example was described in which the tutorial screen (tutorial image GA601) progresses based on an operation (operation of the next button BT603), but the tutorial screen may progress based on other conditions. For example, the tutorial screen may progress based on the passage of time, like the product scan guide image GA624 and the checkout two-dimensional code scan guide image GA633.

[0123] (2) In the above embodiment, an example was described in which the presence (necessity) of displaying the tutorial screen (tutorial image GA601, etc.) was determined based on whether or not a specific application was launched for the first time (first time), but the number of times to determine whether or not to display the tutorial screen is not limited to the first time. As an example, the tutorial screen may be displayed for the first three launches and not displayed for the fourth and subsequent launches.

[0124] (3) In the above embodiment, an example was described in which three types of tutorial images GA601 (images GA601a, GA601b, and GA601c) are displayed on the tutorial screen, but the types of tutorial images GA601 do not have to be three. That is, 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 in sequence on the tutorial screen.

[0125] (4) In the above embodiment, the amount of information provided (guided) when the tutorial screen is displayed is constant, but the amount of information provided may be different depending on the tutorial screen. For example, in relation to the above (2) and (3), depending on the conditions (how many times the application has been started, the attributes of the member, the purchase history, etc.), there may be a case where a normal number (e.g., three types) of tutorial images GA601 are used to explain the service at a normal level, a case where many (e.g., five types) of tutorial images GA601 are used to explain the service at a more detailed level than the normal level, or a case where a small number (e.g., one type) of tutorial images GA601 are used to explain the service at a more concise level than the normal level.

[0126] (5) In the above embodiment, in relation to whether or not the tutorial screen is displayed, an example has been described in which the time point at which the specific application is introduced (downloaded, etc.) is used as a reference (starting point) to determine whether or not the current start of the specific application is the first time. However, it may be determined whether or not the current start of the specific application is the first time based on another time point. For example, instead of or in addition to the time point at which the specific application is introduced, if a predetermined period (e.g., three months) has passed since the previous (previous) start without starting the specific application, it may be determined whether or not the current start of the specific application is the first time based on the time point at which the predetermined period has passed. In other words, if the specific application has been started in the past but has not been started for a while (if it has been started for the first time in a long time), a tutorial screen (tutorial image GA601, etc.) may be displayed. The same applies not only to the first time, but also to the second or subsequent times. For example, instead of or in addition to the time point at which the specific application is introduced or the time point at which the above-mentioned predetermined period has passed, if the specific application has been upgraded (e.g., a function has been added, the UI has been changed), it may be determined whether or not the current start of the specific application is the first time based on the time point at which the upgrade was performed.

[0127] (6) In the above embodiment, an example has been described in which it is determined whether or not to display a tutorial screen based on the start-up record of a specific app (specifically, the number of times the app is started in the past). However, a condition may be set for the start-up record of a specific app. For example, a condition may be set for the start-up time of a specific app. As an example, when a specific app is started at a predetermined time (for example, during the business hours of a store), the start-up may be counted as a start-up record, and when a specific app is started at a time other than the predetermined time, the start-up may not be counted as a start-up record. In addition, a condition may be set for the start-up location of a specific app. As an example, when a specific app is started at a predetermined location (for example, inside a store or within the store premises), the start-up may be counted as a start-up record, and when a specific app is started at a location other than the predetermined location, the start-up may not be counted as a start-up record. The start-up location may be determined by GPS. Also, if the mobile terminal 60 is connected to the wireless LAN of a certain store, it may be determined that the mobile terminal 60 is in a predetermined location. Note that the start-up may be counted as a start-up record only when the specific app is started at a predetermined time and in a predetermined location.

[0128] (7) In the above embodiment, an example was described in which it was determined whether or not to display the tutorial screen based on the launch history of a specific application (specifically, the number of times the application was launched in the past), but it may be determined whether or not to display the tutorial screen based on other conditions. For example, it may be determined whether or not to display the tutorial screen as in the following (a) to (c). (a) Whether or not to display the tutorial screen is determined based on the display history of the tutorial screen (for example, the number of times in the past that the image GA601a displayed first, and the number of times in the past that the image GA601b displayed last) . (b) Whether or not to display the tutorial screen is determined based on the reading record (number of times the barcode attached to the product has been read) or the registration record (number of registered products) of the product. (c) Whether or not to display the tutorial screen is determined based on the transaction completion record for service A (for example, the number of settlements completed at the settlement device 50).

[0129] (8) In the above embodiment, the screens displayed by the mobile terminal 60 on the display unit 305 are described as the tutorial screen (FIGS. 6(A) to 6(C)), the menu screen (FIG. 6(D)), the initial registration screen (FIGS. 7(A) to 7(D)), the registration screen (FIGS. 8(A) to 9(C)), the two-dimensional code display screen for settlement (FIGS. 9(D), 10(A), 10(B)), and the two-dimensional code reading completion screen for settlement (FIG. 10(C)). However, the screens displayed by the mobile terminal 60 are not limited to the above screens.

[0130] (Transaction completion screen) The mobile terminal 60 may display a transaction completion screen (not shown) to notify the completion of the transaction. For example, when the settlement process is completed (for example, when the receipt printed and issued by the printing unit 113 is removed), the settlement device 50 transmits information to the cloud server 20 that the settlement process is completed, and when the cloud server 20 receives the information that the settlement process is completed from the settlement device 50, it transmits display instruction information for the transaction completion screen to the mobile terminal 60, and when the mobile terminal 60 receives the instruction information from the cloud server 20, it may display the transaction completion screen. Note that the mobile terminal 60 may display an image (animation, slide) on the transaction completion screen (same for the status confirmation screen) like other screens.

[0131] In a mode in which the transaction completion screen is not displayed (i.e., in a mode in which the final display in a transaction is the settlement two-dimensional code reading completion screen), the mobile terminal 60 may display, on the settlement two-dimensional code reading completion screen, a message indicating that the operation by the mobile terminal 60 has ended or that the role of the mobile terminal 60 in the transaction has been completed. For example, the mobile terminal 60 may display, on the settlement two-dimensional code reading completion screen, a message such as "Thank you. The operation on the mobile terminal 60 has been completed, so you may put it away. Subsequent transactions will be carried out by the settlement device. Please settle the payment at the settlement device." The mobile terminal 60 may transition from the settlement two-dimensional code reading completion screen to a menu screen. For example, the mobile terminal 60 may display a message such as "Operation on the mobile terminal 60 is complete. Return to the menu screen. Subsequent transactions will be performed at the settlement device. Please settle at the settlement device" on the settlement two-dimensional code reading completion screen instead of the above-mentioned message, and automatically transition from the settlement two-dimensional code reading completion screen to the menu screen after a predetermined time has passed. Also, for example, instead of the above-mentioned message, the settlement two-dimensional code reading completion screen may display a message such as "Operation on the mobile terminal 60 is complete. Do you want to return to the menu screen?", and a button may be provided to confirm whether or not to return to the menu screen, and when the button to return is operated, the settlement two-dimensional code reading completion screen may transition to the menu screen.

[0132] In a mode in which a transaction completion screen is displayed (i.e., a mode in which the final display in a transaction is the transaction completion screen), the mobile terminal 60 may display, on the settlement two-dimensional code reading completion screen, a message indicating that the operation by the mobile terminal 60 has ended and that the completion of the transaction will be notified separately after the transaction is completed, and may display, on the transaction completion screen, a message indicating that the role of the mobile terminal 60 in the transaction has been completed, including confirmation of the completion of the transaction (settlement completion). For example, the mobile terminal 60 may display, on the settlement two-dimensional code reading completion screen, a message such as "Thank you. The operation on the mobile terminal 60 has been completed. The transaction will be carried out by the settlement device from now on. Please settle the transaction at the settlement device. A message will be displayed after the transaction is completed," and may display, on the transaction completion screen, a message such as "The transaction has been completed, so you may put it away." Note that the mobile terminal 60 may transition from the transaction completion screen to a menu screen. For example, the mobile terminal 60 may display a message such as "The transaction is complete. Return to the menu screen" on the transaction completion screen instead of the above-mentioned message, and automatically transition from the transaction completion screen to the menu screen after a predetermined time has passed. Also, for example, the transaction completion screen may display a message such as "The transaction is complete. Return to the menu screen" on the transaction completion screen instead of the above-mentioned message, and a button may be provided to confirm whether or not to return to the menu screen, and when the button to return is operated, the transaction completion screen may transition to the menu screen.

[0133] The portable 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 settlement device"). For example, the portable terminal 60 may display a message indicating that settlement is in progress at the settlement device 50 on the settlement two-dimensional code reading completion screen during the period from when the portable terminal 60 receives display instruction information for a settlement two-dimensional code reading completion screen (FIG. 16) until when the portable terminal 60 receives display instruction information for a transaction completion screen.

[0134] Instead of or in addition to the mobile terminal 60 displaying that settlement is in progress at the settlement device 50, the settlement device 50 itself may display that settlement is in progress. For example, the settlement device 50 may display a message (which may be an animation or slide) such as "Settlement processing will begin with this device. Please put away your mobile terminal" on the condition that the settlement device 50 reads the settlement two-dimensional code GA631. This gives the customer an opportunity to put away the mobile terminal 60.

[0135] The settlement device 50 may also display that settlement has been completed. For example, the settlement device 50 may display a message (which may be an animation or a slide) such as "Settlement processing has been completed" on the condition that the change or receipt has been removed (detection of removal of change, detection of removal of receipt, etc.). In a mode 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 a slide) such as "Settlement processing has been completed. The mobile terminal 60 will also be notified of the completion of the transaction."

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

[0137] That is, the settlement device 50 can use different messages depending on whether the mobile terminal 60 is a customer mobile terminal or a store mobile terminal. By storing information for identifying the store mobile terminal (for example, a contractor unique ID or a MAC address) in a location accessible by the settlement device 50 (which may be in the settlement device itself or in another device), the settlement device 50 may identify whether the mobile terminal 60 being used (used to register the product) is a customer mobile terminal or a store mobile terminal.

[0138] As described above, necessary messages (guidance) are displayed on both the mobile terminal 60 and the settlement device 50, so the customer can concentrate on one device (terminal) to perform operations. In other words, the customer does not need to pay attention to both devices (terminals), and the burden on the customer is reduced. This leads to a reduction in processing time (payment time, etc.), and enables efficient operation for the store.

[0139] (Status check screen) The mobile terminal 60 may display a status check screen (not shown) for checking the status. Although it has been described that the mobile terminal 60 may include a motion determination unit, for example, the mobile terminal 60 may display the status check screen when there is no motion and no operation for a predetermined period of time. The status check screen may display a message encouraging an action (for example, registering a product, canceling 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), and the tutorial screen may be displayed in the specified language. The same applies to the languages ​​of the menu screen, the registration screen (including the initial registration screen and the product scan guide image GA624), the two-dimensional code display screen for payment, the two-dimensional code reading completion screen for payment, the transaction completion screen, and the status confirmation screen.

[0141] (10) In the above embodiment, 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 an operation in the same manner as the tutorial screen (tutorial image GA601).

[0142] (11) In the above embodiment, an example was described in which three types of product scan guide images GA624 (image GA624a, image GA624b, and image GA624c) are displayed on the initial registration screen, but the types of product scan guide images GA624 do not have to be three. 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 in sequence 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, and the product scan guide image GA624 is not displayed 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 reading (item) in the transaction. However, the number of times to determine whether or not to display the product scan guide image GA624 is not limited to the first reading (item). As an example, the product scan guide image GA624 may be displayed up to the third reading (item), and not displayed from the fourth reading (item) onwards.

[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. That is, in the above embodiment, an example was described in which the product scan guide image GA624 is always displayed when the first (item) is read in the transaction. However, there may be cases in which the product scan guide image GA624 is not displayed when the first (item) is read in the transaction. For example, it may be determined whether or not to display the product scan guide image GA624 as follows (a) to (c). (a) Whether or not to display the product scan guide image GA624 is determined based on whether or not the current transaction is the first time (first time) that a specific application is started. In other words, it is displayed only the first time. (b) Whether or not to display the product scan guide image GA624 is determined based on the reading record (number of times read) of the barcode attached to the product or the registration record (number of registered products) of the product. In other words, it is displayed only when the record does not reach a predetermined number (number of products). (c) Whether or not to display the product scan guide image GA624 is determined based on the transaction completion record for service A (for example, the number of settlements completed at the settlement device 50). In other words, it is displayed only when the record does not reach a predetermined number of times.

[0145] (14) In the above embodiment, an example was described in which the commodity scan guide image GA624 is displayed at a position that straddles 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) on the initial registration screen. Specifically, an example was described in which the commodity scan guide image GA624 is displayed such that the upper part of the commodity scan guide image GA624 is positioned in front of the area below the barcode reading area of ​​the captured image display area HR621, and the remaining part of the commodity scan guide image GA624 is positioned in front of the area excluding the lower area of ​​the registration information display area HR622 (FIGS. 7(A) to 7(C)). However, the display mode of the commodity scan guide image GA624 is not limited to this. For example, the commodity scan guide image GA624 may be displayed as shown in the following (a) and (b). (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 FIG. 7(A) etc., the entire product scan guide image GA624 is displayed in front of the captured image display area HR621 (area excluding the barcode reading area (e.g., area below the barcode reading area)). Note that the position of the barcode reading area in the captured image display area HR621 may be higher than in the example shown in FIG. 7(A) etc. Also, the captured image display area HR621 may be wider (the registration information display area HR622 may be narrower) than in the example shown in FIG. 7(A) etc. (b) 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 (i.e., a part of the product scan guide image GA624 is also displayed in front of the related information display area HR633). For example, 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 by making the product scan guide image GA624 larger than the example shown in Fig. 7(A) or by making the related information display area HR633 wider than the example shown in Fig. 7(A).

[0146] (15) In the above embodiment, the registration screen (including the initial registration screen) is configured by providing the captured image display area HR621, the registration information display area HR622, and the related information display area HR633, but 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) A captured image display area HR621 and a registration information display area HR622 are provided on the registration screen (no related information display area HR633 is provided). In this configuration, a button may be provided on the registration screen, and information that would be displayed in the related information display area HR633 based on the operation of the button 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 (without the registration information display area HR622 or the related information display area HR633). In this configuration, when a barcode is read, the registration information may be displayed as a separate screen in the registration information display area HR622. The screen with only the captured image display area HR621 may be referred to as a first registration screen, and the separate screen (the screen displaying the registration information as displayed in the registration information display area HR622) may be referred to as a second registration screen. For example, the mobile terminal 60 may switch from the first registration screen to the second registration screen in response to the reading of a barcode, and switch from the second registration screen to the first registration screen in response to an operation. The mobile terminal 60 may switch from the first registration screen to the second registration screen in response to an operation instead of or in addition to the reading of a barcode.

[0147] (16) In the above embodiment, an example was described in which the registration screen (including the initial registration screen) is configured with the captured image display area HR621, the registration information display area HR622, and the 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, when a 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 captured image display area HR621 in the above embodiment), the entire display area of ​​the display unit 305 (the captured image 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 the present embodiment, the lower part of the registration screen may be considered to be in a state in which the through image on the back side is hidden by the registration information display area HR622 and the related information display area HR633 on the front side.

[0148] (17) In the above embodiment, the two-dimensional code display screen for settlement (two-dimensional code scan guide image for settlement GA633) is advanced based on the passage of time, but the initial registration screen may be advanced based on other conditions. For example, the two-dimensional code display screen for settlement may be advanced based on the operation in the same way as the tutorial screen (tutorial image GA601).

[0149] (18) In the above embodiment, an example was described in which three types of product scan guide images GA624 (image GA633a, image GA633b, image GA633c) are displayed on the checkout two-dimensional code display screen, but the types of checkout two-dimensional code scan guide images GA633 do not have to be three. In other words, one type of checkout two-dimensional code scan guide image GA633 may always be displayed on the checkout two-dimensional code display screen, or two or four or more types of checkout two-dimensional code scan guide images GA633 may be displayed in sequence on the checkout two-dimensional code display screen.

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

[0151] (20) This is related to (19) above, but in the case of a mobile terminal 60 with a long and narrow display unit 305 (an aspect ratio (vertical:horizontal) of, for example, 21:9), even if the settlement two-dimensional code scan guide image GA633 is displayed below the settlement two-dimensional code GA631, the distance between the top of the settlement two-dimensional code display screen and the top of the settlement two-dimensional code GA631 may be long. Therefore, in the case of a mobile terminal 60 with a long and narrow display unit 305, the settlement two-dimensional code GA631 may be arranged so as to be close to the top of the settlement two-dimensional code display screen, thereby shortening the above-mentioned distance. In other words, the layout of the settlement two-dimensional code display screen may be made different depending on the type of mobile terminal 60 so that the member can easily have the settlement device 50 read the settlement two-dimensional code GA631 regardless of the model (type) of the mobile terminal 60. Specifically, the thinner the mobile terminal 60 is, the more the position of the settlement two-dimensional code scan guide image GA633 on the settlement two-dimensional code display screen may be shifted to the upper side.

[0152] (21) In the above embodiment, it was explained that the mobile terminal 60 may be equipped with a motion determination unit, but when the settlement two-dimensional code display screen is displayed, for example, rotation of the settlement two-dimensional code display screen (changing between portrait and landscape screen) using an acceleration sensor (gyro sensor) may be prohibited (i.e., always display in portrait screen as shown in FIG. 9(D) etc. regardless of movement). This prevents the settlement two-dimensional code display screen from rotating unnecessarily, allowing the member to have the settlement device 50 read the settlement two-dimensional code GA631 without difficulty. Note that the acceleration sensor may be prohibited from rotating the screen (not limited to the settlement two-dimensional code display screen; the entire screen) on the condition that the application (specific app) is started.

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

[0154] (23) Although not displayed in the above embodiment, a clerk call button may be displayed on the settlement two-dimensional code display screen. The clerk call button may be displayed, for example, below the settlement two-dimensional code GA631 (for example, between the settlement two-dimensional code scan guide image GA633 and the Return to Shopping button BT639, or below the Return to Shopping button BT639). When the clerk call button is operated, the clerk may be able to identify the mobile terminal 60 related to the clerk call. For example, the mobile terminal 60 may transmit clerk call information (including member identification information, etc.) based on the operation of the clerk call button, and the terminal carried by the clerk or the transaction status management device 40 may receive the clerk call information (for example, via the cloud server 20 or the headquarters server 10) and identify the mobile terminal 60 related to the clerk call (the mobile terminal 60 may transmit the location information). The mobile terminal 60 may always display the store clerk call button on the checkout two-dimensional code display screen, or may display the store clerk call button when a predetermined time (e.g., 30 seconds) has elapsed after the start of the checkout two-dimensional code display screen (or after the Proceed to Checkout button BT626 located on the registration screen is operated) (the button may be displayed in an inoperable manner before the predetermined time has elapsed and displayed in an operable manner after the time has elapsed).

[0155] (24) In the above embodiment, the cloud server 20 generates the two-dimensional settlement code GA631, but the mobile terminal 60 may generate it. That is, when the mobile terminal 60 receives an operation to declare that the registration of the product is completed and that the user wishes to proceed to checkout (operation of the Proceed to Checkout button BT626 on the registration screen), the mobile terminal 60 may generate the two-dimensional settlement code GA631 based on the transaction identification information. Note that a device other than the cloud server 20 and the mobile terminal 60 may generate the two-dimensional settlement code GA631 based on a request from the mobile terminal 60.

[0156] (25) In the above embodiment, an example has been described in which cloud server 20 determines whether or not a specific application is launched for the first time (first time), but mobile terminal 60 may make the determination. For example, when a specific application is launched, mobile terminal 60 may inquire of cloud server 20 about the number of times the application has been launched (obtain number information) and determine whether or not the current launch is the first launch. Also, for example, mobile terminal 60 itself may store (hold) the number of times the application has been launched, and when a specific application is launched, mobile terminal 60 may refer to the number of times the application has been launched that it has stored and determine whether or not the current launch is the first launch.

[0157] (26) In the above embodiment, an example has been described in which the mobile terminal 60 displays the tutorial screen based on an instruction from the cloud server 20 (tutorial screen display instruction information), but the mobile terminal 60 may display the tutorial screen based on its own judgment (control). For example, which is also related to (25) above, the mobile terminal 60 may determine whether the current startup of a specific app is the first startup or not, and display the tutorial screen if it is determined that the current startup is the first startup.

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

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

[0160] (29) In the above embodiment, an example was described in which it was determined whether or not to display the initial registration screen (product scan guide image GA624) based on whether or not one product item has already been registered, but it may be determined based on other conditions. For example, it may be determined as in the following (a) and (b). (a) When the cloud server 20 receives shopping start instruction information (step S42 in FIG. 13), it decides to display the initial registration screen (product scan guide image GA624). When the cloud server 20 receives a product code or the like (steps S52, S62 in FIG. 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 shopping start button BT610 on the menu screen) (step S40 in FIG. 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 and S60 in FIG. 14), it decides not to display the initial registration screen (product scan guide image GA624) (it decides to simply display the registration screen). The above (a) is a mode in which the mobile terminal 60 displays the initial registration screen (product scan guide image GA624) or the registration screen based on an instruction from the cloud server 20. The above (b) is a mode in which the mobile terminal 60 displays the initial registration screen (product scan guide image GA624) or the registration screen based on its own judgment.

[0161] (30) In the above embodiment, an example was described in which the mobile terminal 60 displayed the two-dimensional code display screen for settlement based on instructions from the cloud server 20 (display instruction information for the two-dimensional code display screen for settlement), but the mobile terminal 60 may display the two-dimensional code display screen for settlement based on its own judgment (control). For example, the mobile terminal 60 may determine whether or not it has accepted an operation to declare that the registration of the product has been completed and that the user wishes to 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 two-dimensional code display screen for settlement instead of the registration screen.

[0162] (31) In the above embodiment, the mobile terminal 60 stores screen information and displays a screen based on the screen information stored therein. However, the mobile terminal 60 may not 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, a tutorial screen will be described. The process shown in steps S5 to S7 of FIG. 11 may operate as follows. The cloud server 20 generates screen information of the tutorial screen and transmits 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, an initial registration screen will be described. The process shown in steps S45 to S47 of FIG. 13 may operate as follows. The cloud server 20 generates screen information of the initial registration screen (product information, etc., is empty) and transmits 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 the screen information received from the cloud server 20, and displays the product scan guide image GA624 on top of the initial registration screen. Screens such as the tutorial screen and the registration screen may be web pages provided by the cloud server 20 and browsed by the mobile terminal 60. The format of the image such as the product scan guide image GA624 is not important, and may be, for example, GIF (animated GIF). The image may be played (displayed) after downloading, or may be played during downloading (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 FIG. 11), the initial registration screen (product scan guide image GA624) is erased when the registration screen is displayed (step S57 in FIG. 14), and the payment two-dimensional code display screen (payment two-dimensional code scan guide image GA633) is erased when the payment two-dimensional code reading completion screen is displayed (step S88 in FIG. 16). That is, in the above embodiment, an example was described in which the guide images (tutorial image GA601, product scan guide image GA624, payment two-dimensional code scan guide image GA633) are erased from the screen as a mode in which the need for guidance is no longer necessary or has weakened. However, the mode in which the need for guidance is no longer necessary or has weakened may be such that guidance is substantially stopped, and is not limited to the mode in which the guide image is erased. For example, instead of erasing the guide image, the guide image may be displayed in a small size (for example, displayed as an icon). Also, instead of or in addition to displaying the guide image in a small size, the guide image may be displayed in an inconspicuous position.

[0164] (33) In the above embodiment, an example was described in which the mobile terminal 60 was attached to a shopping cart and used, but the mobile terminal 60 does not have to be attached to a shopping cart when used. For example, the mobile terminal 60 may be used while being held in the hand. Note that some images (e.g., image GA601b in FIG. 6(B) and image GA624a in FIG. 7(A)) are images suited to the manner in which the mobile terminal 60 is used while attached to a shopping cart, and therefore, when the mobile terminal 60 is used while being held in the hand, an image suited to the manner in which the mobile terminal is used while being held in the hand is used.

[0165] (34) In the above embodiment, the mobile terminal 60 has been mainly described as being owned by the customer (customer mobile terminal), but as mentioned above, it may be a loaned item (store mobile terminal) loaned by the store to the customer. By storing information (e.g., a subscriber unique ID or a MAC address) that identifies the mobile terminal 60 (store mobile terminal) loaned by the store, it may be possible to distinguish whether the mobile terminal 60 being used or used is a store mobile terminal (i.e., whether it is a customer mobile terminal or a store mobile terminal). In the case of a store mobile terminal, it may be possible to request input of a membership number and determine whether it is the first time it is activated or the second or subsequent time it is activated.

[0166] (35) In the above embodiment, the customer registers the product using the mobile terminal 60. However, the mobile terminal 60 is not limited to the mobile terminal 60, as long as the mobile terminal is a mobile (portable) device capable of registering the product at the display location. For example, the product may be registered using a tablet terminal (owned or loaned) or a shopping cart with a display unit (or a display unit detachable from the shopping cart). That is, the shopping cart (a shopping cart with a display unit or a display unit detachable from the shopping cart) may display a tutorial screen (FIG. 6(A) to FIG. 6(C)), a menu screen (FIG. 6(D)), an initial registration screen (FIG. 7(A) to FIG. 7(D)), a registration screen (FIG. 8(A) to FIG. 9(C)), a two-dimensional code display screen for payment (FIG. 9(D), FIG. 10(A), FIG. 10(B)), a two-dimensional code read completion screen for payment (FIG. 10(C)), a transaction completion screen (not shown), and a status confirmation screen (not shown). The above-mentioned shopping cart (a shopping cart having a display unit or a detachable display unit) may have a configuration similar to that of the mobile terminal 60 (the configuration shown in FIG. 4) (each component of the configuration may be detachable).

[0167] The shopping cart (shopping cart with a display unit or a detachable display unit) may be equipped with an electronic tag recognition unit that recognizes information on an electronic tag (hereinafter referred to as an electronic tag recognition cart). The shopping cart (which may be an electronic tag recognition cart) may be equipped with a battery (a battery that serves as a power source for the display unit or the display unit) and may be charged (hereinafter referred to as a charging cart). The charging cart is charged, for example, at a cart collection point (a place where at least one of lending and returning of shopping carts is performed). For example, a charging device (charging equipment) may be installed at the cart collection point, and the charging cart may be charged by the charging device. The charging method (method) 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 charging cart to charge it. At the cart collection point, the same number of cables or the like as the number of charging carts that can be stored (the maximum number of waiting carts before lending) are prepared (if storage positions are set, they are prepared in a line at each storage position). In the case of non-contact charging, for example, a non-contact charging system (power supply (transmission) unit, power receiving (reception) unit) is provided on both the charging cart side and the cart accumulation point (charging facility) side, and the power transmitted from the power supply unit on the cart accumulation point side is received by the power receiving unit on the charging cart side to charge the cart. As in the case of contact charging, the cart accumulation point may be provided with the same number of power supply units as the number of charging carts that can be stored, and the power supply and reception units may be arranged in pairs, or a large power supply unit that can transmit power to multiple charging carts (power receiving units) may be provided collectively. Note that, at the cart accumulation point, the removal and return of charging carts, charging of charging carts (contact charging, non-contact charging), etc. may be performed by store staff or by customers (at the request of the store). When charging is entrusted to customers (entrusted), the store staff may periodically check the charging status (whether charging is being performed correctly, etc.).

[0168] In the case of a shopping cart that does not have a battery (a shopping cart that is not a charging cart; it may be an electronic tag recognition cart), charging of the display unit or display may be performed on the display unit or display. Unlike a shopping cart with a detachable display, when a shopping cart with a non-detachable display unit is charged on the display unit, it can also be understood that charging is performed on a part of the shopping cart (the display unit), and therefore a shopping cart with a display unit that is charged may be called a "charging cart".

[0169] When the customer is entrusted with returning the charging cart, the customer may be notified of the return. For example, the charging cart (the charging cart program) may display guidance (guidance information) regarding the return on the display unit (or display device) on the condition that the settlement device 50 has handed over the transaction information (the settlement device 50 has read the settlement two-dimensional code GA631) or the settlement has been completed at the settlement device 50. As an example, the charging cart may display guidance on the return to the cart collection point on the display unit (or display device) on the settlement two-dimensional code reading completion screen ( FIG. 10(C) ) or the transaction completion screen (not shown). The above guidance may include map information (floor information) indicating the return destination (cart collection point). The same applies to a shopping cart (which may be an electronic tag recognition cart) that does not have a battery with regard to the return.

[0170] When charging the charging cart is left to the customer, information regarding charging may be communicated to the customer. For example, the charging cart (the charging cart program) may display guidance (guidance information) regarding charging on the display unit (or display device) on the condition that the transaction information has been handed over to the settlement device 50 or the settlement has been completed at the settlement device 50. As one example, the charging cart may display guidance regarding a method of connecting cables, etc., or guidance regarding a method of contactless charging on the display unit (or display device) on a settlement two-dimensional code reading completion screen or a transaction completion screen.

[0171] The guidance regarding the method of connecting cables or the like may be, for example, guidance on one or more of the following (a) to (c). (a) Available cables, etc. For example, the first (closest) unused cable among multiple cables, etc. prepared at the cart collection point (b) How to connect cables, etc. For example, where on the charging cart is the port for the cable, the direction of insertion, and the depth. (c) Confirmation that cables, etc. are connected correctly (charging has started). For example, the cart device displays on the screen that power is being supplied. Or, the cart device is equipped with a light-emitting unit (LED) that notifies the user that power is being supplied, and the light-emitting unit displays that power is being supplied. In addition, as related to (c) above, the cart collection point may be provided with LEDs corresponding to the cables, etc. (for example, provided on each cable, etc.) so that it is possible to confirm that power is being supplied.

[0172] The guidance regarding the contactless charging method may be, for example, one or more of the following (a) to (c). (a) Available parking areas. For example, the first (closest) unused parking area among 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) in the stopping area. (c) Confirm that the vehicle is parked in an appropriate location (that charging has started) (similar to the guidance on how to connect cables, etc.) In relation to (b) above, since there is no physical connection in the case of contactless power supply, for example, an illustration of a "△" or the like may be drawn on the power supply unit, and an illustration of a "▽" or the like corresponding to the "△" on the power supply unit may be drawn on the power receiving unit, and instructions may be given on the display unit (or display device) to stop the vehicle so that the vertices of the "▽" and "△" overlap. Since the actual illustration is also displayed on the screen, the customer can intuitively grasp the stopping position.

[0173] The same applies to the case where the mobile terminal 60 is not owned by the customer (customer mobile terminal) but is a loaned item (store mobile terminal, loaned mobile terminal) loaned by the store to the customer. As an operation of the loaned mobile terminal 60, it is assumed that the return is entrusted to the customer. In the case where the return of the loaned mobile terminal 60 is entrusted to the customer, guidance on how to return the loaned mobile terminal 60 may be displayed, for example, on a settlement two-dimensional code reading completion screen or a transaction completion screen, as in the case where the return of the charging cart is entrusted to the customer. The above guidance may include map information (floor information) indicating the return destination (return location, return device, etc. of the loaned mobile terminal 60). In addition, as an operation of the loaned mobile terminal 60, in the case where the charging of the loaned mobile terminal 60 is entrusted to the customer, guidance on how to charge the loaned mobile terminal 60 may be displayed, for example, on a settlement two-dimensional code reading completion screen or a transaction completion screen, as in the case where the charging of the charging cart is entrusted to the customer. The guidance may include operation information indicating a charging method (such as a method of operating the charging device that is the return device).

[0174] By displaying the above-mentioned guidance (guidance information), store staff can reduce the burden of cumbersome work such as collecting and charging charging carts and portable rental devices, making it possible to operate the store with a smaller number of staff.

[0175] (36) In the above embodiment, the transaction status management device 40 has been described as a device that mainly manages (monitors and controls) each device in the LAN 19, but the transaction status management device 40 may also manage (monitors and controls) cart collection points, etc. In other words, the transaction status management device 40 may be capable of communicating with devices installed at the cart collection points or the shopping carts themselves present at the cart collection points, and may display, for example, the number of shopping carts (whether they are electronic tag recognition carts or charging carts) present at the cart collection point (the number of waiting carts if the cart collection point is a rental / return point or a rental point) on a management screen. In addition, if the shopping carts are charging carts, the transaction status management device 40 may display, on a management screen, the charging status (battery remaining amount, etc.) of each charging cart at the cart collection point, the number of charging carts available for rental (charging carts with a battery remaining amount equal to or greater than a reference value), etc. The transaction status management device 40 may display the charging status of the charging carts in the store (on loan) on a management screen instead of or in addition to the charging status of each charging cart at the cart collection point. In this case, the charging cart may transmit information about the remaining battery level to the transaction status management device 40 by wireless communication. The transaction status management device 40 may also manage (monitor, control) the return location (return device, charging device) of the loaned mobile terminal 60 in a similar manner.

[0176] (37) The transaction status management device 40 may display operation history information of each device. For example, the transaction status management device 40 may display operation history information of each device in the LAN 19, the mobile terminal 60 (including a loaned mobile terminal 60), and the shopping cart (which may be an electronic tag recognition cart or a charging cart). The operation history includes, for example, the start time of use, the registration time of each product, the registration completion time, the start time of payment, the end time of payment, the completion time of the transaction, the loan time if the mobile terminal 60 is a loaned item, the return time, information on screen transitions, information on operations (including changes to the registered quantity of products, etc.), product registration information, etc. The operation history information includes history information on operations of a transaction after completion, as well as history information on operations of a transaction before completion (currently in progress) (operations up to the present of the transaction). Therefore, a store clerk (a monitoring store clerk) can check, for example, by the transaction status management device 40, on which screen a certain mobile terminal 60 (a certain customer) has been staying and for how long.

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

[0178] According to the above (37) and (38), for example, a store clerk can use the transaction status management device 40 to estimate the situation (such as a situation in which the customer is in trouble) of each customer (each device) and provide suitable guidance to customers who need it by remote operation. In other words, it is possible to efficiently support (guide) multiple customers at a predetermined location (one location if there is only one transaction status management device 40). The transaction status management device 40 may transmit map information (floor information) that clearly indicates the location of the service counter and the location of the transaction status management device 40 to a customer (device) who needs it as guidance (or separately from the guidance) to guide the customer. The mobile terminal 60, etc. may display map information based on the customer's operation (for example, operation of a help button, etc.) so that the customer can confirm the location of the service counter, etc., regardless of whether the information is transmitted or not. The mobile terminal 60, etc. may store map information and display the stored map information based on the customer's operation, or 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 or the like may notify the transaction status management device 40 that a help button or the like has been operated.

[0179] <Overview of the embodiment> [Technical field] The present invention relates to a program and a product sales data processing device. [Background technology] A self-service system has been proposed in which customers themselves can register products using a mobile terminal. Meanwhile, a system that displays guidance about a product that is the subject of an image capture is also known (see, for example, Patent Document 1). [Prior art document] [Patent documents] [Patent Document 1] JP 2015-53030 A [Summary of the Invention] [Problem to be solved by the invention] However, there are some customers who are not familiar with the self-service system described above. Such a system cannot support such customers. The present invention has been made in consideration of the above circumstances, and has an object to provide a technology that allows even a beginner to easily use a service using a mobile terminal. [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.), the program causing the computer to function as an imaging means (e.g., the imaging unit 316) that captures an image of a product to be purchased, a guidance means that guides an operator through a procedure using guide images that guide the operator through the procedure (e.g., a tutorial image GA601, a product scan guide image GA624, a two-dimensional code scan guide image for checkout GA633, an image GA627), and a display means (e.g., the display unit 305) that can display images captured by the imaging means, the display means displaying part or all of a first guide image (e.g., a product scan guide image GA624), which is one of the guide images, in an image display area (e.g., an image display area HR621) for displaying the captured images, and the guidance means terminating the guidance using the first guide image based on a predetermined condition (e.g., the registration of one product item). The program in (1) is easy to use even for beginners.

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

[0182] (3) The program described in (1) or (2) causes the computer to function as an operation receiving means (e.g., a Proceed to Checkout button BT626) capable of receiving an operation to proceed to checkout, the operation receiving means not receiving the operation before the guidance using the first guide image ends (see FIG. 7(D)), and receiving the operation after the guidance using the first guide image ends (see FIG. 8(A)). (3) The program can be easily used even by beginners.

[0183] (4) The display means is capable of displaying a settlement code (e.g., a settlement two-dimensional code GA631) for settling the purchase of a product, and when the settlement code is displayed, a second guide image (e.g., a settlement two-dimensional code scan guide image GA633) different from the first guide image (e.g., a product scan guide image GA624) is displayed below the settlement code, which is a program described in any of (1)1 to (3). (4) The program can be easily used even by beginners.

[0184] (5) The program described in any of (1) to (4) is characterized in that the guide image is displayed on a mobile terminal (e.g., mobile terminal 60) used by a customer who purchases a product, and the guidance means varies the manner of guidance using the guide image (e.g., tutorial image GA601) based on the number of times the customer uses the mobile terminal (e.g., the number of times it is started up). According to the program (5), the guide image can be displayed preferably.

[0185] (6) A product sales data processing device (e.g., a mobile terminal 60, a shopping cart, etc.) comprising: an imaging means for imaging a product to be purchased; a guidance means for guiding an operator through a procedure using a guidance image guiding the operator through the procedure; 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 image capture image display area for displaying the image; and the guidance means terminates the guidance using the first guidance image based on a predetermined condition. (6) The product sales data processing device can be easily used even by beginners.

[0186] (7) 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.), the program causing the computer to function as an imaging means for capturing images of products and a display means for displaying a guide image that guides an operator through a procedure, the display means displaying a part or all of the guide image superimposed on an image captured by the imaging means (see Figure 7 (D)), and the guidance through the guide image is terminated based on a predetermined condition. (7) The program can be easily used even by beginners.

[0187] In addition, a program (for example, a specific application in the case of the mobile terminal 60, etc.) for implementing the functions of each of the above-described devices (headquarters server 10, store controller 30, transaction status management device 40, settlement device 50, registered settlement device 51, mobile terminal 60, shopping cart, etc.) may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be read into a computer system and executed to process each of the above devices. Here, "reading a program recorded on a recording medium into a computer system and executing it" includes installing the program into a computer system. The "computer system" here includes hardware such as an OS and peripheral devices. In addition, the "computer system" may include multiple computer devices connected via a network including a communication line such as the Internet, a WAN, a LAN, or a dedicated line. In addition, the "computer-readable recording medium" refers to a portable medium such as a flexible disk, an optical magnetic disk, a ROM, a CD-ROM, etc., and a storage device such as a hard disk built into a computer system. In this way, the recording medium storing the program may be a non-transient recording medium such as a CD-ROM. In addition, the recording medium also includes a recording medium provided inside or outside and accessible from a distribution server to distribute the program. The code of the program stored in the recording medium of the distribution server may be different from the code of the program in a format executable by the terminal device. In other words, the format in which the program is stored in the distribution server does not matter as long as it can be downloaded from the distribution server and installed in a format executable by the terminal device. The program may be divided into multiple parts, downloaded at different times, and then combined on the terminal device, or each of the divided programs may be distributed by a different distribution server. Furthermore, the "computer-readable recording medium" includes a memory that holds a program for a certain period of time, such as a volatile memory (RAM) inside a computer system that becomes a server or a client when a program is transmitted via a network. The above program may also be for realizing part of the above-mentioned functions.Furthermore, the above-mentioned functions may be realized in combination with a program already recorded in the computer system, that is, a so-called differential file (differential program). [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 causes a computer to function as a product sales data processing device, The computer, Imaging means for imaging the product; a display means capable of displaying an image captured by the imaging means; a registration means for registering the product imaged by the imaging means; Function as a The display means includes: A guide image for guiding the procedure can be displayed to guide the operator through the procedure; A first guide image, which is one of the guide images, is displayed to guide the user on a method for registering the product, and the guidance on the registration method is terminated when the product is registered by the registration means. A program characterized by:

2. The display means includes: When the guidance on the registration method is completed, detailed information of the product registered by the registration means is displayed.

2. The program according to claim 1 .

3. The display means When the guidance on the registration method is completed, a second guide image, which is one of the guide images, is displayed to guide the user to proceed to checkout.

3. The program according to claim 1 or 2.

4. The display means The manner of guidance using the guidance image is varied based on the number of times the operator has used the product sales data processing device.

4. The program according to claim 1, wherein the program is a program for executing a program for executing a program.

5. An imaging means for imaging a product; a display means capable of displaying an image captured by the imaging means; a registration means for registering a commodity imaged by the imaging means; Equipped with The display means includes: A guide image for guiding the procedure can be displayed to guide the operator through the procedure; A first guide image, which is one of the guide images, is displayed to guide the user on a method for registering the product, and the guidance on the registration method is terminated when the product is registered by the registration means. A product sales data processing device comprising:

Images