JP2024025324A - Registration device, payment device, and program - Google Patents

Abstract

[Challenge] Supporting smooth transactions. A product sales processing system includes a registration device for registering products and a payment device for paying for the registered products. The registration device includes a registration means, a declaration reception means, and a display means. The registration means registers the product. The declaration receiving means receives a declaration regarding membership from the customer. The display means displays different screens depending on the membership type included in the declaration received by the declaration reception means. [Selection diagram] Figure 7

Description

The present invention relates to a registration device, a payment device, and a program.

In recent years, so-called self-checkout systems, where customers register products and make payments, have become popular. For example, a system is known in which a customer registers a product using a portable registration device owned by the customer, and the customer makes payment using a payment device (for example, see Patent Document 1). Additionally, membership cards may be used in transactions. For example, multiple types of membership cards may be used depending on the membership type.

Japanese Patent Application Publication No. 2016-219034

However, with the conventional technology, depending on the membership type, it may not be possible to make the customer present the membership card at an appropriate timing. For this reason, there is a problem in that presenting the membership card may become complicated for the customer, which may impede smooth transactions.

The present invention has been made in view of these circumstances, and its purpose is to provide a technology that can support smooth transactions.

In order to solve the above problems, a registration device that is one aspect of the present invention is a registration device in a product sales processing system that includes a registration device that registers products and a payment device that pays for the registered products. , a registration means for registering a product, a declaration reception means for accepting a declaration regarding membership from a customer, and a display means for displaying a different screen depending on the membership type included in the declaration received by the declaration reception means. This is a registration device characterized by comprising the following.

In order to solve the above-mentioned problems, a payment device that is one aspect of the present invention includes a registration device that registers products and receives a declaration of membership from a customer, and a payment device that pays for the registered products. A payment device in a product sales processing system comprising: a member type acquisition means for acquiring information indicating the membership type included in the declaration; a display means for displaying an acquisition screen according to the membership type indicated by the information; The payment device is characterized by comprising: member information acquisition means for acquiring member information on an acquisition screen.

In order to solve the above problems, a program that is one aspect of the present invention uses a computer as a registration device in a product sales processing system that includes a registration device that registers products and a payment device that pays for the registered products. A program that causes the computer to function according to a registration means for registering a product, a declaration reception means for accepting a declaration regarding membership from a customer, and a membership type included in the declaration received by the declaration reception means, This program is characterized by functioning as a display means for displaying different screens.

In order to solve the above-mentioned problems, a program that is one aspect of the present invention includes a registration device that registers products and receives a declaration regarding membership from a customer, and a payment device that pays for the registered products. A program for causing a computer to function as a payment device in a product sales processing system, the program comprising: a membership type acquisition means for acquiring information indicating a membership type included in the declaration; and acquisition according to the membership type indicated by the information. This program is characterized in that it functions as a display means for displaying a screen, and a member information acquisition means for acquiring member information on the acquisition screen.

It is an explanatory diagram showing a network configuration of shopping system St. FIG. 2 is an explanatory diagram showing an example of installation of the POS terminal device 20 as seen from the customer side. 3 is a block diagram showing an example of the hardware configuration of a mobile terminal device 30. FIG. It is a sequence diagram showing the basic flow from the start to the end of a transaction in the shopping system St. It is a diagram showing an example of a transaction information DB2 stored in the cloud server 1. It is a block diagram showing the functional configuration of shopping system St. 5 is an explanatory diagram showing an example of screen transitions displayed on the mobile terminal device 30. FIG. 5 is an explanatory diagram showing an example of screen transitions displayed on the mobile terminal device 30. FIG. 3 is an explanatory diagram showing an example of screen transitions displayed on the customer side display section 205 of the POS terminal device 20. FIG. 3 is an explanatory diagram showing an example of screen transitions displayed on the customer side display section 205 of the POS terminal device 20. FIG. It is a flowchart which shows an example of display control processing concerning acquisition of member information performed by portable terminal device 30 concerning a 1st embodiment. It is a flowchart which shows an example of display control processing concerning acquisition of member information performed by portable terminal device 30 concerning a 1st embodiment. 7 is a flowchart illustrating an example of display control processing related to acquisition of member information performed by the POS terminal device 20 according to the first embodiment. FIG. 7 is an explanatory diagram showing an example of screen transitions displayed on the mobile terminal device 30 according to the second embodiment. 3 is an explanatory diagram showing an example of screen transitions displayed on the customer side display section 205 of the POS terminal device 20. FIG. It is a flow chart which shows an example of display control processing concerning acquisition of member information performed by portable terminal device 30 concerning a 2nd embodiment. 12 is a flowchart illustrating an example of display control processing related to acquisition of member information performed by the POS terminal device 20 according to the second embodiment.

DESCRIPTION OF THE PREFERRED EMBODIMENTS A first embodiment and a second embodiment of the present invention will be described below with reference to the accompanying drawings.

(First embodiment)
(Network configuration of shopping system St)
FIG. 1 is an explanatory diagram showing the network configuration of the shopping system St. The shopping system St is an example of a product sales processing system. The shopping system St can be introduced into various stores such as supermarkets, home centers, convenience stores, and various supply stores.

In FIG. 1, the shopping system St includes an external cloud server 1, a store controller 10, a transaction status management device 11, a POS (Point Of Sales) terminal device 20, and a mobile terminal device 30. Each device is a computer device including a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), a communication section, and the like. Each device is communicably connected via a network. For example, the store controller 10, transaction status management device 11, and POS terminal device 20 are each communicably connected via a LAN (Local Area Network) 55.

(Cloud server 1)
The cloud server 1 is a server device that manages various information such as a transaction information DB (database) 2. The various information includes, for example, various information regarding customers and stores, customer membership information, product information (product master) regarding products for each store, and cart information indicating a virtual cart. The member information includes a member number (member identification information), membership type, number of points earned, name, purchase history, point usage history, and the like. The product master is a file that stores product information such as product identification information (for example, JAN (Japanese Article Number) code), product name, and selling price for each product. In addition, the product master includes various information such as product identification information, product name, and unit price of products that need to be weighed.

The cart information includes information on registered products (registered product information) and information necessary for paying for the products. Specifically, cart information is transaction information generated as a virtual cart for each customer. The cart information is updated based on the product code read by the mobile terminal device 30. Cart identification information that identifies one transaction (cart) is assigned to the cart information.

(Store controller 10)
The store controller 10 manages the POS terminal device 20 and a weighing device (not shown) placed in the store, and stores various information necessary for transactions such as product master data. In addition to the product master, the store controller 10 also stores various information such as inventory status, sales history, deposit and withdrawal records, and member information.

(Transaction status management device 11)
The transaction status management device 11 is a monitor that monitors the POS terminal device 20. Specifically, the transaction status management device 11 is capable of displaying the status (processing status) of the POS terminal device 20 and controlling the POS terminal device 20 . Note that the shopping system St may include a clerk terminal device owned by a store clerk instead of or in addition to the transaction status management device 11. For example, the clerk terminal device displays the same content as that displayed on the transaction status management device 11, or notifies the clerk that the clerk will be called.

(POS terminal device 20)
The POS terminal device 20 is an example of a payment device. The POS terminal device 20 is a register device capable of registering products and making payments. The POS terminal device 20 can operate in any one of a plurality of operation modes. The operation modes include, for example, an accounting-only mode, a full-self mode, and a clerk registration mode. Each operation mode will be briefly explained below.

The accounting only mode is a mode for self-accounting. In the accounting-only mode, the customer himself/herself makes payment based on registration information generated by another device, such as the mobile terminal device 30 or a registration device (POS terminal device 20 in clerk registration mode) where a store clerk registers products. It is. The registered information can be acquired by receiving it from the cloud server 1, by receiving it from another POS terminal device 20, by reading a checkout ticket (registered trademark), or the like.
The full self mode is a mode in which a customer registers a product (self-registration) using the own device and performs payment (self-checkout) using the own device. Note that in the full-self mode, self-checkout may be performed based on registration information generated by another device, similar to the checkout-only mode.
The clerk registration mode is a mode in which a clerk registers a product and a customer faces the clerk and makes payment (face-to-face payment). Further, in the clerk registration mode, it is also possible to transmit payment information to other POS terminal devices 20 in the checkout-only mode and to issue a checkout ticket.

In this embodiment, it is assumed that the POS terminal device 20 operates in an accounting-only mode. Note that the POS terminal device 20 may be a dedicated device that only performs self-checkout without having a product registration function. That is, the POS terminal device 20 may be a device dedicated to self-checkout without an operation mode switching function.

(Mobile terminal device 30)
The mobile terminal device 30 is an example of a registration device. The mobile terminal device 30 is a portable computer device such as a smartphone, a tablet device, or a mobile phone. The mobile terminal device 30 includes a communication section, an imaging section (camera), a touch panel, etc., and is operated by a customer. In this embodiment, the mobile terminal device 30 is detachably attached to the shopping cart. Furthermore, the mobile terminal device 30 is a terminal device owned by the customer.

Note that the mobile terminal device 30 includes a rental terminal device that a store lends to a customer. When the rental terminal device is not in use, it is connected to a charger installed at the entrance of a store and charged. The rental terminal is attached to the shopping cart when used. However, the rental terminal device may be installed in the shopping cart, that is, it may be attached to the shopping cart in a non-removable manner.

Application software (hereinafter referred to as "shopping application") for registering products related to the shopping system St and paying for the registered products is installed in the mobile terminal device 30. The mobile terminal device 30 activates the shopping app and scans (reads) the product (barcode) attached to the product, thereby accepting product registration. When the mobile terminal device 30 reads the product code attached to the product, it transmits the read information to the cloud server 1 along with the cart identification information. Thereby, product information corresponding to the product code is registered in the cart information (virtual cart) of the cloud server 1.

Further, when the mobile terminal device 30 receives an operation to complete product registration (start payment), it displays a payment code that is encoded with the cart identification information assigned to the mobile terminal device 30 . The payment code is, for example, a two-dimensional code (QR code (registered trademark)), but may also be a one-dimensional code (barcode). When the POS terminal device 20 reads the payment code, it requests the cloud server 1 to send cart information (transaction information) indicated by the cart identification information. Then, the POS terminal device 20 receives the transaction information from the cloud server 1 in response to the transmission request, and can perform settlement (self-payment) based on the transaction information.

(Example of configuration of POS terminal device 20)
Next, the configuration of the POS terminal device 20 will be explained using FIG. 2.
FIG. 2 is an explanatory diagram showing an example of installation of the POS terminal device 20 as seen from the customer side. Although not shown in FIG. 2, a counter on which a shopping cart is placed is arranged on either side or one side of the POS terminal device 20.

The POS terminal device 20 includes a CPU 201, a ROM 202, a RAM 203, a hard disk 204, a customer side display section 205, a customer side scanner section 206, a card payment section 208, a change machine 209, and a clerk side display section 210. , a key operation section 211, a clerk side scanner section 212, a printing section 213, an audio output section 214, a communication section 215, a camera 216, and a sign pole 220. These can communicate with each other via a bus (not shown).

The CPU 201 is a central processing unit, and controls the operation of the POS terminal device 20 by reading and executing various programs stored in the ROM 202 . The various programs include the display control program according to this embodiment.
The ROM 202 is a read-only memory and stores various information used by the CPU 201 including various programs.

The RAM 203 is a readable and writable memory that stores various information. For example, the RAM 203 stores information acquired from the outside (for example, a product master acquired from the store controller 10, etc.) and information generated during processing. Further, this information includes registration information indicating registered products (purchased products) and settlement information generated by settlement (payment).

Hard disk 204 stores various information. For example, the hard disk 204 stores imaging results (eg, moving images) captured by the camera 216. For example, instead of the ROM 202, the hard disk 204 may store various programs executed by the CPU 201. Furthermore, instead of the RAM 203, the hard disk 204 may store information acquired from the outside or information generated during processing.

The customer side display section 205 is a touch display for customers. The customer side display unit 205 displays various information to the customer and receives various inputs from the customer.

The customer side scanner unit 206 is a scanner unit for customers, and optically reads various information. Various types of information include, for example, the payment code displayed on the mobile terminal device 30, the code printed on the checkout ticket (barcode, two-dimensional code, etc.), cash certificates (gift certificates and coupons), membership information, etc. Includes codes printed on cards, point cards, etc. Note that the customer side scanner unit 206 can also read a product code (barcode) attached to a product during product registration in full self-mode.

The card payment unit 208 is a payment mechanism using various cards. Various cards include membership cards, prepaid cards, credit cards, and point cards. Further, the card payment unit 208 can also perform payment using a contactless charging medium. The contactless charging medium is, for example, a contactless card (IC card) or a mobile terminal device such as a smartphone. Note that the POS terminal device 20 can also perform barcode payment. Barcode payment is a payment made by displaying a barcode on the mobile terminal device 30 that stores the charge amount, and having the customer side scanner section 206 read the barcode, for example.

The change machine 209 is a cash payment mechanism, and has a banknote and coin input port and a banknote and coin discharge port. The change machine 209 calculates the amount of money inserted into the input slot, calculates the amount of change that is the difference between the input amount and the purchase amount, and discharges the change from the output port. The change machine 209 faces the customer and accepts various operations and cash insertions from the customer. Note that the change machine 209 has a sensor that detects banknotes and coins inserted into the input slot. The sensor detects whether banknotes or coins have been inserted into the input slot, and detects the number of coins of each denomination. Further, the change machine 209 can also accept input of cash to be charged to a prepaid card.

The clerk side display section 210 is a touch display for the clerk. The clerk side display section 210 displays various information to the clerk and receives various inputs from the clerk. For example, in the clerk registration mode, the clerk side display section 210 displays a preset key corresponding to the product. When the preset key is pressed, the clerk side display unit 210 accepts registration of the product corresponding to the preset key.

The key operation unit 211 includes various keys (hardware keys, buttons). The key operation unit 211 receives various inputs from the store clerk. The key operation unit 211 includes keys corresponding to products. The key operation unit 211 accepts registration of the product corresponding to the key when the key is pressed by the store clerk. Further, the key operation unit 211 includes a mode switching button and accepts switching of the operation mode.

The clerk side scanner section 212 is a scanner section for the clerk, and optically reads various information. The various information includes, for example, a bar code attached to a product and a clerk code attached to a clerk's name tag. In addition, the various information includes codes printed on accounting tickets, gift certificates, and various cards.

The printing unit 213 prints and outputs various media (receipts, receipts, billing notes, etc.).
The audio output unit 214 outputs sound. For example, the audio output unit 214 outputs audio guidance, warning sounds, and the like. The audio guidance and warning sounds are related to, for example, product registration operations and checkout operations.
The communication unit 215 is an interface that transmits and receives information to and from other devices (cloud server 1, store controller 10, transaction status management device 11, other POS terminal devices 20, mobile terminal device 30, transaction status management device 40, etc.). .

The camera 216 is attached to the upper right of the customer side display section 205. The camera 216 is a camera that continuously captures moving images or still images. As the camera 216, a CCD (charge coupled device) camera or a CMOS (Complementary Metal Oxide Semiconductor) camera can be used. The camera 216 captures images of registered products as well as product registration operations and checkout operations by customers.

The sign pole 220 is, for example, a lamp or an LED (light emitting diode), and is lit in a predetermined lighting manner. The predetermined lighting mode includes a lighting color mode and a blinking mode. Depending on the lighting mode of the sign pole 220, it is indicated that the POS terminal device 20 is in use, or an abnormality is notified. Further, the sign pole 220 is provided at the uppermost position of the POS terminal device 20, so that even a store clerk who is not near the POS terminal device 20 can recognize the lighting mode.

(Hardware configuration of mobile terminal device 30)
Next, the hardware configuration of the mobile terminal device 30 will be explained.
FIG. 3 is a block diagram showing an example of the hardware configuration of the mobile terminal device 30. In FIG. 3, the mobile terminal device 30 includes a CPU 301, a memory 302, an operation unit 303, a communication I/F (interface) 304, a storage medium I/F 305, a display 306, and a camera 307. Furthermore, each of the constituent units 301 to 307 is connected to each other by a bus 320.

The CPU 301 is in charge of overall control of the mobile terminal device 30. Memory 302 includes, for example, ROM, RAM, flash ROM, and the like. For example, a flash ROM or ROM stores various programs. The various programs include the display control program according to this embodiment. A shopping application including a display control program is installed in the mobile terminal device 30 in advance. The RAM is used as a work area for the CPU 301. The program stored in the memory 302 is loaded into the CPU 301 and causes the CPU 301 to execute the coded processing.

The operation unit 303 includes a touch panel and operation buttons. Note that in addition to the operation unit 303, the input device includes a microphone for inputting audio.
Communication I/F 304 is connected to a network such as the Internet through a communication line, and is connected to other devices (for example, cloud server 1, etc.) via the network. Further, the communication I/F 304 serves as an interface between the network and the inside of the device itself, and controls input/output of data from other devices.

The storage medium I/F 305 controls reading and writing of data to and from a storage medium (not shown) such as a magnetic disk and an optical disk under the control of the CPU 301 .
Display 306 is included in the output device for displaying images. Note that the output device includes a speaker in addition to the display 306.

A camera 307 images a subject. A camera 307 captures moving images or still images. The camera 307 reads the product code attached to the product. Note that the mobile terminal device 30 may include a scanner instead of or in addition to the camera 307. The scanner is provided, for example, at the upper end of the housing of the mobile terminal device 30, and reads a product code (barcode) attached to a product. As the reading method of the scanner, for example, a laser method or a CCD method can be adopted.

(About the basic flow from the start to the end of transactions in shopping system St)
FIG. 4 is a sequence diagram showing the basic flow from the start to the end of a transaction in the shopping system St. In FIG. 4, a flow will be described in which a customer visits a store, registers a product to be purchased using the mobile terminal device 30, and completes payment at the POS terminal device 20.

Step S401: First, the mobile terminal device 30 starts the shopping application and accepts the start of a transaction by pressing the shopping start button 711 (FIG. 7(A)).
Step S402: The mobile terminal device 30 acquires store identification information (store ID). The store identification information is represented by, for example, a store identification code such as a two-dimensional code. The store identification code is displayed, for example, on a display installed near the entrance of the store or on a paper medium affixed near the entrance of the store. The customer operates the mobile terminal device 30 to cause the camera 307 to read the store identification code. Thereby, the mobile terminal device 30 acquires the store identification information. Note that the information identifying the store may be any information that can uniquely identify the store, and is not limited to store identification information, and may be, for example, location information of the mobile terminal device 30.

Step S403: Next, the mobile terminal device 30 displays the member confirmation reception screen 720 (FIG. 7(B)) and receives a declaration regarding membership (hereinafter referred to as "membership declaration information"). The membership declaration information includes information indicating whether the person is a member or a non-member, and information indicating the type of membership in the case of a member customer.

Here, the membership type included in the membership declaration information will be explained in detail. Membership types include, for example, store members, application-related members, and electronic money-related members.
A store member is a member registered at a store. Store members are given benefits such as points and discounts that can be used at the store. In addition, store members are given a plate-shaped store membership card. The store membership card stores member information including information indicating that the person is a store member. The store membership card is, for example, a card that does not have a cash charging function.

An app member is a member registered in a group affiliated with multiple stores. It does not matter whether or not there is a capital alliance between stores belonging to the group. Furthermore, a group may be made up of brands (chain stores or affiliated stores) that are under the umbrella of one company that operates a food and beverage business, or may be made up of brands that are placed under the respective umbrellas of different companies. . App members will receive benefits such as points and discounts that can be used in groups. App members are given a plate-shaped app membership card. The application membership card stores member information including information indicating that the user is an application membership.

The application membership card also includes a mobile terminal device 30 displaying member information. Specifically, a group application (hereinafter referred to as "group application") is installed on the mobile terminal device 30 of the application member. The mobile terminal device 30 can display member information on the display 306 by starting the group application. The member information to be displayed is represented by, for example, a two-dimensional code (membership code). The application membership card includes a membership code displayed on the mobile terminal device 30. The application membership card is, for example, a card that does not have a cash charging function.

An electronic money member is a member who can make payments using electronic money used at affiliated stores. Electronic money members are given benefits such as points and discounts that can be used at affiliated stores. Further, electronic money members are provided with a plate-shaped electronic money member card (for example, a distribution card). Distribution cards are cards issued by retailers such as supermarkets and convenience stores. The electronic money membership card stores member information including information indicating that the user is an electronic money membership. An electronic money membership card is, for example, a card that has a cash charging function.

Note that the electronic money membership card may include the mobile terminal device 30. Specifically, the electronic money member's mobile terminal device 30 may have, for example, a retailer's app (hereinafter referred to as "retail business app") installed therein. The mobile terminal device 30 can display member information on the display 306 by activating the retail business application. The member information to be displayed is represented by, for example, a two-dimensional code (membership code). Furthermore, the mobile terminal device 30 may display a barcode payment code (payment code) on the display 306 in the retail business application. In this way, the retail membership card may include a membership code and a payment code that are displayed on the mobile terminal device 30.

Note that various cards may store all information included in member information (membership number, membership type, number of points earned, name, purchase history, point usage history, etc.), or for example, may store only the membership number. You may also choose to memorize it. If only the membership number is to be stored, other information (membership type, name, etc.) linked to the membership number may be stored in an external device such as the cloud server 1, for example. In this case, the device that has read the membership number may inquire of the external device for other information linked to the read membership number and acquire the other information from the external device. Furthermore, the member information may be stored in the group application or retail application described above.

The mobile terminal device 30 that received the membership declaration information in step S403 requests the cloud server 1 to start a transaction. The transaction start request includes store identification information, membership declaration information, and customer identification information (customer ID) that identifies the mobile terminal device 30 (customer).

Step S404: Upon receiving customer identification information, membership declaration information, and store identification information from the mobile terminal device 30 as a request to start a transaction, the cloud server 1 generates cart information for the transaction. Cart information is included in transaction information. Here, transaction information will be explained in detail using FIG. 5.

FIG. 5 is a diagram showing an example of the transaction information DB2 stored in the cloud server 1. In FIG. 5, the transaction information DB2 includes items of customer identification information, store identification information, membership declaration information, and cart information. The cart information includes items such as cart identification information, registration date and time, registered product information, and pending product information.
The cart identification information is cart identification information that identifies the virtual cart.
The registration date and time indicates the date and time when the product was registered by the mobile terminal device 30.
The registered product information indicates product information registered by the mobile terminal device 30, and specifically includes a product code, product name, price, and the like.
The pending product information indicates product information of the pending product. Pending products are products that require confirmation by a store clerk at the time of checkout, and include, for example, age-verified products, medicines, products with security tags, and products to be returned.

Returning to FIG. 4, the processing after step S405 will be described.
Step S405: The mobile terminal device 30 scans the product and registers the product in response to the customer's operation. Specifically, scanning a product means reading a product code (barcode) attached to the product. When the product is scanned, the mobile terminal device 30 transmits product reading information including the product code, cart identification information, and membership type to the cloud server 1 .

Step S406: Upon receiving the product reading information from the mobile terminal device 30, the cloud server 1 updates the registered product information in the transaction information DB 2 with a price according to the membership type. Specifically, the cloud server 1 specifies cart information including the received cart identification information from among the transaction information in the transaction information DB 2, and updates registered product information in the specified cart information.
Step S407: The cloud server 1 transmits the specified registered product information to the mobile terminal device 30.
Step S408: Upon receiving the registered product information from the cloud server 1, the mobile terminal device 30 displays the product information (product and price) of the scanned product based on the received registered product information.

Step S409: The mobile terminal device 30 repeats the processes of step S405 and step SS408 until the start of payment. The start of payment is to accept an operation indicating the start of payment, and specifically, to press the payment start button 813 (FIG. 8(A)) displayed on the display 306. When the registration of the product is completed, the mobile terminal device 30 generates a payment code 822 (FIG. 8(B)) and displays it on the display 306.

Step S410: When the customer holds the payment code over the customer side scanner unit 206 of the POS terminal device 20, the POS terminal device 20 reads the payment code displayed on the mobile terminal device 30. The payment code includes cart identification information and information for the POS terminal device 20 to request transmission of transaction information from the cloud server 1.
Step S411: Upon reading the payment code, the POS terminal device 20 requests the cloud server 1 to send transaction information. The transaction information transmission request includes cart identification information.

Step S412: Upon receiving the transaction information transmission request from the POS terminal device 20, the cloud server 1 specifies the transaction information using the cart identification information included in the transaction information transmission request.
Step S413: After specifying the transaction information, the cloud server 1 transmits the specified transaction information to the POS terminal device 20.

Step S414: Upon receiving the transaction information from the cloud server 1, the POS terminal device 20 displays a payment screen showing the transaction information.
Step S415: The POS terminal device 20 executes payment processing according to the customer's operation. When the POS terminal device 20 executes the payment process, it transmits a transaction completion notification including cart identification information to the cloud server 1.

Step S416: Upon receiving the transaction end notification from the POS terminal device 20, the cloud server 1 transmits the transaction end notification to the mobile terminal device 30.
Step S417: Upon receiving the transaction end notification from the cloud server 1, the mobile terminal device 30 ends the transaction.

(Regarding presentation of membership card)
Here, in transactions related to the shopping system St, depending on the membership type, it may not be possible to make the customer present the membership card at an appropriate timing. For example, if the mobile terminal device 30 accepts a declaration of membership and prompts the customer to present the membership card, depending on the membership type, the customer may have to present the same membership card multiple times in one transaction. Sometimes it happens. Specifically, in the case of an e-money member, if the user is prompted to present an e-money member card at the mobile terminal device 30 when registering a product, the card will also be used for payment at the POS terminal device 20. In this case, the customer will present the card twice.

Further, regarding the membership code of the application membership card displayed in the group application, it may be difficult to display it on the display 306 because the shopping application is being activated during shopping according to this embodiment.
As described above, in transactions related to the shopping system St, depending on the membership type, it may not be possible to make the customer present the membership card at an appropriate timing. For this reason, presenting the membership card may become complicated for the customer, which may hinder smooth transactions.

Therefore, in this embodiment, the troublesomeness of presenting a membership card is suppressed and smooth transactions are supported. Specifically, when the portable terminal device 30 receives a declaration of membership, an optimal screen according to the membership type is displayed. The functional configuration of the shopping system St shown in FIG. 6 will be described below with reference to screen transition diagrams shown in FIGS. 7 to 10.

FIG. 6 is a block diagram showing the functional configuration of the shopping system St.
7 and 8 are explanatory diagrams showing an example of screen transitions displayed on the mobile terminal device 30.
In the shopping system St, the mobile terminal device 30 includes a registration section 601, a declaration reception section 602, a display section 603, and an output section 604. Each part is realized by the CPU 301. That is, the CPU 301 executes the display control program stored in the memory 302 to realize the functions of each part. The POS terminal device 20 also includes a membership type acquisition section 611, a display section 612, and a membership information acquisition section 613. Each part is realized by the CPU 201. That is, the functions of each part are realized by the CPU 201 executing a display control program stored in the RAM 203 or the like.

(About product registration)
The registration unit 601 registers products received on the registration screen 810 (FIG. 8(A)) from customers shopping while walking around the store. Specifically, the registration unit 601 registers the product by displaying the registration screen 810 and capturing an image of the product code in the imaging area 811.

(About accepting membership declarations)
The declaration receiving unit 602 receives a declaration regarding membership (membership declaration information) from a customer during product registration. The timing at which the declaration reception unit 602 receives the declaration is at the start of product registration. However, the timing is not limited to the start of product registration, but may be in the middle of product registration, for example, before the checkout start button 813 in FIG. 8(A) is pressed.

The declaration regarding membership includes a declaration indicating whether the person is a member or a non-member, and a declaration indicating the type of membership in the case of being a member customer. The transition from the top screen to the membership declaration information reception screen will be described below.
FIG. 7(A) shows a top screen 710. Top screen 710 includes a shopping start button 711. The shopping start button 711 is a button that accepts the start of a new transaction. When the shopping start button 711 is pressed, the screen changes to a member confirmation reception screen 720 shown in FIG. 7(B).

FIG. 7(B) shows a member confirmation reception screen 720. The member confirmation reception screen 720 is a screen for accepting a declaration regarding membership. The member confirmation reception screen 720 includes a member type selection button 721. The membership type selection buttons 721 include a store membership card button 721a that indicates store membership, an application membership button 721b that indicates application membership, and an electronic money membership button 721b that indicates electronic money membership. 721c, and a non-member button 721d indicating that the user does not have a membership card.

(About displaying different screens depending on membership type)
The display unit 603 displays different screens (member information acquisition screen 730 or member information guide screen 740) depending on the membership type included in the declaration received by the declaration reception unit 602. This will be explained in detail.
When the store membership card button 721a is pressed, the screen changes to a member information acquisition screen 730 shown in FIG. 7(C). Further, when the application member button 721b or the electronic money member button 721c is pressed, the screen changes to a member information guide screen 740 shown in FIG. 7(D). Further, when the non-member button 721d is pressed, the screen changes to a registration screen 810 in FIG. 8(A).

FIG. 7C shows a member information acquisition screen 730 (an example of an acquisition screen). The member information acquisition screen 730 is a screen for acquiring member information, and specifically, it is a screen that prompts the user to read the store membership card. Member information acquisition screen 730 includes an imaging area 731, an input button 732, and a cancel button 733. The imaging area 731 is an area where the barcode attached to the store membership card can be imaged (read) by the function of the camera 307 of the mobile terminal device 30. When the mobile terminal device 30 reads the barcode attached to the store membership card in the imaging area 731, it stores the membership information including the membership number and membership type, and transitions to the registration screen 810 in FIG. 8(A).

The input button 732 is a button that accepts direct input of a membership number. When the input button 732 is pressed, the screen changes to an input screen that accepts direct input of the membership number.

The cancel button 733 is a button for accepting cancellation of store membership card reading. When the cancel button 733 is pressed, the screen returns to the member confirmation reception screen 720 shown in FIG. 7(B). Regarding returning to the member confirmation reception screen 720, the functional configuration will be explained. The display unit 603 displays the member confirmation reception screen 720 when the member information cannot be acquired on the member information acquisition screen 730. The case where member information cannot be obtained means pressing the cancel button 733, but is not limited to this, and may also be, for example, when a predetermined period of time has elapsed.

In this way, when the store membership card button 721a is pressed on the member confirmation reception screen 720 (FIG. 7(B)), the screen changes to the member information acquisition screen 730 (FIG. 7(C)). This allows store members to obtain member information at the time of starting product registration. Therefore, when registering a product on the mobile terminal device 30, a member price corresponding to the store member can be displayed to the store member. Further, the store membership card cannot be used for payment. Therefore, by outputting the member information from the mobile terminal device 30 to the POS terminal device 20, the POS terminal device 20 can acquire the member information even if the customer does not present the store membership card at the time of payment. .

FIG. 7(D) shows a member information guide screen 740. The member information guide screen 740 is a guide screen for acquiring member information with another device, and specifically, it is a screen indicating that member information is to be read at the time of payment. The member information guide screen 740 includes a shopping start button 741. The shopping start button 741 is a button for accepting the start of shopping. When the shopping start button 741 is pressed, the screen changes to a registration screen 810 in FIG. 8(A).

In this way, when the application membership button 721b or the electronic money membership button 721c is pressed on the membership confirmation reception screen 720 (FIG. 7(B)), the membership information information screen 740 (FIG. 7(D)) is displayed. Transition.

Here, as described above, the application membership card includes the membership code displayed on the mobile terminal device 30. While shopping, since the shopping app is activated, it is difficult to activate the group app and display the membership code. From this point of view, in this embodiment, member information is not acquired for application-related members at the time of starting product registration.

Furthermore, electronic money membership cards are used at the time of payment. If the electronic money membership card is read at the beginning of product registration, the customer would be required to present the electronic money membership card twice, once at the start of product registration and at the time of checkout. However, it is complicated. From this point of view, in this embodiment, member information is not acquired for electronic money members at the time of starting product registration.

Furthermore, membership prices can be displayed for application-related members and electronic money-related members in accordance with the membership type during product registration on the mobile terminal device 30. Further, by outputting information indicating the accepted membership type from the mobile terminal device 30 to the POS terminal device 20, the POS terminal device 20 can display a screen prompting the user to present a membership card according to the membership type.

(About the product registration screen)
FIG. 8(A) shows a registration screen 810. The registration screen 810 includes an imaging area 811, a total display area 812, a payment start button 813, and a registered product display area 814.
The imaging area 811 is an area where a barcode attached to a product can be imaged (read) by the function of the camera 307 of the mobile terminal device 30.
The total display area 812 is an area that shows the total number and total price of various registered products.
The checkout start button 813 is a button that accepts the start of checkout (completion of product registration).
The registered product display area 814 is an area where the product name, quantity, price, etc. of the registered product are displayed. In the registered product display area 814, products are displayed in the order in which they are registered. Specifically, the most recently registered product is displayed above the registered product display area 814, and the first registered product is displayed below the registered product display area 814. If there are a large number of registered products, the product that was registered earlier may not be displayed in the registered product display area 814 (it may be outside the screen).

The registration unit 601 transmits the product code imaged (read) in the imaging area 811 of the registration screen to the cloud server 1. Then, the registration unit 601 registers the product by receiving product information (registered product information) corresponding to the product code from the cloud server 1. The registration unit 601 registers and displays products at membership prices according to membership types. Specifically, the price displayed in the registered product display area 814 is displayed at a member price according to the membership type if the member is a member, and at a regular price if the member is a non-member.

When the registration unit 601 completes product registration, the mobile terminal device 30 displays the payment code. Specifically, when the start payment button 813 is pressed on the registration screen 810, the screen transitions to a payment code screen 820 (FIG. 8(B)). Note that when the start payment button 813 is pressed, the mobile terminal device 30 calculates points to be given to the member customer in this transaction according to the membership type. Furthermore, the mobile terminal device 30 may display the calculated points on the display 306. Furthermore, the mobile terminal device 30 may accept an input of the number of points to be used among the displayed points. The number of points accepted may be included in the payment code. Note that the point calculation is not limited to being performed by the mobile terminal device 30, and may be performed by the cloud server 1 or the POS terminal device 20.

(About display of payment code)
The output unit 604 outputs information (transaction request information) including information indicating the membership type accepted by the declaration reception unit 602 and registration information (cart identification information) registered by the registration unit 601. The output unit 604 encodes and outputs the transaction request information. The output mode of the transaction request information by the output unit 604 is not limited to a code, and may be a communication. Communication may be wired or wireless. Furthermore, wireless is, for example, short-range wireless communication.

FIG. 8(B) shows a payment code screen 820. The payment code screen 820 includes a guide display 821, a payment code 822, and a registration return button 823.
The guidance display 821 shows a guidance to cause the POS terminal device 20 to read the payment code 822. The settlement code 822 is a code symbol that identifies one transaction. The settlement code 822 is coded transaction request information. The transaction request information includes cart identification information as registration information and member declaration information. The member declaration information includes member information (including information indicating membership type) if the member is a store member. Further, the membership declaration information includes information indicating the membership type if the member is an application member or an electronic money member, and includes information indicating the non-member if the member is a non-member. The registration return button 823 is a button that accepts returning to the registration screen 810 (FIG. 8(A)).

(About the screen of the POS terminal device 20)
The membership type acquisition unit 611 acquires information related to the declaration of membership accepted by the mobile terminal device 30 (membership declaration information). Specifically, the membership type acquisition unit 611 acquires membership declaration information included in the payment code 822. The display unit 612 displays an acquisition screen according to the membership type indicated by the membership declaration information acquired by the membership type acquisition unit 611. The member information acquisition unit 613 acquires member information on the acquisition screen. The screen transitions displayed on the customer side display section 205 of the POS terminal device 20 will be described below with reference to FIG.

9 and 10 are explanatory diagrams showing an example of screen transitions displayed on the customer side display section 205 of the POS terminal device 20.
FIG. 9A shows a standby screen 910 displayed on the customer side display section 205 of the POS terminal device 20. The standby screen 910 includes a notification prompting the customer side scanner unit 206 to read the payment code 822 (FIG. 8(B)). For example, the POS terminal device 20 displays the standby screen 910 in a standby state in the accounting-only mode. On the standby screen 910, when the customer scans the payment code 822 displayed on the mobile terminal device 30 by the customer scanner unit 206, the screen shown in FIGS. 9(B), (C), and (D) is displayed depending on the membership type. Transit to one of the screens shown.

FIG. 9B shows a member information acquisition screen 920 that is displayed when the membership type accepted by the mobile terminal device 30 is an application-related member. The member information acquisition screen 920 is a screen that prompts the user to read the member information of the application member. The POS terminal device 20 reads the membership information of the application member from the application member card. Note that, as described above, the application membership card includes a two-dimensional code (membership code) displayed on the display 306 in the group application of the mobile terminal device 30.

When the reading of the member information of the application member is completed, the screen changes to a small plan screen 940 shown in FIG. 9(D). In this case, in the same way as the membership price of the application-related member displayed on the mobile terminal device 30, the membership price of the application-related member is applied to the small plan screen 940 as well. Also, when the cancel button 921 is pressed on the member information acquisition screen 920, the screen changes to a small plan screen 940 shown in FIG. 9(D). However, in this case, unlike the membership price displayed on the mobile terminal device 30, the regular price will be applied on the small plan screen 940.

FIG. 9C shows a member information guide screen 930 that is displayed when the member type accepted by the mobile terminal device 30 is an electronic money member. The member information guide screen 930 is a screen that guides the user to read the member information of the electronic money member after selecting the payment type. After the member information guidance screen 930 is displayed, when a predetermined period of time has elapsed (or when a confirmation button for receiving confirmation from the customer is pressed, the button is pressed), the screen shown in FIG. 9(D) is displayed. The screen changes to a small plan screen 940 shown in FIG. In this case, in the same way as the electronic money membership price displayed on the mobile terminal device 30, the electronic money membership price is applied on the small screen 940 as well.

FIG. 9(D) shows a small plan plane 940. The small plan screen 940 can be used for transitions from the member information acquisition screen 920 in FIG. 9(B) and from the member information guide screen 930 in FIG. 9(C), as well as the standby screen in FIG. 9(A). There is also a mode in which the transition occurs from 910. Specifically, if the membership type accepted by the mobile terminal device 30 is a store member or a non-member, when the payment code 822 is read on the standby screen 910 in FIG. Transition to.

The small plan screen 940 includes a registered product display area 941 and a checkout start button 942. The registered product display area 941 not only shows the product name, number of purchased items, and purchase price for each registered product, but also shows the total number of registered products, the total amount of money, and the like. The purchase amount and total amount are displayed as an amount according to the membership type, and for non-members, the regular price is displayed. The customer checks the registered product display area 941, and if the registered product is correct, presses the checkout start button 942.

When the payment start button 942 is pressed on the small plan screen 940, the screen transitions to a payment type selection screen 1010 in FIG. 10(A).
FIG. 10(A) shows a payment type selection screen 1010. The payment type selection screen 1010 includes a payment type selection button 1011. A payment type selection button 1011 accepts selection of a payment type. Specifically, the payment type selection button 1011 accepts one payment type among cash, credit card, and electronic money, for example. When electronic money is selected using the payment type selection button 1011, the screen transitions to a guide screen 1020 shown in FIG. 10(B). When cash is selected using the payment type selection button 1011, the screen transitions to a payment screen 1030 in FIG. 10(C).

FIG. 10(B) shows a guide screen 1020. The guide screen 1020 is a screen that prompts the user to read the charge medium. When reading the charge medium, member information is also read at the same time. When the payment based on the charging medium is completed, the POS terminal device 20 issues a receipt and ends the transaction. When the transaction is completed, the screen returns to the standby screen shown in FIG. 9(A). In this way, in the case of e-money membership, in a series of transactions, the customer only needs to present the e-money membership card once at the time of payment to have the payment and member information read, thereby simplifying the procedure. Simplification can be achieved.

Note that in the case of an electronic money member, since there is a high possibility that payment will be made with electronic money, the payment type selection screen 1010 may be skipped and the transition to the guidance screen 1020 may be made. Specifically, in the case of an electronic money member, when the payment start button 942 is pressed on the sub-plan screen 940 (FIG. 9(D)), the payment type selection screen 1010 is skipped and the transition is made to the guidance screen 1020. Just do it like this.

FIG. 10(C) shows the payment screen 1030. Settlement screen 1030 includes an amount area 1031 and an end button 1032. The amount area 1031 is an area for displaying the total payment amount, deposit amount, and change amount. The end button 1032 is a button that accepts confirmation of the amount displayed in the amount area 1031. When the end button 1032 is pressed, a receipt is issued and the transaction ends. Note that when a credit card is selected as the payment type, the payment is completed by inserting the credit card into the card payment unit 208.

(Example of display control processing related to acquisition of member information performed by mobile terminal device 30)
FIGS. 11A and 11B are flowcharts illustrating an example of display control processing related to acquisition of member information performed by the mobile terminal device 30 according to the first embodiment. 11A and 11B, the mobile terminal device 30 determines whether or not the start of a transaction has been accepted on the top screen 710 (FIG. 7(A)) (step S1101). The mobile terminal device 30 waits until accepting the start of a transaction (step S1101: NO). When accepting the start of a transaction (step S1101: YES), the mobile terminal device 30 displays a member confirmation reception screen 720 (FIG. 7(B)) (step S1102).

Then, the mobile terminal device 30 determines whether a store member (store membership card button 721a) is selected (step S1103). If a store member is selected (step S1103: YES), the mobile terminal device 30 displays the member information acquisition screen 730 (FIG. 7(C)) (step S1104). Then, the mobile terminal device 30 determines whether the member information of the store member has been acquired (step S1105). If the member information of the store member is acquired (step S1105: YES), the mobile terminal device 30 proceeds to the process of step S1110.

On the other hand, if the member information of the store member is not acquired (step S1105: NO), the mobile terminal device 30 determines whether pressing of the cancel button 733 has been accepted (step S1106). If pressing the cancel button 733 is not accepted (step S1106: NO), the mobile terminal device 30 returns to the process of step S1105. On the other hand, if the press of the cancel button 733 is accepted (step S1106: YES), the mobile terminal device 30 returns to the process of step S1102 and displays the member confirmation reception screen 720 (FIG. 7(B)).

In step S1103, if a store member is not selected (step S1103: NO), the mobile terminal device 30 determines whether an app member or an electronic money member is selected (step S1107). If an app member or an electronic money member is selected (step S1107: YES), the mobile terminal device 30 displays a member information guide screen 740 (FIG. 7(D)), and a shopping start button 741 is pressed. Depending on the situation, the process advances to step S1110.

On the other hand, if an application member or an electronic money member is not selected (step S1107: NO), the mobile terminal device 30 determines whether a non-member is selected (step S1109). If a non-member is not selected (step S1109: NO), the mobile terminal device 30 returns to the process of step S1103. On the other hand, if a non-member is selected (step S1109: YES), the mobile terminal device 30 displays the registration screen 810 (FIG. 8(A)) (step S1110).

Then, the mobile terminal device 30 determines whether the product has been scanned in accordance with the customer's operation on the registration screen 810 (step S1121). If the product is not scanned (step S1121: NO), the mobile terminal device 30 proceeds to the process of step S1129. On the other hand, when the product is scanned (step S1121: YES), the mobile terminal device 30 displays the scanned product by transmitting product reading information to the cloud server 1 and receiving registered product information from the cloud server 1. .

The display based on the registered product information received from the cloud server 1 will be explained in detail. If the customer is not a member (step S1122: NO), the product is registered and displayed at the regular price (step S1123). On the other hand, if the customer is a member (step S1122: YES) or a store member (step S1124: YES), products are registered and displayed at the member price of the store member (step S1125).

If the user is not a store member (step S1124: NO), and if the user is an app member (step S1126: YES), products are registered and displayed at the member price of the app member (step S1127). If the user is not an application member (step S1126: NO), that is, if the user is an electronic money member, the product is registered and displayed at the member price of the electronic money member (step S1128).

Then, the mobile terminal device 30 determines whether or not the payment is started by pressing the payment start button 813 (FIG. 8(A)) (step S1129). If it is not the start of payment (step S1129: NO), the mobile terminal device 30 returns to the process of step S1121. If the payment is to be started (step S1129: YES), the mobile terminal device 30 refers to the membership type accepted on the membership confirmation reception screen 720 (FIG. 7(B)) and determines whether the customer is a member. (Step S1130).

If the customer is a member (step S1130: YES), the mobile terminal device 30 calculates points to be given in this transaction according to the membership type (step S1131). Then, the mobile terminal device 30 receives the membership type (membership declaration information) accepted on the membership confirmation reception screen 720 (FIG. 7(B)), point information indicating the calculated points, and registration information (cart identification information). The payment code 822 encoded is displayed on the display 306 (step S1132), and the series of processing ends.

On the other hand, if the customer is not a member (step S1130: NO), the mobile terminal device 30 determines the membership type (membership declaration information: information indicating non-membership) received on the membership confirmation reception screen 720 (FIG. 7(B)). , and the registration information (cart identification information) are displayed on the display 306 (step S1133), and the series of processing ends.

(Example of display control processing related to acquisition of member information performed by POS terminal device 20)
FIG. 12 is a flowchart illustrating an example of display control processing related to acquisition of member information performed by the POS terminal device 20 according to the first embodiment. In FIG. 12, the POS terminal device 20 determines whether transaction information has been acquired from the cloud server 1 based on the transaction request information obtained by scanning the payment code 822 (FIG. 7(B)). Step S1201). The POS terminal device 20 waits until the transaction information is acquired (step S1201: NO).

Upon acquiring the transaction information (step S1201: YES), the POS terminal device 20 refers to the membership declaration information included in the payment code 822 and determines whether the customer is a member (step S1202). If the customer is not a member (step S1202: NO), the POS terminal device 20 displays the small plan screen 940 (FIG. 9(D)) (step S1209). In this case, the small plan screen 940 is displayed at the normal price. On the other hand, if the customer is a member (step S1202: YES), the POS terminal device 20 determines whether the customer is a store member (step S1203).

If the customer is a store member (step S1203: YES), since member information is included in the payment code 822, the mobile terminal device 30 proceeds to step S1209 and displays the small plan screen 940 (FIG. 9(D). )). In this case, the small plan screen 940 is displayed at the member price of the store member. On the other hand, if the customer is not a store member (step S1203: NO), the mobile terminal device 30 determines whether the customer is an app member (step S1204).

If the customer is an app member (step S1204: YES), the POS terminal device 20 displays the member information acquisition screen 920 (FIG. 9(B)) of the app member (step S1206), and performs the processing in step S1207. Proceed to. On the other hand, if the customer is not an app member (step S1204: NO), that is, if the customer is an electronic money member, the POS terminal device 20 displays the electronic money member's member information guidance screen 930 (FIG. 9). (C)) is displayed (step S1205), and the process proceeds to step S1209.

In step S1207, the POS terminal device 20 determines whether member information has been acquired on the member information acquisition screen 920 displayed in step S1206 (step S1207). If the member information is acquired (step S1207: YES), the POS terminal device 20 displays the small plan screen 940 (FIG. 9(D)) (step S1209). In this case, the small plan screen 940 is displayed at a membership price according to the membership type.

On the other hand, if member information is not acquired (step S1207: NO), the POS terminal device 20 determines whether pressing of the cancel button 921 (FIGS. 9C and 9D) has been accepted (step S1208). If the press of the cancel button 921 is not accepted (step S1208: NO), the POS terminal device 20 returns to the process of step S1207. On the other hand, if the press of the cancel button 921 is accepted (step S1208: YES), the POS terminal device 20 displays the small plan screen 940 (FIG. 9(D)) (step S1209). In this case, the small plan screen 940 is displayed at the regular price.

Next, the POS terminal device 20 determines whether the payment start button 942 has been pressed on the small plan screen 940 (step S1210). The POS terminal device 20 waits until the start payment button 942 is pressed (step S1210: NO), and when the start payment button 942 is pressed (step S1210: YES), the POS terminal device 20 changes the membership type to electronic. It is determined whether the user is a money member (step S1211).

If the member type is an electronic money member (step S1211: YES), there is a high possibility that the payment type will be electronic money, so the POS terminal device 20 advances to step S1214 and accepts payment using electronic money. Note that when paying with electronic money, the charge amount and member information stored in the electronic money membership card are read at the same time. On the other hand, if the member type is not an electronic money member (step S1211: NO), the POS terminal device 20 displays the payment type selection screen 1010 (FIG. 10(A)) (step S1212), and selects the payment type. (Step S1213).

The POS terminal device 20 then determines whether the payment has been completed (step S1214). The POS terminal device 20 waits until the payment is completed (step S1214: NO), and when the payment is completed (step S1214: YES), the series of processes ends.

As described above, the mobile terminal device 30 according to the present embodiment accepts a declaration indicating membership from a customer during product registration, and displays different screens depending on the membership type included in the declaration. This makes it possible to display an optimal screen for acquiring member information depending on the membership type. Therefore, it is possible to reduce the number of times a customer presents the same membership card in one transaction. Therefore, it is possible to suppress the trouble associated with presenting a membership card and to support smooth transactions.

In addition, the mobile terminal device 30 according to the present embodiment can display member information on an acquisition screen (member information acquisition screen 730 in FIG. 7C) or on another device depending on the membership type. A guidance screen (member information guidance screen 740 in FIG. 7(D)) for obtaining the information is displayed. Thereby, notification regarding the presentation of the membership card can be made at the time of product registration or at the time of checkout, depending on the membership type. Therefore, it is possible to have the customer present the membership card at an appropriate timing depending on the membership type.

In addition, when the mobile terminal device 30 according to the present embodiment cannot acquire member information on the acquisition screen (member information acquisition screen 730 in FIG. 7(C)), the mobile terminal device 30 displays a screen for accepting membership type (FIG. 7(B)). A member confirmation reception screen 720) is displayed. This allows the customer to select the membership type again.

Furthermore, the mobile terminal device 30 according to the present embodiment outputs transaction request information (payment code 822) including information indicating the accepted membership type and registration information (cart identification information). Thereby, by outputting information indicating the membership type from the mobile terminal device 30 to the POS terminal device 20, the POS terminal device 20 can prompt the presentation of a membership card according to the membership type.

Further, the POS terminal device 20 according to the present embodiment acquires the membership type accepted by the mobile terminal device 30, displays an acquisition screen (membership information acquisition screen 920 in FIG. 9B) according to the membership type, Obtain member information on the acquisition screen. Thereby, it is possible to display an optimal acquisition screen according to the membership type acquired from the mobile terminal device 30. Moreover, since the POS terminal device 20 can acquire member information read by the mobile terminal device 30 from the mobile terminal device 30 for store members, an acquisition screen related to acquiring member information can be omitted.

(Second embodiment)
Next, a second embodiment will be described. Note that, in the second embodiment, descriptions of the contents described in the first embodiment described above are omitted as appropriate. Furthermore, it is also possible to appropriately combine the second embodiment and the first embodiment described above.

In the first embodiment described above, an example was described in which the mobile terminal device 30 receives the membership type. In the second embodiment, an example will be described in which the POS terminal device 20 receives the membership type.

FIG. 13 is an explanatory diagram showing an example of screen transitions displayed on the mobile terminal device 30 according to the second embodiment. FIG. 13(A) shows a top screen 710 similar to FIG. 7(A). When the shopping start button 711 is pressed on the top screen 710, the screen changes to a member confirmation reception screen 1320 shown in FIG. 13(B).

FIG. 13(B) shows a member confirmation reception screen 1320. The member confirmation reception screen 1320 is a screen for accepting whether or not the user is a member. The member confirmation reception screen 1320 includes a member declaration button 1321 and a non-member declaration button 1322. The member declaration button 1321 is a button for accepting a declaration of membership. The non-member declaration button 1322 is a button for accepting a declaration of being a non-member. When either the member declaration button 1321 or the non-member declaration button 1322 is selected, the screen transitions to the registration screen 810 in FIG. 13(C).

FIG. 13(C) shows a registration screen 810 similar to FIG. 8(A). The price displayed in the registered product display area 814 is displayed at the member price if the declaration of membership is accepted, and the regular price is displayed if the declaration of non-membership is accepted. When the start payment button 813 is pressed on the registration screen 810, the screen transitions to a payment code screen 820 (FIG. 13(D)). Note that the membership price may be, for example, a price that is commonly applied to all members (store members, app members, and electronic money members), or may be a price that is applied based on the usage history of the customer who uses the mobile terminal device 30. It may also be a price for a membership type that can be estimated.

FIG. 13(D) shows a payment code screen 820 similar to FIG. 8(B). In the payment code screen 820, the payment code 822 includes membership declaration information. The membership declaration information includes information indicating membership or non-membership accepted on the membership confirmation reception screen 1320.

(About the screen of the POS terminal device 20)
FIG. 14 is an explanatory diagram showing an example of screen transitions displayed on the customer side display section 205 of the POS terminal device 20.
FIG. 14(A) shows a standby screen 910 similar to FIG. 9(A). On the standby screen 910, when the customer scans the payment code 822 displayed on the mobile terminal device 30 by the customer side scanner unit 206, the payment code 822 is displayed according to the declaration (member or non-member) received on the mobile terminal device 30. The screen displayed is different. Specifically, if a declaration of membership has been accepted, the standby screen 910 transitions to a membership type selection screen 1420 in FIG. 14(B). On the other hand, if a declaration of non-membership has been accepted, the standby screen 910 transitions to a sub-plan screen 940 in FIG. 14(C).

FIG. 14(B) shows a member type selection screen 1420. Membership type selection screen 1420 includes membership type selection buttons 1421. Membership type selection buttons 1421 include a store membership card button 1421a that indicates store membership, an application membership button 1421b that indicates application membership, and an electronic money membership button 1421b that indicates electronic money membership. 1421c. When either the store membership card button 1421a or the application membership button 1421b is pressed, a transition is made to a member information acquisition screen that prompts the reader to read the membership card corresponding to the pressed button. For example, when the application member button 1421b is pressed, the screen changes to a member information acquisition screen 920 (FIG. 9(B)). On the other hand, if the electronic money member button 1421c is pressed, the screen changes to a member information guide screen 930 (FIG. 9(C)). When the member information of the corresponding member card is read on the member information acquisition screen, or when the member information guide screen 930 is displayed, the screen changes to a sub-plan screen 940 in FIG. 14(C). Also, when the cancel button 1422 is pressed on the membership type selection screen 1420, the screen changes to a small plan screen 940 shown in FIG. 14(C). In this case, the regular price is applied on the small plan screen 940.

FIG. 14(C) shows a small plane 940 similar to FIG. 9(D). In the registered product display area 941, the purchase amount and total amount are displayed at the amount according to the membership type, and for non-members, the regular price is displayed. When the payment start button 942 is pressed on the small plan screen 940, the screen transitions to a payment type selection screen 1010 in FIG. 14(D).

FIG. 14(D) shows a payment type selection screen 1010 similar to FIG. 10(A). In the payment type selection screen 1010, when one of the payment type selection buttons 1011 is received to be pressed, payment processing is performed according to the accepted payment type.

Note that in the case of an electronic money member, the payment type selection screen 1010 may be skipped since there is a high possibility that payment will be made using electronic money. Specifically, when the electronic money membership button 1421c is selected on the membership type selection screen 1420 (FIG. 14(B)), the start payment button 942 is pressed on the small plan screen 940 (FIG. 14(C)). Then, the payment type selection screen 1010 (FIG. 14(D)) may be skipped and the transition may be made to the guidance screen 1020 (FIG. 10(B)). Note that when paying with electronic money, the charge amount and member information stored in the electronic money membership card are read at the same time.

(Example of display control processing related to acquisition of member information performed by mobile terminal device 30)
FIG. 15 is a flowchart illustrating an example of display control processing related to acquisition of member information performed by the mobile terminal device 30 according to the second embodiment. In FIG. 15, the mobile terminal device 30 determines whether or not the start of a transaction has been accepted on the top screen 710 (FIG. 13(A)) (step S1501). The mobile terminal device 30 waits until accepting the start of a transaction (step S1501: NO). When accepting the start of a transaction (step S1501: YES), the mobile terminal device 30 displays the member confirmation reception screen 1320 (FIG. 13(B)) (step S1502).

Then, the mobile terminal device 30 receives a declaration indicating membership (membership declaration button 1321) or non-member (non-membership declaration button 1322) on the membership confirmation reception screen 1320 (step S1503). Next, the POS terminal device 20 displays the registration screen 810 (FIG. 13(C)) (step S1504).

Then, the mobile terminal device 30 determines whether or not the product has been scanned in accordance with the customer's operation on the registration screen 810 (step S1505). If the product is not scanned (step S1505: NO), the mobile terminal device 30 proceeds to the process of step S1509. On the other hand, when the product is scanned (step S1505: YES), the mobile terminal device 30 displays the scanned product by transmitting product reading information to the cloud server 1 and receiving registered product information from the cloud server 1. .

To specifically explain the display based on the registered product information received from the cloud server 1, if the customer is not a member (step S1506: NO), the product is registered and displayed at the regular price (step S1507). On the other hand, if the customer is a member (step S1506: YES), products are registered and displayed at member prices (step S1508).

Then, the mobile terminal device 30 determines whether the payment is started by pressing the payment start button 813 (FIG. 13(A)) (step S1509). If it is not the start of payment (step S1509: NO), the mobile terminal device 30 returns to the process of step S1505. If it is the start of payment (step S1509: YES), the mobile terminal device 30 refers to the membership type accepted on the membership confirmation reception screen 1320 (FIG. 13(B)) and determines whether the customer is a member. (Step S1510).

If the customer is a member (step S1510: YES), the mobile terminal device 30 calculates the points to be given in this transaction (step S1511). Note that the points to be calculated may be points given in common to all members (store members, app members, and electronic money members), or may be estimated from the usage history of the customer who uses the mobile terminal device 30. Points may be given according to possible membership types. Then, the mobile terminal device 30 receives the declaration received on the membership confirmation reception screen 1320 (FIG. 13(B)) (membership declaration information: information indicating membership), point information indicating the calculated points, and registration information (cart identification The payment code 822 (FIG. 13C) encoded with the information) is displayed on the display 306 (step S1512), and the series of processing ends.

On the other hand, if the customer is not a member (step S1510: NO), the mobile terminal device 30 receives the declaration (membership declaration information: information indicating non-membership) received on the membership confirmation reception screen 1320 (FIG. 13(B)), The payment code 822 (FIG. 13(C)) which is encoded with the registration information (cart identification information) is displayed on the display 306 (step S1513), and the series of processing is completed.

(Example of display control processing related to acquisition of member information performed by POS terminal device 20)
FIG. 16 is a flowchart illustrating an example of display control processing related to acquisition of member information performed by the POS terminal device 20 according to the second embodiment. In FIG. 16, the POS terminal device 20 determines whether transaction information has been acquired from the cloud server 1 based on the transaction request information obtained by scanning the payment code 822 (FIG. 13(C)). Step S1601). The POS terminal device 20 waits until the transaction information is obtained (step S1601: NO).

Upon acquiring the transaction information (step S1601: YES), the POS terminal device 20 refers to the membership declaration information included in the payment code 822 and determines whether the customer is a member (step S1602). If the customer is not a member (step S1602: NO), the POS terminal device 20 moves to step S1608 and displays the small plan screen 940 (FIG. 14(C)). In this case, the small plan screen 940 is displayed at the normal price. On the other hand, if the customer is a member (step S1602: YES), the POS terminal device 20 displays the membership type selection screen 1420 (FIG. 14(B)) (step S1603) and accepts the selection of the membership type (step S1603). S1604).

Then, the POS terminal device 20 determines whether the received membership type is an electronic money membership (step S1605). If the received member type is an electronic money member (step S1605: YES), the POS terminal device 20 proceeds to the process of step S1608. On the other hand, if the received member type is not an electronic money member (step S1605: NO), the POS terminal device 20 determines whether membership information has been acquired (step S1606). If the member information is acquired (step S1606: YES), the POS terminal device 20 advances to step S1608 and displays the sub-plan screen 940 (FIG. 14(C)). In this case, the small plan screen 940 displays the membership price according to the membership type.

On the other hand, if member information is not acquired (step S1606: NO), the POS terminal device 20 determines whether pressing of the cancel button 1422 (FIG. 14(B)) has been accepted (step S1607). If the press of the cancel button 1422 is not accepted (step S1607: NO), the POS terminal device 20 returns to the process of step S1606. On the other hand, if the press of the cancel button 1422 is accepted (step S1607: YES), the small plan screen 940 (FIG. 14(C)) is displayed (step S1608). In this case, the regular price is displayed on the small plan screen 940.

Next, the POS terminal device 20 determines whether the payment start button 942 has been pressed on the small plan screen 940 (step S1609). The POS terminal device 20 waits until the start payment button 942 is pressed (step S1609: NO), and when the start payment button 942 is pressed (step S1609: YES), the POS terminal device 20 changes the membership type to electronic. It is determined whether the user is a money member (step S1610).

If the member type is an electronic money member (step S1610: YES), there is a high possibility that the payment type will be electronic money, so the POS terminal device 20 advances to step S1613 and accepts payment using electronic money. Note that when paying with electronic money, the charge amount and member information stored in the electronic money membership card are read at the same time. On the other hand, if the member type is not an electronic money member (step S1610: NO), the POS terminal device 20 displays the payment type selection screen 1010 (FIG. 14(D)) (step S1611), and selects the payment type. (Step S1612).

The POS terminal device 20 then determines whether the payment has been completed (step S1613). The POS terminal device 20 waits until the payment is completed (step S1613: NO), and when the payment is completed (step S1613: YES), the series of processing ends.

As explained above, in the second embodiment, the mobile terminal device 30 receives a declaration from the customer indicating whether or not the customer is a member, and the POS terminal device 20 displays different screens (FIG. 14) according to the declaration. The member type selection screen 1420 in (B) or the small plan screen 940 in FIG. 14(C) is displayed. This makes it possible to display an optimal screen for acquiring member information depending on whether the user is a member or not. Therefore, it is possible to reduce the number of times a customer presents the same membership card in one transaction. Smooth transactions can be realized. Therefore, it is possible to suppress the trouble associated with presenting a membership card and to support smooth transactions.

(Modified example of second embodiment)
Next, a modification of the second embodiment will be described. In the second embodiment described above, an example has been described in which the membership type selection screen 1420 (FIG. 14(B)) is displayed in accordance with the reception result of whether the mobile terminal device 30 is a member. In a modification of the second embodiment, an example will be described in which it is determined whether the customer is a member or not when entering the store, and a membership type selection screen 1420 is displayed according to the determination result.

In a modified example, the store is, for example, an unmanned store (for example, an unmanned convenience store) without staff. A member identification device for identifying whether a member is a member or not is placed at the entrance of the store. The member identification device may be, for example, a reading device that reads a membership card, or a biometric authentication device that authenticates the member's biometrics. Biometric authentication includes fingerprint authentication, face authentication, vein authentication, iris authentication, voice authentication, etc. The member identification device determines whether a customer is a member or a non-member when the customer enters the store.

A large number of cameras and sensors will be installed inside the store. A transaction control device that monitors transactions in an unmanned store recognizes the products that customers have taken out from the shelf based on the imaging results of the camera and the detection results of the sensors, and registers the products for each customer. After the customer has finished putting the products to be purchased into the bag, the customer moves to the POS terminal device 20 (self-checkout) for payment. The POS terminal device 20 acquires transaction information from the transaction control device and displays the transaction information including the purchased product and the payment amount on the customer side display section 205. If the transaction information is correct, the customer selects the payment type and completes the payment. Note that if the transaction includes an age-verified product, for example, a store employee who monitors the inside of the store using a monitor in the backyard may go to the POS terminal device 20 and request the customer to present his/her identification card.

In a modified example, when the POS terminal device 20 performs payment, if the target customer is a member, the POS terminal device 20 displays a membership type selection screen 1420 (FIG. 14(B)) on the customer side display section 205. On the other hand, when making payment, if the target customer is a non-member, the POS terminal device 20 does not display the membership type selection screen 1420 on the customer side display unit 205, but displays the small screen 940 (FIG. 14). C)).

In a modification of the second embodiment, it is determined whether the customer is a member or not when entering the store, and depending on the determination result, different screens (membership type selection screen 1420 in FIG. 14(B), Alternatively, the small plan screen 940 in FIG. 14(C) is displayed. This makes it possible to display an optimal screen for acquiring member information depending on whether the user is a member or not. Even in this manner, smooth transactions can be supported.

A summary of the embodiments will be described below.
[Name of the invention] Registration device, payment device, and program [Technical field]
The present invention relates to a registration device, a payment device, and a program.
[Background technology]
In recent years, so-called self-checkout systems, where customers register products and make payments, have become popular. For example, a system is known in which a customer registers a product using a portable registration device owned by the customer, and the customer makes payment using a payment device (for example, see Patent Document 1). Additionally, membership cards may be used in transactions. For example, multiple types of membership cards may be used depending on the membership type.
[Prior art documents]
[Patent document]
[Patent Document 1] Japanese Patent Application Publication No. 2016-219034 [Summary of the invention]
[Problem to be solved by the invention]
However, with the conventional technology, depending on the membership type, it may not be possible to make the customer present the membership card at an appropriate timing. For this reason, there is a problem in that presenting the membership card may become complicated for the customer, which may impede smooth transactions.
The present invention has been made in view of such circumstances, and its purpose is to provide a technology that can support smooth transactions.

[Means to solve the problem]
(1) In order to solve the above-mentioned problems, a registration device that is one aspect of the present invention is a registration device in a product sales processing system that includes a registration device that registers products and a payment device that pays for the registered products. A registration means for registering a product, a declaration reception means for accepting a declaration regarding membership from a customer, and different screens are displayed depending on the membership type included in the declaration received by the declaration reception means. A registration device comprising a display means.
According to the above configuration, it is possible to display an optimal screen related to acquiring member information depending on the membership type. Therefore, it is possible to reduce the number of times a customer presents the same membership card in one transaction. Therefore, it is possible to suppress the trouble associated with presenting a membership card and to support smooth transactions.

(2) In the configuration of (1) above, the display means displays an acquisition screen for acquiring member information or a guide screen for acquiring the member information with another device, depending on the membership type. It may also be displayed.
According to the above configuration, notification regarding the presentation of the membership card can be made at the time of product registration or at the time of payment, depending on the membership type. Therefore, it is possible to have the customer present the membership card at an appropriate timing depending on the membership type.

(3) In the configuration of (2) above, the display means may display a screen for accepting the membership type when the member information cannot be acquired on the acquisition screen.
According to the above configuration, the customer can be allowed to select the membership type again.

(4) The configuration of (1) or (2) above, further comprising output means for outputting information including information indicating the membership type accepted by the declaration receiving means and registration information registered by the registration means. It may also be a thing.
According to the above configuration, by outputting information indicating the membership type from the mobile terminal device 30 to the POS terminal device 20, the POS terminal device 20 can prompt the presentation of a membership card according to the membership type.

(5) In order to solve the above-mentioned problems, a checkout device that is one aspect of the present invention includes a registration device that registers products and receives a declaration from a customer regarding membership, and a checkout device that registers products and receives a declaration regarding membership from a customer. A payment device in a product sales processing system including a member type acquisition means for acquiring information indicating the membership type included in the declaration, and a display means for displaying an acquisition screen according to the membership type indicated by the information. and a member information acquisition means for acquiring member information on the acquisition screen.
According to the above configuration, it is possible to display an optimal acquisition screen according to the membership type acquired from the mobile terminal device 30. Moreover, since the POS terminal device 20 can acquire member information read by the mobile terminal device 30 from the mobile terminal device 30 for store members, an acquisition screen related to acquiring member information can be omitted.

(6) In order to solve the above problems, a program that is one aspect of the present invention is provided as a registration device in a product sales processing system that includes a registration device that registers products and a payment device that pays for the registered products. , a program that causes a computer to function, which controls the computer to register a product, a declaration reception means for accepting a declaration regarding membership from a customer, and a membership type included in the declaration received by the declaration reception means. This program is characterized in that it functions as a display means that displays different screens depending on the user's needs.
According to the above configuration, it is possible to display an optimal screen related to acquiring member information depending on the membership type. Therefore, in one transaction, it is possible to reduce the number of times a customer presents the same membership card and realize a smooth transaction.

(7) In order to solve the above-mentioned problems, a program that is one aspect of the present invention includes a payment device that registers products and receives a declaration of membership from a customer, and a payment device that pays for the registered products. A program for causing a computer to function as a registration device in a product sales processing system comprising: a membership type acquisition means for acquiring information indicating a membership type included in the declaration; This program is characterized in that it functions as a display means for displaying a corresponding acquisition screen, and a member information acquisition means for acquiring member information on the acquisition screen.
According to the above configuration, it is possible to display an optimal acquisition screen according to the membership type taken over from the mobile terminal device 30. Moreover, since the POS terminal device 20 can acquire member information read by the mobile terminal device 30 from the mobile terminal device 30 for store members, the acquisition screen can be omitted.

In addition, all or part of each function (input/output, storage, processing (including judgment)) in the shopping system St (POS terminal device 20, mobile terminal device 30) explained above is explained as the entity that executes the function. It may also be realized in a device different from the one described above.

Specifically, in the above description, a configuration in which the mobile terminal device 30 or the POS terminal device 20 includes each of the functional units shown in FIG. 6 has been described. All or part of each functional unit may be included in another computer device. For example, all or part of each functional unit may be included in the cloud server 1, the store controller 10, or a computer device other than these. Further, the number of computer devices equipped with each functional section is not limited to a plurality of devices, and may be one computer device. For example, all of the functional units may be included in one computer device.

Specifically, for example, instead of the mobile terminal device 30, the cloud server 1 may issue instructions to display different screens depending on the membership type included in the membership declaration received from the customer. You can also do this.

In relation to the above, the mobile terminal device 30 and the POS terminal device 20 may function as a so-called thin client specializing in input/output interface portions regarding various displays and the like. In other words, the mobile terminal device 30 and the POS terminal device 20 accept various inputs (operator operations and device detection), transmit the input information (operation information, detection information, etc.) to the cloud server 1, and send the input information to the cloud server 1. The processing results (updated screen information, device control information, etc.) of the cloud server 1 based on the above may be received, and various outputs (display on a display unit, device control) may be performed.

Note that the program for realizing the shopping system St (POS terminal device 20 and mobile terminal device 30) described above is recorded on a computer-readable storage medium, and the program is read and executed by the computer system. You can also do this. Note that the "computer system" herein includes hardware such as an OS and peripheral devices. Furthermore, "computer-readable storage media" refers to portable media such as USB (Universal Serial Bus) flash memory, SSD (Solid State Drive), flexible disks, magneto-optical disks, ROM, CD-ROM, and computer systems. Refers to a built-in storage device such as a hard disk. Furthermore, "computer-readable storage medium" refers to volatile memory (RAM) inside a computer system that serves as a server or client when a program is transmitted via a network such as the Internet or a communication line such as a telephone line. This also includes programs that are retained for a certain period of time. Further, the program may be transmitted from a computer system storing the program in a storage device or the like to another computer system via a transmission medium or by a transmission wave in a transmission medium. Here, the "transmission medium" that transmits the program refers to a medium that has a function of transmitting information, such as a network (communication network) such as the Internet or a communication line (communication line) such as a telephone line. Moreover, the above-mentioned program may be for realizing a part of the above-mentioned functions. Furthermore, it may be a so-called difference file (difference program) that can realize the above-described functions in combination with a program already recorded in the computer system.

St...Shopping system, 1...Cloud server, 10...Store controller, 11...Transaction status management device, 20...POS terminal device, 30...Mobile terminal device, 201...CPU, 205...Customer side display unit, 206...Customer side scanner 301...CPU, 303...Operation unit, 306...Display, 601...Registration unit, 602...Declaration reception unit, 603...Display unit, 604...Output unit, 611...Membership type acquisition unit, 612...Display unit, 613... Member information acquisition department

Claims (7)

A registration device in a product sales processing system including a registration device for registering products and a payment device for paying for the registered products,
a registration means for registering a product;
a declaration reception means for accepting a declaration regarding membership from a customer;
display means for displaying different screens depending on the membership type included in the declaration received by the declaration reception means;
A registration device comprising: The display means displays an acquisition screen for acquiring member information or a guide screen for acquiring the member information with another device, depending on the membership type.
The registration device according to claim 1, characterized in that: The display means displays a screen for accepting the membership type when the member information cannot be acquired on the acquisition screen.
The registration device according to claim 2, characterized in that: output means for outputting information including information indicating the membership type received by the declaration reception means and registration information registered by the registration means;
The registration device according to claim 1 or 2, comprising: a. A payment device in a product sales processing system including a registration device that registers products and receives a declaration of membership from a customer, and a payment device that pays for the registered products,
Membership type acquisition means for acquiring information indicating the membership type included in the declaration;
a display means for displaying an acquisition screen according to the membership type indicated by the information;
Member information acquisition means for acquiring member information on the acquisition screen;
A payment device characterized by comprising: A program that causes a computer to function as a registration device in a product sales processing system including a registration device for registering products and a payment device for paying for the registered products, the program comprising:
The computer,
Registration means for registering products;
declaration reception means for receiving a declaration regarding membership from a customer;
display means for displaying different screens depending on the membership type included in the declaration received by the declaration reception means;
A program characterized by functioning as A program that causes a computer to function as a payment device in a product sales processing system that includes a registration device that registers products and receives a declaration from a customer regarding membership, and a payment device that pays for the registered products.
The computer,
Membership type acquisition means for acquiring information indicating the membership type included in the declaration;
display means for displaying an acquisition screen according to the membership type indicated by the information;
Member information acquisition means for acquiring member information on the acquisition screen;
A program characterized by functioning as

Images