Program and registration device

Abstract

To support appropriate transactions. [Solution] The program causes the computer to function as a registration device. The program causes the computer to function as a registration means, an addition / deletion means, and a notification means. The registration means registers products, including specific products that are the same product but have different prices. The addition / deletion means adds or deletes products registered by the registration means. When adding or deleting a specific product of the same type as a specific product registered by the registration means, the notification means provides a notification prompting confirmation of the specific product to be added or deleted.

Description

Technical Field

[0006] , ,

[0001] The present invention relates to a program and a registration device.

Background Art

[0002] In recent years, a system for registering products using a mobile terminal device owned by a customer has been known (see, for example, Patent Document 1). Products include fixed-price products with a fixed price determined by the weight and shape of the product for each individual, and variable-price products with different prices due to different weights and quantities for each individual.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, in the prior art, there is a problem that in the addition / removal (addition or deletion) of specific products such as variable-price products, improper product registration may be performed, and thus transactions may not be properly conducted.

[0005] The present invention has been made in view of such circumstances, and an object thereof is to provide a technology capable of supporting appropriate transactions.

Means for Solving the Problems

[0006] To solve the above-mentioned problems, one aspect of the present invention is a program that causes a computer to function as a registration device, characterized in that the computer functions as a registration means for registering products including specific products that are the same product but have different prices set for them, an addition / deletion means for adding or deleting products registered by the registration means, and a notification means for prompting confirmation of the specific product to be added or deleted when adding or deleting a specific product of the same type as a specific product registered by the registration means.

[0007] To solve the above-mentioned problems, another aspect of the present invention is a registration device comprising: a registration means for registering products including specific products that are the same product but have different prices set for them; an addition / deletion means for adding or deleting products registered by the registration means; and a notification means for prompting confirmation of the specific product to be added or deleted when adding or deleting a specific product of the same type as a specific product registered by the registration means. [Brief explanation of the drawing]

[0008] [Figure 1] This is an explanatory diagram showing the network configuration of the registration and settlement system according to the embodiment. [Figure 2] This is a block diagram showing an example of a hardware configuration for a mobile terminal device. [Figure 3] This is a sequence diagram showing the processing flow from product registration to transaction completion in the registration and settlement system. [Figure 4] This is an explanatory diagram showing an example of the functional configuration of a mobile terminal device. [Figure 5] This figure shows an example of the screen displayed when adding a variable-weight product. [Figure 6] This figure shows an example of the screen displayed when deleting a variable-weight product. [Figure 7] This flowchart shows an example of a registration and settlement process performed by a mobile terminal device. [Figure 8] This figure shows a modified version 1 of the screen displayed when deleting a variable-weight product. [Modes for carrying out the invention]

[0009] (Embodiment) (Network configuration of registration and settlement system 1) Figure 1 is an explanatory diagram showing the network configuration of the registration and settlement system 1 according to this embodiment. The registration and settlement system 1 is installed in various types of stores. These stores are, for example, retail stores. Retail stores include, for example, supermarkets, convenience stores, drugstores, discount stores, department stores, general merchandise stores, etc. In this embodiment, the store is a supermarket. However, these stores may also be restaurants. Restaurants include fast food restaurants, restaurants, izakayas, cafes, diners, food courts, etc.

[0010] In Figure 1, the registration and settlement system 1 comprises an external cloud server Sv, a store controller 10, a transaction status management device 11, a mobile terminal device 30, and a settlement device 40. Each device is connected to the others via a network 55. Each device is a computer device equipped with a CPU (Central Processing Unit), ROM (Read Only Memory), RAM (Random Access Memory), a communication unit, etc. The network 55 can be a LAN (Local Area Network) or a WAN (Wide Area Network), and may be wired or wireless.

[0011] (Cloud Server Sv) The cloud server Sv is a server device that manages various types of information. This information includes customer information, store information, store-specific product information (product master), and customer membership information. The product master is a file that stores product information such as product identification information (e.g., JAN (Japanese Article Number) code), product name, and sales price for each product. Furthermore, the product master includes not only fixed-price products but also product identification information, product name, and unit price (price per gram) for products that require weighing (variable-weight products). For example, based on the product information read by the mobile terminal device 30, the cloud server Sv generates cart information representing a virtual cart for each customer and registers the products.

[0012] (Store controller 10) The store controller 10 stores various information necessary for transactions. This information includes registration information and settlement information generated by the settlement device 40. It also includes product master data. Furthermore, the information stored by the store controller 10 also includes inventory status, sales history, deposit and withdrawal records, special sale information, and member information.

[0013] (Transaction status management device 11) The transaction status management device 11 is a monitoring device. Specifically, the transaction status management device 11 displays the processing status of the settlement device 40 and controls the settlement device 40. For example, a store employee (monitoring employee) is stationed at the transaction status management device 11, and the monitoring employee monitors the settlement device 40. The transaction status management device 11 displays the status of each of the multiple settlement devices 40. Specifically, the transaction status management device 11 displays multiple screens (split screens) corresponding to each of the multiple settlement devices 40, and displays the status of each settlement device 40. The monitoring employee supports customers operating the settlement device 40 and verifies the age of customers when age-recognized products such as alcoholic beverages are registered at the settlement device 40.

[0014] (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 terminal, or a mobile phone. The mobile terminal device 30 includes a communication unit, an imaging unit (camera), a touch panel, etc., and is operated by a customer. In the present embodiment, the mobile terminal device 30 is detachably attached to the shopping cart. However, the mobile terminal device 30 may be fixedly installed to the shopping cart so as not to be detachable. Also, the mobile terminal device 30 may be owned by the customer or may be lent by the store to the customer.

[0015] An application software (hereinafter referred to as "shopping app") for registering products related to the registration settlement system 1 and for settling the registered products is installed in the mobile terminal device 30. By starting the shopping app, the mobile terminal device 30 scans (reads) the barcode (product code) attached to the product and accepts the registration of the product. When the mobile terminal device 30 reads the product code, it transmits the read information to the cloud server Sv. As a result, the product corresponding to the barcode is registered in the cart information (virtual cart) of the cloud server Sv.

[0016] Also, when the mobile terminal device 30 receives an operation indicating completion of registration, it displays a settlement code obtained by encoding the cart identification information assigned to the device itself. The settlement code is, for example, a two-dimensional code (QR code (registered trademark)), but may also be a one-dimensional code (barcode).

[0017] The settlement device 40 is a computer device capable of performing self - settlement for products registered by the mobile terminal device 30. The settlement device 40 acquires cart identification information by reading the settlement code displayed on the mobile terminal device 30. When the settlement device 40 reads the settlement code, it sends a request to the cloud server Sv to transmit the cart information indicated by the cart identification information. Then, the settlement device 40 receives transaction information from the cloud server Sv in response to the transmission request and performs settlement. In FIG. 1, the number of settlement devices 40 is illustrated as a plurality, but it may also be one.

[0018] (Hardware Configuration of Mobile Terminal Device 30) FIG. 2 is a block diagram showing an example of the hardware configuration of the mobile terminal device 30. As shown in FIG. 2, the mobile terminal device 30 includes components such as a CPU 201, a memory 202, an operation unit 203, a communication I / F (interface) 204, a storage medium I / F 205, a display 206, and a camera 207. Also, each component is connected by a bus 220.

[0019] The CPU 201 controls the entire mobile terminal device 30. The memory 202 has, for example, a ROM, a RAM, and a flash ROM. For example, the flash ROM and the ROM store various programs. The various programs include the registration program according to this embodiment. A shopping app including the registration program is pre - installed on the mobile terminal device 30. The RAM is used as a work area for the CPU 201. The programs stored in the memory 202 are loaded into the CPU 201 to cause the CPU 201 to execute the coded processing.

[0020] The input device 203 is a touch panel or operation buttons. Note that the input device 203 may include a microphone or the like. The communication interface 204 is connected to a network such as the internet via a communication line, and connects to other devices (e.g., a cloud server Sv) via the network. The communication interface 204 also manages the interface between the network and the inside of the device, and controls the input and output of data from other devices.

[0021] The storage medium interface 205 controls the reading and writing of data to storage media (not shown), such as magnetic disks and optical disks, according to the control of the CPU 201. Display 206 is an output device that displays images. In addition to display 206, speakers may also be included as output devices.

[0022] Camera 207 captures images of the subject. Camera 207 captures video or still images. Camera 207 reads the product code attached to the product. The portable terminal device 30 may also be equipped with a scanner in place of or in addition to camera 207. The scanner is, for example, mounted on the upper end of the housing of the portable terminal device 30 and reads the product code (barcode) attached to the product. The scanner can employ, for example, a laser system or a CCD system for reading.

[0023] (An example of the process from product registration to transaction completion in the registration and settlement system 1) Figure 3 is a sequence diagram showing the processing flow from product registration to transaction completion in the registration and settlement system 1. Figure 3 illustrates the process from when a customer visits a store, registers the products to be purchased using a mobile terminal device 30, and completes the transaction using the settlement device 40.

[0024] Step S301: First, the mobile device 30 launches the shopping app. Step S302: The mobile terminal device 30 acquires information that identifies a store (store identification information). The store identification information is represented, for example, by a two-dimensional code near the entrance of the store. The two-dimensional code may be displayed on a predetermined display device or printed on paper. The mobile terminal device 30 activates its camera when the shopping app is launched based on customer operation and scans the two-dimensional code. As a result, the mobile terminal device 30 acquires the store identification information. The two-dimensional code also contains instructions to request the cloud server Sv to start a transaction. Therefore, once the mobile terminal device 30 acquires the store identification information, it requests the cloud server Sv to start a transaction. Specifically, the mobile terminal device 30 transmits the acquired store identification information and customer identification information (terminal identification information) to the cloud server Sv.

[0025] Furthermore, store identification information may be obtained based on location information. For example, when the mobile terminal device 30 launches the shopping app, it acquires GPS information indicating its current location and sends a query to the cloud server Sv based on the acquired GPS information. The cloud server Sv extracts the nearest store to the mobile terminal device 30 based on the GPS information and sends the extraction result to the mobile terminal device 30. When the mobile terminal device 30 receives the extraction result from the cloud server Sv, The nearest store is displayed, and the customer is allowed to select a store to use. The mobile terminal device 30 then transmits store identification information indicating the selected store and customer identification information (terminal identification information) to the cloud server Sv.

[0026] Step S303: When the cloud server Sv receives a transaction initiation request (customer identification information and store identification information) from the mobile terminal device 30, it generates cart information for that transaction. The cart information includes, for example, the following information: Cart identification information. • Customer identification information. • Transaction start date and time. • Registered product information. Cart identification information is, for example, information that combines a serial number assigned by a numbering system, store identification information, and the current date. Customer identification information is information that identifies the customer. Registered product information shows the product information registered in this transaction.

[0027] Step S304: The mobile terminal device 30 reads the product code (barcode) attached to the product in response to the customer's operation and registers the product corresponding to the read product code. Alternatively, the mobile terminal device 30 may register a product corresponding to a preset key (button corresponding to a product) displayed on the display 206 when the preset key is pressed. Once a product is registered, the mobile terminal device 30 sends product information indicating the product and cart identification information to the cloud server Sv.

[0028] Step S305: When the cloud server Sv receives product information and cart identification information from the mobile terminal device 30, it identifies the cart information containing the received cart identification information and updates the registered product information contained in the identified cart information.

[0029] Step S306: The mobile terminal device 30 returns to step S304 and enables product registration until product registration is complete. Completion of registration is, for example, when a predetermined button that accepts the start of payment (the registration completion button 514 in Figure 5(A)) displayed on the display 306 is pressed. Step S307: Once registration is complete, the mobile terminal device 30 generates a settlement code and displays it on the display 306.

[0030] Step S308: The payment device 40 reads the payment code displayed on the mobile terminal device 30. The payment code includes cart identification information and information indicating that a request for cart information is to be sent to the cloud server Sv. Step S309: When the payment device 40 reads the payment code, it requests the cloud server Sv to send cart information. In the request to send cart information, the payment device 40 sends the cart identification information obtained from the payment code to the cloud server Sv.

[0031] Step S310: When the cloud server Sv receives a request to send cart information from the payment device 40, it identifies the cart information using the cart identification information. Once the cloud server Sv has identified the cart information, it sends the identified cart information to the payment device 40.

[0032] Step S311: When the settlement device 40 receives cart information from the cloud server Sv, it performs settlement processing using the cart information. Once the settlement processing is complete, the settlement device 40 sends a transaction completion notification, including cart identification information, to the cloud server Sv.

[0033] Step S312: When the cloud server Sv receives a transaction completion notification from the settlement device 40, it extracts the cart identification information contained in the transaction completion notification. The cloud server Sv then stores the transaction end date and time (settlement date and time) of the cart information containing the cart identification information and sends the transaction completion notification to the mobile terminal device 30.

[0034] Step S313: When the mobile terminal device 30 receives a transaction completion notification from the cloud server Sv, it deletes the products registered in the mobile terminal device 30 and terminates the shopping application. Note that the conditions for deleting products and terminating the shopping application are not limited to receiving a transaction completion notification; they may also be the reading of the settlement code by the settlement device 40 in step S308. In this case, the cloud server Sv sends information to the mobile terminal device 30 indicating that the settlement code has been read by the settlement device 40. When the mobile terminal device 30 receives this information, it should delete the products and terminate the shopping application.

[0035] (Regarding the addition or removal of variable-weight products) The products registered by the mobile terminal device 30 include fixed-weight products and variable-weight products. Fixed-weight products are products with a fixed price, where the weight and shape of each individual product are predetermined. Variable-weight products are an example of a specific product. Variable-weight products are products that are the same product but have different prices set for them. Specifically, variable-weight products are products whose prices differ due to differences in weight and quantity from one individual to another. For example, variable-weight products are products whose prices are set according to the price per gram and the net weight. For variable-weight products of the same type (for example, minced pork from XX), the price is rarely the same because each product will have a different weight. For example, if a product has a price per gram of 100 yen (¥100 / 100g), the price will be 251 yen if it contains 251g, and 302 yen if it contains 302g.

[0036] In this context, the addition or deletion of variable-weight goods may lead to improper product registration (hereinafter sometimes referred to as "improper registration"). Two examples of improper registration are given below. When registering two variable-weight products of the same type (251 yen and 302 yen), register the cheaper product (251 yen) and enter "2" as the quantity for that product, thereby purchasing the more expensive product (302 yen) at a lower price (251 yen). • When two variable-weight products of the same type are registered, if one product is to be deleted, the higher-priced product (302 yen) should be deleted and the lower-priced product (251 yen) should be returned to the shelf. In other words, the higher-priced product should be purchased at the price of the lower-priced product.

[0037] Unauthorized registration can occur intentionally or unintentionally. Therefore, even if unauthorized registration is discovered and a store employee confronts the customer, the customer may have the opportunity to claim that the unauthorized registration was unintentional, even if it was done intentionally.

[0038] Thus, in the addition and removal of variable-weight goods, there was a risk of unfair product registration, which sometimes prevented proper transactions. Therefore, the mobile terminal device 30 according to this embodiment is designed to support proper transactions. The functional configuration of the mobile terminal device 30 shown in Figure 4 will be described below.

[0039] (Regarding the functional configuration of the mobile terminal device 30) Figure 4 is an explanatory diagram showing an example of the functional configuration of the mobile terminal device 30. As shown in Figure 4, the mobile terminal device 30 comprises the following functional units: a registration unit 401, an addition / deletion reception unit 402, an addition / deletion unit 403, a notification unit 404, a modification unit 405, and a reading unit 406. Each functional unit is implemented by the CPU 201. That is, the CPU 201 implements each functional unit by executing a registration program.

[0040] The registration unit 401 registers products based on product codes obtained from customers shopping while browsing the store, according to the product codes displayed on the registration screen. The registration unit 401 registers products by reading product codes or by accepting the press of preset keys. The registration unit 401 registers products that include both fixed-weight and variable-weight items.

[0041] The Addition / Deletion Reception Unit 402 accepts additions and deletions of products registered by the Registration Unit 401. Additions and deletions of products include adding products, deleting products, and changing quantities. The addition / deletion unit 403 adds or deletes products according to the reception results of the addition / deletion reception unit 402. For fixed-weight products, the addition / deletion unit 403 adds, deletes, or changes the quantity of products according to the reception results of the addition / deletion reception unit 402. On the other hand, for variable-weight products, the addition / deletion unit 403 adds or deletes products when certain conditions are met (for example, after the confirmation notification described later).

[0042] When the notification unit 404 adds or removes a variable weight product of the same type as a variable weight product registered by the registration unit 401, it issues a notification prompting confirmation regarding the variable weight product to be added or removed (hereinafter referred to as "confirmation notification"). A variable weight product of the same type is a product that has the same price per gram and the same product name (for example, "minced pork from XX"). Adding or removing a variable weight product of the same type as a registered variable weight product includes the following: - Deleting some of the multiple listings for the same type of variable-weight product. - Adding another variable-weight product of the same type when a variable-weight product is already registered.

[0043] The confirmation notification is a notification confirming the addition or subtraction of variable weight products. Specifically, the confirmation notification may be, for example, a notification asking "Do you want to add XX-produced minced pork?" for a variable weight product to be added (XX-produced minced pork), or a notification asking "Do you want to remove XX-produced minced pork?" for a variable weight product to be removed (XX-produced minced pork).

[0044] After issuing the confirmation notification, the addition / deletion unit 403 adds or deletes the variable-weight products to be added or deleted.

[0045] (Regarding the deletion of variable-weight products when multiple identical variable-weight products are registered.) The notification unit 404 issues a confirmation notification if multiple variable-weight products of the same type have been registered by the registration unit 401, and if some of these variable-weight products are to be deleted. This helps to prevent fraudulent registrations, such as deleting high-priced products and returning low-priced products to the shelves.

[0046] Furthermore, if only one variable-weight product of the same type is registered, no confirmation notification will be issued when deleting that product. This is because it prevents situations such as deleting high-priced items and returning low-priced items to the shelves, thus preventing fraudulent registration.

[0047] (Regarding restrictions on changing the quantity of products) The Addition / Deletion Reception Department 402 and the Registration Department 401 accept changes to the quantity of registered products. Products subject to quantity changes are fixed-weight products. Fixed-weight products are products whose weight and shape are determined for each individual item, and whose price is fixed.

[0048] The modification unit 405 restricts quantity changes for variable-weight products registered by the registration unit 401. Specifically, the modification unit 405 prohibits quantity changes for variable-weight products. The notification unit 404 issues a confirmation notification indicating that the modification unit 405 is restricting quantity changes. This confirmation notification is such as, "The quantity of minced pork from XX cannot be increased." However, even if variable-weight products are registered, if the weights and prices of multiple registered variable-weight products of the same type are the same (for example, if two 251g packages happen to be registered), the modification unit 405 may allow quantity changes for the variable-weight products.

[0049] (Regarding the addition or removal of variable-weight products by reading product codes) The reading unit 406 reads the barcode (product code) attached to the product. The notification unit 404 issues a confirmation notification prompting the reading of the product code attached to the variable-weight product to be changed. This confirmation notification is something like, "If you are adding (or deleting) the product, please read the barcode for the minced pork from XX prefecture."

[0050] The addition / deletion unit 403 adds or deletes variable-weight products to be added or deleted when the product code is read by the reading unit 406. This allows for the deletion of a product on the condition that the product code of that product is read.

[0051] (Example of a screen displayed on the mobile terminal device 30) Next, using Figures 5 and 6, we will describe examples of screens displayed on the display 206 of the mobile terminal device 30. Figure 5 shows an example of the screen when adding a variable-weight product.

[0052] Figure 5(A) shows the product registration screen 510. The product registration screen 510 includes an imaging area 511, a total area 512, a registered product area 513, and a registration completion button 514. The imaging area 511 is an area in which the camera 207 of the mobile terminal device 30 can capture images of the barcode attached to the product. Total area 512 is the area that displays the total number of items and total price of the various products that have been registered. The registered product area 513 includes the number (quantity) and price of the registered product. In the illustration, the registered product area 513 shows that one unit of "251g of ground pork," which is a variable-weight product, is registered. The registered product area 513 also includes an add / delete button 513a. The add / delete button 513a is a button that accepts quantity changes. The registration completion button 514 is a button that accepts registration completion (display of the payment code).

[0053] When the add / delete selection button 513a is pressed, the system transitions to the add / delete request screen 520 shown in Figure 5(B). Figure 5(B) shows the addition / deletion acceptance screen 520. The addition / deletion acceptance screen 520 includes an addition / deletion button 521. The addition / deletion button 521 is a button that pops up on the addition / deletion specification button 513a. The addition / deletion button 521 includes an add button 521a and a subtraction button 521b. The add button 521a accepts the addition of items. Each time the add button 521a is pressed, the quantity of the item can be increased by 1. The subtraction button 521b accepts the subtraction of items. Each time the subtraction button 521b is pressed, the quantity of the item can be decreased by 1.

[0054] In this embodiment, if multiple variable-weight products of the same type are registered, the addition / deletion unit 403 deletes the target product when certain conditions are met (for example, after reading the product code). In the illustration, only one variable-weight product is registered. Therefore, when the subtraction button 521b is pressed, the variable-weight product "251g of ground pork" is deleted.

[0055] On the other hand, if a variable-weight product is registered, the addition / deletion unit 403 adds the target product after fulfilling certain conditions (for example, after reading the product code). When the add button 521a is pressed, the addition of quantity is restricted. Specifically, as shown in the figure, when the add button 521a is pressed, the system transitions to the addition restriction screen 530 shown in Figure 5(C). By registering a low-priced product and entering "2" as the quantity of that low-priced product, it is possible to prevent fraudulent registrations such as purchasing high-priced products at a low price.

[0056] Figure 5(C) shows the addition restriction screen 530. The addition restriction screen 530 includes a confirmation notification 531. The confirmation notification 531 includes (1) a notification that the addition of quantity is restricted (that addition is not possible), (2) a notification to confirm the addition of variable weight products, and (3) a notification prompting the reading of the product code. When the confirmation button 532 is pressed in the confirmation notification 531, the screen transitions to the product registration screen 540 shown in Figure 5(D).

[0057] Figure 5(D) shows the product registration screen 540. On the product registration screen 540, the product code 541 of the variable-weight product to be registered is displayed in the imaging area 511. When the camera 207 reads the product code 541, the variable-weight product "302g of ground pork" is added to the registration, as shown in the registered product area 513.

[0058] (Example of the screen when deleting an item) Figure 6 shows an example of the screen when deleting a variable-weight product. Figure 6(A) shows the product registration screen 610. In the product registration screen 510, the registered product area 513 shows that two variable-weight products of the same type, "Ground Pork 251g" and "Ground Pork 302g," are registered. When the add / delete button 513a is pressed, the system transitions to the add / delete acceptance screen 620 shown in Figure 6(B).

[0059] Figure 6(B) shows the addition / deletion acceptance screen 620. In the illustration, multiple variable-weight products of the same type are registered. Therefore, there is a risk of fraudulent registration, such as deleting high-priced products and returning low-priced products to the shelves. To address this, when the subtraction button 521b is pressed, the subtraction of quantities is restricted. Specifically, in the illustration, when the subtraction button 521b is pressed, the system transitions to the deletion restriction screen 630 shown in Figure 6(C).

[0060] Figure 6(C) shows the deletion restriction screen 630. The deletion restriction screen 630 includes a confirmation notification 631. The confirmation notification 631 includes (1) a notification that the deduction of quantity is restricted (that deduction is not possible), (2) a notification to confirm the deletion of variable weight products, and (3) a notification prompting the reading of the product code. When the confirmation button 632 is pressed in the confirmation notification 631, the screen transitions to the product registration screen 640 shown in Figure 6(D).

[0061] Figure 6(D) shows the product registration screen 640. On the product registration screen 640, the product code 641 of the variable-weight product to be deleted is displayed in the imaging area 511. When the camera 207 reads the product code 641, the variable-weight product "302g of ground pork" is deleted, as shown in the registered product area 513. The deleted product is also displayed in a way that indicates it has been deleted. In the figure, the deleted product is marked with a strikethrough line 642. The deleted product may be hidden.

[0062] (An example of registration and settlement processing performed by the mobile terminal device 30) Figure 7 is a flowchart showing an example of the registration and settlement process performed by the mobile terminal device 30. As shown in Figure 10, the mobile terminal device 30 waits until product registration begins (step S701: NO). Product registration begins when the shopping app is launched and the product registration screen 510 (Figure 5(A)) is displayed. When product registration begins (step S701: YES), the mobile terminal device 30 determines whether or not it has scanned the product code displayed in the imaging area 511 (step S702).

[0063] If a product code is scanned (step S702: YES), the mobile terminal device 30 registers the product corresponding to the product code (step S703). Next, the mobile terminal device 30 determines whether or not product registration is complete (whether or not the registration completion button 514 in Figure 5(A) was pressed) (step S704). If product registration is not complete (step S704: NO), the mobile terminal device 30 returns to step S702. On the other hand, if product registration is complete (step S704: YES), the mobile terminal device 30 displays a settlement code (step S705) and terminates the series of processes.

[0064] In step S702, if the product code is not scanned (step S702: NO), the mobile terminal device 30 determines whether or not the addition / deletion request has been accepted (the addition / deletion designation button 513a in Figure 5(A) is pressed) (step S706). If the addition / deletion request is not accepted (step S706: NO), the mobile terminal device 30 proceeds to step S704. On the other hand, if the addition / deletion request has been accepted (step S706: YES), the mobile terminal device 30 determines whether or not the product to be added or deleted is a variable-weight product (step S707).

[0065] If the product to be added or removed is not a variable-weight product (step S707: NO), that is, if the product to be added or removed is a fixed-weight product, the mobile terminal device 30 proceeds to step S712, and the product is deleted or added as is. On the other hand, if the product to be added or removed is a variable-weight product (step S707: YES), the mobile terminal device 30 determines whether or not it is a deletion of a variable-weight product (step S708). If it is not a deletion of a variable-weight product (step S708: NO), that is, if it is an addition of a variable-weight product, the mobile terminal device 30 proceeds to step S710.

[0066] In step S708, if the deletion is for a variable weight product (step S708: YES), the mobile terminal device 30 determines whether or not other variable weight products of the same type as the variable weight product to be deleted are registered (step S709). If no other variable weight products of the same type as the variable weight product to be deleted are registered (step S709: NO), that is, if only one variable weight product of the same type is registered, the mobile terminal device 30 proceeds to step S714 and deletes the variable weight product, as no improper product registration will occur.

[0067] On the other hand, if other variable weight products of the same type as the variable weight product to be deleted are registered (step S709: YES), that is, if multiple variable weight products of the same type are registered, there is a risk of improper product registration, so a confirmation notification is issued in response to the addition or deletion of a product (confirmation notification 531 in Figure 5(C) or confirmation notification 631 in Figure 6(C)) (step S710). Then, the mobile terminal device 30 scans the product code of the variable weight product to be added or deleted in response to the customer's scan operation (step S711).

[0068] Next, the mobile terminal device 30 determines whether or not it is a deletion of an item (step S712). If it is not a deletion of an item (step S712: NO), that is, if it is an addition of an item, the mobile terminal device 30 adds the variable weight item in question (step S713) and proceeds to step S704. On the other hand, if it is a deletion of an item (step S712: YES), the mobile terminal device 30 deletes the variable weight item in question (step S714) and proceeds to step S704.

[0069] (Effects of the embodiment) As described above, when adding or removing a variable weight product of the same type as a registered variable weight product, the portable terminal device 30 according to this embodiment provides a notification (confirmation notification 531, 631) prompting confirmation regarding the variable weight product to be added or removed. This allows customers to confirm the addition or deletion of variable-weight goods when adding or removing them. Therefore, it is possible to prevent unfair product registration when adding or removing variable-weight goods. Thus, it is possible to support fair transactions.

[0070] Furthermore, in this embodiment, the portable terminal device 30 has registered multiple variable weight products of the same type by the registration unit 401, and when some of these variable weight products are to be deleted, it issues a confirmation notification 631 (Figure 6(C)). This helps to prevent unfair product registration practices, such as removing high-priced items from a list of multiple variable-weight products of the same type and returning lower-priced items to the shelves.

[0071] Furthermore, the portable terminal device 30 according to this embodiment restricts changes to the quantity of variable-weight goods if such goods are registered. This prevents fraudulent registrations, such as registering a low-priced item and setting its quantity to "2" when adding a variable-weight item of the same type, thereby purchasing a high-priced item at a low price. Furthermore, it prevents fraudulent registrations, such as removing some of the high-priced items and returning the low-priced items to the shelves when deleting multiple variable-weight items of the same type.

[0072] Furthermore, the portable terminal device 30 according to this embodiment adds or removes variable weight products to be added or removed by reading the product code attached to the variable weight product to be changed. This allows for the addition or removal of variable-weight products based on their product codes, thereby improving the deterrent effect against fraudulent product registration.

[0073] (Modified version of the embodiment) Next, modifications of the embodiments will be described. In each of the following modifications, explanations of the contents described in the embodiments described above will be omitted as appropriate. Furthermore, each of the following modifications and the embodiments described above can be combined.

[0074] (Variation 1: An example where reading the product code is unnecessary when adding or removing variable-weight products) The above-described embodiment explains an example in which reading the product code is required when adding or removing variable-weight products. Modification 1 explains an example in which reading the product code is not required when adding or removing variable-weight products. The following describes the case of deleting a variable-weight product, but the same applies to the registration of additional variable-weight products.

[0075] Figure 8 shows a modified version 1 of the screen when deleting variable-weight products. Figure 8(A) shows a product registration screen 610 similar to that in Figure 6(A). Figure 8(B) shows an add / delete acceptance screen 620 similar to Figure 6(B). In the illustration, when the subtraction button 521b is pressed, the system transitions to the delete notification screen 830 shown in Figure 8(C).

[0076] Figure 8(C) shows the deletion notification screen 830. The deletion notification screen 830 includes a confirmation notification 831. The confirmation notification 831 includes a notification confirming the deletion of the variable weight product. The confirmation notification 831 includes an affirmative button 832a and a negative button 832b. The affirmative button 832a is a button that accepts the deletion of the variable weight product to be deleted. The negative button 832b is a button that does not accept the deletion of the variable weight product to be deleted. If the negative button 832b is pressed, the confirmation notification 831 is cleared and the user returns to the product registration screen 610 (Figure 6(A)). If the affirmative button 832a is pressed, the user transitions to the product registration screen 840 shown in Figure 8(D).

[0077] Figure 8(D) shows the product registration screen 840. On the product registration screen 840, as shown in the registered product area 513, a strikethrough 642 is applied to the variable weight product "302g of ground pork," indicating that the variable weight product has been deleted. In other words, the variable weight product is deleted without requiring the product code to be read.

[0078] As described above, when adding or removing a registered variable weight product, the portable terminal device 30 according to Modification Example 1 issues a notification (confirmation notification 831) prompting the user to confirm the variable weight product to be added or removed. This allows customers to confirm the addition or removal of variable-weight goods. Therefore, it is possible to prevent unfair product registration when adding or removing variable-weight goods. Thus, it is possible to support fair transactions.

[0079] (Variation 2: Another example of confirmation notification display: Only the fact that addition or deletion of quantities is restricted is notified.) Next, a modified example 2 will be described. In the embodiment described above, an example was described in which the confirmation notification regarding the addition or deletion of variable weight products (confirmation notifications 531 and 631 in Figures 5 and 6) included (1) a notification that the addition or deletion of the quantity is restricted (that addition or deletion is not possible), (2) a notification confirming the addition or deletion of the variable weight product, and (3) a notification prompting the reading of the product code. In modified example 2, the confirmation notification regarding the addition or deletion of variable weight products may not include (2) a notification confirming the addition or deletion of the variable weight product, or (3) a notification prompting the reading of the product code, but only (1) a notification that the addition or deletion of the quantity is restricted (that addition or deletion is not possible). In this case, the addition / deletion unit 403 may be configured not to perform addition or deletion of variable weight products.

[0080] According to Modification 2, when adding or removing variable-weight goods, customers can be informed that the addition or removal of quantity is limited. Therefore, it is possible to prevent unfair product registration when adding or removing variable-weight goods. Thus, it is possible to support appropriate transactions.

[0081] (Modification 3: An example where the add / delete selection button 513a and the add / delete button 521 are disabled.) Next, we will describe a third modification. In this third modification, we will describe an example in which the display of the operation buttons related to adding or removing variable weight products (for example, the add / remove specification button 513a and the add / remove button 521 in Figure 5) is different from that of the embodiment.

[0082] In Modification 3, the portable terminal device 30 displays the operation buttons for adding or removing variable weight products (add / remove designation button 513a and add / remove button 521 in Figures 5 and 6) in a way that indicates they are disabled. This display method may be, for example, graying them out or hiding them. If an operation button for adding or removing variable weight products is pressed, the portable terminal device 30 may display a confirmation notification (confirmation notifications 531 and 631 in Figures 5 and 6).

[0083] According to Modification 3, customers can easily understand that the quantity of variable-weight products cannot be changed on the product registration screens 510 and 610, and the addition / deletion acceptance screens 520 and 620.

[0084] (Variation 4: An example where the registration device is a fully self-service registration and payment device) Next, we will describe Modification 4. In the embodiment described above, a mobile terminal device 30 was used as an example of a registration device for registering products. In Modification 4, a fully self-service registration and payment device will be used as an example of a registration device for registering products.

[0085] In Modification 4, the registration and settlement device is located within the store. The registration and settlement device is a POS register that allows customers to register and settle their own payments. The registration unit 401, the addition / deletion acceptance unit 402, the addition / deletion unit 403, the notification unit 404, the change unit 405, and the reading unit 406, as shown in Figure 4, are all provided in the registration and settlement device. The registration and settlement device is capable of registering variable weight products. When adding or deleting a variable weight product of the same type as a registered variable weight product, the registration and settlement device provides confirmation notification for the variable weight product to be added or deleted.

[0086] According to Modification 4, in a fully self-service registration and settlement device, when adding or removing variable-weight goods, the customer can be required to confirm the addition or deletion of the variable-weight goods. Therefore, it is possible to prevent the registration of improper goods when adding or removing variable-weight goods. Thus, even in a fully self-service registration and settlement device, appropriate transactions can be supported.

[0087] (Variation 5: An example where confirmation by a store employee is required when adding or removing variable-weight goods) Next, we will describe Modification 5. In the embodiment described above, we described an example in which reading the product code is required when adding or removing variable weight products. In Modification 5, we will describe an example in which confirmation by a store clerk is required when adding or removing variable weight products without reading the product code.

[0088] In Modification 5, the addition / deletion unit 403 allows for the free addition of variable weight products of the same type, or the deletion of some of multiple variable weight products of the same type. However, these variable weight products to be registered are designated as reserved products requiring confirmation by a store employee, and the addition or deletion is finalized after confirmation by the store employee. Confirmation by the store employee is performed, for example, at the time of settlement. In other words, at the time of settlement, if reserved products are included in the variable weight products to be purchased, the settlement device 40 executes a process to call a store employee, and after confirmation by the store employee, the addition or deletion of the variable weight products is finalized and settlement is performed.

[0089] According to Modification 5, the addition or removal of variable-weight goods requires confirmation by a store employee, thus preventing unfair product registration in the addition or removal of variable-weight goods. Therefore, it can support appropriate transactions.

[0090] (Variation 6: An example of adding certain conditions to changes in the quantity of fixed-weight goods) Next, we will describe Modification 6. In the embodiment described above, we described an example in which the quantity of fixed-weight goods can be freely changed. Modification 6 describes an example in which certain conditions are added to the change in the quantity of fixed-weight goods.

[0091] In Modification 6, the addition / deletion unit 403 allows customers to freely increase the quantity of fixed-weight products according to their own actions, while allowing them to freely decrease the quantity. For example, in Modification 6, when decreasing the quantity, the product may be designated as a reserved item requiring confirmation by a store employee, and the decrease in quantity may be confirmed after confirmation by the store employee. Confirmation by the store employee may be performed, for example, at the time of settlement. In other words, at the time of settlement, if the purchased items include reserved items, the settlement device 40 executes a process to call a store employee, and after confirmation by the store employee, confirms the decrease in the quantity of fixed-weight products and performs settlement.

[0092] According to Modification 6, since the reduction in the quantity of fixed-weight products requires confirmation by a store employee, it is possible to prevent fraudulent registrations where the quantity of fixed-weight products to be purchased is entered, but then the quantity is reduced without returning the products.

[0093] (Example of modification 7: An example of providing confirmation when adding or removing items that are expected to be discounted) Next, we will describe Modification 7. In the embodiment described above, we described an example of providing confirmation notification when adding or removing variable-weight products. Modification 7 describes an example of providing confirmation notification when adding or removing products that are likely to be given a value quote or a discount barcode (hereinafter referred to as "discount code") (hereinafter referred to as "discount-expected products").

[0094] (Regarding the addition or removal of items expected to be discounted) In Modification Example 7, the products registered by the mobile terminal device 30 include products with potential discounts. Products with potential discounts are an example of specific products. Products with potential discounts are the same product but have different prices set for them. Specifically, products with potential discounts are fixed-weight products that may have discount codes, such as a 50% discount, applied when their expiration date approaches. Products with potential discounts include products with discount codes and products without discount codes. In other words, products with potential discounts have different prices depending on whether or not a discount code is applied. For example, in the case of a product with a regular price of 300 yen that has potential discounts, the price is 150 yen if a 50% discount code is applied, and 300 yen if no discount code is applied.

[0095] Here, adding or removing (adding or deleting) items expected to be discounted may lead to fraudulent registration. Two examples of fraudulent registration are given below. When registering two discounted items of the same type (150 yen and 300 yen), register the cheaper item (150 yen) and enter "2" as the quantity for that item, thereby purchasing the more expensive item (300 yen) at a lower price (150 yen). • When two discounted items of the same type are registered, if one item is to be removed, the higher-priced item (300 yen) should be removed and the lower-priced item (150 yen) should be returned to the shelf. In other words, the higher-priced item should be purchased at the price of the lower-priced item.

[0096] Thus, when adding or removing discounted products, there was a risk of unfair product registration, which sometimes prevented proper transactions. Therefore, the mobile terminal device 30 according to Modification 7 is designed to support proper transactions. The functional configuration of the mobile terminal device 30 according to Modification 7 will now be described with reference to Figure 4.

[0097] The registration unit 401 registers products by reading product codes and discounts, or by reading discount codes. The registration unit 401 also registers products that include discounted items.

[0098] The Addition / Deletion Reception Unit 402 accepts additions and deletions of products registered by the Registration Unit 401. The addition / deletion unit 403 adds or deletes products according to the reception results of the addition / deletion reception unit 402. The addition / deletion unit 403 adds or deletes products that are expected to be discounted if certain conditions are met (after confirmation notification).

[0099] When the notification unit 404 adds or removes discounted products of the same type as those registered by the registration unit 401, it issues a notification (confirmation notification) prompting confirmation regarding the discounted products to be added or removed. Discounted products of the same type are products to which the same product code (product identification information) is assigned. Adding or removing discounted products of the same type as those already registered includes the following: - Deleting some of the multiple registered discount items of the same type. • Adding another discounted item of the same type when a discounted item is already registered.

[0100] The confirmation notification is a notification to confirm the addition or subtraction of discounted items. Specifically, the notification may be, for example, a notification asking "Do you want to add XX milk?" for a discounted item to be added (XX milk), or a notification asking "Do you want to remove XX milk?" for a discounted item to be removed (XX milk). After issuing the confirmation notification, the addition / deletion unit 403 adds or deletes the discounted products to be added or deleted.

[0101] (Regarding the deletion of discounted items when multiple discounted items of the same type are registered) The notification unit 404 issues a confirmation notification when the registration unit 401 has registered multiple discounted items of the same type, and when some of these discounted items are to be deleted. This helps to prevent fraudulent registrations, such as deleting high-priced items and returning low-priced items to the shelves.

[0102] Furthermore, if only one discounted item of the same type is registered, no confirmation notification will be issued when deleting that discounted item. This is to prevent situations where high-priced items are deleted and low-priced items are returned to the shelves, thus preventing fraudulent registrations.

[0103] (Regarding restrictions on changing the quantity of products) The modification unit 405 restricts quantity changes for discounted products registered by the registration unit 401. Specifically, the modification unit 405 prohibits quantity changes for discounted products. The notification unit 404 issues a confirmation notification indicating that the modification unit 405 is restricting quantity changes. This confirmation notification is such as, "You cannot add the quantity of XX milk." However, even if discounted products are registered, if the prices of multiple registered discounted products of the same type are the same (for example, if two XX milk products with a 50% discount are registered), the modification unit 405 may allow quantity changes for the discounted products.

[0104] (Regarding adding or removing discounted items by reading product codes) The notification unit 404 issues a confirmation notification prompting the user to scan the product code attached to the discounted product that is subject to change. This confirmation notification is something like, "If you are adding (or deleting) a product, please scan the barcode attached to the XX milk product."

[0105] The addition / deletion unit 403 adds or deletes discounted products to be added or deleted when the product code (or discount code) is read by the reading unit 406. This allows for the deletion of discounted products on the condition that the product code (or discount code) of the product to be deleted is read.

[0106] As described above, the mobile terminal device 30 according to Modification 7 provides notification prompting the user to confirm the discounted product to be added or removed when adding or removing a discounted product of the same type as a registered discounted product. This allows customers to confirm the addition or removal of discounted products when adding or removing them. Therefore, it is possible to prevent the registration of unfair products when adding or removing discounted products. Thus, it is possible to support fair transactions.

[0107] The following is a summary of the embodiments. [Title of Invention] Program and Registration Device [Technical field] The present invention relates to a program and a registration device. [Background technology] In recent years, systems have been known that use mobile terminal devices owned by customers to register products (see, for example, Patent Document 1). Products include fixed-weight products, which have a fixed price and whose weight and shape are determined for each individual product, and variable-weight products, whose price varies because the weight and quantity differ for each individual product. [Prior art document] [Patent] [Patent Document 1] Japanese Unexamined Patent Publication No. 2016-219034 [Overview of the prefecture] [Problems the invention aims to solve] However, with conventional technology, there was a problem in that the addition or deletion of certain products, such as variable-weight goods, could lead to improper product registration, which could prevent proper transactions. This invention has been made in view of these circumstances, and its purpose is to provide a technology that can support appropriate transactions.

[0108] [Means for solving the problem] (1) In order to solve the above-mentioned problems, a program according to one aspect of the present invention is a program that causes a computer to function as a registration device, characterized in that the computer functions as a registration means for registering products including specific products that are the same product but have different prices set for them, an addition / deletion means for adding or deleting products registered by the registration means, and a notification means that, when adding or deleting specific products of the same type as the specific products registered by the registration means, provides notification prompting confirmation regarding the specific products to be added or deleted. According to the above configuration, when adding or removing specific products, customers can be required to confirm the addition or deletion of those products. Therefore, it is possible to prevent the registration of improper products when adding or removing specific products. Thus, it is possible to support appropriate transactions.

[0109] (2) In the configuration of (1) above, the notification means may provide notification when multiple specific products of the same type are registered by the registration means and some of the specific products among the multiple specific products are to be deleted. According to the above configuration, it is possible to suppress unfair product registration, such as removing high-priced items from a list of multiple specific products of the same type and returning low-priced items to the shelves.

[0110] (3) In the configuration of (1) or (2) above, the computer may function as a change means for changing the quantity of goods registered by the registration means, and the change means may be configured to restrict changes in the quantity of specific goods registered by the registration means. According to the above configuration, when adding a specific product of the same type, it is possible to prevent fraudulent registrations such as purchasing a high-priced product at a low price by registering a low-priced product and setting the quantity of that product to "2". Furthermore, when deleting some of multiple specific products of the same type, it is possible to prevent fraudulent registrations such as deleting a high-priced product and returning a low-priced product to the shelves.

[0111] (4) In the configuration of (1) or (2) above, the computer may function as a reading means for reading product codes, the notification means may provide the notification prompting the reading of the product code attached to the specific product to be changed, and the addition / deletion means may add or delete the specific product to be added or deleted when the product code is read by the reading means. According to the above configuration, it is possible to add or remove specific products by reading their product codes, thereby improving the deterrent effect against fraudulent product registration.

[0112] (5) In the configuration of (1) or (2) above, the specified product may be a product of variable weight. According to the above configuration, it is possible to prevent unfair product registration when adding or removing variable-weight products.

[0113] (5) In order to solve the above-mentioned problems, another aspect of the present invention is a registration device comprising: a registration means for registering products including specific products that are the same product but have different prices set for them; an addition / deletion means for adding or deleting products registered by the registration means; and a notification means for prompting confirmation of the specific product to be added or deleted when adding or deleting a specific product of the same type as a specific product registered by the registration means. According to the above configuration, when adding or removing specific products, customers can be required to confirm the addition or deletion of those products. Therefore, it is possible to prevent the registration of improper products when adding or removing specific products. Thus, it is possible to support appropriate transactions.

[0114] Furthermore, all or part of the functions (input / output, storage, processing (including judgment)) of the registration and settlement system 1 (mobile terminal device 30, registration and settlement device) described above may be implemented in a device other than the device described as the entity executing the said function.

[0115] Specifically, the above description described a configuration in which the mobile terminal device 30 or the registration and settlement device is equipped with the functional units shown in Figure 4. All or part of each functional unit may be equipped on other computer devices. For example, all or part of each functional unit may be equipped on the store controller 10, on the cloud server Sv, or on other computer devices. Furthermore, the computer devices equipped with each functional unit are not limited to multiple units, but may consist of only one unit. For example, all of each functional unit may be equipped on a single computer device.

[0116] Specifically, for example, instead of the mobile terminal device 30, the store controller 10 or the cloud server Sv may issue instructions to provide confirmation notification regarding specific products of the same type as registered specific products when adding or removing them.

[0117] In relation to the above, the mobile terminal device 30 and the registration and settlement device may function as so-called thin clients specializing in input / output interface parts with respect to various displays, etc. That is, the mobile terminal device 30 and the registration and settlement device may receive various inputs (operator operations and device detection), transmit input information (operation information, detection information, etc.) to the cloud server Sv, receive the processing results of the cloud server Sv based on the input information (updated screen information, device control information, etc.), and perform various outputs (display on the display unit, device control).

[0118] Furthermore, the program for implementing the registration and settlement system 1 (mobile terminal device 30 and registration and settlement device) described above may be recorded on a computer-readable storage medium, and the program may be loaded into a computer system and executed. Here, "computer system" includes hardware such as the OS and peripheral devices. "Computer-readable storage medium" refers to portable media such as flexible disks, magneto-optical disks, ROMs, CD-ROMs, and storage devices such as hard disks built into a computer system. Moreover, "computer-readable storage medium" also includes volatile memory (RAM) inside a computer system that acts 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, which retains the program for a certain period of time. Furthermore, the above program may be transmitted from the computer system that stores the program in a storage device, etc., to another computer system via a transmission medium or by transmission waves in the transmission medium. Here, "transmission medium" for transmitting the program refers to a medium that has the function of transmitting information, such as a network such as the Internet or a communication line such as a telephone line. Furthermore, the above program may be for the purpose of implementing a part of the functions described above. Furthermore, the aforementioned functions may be implemented in combination with programs already recorded in the computer system, such as so-called differential files (differential programs). [Explanation of Symbols]

[0119] 1...Registration and settlement system, Sv...Cloud server, 10...Store controller, 11...Transaction status management device, 30...Mobile terminal device, 40...Settlement device, 201...CPU, 202...Memory, 203...Operation unit, 204...Communication I / F, 206...Display, 401...Registration unit, 402...Addition / deletion reception unit, 403...Addition / deletion unit, 404...Notification unit, 405...Change unit, 406...Reading unit

Claims

1. A program that makes a computer function as a registration device, The aforementioned computer, A registration method for registering products that include specific products that are the same product but have different prices set for them. Addition / removal means for adding or removing products registered by the registration means, When adding or removing specific products of the same type as those registered by the aforementioned registration means, a notification means provides notification prompting confirmation regarding the specific products to be added or removed. A program characterized by being designed to function as such.

2. The notification means provides notification when multiple specific products of the same type are registered by the registration means, and when some of the multiple specific products are to be deleted. The program according to feature 1.

3. The aforementioned computer, A change means for changing the quantity of goods registered by the registration means, To make it function as, The modification means restricts changes in the quantity of specific products registered by the registration means. The program according to claim 1 or 2.

4. The aforementioned computer, A reading device for reading product codes. To make it function as, The notification means provides the notification prompting the reading of the product code attached to the specific product to be changed. The addition / deletion means adds or deletes a specific product to be added or deleted when the product code is read by the reading means. The program according to claim 1 or 2.

5. The aforementioned specific product is a variable-weight product. The program according to claim 1 or 2.

6. A registration method for registering products that include specific products that are the same product but have different prices set, An addition / deletion means for adding or removing products registered by the registration means, When adding or removing specific products of the same type as those registered by the aforementioned registration means, a notification means provides a notification prompting confirmation regarding the specific products to be added or removed. A registration device characterized by comprising the following features.

Images