JP7634867B2 - Portable terminal and program - Google Patents

Description

The present invention relates to a portable terminal and a program.

There is known technology that uses a gyro sensor or the like built into a portable terminal to determine whether the mobile terminal (portable terminal) used by a customer to register products when shopping is attached to a shopping cart or held in the hand (see, for example, Patent Document 1).

JP 2020-129337 A

As described above, when a customer changes the way they hold a portable terminal, it may become difficult to see or operate the screen displayed on the portable terminal.

The present invention was made in consideration of these circumstances, and aims to display a screen that is easy for customers to use depending on changes in the holding state of the portable terminal.

One aspect of the present invention that solves the above-mentioned problems is a portable terminal that includes a display means, a product registration means for registering products, and a display control means for changing the display mode of the display means depending on whether the portable terminal is in a first holding state in which the portable terminal is held by hand, or a second holding state in which the portable terminal is held by a holding means provided on a mobile object.

1 is a diagram illustrating an example of the overall configuration of a product sales data processing system according to an embodiment of the present invention. 1 is a diagram showing an example of the state near the entrance/exit of a store in which a product sales data processing system according to an embodiment of the present invention has been introduced. 1A to 1C are diagrams illustrating examples of how a mobile terminal is set in a shopping cart according to an embodiment of the present invention. FIG. 2 is a diagram illustrating a settlement device according to the present embodiment. FIG. 2 is a diagram illustrating an example of the configuration of a mobile terminal according to the present embodiment. FIG. 2 is a diagram illustrating an example of the configuration of a transaction management device according to the present embodiment. 5A to 5C are diagrams illustrating an example of customer information, store information, and cart information according to the embodiment. FIG. 2 is an explanatory diagram illustrating classification of reserved products according to the embodiment. A sequence diagram showing an example of processing procedures executed by a mobile terminal, a settlement device, and a transaction management device according to this embodiment in response to the accounting of one transaction in self-service operation. 11A to 11C are diagrams showing examples of a start-up screen, a product registration initial screen, a product registration update screen, and a code screen according to the present embodiment. 13A and 13B are diagrams illustrating examples of a product registration result area in the present embodiment. FIG. 13 is a diagram showing an example of a product registration change screen corresponding to a hand-held state in the present embodiment. FIG. 13 is a diagram showing an example of a product registration change screen corresponding to a cart holding state in the present embodiment. FIG. 13 is a diagram showing an example of a product registration result area in a modified example of the present embodiment. 10 is a flowchart illustrating an example of a processing procedure executed by the mobile terminal in the present embodiment in relation to displaying a product registration screen. FIG. 13 is a diagram showing an example of a code screen in a first modified example of the embodiment. A figure showing an example of how products sold by weight are displayed in a store relating to a second modified example of this embodiment. FIG. 13 is a diagram showing an example of a pricing operation screen in a second modified example of the embodiment. FIG. 13 is a diagram showing an example of a pricing operation screen in a second modified example of the embodiment. FIG. 11 is a diagram showing an example of a product registration screen in a second modified example of the embodiment.

<Embodiment>
[Example of overall configuration of product sales data processing system]
FIG. 1 shows an example of the overall configuration of a product sales data processing system 1 according to this embodiment.
The product sales data processing system 1 in the figure includes a store controller 10, a transaction management device 20 (cloud server), a registration settlement device 30, a settlement device 40, a transaction status management device 50 (e.g., a personal computer, etc.), and a mobile terminal 60.
The product sales data processing system 1 in the figure can be introduced into various stores (supermarkets, convenience stores, drug stores, home centers, home appliance retailers, etc.).

In addition, although one registered settlement device 30 is illustrated in the figure, the number of registered settlement devices 30 installed in one store may be two or more. Also, although two settlement devices 40 are illustrated in the figure, the number of settlement devices 40 in one store may be one or three or more. Also, although one transaction status management device 50 is illustrated in the figure, the number of transaction status management devices 50 in one store may be two or more. Also, there may be two or more store controllers 10 in one store.

The product sales data processing system 1 in the figure is capable of handling both a store clerk-assisted operation in which a store clerk uses a registration and settlement device 30 to register products, and a self-service operation in which a customer registers products using a mobile terminal 60 and then uses a settlement device 40 to settle the payment.
In the following explanation, self-operation will be mainly described.

The store controller 10, the registration settlement device 30, the settlement device 40, and the transaction status management device 50 are installed in the store. The store controller 10, the registration settlement device 30, the settlement device 40, and the transaction status management device 50 are connected to each other so as to be able to communicate with each other via a LAN 19 (which may be wired or wireless). The store controller 10 is capable of communicating with the transaction management device 20.

The store controller 10 is a device that mainly manages various devices installed in a store. For example, the store controller 10 has a communication function with external devices, and receives product files (product masters) from external devices (e.g., a headquarters server not shown, which may be the transaction management device 20) and supplies them to the registered settlement device 30, etc., and receives transaction information from the settlement device 40, etc. and transmits it to the external device (e.g., the transaction management device 20, etc.).

The transaction management device 20 is a server that provides various services. For example, the transaction management device 20 manages various information corresponding to self-operation (e.g., transaction information (cart information), etc.).

The registration and settlement device 30 is a device that executes the registration process and the settlement process. The registration and settlement device 30 is used by a store clerk (the registration process and the settlement process are executed by the operation of the store clerk).

The settlement device 40 is a device that executes settlement processing. The settlement device 40 is used by a customer. That is, the settlement device 40 executes settlement processing in response to operations by the customer.
In addition, when the payment includes items whose processing is temporarily suspended for confirmation by a store clerk (hereinafter referred to as "pending items"; details will be described later), a store clerk will be called and the store clerk (or the customer) will operate the payment device 40 to confirm the pending items.

The transaction status management device 50 is a device that mainly manages (or monitors) various devices within the LAN 19. The transaction status management device 50 manages the operating status of other devices (e.g., the registered settlement device 30, the settlement device 40, etc.), by displaying various information on the other devices and outputting various commands to the other devices.

The mobile terminal 60 is a terminal used by the customer when registering products in a self-service environment. The mobile terminal 60 is used while being held in a holder of the shopping cart 70, or while being removed from the holder of the shopping cart 70 and held in the customer's hand.

The mobile terminal 60 has a communication function, an imaging function (camera), and also a recognition function that recognizes various codes (barcodes, two-dimensional codes, etc.). For example, the mobile terminal 60 recognizes the barcode attached to a product. In other words, the mobile terminal 60 reads product identification information (product code). The mobile terminal 60 may also extract feature points in an image captured by the imaging function (an image acquired as a through image) and recognize objects (various codes).

The mobile terminal 60 is a smartphone or the like owned by the customer. The mobile terminal 60 may be owned by the store and loaned to the customer when shopping. Although two mobile terminals 60 are shown in the figure, the number of mobile terminals 60 used for product registration in the store varies depending on the number of customers.

A shopping application having a function for registering products in accordance with the self-service operation of this embodiment is installed on the mobile terminal 60.

Figure 2 shows an example of the state near the entrance of a store that has introduced the product sales data processing system 1 of this embodiment. As shown in Figure 2, near the entrance (or the entrance if the entrance and exit are separate), a rental shopping cart 70, a rental shopping basket 80, and a sale shopping bag 90 are prepared. When a customer visits the store, they place the shopping basket 80 in the shopping cart 70, place the shopping bag 90 in the shopping basket 80, etc., and proceed inside the store. At this time, if the customer wishes to do their own shopping, they place the mobile terminal 60 in the shopping cart 70.

The customer may bring the shopping bag 90 that they purchased this time as their own bag the next time they visit the store, or may bring a different bag from the shopping bag 90 as their own bag. They may also purchase a plastic bag.

Although not shown in the figure, the shopping cart 70 is equipped with a bag for reserved items (described below) in addition to the shopping basket 80.

[Example of setting a mobile terminal in a shopping cart]
An example of how the mobile terminal 60 is set (attached) to the shopping cart 70 will be described with reference to Fig. 3. Fig. 3(A) is a side view of the portion of the shopping cart 70 where the mobile terminal 60 is set. Fig. 3(B) is a top view of the shopping cart 70.

As shown in FIG. 3(A), a holder 71 for setting the mobile terminal 60 is attached to the shopping cart 70. The customer sets the mobile terminal 60 in the holder 71. When the mobile terminal 60 is set in the holder 71, as shown in FIG. 3(B), it is in a state where an image of the entire shopping bag 90 or my bag can be captured by the imaging unit 606 (see FIG. 4(B)).

The holder 71 may also be provided with a rechargeable battery for charging the mobile terminal 60. The rechargeable battery is provided with, for example, a charging cable. Multiple charging cables may be provided to accommodate different standards for the connector shapes of the mobile terminals 60. This allows the customer to keep the mobile terminal 60 connected to the rechargeable battery and charging when the customer sets the mobile terminal 60 in the holder 71, eliminating the need to worry about the remaining battery power inside the mobile terminal 60.

[About the payment device]
Fig. 4 is a diagram for explaining the settlement device 40. Fig. 4(A) is a diagram showing an example of the appearance of the settlement device 40 (a front view seen from the customer side). Fig. 4(B) is a diagram showing an example of the configuration of the settlement device 40. In Fig. 4(A) and Fig. 4(B), the same parts are given the same reference numerals.

Below, an example of the configuration of the settlement device 40 shown in FIG. 4(B) will be described with reference to FIG. 4(A). The settlement device 40 comprises a CPU 401, a ROM 402, a RAM 403, a hard disk 404, a display unit 405, a scanner unit 406, a card payment unit 408, a change dispenser 409, a printing unit 413, an audio output unit 414, a communication unit 415, and an imaging unit 416 (camera). These can communicate with each other via a bus. The settlement device 40 may further comprise a key operation unit and an alarm unit (for example, a lamp on a sign pole, etc.).

The CPU 401 is a central processing unit, and controls the operation of the settlement device 40 by reading and executing programs stored in the ROM 402 .
The ROM 402 is a read-only memory, and stores various types of information used by the CPU 401, including programs.

RAM 403 is a read/write memory, and stores various information as a main storage device. For example, RAM 403 stores information read from ROM 402 or hard disk 404, information acquired from the outside, information generated during processing, etc.

The hard disk 404 stores various information as an auxiliary storage device. For example, the hard disk 404 may store programs executed by the CPU 401 instead of the ROM 402. Also, instead of the RAM 403, the hard disk 404 may store information read from the ROM 402, information obtained from the outside, information generated during processing, etc. Note that a storage device such as an SSD (Solid State Drive) may be provided instead of the hard disk 404.

The display unit 405 is a touch panel that displays various information and accepts operations performed on the touch panel.

The scanner unit 406 optically reads various information. For example, the scanner unit 406 scans a code (barcode, two-dimensional code, etc.) displayed on the display unit of the mobile terminal 60 and reads information necessary for the settlement process. The scanner unit 406 may also scan a code printed on an accounting ticket (registered trademark) issued by another device (for example, a registered settlement device 30) and reads information necessary for the settlement process. The scanner unit 406 may also scan a code attached to a product and read the product code. The scanner unit 406 may also scan a code attached to a store clerk's name tag and read the store clerk code.

The card payment unit 408 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 408 is equipped with a card recognition unit (reading unit), a display unit, and an operation unit, but it is sufficient that it is equipped with at least the card recognition unit. The card recognition unit may recognize various cards (e.g., point cards, membership cards, shareholder cards, etc.) for the purpose of granting benefits, discounts, etc.

The change dispenser 409 (cash settlement unit) is a cash settlement mechanism that 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.).

The printing unit 413 prints and issues various media (receipts, bills, etc.).
The audio output unit 414 outputs audio. For example, the audio output unit 414 outputs audio guidance and the like.
The communication unit 415 transmits and receives information between other devices (the store controller 10, the registered settlement device 30, the other settlement devices 40, the transaction status management device 50, etc.).

The imaging unit 416 is configured to capture, for example, an image of the hands of a customer operating the change machine.

[Registered payment device]
The registration and settlement device 30 may be configured to have a display unit and a scanner unit on each side (clerk side, customer side) and a settlement unit (card settlement unit, cash settlement unit) on one side (customer side). The registration and settlement device 30 configured in this manner may be a device that can be switched to any of a plurality of operation modes (a mode in which the registration process is executed by the operation of the clerk and the settlement process is executed by the operation of the customer, a mode in which the registration process is executed by the operation of the clerk and the customer and the settlement process is executed by the operation of the customer, etc.) depending on, for example, the operating status. Also, if the mode in which the settlement process is executed by the operation of the customer, the registration and settlement device 30 can be used for self-operation. That is, the customer can make a transaction by having the mobile terminal 60 execute the registration process and have the registration and settlement device 30 execute the settlement process.
In the following description, an example will be given in which the registration settlement device 30 is used for self-service operation.

[Example of mobile terminal configuration]
5 shows an example of the configuration of the portable terminal 60. The portable terminal 60 in the figure includes a CPU 601, a storage unit 602, a RAM 603, a display unit 604, an operation unit 605, an imaging unit 606, a network-compatible communication unit 607, and a sensor unit 608.

The CPU 601 is a central processing unit that controls the operation of the mobile terminal 60 by reading and executing programs stored in the storage unit 602 .
The storage unit 602 is an auxiliary storage device for the CPU 601, and stores various types of information used by the CPU 601, including programs.
The RAM 603 is a main storage device for the CPU 601 .

The display unit 604 displays an image according to the display control of the CPU 601. The display unit 604 may be configured as a touch panel that allows operations to be performed on the screen.
The operation unit 605 collectively indicates various operators provided on the mobile terminal 60 and various input devices connected to the mobile terminal 60 .

The imaging unit 606 captures images under the control of the CPU 401. In addition, the imaging unit 606 in this embodiment can also function as a part that reads two-dimensional codes in a code reader that processes two-dimensional codes.

The network-compatible communication unit 607 is a part that communicates wirelessly via a network. The network-compatible communication unit 607 enables the mobile terminal 60 to communicate with the transaction management device 20.

The sensor unit 608 collectively indicates various sensors equipped in the mobile terminal 60. The sensor unit 608 may include a motion sensor for detecting a motion state such as the attitude and traveling direction of the mobile terminal 60. The motion sensor may be configured to include a gyro sensor, an acceleration sensor, and the like.
The sensor unit 608 may also include a positioning sensor that detects its own position using a positioning device compatible with GPS, for example.

[Example of transaction management device configuration]
6 shows an example of the configuration of transaction management device 20. Transaction management device 20 in the figure includes a CPU 201, a storage unit 202, a RAM 203, and a network-compatible communication unit 204.
The CPU 201 is a central processing unit that controls the operation of the transaction management device 20 by reading and executing programs stored in the memory unit 202 .
The storage unit 202 is an auxiliary storage device for the CPU 201, and stores various types of information used by the CPU 201, including programs.
The RAM 203 is a main storage device for the CPU 201 .
The network-compatible communication unit 204 is a part that performs communication via a network.

The memory unit 202 of the transaction management device 20 stores customer information, store information, and cart information.

[Information stored in the transaction management device]
The customer information stored in the memory unit 202 is information for managing individual customers. The transaction management device 20 generates customer information when a customer is registered (a customer may be considered to have been registered when the customer information of that customer is stored). The transaction management device 20 also updates the customer information as appropriate based on cart information, etc. The transaction management device 20 may refer to the cart information at a specified time every day, for example, and update the customer information.

7A shows an example of customer information stored in the memory unit 202 of the transaction management device 20. The customer information in the figure includes customer identification information, customer name, customer registration date, product cancellation information, customer rank, number of points, etc.
The customer identification information is identification information that uniquely identifies a customer.
As the customer identification information (or instead of the customer identification information), for example, application identification information that is uniquely (e.g., sequentially) assigned to each installed shopping application may be used. Also, as the customer identification information (or instead of the customer identification information), terminal identification information unique to the mobile terminal 60 in which the shopping application is installed may be used. The terminal identification information may be hardware identification information uniquely assigned to the hardware of the mobile terminal 60, such as a telephone number assigned to a customer who is a user of the mobile terminal 60, or a MAC (Media Access Control) address.
The customer name is the customer's name or nickname, etc. The customer registration date is the date and time when the customer was registered. Product cancellation information is information regarding cancellation of a product after it has been registered. The customer rank is a rank according to the customer's purchasing history. When generating customer information for a new customer, the customer identification information, customer name, and customer registration date are generated, but since this is before the start of actual trading (product registration), other information (product cancellation information, etc.) is not generated.

The transaction management device 20 generates and stores customer identification information, for example, when a customer is registered (for example, when the mobile terminal 60 downloads or installs a shopping application from an external device (for example, a specified server that provides general applications, the transaction management device 20) to use a shopping service provided by the transaction management device 20). In addition, the transaction management device 20 acquires information entered into the name field of a registration form (input form) using the mobile terminal 60, for example, when a customer is registered, and stores it as the customer name. In addition, the transaction management device 20 acquires the current date and time when the customer is registered, and stores it as the customer registration date.

In addition, instead of or in addition to storing the customer information in its own memory, the transaction management device 20 may store some or all of the customer information in another device (such as a file server accessible to the transaction management device 20).

7B shows an example of store information stored in the memory unit 202 of the transaction management device 20. The store information in the figure includes store identification information, store name (branch name), store specific information 1, and store specific information 2.
The store identification information is identification information that uniquely identifies a store. The store identification information shown in Fig. 7B is composed of a store (trade name) or company code and a branch code.
The store name is the name of the store. The store name shown in Fig. 7B is composed of the store (trade name) or company and the branch name.
The store identification information 1 is information on a two-dimensional code (QR code (registered trademark) or the like) for identifying a store in which a transaction takes place (a store where goods are bought and sold).
The store identification information 2 is store location information (GPS information) for identifying the store where the transaction is to be carried out.
In the example shown in FIG. 7B, the store identification information and the store specifying information 1 are different, but the store identification information and the store specifying information 1 may be the same.

The transaction management device 20 may obtain and store store information from an external source (such as a server (not shown) at a headquarters that oversees each store). Also, instead of or in addition to storing the store information in its own memory, the transaction management device 20 may store some or all of the store information in another device (such as a file server accessible by the transaction management device 20).

The cart information is information for managing individual transactions. The transaction management device 20 generates the cart information at the start of a transaction. In addition, the transaction management device 20 updates the cart information as the transaction progresses (each time a product is registered) (it may be considered that a product has been registered when the product is stored in the cart information).

FIG. 7(C) is an example of cart information stored in the memory unit 202 of the transaction management device 20.
The cart information in FIG. 1 includes cart identification information, transaction start date and time, transaction end date and time, customer identification information, registered product information, and reserved product information.

The cart identification information is identification information that uniquely identifies the cart information, and includes, for example, store identification information, a date, and a serial number (for example, a serial number for each store and date).
The transaction start date and time is the date and time when the transaction starts. The transaction start date and time may be, for example, the date and time when the cart information is generated. The transaction start date and time may be the registration date and time of the first item of product (the date and time when the registered product information (registered product 1) in FIG. 7(C) is stored). The date and time when the cart information is generated and the registration date and time of the first item of product may both be stored separately.

The transaction end date and time is the end date and time of the transaction. For example, the transaction start date and time may be the settlement date and time. The customer identification information is customer identification information that identifies the customer of the transaction. When the cart information is generated, the cart identification information, transaction start date and time, and customer identification information are generated, but since this is before the start of the actual transaction (product registration), other information (transaction end date and time, etc.) is not generated. The settlement date and time may be the settlement start date and time or the settlement end date and time. Both the settlement start date and time and the settlement end date and time may be stored separately as the transaction end date and time.

Registered product information (total) is information that is updated each time a product is registered. Registered product information (total) includes the number of products (number of products), estimated subtotal amount (e.g., subtotal amount before discounts, etc. are reflected), subtotal amount, etc. Registered product information (registered product 1) is the registration information for one product item. Registered product information (registered product 2) is the registration information for two products. In the example shown in Figure 7 (C), registered product information (registered product 3) to registered product information (registered product 5) are omitted from the illustration. Registered product information (registered product N; N is an integer) includes the product code, product name (product name), price, etc.

The registered product information (N) may include the registration date and time of the Nth item of product. In other words, the transaction management device 20 may store the registration date and time of the registered product as the registered product information. The registration date and time of each product may also be used as a basis for determining whether or not to apply a service such as a time service and the effect of applying the service.

The reserved item information (total) is information that is updated each time a reserved item is registered. The reserved item information (total) includes the number of reserved items (items) of all types and the number of reserved items (items) of each type. In this embodiment, the reserved items are classified into multiple types, and each classification is managed by classification number (reserved major classification number, reserved minor classification number) (details are explained in Figure 8). In the example of Figure 7 (C), "Total number of items: 3" in the reserved item information (total) indicates that the number of items in all types (total of reserved items with reserved major classification numbers "1" to "4") is 3, "NON-FILE: 2" indicates that the number of reserved items classified as NON-FILE (total of reserved items with reserved major classification number "1") is 2, and "Read NG: 1" indicates that the number of reserved items classified as read NG (total of reserved items with reserved major classification number "2") is 1.

A NON-FILE means that the barcode or product code was successfully scanned at the store (the product code was read), but the product code has not been stored (registered) in the product file. In other words, reserved products classified as NON-FILE are reserved products whose product code was successfully scanned, but whose product code has not been stored in the product file.

A "no read" means that the store was unable to successfully read (scan) the product code. In other words, a reserved product classified as a "no read" is one for which the product code could not be successfully read.

Pending product information (pending product 1) is information on pending product item 1. Pending product information (pending product 2) is information on pending product item 2. Pending product information (pending product 3) is information on pending product item 3.

The reserved product information (reserved product N; N is an integer) includes a reserved major classification number (described below). For example, if the Nth item is a reserved product classified as a NON-FILE with a reserved major classification number of "1", the reserved product information (reserved product N) includes the reserved major classification number "1 (NON-FILE)" and a product code. Also, if the Nth item is a reserved product classified as a read NG with a reserved major classification number of "2", the reserved product information (reserved product N) includes the reserved major classification number "2 (read NG)" and image data (image captured by the mobile terminal 60). Note that the reserved product information for reserved products classified as NON-FILE may include image data in addition to the reserved major classification number "1 (NON-FILE)" and the product code.

Note that the information shown in FIG. 7 is an example of information stored by the transaction management device 20, and the transaction management device 20 may store other information (e.g., a product file). Information about one product in a product file may include, for example, a product code (product identifier), product name, price, etc.

Figure 8 is an explanatory diagram explaining the classification of reserved items according to this embodiment. As shown in Figure 8, in this embodiment, reserved items are classified into major categories (classification by reserved major category number) and minor categories (classification by reserved minor category number). Note that the devices in the product sales data processing system 1 may be able to refer to information such as that shown in Figure 8 (such as a file showing the relationship between reserved major category numbers and reserved minor category numbers).

As shown in FIG. 8, in this embodiment, reserved items are classified into four major categories, with reserved major category numbers "1" to "4."

Reserved products classified under reserve category number "1" are NON-FILE reserved products. As described above, NON-FILE reserved products are reserved products whose product code has been successfully scanned, but whose product code has not been stored in the product file. In other words, if a product code has been successfully scanned, but the product code has not been stored in the product file, the reserved product is classified under reserve category number "1." Reserved products classified under reserve category number "1" are not specific to the product type and the price, etc., is unknown, so confirmation by a store clerk is required at the time of payment.

In FIG. 8, "NON-FILE" in "1 (NON-FILE)" is the classification name of the reserved item (major reserved classification name). The same applies to "Read NG" in "2 (Read NG)", "Specific item" in "3 (Specific item)", and "Cancelled item" in "4 (Cancelled item)" described below.

In this embodiment, reserved minor category number "11" exists as a subordinate (lower) minor category of reserved major category number "1". Since there is only one reserved minor category under reserved major category number "1", reserved minor category number "11", all reserved products classified under reserved major category number "1" are classified under reserved minor category number "11".

In FIG. 8, "NON-FILE" in "11 (NON-FILE)" is the category name of the reserved product (reserved subcategory name). The same applies to "Pseudo scan (coated, etc.)" in "21 (Pseudo scan (coated, etc.)")" and "Pseudo scan (short time)" in "22 (Pseudo scan (short time)")" which will be described later.

In addition, in Figure 8, a read operation "Yes" indicates that a read operation was performed, a read operation "No" indicates that a read operation was not performed, a read success/failure "Success" indicates that the read operation was successful, a read success/failure "Failure" indicates that the read operation failed, and a read success/failure "-" indicates that the read operation was not performed, so the problem is prior to the success or failure of the read.

Reserved items classified under reserve category number "2" are reserved items that could not be read. As described above, reserved items that could not be read are reserved items whose product codes could not be read successfully. In other words, when an item is placed on hold because the product code could not be read successfully, the item is classified under reserve category number "2." Reserved items classified under reserve category number "2" have an unknown price and are also susceptible to fraudulent manipulation, so they require confirmation by a store clerk at the time of payment.

In this embodiment, reserved minor category numbers "21", "22", "23", and "24" exist as minor categories under the major category of reserved major category number "2". Reserve minor category number "21" is reserved product with "pseudo scan (covered, etc.)". Reserve minor category number "22" is reserved product with "pseudo scan (short time)". Reserve minor category number "23" is reserved product with "bad barcode". Reserve minor category number "24" is reserved product with "non-scanned input".

A reserved item with reserved subcategory number "21" (pseudo scan (covered, etc.)) is, for example, a reserved item for which a reading operation was performed (the item was held over), that is, the item was placed within the imaging range of the imaging unit 606 (more specifically, the readable range of the barcode), but the barcode of the item was not captured (captured within the readable range) (because only parts other than the barcode of the item are captured within the readable range), so the item could not be read; a reserved item for which the barcode of the item was captured but part of the barcode was covered, for example by a finger, so the item could not be read; or a reserved item for which the barcode of the item was captured but the imaging angle of the barcode was inappropriate, so the item could not be read.

A reserved product with reserved subcategory number "22" (pseudo scan (short time)) is, for example, a reserved product whose barcode was imaged but could not be read because the barcode moved (including passing by) too quickly to be read.

A reserved product with reserved subcategory number "23" (defective barcode) is, for example, a reserved product whose barcode was imaged but could not be read due to wrinkles, fading, dirt, reflections, etc. in the printed portion of the barcode.

A reserved item with a reserved subcategory number of "24" (non-scanned entry) is, for example, a reserved item that could not be read because it was placed in the shopping cart 80 without the product being scanned (without being held over the cart).

Pending products with reserved subcategory numbers "21" to "24" (i.e. pending products with reserved major category number "2") may be referred to as unreadable products. Also, a situation resulting in pending products with reserved subcategory numbers "21" to "24" may be referred to as a unreadable situation (or simply "unreadable").

The reserved items with reserved subcategory number "21" (pseudo scan (covered, etc.)), reserved items with reserved subcategory number "22" (pseudo scan (short time)), and reserved items with reserved subcategory number "23" (bad barcode) have in common that they are all reserved items for which a reading operation was performed but the reading was unsuccessful. However, the reserved items with reserved subcategory number "21" (pseudo scan (covered, etc.)) and reserved items with reserved subcategory number "22" (pseudo scan (short time)) are considered to have less of an intention to successfully read the item than the reserved item with reserved subcategory number "23" (bad barcode). In other words, the reserved items with reserved subcategory number "21" (pseudo scan (covered, etc.)) and reserved items with reserved subcategory number "22" (pseudo scan (short time)) can also be said to be pseudo reading operations (fake reading operations), and are therefore referred to as pseudo-scanned (fake scan) reserved items.

Pending items classified under the reserve category number "3" are specific items (described below). Specific items are pending items that have been successfully registered, but because they are specific items, they require the assistance of a store clerk when checking out. In other words, when a pending item becomes a pending item because it is a specific item, it is classified under the reserve category number "3". Pending items classified under the reserve category number "3" are specific items, and therefore require the assistance of a store clerk when checking out.

In this embodiment, reserved minor category numbers "31," "32," and "33" exist as minor categories under the reserved major category number "3." Reserve minor category number "31" is a reserved product for "age verification products." Reserve minor category number "32" is a reserved product for "pharmaceuticals." Reserve minor category number "33" is a reserved product for "anti-theft tags."

Reserved items with reservation subcategory number "31" (age verification items) are reserved items such as alcohol and tobacco, which require a store clerk to verify the customer's age before selling them.

"Reserved products with reservation subcategory number 32 (pharmaceuticals)" are reserved products that require, for example, a licensed person such as a pharmacist to explain the product to the customer.

A reserved item with reservation subcategory number "33" (item with security tag) is, for example, a reserved item that has a security tag attached and therefore requires a store clerk to remove the security tag from the item at the time of sale.

Reserved items classified under reserve category number "4" are canceled reserved items. Cancelled reserved items are reserved items that were successfully registered, but whose registration was cancelled after registration. In other words, if a product becomes reserved because its registration was cancelled after it was registered, the reserved item is classified under reserve category number "4". Reserved items classified under reserve category number "4" are cancelled items (i.e. items that will not be purchased) and will not be taken out of the store, so confirmation by a store clerk is required when making the payment.

In this embodiment, reserved minor category number "41" exists as a minor category under reserved major category number "4". Since reserved major category number "4" has only one reserved minor category under reserved minor category number "41", all reserved products classified under reserved major category number "4" are classified under reserved minor category number "41".

In the above explanation, it is assumed that the reading operation has been performed for reserved items with reserved subcategory number "31" (age verification items), but if the reading operation is not performed, the reserved item will be classified as reserved item with reserved subcategory number "24" (non-scanned input). The same applies to reserved items with reserved subcategory number "32" (pharmaceuticals), reserved items with reserved subcategory number "33" (anti-theft tag items), and reserved items with reserved subcategory number "41" (cancelled items).

In the above explanation, it is assumed that a reading operation is performed on reserved items with reserved subcategory number "31" (age verification items) and that the reading is successful. However, if a reading operation is performed and the reading fails, the reserved item will be classified as either a reserved item with reserved subcategory number "21" (pseudo scan (covered, etc.)), a reserved item with reserved subcategory number "22" (pseudo scan (short time)), or a reserved item with reserved subcategory number "23" (bad barcode). The same applies to reserved items with reserved subcategory number "32" (pharmaceuticals), reserved items with reserved subcategory number "33" (anti-theft tag items), and reserved items with reserved subcategory number "41" (cancelled items).

As shown in FIG. 8, the reserved major category number and the reserved minor category number are in a higher-order and lower-order relationship, but one or both may be used depending on the situation. For example, in the cart information shown in FIG. 7(C), an example is described in which the reserved major category number is stored in the reserved product information, but the reserved minor category number may be stored instead of or in addition to the reserved major category number.

In addition, instead of or in addition to storing the cart information in its own memory, the transaction management device 20 may store some or all of the cart information in another device (such as a file server accessible to the transaction management device 20).

[Example of basic processing procedure for self-operation]
The sequence diagram in Fig. 9 shows an example of a processing procedure executed by the mobile terminal 60, the settlement device 40, and the transaction management device 20 in response to a transaction in a self-service operation. Specifically, the processing in Fig. 9 shows an example of the processing of the mobile terminal 60, the settlement device 40, and the transaction management device 20 from when a customer registers a product to be purchased from among products displayed in the store, until the settlement for the registered product is completed.

Step S1: The mobile terminal 60 acquires information that identifies the store (store identification information). For example, a two-dimensional code for identifying the store may be displayed near the entrance of the store (the two-dimensional code may be output to a display screen, a medium with the two-dimensional code printed on it may be attached, etc.), and a customer visiting the store may scan (read) the two-dimensional code with the mobile terminal 60, thereby causing the mobile terminal 60 to acquire the store identification information. When a customer visiting the store starts a shopping application, a screen instructing the customer to scan the two-dimensional code may be displayed as a start-up screen, or when a customer visiting the store scans the two-dimensional code with the mobile terminal 60, the shopping application may start and a screen informing the customer that they are currently connected to the transaction management device 20 may be displayed as a start-up screen.

For example, since a store is identified by its location, a customer who visits the store may obtain location information (GPS information) on the mobile terminal 60 at the store (i.e., the store's location information may be obtained as store identification information). When a customer who visits the store starts a shopping application, the location information may be obtained and a screen may be displayed as a startup screen informing the customer that the application is currently connected to the transaction management device 20. If multiple stores are detected from the location information and it is not possible to identify one, a selection screen may be displayed to allow the customer to select. Alternatively, the application may switch to a mode that forcibly obtains a two-dimensional code.

10A shows an example of a start-up screen of a shopping application displayed on the display unit 504 of the mobile terminal 60. The start-up screen in the figure displays the name of the store. This store name is displayed based on the store-specific information acquired in step S1.
When a customer wishes to start registering a product for shopping, the customer operates a transaction start button BT10 arranged on the start-up screen.
In response to the operation of the transaction start instruction button BT10, the mobile terminal 60 transmits a transaction start request including the acquired store specific information and customer identification information to the transaction management device 20. The transaction start request may be transmitted in response to the customer's operation on the mobile terminal 60 as described above, or may be transmitted in response to the acquisition of store specific information without receiving any particular operation.
Regarding the customer identification information, the information entered in the name field of the registration form using the mobile terminal 60 during customer registration (when downloading or installing a shopping application on the mobile terminal 60) may be stored in the customer information of the transaction management device 20, but may also be stored in the memory of the mobile terminal 60 in addition to the transaction management device 20. When a store is identified (when the product registration initial screen described below is acquired), the store name, the services being offered (flyer information distributed on that day), and available coupon information of the store may be displayed on a screen (the product registration initial screen or a screen other than the product registration initial screen). The service and coupon information may be acquired from the transaction management device 20 as screen information, for example.

The destination information (address of the transaction management device 20) may also be obtained when registering the customer (when downloading or installing a shopping application to the mobile terminal 60) and stored in the memory of the mobile terminal 60. When scanning a two-dimensional code, the destination information may be converted into a two-dimensional code in addition to the store-specific information, and the mobile terminal 60 may obtain the destination information along with the store-specific information by scanning the two-dimensional code.

Step S2: The transaction management device 20, which has received the customer identification information and store identification information as a transaction start request from the mobile terminal 60, generates cart information for the transaction. Note that in the initial state in which the cart information is generated, the cart identification information, transaction start date and time, and customer identification information are stored, but since this is before the start of the actual transaction (product registration), other information (transaction end date and time, product information (registered product information, pending product information), etc.) is not stored.

As described above, the transaction management device 20 stores store information such as that shown in FIG. 7(B), so when it receives store identification information (it also receives customer identification information) as a transaction start request from the mobile terminal 60, if the received store identification information is a two-dimensional code, it acquires the store identification information by referring to store identification information 1, and if the received store identification information is location information (GPS information), it acquires the store identification information by referring to store identification information 2. Note that if the store identification information received from the mobile terminal 60 is a two-dimensional code of the store identification information, the transaction management device 20 can simply acquire it as is.

In other words, the transaction management device 20, which receives customer identification information and store identification information from the mobile terminal 60 as a transaction start request, acquires the store identification information from the store identification information received from the mobile terminal 60, and further acquires the current date, issues (assigns) a serial number, combines the store identification information, the current date, and the serial number, and stores them as cart identification information in the cart information. Also, the transaction management device 20, which receives store identification information and customer identification information from the mobile terminal 60 as a transaction start request, acquires the current date and time, and stores them as the transaction start date and time (generation date and time) in the cart information. Also, the transaction management device 20, which receives store identification information and customer identification information from the mobile terminal 60 as a transaction start request, stores the customer identification information received from the mobile terminal 60 as customer identification information in the cart information.

Step S3: The transaction management device 20, which has generated the cart information for the transaction, generates product registration initial screen information (screen information of the product registration screen, which is the initial screen), and transmits it to the mobile terminal 60. Specifically, the transaction management device 20, for example, generates product registration initial screen information, and transmits the generated product registration initial screen information together with cart identification information to the mobile terminal 60.

Step S4: The mobile terminal 60 receives the cart identification information and the product registration initial screen information from the transaction management device 20, stores the cart identification information, and displays the registration screen on the display unit. Specifically, the mobile terminal 60 displays the product registration initial screen as shown in FIG. 10(B), for example.

The product registration initial screen is a product registration screen that is displayed first when product registration is started.
The product registration screen has a captured image area AR1 and a product registration result area AR2. The captured image area AR1 is an area in which a captured image obtained by imaging by the imaging unit 506 is displayed. A product code (e.g., a barcode) captured so as to fall within a predetermined range in the captured image displayed in the captured image area AR1 is to be read.
The product registration result area AR2 shows the number of registered products (registered points) and the total price for the products registered so far, and is an area in which list items corresponding to each registered product are arranged. In the case of the product registration initial screen shown in the figure, since no products have been registered yet, the product registration result area AR2 is blank with no list items arranged.

Step S5: The customer operates the mobile terminal 60 to scan the barcode attached to the product and read the product code. In the figure, it is assumed that the barcode scan was successful. Steps S5 to S9 are repeated each time a barcode attached to a product is scanned.

The mobile terminal 60 that has acquired the barcode transmits the cart identification information and the product registration information, including the product code obtained by scanning, to the transaction management device 20.

Step S6: The transaction management device 20 receives the product registration information (cart identification information and product code) from the mobile terminal 60 and identifies the cart information of the transaction from the cart identification information included in the received product registration information.

Step S7: The transaction management device 20 updates the product data in the identified cart information. Specifically, if the received product registration information contains a product code for item N, the transaction management device 20 stores the product code as the product code of the registered product information (registered product N) in the identified cart information, obtains the product name and price corresponding to the product code from the product information, and stores them as the product and price of the registered product information (registered product N). The transaction management device 20 also updates the registered product information (total) in the identified cart information.

Step S8: After updating the product data in the cart information, the transaction management device 20 generates product registration update screen information (screen information of the product registration screen, which is an update screen to which the registered product has been added) and transmits it to the mobile terminal 60. Specifically, the transaction management device 20 generates product registration update screen information on the mobile terminal 60, for example, such that a product registration update screen is displayed on the mobile terminal 60 in which the list item Itm of the currently registered product has been added in the product registration result area AR2, as shown in FIG. 10 (C), and transmits the generated product registration update screen information to the mobile terminal 60 together with the cart identification information.

The product registration screen (product registration update screen) shown in Figure 10 (C) is displayed on the mobile terminal 60 after "XX bread" is registered as the third product item. In other words, when "XX yogurt" is stored in the cart information as the first item, the transaction management device 20 generates product registration update screen information such that "XX yogurt" is displayed as the list item Itm on the mobile terminal 60 and transmits the generated product registration update screen information together with the cart identification information to the mobile terminal 60; when "XX chocolate" is stored in the cart as the second item, the transaction management device 20 generates product registration update screen information such that "XX yogurt" and "XX chocolate" are displayed as the list items Itm on the mobile terminal 60 and transmits the generated product registration update screen information together with the cart identification information to the mobile terminal 60; when "XX bread" is stored in the cart information as the third item, the transaction management device 20 generates product registration update screen information such that "XX yogurt", "XX chocolate", and "XX bread" are displayed as the list items Itm on the mobile terminal 60 as shown in FIG. 10(C), and transmits the generated product registration update screen information together with the cart identification information to the mobile terminal 60.

Step S9: The mobile terminal 60, which has received the cart identification information and product registration update screen information from the transaction management device 20, adds the product to the registration screen. Specifically, the mobile terminal 60 displays a product registration update screen such as that shown in FIG. 10(C). As described above, the product registration screen (product registration update screen) shown in FIG. 10(C) is displayed on the mobile terminal 60 after "XX bread" has been registered as the third product item.

Step S10: The mobile terminal 60 accepts a checkout instruction operation as a customer operation. For example, it accepts a touch of the checkout instruction button BT15 that displays "Proceed to checkout" as shown in FIG. 10(C).

Step S11: The mobile terminal 60 that has accepted the settlement transition instruction operation generates a two-dimensional code. That is, the mobile terminal 60 converts information (e.g., cart identification information) required to execute the settlement process for the products purchased by the mobile terminal 60 into a two-dimensional code. The mobile terminal 60 that has generated the two-dimensional code displays the generated two-dimensional code on the display unit. For example, a code screen with a two-dimensional code arranged as shown in FIG. 10(D) is displayed on the display unit.
Furthermore, a message area AR3 is arranged on the code screen. In this case, the message area AR3 displays a message such as "Please read the following code with the settlement machine" to guide the customer to have the scanner unit 406 of the settlement device 40 read the code on the code screen.

Step S12: The settlement device 40 scans (reads) the two-dimensional code displayed on the display unit of the mobile terminal 60. For example, the settlement device 40 scans the two-dimensional code displayed on the display unit of the mobile terminal 60 that is pointed by the customer within the recognition range of the scanner unit 406.

Step S13: The settlement device 40 reads the two-dimensional code displayed on the display of the mobile terminal 60 and requests the transaction management device 20 to calculate the subtotal amount. For example, the settlement device 40 sends a calculation request (subtotal calculation request information) requesting calculation of the subtotal amount to the transaction management device 20 together with the cart identification information obtained from the two-dimensional code.

Step S14: The transaction management device 20 receives the cart identification information and the sub-calculation output request information from the mobile terminal 60 and identifies the cart information of the transaction from the cart identification information.

Step S15: After identifying the cart, the transaction management device 20 calculates the subtotal amount using information such as the price in the registered product information included in the cart information corresponding to the identified cart information.

Step S16: After calculating the subtotal, the transaction management device 20 updates the cart information (stores the subtotal (calculated subtotal)) and transmits the subtotal information indicating the calculated subtotal together with the cart identification information to the settlement device 40.

Step S17: Having received the cart identification information and subtotal information from the transaction management device 20, the settlement device 40 displays the subtotal amount on the display unit 405.

Step S18: The settlement device 40, which has displayed the subtotal amount on the display unit 405, executes the payment (settlement). Specifically, the settlement device 40 accepts the selection of the payment type. In the case of cash, it accepts the deposit, calculates the change amount, and, if there is change, dispenses the change and issues a receipt. In addition, when the settlement is completed, the settlement device 40 sends settlement completion information together with the cart information to the transaction management device 20, and the transaction management device 20 stores the transaction end date and time (settlement date and time) for that cart.

The mobile terminal 60 transmits the product code to the transaction management device 20 after scanning the product (S5), but may not transmit product codes for products (e.g., products scanned at another store, etc.) other than the products scanned in the store (the store when the user visited the store and displayed the product registration initial screen). For example, the mobile terminal 60 acquires and stores location information (GPS information) when the user visits the store (or when the product registration initial screen is displayed). The mobile terminal 60 also acquires location information when scanning each product, and compares the location information acquired when the user scanned the product with the location information acquired when the user visited the store (or when the product registration initial screen is displayed). The mobile terminal 60 may then permit the transmission of the product code of the product to the transaction management device 20 if the two match (or approximately match), and prohibit the transmission of the product code of the product to the transaction management device 20 if the two do not match (or approximately match).
This makes it possible to prevent inappropriate product registration (for example, registering a product to a cart created at another store, etc.).

When the settlement device 40 prohibits the transmission of the product code as described above, it may display an error message (e.g., "Registration is not possible because it is not in the XX store") on the display unit 405 after scanning the product. The settlement device 40 may also display the above message on the store clerk's display unit 410 instead of or in addition to the display unit 405.

The settlement device 40 may read the two-dimensional code displayed on the display of the mobile terminal 60 and then request the transaction management device 20 to calculate the subtotal amount (S13), but may not request the calculation of the subtotal amount for products other than the product scanned in the store (for example, products scanned in other stores). For example, the settlement device 40 refers to the store identification information of the store (the settlement device 40 may store and refer to the store identification information of the store in the settlement device 40 itself, or may refer to the store identification information stored in another accessible device), and when the settlement device 40 reads the two-dimensional code displayed on the display of the mobile terminal 60, compares the cart identification information obtained from the two-dimensional code with the store identification information of the store. The settlement device 40 may permit the request to calculate the subtotal amount if the store identification information included in the cart identification information includes the store identification information of the store, and may prohibit the request to calculate the subtotal amount if the store identification information does not include the store identification information of the store.
This makes it possible to prevent inappropriate payments (for example, payments for products registered at other stores, etc.).

When the settlement device 40 prohibits the request for the subtotal amount as described above, it may display an error message (e.g., "Settlement is not possible because the transaction includes products from a store other than XX") on the display unit 405 after reading the two-dimensional code. The settlement device 40 may also display the above message on the store clerk's display unit 410 instead of or in addition to the display unit 405.

In the example of the processing procedure in Fig. 9, the transaction management device 20 calculates the subtotal amount. However, for example, the settlement device 40 may acquire cart information from the transaction management device 20 and calculate the subtotal amount based on the acquired cart information.
Alternatively, the transaction management device 20 may send cart information to the store controller 10 and request calculation of the subtotal amount, and the store controller 10 may calculate the subtotal amount using the received cart information, and transmit the calculated subtotal amount to the settlement device 40 via the transaction management device 20.

When processing the settlement, the transaction management device 20 may check the cancellation status of the customer's products based on the customer information and cart information for the customer, and determine whether or not to issue a warning against fraud. If it is determined that a warning should be issued, the transaction management device 20 may, for example, cause the settlement device 40 to issue a warning notification.

Furthermore, during checkout processing, the transaction management device 20 may determine whether the product information included in the cart information includes any reserved items, and if so, may request the checkout device 40 to provide instructions to correct the reserved items. Upon receiving a request to provide instructions to correct the reserved items, the checkout device 40 may display a message to notify the user that there are reserved items. Upon confirming the message, the store clerk may perform an operation to release (correct) the reserved items, such as entering a price corresponding to the reserved items or canceling the reserved items.

[Overview of changing display mode according to holding state]
In self-operation, when a customer registers an item, the customer can use the mobile terminal 60 while it is held in a holder 71 of a shopping cart 70 (cart-held state), or can remove it from the holder 71 of the shopping cart 70 and hold it in his/her hand (hand-held state).
In this case, for example, in the hand-held state, the customer can adjust the distance between himself/herself and the mobile terminal 60 so that the contents on the screen can be easily seen and the operation can be easily performed. On the other hand, in the cart-held state, the position of the mobile terminal 60 is fixed with a certain distance between the customer and the mobile terminal 60, so that it may be difficult for the customer to see the contents on the screen of the mobile terminal 60 and to operate the screen, compared to the hand-held state.

Therefore, the mobile terminal 60 of this embodiment determines whether the state of its own holding is a hand-held state or a cart-held state, and when it determines that it is in the cart-held state, performs screen change control so as to change the display on the screen to a mode different from that in the hand-held state. This improves the visibility and operability of the screen in the cart-held state, making the mobile terminal 60 easier to use.
This point will be explained below.

[Determining the holding state]
When the mobile terminal 60 performs the above-mentioned screen change control, it is configured to determine whether the current state of its own holding is a cart-held state or a hand-held state. The mobile terminal 60 may determine whether the state is a cart-held state or a hand-held state based on detection information from a motion sensor in the sensor unit 608. The mobile terminal 60 determines whether the state is a cart-held state or a hand-held state based on a predetermined change pattern or the like in a detection signal input from an acceleration sensor or a gyro sensor as a motion sensor.
It should be noted that, without using a motion sensor, it may be possible to determine whether the state is a cart-held state or a hand-held state, for example, as follows.
For example, a sensor may be provided for the portable terminal 60, which is in a state where pressure is applied to the portable terminal 60 or where light reception is blocked when the portable terminal 60 is held by the holder 71. The portable terminal 60 may determine whether the portable terminal 60 is in a cart-held state or a hand-held state, depending on the state detected by the sensor.
Also, for example, a sensor may be provided in holder 71 that is in a state where pressure is applied or where light is not received when portable terminal 60 is held. Holder 71 is communicably connected to portable terminal 60 by short-range wireless communication such as Bluetooth. Holder 71 transmits information to portable terminal 60 indicating whether or not portable terminal 60 is being held, according to the detection output of the sensor. Portable terminal 60 may determine whether it is in a cart-held state or a hand-held state, based on the received information.
Also, a sensor for detecting an external temperature may be provided in the mobile terminal 60. In this case, the mobile terminal 60 may determine whether it is in a cart-held state or a hand-held state based on a temperature detected in response to the body temperature of a hand applied to the mobile terminal 60 when the mobile terminal 60 is in a hand-held state and a temperature detected by the sensor in a state where no body temperature is applied when the mobile terminal 60 is not in a hand-held state (cart-held state).
Also, for example, the customer may perform an operation to specify the cart-held state when changing to the cart-held state, and may perform an operation to specify the hand-held state when changing to the hand-held state on the mobile terminal 60. In this case, the mobile terminal 60 may determine whether it is in the cart-held state or the hand-held state depending on whether the mobile terminal 60 is currently in the designated state of the cart-held state or the hand-held state.
In the following description, an example will be described in which the mobile terminal 60 makes a determination using a detection signal from a motion sensor.

[Example of changing display mode according to holding state]
During product registration, the mobile terminal 60 displays a product registration screen. When the mobile terminal 60 determines that the current state of its own holding is a hand-held state, the mobile terminal 60 displays the product registration screen in the form exemplified in Fig. 10(C). Here, the product registration screen in the form exemplified in Fig. 10(C) is treated as being in a standard state.

Fig. 11A shows an extracted product registration result area AR2 on the product registration screen in the standard state as shown in Fig. 10C. The product registration result area AR2 on the product registration screen in the standard state shown in the figure is treated as the standard size.
As shown in FIG. 11(A), the standard size product registration result area AR2 has an estimate area AR21 and a registration list area AR22. The estimate area AR21 shows the number of registered products (registered number) and the total amount for the products registered so far, and has a checkout instruction button BT15. The registration list area AR22 is an area where list items Itm corresponding to each registered product are arranged. A quantity area 221 is arranged in each list item Itm. The quantity area AR221 is an area showing the registered quantity (registered quantity) for the corresponding product. The quantity area AR221 also functions as a button for performing an operation to instruct the display of a product registration change screen, which will be described next.

When the quantity area AR221 of a certain list item Itm is operated in the standard product registration result area AR2 shown in FIG. 11 (A), a product registration change screen is displayed. The product registration change screen is a screen where operations are performed to change the registered quantity of the product corresponding to the list item Itm that includes the operated quantity area AR221, cancel the registration, and otherwise change the registered details.

Figure 12 shows an example of a product registration change screen P30 that is displayed in response to an operation on the quantity area AR221 in the product registration result area AR2 in the standard state as described above. The product registration change screen P30 in the figure shows an example in the form of a pop-up screen that is superimposed on the product registration screen. The product registration change screen P30 in the figure is also small in size, occupying a portion of the product registration result area AR2.

The product registration change screen P30 in the figure is displayed in response to selecting the list item Itm for the "XX Chocolate" product from among the three list items Itm in the product registration result area AR2 in the figure. In this case, in the product registration result area AR2, the two list items Itm for products other than "XX Chocolate" are grayed out, indicating that they are not available for selection, and the list item Itm for "XX Chocolate" is not grayed out, indicating that it is available for selection.

The product registration change screen P30 is arranged with a cancel button BT31, a quantity/price area AR30, a plus button BT32-1, and a minus button BT32-2.
The cancel button BT31 is a button that is operated to cancel the registration of the target product. When the cancel button BT31 is operated, if the registered quantity of the target product is two or more, the entire registered quantity is cancelled.
The quantity/price area AR30 indicates the registered quantity of the target product corresponding to the current time and the price according to the registered quantity.
The plus button BT32-1 is a button that is operated when making a change to increase the registered quantity of a target product. Each time the plus button BT32-1 is operated, the registered quantity is changed to increase by one.
The minus button BT32-2 is a button that is operated when making a change to decrease the registered quantity of the target product. Each time the minus button BT32-2 is operated, the registered quantity is changed to decrease by one.
In response to a change in the registered quantity by operating the plus button BT32-1 or the minus button BT32-2, the registered quantity and price in the quantity/price area AR30 are changed.

Note that decreasing the registered quantity in response to the operation of the minus button BT32-2 may also be treated as canceling the product. In other words, when the registered quantity of a registered product is decreased, the product corresponding to the decreased quantity may be treated as being canceled.

When the product registration change screen P30 is displayed, for example, if the list item Itm corresponding to the target product is operated, the product registration change screen P30 is cleared and the product registration screen is returned to being displayed.

When canceling the entire quantity of the target product (cancelling the registration), the customer operates the cancel button BT31. When the cancel button BT31 is operated, for example, the product registration change screen P30 is cleared and a confirmation screen is displayed. If the customer is happy to proceed with the cancellation, he or she performs a cancel instruction operation on the confirmation screen (for example, by operating the execute button). In response to the cancel instruction operation being performed, the confirmation screen is cleared and the display returns to the product registration screen. In this case, on the product registration screen that is displayed after the confirmation screen is cleared, the list item Itm of the "XX Chocolate" product that was selected for cancellation has been cleared.

On the other hand, when the mobile terminal 60 determines that its current holding state is a cart holding state, it changes the product registration result area AR2 on the product registration screen from the standard state to an enlarged state, as shown in Figure 11 (B).
In the product registration result area AR2 in Fig. 11 (B), the area sizes of the estimate area AR21 and the list items Itm in the registration list area AR22 are enlarged from the standard state. In the estimate area AR21, the area size is enlarged, and therefore the displayed characters and the payment transition instruction button BT15 are enlarged from the standard state. In the list item Itm, the area size is also enlarged, and therefore the characters indicating the product name, price, etc. and the quantity area AR221 are enlarged.
In addition, in the product registration result area AR2 in Fig. 11(B), the number of list items Itm that can be displayed in the registration list area AR22 becomes smaller than in the standard state in accordance with the enlargement of the estimation area AR21 and the list items Itm as described above. Specifically, in the product registration result area AR2 in Fig. 10(C), three list items Itm are displayed so as to fit, but in Fig. 11(B), the registration list area AR22 is occupied by the display of two list items Itm.

Here, in the registration list area AR22 of Fig. 11(B), two list items Itm are displayed corresponding to "XX Chocolate" which is the second product registered in the order of registration, and "XX Bread" which is the third product registered in the order of registration. In other words, in the registration list area AR22 of the same figure, the list item Itm of the last product registered in the order of registration is placed at the bottom, and the list items Itm are placed above it in the order of registration going back. By placing the list items Itm in this way, the customer can immediately know which product was registered most recently.
In addition, the first list item Itm "XX Yogurt" that is not displayed in the registration list area AR22 in the state shown in Figure 11 (B) can be displayed, for example, by performing a scroll operation or a page forward operation on the registration list area AR22.
In addition, in the product registration result area AR2, the list items Itm may be arranged in the order of registration starting from the first item.

Even in the state where the display is enlarged as shown in FIG. 11(B), it is possible to operate the quantity area AR221 of the list item Itm. When the quantity area AR221 of a certain list item Itm is operated in the state shown in the figure, the product registration change screen P40 in the state shown in FIG. 13 is displayed.

The product registration change screen P40 in FIG. 13 is displayed in a larger size than the product registration change screen P30 in FIG. 12 so as to be superimposed on the product registration screen.
Also, the product registration change screen P40 in Fig. 13 shows an example of a case where the product is displayed in response to selecting the list item Itm of the product "XX Chocolate" from among the three list items Itm in the product registration result area AR2 in Fig. 11 (B). A target product name area AR41 is arranged in the product registration change screen P40. In the target product name area AR41, the product name of the product that is the target of the registration content change is displayed. Specifically, the target product name area AR41 in the figure displays "XX Chocolate", thereby indicating that the product that is the target of the registration content change is "XX Chocolate".

In the product registration change screen P40 of the figure, in addition to the target product name area AR41, a unit price area AR42, a quantity area AR43, a plus button BT41-1, a minus button BT41-2, a price area AR44, a cancel button BT42, and a confirm button BT43 are arranged.
The unit price area AR42 indicates the unit price of the target product.
The quantity area AR43 indicates the quantity specified for the target product.
The plus button BT41-1 is a button that is operated when making a change to increase the registered quantity of the target product, and the minus button BT41-2 is a button that is operated when making a change to decrease the registered quantity of the target product.
The price area AR44 indicates the price of the target product according to the quantity indicated in the quantity area AR43.
The cancel button BT42 is a button that is operated to cancel the registration of the target product.
The decision button BT43 is a button used to confirm the quantity shown in the quantity area AR43 as the registered quantity.

When a customer wishes to change the registered quantity, they operate the plus button BT41-1 and the minus button BT41-2 to specify the quantity, and then operate the confirm button BT43. When the confirm button BT43 is operated, the quantity previously shown in the quantity area AR43 is confirmed, the product registration change screen P40 is cleared, and the display returns to the product registration screen. In the product registration screen that is displayed after the product registration change screen P40 is cleared, the list item Itm of the targeted product shows the confirmed quantity in the quantity area AR221, and the price according to the confirmed quantity is also displayed.

If the customer wishes to cancel the registration of the product in question, he or she operates the cancel button BT42. In response to the operation of the cancel button BT42, the product registration change screen P40 is cleared, and the product registration screen is returned to its displayed state. In this case, in the product registration screen that is displayed after the product registration change screen P40 is cleared, the list item Itm of the "XX Chocolate" product that was the subject of this cancellation has been cleared.

The product registration change screen P40 is displayed in a larger size than the product registration change screen P30 in FIG. 12. For this reason, the text on the product registration change screen P40 can be made larger than the text on the product registration change screen P30. In addition, image controls such as the plus button BT41-1, minus button BT41-2, cancel button BT42, and enter button BT43 can also be made larger than the image controls on the product registration change screen P30.

As can be understood from the above description, in this embodiment, when the mobile terminal 60 is in a cart holding state, the display mode of the product registration result area AR2 on the product registration screen and the product registration change screen P40 is changed so that they are enlarged compared to when they are in a hand-held state. This allows a customer who is registering a product to ensure that the visibility and operability of the product registration change screen P40 are not impaired by putting the mobile terminal 60 in a cart holding state, even if the customer is far away from the mobile terminal 60.

In the above explanation, the display aspect corresponding to the hand-held state is considered to be the standard, and the display aspect corresponding to the cart-held state is considered to be an enlarged version of the standard, but which of the display aspects corresponding to such holding states is considered to be the standard may be relative. In other words, the display aspect corresponding to the cart-held state may be considered to be the standard, and the display aspect corresponding to the hand-held state may be considered to be a reduced version of the standard.

[Modification of the embodiment]
A modified example of this embodiment will be described. In this embodiment, the product registration result area AR2 is displayed in a larger size in the cart holding state than in the hand-held holding state. In addition, in the above embodiment, the product registration change screen P40 is displayed on the product registration screen in response to an operation on the quantity area AR221 in the product registration result area AR2.
In contrast, in a modified example of this embodiment, the product registration result area AR2 is configured to allow the customer to change the registered product details. In this case, the customer can change the registered product details while the product registration screen is displayed, without displaying the product registration change screen P40.

Fig. 14 shows an example of the form of the product registration result area AR2 as a modified example of this embodiment. The product registration result area AR2 in the figure corresponds to the cart holding state. In this modified example, the product registration result area AR2 in the hand-held holding state may be the same as that in Fig. 10.
In the list item Itm of the product registration result area AR2 in the figure, the product name and price are displayed, and a quantity change area AR222, a cancel button, and a button BT52 are arranged.
The quantity change area AR222 is an area where an operation for changing the registered quantity of the corresponding product is performed. In the quantity change area AR222, a quantity area AR52, a plus button BT51-1, and a minus button BT51-2 are arranged.
A customer can change the registered quantity of a corresponding product by operating the plus button BT51-1 or the minus button BT51-2. In this case, the registered quantity is changed by operating the plus button BT51-1 or the minus button BT51-2, and the registered quantity may be confirmed each time the price shown in the same list item Itm is updated to a price corresponding to the changed registered quantity.
Furthermore, the customer can cancel the registration of the corresponding product by operating the cancel button and BT52. In this case, in response to the operation of the cancel button and BT52, a confirmation screen is displayed for the customer to confirm the cancellation. If the customer is happy to cancel the product, he or she performs a cancel instruction operation on the confirmation screen. In response to the cancel instruction operation being performed, the confirmation screen is cleared and the display returns to the product registration screen. In the product registration result area AR2 of the displayed product registration screen, the list item Itm corresponding to the product that was the subject of this cancellation has been deleted.

The captured image area AR1 on the product registration screen may also be altered between the hand-held state and the cart-held state. As an example, in the cart-held state, messages such as "Please scan the barcode" displayed in the captured image area AR1 of FIG. 10(C) and a frame indicating the position of the code of the product to be scanned in the captured image may be displayed larger than in the hand-held state to improve visibility. At this time, a magnification of the captured image different from that in the hand-held state may be set so that the product code can be easily fitted within the frame.

[Example of processing procedure]
An example of a processing procedure executed by the mobile terminal 60 in relation to the display of the product registration screen will be described with reference to the flowchart of Fig. 15. The processing in Fig. 15 is executed during product registration (from the start of displaying the product registration initial screen until a payment transition instruction operation is performed). In addition, the processing in Fig. 15 corresponds to the case where the product registration change screen P40 in Fig. 13 is displayed in response to an operation on the quantity area AR221 in a cart holding state.

Step S101: During product registration, the mobile terminal 60 determines whether the current holding state is a cart holding state based on the detection signal of the motion sensor in the sensor unit 608.

Step S102: If it is determined that the cart is in a holding state, the mobile terminal 60 displays a product registration screen with the product registration result area AR2 enlarged as shown in FIG. 11 (B). In the following description, the product registration screen with the enlarged product registration result area AR2 is also referred to as the enlarged product registration screen.

Step S103: If it is determined in step S101 that the item is not in a cart-held state but in a hand-held state, the mobile terminal 60 displays a product registration screen with a standard-sized product registration result area AR2, as shown in Figures 10(C), 11(A), etc. In the following description, the product registration screen with a standard-sized product registration result area AR2 is also referred to as the standard product registration screen.

Step S104: After processing step S102 or step S103, the mobile device 60 determines whether an operation has been performed on the quantity area AR221 of any of the list items Itm on the currently displayed product registration screen.

If it is determined in step S104 that no operation has been performed on the quantity area AR221, the process returns to step S101.
When the process returns to step S101, if there is no change in the holding state between before the process returned to step S101 and now, the process may skip step S102 or step S103 and proceed to step S104.
On the other hand, if the customer changes the mobile terminal 60 from a cart-holding state to a hand-held state at the timing when the process is returned to step S101, it is determined in step S101 that the mobile terminal 60 is in a hand-held state. In this case, the mobile terminal 60 executes the process of step S103 to change the display from the enlarged product registration screen to the standard product registration screen.
Furthermore, when the customer changes the mobile terminal 60 from a hand-held state to a cart-held state at the timing when the process is returned to step S101, it is determined in step S101 that the mobile terminal 60 is in a cart-held state. In this case, the mobile terminal 60 executes the process of step S102 to change the display from the standard product registration screen to an enlarged product registration screen.

Step S105: If it is determined in step S104 that an operation has been performed on the quantity area AR221, the mobile terminal 60 determines whether the current holding state is a cart holding state.

Step S106: If it is determined in step S105 that the cart is in a holding state, the mobile terminal 60 displays an enlarged product registration change screen P40 as shown in FIG. 13.

Step S107: If step S105 determines that the product is being held in the hand, the mobile terminal 60 displays the standard-sized product registration change screen P30, as shown in FIG. 12.

Step S108: The mobile terminal 60 waits for an operation to confirm the change to the registered contents (change confirmation operation) on the product registration change screen (P30 or P40) displayed by the processing of step S106 or step S107. The change confirmation operation here is either an operation to confirm (determine) the quantity changed by operating the plus button or minus button, or an operation to confirm the cancellation of the registration of the target product.

Step S109: When the change confirmation operation is performed, the mobile terminal 60 executes a process to confirm the changed registration details for the target product, erases the product registration change screen that was displayed up until that point, and returns the process to step S101.

In the process shown in the figure, even if the holding state changes while the product registration change screen is displayed, the display of the initially displayed product registration change screen P30 and product registration change screen P40 is maintained regardless of the change in the holding state. This is to take into consideration the fact that changing the appearance of the product registration change screen in response to a change in the holding state may make it more difficult to operate. In some cases, the product registration change screen may be changed in response to a change in the holding state.

<Modification>
Modifications of the present embodiment will be described below. The modifications described below may be combined with the above embodiment and other modifications as appropriate.

[First Modification]
As described above, after completing product registration using the mobile terminal 60, the customer can perform a checkout transition instruction operation (operation of the checkout transition instruction button BT15) to display a code screen on the mobile terminal 60, and then start checkout by having the checkout device 40 read the code displayed on the code screen.
To have the settlement device 40 read the code, the customer holds the mobile terminal 60 in his/her hand and holds the code displayed on the display unit 405 of the mobile terminal 60 over the scanner unit 406 of the settlement device 40. Therefore, when a settlement transition instruction operation is performed on the mobile terminal 60 in the cart holding state, the customer needs to remove the mobile terminal 60 from the holder 71 of the shopping cart 70 and hold it in his/her hand after the settlement transition instruction operation. At this time, the mobile terminal 60 changes from the cart holding state to the hand-held state after the settlement transition instruction operation.

Therefore, when the mobile terminal 60 of this modified example determines that the cart is in a cart holding state when a checkout transition instruction operation is performed, it displays a message different from that shown in Figure 10 (D) in the message area AR3 of the code screen displayed in response to the checkout transition instruction operation, as shown in Figure 16.
16 , a message is displayed saying, "Please pick up your smartphone so that the settlement machine can read the code below." In other words, in the message area AR3 in FIG 16 , a message is displayed instructing the customer to first remove the mobile terminal 60 from the holder 71 and hold it in their hand before the settlement device 40 can read the code.
When a customer removes the mobile terminal 60 displaying the display in Fig. 16 from the holder 71 and holds it in his/her hand, the mobile terminal 60 determines that the state has changed from the cart-held state to the hand-held state. When it is determined that the state has changed to the hand-held state, the mobile terminal 60 may change the display in the message area AR3 on the code screen to, for example, the display in Fig. 10(D).
In addition, in this modified example, when a settlement transition instruction operation is performed while the device is being held in hand, a message area AR3 with content similar to that shown in FIG. 10 (D) may be displayed from the start of the display of the code screen.

[Second Modification]
Next, a second modified example will be described. In this modified example, a sales area capable of selling by weight in a self-service manner is provided in a store, where customers can price products using a weighing pricing device and register the products.
The weighing and pricing device measures the weight of the product to be registered that is placed on a weighing platform, and registers the product by determining the price of the product according to the measured weight using information such as the weight unit price of the measured product.
In a sales area where a weighing and pricing device compatible with such a self-service system is used, the procedure for registering products and the associated processing in the shopping system are different from those in the previous embodiment. This point will be described below.

First, an example of a procedure for a customer to register an item at a sales floor where a weighing and pricing device is used will be described.
When a customer wishes to purchase a commodity sold by weight, the customer first uses his/her mobile terminal 60 to input the item name of the commodity to be purchased as follows.
17 shows an example of a display of products sold by weight in a store. In the example shown in the figure, lemons LM, apples AP, and oranges OG are displayed as products sold by weight. Also, product information panels 3000-LM, 3000-AP, and 3000-OG are installed corresponding to the displayed lemons LM, apples AP, and oranges OG. When no particular distinction is made between the product information panels 3000-LM, 3000-AP, and 3000-OG, they will be referred to as product information panel 3000.

The product information panel 3000 presents information on the corresponding product. In the figure, the product information panel 3000-LM is shown enlarged. Thus, the product information panel 3000-LM presents, as product information, that the product's item is lemon, the unit price per unit weight, and a product information code 3001. In the example shown in the figure, the product information code 3001 is a barcode (one-dimensional code). The product information code 3001 includes the product code of the product's item type as lemon.
Similarly, the other product information panels 3000 also present product information such as the product category, unit price per unit weight, and product information code.

The product information panel 3000 may be configured to present product information by displaying it on a display device. Alternatively, the product information panel 3000 may be configured to present product information by attaching a printed material such as a poster.

When inputting the item of the product to be purchased, the customer displays the product registration screen on his/her mobile terminal 60 and has the mobile terminal 60 read the product information code displayed on the product information panel 3000 of the product to be purchased. The figure shows the customer reading the product information code 3001 corresponding to lemon LM. The captured image area AR1 on the product registration screen of the mobile terminal 60 shows the captured image of the product information code 3001.
When the product information code 3001 corresponding to lemon LM is scanned in this manner, the mobile terminal 60 acquires product information of lemon LM from the read product information code 3001. The mobile terminal 60 uses the acquired product information to specify lemon LM as an item of a product sold by weight.

Furthermore, a product registration result area AR2 is arranged on the product registration screen. The product registration result area AR2 shows the current registration status of the product to be purchased. In the figure, an estimate area AR21 and list items Itm are arranged in the product registration result area AR2. In the figure, three list items Itm-1, Itm-2, and Itm-3 corresponding to yogurt, apples AP, and lemons LM are arranged as list items Itm.
In this case, yogurt is not a product sold by weight, so for the list item Itm-3 for yogurt, "x1" is displayed in the quantity area AR221, indicating that one unit has been registered, and the price is 160 yen.
In contrast, the Apple AP and Lemon LM products sold by weight are in a "provisionally registered" state (provisionally registered state) for the products to be purchased. A product in a provisionally registered state is a product for which the item has been entered but pricing has not yet been completed (it is also in a state of waiting to be weighed).
For this reason, in the list items Itm-1 and Itm-2 for Apple AP and Lemon LM, for example, the quantity area AR221 indicates that pricing by weighing has not yet been done, with "quantity required." Accordingly, in the list items for Apple AP and Lemon LM, the display of "?? yen" indicates that the price is yet to be determined. Furthermore, in the list items Itm-1 and Itm-2, a predetermined background color is set to indicate the provisional registration status.

In the example shown in the figure, the customer has provisionally registered lemons LM and apples AP as products sold by weight. In this case, the two products sold by weight that the customer specified as items to purchase are lemons LM and apples AP. In this case, the customer will weigh each of the lemons LM and apples AP. The customer will then remove the amount (number) of lemons LM and apples AP that he or she wishes to purchase from the lemons LM and apples AP on display. The customer then takes the removed lemons LM and apples AP with him or her to the weighing and pricing device.

The weighing and pricing device where the customer arrived was not operating in response to operations by other customers, and was therefore in standby mode, waiting for the start of weighing for a transaction. In standby mode, the weighing and pricing device displayed the initial pricing operation screen on the display unit.

18 shows an example of a pricing operation screen in an initial state. A weighing result area AR61 is arranged on the pricing operation screen in the figure. The weighing result area AR61 is an area (column) in which the results of weighing the item sold by weight to be priced are displayed. The weighing result area AR61 includes a weight area AR61-1, a price per unit weight area AR61-2, and a total amount area AR61-3.
The weight area AR61-1 is an area in which the measured weight of the bulk product to be priced is shown.
The price per weight area AR61-2 is an area in which the price per weight of the commodity being priced is shown.

In addition, among the products sold by weight, there are products sold by number, in which the number of items is calculated based on the measured weight and unit weight, and the price is calculated based on the calculated number of items and the unit price per item. In the case of such products sold by weight, the weight area AR61-1 may display the number of items calculated based on the measured weight and unit weight, and the weight unit price area AR61-2 may display the unit price per item.
The total amount area AR61-3 is an area showing the total amount of the prices of the bulk items for which pricing has been completed up to this point in the same transaction.

The product selection area AR62 is an area in which the product to be priced can be selected. In the product selection area AR62 in the same figure, four tabs TB (TB-1 to TB-4) are arranged in the product selection area AR62. In the product selection area AR62, each tab TB is associated with a sheet on which product buttons are arranged. The tab TB can be selected by the customer's operation. The selected tab TB is highlighted relative to the other tabs TB, and in the product selection area AR62, the product button BT6 arranged on the sheet of the selected tab TB is displayed.

In the example of the same figure, the sheet corresponding to the tab TB-1 has a product button BT6 for a provisionally registered product arranged thereon.
On the sheet corresponding to tab TB-2, product buttons BT6 (preset keys) for each product that is registered in advance in the product master according to the classification of the bulk sales product are arranged in a predetermined order.
The sheet corresponding to tab TB-3 has product buttons for products classified as fruits under the classification of bulk products in the product master.
The sheet corresponding to tab TB-4 is a tab corresponding to a sheet on which product buttons for products further classified as vegetables under the classification of bulk products in the product master are arranged.
In this case, a sheet for fruits and a sheet for vegetables are prepared in response to the fact that fruits and vegetables have a high purchase history among the bulk products.

As shown in the figure, the tab TB-2 is selected on the initial pricing operation screen, and as a result, in the product selection area AR62, product buttons BT6 for products included in the general products registered in the product master under the classification of products sold by weight are arranged on the sheet corresponding to the tab TB-2.
The sheet corresponding to tab TB-2 is an area where a customer who is pricing bulk items without using a mobile terminal 60 can select the bulk items to be priced.

If the bulk product to be purchased is fruit, a customer who does not use the mobile terminal 60 to register the product can operate the tab TB-3 to display a sheet on which product buttons BT6 for bulk products in the fruit category are arranged. The customer can operate the product button BT6 corresponding to the bulk product to be purchased from among the product buttons BT6 arranged on the displayed sheet, and designate it as the item of the product to be priced.
Furthermore, if the bulk product to be purchased is a vegetable, a customer who does not use the mobile terminal 60 to register the product can operate the tab TB-4 to display a sheet on which product buttons BT6 for bulk products in the vegetable category are arranged. The customer can operate the product button BT6 corresponding to the bulk product to be purchased from among the product buttons BT6 arranged on the displayed sheet, and designate it as the item of the product to be priced.

In addition, a message area ARm is located above the product selection area AR62. The message area ARm is an area in which a message with a predetermined content according to the content of the current screen is displayed. In the message area ARm in the same figure, "Select The Item" is displayed. In other words, in this case, the message area ARm displays a message instructing the customer to operate the product button BT6 to specify the item of the product to be priced.

Furthermore, a connection information code area AR64 is arranged on the pricing operation screen. The connection information code area AR64 is an area in which a connection information code CD is displayed. The connection information code in the figure is a two-dimensional code, but may be another type of code such as a barcode. The connection information code CD is control information indicating a procedure for connecting the mobile terminal 60 running the shopping application to the weighing pricing device via Bluetooth, for example.
In the connection information code area AR64, a message is displayed to guide the customer to have the portable terminal 60 read the connection information code CD.

In addition, the pricing operation screen includes a search area AR63 where bulk products can be searched for by inputting characters. In the example shown in the figure, bulk products can be searched for by inputting the product name, etc., using a software keyboard provided in the search area AR63.
The search area AR63 does not have to be arranged on the pricing operation screen. In addition, the search area AR63 may be displayed in response to a predetermined operation being performed on the pricing operation screen, for example.

A customer using the mobile terminal 60 to register a product performs an operation to have the mobile terminal 60 read the connection information code CD displayed in the connection information code area AR64 when starting to register a bulk product to be purchased.
In response to reading the connection information code CD as described above, the portable terminal 60 establishes communication with the weighing and pricing device.

When communication with the weighing and pricing device is established, the mobile terminal 60 transmits information about the temporarily registered bulk products to the weighing and pricing device. Specifically, the mobile terminal 60 in this case transmits information about Lemon LM and Apple AP as information about the temporarily registered bulk products.

When the weighing pricing device receives information about a product sold by weight that is provisionally registered, it changes the pricing operation screen from the state shown in FIG. 18 to the state shown in FIG. 19. In FIG. 19, the same parts as in FIG. 18 are given the same reference numerals and descriptions are omitted as appropriate.

In the product selection area AR62 of the pricing operation screen in Figure 19, tab TB-1 is selected instead of tab TB-1 that was selected in Figure 18. Two product buttons BT6 corresponding to apples AP and lemons LM are arranged on the sheet corresponding to the selected tab TB-1. The weight-sold products of apples AP and lemons LM corresponding to the two product buttons BT6 are products provisionally registered as explained above in Figure 17.
In other words, based on the information of the bulk product in a provisionally registered state received from the portable terminal 60, the portable terminal 60 displays a product button BT6 of the bulk product in a provisionally registered state in the product selection area AR62 on the sheet corresponding to the tab TB-1.
In this case, the arrangement order of the product buttons BT6 may correspond to the provisional registration order (the reading order of the product information code).

In other words, the weighing pricing device receives information on products sold by weight that are provisionally registered (provisionally registered products) by establishing a connection with the mobile terminal 60 in standby mode. When the weighing pricing device receives information on provisionally registered products, if the tab TB-2 sheet (Figure 18) is displayed on the initial pricing operation screen, the weighing pricing device will switch to displaying the tab TB-1 sheet (Figure 19) on which the product button BT6 for provisionally registered products is located.

In addition, on the pricing operation screen of FIG. 19, in the connection information code area AR64, the connection information code CD is erased and instead connection compatibility information, such as "connecting," is displayed, indicating that the weighing pricing device is currently connected to the mobile terminal 60.

In addition, in the message area ARm of the same figure, a message is displayed instructing the customer to operate the product button BT6 to specify the item of the product to be priced.

In the following description, an example will be given in which a customer performs registration by operating a pricing operation screen displayed on the weighing pricing device.
Here, the customer decides to register Apple AP first, out of Apple AP and Lemon LM, which are provisionally registered. The customer then operates the product button BT1 corresponding to Apple AP. This designates Apple AP as the item to be priced.

In response to the apple AP being designated as a pricing target, the display on the display unit of the weighing and pricing device transitions from the pricing operation screen to a weighing guidance screen.
Although not shown in the figure, the weighing guidance screen displays a message to the customer instructing them to place the product to be priced on the weighing platform.

With the weighing guidance screen displayed, the customer places the apple AP to be priced on the scale of the weighing and pricing device.
In response to the apple AP being placed on the weighing platform, the weighing and pricing device executes a pricing process. That is, the weighing and pricing device determines the weight of the apple AP in response to determining that the measured weight of the apple AP has stabilized, and calculates the price based on the determined weight and the unit price by weight.

In response to the pricing process being executed in this manner, the display on the display unit transitions to a weighing result screen.
On the weighing result screen, although not shown in the figure, the weight of the weighed Apple AP is shown, along with the price of the Apple AP calculated based on the weight and a total amount based on the calculated price, etc.
The weighing result screen may also have a label issuing button, which allows the customer to issue a label. The customer operates the label issuing button. In this case, the weighing pricing device confirms the pricing process in response to the label issuing button being operated, and issues a label (single item label) on which the pricing result confirmed for the apple AP is printed.

In response to an operation of the label issuing button, the weighing and pricing device issues a label and also transmits product pricing information for the apple AP to the connected mobile terminal 60.

Although not shown in the figure, after the label is printed, the weighing result screen may transition to a label attachment guidance screen.

When the pricing results are obtained for the bulk products in the provisionally registered state as described above and a label is issued, the weighing pricing device transmits the product registration information of the Apple AP reflecting the pricing results to the mobile terminal 60.
The weighing and pricing device may transmit the product registration information to the transaction management device 20 via a communication line.

As soon as the label for the Apple AP has been issued, the pricing operation screen is displayed again. On the displayed pricing operation screen, the Apple AP product button BT1 that was displayed on the pricing operation screen in FIG. 19 is grayed out or erased, making it inoperable.

With the pricing operation screen in the figure displayed, the customer operates the Lemon LM product button BT1 to make the Lemon LM, which is still in a provisional registration state, the subject of pricing.

The customer operates the product button BT11-2 corresponding to the lemon LM, and then has the weighing pricing device price the lemon LM and print a label in the same manner as for the apple AP described above. With the label for the lemon LM printed, the pricing process (registration) for all bulk products that were provisionally registered is completed.

When registration has been completed for all bulk items that were in a provisionally registered state, the display on the weighing pricing device's display will return to the initial pricing operation screen (Figure 18).

In response to the completion of registration of all bulk products that were in a provisionally registered state, the product registration screen displayed on the mobile terminal 60 will be, for example, as shown in FIG.
The product registration result area AR2 on the product registration screen in the figure has changed as follows, in comparison with FIG. 17. That is, the list items Itm-1 and Itm-2 corresponding to lemon LM and apple AP have changed from a state indicating provisional registration to a state indicating registered. Specifically, the background color of each of the list items Itm-1 and Itm-2 has changed from a color indicating a provisional registration state to a color indicating registered. In addition, the price determined by the pricing process is displayed in each of the list items Itm-1 and Itm-2. In addition, the quantity area AR221 in each of the list items Itm-1 and Itm-2 has changed from "measured" to "measured". The quantity area AR221 with "measured" indicates that the corresponding product is a product sold by weight and has been registered by the weighing and pricing process.

When a customer registers a product sold by weight in the manner described above, the customer first reads the product information code 3001 on the product information panel 3000 with the mobile terminal 60 at the sales floor for products sold by weight to provisionally register the product to be purchased, and then travels a certain distance to the weighing and pricing device. When traveling to the weighing and pricing device in this manner, the customer may attach the mobile terminal 60 to the holder 71 of the shopping cart 70, or may hold it in their hand.

When a customer has completed provisional registration of a bulk item and is moving to the weighing and pricing device, it is preferable that a display be displayed on the mobile terminal 60 instructing the customer to have the mobile terminal 60 read the connection information code CD in order to communicatively connect the weighing and pricing device to the mobile terminal 60 when the customer arrives at the weighing and pricing device.

In this modified example, while the customer has completed provisional registration of the bulk product and is proceeding to the weighing and pricing device, the above-mentioned guidance is displayed on the mobile terminal 60. Furthermore, in this modified example, the content (manner) of the guidance is different depending on whether the customer has the mobile terminal 60 attached to the holder 71 of the shopping cart 70 or is holding it in his/her hand when the guidance is displayed.

In this modified example, the mobile terminal 60 determines whether provisional registration of all bulk products that the customer wishes to purchase has been completed. For example, the mobile terminal 60 may determine that provisional registration of all bulk products that the customer wishes to purchase has been completed if a certain amount of time has passed since the reading of the product information code 3001 was performed but the next reading of the product information code 3001 has not been performed.

At this time, the customer has not completed product registration and has not yet performed the payment transition instruction operation, so the mobile terminal 60 displays a product registration screen including a list item Itm for a product sold by weight that is displayed as "requires measurement" in the quantity area AR221, as shown in FIG. 17, for example.

In response to determining that provisional registration of the bulk product is complete, the mobile terminal 60 determines whether its current holding state is a cart holding state or a hand-held holding state.
When it is determined that the cart is in a holding state, the mobile terminal 60 displays, for example, a message such as the following on the product registration screen.
Specifically, for example, in order to communicatively connect the weighing-pricing device and the portable terminal 60, the portable terminal 60 is removed from the holder 71 of the shopping cart 70 and held in the hand, and a message is displayed instructing the user to have the portable terminal 60 read the connection information code CD displayed on the display unit of the weighing-pricing device.
On the other hand, if it is determined that the portable terminal 60 is being held in the hand, the portable terminal 60 will, for example, simply display a message instructing the user to read the connection information code CD displayed on the display unit of the weighing and pricing device using the portable terminal 60 currently being held in the hand.
Such a message may be displayed as a pop-up screen superimposed on the product registration screen. The pop-up screen may be cleared, for example, by operating a confirmation button arranged on the pop-up screen. Alternatively, the pop-up screen may be cleared when the mobile terminal 60 and the weighing and pricing device are connected to each other so as to be able to communicate with each other.

[Third Modification]
Regardless of the holding state of the mobile terminal 60, the screen change control may be stopped and the screen may be fixed in the standard state or the enlarged display state.
For example, a display fix operation may be performed on the mobile terminal 60 to fix the screen state at the current screen state. If a display fix operation is performed when the mobile terminal 60 is currently displaying the screen in the standard state, the mobile terminal 60 will fix the display in the standard state thereafter, regardless of changes in the holding state. For example, some customers may wish to always display as much information as possible on one screen, for example, list items of registered products, regardless of whether the device is in a hand-held state or a cart-held state. In such a case, the screen may be fixed in the standard state. Therefore, the customer in this case may perform a display fix operation when the screen is displayed in the standard state due to the hand-held state.
Furthermore, if the display fixing operation is performed when the mobile terminal 60 is currently in an enlarged display state, the mobile terminal 60 will be fixed in the enlarged display state thereafter regardless of the change in the holding state. Even in a situation where a product is registered with the mobile terminal 60 in a cart holding state, for example, in the case of a product weighing about several kilograms such as rice in a bag, it may be better for the customer to temporarily remove the mobile terminal 60 from the holder 71 and hold it in his/her hand to hold it in his/her hand, and have the mobile terminal 60 read the product code attached to the product. In this way, when the mobile terminal 60 is temporarily held in his/her hand, it may be annoying for the customer that the display on the screen changes to the standard state. In such a case, the customer can perform a display fixing operation when the enlarged display is being performed in the cart holding state, so that the enlarged display is maintained even in the hand-held state.
After the display has been fixed by the display fixing operation as described above, the display fixation may be released, for example, in response to an operation to instruct release of the display fixation.

In addition, for example, from the time when a product registration operation for one item is started until the product registration operation is completed or canceled, the display state (standard state or enlarged display state) at the time when the product registration operation is started may be fixed regardless of the holding state.

[Fourth Modification]
When the product registration screen is displayed in either the standard state or the enlarged display state, the product registration result area AR2 may be hidden and only the captured image area AR1 may be displayed.
For example, in the case where a customer does not often check the product registration results when the cart is held, the product registration result area AR2 may be hidden and only the captured image area AR1 may be displayed when the cart is held. In this case, for example, the customer may perform an operation to display the product registration result area AR2 in an enlarged display state.
On the other hand, in a situation where the customer is less likely to check the product registration results when the product is held in the hand, the product registration result area AR2 may be hidden and only the captured image area AR1 may be displayed when the product is held in the hand. In this case, for example, the product registration result area AR2 in the standard state may be displayed by the customer performing an operation.

[Fifth Modification]
The shopping cart 70 is provided with a rechargeable battery, so that it is possible to charge the mobile terminal 60 attached to the holder 71. Therefore, if the customer charges the mobile terminal 60 with the rechargeable battery while the mobile terminal 60 is in a cart-held state, the stored power of the built-in battery of the mobile terminal 60 can be prevented from decreasing. On the other hand, when the mobile terminal 60 is in a hand-held state, it may be difficult to keep the rechargeable battery of the shopping cart 70 connected, so the stored power of the built-in battery of the mobile terminal 60 decreases.

When the captured image area AR1 is displayed on the product registration screen displayed on the mobile terminal 60, the imaging unit 606 (camera) is activated, and so power consumption is relatively large. For this reason, when the product registration screen is displayed without receiving external charging, the rate at which the stored power of the built-in battery of the mobile terminal 60 decreases also increases.

Therefore, in this modified example, the mobile terminal 60 changes the display mode of the captured image area AR1 as follows, depending on whether the current holding state is a cart holding state or a hand-held holding state.

When the mobile terminal 60 is in the cart holding state, the captured image area AR1 in which the captured image is constantly displayed is displayed on the product registration screen. In other words, when the mobile terminal 60 is in the cart holding state during product registration, the mobile terminal 60 keeps the imaging unit 606 constantly activated. In this case, the power consumption of the mobile terminal 60 increases, but since charging from the charging battery of the shopping cart 70 is possible in the cart holding state, it is possible to prevent the remaining charge of the built-in battery of the mobile terminal 60 from decreasing.

On the other hand, when the mobile terminal 60 is in a hand-held state, if the customer causes the mobile terminal 60 to read the product code for product registration, the captured image is displayed in the captured image area AR1, and if the product code is not to be read, the captured image is not displayed in the captured image area AR1. For this purpose, when the customer causes the mobile terminal 60 to read the product code, an operation for starting the imaging unit 606 may be performed on the product registration screen. In addition, the activation of the imaging unit 606 after the product code is read may be stopped by, for example, an operation by the customer. Alternatively, the activation of the imaging unit 606 may be stopped in response to the passage of a certain time after the mobile terminal 60 reads the product code without the product code being imaged.
When the portable terminal 60 is held in the hand, there are cases where charging from the rechargeable battery is not possible, but by doing as described above, the imaging unit 606 can be started only when reading the product code, which makes it possible to reduce the power consumption of the built-in battery of the portable terminal 60 when held in the hand.

[Sixth Modification]
Contrary to the fifth variant, when the cart is held, the captured image area AR1 is normally not displayed, and when a customer wants to read the product code to register the product, the captured image is displayed in the captured image area AR1 by activating the camera, and when the cart is held in the hand, the captured image area AR1 can be constantly displayed.
For example, shopping using a shopping cart with the mobile terminal 60 held in the cart tends to take a long time. In such a case, in a store where the shopping cart is not equipped with a rechargeable battery, if the captured image area AR1 is constantly displayed, a lot of battery power will be consumed in the mobile terminal 60. In such a case, if the customer operates the camera to display the captured image area AR1, it is possible to reduce battery power consumption during shopping.
On the other hand, when the portable terminal 60 is used in a hand-held state, it is likely to be for short shopping trips at a convenience store, etc. In this case, the power consumed by the portable terminal 60 for product registration is small, so it is preferable to constantly display the captured image area AR1.

[Seventh Modification]
In the above embodiment, a part of the processing executed by the mobile terminal 60 may be executed by, for example, the transaction management device 20, the registration and settlement device 30, the settlement device 40, the transaction status management device 50, the store controller 10, other higher-level devices in the store, or server devices on the cloud. Similarly, a part of the processing executed by each of the transaction management device 20, the registration and settlement device 30, the settlement device 40, the transaction status management device 50, the store controller 10, etc. may also be executed by other devices.
As one of the above-mentioned aspects, the shopping system of the present embodiment may be provided with a thin client system configuration. As an example, the transaction management device 20 or another server may be configured as a thin client-compatible server device (e.g., a cloud server), and the mobile terminal 60 or the like may function as a thin client.
In this case, for example, the cloud server may determine whether the holding state of the mobile terminal 60 is a cart-held state or a hand-held state by utilizing a detection signal from the sensor unit 608 transmitted from the mobile terminal 60.
In addition, the transaction management device 20, transaction status management device 50, store controller 10, etc. may be configured to be distributed across multiple computer devices or servers.

<Overview of the embodiment>
[Technical field]
The present invention relates to a portable terminal and a program.
[Background Art]
There is known technology that uses a gyro sensor or the like built into a portable terminal to determine whether a mobile terminal (portable terminal) used by a customer to register products when shopping is fixed to a shopping cart or held in the hand (see, for example, Patent Document 1).
[Prior Art Literature]
[Patent Documents]
[Patent Document 1] JP 2020-129337 A [Summary of the Invention]
[Problem to be solved by the invention]
As described above, when a customer changes the way he or she holds a portable terminal, it may become difficult to see or operate the screen displayed on the portable terminal.
The present invention has been made in view of the above circumstances, and has an object to enable a screen to be displayed in a manner that is easy for a customer to use depending on how the portable terminal is being held.

[Means for solving the problems]
(1) As described above, one aspect of this embodiment is a portable terminal that includes a display means, a product registration means for registering products, and a display control means for changing the manner of display performed by the display means depending on whether the portable terminal (e.g., mobile terminal 60) is in a first holding state (e.g., hand-held state) in which the portable terminal is held by hand, or a second holding state (e.g., cart holding state) in which the portable terminal is held by a holding means (e.g., holder 71) provided on a mobile object (e.g., shopping cart 70).

According to the above configuration, it is possible to determine whether the mobile terminal 60 is in a cart-held state or a hand-held state, and change the display mode for the customer depending on the result of the determination. This allows a screen that is easy for the customer to use to be displayed depending on the holding state of the mobile terminal 60.

(2) One aspect of this embodiment is the portable terminal described in (1), in which the display (e.g., the display of the product registration result area AR2) on the product registration screen that presents information about the product registered by the product registration means is changed.

According to the above configuration, the product registration screen that is displayed when the customer registers a product displays the product in an appropriate manner depending on whether the product is held in a cart or in a hand-held state.

(3) One aspect of this embodiment is the portable terminal described in (2), in which an area on the product registration screen where specific information about a product is entered (e.g., product registration change screens P30 and P40) is displayed larger in the second holding state than in the first holding state.

When the cart is being held, the distance between the mobile terminal 60 and the customer is greater than when the mobile terminal is being held in the hand. With the above configuration, when the cart is being held, a product registration change screen P40 that is larger than the product registration change screen P30 when the cart is being held in the hand is displayed, thereby improving visibility and operability of the screen when the cart is being held.

(4) One aspect of this embodiment is the portable terminal described in (2) or (3), in which the number of information items (e.g., list items Itm) displayed on the product registration screen, in which information is shown on a registered product basis, is displayed in the second holding state so as to be less than the number in the first holding state.

According to the above configuration, when the cart is being held, the number of list items Itm displayed in the product registration result area AR2 can be reduced compared to when the cart is being held in the hand. This makes it easy to enlarge and display the list items Itm when the cart is being held.

(5) One aspect of this embodiment is the portable terminal described in any one of (1) to (4), in which the display control means changes the display mode depending on whether the holding state is the first holding state or the second holding state, determined based on the detection output of the detection unit.

The above configuration enables the mobile device 60 to determine its own holding state and control changing the display mode.

(6) One aspect of this embodiment is the portable terminal described in any one of (1) to (5), in which the display control means causes a display to differ between the first holding state and the second holding state, to allow a settlement device (40) that performs settlement according to the registration result of the product by the portable terminal to obtain information indicating the registration result of the product by the portable terminal (e.g., a code (two-dimensional code) on a code screen).

With the above configuration, the instructions displayed to the customer to have the settlement device 40 read the code displayed on the mobile terminal 60 to execute the settlement process can be displayed in a manner appropriate to whether the cart is being held or in the handheld state.

(7) One aspect of this embodiment is the portable terminal described in any one of (1) to (6), in which the display control means causes the display to differ between the first holding state and the second holding state in order to communicatively connect the portable terminal to a weighing device that weighs the product.

According to the above configuration, when registering products sold by weight, the instructions displayed to the customer for connecting the weighing and pricing device to the mobile terminal 60 so that they can communicate with each other can be appropriate for when the customer is holding a cart or when the customer is holding the product in his/her hand.

(8) One aspect of this embodiment is a program for causing a computer serving as a portable terminal to function as a display means, a product registration means for registering products, and a display control means for varying the manner of display performed by the display means depending on whether the portable terminal is in a first holding state in which the portable terminal is held by hand, or a second holding state in which the portable terminal is held by a holding means provided on a mobile object.

In addition, a program for implementing the functions of the above-mentioned store controller 10, transaction management device 20, registration settlement device 30, settlement device 40, transaction status management device 50, mobile terminal 60, weighing and pricing device, 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 perform processing of each of the above-mentioned 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 client when a program is transmitted over a network. The program may also be a program for realizing part of the above-mentioned functions. Furthermore, the program may be a so-called difference file (difference program) that can realize the above-mentioned functions in combination with a program already recorded in the computer system.

1 Product sales data processing system, 10 Store controller, 20 Transaction management device, 40 Payment device, 50 Transaction status management device, 60 Mobile terminal, 70 Shopping cart, 71 Holder, 80 Shopping basket

Claims (8)

A display means;
A product registration means for registering products;
a display control means for changing a display mode displayed by the display means depending on whether the portable terminal is in a first holding state in which the portable terminal is held by hand or a second holding state in which the portable terminal is held by a holding means provided on a moving body ;
The display control means changes a display mode of a product registration screen that presents information about the product registered by the product registration means.
Portable terminal. A display means;
A product registration means for registering products;
a display control means for changing a display mode displayed by the display means depending on whether the portable terminal is in a first holding state in which the portable terminal is held by hand or a second holding state in which the portable terminal is held by a holding means provided on a moving body;
The display control means changes the manner of the display depending on a result of determining whether the holding state is the first holding state or the second holding state based on a detection output from a detection unit.
Portable terminal. A display means;
A product registration means for registering products;
a display control means for changing a display mode displayed by the display means depending on whether the portable terminal is in a first holding state in which the portable terminal is held by hand or a second holding state in which the portable terminal is held by a holding means provided on a moving body;
The display control means causes a settlement device, which performs settlement according to the registration result of the product by the portable terminal, to obtain information indicating the registration result of the product by the portable terminal, to display differently between the first holding state and the second holding state .
Portable terminal. A display means;
A product registration means for registering products;
a display control means for changing a display mode displayed by the display means depending on whether the portable terminal is in a first holding state in which the portable terminal is held by hand or a second holding state in which the portable terminal is held by a holding means provided on a moving body;
The display control means changes a display for connecting a weighing device that weighs the product and the portable terminal so as to be able to communicate with each other between the first holding state and the second holding state.
Portable terminal. Computers as portable terminals,
Display means,
A product registration means for registering products;
a program for causing the portable terminal to function as a display control means for changing a display mode performed by the display means depending on whether the portable terminal is in a first holding state in which the portable terminal is held by hand or a second holding state in which the portable terminal is held by a holding means provided on a moving body,
The display control means changes a display mode of a product registration screen that presents information about the product registered by the product registration means.
program. Computers as portable terminals,
Display means,
A product registration means for registering products;
a program for causing the portable terminal to function as a display control means for changing a display mode performed by the display means depending on whether the portable terminal is in a first holding state in which the portable terminal is held by hand or a second holding state in which the portable terminal is held by a holding means provided on a moving body,
The display control means changes the manner of the display depending on a result of determining whether the holding state is the first holding state or the second holding state based on a detection output from a detection unit.
Program. Computers as portable terminals,
Display means,
A product registration means for registering products;
a program for causing the portable terminal to function as a display control means for changing a display mode performed by the display means depending on whether the portable terminal is in a first holding state in which the portable terminal is held by hand or a second holding state in which the portable terminal is held by a holding means provided on a moving body,
The display control means causes a settlement device, which performs settlement according to the registration result of the product by the portable terminal, to obtain information indicating the registration result of the product by the portable terminal, to display differently between the first holding state and the second holding state.
Program. Computers as portable terminals,
Display means,
A product registration means for registering products;
a program for causing the portable terminal to function as a display control means for changing a display mode performed by the display means depending on whether the portable terminal is in a first holding state in which the portable terminal is held by hand or a second holding state in which the portable terminal is held by a holding means provided on a moving body,
The display control means changes a display for connecting a weighing device that weighs the product and the portable terminal so as to be able to communicate with each other between the first holding state and the second holding state.
Program.

Images