Product registration device and its program, product registration system

Abstract

We aim to improve the efficiency of operations related to services provided after payment. [Solution] The product registration device comprises a registration means, a reception means, an association means, and an output means. The registration means registers products to be purchased. The reception means accepts services to be applied to the products after payment. The association means associates and stores the products registered by the registration means with the services to be applied to the products. The output means outputs the products and services associated by the association means.

Description

Technical Field

[0001] Embodiments of the present invention relate to a product registration device, its program, and a product registration system.

Background Art

[0002] Generally, large stores such as supermarkets and department stores have service counters installed. At the service counter, services available to customers, such as a delivery service for delivering the products purchased by the customer to their home or the like, a packaging service for packaging products, etc., are accepted.

[0003] Customers using the service counter bring the products after settlement to the service counter and verbally inform the store clerk of the service they want to use and the products for which they request that service. The store clerk performs the service requested by the customer and records the type of the service and the products for which the request was received, for example, by entering them in a ledger or inputting them into a dedicated terminal. Also, if there is a charge for the service, the store clerk bills the customer and receives the payment.

[0004] Thus, regarding the services performed after settlement, various exchanges occur between the store clerk providing the service and the customer using the service, so it takes time to deal with the customer, and improvement in business efficiency is demanded.

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0006] The problem to be solved by the embodiments of the present invention is to provide a product registration device and its program, and a product registration system that can improve the efficiency of operations related to services performed after settlement. [Means for solving the problem]

[0007] In one embodiment, the product registration device comprises a registration means, a receiving means, an association means, an output means, and a summing means. The registration means registers the product to be purchased. The receiving means applies to the product after payment. Multiple types The service is accepted. The association means stores the association between the product registered by the registration means and the service applicable to that product. The output means outputs the product and service associated by the association means. The summing means adds the fee for the service accepted by the acceptance means to the price of the product registered by the registration means. The acceptance means is registered by the registration means A means for displaying a screen to select the type of service to apply to multiple products; a means for selecting the type of service; and a means for selecting the product to which the service will be applied with respect to the target product corresponding to the selected type of service included among the multiple products. The means include, choice by means choice The system associates and remembers the products and services that have been provided. [Brief explanation of the drawing]

[0008] [Figure 1] Figure 1 is a block diagram showing the schematic configuration of a product registration system, which is the first embodiment. [Figure 2] Figure 2 is a schematic diagram showing the main data structure of a product record. [Figure 3] Figure 3 is a schematic diagram showing the main data structure of member records. [Figure 4] Figure 4 is a schematic diagram showing the main data structure of a service record. [Figure 5] Figure 5 is a schematic diagram showing an example of a service record related to a delivery service. [Figure 6] Figure 6 is a schematic diagram showing an example of a service record related to packaging services. [Figure 7] Figure 7 is a block diagram showing the main circuit configuration of an information terminal. [Figure 8] Figure 8 is a block diagram showing the main circuit configuration of a payment terminal. [Figure 9]FIG. 9 is a block diagram showing the main circuit configuration of the mobile controller. [Figure 10] FIG. 10 is a schematic diagram showing the main data items stored in the transaction file. [Figure 11] FIG. 11 is a schematic diagram for explaining the main functions of the processor of the mobile controller. [Figure 12] FIG. 12 is a flowchart showing the main information processing procedures executed by the processor of the information terminal. [Figure 13] FIG. 13 is a flowchart showing the main information processing procedures executed by the processor of the information terminal. [Figure 14] FIG. 14 is a flowchart showing the main information processing procedures executed by the processor of the information terminal. [Figure 15] FIG. 15 is a flowchart showing the main information processing procedures executed by the processor of the information terminal. [Figure 16] FIG. 16 is a flowchart showing the main information processing procedures executed by the processor of the mobile controller. [Figure 17] FIG. 17 is a flowchart showing the main information processing procedures executed by the processor of the mobile controller. [[ID=2B]] [Figure 18] FIG. 18 is a flowchart showing the main information processing procedures executed by the processor of the mobile controller. [Figure 19] FIG. 19 is a flowchart showing the main information processing procedures executed by the processor of the mobile controller. ]> [Figure 20] FIG. 20 is a flowchart showing the main information processing procedures executed by the processor of the mobile controller [Figure 21] FIG. 21 is a flowchart showing the main information processing procedures executed by the processor of the mobile controller. [Figure 22] FIG. 22 is a flowchart showing the main information processing procedures executed by the processor of the mobile controller. [Figure 23]FIG. 23 is a flowchart showing the main information processing procedure executed by the processor of the mobile controller. [Figure 24] FIG. 24 is a flowchart showing the main information processing procedure executed by the processor of the mobile controller. [Figure 25] FIG. 25 is a flowchart showing the main information processing procedure executed by the processor of the settlement terminal according to the program. [Figure 26] FIG. 26 is a schematic diagram showing an example of a start screen displayed on the touch panel of the information terminal. [Figure 27] FIG. 27 is a schematic diagram showing an example of a registration screen displayed on the touch panel of the information terminal. [Figure 28] FIG. 28 is a schematic diagram showing an example of a service screen displayed on the touch panel of the information terminal. [Figure 29] FIG. 29 is a schematic diagram showing an example of a service screen after requesting a packaging service. [Figure 30] FIG. 30 is a schematic diagram showing an example of a service screen after receiving a negative response command. [Figure 31] FIG. 31 is a schematic diagram showing an example of a delivery destination designation screen displayed on the touch panel of the information terminal. [Figure 32] FIG. 32 is a schematic diagram showing an example of a printed receipt issued from the settlement terminal. [Figure 33] FIG. 33 is a block diagram showing the schematic configuration of the product registration system according to the second embodiment. [Figure 34] FIG. 34 is a block diagram showing the main circuit configuration of the self-POS terminal. [Figure 35] FIG. 35 is a flowchart showing the main information processing procedure executed by the processor of the self-POS terminal. [Figure 36] FIG. 36 is a flowchart showing the main information processing procedure executed by the processor of the self-POS terminal. [Figure 37] FIG. 37 is a flowchart showing the main information processing procedure executed by the processor of the self-POS terminal. [Figure 38] Figure 38 is a flowchart illustrating the main information processing steps performed by the processor of a self-service POS terminal. [Figure 39] Figure 39 is a schematic diagram showing an example of the registration screen. [Figure 40] Figure 40 is a schematic diagram showing an example of a service screen display. [Figure 41] Figure 41 is a schematic diagram showing an example of how the target product list screen is displayed. [Figure 42] Figure 42 is a schematic diagram showing an example of the display on the delivery address selection screen. [Figure 43] Figure 43 is a schematic diagram showing an example of how the target product list screen is displayed. [Modes for carrying out the invention]

[0009] Several embodiments will be described below with reference to the drawings. [First Embodiment] The first embodiment illustrates the product registration system 1 shown in Figure 1 as a product registration system that can improve the efficiency of operations related to services performed after payment at, for example, a service counter. This product registration system 1 is a system that is built in a store where each customer uses an information terminal 2 to register the products they purchase themselves. In this type of product registration system 1, the information terminal 2 can be, for example, a smartphone owned by the customer, a mobile terminal owned by the store and lent to the customer, or a tablet-type cart terminal attached to a shopping cart. In this embodiment, the case in which a smartphone is used as the information terminal 2 is illustrated. In addition, there are various services that customers can use at the service counter, but in this embodiment, a delivery service that delivers the products purchased by the customer to their home, etc., and a packaging service that packages the products are illustrated as examples.

[0010] [Description of the product registration system] Figure 1 is a block diagram showing the schematic configuration of product registration system 1. Product registration system 1 includes a payment terminal 11, an attendant terminal 12, a store server 13, a mobile controller 14, and an access point 15. Product registration system 1 also includes a communication network 16 such as a LAN (Local Area Network), and the payment terminal 11, attendant terminal 12, store server 13, mobile controller 14, and access point 15 are connected to this communication network 16 to construct product registration system 1. The communication network 16 may be wired or wireless. The communication network 16 may also use both wired and wireless connections.

[0011] The payment terminal 11 is a device for processing payments from customers who have purchased goods and for settling sales transactions with those customers. The payment terminal 11 may be operated by a customer or a store employee. The payment terminal 11 is also called a POS (Point of Sales) terminal or accounting machine, for example. The payment terminal 11 is installed in a separate checkout area from the sales floor where goods are displayed. There is no particular limit to the number of payment terminals 11 that can be installed.

[0012] The attendant terminal 12 is a device that has the function of displaying the monitoring image of the payment terminal 11 on a display device. The attendant terminal 12 is installed near the exit of the checkout area. An employee referred to as an attendant is stationed at the location where the attendant terminal 12 is installed. The monitoring image changes in response to the operation input to the payment terminal 11. The attendant monitors for customer errors, fraudulent operations, etc., from the information in the monitoring image.

[0013] The store server 13 is a computer that supports all aspects of store operations. To support these operations, the store server 13 manages various databases, including a product database 31, a member database 32, and a service database 33. The product database 31 is a collection of product records 311 (see Figure 2) created for each product sold in the store. The member database 32 is a collection of member records 321 (see Figure 3) created for each consumer who becomes a member. The service database 33 is a collection of service records 331 (see Figure 4) created for each type of service available at the service counter to consumers who have purchased products in the store, i.e., customers. Details of the product records 311, member records 321, and service records 331 will be described later.

[0014] Access point 15 is a device that receives connection requests from information terminals 2 as the end of the communication network 16 and relays communication to devices on the communication network 16. Access point 15 is installed within the store so that it can receive connection requests from information terminals 2 throughout the entire sales area. Multiple access points 15 may be installed in a distributed manner within the store to prevent communication dead zones.

[0015] The mobile controller 14 is a computer that processes information so that the information terminal 2, connected via the access point 15, can function as a product registration device, by performing bidirectional data communication with the information terminal 2. The mobile controller 14 is an example of a product registration device.

[0016] Figure 2 is a schematic diagram showing the main data structure of product record 311. Product record 311 includes product data such as product code, product name, and price, as well as a delivery target flag Fa and a packaging target flag Fb. The product code is a unique identification code set for each product to identify it individually. Each product usually has a barcode that represents the product code. Some products, such as fresh food, may not have a barcode. Products without a barcode are assigned an in-store code, which is a code system unique to the company or store.

[0017] The delivery target flag Fa is a 1-bit data that identifies whether or not a product is eligible for the delivery service. For example, frozen foods and some fresh foods are not eligible for the delivery service. In this embodiment, the delivery target flag Fa is set to "1" to indicate that a product is eligible for the delivery service, and to "0" to indicate that a product is not eligible.

[0018] The packaging target flag Fb is a 1-bit data that identifies whether or not a product is eligible for the packaging service. For example, some large products are not eligible for the packaging service. In this embodiment, the packaging target flag Fb is set to "1" to indicate that a product is eligible for the packaging service, and to "0" to indicate that a product is not eligible.

[0019] Figure 3 is a schematic diagram showing the main data structure of member record 321. Member record 321 includes member data such as member ID, name, and home address, as well as delivery addresses other than the home address. The member ID is a unique identification code set for each member. Members possess a member card that records information linked to their member ID. Alternatively, members have installed a member-only application (application software) on an information terminal 2 such as a smartphone that can display a barcode or QR code linked to their member ID.

[0020] The delivery address is any address other than the member's home address that was previously designated as the delivery address when using the delivery service. Therefore, member record 321 of a member who has not had products delivered to a location other than their home does not contain a delivery address. On the other hand, member record 321 of a member who has had products delivered to multiple locations other than their home contains all of those delivery addresses. In this way, by setting multiple delivery addresses, members can select their desired delivery address from among several options.

[0021] Figure 4 is a schematic diagram showing the main data structure of a service record 331. A service record 331 includes a service code, service name, service fee, and subcode. The service code is a unique identification code set for each type of service available to customers at the service counter. The service name is the name that indicates the service identified by that service code, and the service fee is the cost of that service. The subcode is a code used to identify a second service that is linked to the first service identified by the service code. The service database 33 also registers service records 331 where the subcode is used as the service code.

[0022] A specific example of service record 331 will be explained using Figures 5 and 6. Figure 5 shows an example of a service record 331 related to a delivery service. In this embodiment, the delivery service is primarily for home delivery, with a service fee of 300 yen. However, delivery to locations other than home is also possible, in which case a shipping fee is charged in addition to the service fee. For such a delivery service, a first service record 3311 and a second service record 3312 are registered in the service database 33. The first service record 3311 is a record related to a home delivery service, with the service code "100", the service name "Delivery Service", and the service fee "¥300". In addition, the service code "101" of the second service record 3312 is described as a subcode. The second service record 3312 is a record related to a delivery service to a location other than home, with the service code "101", the service name "Other Location", and the service fee "Shipping Fee". No subcode is described. Regarding shipping costs, a flat rate may be applied, or the shipping cost may be determined based on the delivery address by referring to a data table that sets shipping costs by region.

[0023] Figure 6 shows an example of a service record 331 related to a packaging service. In this embodiment, the packaging service is, in principle, simple packaging in which the product is wrapped in wrapping paper, and the service fee is free. However, gift packaging in which the product is wrapped in a special gift box is also possible, in which case a box fee is charged. For such packaging services, a third service record 3313 and a fourth service record 3314 are registered in the service database 33. The third service record 3313 is a record related to the simple packaging service, and the service code is "200", the service name is "Simple Packaging", and the service fee is "¥0". In addition, the service code "201" of the fourth service record 3314 is described as a subcode. The fourth service record 3314 is a record related to the gift packaging service, and the service code is "201", the service name is "Gift", and the service fee is "Box Fee". No subcode is described. Regarding the box fee, it may be a flat rate, or the box fee for each product may be determined by referring to a data table that sets box fees for each product.

[0024] [Description of the information terminal configuration] Figure 7 is a block diagram showing the main circuit configuration of the information terminal 2. The information terminal 2 includes a processor 21, main memory 22, auxiliary storage device 23, touch panel 24, camera 25, wireless unit 26, and system transmission line 27, etc. The system transmission line 27 includes an address bus, data bus, control signal lines, etc. The system transmission line 27 connects the processor 21 and the other parts directly or via signal input / output circuits, and transmits data signals exchanged between them.

[0025] The processor 21 corresponds to the central part of the computer described above. The processor 21 controls various parts in order to realize various functions as an information terminal 2 according to the operating system or application program. The processor 21 is, for example, a CPU (Central Processing Unit).

[0026] Main memory 22 corresponds to the main memory portion of the computer described above. Main memory 22 includes non-volatile memory areas and volatile memory areas. In the non-volatile memory area, main memory 22 stores the operating system or application programs. Main memory 22 may also store data necessary for the processor 21 to perform processing to control each part in non-volatile or volatile memory areas. Main memory 22 uses the volatile memory area as a work area where data is rewritten as needed by the processor 21. The non-volatile memory area is, for example, ROM (Read Only Memory). The volatile memory area is, for example, RAM (Random Access Memory).

[0027] The auxiliary storage device 23 corresponds to the auxiliary storage portion of the computer described above. For example, an EEPROM (Electric Erasable Programmable Read-Only Memory), an SD memory card, etc., can serve as the auxiliary storage device 23 of the information terminal 2. The auxiliary storage device 23 stores data used by the processor 21 in performing various processes, data created by the processing performed by the processor 21, etc. The auxiliary storage device 23 may also store the application program described above.

[0028] The touch panel 24 is a device that combines an input device and a display device. The touch panel 24 displays information to the operator of the information terminal 2 and also accepts operation input from the operator. The operator is typically a customer shopping at a store.

[0029] Camera 25 is an imaging device mounted on the information terminal 2. Camera 25 operates as a still image or video capture device, or as a data code scanning device such as a barcode or two-dimensional code, depending on the application program installed on the information terminal 2. Camera 25 is an example of a code reader.

[0030] The wireless unit 26 is a circuit for performing data communication with the access point 15 in accordance with the wireless LAN communication protocol.

[0031] The information terminal 2 with this configuration has a shopping support program 231 installed on its auxiliary storage device 23 in order to make it usable with the product registration system 1. The shopping support program 231 is a type of application software and is installed on the information terminal 2 using the internet or the like. When the shopping support program 231 is installed on the information terminal 2, a portion of the storage area of ​​the auxiliary storage device 23 is designated as the user ID area 232 and the member ID area 233.

[0032] The User ID area 232 is a region for storing a unique User ID, which is set for each user to individually identify users of information terminal 2. Each information terminal 2 on which the shopping support program 231 is installed has a different User ID stored in the User ID area 232. A User ID stored in the User ID area 232 of one information terminal 2 will not overlap with a User ID stored in the User ID area 232 of another information terminal 2. In this specification, users may be referred to as consumers, customers, members, etc.

[0033] The Member ID area 233 is a region for storing the Member ID assigned to each member. One of the functions of the Shopping Support Program 231 is the Member ID linkage function. By using this linkage function, a member who is a user of the information terminal 2 can register their own Member ID, and that Member ID will be stored in the Member ID area 233. If the user does not use the linkage function, the Member ID will not be stored in the Member ID area 233.

[0034] [Description of Payment Terminal Configuration] Figure 8 is a block diagram showing the main circuit configuration of the payment terminal 11. The payment terminal 11 includes a processor 41, main memory 42, auxiliary storage device 43, clock 44, communication interface 45, touch panel 46, scanner 47, printer 48, reader / writer 49, change dispenser interface 410, and system transmission path 411, etc. The system transmission path 411 includes an address bus, data bus, control signal lines, etc. The system transmission path 411 connects the processor 41 and the other parts directly or via signal input / output circuits, and transmits data signals exchanged between them.

[0035] The payment terminal 11 is configured as a computer by connecting the processor 41, main memory 42, auxiliary storage device 43, clock 44, and communication interface 45 via a system transmission path 411. The payment terminal 11 then connects device interfaces or devices such as a touch panel 46, scanner 47, printer 48, reader / writer 49, and change dispenser interface 410 to this computer via the system transmission path 411.

[0036] The processor 41 corresponds to the central part of the computer described above. The processor 41 controls each part in order to realize various functions as a payment terminal 11 according to the operating system or application program. The processor 41 is, for example, a CPU.

[0037] Main memory 42 corresponds to the main memory portion of the computer described above. Main memory 42 includes a non-volatile memory area and a volatile memory area. In the non-volatile memory area, main memory 42 stores the operating system or application programs. Main memory 42 may also store data necessary for the processor 41 to perform processing to control each part in the non-volatile or volatile memory area. Main memory 42 uses the volatile memory area as a work area where data is rewritten as appropriate by the processor 41. The non-volatile memory area is, for example, ROM. The volatile memory area is, for example, RAM.

[0038] The auxiliary storage device 43 corresponds to the auxiliary storage portion of the computer described above. For example, an EEPROM, HDD (Hard Disk Drive), or SSD (Solid State Drive) can serve as the auxiliary storage device 43 of the payment terminal 11. The auxiliary storage device 43 stores data used by the processor 41 in performing various processes, data created by the processing performed by the processor 41, etc. The auxiliary storage device 43 may also store the application program described above.

[0039] Clock 44 measures the date and time. Processor 41 processes the date and time measured by clock 44 as the current date and time.

[0040] The communication interface 45 is a circuit for performing data communication with the store server 13, mobile controller 14, etc., which are connected via the communication network 16.

[0041] The touch panel 46 is a device that combines an input device and a display device. The touch panel 46 displays information to the operator of the payment terminal 11 and accepts operation input from the operator. The operator may be a customer or a store employee.

[0042] Scanner 47 is an example of a reading device that reads code symbols such as barcodes and two-dimensional codes. Scanner 47 may be a type that reads code symbols by scanning with a laser beam, or a type that reads code symbols from an image captured by an imaging device.

[0043] The printer 48 issues a purchase receipt by printing various strings of characters or images onto receipt paper. The purchase receipt is a receipt that prints the product names, prices, and total amounts of the items purchased by the customer. Examples of printers 48 of this type include thermal printers and dot matrix printers. The payment terminal 11 may also have an electronic receipt function that digitizes the receipt data and provides it to the customer.

[0044] The reader / writer 49 has the function of reading data recorded on a medium such as a card or smartphone, and the function of writing data to the aforementioned medium. The card may include payment cards such as credit cards, debit cards, electronic money cards, and prepaid cards, as well as membership cards such as company point cards and common point cards. The reader / writer 49 may be a magnetic, contact, or contactless device, or may include multiple types of devices.

[0045] The change dispenser interface 410 forms an interface with an automatic change dispenser (not shown). The change dispenser interface 410 receives monetary data of the money inserted into the automatic change dispenser from the automatic change dispenser. The change dispenser interface 410 outputs change data from the payment terminal 11 to the automatic change dispenser. The automatic change dispenser, having received the change data, automatically dispenses the amount of money corresponding to that change data as change.

[0046] The payment terminal 11 having such hardware configuration is capable of cash payment processing, which settles sales transactions with customers using cash deposited into an automatic change dispenser; credit payment processing, which settles transactions using credit cards read by a reader / writer 49; electronic money payment processing, which settles transactions using electronic money identified by an electronic money ID read by a scanner 47 or reader / writer 49; and code payment processing, which settles transactions using a barcode or two-dimensional code read by a scanner. Since cash payment processing, credit payment processing, electronic money payment processing, and code payment processing are well-known processes, a detailed explanation will be omitted.

[0047] [Mobile Controller Configuration Description] Figure 9 is a block diagram showing the main circuit configuration of the mobile controller 14. The mobile controller 14 includes a processor 51, main memory 52, auxiliary storage device 53, clock 54, communication interface 55, and system transmission path 56, etc. The system transmission path 56 includes an address bus, data bus, control signal lines, etc. The system transmission path 56 connects the processor 51 and the other parts directly or via signal input / output circuits, and transmits data signals exchanged between them.

[0048] The mobile controller 14 constitutes a computer by connecting the processor 51, main memory 52, auxiliary storage device 53, clock 54, and communication interface 55 via a system transmission path 56.

[0049] The processor 51 corresponds to the central part of the computer described above. The processor 51 controls each part in order to realize various functions as a mobile controller 14 according to the operating system or application program. The processor 51 is, for example, a CPU.

[0050] Main memory 52 corresponds to the main memory portion of the computer described above. Main memory 52 includes a non-volatile memory area and a volatile memory area. In the non-volatile memory area, main memory 52 stores the operating system or application programs. Main memory 52 may also store data necessary for the processor 51 to perform processing to control each part in the non-volatile or volatile memory area. Main memory 52 uses the volatile memory area as a work area where data is rewritten as appropriate by the processor 51. The non-volatile memory area is, for example, ROM. The volatile memory area is, for example, RAM.

[0051] The auxiliary storage device 53 corresponds to the auxiliary storage portion of the computer described above. For example, an EEPROM, HDD, or SSD can serve as the auxiliary storage device 53 of the mobile controller 14. The auxiliary storage device 53 stores data used by the processor 51 in performing various processes, data created by the processing performed by the processor 51, and so on. The auxiliary storage device 53 may also store the application program described above.

[0052] Clock 54 measures the date and time. Processor 51 processes the date and time measured by clock 54 as the current date and time.

[0053] The communication interface 55 is a circuit for performing data communication with the payment terminal 11, attendant terminal 12, store server 13, access point 15, etc., which are connected via the communication network 16.

[0054] In this configuration, the mobile controller 14 uses a portion of the volatile memory area of ​​the main memory 52 as the storage area for the transaction file 521. The transaction file 521 is a data file created for each customer who performs the registration operation of the products to be purchased using the information terminal 2, a so-called self-service operation.

[0055] Figure 10 is a schematic diagram showing the main data items stored in the transaction file 521. As shown in Figure 10, the transaction file 521 stores at least the user ID, member ID, delivery declaration flag Fc, one or more product sales data, the service status and service code associated with each product sales data, the service fee, and total data.

[0056] The delivery declaration flag Fc is a 1-bit data that identifies whether or not a customer requests delivery service for all items purchased at the store. In this embodiment, the delivery declaration flag Fc is set to "1" when delivery service is requested for all items. A user who requests delivery service for all items enters the delivery request key from the start screen 100 (see Figure 26) displayed on the touch panel 24 of the information terminal 2 before starting shopping at the store. As a result of this operation, the delivery declaration flag Fc in the transaction file 521 where the customer's user ID is stored becomes "1".

[0057] Product sales data is data related to the sale of products registered via information terminal 2, so-called registered products. Product sales data includes product code, product name, price, number of units sold, sales amount, delivery target flag Fa, packaging target flag Fb, etc.

[0058] The service status and service code are examples of service data related to the services applied to registered products. In this embodiment, there are two types of services applied to registered products: delivery service and packaging service. Therefore, in this embodiment, the service status is two digits, with the tens digit representing information related to the delivery service and the units digit representing information related to the packaging service. Specifically, for registered products to which the delivery service applies, the tens digit in the service status is set to "1", and for registered products to which the delivery service does not apply, the tens digit in the service status is set to "0". Similarly, for registered products to which the packaging service applies, the units digit in the service status is set to "1", and for registered products to which the packaging service does not apply, the units digit in the service status is set to "0". Incidentally, if there are three or more types of services applied to a registered product, the number of digits in the service status should match the number of service types.

[0059] The service codes are as explained using Figures 4 to 6. Specifically, for registered products to which home delivery service applies, the service code is "100," and for registered products to which delivery service to an address other than home applies, the service code is "101." Similarly, for registered products to which simple packaging service applies, the service code is "200," and for registered products to which gift packaging service applies, the service code is "201." Hereafter, the service code related to delivery service will be referred to as the delivery code, and the service code related to packaging service will be referred to as the packaging code.

[0060] The service fee is the total cost of the services applied to the registered product. If shipping or packaging fees are incurred for the applicable services, these fees will also be added to the service fee.

[0061] The total data includes the total number of items and total amount data for registered products. The total number of items is the sum of the sales figures for the product sales data stored in transaction file 521, and the total amount data is the sum of the sales amounts for the same product sales data. If a service fee is charged for the services applied to the registered product, the service fee will be added to the total amount.

[0062] Figure 11 is a schematic diagram illustrating the main functions of the processor 51. The mobile controller 14 implements a control program such that the processor 51 functions as a registration means 511, a receiving means 512, an association means 513, an output means 514, an aggregation means 515, a delivery destination determination means 516, and a packaging method determination means 517. The control program is a type of application program stored in the main memory 52 or auxiliary storage device 53. The method of installing the control program in the main memory 52 or auxiliary storage device 53 is not particularly limited. The control program can be recorded on a removable recording medium, or distributed via communication through the communication network 16 and installed in the main memory 52 or auxiliary storage device 53. The recording medium can be of any form as long as it can store a program and is readable by the device, such as a CD-ROM or memory card.

[0063] The registration means 511 is a function for registering the products to be purchased. Based on data from the information terminal 2 operated by the customer purchasing the products, the registration means 511 registers product sales data related to the products to be purchased in the transaction file 521.

[0064] The reception means 512 is a function that accepts services to be applied to goods after payment. The reception means 512 accepts multiple types of services via the information terminal 2. In this embodiment, the reception means 512 accepts delivery services and packaging services.

[0065] The association means 513 has the function of associating and storing the goods registered by the registration means 511 with the services applicable to those goods. The association means 513 stores the service data, that is, the service status and service code (delivery code, packaging code), in association with the product sales data registered in the transaction file 521 on the transaction file 521.

[0066] The output means 514 has the function of outputting the products and services associated by the association means 513. The output means 514 outputs product sales data and service data to the payment terminal 11 which performs payment for products registered by the registration means 511. The output means 514 may output the product sales data and service data to the payment terminal 11 via, for example, the store server 13. If the information terminal 2 has a payment function, the output means 514 may output the product sales data and service data to the information terminal 2 and use it for payment processing at the information terminal 2.

[0067] The aggregation means 515 has the function of adding the service fee received by the reception means 512 to the price of the goods registered by the registration means 511. For example, in the payment terminal 11, payment processing is performed on the amount obtained by adding the service fee to the price of the goods.

[0068] The delivery destination determination means 516 is a function that determines the delivery destination of the product when a delivery service is accepted by the acceptance means 512. As mentioned above, the delivery destination can be the home or a location other than the home.

[0069] The packaging method determination means 517 is a function that determines the packaging method for the product when a packaging service is received by the reception means 512. As mentioned above, the packaging methods include simple packaging and gift packaging. Details of each function will be explained in detail in the following operation description.

[0070] [Explanation of how the product registration system works] Figures 12 to 15 are flowcharts showing the main information processing steps performed by the processor 21 of the information terminal 2 according to the shopping support program 231. Figures 16 to 24 are flowcharts showing the main information processing steps performed by the processor 51 of the mobile controller 14 according to the control program. Figure 25 is a flowchart showing the main information processing steps performed by the processor 41 of the payment terminal 11 according to the program. Figures 26 to 31 are schematic diagrams showing an example of the main screen display on the touch panel 24 of the information terminal 2. Figure 32 is a schematic diagram showing an example of a receipt printout issued from the payment terminal 11. The main operations of the product registration system 1 will be explained below using these figures. Note that the operations described below are examples. The operation procedures and contents are not particularly limited as long as similar results can be obtained. Also, the screen display and receipt printout layout, text data, etc. are examples and can be changed as appropriate.

[0071] <Explanation of information terminal operation> First, using the flowcharts in Figures 12 to 15 and the screen examples in Figures 26 to 31, we will explain the main operations of the information terminal 2 when a customer who has self-registered the products they wish to purchase using the information terminal 2 then requests a delivery or packaging service after payment.

[0072] When the shopping support program 231 is started, the processor 21 of the information terminal 2 begins processing the procedures shown in the flowcharts in Figures 12 to 15. First, the processor 21 waits for the entry code to be entered as ACT1. The entry code is a code that encodes the store's configuration information into a predetermined two-dimensional code system, and is provided, for example, at the entrance of the store. The configuration information includes, for example, parameters necessary for the information terminal 2 to communicate with the access point 15 using a wireless LAN, or information related to the operational restrictions of the information terminal 2. When a customer enters the store, they have the camera 25 of the information terminal 2 read the entry code.

[0073] When the entry code is read by camera 25, processor 21 controls wireless unit 26 as ACT2 and connects to access point 15 using wireless LAN. Once connected to access point 15, processor 21 retrieves the user ID from user ID area 232 as ACT3. Also, if a member ID is stored in member ID area 233, processor 21 retrieves the member ID as well.

[0074] The processor 21 controls the wireless unit 26 to send a check-in request command as ACT4. This control causes the check-in request command to be transmitted wirelessly via the wireless unit 26. The check-in request command is received by the access point 15 and transmitted to the mobile controller 14 via the communication network 16. The check-in request command includes the user ID. If a member ID has also been obtained along with the user ID, that member ID is also included in the check-in request command.

[0075] The processor 21, which sent the check-in request command, waits for an acceptance response command as ACT5. As will be explained later using Figure 17, the mobile controller 14 that received the check-in request command sends back an acceptance response command. When the processor 21 receives the acceptance response command via the wireless unit 26, it sets the screen of the touch panel 24 to the start screen 100 (see Figure 26) as ACT6.

[0076] Figure 26 is a schematic diagram showing one example of the display of the start screen 100. The start screen 100 has two soft keys: a delivery request key 101 and a start key 102. The delivery request key 101 is entered by customers who have decided to request delivery service for all items they will purchase at the store before starting their shopping. The start key 102 is entered by other customers when they start shopping at the store.

[0077] The processor 21, displaying the start screen 100, waits for either the delivery request key 101 to be entered as ACT7 or the start key 102 to be entered as ACT8. When the delivery request key 101 is entered while waiting for ACT7 or ACT8, the processor 21 proceeds from ACT7 to ACT9. The processor 21 controls the wireless unit 26 to send a delivery declaration request command as ACT9. This control causes the delivery declaration request command to be transmitted wirelessly via the wireless unit 26. The delivery declaration request command is received by the access point 15 and sent to the mobile controller 14 via the communication network 16. The delivery declaration request command includes a user ID.

[0078] The processor 21 that sent the delivery declaration request command waits for an acceptance response command as ACT10. As will be explained later using Figure 18, the mobile controller 14 that received the delivery declaration request command sends back an acceptance response command. When the processor 21 receives the acceptance response command via the wireless unit 26, it sets the screen of the touch panel 24 as the registration screen 110 (see Figure 27) as ACT11.

[0079] On the other hand, if the start key 102 is entered while in the standby state of ACT7 or ACT8, the processor 21 proceeds from ACT8 to ACT11. The processor 21 sets the screen of the touch panel 24 as the registration screen 110 as ACT11. In this way, when the customer enters the delivery request key 101 on the start screen 100 or enters the start key 102, the screen of the touch panel 24 transitions from the start screen 100 to the registration screen 110.

[0080] Figure 27 is a schematic diagram showing one example of the display of the registration screen 110. The registration screen 110 comprises a details area 111 and a total area 112 for registered products, and an operation key area 113. The details area 111 displays details data such as the product name, number of items sold, and sales amount for products registered by the operation of the information terminal 2. The total area 112 displays the total number of items and total amount for registered products. Note that at the time of ACT 11, no products have been registered, so no information is displayed in the details area 111 and the total area 112.

[0081] The operation key area 113 displays soft keys for barcode, no barcode, and payment. The barcode key is entered by the customer when registering products with barcodes. When the barcode key is entered, the camera 25 is activated, and the customer scans the barcode attached to the product with the camera 25. The no barcode key is entered by the customer when registering products without barcodes. When the no barcode key is entered, a list of products without barcodes is displayed on the touch panel 24, and the customer selects the product they wish to purchase from that list. The payment key is entered by the customer when they have finished shopping and declare that they wish to pay.

[0082] The processor 21, displaying the registration screen 110, waits for the customer to perform the registration operation for the product they wish to purchase as ACT 12. The product registration operation involves either entering a barcode key to scan the product's barcode with the camera 25, or entering a no-barcode key to select a product without a barcode from the product list. Through such a product registration operation, the processor 21 can obtain the product code of the registered product.

[0083] After the customer confirms the registration screen 110, they begin shopping. When they find an item they wish to purchase from the items displayed on the sales floor, the customer registers that item on the information terminal 2. In ACT 12, once the item registration operation is completed, the processor 21 proceeds to ACT 13 in Figure 13. In ACT 13, the processor 21 obtains the product code of the registered item. For example, if the registration operation was performed by entering a barcode key, the product code of the registered item is obtained from that barcode. For example, if the registration operation was performed by entering no barcode key, the product code of the registered item selected from the list is obtained.

[0084] The processor 21, having obtained the product code of the registered product, controls the wireless unit 26 to send a product registration request command as ACT 14. This control causes the product registration request command to be transmitted wirelessly via the wireless unit 26. The product registration request command is received by the access point 15 and sent to the mobile controller 14 via the communication network 16. The product registration request command includes the user ID and the product code of the product to be registered.

[0085] The processor 21 that sent the product registration request command waits for an acceptance response command as ACT15. As will be explained using Figure 19 below, the mobile controller 14 that received the product registration request command sends back an acceptance response command. The acceptance response command contains data from the transaction file 521 created for the customer identified by the user ID. Upon receiving the acceptance response command, the processor 21 stores the data from the transaction file 521 in the main memory 22 as ACT16. Then, the processor 21 updates the data in the detail area 111 and the total area 112 of the registration screen 110 based on the data from the transaction file 521.

[0086] Figure 27 illustrates the registration screen 110 after a customer has registered one unit each of three items: product AAA (priced at 300 yen), product BBB (priced at 200 yen), and product CCC (priced at 100 yen). The details area 111 displays the product name, number of units sold, and sales amount as detailed data for each registered product, on a separate line. The total area 112 displays the total number of units and total amount as total data. The customer can change the number of units sold by touching the number of units sold in the details data. Changing the number of units sold also updates the sales amount in the details data. The total number of units and total amount are also updated.

[0087] In the details area 111, a service key 114 is displayed for each item of data. The customer enters the service key 114 when applying a delivery service or packaging service to the purchased item. The service key 114 is an example of an individual instruction means that instructs the application of a service individually to a registered item. For example, to apply a delivery service to item AAA, the customer enters the service key 114 in the row where the item data for item AAA is displayed. For example, to apply a packaging service to item BBB, the customer enters the service key 114 in the row where the item data for item BBB is displayed.

[0088] In addition, in the details area 111, a delivery service mark 115 and a packaging service mark 116 can be displayed for each line. The delivery service mark 115 is displayed when a request for delivery service is received for a product whose details data is displayed on the same line. The packaging service mark 116 is displayed when a request for packaging service is received for a product whose details data is displayed on the same line.

[0089] Returning to the explanation of Figure 13. The processor 21, having updated the registration screen 110, waits for either a product registration operation to be performed as ACT17, a service key 114 to be entered as ACT18, or a payment key to be entered as ACT19. If a product registration operation is performed using a barcode key or no barcode key while waiting for ACT17 through ACT19, the processor 21 returns to ACT13. The processor 21 executes the processing of ACT13 through ACT16 in the same manner as described above. Then the processor 21 returns to the waiting state for ACT17 through ACT19 once again.

[0090] When a service key 114 is entered while the system is in the waiting state of ACT17 through ACT19, the processor 21 proceeds from ACT18 to ACT21 in Figure 14. The processor 21 selects the product identified in the detail data of the line displaying the service key 114 entered as ACT21 as the product requested for service. For example, in Figure 27, if a service key 114 displayed on the same line as the detail data for product CCC is entered, the processor 21 selects product CCC as the product requested for service. The processor 21 then displays the service screen 120 (see Figure 28) on the touch panel 24 as ACT22. The service screen 120 is displayed as a pop-up overlaid on the registration screen 110.

[0091] Figure 28 is a schematic diagram showing one example of the service screen 120. The service screen 120 comprises a details area 121 for the requested service item and an operation key area 122. The details area 121 displays the product name, number of items sold, sales amount, etc. for the requested service item. The operation key area 122 displays a delivery key, a packaging key, and a return key as soft keys. The delivery key is entered when the customer requests a delivery service. The packaging key is entered when the customer requests a packaging service. The return key is entered when the customer cancels a service request.

[0092] The processor 21, displaying the service screen 120, waits for either a delivery key to be entered as ACT23, a packaging key as ACT24, or a return key as ACT25. If a return key is entered while waiting for ACT23 through ACT25, the processor 21 proceeds from ACT25 to ACT35. The processor 21 clears the service screen 120 as ACT35 and returns to ACT16 in Figure 13.

[0093] If a delivery key is entered while the system is in the waiting state of ACT23 through ACT25, the processor 21 proceeds from ACT23 to ACT26. The processor 21 refers to the data of the transaction file 521 stored in the main memory 22 as ACT26 and checks whether the tens digit of the service status in the service data associated with the product sales data of the product requested for service is "1". If the tens digit of the service status is "0", a delivery service has not yet been requested for the product requested for service. If the tens digit of the service status is "1", a delivery service has already been requested for the product requested for service.

[0094] If the tens digit of the service status is "0", meaning the customer is requesting delivery service, the processor 21 proceeds to ACT 27. The processor 21 controls the wireless unit 26 to send a delivery setup request command as ACT 27. This control causes the delivery setup request command to be transmitted wirelessly via the wireless unit 26. The delivery setup request command is received by the access point 15 and transmitted to the mobile controller 14 via the communication network 16. The delivery setup request command includes the user ID and the product code of the service requested item.

[0095] If the tens digit of the service status in ACT26 is "1", meaning the customer cancels the delivery service request, the processor 21 proceeds to ACT28. The processor 21 controls the wireless unit 26 to send a delivery cancellation request command as ACT28. This control causes the delivery cancellation request command to be transmitted wirelessly via the wireless unit 26. The delivery cancellation request command is received by the access point 15 and transmitted to the mobile controller 14 via the communication network 16. The delivery cancellation request command includes the user ID and the product code of the service request item.

[0096] If a packaging key is entered while the system is in the waiting state of ACT23 through ACT25, the processor 21 proceeds from ACT24 to ACT29. The processor 21 refers to the data of the transaction file 521 stored in the main memory 22 as ACT29 and checks whether the last digit of the service status associated with the product sales data of the product requested for service is "1". If the last digit of the service status is "0", packaging service has not yet been requested for the product requested for service. If the last digit of the service status is "1", packaging service has already been requested for the product requested for service.

[0097] If the units digit of the service status is "0", that is, if the customer requests a wrapping service, the processor 21 proceeds to ACT30. The processor 21 waits for the wrapping method to be specified as ACT30. Specifically, as shown in Figure 29, the processor 21 changes the soft keys displayed in the operation key area 122 of the service screen 120 to the simple wrapping key and the gift wrapping key. The simple wrapping key is entered when the customer specifies simple wrapping as the wrapping method. The gift wrapping key is entered when the customer specifies gift wrapping as the wrapping method.

[0098] The processor 21 waits for a simple packaging key or a gift key to be entered in ACT 30. When a simple packaging key or a gift key is entered, the processor 21 controls the wireless unit 26 to send a packaging setting request command as ACT 31. This control causes the packaging setting request command to be transmitted wirelessly via the wireless unit 26. The packaging setting request command is received by the access point 15 and transmitted to the mobile controller 14 via the communication network 16. The packaging setting request command includes data for the user ID, the product code of the service requested item, and the packaging method. The packaging method data indicates simple packaging if a simple packaging key is entered in ACT 30. The packaging method data indicates gift packaging if a gift key is entered in ACT 30.

[0099] In ACT29, if the units digit of the service status is "1", meaning the customer cancels the request for packaging service, the processor 21 proceeds to ACT32. The processor 21 controls the wireless unit 26 to send a packaging cancellation request command as ACT32. This control causes the packaging cancellation request command to be transmitted wirelessly via the wireless unit 26. The packaging cancellation request command is received by the access point 15 and transmitted to the mobile controller 14 via the communication network 16. The packaging cancellation request command includes the user ID and the product code of the service requested item.

[0100] The processor 21 that sent the delivery setting request command, delivery cancellation request command, packaging setting request command, or packaging cancellation request command waits for a response command as ACT33. As will be explained using Figures 20 and 21 below, the mobile controller 14 that received the delivery setting request command, delivery cancellation request command, packaging setting request command, or packaging cancellation request command replies with either an acceptance response command or a rejection response command. If the goods for which the delivery service or packaging service has been requested are eligible for that service, the mobile controller 14 replies with an acceptance response command. If the goods for which the delivery service or packaging service has been requested are not eligible for that service, the mobile controller 14 replies with a rejection response command.

[0101] Upon receiving the acceptance response command in ACT33, the processor 21 proceeds to ACT35. In ACT35, the processor 21 clears the service screen 120 and returns to ACT16 in Figure 13. The processor 21 updates the registration screen 110 based on the data in the transaction file 521 included in the acceptance response command. After that, the processor 21 enters a waiting state for ACT17 through ACT19.

[0102] Upon receiving a negative response command in ACT33, the processor 21 proceeds to ACT34. As ACT34, the processor 21 waits for the customer to confirm their input. Specifically, as shown in Figure 30, the processor 21 changes the soft keys displayed in the operation key area 122 of the service screen 120 to confirmation keys. In addition, a message notifying the customer that the product for which delivery or packaging services were specified is not covered by those services is displayed in the operation key area 122. Upon seeing this message, the customer enters the confirmation key. Once the confirmation key is entered, the processor 21 proceeds to ACT35. As ACT35, the processor 21 clears the service screen 120 and returns to ACT16 in Figure 13. The negative response command does not contain any data from the transaction file 521. Therefore, the processor 21 does not update the registration screen 110 and enters a waiting state for ACT17 to ACT19.

[0103] If a payment key is entered while the system is in the waiting state of ACT17 through ACT19, the processor 21 proceeds from ACT19 to ACT41 in Figure 15. The processor 21 checks whether there are any products for which delivery service has been requested among the products registered as ACT41. If there is a service status with a tens digit of "1" in the status data associated with the product sales data contained in the transaction file stored in the main memory 22, the processor 21 recognizes that there are products for which delivery service has been requested. If there is no service status with a tens digit of "1", the processor 21 recognizes that there are no products for which delivery service has been requested.

[0104] If there are items for which delivery service has been requested, processor 21 proceeds to ACT42. Processor 21 checks whether the user of information terminal 2 is a member or not as ACT42. If a member ID is stored in member ID area 233, processor 21 recognizes that the user is a member. If a member ID is not stored in member ID area 233, processor 21 recognizes that the user is not a member.

[0105] If the user is a member, the processor 21 proceeds to ACT43. The processor 21 controls the wireless unit 26 to send a delivery destination request command as ACT43. This control causes the delivery destination request command to be transmitted wirelessly via the wireless unit 26. The delivery destination request command is received by the access point 15 and sent to the mobile controller 14 via the communication network 16. The delivery destination request command includes the user ID and the member ID.

[0106] The processor 21 that sent the delivery destination request command waits for an acceptance response command as ACT44. As will be explained using Figure 22 below, the mobile controller 14 that received the delivery destination request command replies with an acceptance response command. Upon receiving the acceptance response command, the processor 21 displays the delivery destination specification screen 130 (see Figure 31) on the touch panel 24 as ACT45.

[0107] Figure 31 is a schematic diagram showing one example of the display of the delivery destination selection screen 130. The delivery destination selection screen 130 consists of a point area 131 and an operation key area 132. The point area 131 displays the total number of items for which delivery service has been requested. The operation key area 132 displays a home key and an other key as soft keys. Customers who specify their home as the delivery destination input the home key. Customers who specify a delivery destination other than their home input the other key.

[0108] The processor 21, displaying the delivery address selection screen 130, waits for the delivery address to be specified as ACT46. If the home key is entered, the processor 21 recognizes that the home address has been specified as the delivery address. If any other key is entered, the processor 21 recognizes that a delivery address other than the home address has been specified. If a delivery address is registered in the member record 321, which is identified by the member ID of the customer who entered the other key, a list of delivery addresses, or the so-called delivery address list, is displayed on the touch panel 24. The customer then selects the desired delivery address from the delivery address list. Once an address is selected, the processor 21 recognizes that that address has been specified as the delivery address. If the desired delivery address is not in the delivery address list, the customer selects "None". In the case of "None", the processor 21 recognizes that a delivery address other than the home address has been specified.

[0109] If a delivery address is specified, processor 21 proceeds to ACT47. On the other hand, if there is no delivery request in ACT41, processor 41 skips the processing of ACT42 through ACT46 and proceeds to ACT47. Also, if the user is not a member in ACT42, processor 21 skips the processing of ACT43 through ACT46 and proceeds to ACT47.

[0110] Thus, if a delivery destination is specified through the processing of ACT43 to ACT46, or if the processing of ACT43 to ACT46 is skipped, the processor 21 proceeds to ACT47. The processor 21 controls the wireless unit 26 to send a payment request command as ACT47. This control causes the payment request command to be transmitted wirelessly via the wireless unit 26. The payment request command is received by the access point 15 and sent to the mobile controller 14 via the communication network 16. The payment request command includes the user ID. If a delivery destination is specified, information indicating that delivery destination is also included in the payment request command. That is, if the home key is entered, the payment request command includes information indicating that home has been specified as the delivery destination. If any other key is entered, the payment request command includes information indicating that a delivery destination other than home, or a delivery address, has been specified.

[0111] The processor 21 that sent the payment request command waits for an acceptance response command as ACT48. As will be explained using Figure 23 below, the mobile controller 14 that received the payment request command replies with an acceptance response command. The acceptance response command includes an accounting code. The accounting code is a unique code that is generated each time a payment request command is received. Upon receiving the acceptance response command, the processor 21 displays an accounting barcode, which represents the accounting code in barcode form, on the touch panel 24 as ACT49.

[0112] The processor 21, displaying the accounting barcode, waits for the accounting start command as ACT50. The accounting barcode is the barcode read by the scanner 77 of the payment terminal 11. When the payment terminal 11 reads the accounting barcode with the scanner 77, the payment process begins. At this time, as will be explained using Figure 24 below, the mobile controller 14 sends the accounting start command to the information terminal 2, which is the source of the payment request command. Upon receiving the accounting start command, the processor 21 erases the accounting barcode on the touch panel 24 as ACT51. With this, the processor 21 completes the information processing for the procedure shown in the flowcharts in Figures 12 to 15.

[0113] <Explanation of Mobile Controller Operation> Next, the main operations of the mobile controller 14 will be explained using the flowcharts in Figures 16 to 25. The processor 51 of the mobile controller 14 is waiting for a request command as ACT101 in Figure 16. When a request command is received via the communication interface 55, the processor 51 identifies the type of the request command as ACT102 to ACT111 and performs information processing according to that type.

[0114] <<Explanation of actions taken when a check-in request command is received>> If the request command is a check-in request command issued from information terminal 2, processor 51 proceeds from ACT102 to ACT121 in Figure 17. Processor 51 detects the user ID from the check-in request command as ACT121. Processor 51 creates a customer transaction file 521 identified by that user ID as ACT122. This transaction file 521 stores the user ID detected in ACT121.

[0115] Processor 51 checks whether the check-in request command, as ACT123, was issued from information terminal 2 linked to the member ID. If the check-in request command includes the member ID, processor 51 recognizes that it was issued from information terminal 2 linked to the member ID. If the check-in request command does not include the member ID, processor 51 recognizes that it was issued from information terminal 2 not linked to the member ID.

[0116] When a check-in request command is issued from information terminal 2 linked to a member ID, processor 51 proceeds to ACT124. Processor 51 saves the member ID included in the check-in request command to the transaction file 521 created in the processing of ACT122 as ACT124. It also sets the delivery declaration flag Fc of the transaction file 521 to the default value of "0".

[0117] If the check-in request command is issued from information terminal 2 that is not linked to a member ID, processor 51 skips the processing of ACT124. After completing or skipping the processing of ACT124, processor 51 proceeds to ACT125. As ACT125, processor 51 sends an acceptance response command to information terminal 2 that sent the check-in request command. With this, processor 51 completes the information processing of the procedure shown in the flowchart of Figure 17.

[0118] Upon receiving the permission response command, the information terminal 2 displays the start screen 100 on the touch panel 24 in ACT6 of Figure 12, as described above.

[0119] <<Explanation of actions taken when receiving a delivery declaration request command>> If the request command is a delivery declaration request command issued from information terminal 2, processor 51 proceeds from ACT103 to ACT131 in Figure 18. Processor 51 detects the user ID from the delivery declaration request command as ACT131. Then, processor 51 selects the transaction file 521 in which that user ID is stored as ACT132. Hereafter, the transaction file 521 in which the user ID obtained from the command is stored will be referred to as the target transaction file 521.

[0120] Processor 51 checks the delivery declaration flag Fc stored in the target transaction file 521 as ACT133. If the delivery declaration flag Fc is "0", processor 51 proceeds to ACT134. Processor 51 changes the delivery declaration flag Fc to "1" as ACT134. If the delivery declaration flag Fc is "1", processor 51 proceeds to ACT135. Processor 51 changes the delivery declaration flag Fc to "0" as ACT135.

[0121] After completing the processing of ACT134 or ACT135, the processor 51 proceeds to ACT136. As ACT136, the processor 51 sends an acceptance response command to the information terminal 2 that sent the delivery declaration request command. With this, the processor 51 completes the information processing of the procedure shown in the flowchart of Figure 18.

[0122] Upon receiving the permission response command, the information terminal 2 displays the registration screen 110 on the touch panel 24 in ACT11 of Figure 12, as described above.

[0123] <<Explanation of operation when receiving a product registration request command>> If the request command is a product registration request command issued from information terminal 2, processor 51 proceeds from ACT104 to ACT141 in Figure 19. Processor 51 detects the user ID from the product registration request command as ACT141. Then, as ACT142, processor 51 selects the transaction file 521 in which that user ID is stored, i.e., the target transaction file 521.

[0124] Processor 51 detects the product code from the product registration request command as ACT143. Then, as ACT144, Processor 51 accesses the store server 13 and retrieves the product data described in the product record 311 containing that product code from the product database 31. As ACT145, Processor 51 saves product sales data, including the product code, product name, price, number of units sold, sales amount, delivery target flag Fa, and packaging target flag Fb, etc., to the target transaction file 521 based on that product data. At this time, Processor 51 also updates the total data in the target transaction file 521.

[0125] Processor 51 checks the delivery declaration flag Fc stored in the target transaction file 521 as ACT146. If the delivery declaration flag Fc is "1", meaning a request for delivery of all items is specified, Processor 51 proceeds to ACT147. Processor 51 checks the delivery target flag Fa of the product data obtained in ACT144 as ACT147. If the delivery target flag Fa is "1", meaning a product subject to delivery service has been registered, Processor 51 proceeds to ACT148. Processor 51 sets the service status of the service data stored in association with the product sales data saved in the transaction file 521 in ACT145 to "10". Processor 51 also sets the delivery code of the same service data to "100" and the packaging code to "000".

[0126] In contrast, if the delivery declaration flag Fc in ACT146 is "0", meaning that a request for delivery of all items has not been specified, or if the delivery target flag Fa in ACT147 is "0", meaning that a request for delivery of all items has been specified but items that are not eligible for delivery service have been registered, the processor 51 proceeds to ACT149. In ACT149, the processor 51 sets the service status of the service data stored in association with the product sales data saved in the transaction file 521 in ACT145 to "00". The processor 51 also sets both the delivery code and packaging code of the same service data to "000".

[0127] After completing the processing of ACT148 or ACT149, the processor 51 proceeds to ACT150. As ACT150, the processor 51 sends an acceptance response command to the information terminal 2 that sent the product registration request command. The acceptance response command contains the data of the target transaction file 521. With this, the processor 51 completes the information processing of the procedure shown in the flowchart of Figure 19.

[0128] Upon receiving the authorization response command, the information terminal 2 updates the data in the details area 111 and the total area 112 of the registration screen 110 in ACT 16 of Figure 13, as described above. At this time, if the delivery code of the service data is "100", that is, if a product subject to the delivery service is registered while a full delivery request is specified, the delivery service mark 115 in the details line of that product lights up.

[0129] <<Explanation of actions when receiving a delivery setting request command or a delivery deletion request command>> If the request command is a delivery setting request command issued from information terminal 2, processor 51 proceeds from ACT105 to ACT161 in Figure 20. Similarly, if the request command is a delivery deletion request command issued from information terminal 2, processor 51 proceeds from ACT106 to ACT161 in Figure 20. Processor 51 detects the user ID from the delivery setting request command or delivery deletion request command as ACT161. Then, as ACT162, processor 51 selects the transaction file 521 in which that user ID is stored, i.e., the target transaction file 521.

[0130] Processor 51 detects the product code from the delivery setting request command or delivery deletion request command as ACT163. Processor 51 then checks the service status of the service data stored in the target transaction file 521, which is associated with the product sales data containing that product code, as ACT164.

[0131] If the tens digit of the service status is "0", that is, if a delivery setting request command has been received, processor 51 proceeds from ACT164 to ACT165. Processor 51 checks the delivery target flag Fa of the product sales data containing the product code as ACT165. If the delivery target flag Fa is "1", processor 51 proceeds to ACT166. Processor 51 sets the tens digit of the service status to "1" as ACT166. Processor 51 also sets the delivery code of the service data to "100".

[0132] In ACT164, if the tens digit of the service status is "1", i.e., if a delivery cancellation request command has been received, processor 51 proceeds to ACT167. Processor 51 sets the tens digit of the service status to "0" in ACT167. Processor 51 also sets the delivery code of the service data to "000".

[0133] After completing the processing of ACT166 or ACT167, the processor 51 proceeds to ACT168. As ACT168, the processor 51 sends an acceptance response command to the information terminal 2 that sent the delivery setting request command or the delivery deletion request command. With this, the processor 51 completes the information processing of the procedure shown in the flowchart of Figure 20.

[0134] If the delivery target flag Fa is "0" in ACT165, the processor 51 proceeds to ACT169. As ACT169, the processor 51 sends a negative response command to the information terminal 2 that sent the delivery setting request command or the delivery deletion request command. With this, the processor 51 completes the information processing of the procedure shown in the flowchart of Figure 20.

[0135] Upon receiving the acceptance response command, the information terminal 2, as described above, clears the service screen 120 in ACT35 of Figure 14. Then, in ACT16 of Figure 13, the data in the details area 111 and the total area 112 of the registration screen 110 is updated based on the data in the transaction file 521. At this time, the delivery service mark 115 lights up in the details line of registered products whose delivery code in the service data is "100," that is, products for which the customer has requested delivery service by entering a delivery key on the service screen 120. Conversely, the delivery service mark 115 lights up in the details line of registered products whose delivery code in the service data is "000," that is, products for which the customer has canceled delivery service by entering a service key 114 on the registration screen 110.

[0136] Upon receiving a negative response command, the information terminal 2 displays a message on the touch panel 24 indicating that the product for which delivery service was specified is not eligible for that service, as described above. When a confirmation operation is performed in response to this message, the service screen 120 is cleared, and the touch panel 24 returns to the registration screen 110, which was displayed before the service key was entered.

[0137] <<Explanation of operation when receiving a packaging setting request command or a packaging deletion request command>> If the request command is a packaging setting request command issued from information terminal 2, processor 51 proceeds from ACT107 to ACT171 in Figure 21. Similarly, if the request command is a packaging deletion request command issued from information terminal 2, processor 51 proceeds from ACT108 to ACT171 in Figure 21. Processor 51 detects the user ID from the packaging setting request command or packaging deletion request command as ACT171. Then, as ACT172, processor 51 selects the transaction file 521 in which that user ID is stored, i.e., the target transaction file 521.

[0138] Processor 51 detects the product code from the packaging setting request command or packaging deletion request command as ACT173. Processor 51 then checks the service status of the service data stored in the target transaction file 521, which is associated with the product sales data containing that product code, as ACT174.

[0139] If the units digit of the service status is "0", that is, if a packaging setting request command has been received, the processor 51 proceeds to ACT175. As ACT175, the processor 51 checks the packaging target flag Fb of the product sales data that includes the product code. If the packaging target flag Fb is "1", the processor 51 proceeds to ACT176. As ACT176, the processor 51 sets the units digit of the service status to "1". The processor 51 also sets the packaging code of the service data to "200".

[0140] Processor 51 examines the packaging method data included in the packaging setting request command as ACT177. If the packaging method data indicates gift packaging, Processor 51 changes the packaging code in the service data from "200" to "201" as ACT178. Processor 51 also adds the service fee, i.e., the box cost, set in service record 3314 with packaging code "201", to the service fee and the total amount in the target transaction file 521 as ACT179.

[0141] In ACT177, if the data for the packaging method indicates simple packaging, the processor 51 skips processing in ACT178 and ACT179. After completing or skipping processing in ACT178 and ACT179, the processor 51 proceeds to ACT184. The processing in ACT184 will be described later.

[0142] In ACT174, if the units digit of the service status is "1", i.e., if a packaging cancellation request command has been received, processor 51 proceeds to ACT180. Processor 51 retrieves the packaging code of the service data as ACT180. Processor 51 checks whether the packaging code is "201" as ACT181. If the packaging code is "201", processor 51 subtracts the service fee set in service record 3314 with packaging code "201", i.e., the box cost, from the service fee and the total data amount in the target transaction file 521 as ACT182. If the packaging code is not "201", processor 51 skips processing in ACT182. After completing or skipping processing in ACT182, processor 51 proceeds to ACT183. Processor 51 sets the units digit of the service status to "0" as ACT183. Processor 51 also sets the packaging code of the service data to "000". Processor 51 then proceeds to ACT184.

[0143] The processor 51 sends an acknowledgment response command as ACT184 to the information terminal 2 that sent the packaging setting request command or the packaging deletion request command. With this, the processor 51 completes the information processing for the procedure shown in the flowchart of Figure 21.

[0144] If the packaging target flag Fb is "0" in ACT175, the processor 51 proceeds to ACT185. As ACT185, the processor 51 sends a negative response command to the information terminal 2 that sent the packaging setting request command or the packaging deletion request command. With this, the processor 51 completes the information processing of the procedure shown in the flowchart of Figure 21.

[0145] Upon receiving the acceptance response command, the information terminal 2, as described above, clears the service screen 120 in ACT35 of Figure 14. Then, in ACT16 of Figure 13, the data in the details area 111 and the total area 112 of the registration screen 110 is updated based on the data in the transaction file 521. At this time, the packaging service mark 116 lights up in the details line of registered products whose delivery code in the service data is "200" or "201," that is, products for which the customer has requested packaging services by entering a packaging key on the service screen 120. Conversely, the packaging service mark 116 turns off in the details line of registered products whose packaging code in the service data is "000," that is, products for which the customer has canceled the packaging service by entering a service key 114 on the registration screen 110.

[0146] Upon receiving a negative response command, the information terminal 2 displays a message on the touch panel 24 indicating that the product for which packaging service was specified is not eligible for that service, as described above. When a confirmation operation is performed in response to this message, the service screen 120 is cleared, and the touch panel 24 returns to the registration screen 110, which was displayed before the service key was entered.

[0147] <<Explanation of operation when receiving a delivery destination request command>> If the request command is a delivery destination request command issued from information terminal 2, processor 51 proceeds from ACT109 to ACT191 in Figure 22. Processor 51 detects the user ID from the delivery destination request command as ACT191. Then, as ACT192, processor 51 selects the transaction file 521 in which that user ID is stored, i.e., the target transaction file 521.

[0148] Processor 51 detects the member ID from the delivery destination request command as ACT193. Then, as ACT194, processor 51 accesses the store server 13 and retrieves the member record 321 of the member identified by that member code from the member database 32.

[0149] Processor 51 checks, as ACT195, whether one or more shipping addresses are set for the member record 321. If shipping addresses are set, processor 51 creates a shipping address list, as ACT196, listing the one or more shipping addresses. If no shipping addresses are set, processor 51 skips processing ACT196.

[0150] Once the processing of ACT196 is complete or skipped, the processor 51 proceeds to ACT197. As ACT197, the processor 51 sends an acceptance response command to the information terminal 2 that sent the delivery destination request command. The acceptance response command includes the home address as delivery destination data. If a delivery list has been created, this delivery destination list is also included as delivery destination data. With this, the processor 51 completes the information processing of the procedure shown in the flowchart of Figure 21.

[0151] Upon receiving the permission response command, as described above, the delivery destination specification screen 130 is displayed on the touch panel 24 in ACT45 of Figure 15. If the delivery destination data includes a delivery destination list, the delivery destination list is displayed when the "Other" key is pressed on the delivery destination specification screen 130.

[0152] <<Explanation of actions taken when a payment request command is received>> If the request command is a payment request command issued from information terminal 2, processor 51 proceeds from ACT110 to ACT201 in Figure 23. Processor 51 detects the user ID from the payment request command as ACT201. Then, as ACT202, processor 51 selects the transaction file 521 in which the user ID is stored, i.e., the target transaction file 521.

[0153] Processor 51 checks for a request for delivery service as ACT203. If the payment request command includes information indicating the delivery address, processor 51 recognizes that a request for delivery service has been made. If the payment request command does not include information indicating the delivery address, processor 51 recognizes that there is no request for delivery service.

[0154] If there is a request for delivery service, processor 51 proceeds to ACT204. Processor 51 saves the information indicating the delivery destination to the target transaction file 521 as ACT204. Processor 51 also adds the service fee set in service record 3311 for delivery code "100" to the service fee and the total amount in the target transaction file 521 as ACT205.

[0155] Processor 51, as ACT206, checks whether the delivery address is the home address. If the information indicating the delivery address is not the home address, Processor 51 proceeds to ACT207. As ACT207, Processor 51 changes the delivery code of the service data with a delivery code of "100" stored in the target transaction file 521 in association with the product sales data to "101". Also, as ACT208, Processor 51 adds the service fee, i.e., shipping fee, set for service record 3312 with delivery code "101" to the service fee and the total amount in the target transaction file 521, respectively.

[0156] If the information indicating the delivery address in ACT206 indicates the home address, the processor 51 skips the processing of ACT207 and ACT208. After completing or skipping the processing of ACT207 and ACT208, the processor 51 proceeds to ACT209. The processor 51 generates an accounting code as ACT209. The accounting code is data for barcoding the user ID detected in the processing of ACT201. The processor 51 sends an acceptance response command as ACT210 to the information terminal 2 that sent the payment request command. The acceptance response command includes the accounting code.

[0157] On the other hand, if there is no request for delivery service in ACT203, the processor 51 proceeds to ACT209. The processor 51 generates an accounting code as ACT209 and sends an acceptance response command as ACT210 to the information terminal 2 that sent the payment request command. With this, the processor 51 completes the information processing of the procedure shown in the flowchart of Figure 23.

[0158] Upon receiving the authorization response command, the information terminal 2 displays an accounting barcode, which is the accounting code represented in barcode form, on the touch panel 24 in ACT49 of Figure 15, as described above. After the customer confirms the accounting barcode, they move to the checkout counter. The customer then scans the accounting barcode using the scanner 47 of an available payment terminal 11.

[0159] <<Explanation of operation when receiving a transaction data request command>> When the barcode of the accounting code displayed on the touch panel 24 of the information terminal 2 is scanned by the scanner 47 of the payment terminal 11, a transaction data request command is sent from the payment terminal 11 to the mobile controller 14. The transaction data request command includes the user ID obtained from the accounting code.

[0160] If the request command is a transaction data request command, the processor 51 proceeds from ACT111 to ACT211 in Figure 24. The processor 51 detects the user ID from the transaction data request command as ACT211. Then, the processor 51 selects the transaction file 521 in which the user ID is stored, i.e., the target transaction file 521, as ACT212.

[0161] Processor 51 retrieves transaction data from the target transaction file 521 as ACT213. The transaction data includes product sales data and related service data, as well as service charges and total data. If information indicating the delivery address is stored in the target transaction file 521, that information is also included in the transaction data. Processor 51 outputs the transaction data as ACT214 to the settlement terminal 11, the source of the transaction data request command. Processor 51 also sends an accounting start command as ACT215, with the user ID detected in the processing of ACT211 as the destination. With this, Processor 51 completes the information processing procedure shown in the flowchart of Figure 24.

[0162] The payment start command is received by information terminal 2, which stores the destination user ID in user ID area 232. Upon receiving the payment start command, information terminal 2 erases the barcode of the payment code that was displayed on the touch panel 24 in ACT51 of Figure 15.

[0163] Furthermore, if processor 51 receives a command other than the request command described above, it will execute processing corresponding to that command as ACT112.

[0164] <Description of Mobile Controller Functions> The processor 51 of the mobile controller 14, operating in this manner, performs the processing shown in Figure 19, ACT141 to ACT145, in response to a product registration request command from the information terminal 2, thereby realizing the function of a registration means 511.

[0165] The processor 51 functions as a receiving means 512 by executing the processes shown in Figure 20, ACT161 to ACT165, in response to a delivery setting request command from the information terminal 2. The processor 51 also functions as a receiving means 512 by executing the processes shown in Figure 21, ACT171 to ACT175, in response to a packaging setting request command from the information terminal 2.

[0166] The processor 51 realizes its function as an association means 513 by executing the process of ACT166 in Figure 20. The processor 51 also realizes its function as an association means 513 by executing the process of ACT179 in Figure 21.

[0167] The processor 51 performs the processing shown in Figure 24, ACT211 to ACT214, in response to transaction data request commands from the payment terminal 11, thereby realizing its function as an output means 514.

[0168] The processor 51 performs the processing of ACT179 in Figure 21 and the processing of ACT205 and ACT208 in Figure 23, thereby realizing the function of the summing means 515.

[0169] The processor 51 performs the processing of ACT204 in Figure 23 in response to a payment request command from the information terminal 2, thereby realizing its function as a delivery destination determination means 516.

[0170] The processor 51 performs the processing shown in Figure 21, ACT176 to ACT178, in response to a packaging setting request command from the information terminal 2, thereby realizing its function as a packaging method determination means 517.

[0171] <Explanation of payment terminal operation> Figure 25 is a flowchart showing the main information processing steps performed by the processor 41 of the payment terminal 11. In the default state, the touch panel 46 of the payment terminal 11 displays a guidance screen. The guidance screen instructs the customer to scan the barcode of the accounting code displayed on the touch panel 46 of the information terminal 2 with the scanner 47. The processor 41, as ACT301, waits for the barcode of the accounting code to be scanned by the scanner 47.

[0172] When a customer sees a barcode of the accounting code displayed on the touch panel 24, they scan that barcode with the scanner 47 of the payment terminal 11. Once the barcode of the accounting code is scanned by the scanner 47, the processor 41 detects the user ID from the scanned barcode as ACT302. The processor 41 then sends a transaction data request command to the mobile controller 14 as ACT303. The transaction data request command is sent to the mobile controller 14 via the communication network 16. The transaction data request command includes the user ID detected in the processing of ACT302.

[0173] The processor 71 that sent the transaction data request command waits for transaction data as ACT304. The mobile controller 14 that received the transaction data request command retrieves the transaction data from the transaction file that stores the user ID included in the transaction data request command, as explained with reference to Figure 24. The mobile controller 14 then sends the transaction data to the settlement terminal 11 that sent the transaction data request command.

[0174] Upon receiving transaction data, processor 41 stores the transaction data in transaction memory as ACT305. Transaction memory is part of the volatile memory area of ​​main memory 42. Processor 41 retrieves the first product sales data from transaction memory as ACT306. Processor 41 then checks the service status of the service data associated with that product sales data as ACT307. If the tens digit of the service status is "1", that is, if a delivery service is specified for the product in the product sales data associated with that service data, processor 41 proceeds to ACT308. Processor 41 stores the product sales data in delivery memory as ACT308. Delivery memory is part of the volatile memory area of ​​main memory 42. If the tens digit of the service status is "0", processor 41 skips processing ACT308.

[0175] If the processor 41 finishes processing ACT308 or skips it, it checks as ACT309 whether the units digit of the service status of the service data is "1". If the units digit of the service status is "1", that is, if a packaging service was specified for the product in the product sales data associated with the service data, the processor 41 proceeds to ACT310. The processor 41 stores the product sales data in the packaging memory as ACT310. The packaging memory is part of the volatile memory area of ​​the main memory 42. If the units digit of the service status is "0", the processor 41 skips processing ACT310.

[0176] If the processing of ACT310 is completed or skipped, the processor 41 checks, as ACT311, whether the processing of ACT307 through ACT310 described above has been performed on all product sales data included in the transaction data. If there is product sales data on which the processing of ACT307 through ACT310 has not been performed, the processor 41 returns to ACT306. The processor 41 then retrieves the next product sales data from the transaction data and performs the processing of ACT307 through ACT310.

[0177] Once processor 41 has finished processing ACT307 through ACT310 for all product sales data included in the transaction data, it proceeds to ACT312. Processor 41 then performs settlement processing for the total amount included in the transaction data as ACT312. The settlement processing can be any of the aforementioned cash settlement processing, credit card settlement processing, electronic money settlement processing, or code settlement processing. It may also be any other settlement processing.

[0178] Once the settlement process is complete, the processor 41 controls the issuance of the transaction receipt 201 (see Figure 32) as ACT313. That is, the processor 41 creates print data for the transaction receipt 201 based on the transaction data stored in the transaction memory and outputs this print data to the printer 48.

[0179] Next, the processor 41 checks, as ACT314, whether or not product sales data is stored in the delivery memory. If product sales data is stored in the delivery memory, the processor 41 proceeds to ACT315. As ACT315, the processor 41 controls the issuance of the delivery receipt 202 (see Figure 32). That is, the processor 41 creates print data for the delivery receipt 202 based on the product sales data stored in the delivery memory and outputs this print data to the printer 48. If product sales data is not stored in the delivery memory, the processor 41 skips the processing of ACT315.

[0180] If the processing of ACT315 is completed or skipped, the processor 41 checks as ACT316 whether product sales data is stored in the packaging memory. If product sales data is stored in the packaging memory, the processor 41 proceeds to ACT317. As ACT317, the processor 41 controls the issuance of the packaging receipt 203 (see Figure 32). That is, the processor 41 creates print data for the packaging receipt 203 based on the product sales data stored in the packaging memory and outputs this print data to the printer 48. If product sales data is not stored in the packaging memory, the processor 41 skips the processing of ACT317.

[0181] Once the processing of ACT317 is completed or skipped, the processor 41 terminates the information processing of the procedure shown in the flowchart of Figure 25.

[0182] Figure 32 is a schematic diagram showing an example of the printing of a transaction receipt 201, a delivery receipt 202, and a packaging receipt 203. The delivery receipt 202 prints the product name and quantity of the items for which delivery service was requested. The delivery address is also printed on the delivery receipt 202. The packaging receipt 203 prints the product name and quantity of the items for which packaging service was requested. The packaging method is also printed on the packaging receipt 203. On the other hand, in the transaction receipt 201, "Delivery Request" is printed for items for which delivery service was requested. Similarly, "Packaging Request" is printed for items for which packaging service was requested. The total amount is printed separately as a subtotal, which is the total amount of the registered items, and a service fee. Thus, the payment terminal 11 that issues the delivery receipt 202 and the packaging receipt 203 functions as a visualization means for visualizing the products associated with the service, based on the data output from the mobile controller 14, which is an example of a product registration device.

[0183] [Effects and benefits of the product registration system] In the sales area, the touch panel 24 of the information terminal 2, which customers use to register the products they purchase themselves, displays the registration screen 110. The registration screen 110 displays a service key 114 for each registered product.

[0184] If a customer has registered items for which they wish to request delivery service, they enter the service key 114 corresponding to that item. The touch panel 24 then switches to the service screen 120, where the customer enters the delivery key. After these operations are completed, the tens digit of the service status in the service data associated with the product sales data of the item for which the service was requested, stored in the transaction file 521, becomes "1". Additionally, the delivery code in the same service data becomes "100".

[0185] When a customer finishes shopping in the store and enters a payment key on the registration screen 110, the delivery address selection screen 130 is displayed on the touch panel 24. If the delivery address is their home, the customer enters the home key. If the delivery address is other than their home, the customer enters the other key. After entering the other key, a list of delivery addresses previously specified by the customer is displayed, and the customer selects the desired delivery address from the list. After performing these operations, a payment barcode is displayed on the touch panel 24, and the customer scans the payment barcode with the scanner 47 of an available payment terminal 11 and then performs the payment operation on the payment terminal 11. The payment includes the service fee for the delivery service. If the delivery address is other than the home, it also includes shipping costs. After performing these operations, the payment terminal 11 issues a transaction receipt 201 and a delivery receipt 202. The delivery receipt 202 has information about the products the customer requested delivery service for and information indicating the delivery address printed on it.

[0186] The customer then goes to the service counter and presents the delivery receipt 202 along with the items they wish to have delivered to the staff. The staff then proceeds with the delivery of the items to the delivery address printed on the delivery receipt 202. Because the delivery receipt 202 is already in place, the staff does not need to record delivery information in a ledger or input it into a dedicated terminal; they only need to receive the items and delivery receipt 202 from the customer. Furthermore, since the service fee or shipping fee has already been paid, there is no need to collect it from the customer. Consequently, the amount of work required for staff to interact with customers is simplified, and the time spent interacting with customers is shortened, thus improving the efficiency of delivery service reception operations at the service counter.

[0187] Incidentally, the delivery receipt 202 has information printed on it about the items the customer has requested to be delivered. Therefore, the store staff will implement a system where they gather the items to be delivered according to the delivery receipt 202. By doing so, customers using the delivery service will no longer need to carry the items from the sales floor to the service counter. Generally, delivery services are provided to reduce the burden on elderly people to carry goods home. Therefore, by implementing the above system, elderly people will no longer need to carry the items to the service counter, which is expected to increase the number of people using the delivery service and boost store sales.

[0188] On the other hand, customers who have registered items for which they wish to request packaging services will enter the service key 114 corresponding to the item for which they wish to have the service provided. The touch panel 24 will then switch to the service screen 120, where the customer will enter the packaging key. Furthermore, customers who wish for simple packaging will enter the simple packaging key, and customers who wish for gift packaging will enter the gift packaging key. After performing these operations, the last digit of the service status in the service data associated with the product sales data of the item for which the service was requested, stored in the transaction file 521, will become "1". In addition, the delivery code of the same service data will become "200" or "201".

[0189] When a customer finishes shopping in the store and enters a payment key on the registration screen 110, a payment barcode is displayed on the touch panel 24. The customer then scans the payment barcode with the scanner 47 on an available payment terminal 11 and then makes a payment to the payment terminal 11. The payment includes the cost of the box if gift wrapping is selected as the packaging method. After these operations are completed, the payment terminal 11 issues a transaction receipt 201 and a packaging receipt 203. The packaging receipt 203 has information printed on it about the product for which the customer requested packaging service and information indicating the packaging method.

[0190] The customer then goes to the service counter and presents the item to be wrapped along with the wrapping receipt 203 to the staff member. The staff member wraps the item according to the wrapping method printed on the wrapping receipt 203 and returns it to the customer. At this time, because the wrapping receipt 203 exists, the staff member does not need to record information about the wrapping in a ledger or enter it into a dedicated terminal, and only needs to receive the wrapping receipt 203. Also, since the box fee has already been paid, there is no need to collect it from the customer. Therefore, the amount of work required for staff members to interact with customers is simplified and the interaction time is shortened, thus improving the efficiency of wrapping service reception operations at the service counter.

[0191] Incidentally, the transaction receipt 201 received by the customer will have "Delivery Requested" printed on it for items for which delivery service was requested, and "Packaging Requested" printed on it for items for which packaging service was requested. In addition, a service fee will be printed separately from the subtotal, which is the price of the registered items. Therefore, the customer can easily identify the items for which delivery service or packaging service was requested from the transaction receipt 201. The customer can also find out the cost incurred for those services from the transaction receipt 201.

[0192] Furthermore, on the registration screen 110, a delivery service mark 115 lights up for items for which delivery service has been requested, and a packaging service mark 116 lights up for items for which packaging service has been requested. Therefore, customers can easily identify items for which delivery service or packaging service has been requested from the information on the registration screen 110.

[0193] Here, if a customer wants to cancel a delivery service request, for example, they enter the service key 114 corresponding to that product. Similarly, if they want to cancel a packaging service request, they enter the service key 114 corresponding to that product. As a result of these operations, the tens or units digit of the service status in the service data associated with that product becomes "0". Also, the delivery code or packaging code in the same service data becomes "000". In this way, customers can easily cancel a requested service simply by entering the service key 114.

[0194] Furthermore, a delivery request key is provided on the start screen 100, which is displayed on the touch panel 24 of the information terminal 2 before the customer begins shopping. Customers who wish to request delivery service for all items they purchase enter the delivery request key. In this case, for the items registered by the customer that are eligible for delivery service, the tens digit of the service status in the service data becomes "1", and the delivery code becomes "100". Therefore, the customer is no longer required to select each item they wish to have delivered on the registration screen 110 and enter the service key 114 one by one. This effect is very convenient for elderly people who wish to use the delivery service for all their items, and an increase in the number of delivery service users can be expected.

[0195] [Second Embodiment] The second embodiment illustrates the product registration system 6 shown in Figure 33 as a product registration system that can improve the efficiency of operations at the service counter. This product registration system 6 is a system that is installed in a store where customers use a self-service POS terminal 61 to register the products they purchase themselves. As with the first embodiment, delivery service and packaging service are given as examples of services that customers can use at the service counter.

[0196] [Description of the product registration system] Figure 33 is a block diagram showing the schematic configuration of the product registration system 6. The product registration system 6 includes a self-service POS terminal 61, a POS terminal 62, an attendant terminal 63, and a store server 64. The product registration system 6 also includes a communication network 65 such as a LAN, and the self-service POS terminal 61, POS terminal 62, attendant terminal 63, and store server 64 are connected to this communication network 16 to construct the product registration system 6. The communication network 65 may be wired or wireless. The communication network 65 may also use both wired and wireless connections.

[0197] Self-service POS terminal 61 is a device that allows customers to register items and make payments themselves. POS terminal 62 is a device that allows store employees to register items and make payments. Self-service POS terminals 61 and POS terminals 62 are installed in a separate checkout area from the sales floor where the products are displayed. There is no particular limit to the number of self-service POS terminals 61 and POS terminals 62 that can be installed. Self-service POS terminal 61 is an example of a product registration device.

[0198] The attendant terminal 63 is a device that has the function of displaying the monitoring image of the self-service POS terminal 61 on a display device. The attendant terminal 63 is installed near the exit of the checkout area. An employee referred to as an attendant is stationed at the location where the attendant terminal 63 is installed. The monitoring image changes according to the operation input to the self-service POS terminal 61. The attendant monitors customer errors, fraudulent operations, etc., from the information in the monitoring image.

[0199] The store server 64 is a computer that supports all aspects of store operations. To support these operations, the store server 64 manages various databases, including the product database 31, the member database 32, and the service database 33. The product database 31, the member database 32, and the service database 33 are the same as in the first embodiment, so their explanation is omitted here.

[0200] [Description of Self-Service POS Terminal Configuration] Figure 34 is a block diagram showing the main circuit configuration of the self-service POS terminal 61. The self-service POS terminal 61 includes a processor 71, main memory 72, auxiliary storage device 73, clock 74, communication interface 75, touch panel 76, scanner 77, printer 78, reader / writer 79, change dispenser interface 80, scale interface 81, and system transmission path 82, etc. The system transmission path 82 includes an address bus, data bus, control signal lines, etc. The system transmission path 82 connects the processor 71 and the other parts directly or via signal input / output circuits, and transmits data signals exchanged between them.

[0201] The self-service POS terminal 61 is configured as a computer by connecting the processor 71, main memory 72, auxiliary storage device 73, clock 74, and communication interface 75 via a system transmission path 82. The self-service POS terminal 61 then connects device interfaces or devices such as a touch panel 76, scanner 77, printer 78, reader / writer 79, change dispenser interface 80, and scale interface 81 to its computer via the system transmission path 82.

[0202] The processor 71, main memory 72, auxiliary storage device 73, clock 74, communication interface 75, touch panel 76, scanner 77, printer 78, reader / writer 79, and change dispenser interface 80 of the self-service POS terminal 61 have the same functions as the processor 41, main memory 42, auxiliary storage device 43, clock 44, communication interface 45, touch panel 46, scanner 47, printer 48, reader / writer 49, and change dispenser interface 410 of the payment terminal 11 in the first embodiment. Therefore, a detailed explanation is omitted here.

[0203] The scale interface 81 forms an interface with a weighing device (not shown). The customer places the items they have registered one by one on the bagging table at the self-service POS terminal 61. A weighing device is provided on the bagging table and measures the weight of the items placed on the bagging table. The unit weight of the item is pre-set in the item record 311, and the processor 71 of the self-service POS terminal 61 compares the unit weight of the registered item with the weight of the item placed on the bagging table to determine if the registered item and the bagged item match. If a match is found, the processor 71 registers the data of the registered item.

[0204] A self-service POS terminal 61 with this configuration can be used as is with existing self-service POS terminals. However, in this embodiment, the self-service POS terminal 61 uses a portion of the volatile memory area of ​​the main memory 72 as the storage area for the transaction file 721. The data items stored in the transaction file 721 are the data items of the transaction file 521 described using Figure 10, excluding the user ID and the delivery declaration flag Fc.

[0205] Furthermore, the self-service POS terminal 61 implements a control program such that the processor 71 functions as a registration means 711, a receiving means 712, an association means 713, an output means 714, a summing means 715, a delivery destination determination means 716, and a packaging method determination means 717. The control program is a type of application program stored in the main memory 72 or auxiliary storage device 73. The method of installing the control program in the main memory 72 or auxiliary storage device 73 is not particularly limited. The control program can be recorded on a removable recording medium, or the control program can be distributed via communication through the communication network 65 and installed in the main memory 72 or auxiliary storage device 73. The recording medium can be of any form as long as it can store a program and is readable by the device, such as a CD-ROM or memory card.

[0206] The registration means 711 is a function for registering the products to be purchased. Based on the data from the scanner 77 or the touch panel 76, the registration means 711 registers product sales data related to the products to be purchased in the transaction file 721.

[0207] The reception means 712 is a function that accepts services to be applied to goods after payment. The reception means 712 accepts multiple types of services via the touch panel 76. In this embodiment, the reception means 712 accepts delivery services and packaging services.

[0208] The association means 713 has the function of associating and storing the goods registered by the registration means 711 with the services applicable to those goods. The association means 713 stores the service data, namely the service status and service code, in association with the product sales data registered in the transaction file 721 on the transaction file 721.

[0209] The output means 714 has the function of outputting the goods and services associated by the association means 713. The output means 714 outputs the goods sales data and service data stored in the transaction file 721 to the printer 78.

[0210] The aggregation means 715 has the function of adding the service fee received by the reception means 712 to the price of the goods registered by the registration means 711. In the self-service POS terminal 61, payment processing is performed on the amount obtained by adding the service fee to the price of the goods.

[0211] The delivery destination determination means 716 is a function that determines the delivery destination of the product when the delivery service is accepted by the acceptance means 712. The delivery destination can be the home or a location other than the home, as in the first embodiment.

[0212] The packaging method determination means 717 has the function of determining the packaging method for the product when a packaging service is received by the reception means 712. The packaging methods include simple packaging and gift packaging, as in the first embodiment. Details of each function will be explained in the following operation description.

[0213] [Explanation of Self-POS Terminal Operation] Figures 35 to 38 are flowcharts showing the main information processing steps performed by the processor 71 of the self-service POS terminal 61 according to the control program. Figures 39 to 42 are schematic diagrams showing an example of the main screen display on the touch panel 76 of the self-service POS terminal 61. Figure 32 is a schematic diagram showing an example of a receipt printed from the printer 78 of the self-service POS terminal 61. The main operations of the self-service POS terminal 61 will be explained below using these figures. Note that the operations described below are examples. The operation procedures and content are not particularly limited as long as similar results can be obtained. Also, the screen display and receipt printing layout, text data, etc. are examples and can be changed as appropriate.

[0214] The processor 71 is waiting for an activation operation as ACT401. For example, an initial screen is displayed on the touch panel 76 with soft keys for member key and non-member key, and the processor 71 is waiting for either the member key or non-member key to be entered. A member customer enters their member key before registering the product they wish to purchase, allowing the reader / writer 79 to read the information on their member card. A non-member customer enters their non-member key.

[0215] When a member key or non-member key is entered, the processor 71 recognizes that an activation operation has been performed. The processor 71 proceeds to ACT402. As ACT402, the processor 71 clears the transaction file 402. As ACT403, the processor 71 checks whether the activation operation was an input operation for a member key. If it was an input operation for a member key, the processor 71 proceeds to ACT404. As ACT404, the processor 71 obtains the member ID from the member card information read by the reader / writer 79 and saves it to the transaction file 721. If the activation operation was an input operation for a non-member key, the processor 71 skips the processing of ACT404. After completing or skipping the processing of ACT404, the processor 71 sets the screen of the touch panel 76 to the registration screen 800 (see Figure 39) as ACT405.

[0216] Figure 39 is a schematic diagram showing one example of the registration screen 800. The registration screen 800 includes a details area 801 and a total area 802 for registered products. The details area 801 displays details such as the product name, number of items sold, and sales amount for products registered by operating the scanner 77 or touch panel 76. The total area 802 displays the total number of items and total amount for registered products. Note that at the time of ACT 405, no products have been registered, so no information is displayed in the details area 111 and the total area 112.

[0217] The registration screen 800 also includes soft keys for a payment key 803 and a service key 804. The payment key 803 is entered by the customer when they declare their intention to pay after registering the items they wish to purchase. The service key 804 is entered by the customer when they wish to apply a delivery service or packaging service to the items they wish to purchase. The service key 804 is an example of a batch instruction means that collectively instructs the application of a service to multiple items registered by the registration means 711.

[0218] The processor 71, displaying the registration screen 800, waits for the customer to perform the registration operation for the product they wish to purchase as ACT406. The product registration operation involves scanning the product's barcode with the scanner 77, or selecting a product without a barcode from the list of products displayed on the touch panel 76. Through such a product registration operation, the processor 71 can obtain the product code of the registered product.

[0219] Processor 71, having obtained the product code of a registered product, accesses the store server 13 as ACT407 and retrieves product data from the product database 31, specifically the product record 311 containing that product code. Processor 71, as ACT408, saves product sales data, including the product code, product name, price, number of units sold, sales amount, delivery target flag Fa, and packaging target flag Fb, to the transaction file 721 based on that product data. At this time, processor 51 also updates the total data in the transaction file 721. Processor 71, as ACT409, updates the data in the detail area 801 and the total area 802 of the registration screen 800 based on the data in the transaction file 721.

[0220] Figure 39 illustrates the registration screen 800 after a customer has registered one item each of product AAA (priced at 300 yen), product BBB (priced at 200 yen), and product CCC (priced at 100 yen). The details area 801 displays the product name, unit price, number of items sold, and total sales amount as detailed data for each registered product on a separate line. The total area 802 displays the total number of items and total sales amount as total data.

[0221] The processor 71, having updated the registration screen 800, waits for either a product registration operation to be performed as ACT410, a service key 804 to be entered as ACT411, or a payment key 803 to be entered as ACT412. If a product registration operation is performed while waiting for ACT410 through ACT412, the processor 71 returns to ACT407. The processor 71 then executes the processing of ACT407 through ACT409 in the same manner as described above. The processor 71 then returns to the waiting state for ACT410 through ACT412 once again.

[0222] When the service key 804 is entered while in the standby state of ACT410 to ACT412, the processor 71 proceeds from ACT411 to ACT413. As ACT413, the processor 71 sets the screen of the touch panel 76 as the service screen 810 (see Figure 40).

[0223] Figure 40 is a schematic diagram showing one example of the service screen 810. The service screen 810 includes a delivery key 811, a packaging key 812, and a return key 813. The delivery key 811 is entered when a customer requests a delivery service. The packaging key 812 is entered when a customer requests a packaging service. The return key 813 is entered when a customer cancels a service request.

[0224] The processor 71, displaying the service screen 810, waits for either the delivery key 811 to be entered as ACT414, the packaging key 812 to be entered as ACT415, or the return key 813 to be entered as ACT416. If the return key 813 is entered while waiting for ACT414 through ACT416, the processor 71 returns from ACT416 to ACT409. The processor 71 clears the service screen 810 and returns the touch panel 76 screen to the registration screen 800.

[0225] If a delivery key 811 is entered while in the standby state of ACT414 to ACT416, the processor 71 proceeds from ACT414 to ACT421 in Figure 36. As ACT421, the processor 71 sets the screen of the touch panel 76 to the delivery service target product list screen 820 (see Figure 41).

[0226] Figure 41 is a schematic diagram showing one example of the display of the target product list screen 820. The target product list screen 820 displays a list of product names, unit prices, number of items sold, and sales amounts for products that are eligible for delivery services and whose delivery target flag Fa is "1," among the products for which product sales data has been registered in the transaction file 721. A checkbox 821 is placed for each product. The target product list screen 820 also has two soft keys: a confirmation key 822 and a return key 823. The customer selects the products for which they want to request delivery services by checking the checkbox 821. The checkbox 821 is an example of a selection method for selecting products to which the service will be applied from among multiple products. The confirmation key 822 is entered by the customer to confirm the products selected using the checkbox 821. The return key 823 is entered by the customer to cancel the request for delivery services.

[0227] The processor 71, which displays the target product list screen 820, waits for either the confirmation key 822 (ACT422) or the return key 823 (ACT423) to be input. When the return key 823 is input while waiting for ACT422 or ACT423, the processor 71 returns from ACT423 to ACT409 in Figure 35. The processor 71 clears the target product list screen 820 and returns the touch panel 76 screen to the registration screen 800.

[0228] If the confirmation key 822 is entered while ACT422 and ACT423 are in standby mode, the processor 71 proceeds from ACT422 to ACT424. As ACT424, the processor 71 sets the tens digit of the service status in the service data stored in association with the product sales data of products for which checkbox 821 is checked to "1". The processor 71 also sets the tens digit of the service status in the service data stored in association with the product sales data of products for which checkbox 821 is not checked to "0".

[0229] Processor 71 checks whether there is a request for delivery service as ACT425. If, as a result of processing ACT424, there is at least one product with a service status where the tens digit is "1", processor 71 recognizes that there is a request for delivery service. If there are no products with a service status where the tens digit is "1", processor 71 recognizes that there is no request for delivery service. If there is no request for delivery service, processor 71 returns to ACT409 in Figure 35. Processor 71 clears the target product list screen 820 and returns the touch panel 76 screen to the registration screen 800.

[0230] In ACT425, if there is a request for delivery service, the processor 71 proceeds to ACT426. In ACT426, the processor 71 sets the touch panel 76 screen to the delivery destination specification screen 830 (see Figure 42).

[0231] Figure 42 is a schematic diagram showing one example of the display of the delivery address selection screen 830. The delivery address selection screen 830 has two soft keys: a home key 831 and an other key 832. Customers who specify their home address as the delivery address enter the home key 831. Customers who specify a delivery address other than their home address enter the other key 832.

[0232] The processor 71, which displays the delivery address selection screen 830, waits for the delivery address to be specified as ACT427. If the home key 831 is entered, the processor 71 recognizes that the home address has been specified as the delivery address. If the other key 832 is entered, the processor 71 recognizes that a delivery address other than the home address has been specified. Here, if a delivery address is registered in the member record 321 identified by the member ID of the customer who entered the other key 832, a list of delivery addresses, or the so-called delivery address list, is displayed on the delivery address selection screen 830. The customer then selects the desired delivery address from the delivery address list. Once an address is selected, the processor 71 recognizes that that address has been specified as the delivery address. If the desired delivery address is not in the delivery address list, the customer selects "None". In the case of "None", the processor 71 recognizes that a delivery address other than the home address has been specified.

[0233] If the home address is specified as the delivery destination, processor 71 proceeds to ACT428. Processor 71 sets the delivery code of the service data with a tens digit of "1" in the service status to "100" as ACT428. Processor 71 also saves information indicating the delivery destination, that is, information indicating that the home address was specified as the delivery destination, to transaction file 721 as ACT429. Furthermore, as ACT430, processor 71 adds the service fee set for service record 3311 with delivery code "100" to the service fee and the total amount in transaction file 521, respectively.

[0234] In ACT427, if a delivery address other than the home address is specified, processor 71 proceeds to ACT431. Processor 71 sets the delivery code of the service data with a tens digit of "1" in the service status to "101" as ACT431. Processor 71 also saves information indicating the delivery address, that is, information indicating that a delivery address other than the home address or a specific delivery address has been specified, to transaction file 721 as ACT432. Furthermore, as ACT433, processor 71 adds the service fee set in service record 3311 for delivery code "100" and the shipping fee set in service record 3312 for delivery code "101" to the service fee and total data amount in transaction file 521, respectively.

[0235] After completing the processing of ACT430 or ACT433, the processor 71 returns to ACT409 in Figure 35. The processor 71 clears the delivery destination specification screen 830 and returns the touch panel 76 screen to the registration screen 800.

[0236] If a packaging key 812 is entered while in the standby state of ACT414 to ACT416, the processor 71 proceeds from ACT415 to ACT441 in Figure 37. For ACT441, the processor 71 sets the screen of the touch panel 76 to the product list screen 840 for packaging services (see Figure 43).

[0237] Figure 43 is a schematic diagram showing one example of the display of the target product list screen 840. The target product list screen 840 displays a list of product names, unit prices, sales quantities, and sales amounts for products that are eligible for packaging services and whose packaging target flag Fb is "1," among the products for which product sales data has been registered in the transaction file 721. A first checkbox 841 and a second checkbox 842 are placed for each product. The target product list screen 840 also has two soft keys: a confirmation key 843 and a return key 844. When a customer requests the simple packaging service, they select the product by checking the first checkbox 841. When a customer requests the gift packaging service, they select the product by checking the second checkbox 842. Note that it is not possible to check both the first checkbox 841 and the second checkbox 842. The first checkbox 841 and the second checkbox 842 are examples of selection means for selecting products to which a service should be applied from among multiple products. The confirmation key 843 is entered by the customer to confirm the items selected using the first checkbox 841 or the second checkbox 842. The return key 844 is entered by the customer to cancel the request for packaging services.

[0238] The processor 71, displaying the target product list screen 840, waits for either the confirmation key 843 to be input as ACT442 or the return key 844 to be input as ACT443. When the return key 844 is input while in the waiting state for ACT442 and AT443, the processor 71 returns from ACT443 to ACT409 in Figure 35. The processor 71 clears the target product list screen 840 and returns the touch panel 76 screen to the registration screen 800.

[0239] If the confirmation key 843 is entered while ACT442 and ACT443 are in a waiting state, the processor 71 proceeds from ACT442 to ACT444. As ACT444, the processor 71 sets the units digit of the service status in the service data stored in association with the product sales data of products for which the first checkbox 841 or the second checkbox 842 is checked to "1". The processor 71 also sets the units digit of the service status in the service data stored in association with the product sales data of products for which the first checkbox 841 or the second checkbox 842 is not checked to "0".

[0240] Processor 71 checks whether there is a request for packaging service as ACT445. If, as a result of processing ACT444, there is at least one product with a service status where the last digit is "1", processor 71 recognizes that there is a request for packaging service. If there are no products with a service status where the last digit is "1", processor 71 recognizes that there is no request for packaging service. If there is no request for packaging service, processor 71 returns to ACT409 in Figure 35. Processor 71 clears the target product list screen 840 and returns the touch panel 76 screen to the registration screen 800.

[0241] In ACT445, if a request for packaging services is received, the processor 71 proceeds to ACT446. The processor 71 identifies the packaging method in ACT446. The processor 71 recognizes that for items with the first checkbox 841 checked, the packaging method is simple packaging. The processor 71 recognizes that for items with the second checkbox 842 checked, the packaging method is gift packaging.

[0242] If the packaging method is simple packaging, the processor 71 proceeds to ACT447. As ACT447, the processor 71 sets the packaging code of the service data with a units digit of "1" in the service status to "200".

[0243] In ACT446, if the packaging method is gift packaging, processor 71 proceeds to ACT448. Processor 71 sets the packaging code of the service data with a units digit of "1" in the service status to "201" as ACT448. Processor 71 also adds the box cost set in service record 3314 with packaging code "201" to the service fee and the total amount in transaction file 521, respectively, as ACT449.

[0244] After completing the processing of ACT447 or ACT449, the processor 71 returns to ACT409 in Figure 35. The processor 71 clears the delivery destination specification screen 830 and returns the touch panel 76 screen to the registration screen 800.

[0245] If a payment key 803 is entered while the system is in the waiting state of ACT410 or ACT412, the processor 71 proceeds from ACT412 to ACT451 in Figure 38. The processor 71 searches the transaction file 721 as ACT451. The processor 71 retrieves the first product sales data from the transaction file 721 as ACT452. Then, the processor 71 checks the service status of the service data associated with that product sales data as ACT543. If the tens digit of the service status is "1", that is, if a delivery service is specified for the product in the product sales data associated with that service data, the processor 71 proceeds to ACT454. The processor 71 stores the product sales data in the delivery memory as ACT454. The delivery memory is part of the volatile memory area of ​​the main memory 72. If the tens digit of the service status is "0", the processor 71 skips the processing of ACT454.

[0246] If the processor 71 has finished processing ACT454 or has skipped it, it checks as ACT455 whether the units digit of the service data is "1". If the units digit of the service data is "1", that is, if a packaging service was specified for the product in the product sales data associated with that service data, the processor 71 proceeds to ACT456. The processor 71 stores the product sales data in packaging memory as ACT456. Packaging memory is part of the volatile memory area of ​​main memory 72. If the units digit of the service status is "0", the processor 71 skips processing ACT456.

[0247] If the ACT456 process is completed or skipped, the processor 71 checks whether the processes described above for ACT452 through ACT456 have been performed for all product sales data stored in the transaction file 721 as ACT457. If there is any product sales data for which the processes for ACT452 through ACT456 have not been performed, the processor 71 returns to ACT452. The processor 71 then retrieves the next product sales data from the transaction file 721 and performs the processes for ACT453 through ACT456.

[0248] Once processor 71 has finished processing ACT452 through ACT456 for all product sales data stored in transaction file 721, it proceeds to ACT458. Processor 71 then performs settlement processing for the total amount stored in transaction file 721 as ACT458. The settlement processing can be cash settlement, credit card settlement, electronic money settlement, or code settlement. It may also be any other settlement processing.

[0249] Once the settlement process is complete, the processor 71 controls the issuance of the transaction receipt 201 (see Figure 32) as ACT459. That is, the processor 71 creates the print data for the transaction receipt 201 based on the stored transaction data stored in the transaction file, and outputs this print data to the printer 78.

[0250] Next, the processor 71 checks whether the merchandise sales data is stored in the delivery memory as ACT460. If the merchandise sales data is stored in the delivery memory, the processor 71 proceeds to ACT461. The processor 71 controls the issuance of the delivery receipt 202 (see FIG. 32) as ACT461. That is, the processor 71 creates the print data for the delivery receipt 202 based on the merchandise sales data stored in the delivery memory, and outputs this print data to the printer 78. If the merchandise sales data is not stored in the delivery memory, the processor 71 skips the processing of ACT461.

[0251] When finishing or skipping the processing of ACT461, the processor 71 checks whether the merchandise sales data is stored in the packaging memory as ACT462. If the merchandise sales data is stored in the packaging memory, the processor 71 proceeds to ACT463. The processor 71 controls the issuance of the packaging receipt 203 (see FIG. 32) as ACT463. That is, the processor 71 creates the print data for the packaging receipt 203 based on the merchandise sales data stored in the packaging memory, and outputs this print data to the printer 78. If the merchandise sales data is not stored in the packaging memory, the processor 71 skips the processing of ACT463.

[0252] When finishing or skipping the processing of ACT463, the processor 71 ends the information processing of the procedures shown in the flowcharts of FIGS. 35 to 38.

[0253] <Function Description of Self-POS Terminal> The processor 71 of the self-POS terminal 61 that operates in this way realizes the function as the registration means 711 by executing the processing of ACT406 to ACT410 in FIG. 35.

[0254] The processor 71 realizes the function as the reception means 712 by executing the processes of ACT421 to ACT424 in FIG. 36. Also, the processor 71 realizes the function as the reception means 712 by executing the processes of ACT441 to ACT444 in FIG. 37.

[0255] The processor 71 realizes the function as the association means 513 by executing the processes of ACT428 and ACT431 in FIG. 36. Also, the processor 71 realizes the function as the association means 713 by executing the processes of ACT447 and ACT448 in FIG. 37.

[0256] The processor 71 realizes the function as the output means 714 by executing the processes of ACT460 to ACT463 in FIG. 38.

[0257] The processor 71 realizes the function as the summation means 715 by executing the processes of ACT430, ACT433 in FIG. 36, and ACT449 in FIG. 37.

[0258] The processor 71 realizes the function as the delivery destination determination means 716 by executing the processes of ACT429 and ACT432 in FIG. 36.

[0259] The processor 71 realizes the function as the packaging method determination means 517 by executing the process of ACT446 in FIG. 37.

[0260] [Operational Effects of the Product Registration System] When a customer uses the self-service POS terminal 61 to register the items they wish to purchase, the registration screen 800 is displayed on the touch panel 76 of the self-service POS terminal 61. Customers who wish to use the delivery service then enter the service key 804. The touch panel 76 then transitions from the registration screen 800 to the service screen 810, where the customer enters the delivery key 811. The touch panel 76 then transitions from the service screen 810 to the target product list screen 820, where the customer checks the checkbox 821 corresponding to the items for which they wish to request delivery service and enters the confirmation key 822. The touch panel 76 then transitions from the target product list screen 820 to the delivery address selection screen 830, where the customer selects the desired delivery address. The touch panel 76 then returns from the delivery address selection screen 830 to the registration screen 800, where the customer enters the payment key 803.

[0261] By performing the above operations, the self-service POS terminal 61 issues a delivery receipt 202 along with a transaction receipt 201, similar to the payment terminal 11 in the first embodiment. Therefore, in the product registration system 6 of the second embodiment, the efficiency of delivery service acceptance operations at the service counter can be improved, similar to the first embodiment. Furthermore, by enabling store staff to prepare products for delivery according to the delivery receipt 202, the number of users of the delivery service may increase, and an improvement in store sales can be expected.

[0262] On the other hand, a customer who has registered items for which they wish to request packaging services enters the service key 804 on the registration screen 800, and then enters the packaging key 812 on the service screen 810. The touch panel 76 then transitions from the service screen 810 to the target item list screen 840, where the customer checks either the first checkbox 841 or the second checkbox 842 corresponding to the item for which they wish to request packaging services, and then enters the confirmation key 843. The touch panel 76 then returns from the target item list screen 840 to the registration screen 800, where the customer enters the payment key 803.

[0263] By performing the above operations, the self-service POS terminal 61 issues a packaging receipt 203 along with a transaction receipt 201, similar to the payment terminal 11 in the first embodiment. Therefore, in the product registration system 6 of the second embodiment, the efficiency of packaging service reception operations at the service counter can be improved, similar to the first embodiment.

[0264] [Differentiation] In the above embodiment, delivery service and packaging service were given as examples of services that can be accepted at the service counter. The types of services are not limited to these. For example, services such as warranty extension services, reservations for seasonal products such as New Year's dishes and Christmas cakes can also be configured in the same way as the delivery service or packaging service in the embodiment, thereby improving the efficiency of operations at the service counter.

[0265] In the above embodiment, an example was given of issuing a delivery receipt 202 or a packaging receipt 203 from a payment terminal 11 or a self-service POS terminal 61. For example, a network printer is installed at the service counter and connected to the communication network 16 or 65. The payment terminal 11 or self-service POS terminal 61 then outputs the print data for the delivery receipt 202 or packaging receipt 203 to the network printer. This simplifies the process for customers from having to present the delivery receipt 202 or packaging receipt 203 issued by the payment terminal 11 or self-service POS terminal 61 to the staff at the service counter. In particular, in stores where staff prepare the items to be delivered according to the delivery receipt 202, customers requesting delivery services no longer need to go to the service counter. Alternatively, a display device may be connected instead of a receipt printer so that staff can check the contents of the delivery receipt 202 or packaging receipt 203 on the screen.

[0266] Furthermore, for the delivery receipt 202, information about the products for which delivery service was requested and information indicating the delivery address are printed on the delivery receipt 202 in a barcode or two-dimensional code system. Similarly, for the packaging receipt 203, information about the product name and quantity of the products for which packaging service was requested and information about the packaging method are printed on the packaging receipt 203 in a barcode or two-dimensional code system. By doing so, the staff at the service counter can complete the acceptance of the delivery or packaging service by reading the barcode or two-dimensional code printed on the delivery receipt 202 or packaging receipt 203 with the code reader on the terminal. Therefore, the efficiency of the acceptance process can be further improved.

[0267] In the first embodiment, the service screen 120 may prevent input operations by graying out the delivery key if the delivery target flag Fa of the service request product is "0", i.e., the product is not eligible for delivery services. Similarly, if the packaging target flag Fb of the service request product is "0", i.e., the product is not eligible for packaging services, the packaging key may be grayed out to prevent input operations. By doing so, the mobile controller 14 will not return a negative response, and the mobile controller 14 can omit information processing related to negative responses. As a result, the processing efficiency of the mobile controller 14 can be improved.

[0268] In the first embodiment, an example was given in which a service key 114 is displayed for each detail data displayed in the detail area 111 of the registration screen 110. In another embodiment, instead of the service key 114, the delivery key and packaging key of the service screen 120 are displayed, respectively. When the delivery key is entered, the processor 21 executes ACT26 to ACT28 in Figure 14, and when the packaging key is entered, the processor 21 executes ACT29 to ACT32 in Figure 14. In such embodiments, the delivery key and packaging key become individual instruction means.

[0269] The order in which the transaction receipt 201, delivery receipt 202, and packaging receipt 203 are issued is not limited to the above embodiment. For example, the delivery receipt 202 or packaging receipt 203 may be issued first, followed by the transaction receipt 201. Doing so can prevent customers from forgetting to take the delivery receipt 202 or packaging receipt 203.

[0270] In the second embodiment, a bulk selection key may be added to the target product list screen 820, so that when this bulk selection key is entered, all of the checkboxes 821 corresponding to each product are checked. This improves the user experience when requesting delivery service for all items.

[0271] In the second embodiment, the processor of the POS terminal 62 is configured to have the functions of a registration means 711, a receiving means 712, an association means 713, an output means 714, a summing means 715, a delivery destination determination means 716, and a packaging method determination means 717. Then, in response to a customer's request, a store employee may operate the POS terminal 62 to issue a delivery receipt 202 or a packaging receipt 203. As mentioned above, delivery services are frequently used by the elderly, and many of them are reluctant to use self-service POS terminals 61. For this reason, there is a great advantage to using the POS terminal 62 as an example of a product registration device.

[0272] In the above embodiment, the mobile controller 14 is connected to the communication network 16. In another embodiment, the functions of the mobile controller 14 may be realized by a cloud server on the internet. In this case, the cloud server on the internet is connected to a wide area network and realizes the functions of the mobile controller 14. By realizing the functions of the mobile controller 14 by a cloud server, the functions can be easily expanded.

[0273] In addition, although some embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the gist of the invention. These embodiments and their modifications are included in the scope of the invention and are included in the invention described in the claims and the equivalent scope thereof. The original claims of this application are included below. [C1] <e A registration method for registering the products to be purchased, A means of receiving requests for services to be applied to the aforementioned products after payment, An association means for storing the registered goods and the services applicable to those goods in association with each other, An output means that outputs the product and the service associated by the association means, A product registration device equipped with the following features. [C2] A summing means that adds the service fees received by the reception means to the price of the goods registered by the registration means. The product registration device according to claim 1, further comprising: [C3] The reception means includes an individual instruction means for individually instructing the application of the service to products registered by the registration means, The product registration device according to claim 1 or 2, wherein the association means stores the product to which the application of the service has been instructed by the individual instruction means in association with the service. [C4] The reception means includes a batch instruction means for collectively instructing the application of the service to a plurality of products registered by the registration means, and a selection means for selecting a product to which the service is to be applied from among the plurality of products. The product registration device according to claim 1 or 2, wherein the association means stores the product selected by the selection means in association with the service. [C5] The registration means registers the products to be purchased based on data from a terminal operated by the customer purchasing the products. The reception means receives the service via the terminal, The product registration device according to claim 1, wherein the output means outputs to a payment terminal that performs payment for products registered by the registration means. [C6] The aforementioned reception means accepts multiple types of services, The product registration device according to claim 1, wherein the output means outputs the products to which the service is applied and the service, according to the type of service. [C7] The aforementioned service includes a delivery service for delivering goods purchased by the customer. A delivery destination determination means that determines the delivery destination of the product for which the delivery service has been received by the reception means, The product registration device according to claim 6, further comprising: [C8] The aforementioned service includes a packaging service for packaging the goods purchased by the customer. A packaging method determination means for determining the packaging method of the product for which the packaging service has been received by the reception means, The product registration device according to claim 6, further comprising: [C9] It includes a product registration device that communicates data with a terminal operated by a customer purchasing a product, and a payment terminal that processes payment for the said product, The aforementioned product registration device is A registration method for registering the products to be purchased, A means of receiving requests for services to be applied to the aforementioned products after payment, An association means for storing the registered goods and the services applicable to those goods in association with each other, An output means that outputs the product and the service associated by the association means, It is equipped with, The aforementioned payment terminal is A visualization means that visualizes the products associated with the service based on the data output from the product registration device. A product registration system is provided. [C10] The computer of the product registration device A registration method for registering the products to be purchased. A means of receiving a service to be applied to the aforementioned product after payment, An association means for storing the registered goods and the services applicable to those goods in association, and Output means for outputting the product and the service associated by the association means, A program designed to function as such. [Explanation of Symbols]

[0274] 1,6...Product registration system, 2...Information terminal, 11...Payment terminal, 12,63...Attendant terminal, 13,64...Store server, 14...Mobile controller, 15...Access point, 16,65...Communication network, 31...Product database, 32...Member database, 33...Service database, 100...Start screen, 110,800...Registration screen, 120,810...Service screen, 130, 830...Delivery address selection screen, 201...Transaction receipt, 202...Delivery receipt, 203...Packaging receipt, 511,711...Registration means, 512,712...Acceptance means, 513,713...Association means, 514,714...Output means, 515,715...Aggregation means, 516,716...Delivery address determination means, 517,717...Packaging method determination means, 521,721...Transaction file, 820,840...Target product list screen.

Claims

1. A registration method for registering the products to be purchased, A means of receiving multiple types of services to be applied to the aforementioned product after payment, An association means for storing the registered goods and the services applicable to those goods in association with each other, An output means that outputs the product and the service associated by the association means, A summing means for adding the service fees received by the reception means to the prices of goods registered by the registration means, It is equipped with, The reception means includes means for displaying a screen for selecting the type of service to apply to a plurality of products registered by the registration means, means for selecting the type of service, and means for selecting the product to which the service will be applied with respect to the target product corresponding to the selected type of service included among the plurality of products. The association means is a product registration device that stores the product selected by the selection means in association with the service.

2. The registration means registers the products to be purchased based on data from a terminal operated by the customer purchasing the products. The reception means receives the multiple types of services via the terminal, The product registration device according to claim 1, wherein the output means outputs to a payment terminal that performs payment for products registered by the registration means.

3. The product registration device according to claim 1, wherein the output means outputs the products to which the service is applied and the service, according to the type of service.

4. The aforementioned service includes a delivery service for delivering goods purchased by the customer. A delivery destination determination means that determines the delivery destination of the product for which the delivery service has been received by the reception means, The product registration device according to claim 3, further comprising:

5. The aforementioned service includes a packaging service for packaging the goods purchased by the customer. A packaging method determination means for determining the packaging method of the product for which the packaging service has been received by the reception means, The product registration device according to claim 3, further comprising:

6. It includes a product registration device that communicates data with a terminal operated by a customer purchasing a product, and a payment terminal that processes payment for the said product, The aforementioned product registration device is A registration method for registering the products to be purchased, A means of receiving requests for services to be applied to the aforementioned products after payment, An association means for storing the registered goods and the services applicable to those goods in association with each other, An output means that outputs the product and the service associated by the association means, A summing means for adding the service fees received by the reception means to the prices of goods registered by the registration means, It is equipped with, The reception means includes means for displaying a screen for selecting the type of service to apply to a plurality of products registered by the registration means, means for selecting the type of service, and means for selecting the product to which the service will be applied with respect to the target product corresponding to the selected type of service included among the plurality of products. The association means stores the product selected by the selection means in association with the service, The aforementioned payment terminal is A visualization means that visualizes the products associated with the service based on the data output from the product registration device. A product registration system is provided.

7. The computer of the product registration device A registration method for registering the products to be purchased. A means of receiving a service to be applied to the aforementioned product after payment, Association means for storing in association the goods registered by the registration means and the services applicable to said goods, An output means for outputting the product and the service associated by the association means, A summing means that adds the service fees received by the reception means to the price of the goods registered by the registration means. To make it function as, The reception means includes means for displaying a screen for selecting the type of service to apply to a plurality of products registered by the registration means, means for selecting the type of service, and means for selecting the product to which the service will be applied with respect to the target product corresponding to the selected type of service included among the plurality of products. The association means is a program that stores the association between the product selected by the selection means and the service.

Images