JP7844263B2 - Information terminals and their programs - Google Patents

Description

Embodiments of the present invention relate to an information terminal and its program.

Self-service product registration systems, which allow customers to input necessary data for registering purchased items using information terminals such as smartphones and tablets, are already being used in stores such as supermarkets. In this type of self-service product registration system, techniques for enhancing promotional effectiveness are already known, such as displaying promotional information on the information terminal's display device when customers use it in the store, including information on special offers and coupons usable at that store.

However, in order to obtain information about store promotions from an information terminal, customers must actually go to that store. Therefore, it's not possible to use an information terminal to gather information about promotions from multiple stores in advance and then decide which store to shop at.

Japanese Patent Publication No. 2019-153088

The problem that the embodiments of this invention aim to solve is to enable users of an information terminal used as a product registration terminal in a self-service product registration system to easily obtain information related to the store's sales promotions, etc., on that information terminal before entering the store.

In one embodiment, the information terminal is a portable information terminal for users to self-input data necessary for registering purchased items at a store. The information terminal comprises a setting unit, a first acquisition unit, and a notification unit. The setting unit allows the user to set their favorite stores from among multiple stores. The first acquisition unit acquires data from a server via wireless communication indicating whether each of the multiple stores has information that should be notified to the consumer. The notification unit, based on the data acquired by the first acquisition unit, notifies the user if their favorite store has information that should be notified to the consumer.

Figure 1 is a block diagram showing a schematic configuration of a self-service product registration system according to one embodiment. Figure 2 is a schematic diagram showing the main components of the member data stored in the member data file. Figure 3 is a schematic diagram showing the main components of the store data stored in the store data file. Figure 4 is a schematic diagram showing the main components of the distribution data stored in the distribution data file. Figure 5 is a block diagram showing the main circuit configuration of the support server. Figure 6 is a schematic diagram showing the main data sets stored in the transaction file. Figure 7 is a schematic diagram showing the main data sets stored in the store list. Figure 8 is a block diagram showing the main circuit configuration of an information terminal. Figure 9 is a flowchart showing the main steps of the primary information processing performed by the processor of an information terminal. Figure 10 is a flowchart showing the main steps of the primary information processing performed by the processor of an information terminal. Figure 11 is a flowchart showing the main steps of the primary information processing performed by the processor of an information terminal. Figure 12 is a flowchart showing the main steps of the primary information processing performed by the processor of an information terminal. Figure 13 is a flowchart showing the main steps of the primary information processing performed by the processor of an information terminal. Figure 14 is a flowchart showing the main steps of the primary information processing performed by the processor of an information terminal. Figure 15 is a flowchart showing the main steps of the primary information processing performed by the processor of an information terminal. Figure 16 is a flowchart showing the main steps of the primary information processing performed by the processor of an information terminal. Figure 17 is a flowchart showing the main steps of the primary information processing performed by the processor of an information terminal. Figure 18 is a flowchart showing the essential steps of the startup notification command reception process executed by the support server's processor. Figure 19 is a flowchart showing the essential steps of the timer interrupt processing performed by the support server's processor. Figure 20 is a flowchart showing the essential steps of the termination notification command reception process executed by the support server's processor. Figure 21 is a flowchart showing the main steps of the favorite notification command reception process executed by the support server's processor. Figure 22 is a flowchart showing the essential steps of the release notification command reception process executed by the support server's processor. Figure 23 is a flowchart showing the essential steps of the notification request command reception process executed by the support server's processor. Figure 24 is a flowchart showing the essential steps of the check-in request command reception process executed by the support server's processor. Figure 25 is a flowchart showing the essential steps of the registration request command reception process executed by the support server's processor. Figure 26 is a flowchart showing the essential steps of the settlement request command reception process executed by the support server's processor. Figure 27 is a schematic diagram showing an example of the display on the top screen of an information terminal's touch panel. Figure 28 is a schematic diagram showing one example of a merchant list screen displayed on the touch panel of an information terminal. Figure 29 is a schematic diagram showing an example of a favorites screen displayed on the touch panel of an information terminal. Figure 30 is a schematic diagram showing an example of a store notification screen displayed on the touch panel of an information terminal. Figure 31 is a schematic diagram showing an example of a notification screen displayed on the touch panel of an information terminal. Figure 32 is a schematic diagram showing an example of a display on the reading screen of an information terminal's touch panel. Figure 33 is a schematic diagram showing an example of a registration screen displayed on the touch panel of an information terminal. Figure 34 is a schematic diagram showing an example of an accounting screen displayed on the touch panel of an information terminal.

One embodiment will be described below with reference to the drawings.
This embodiment allows users of an information terminal used as a product registration terminal in a self-service product registration system to easily access information related to the store's sales promotions before entering the store. In the following description, the user of the information terminal may be referred to as a consumer, customer, member, or operator.

[Explanation of the Self-Service Product Registration System Configuration]
First, we will explain the configuration of the self-service product registration system.
Figure 1 is a block diagram illustrating the schematic configuration of the self-service product registration system 100 according to this embodiment. The self-service product registration system 100 includes a server system 10 utilizing cloud computing and a POS (Point of Sales) system 20 built in a store. The store is a retail store such as a supermarket, where the sales area where goods are displayed and the checkout area (cash register) for payment are separated. The store is, for example, a franchisee that has entered into a franchise agreement with a company that operates the server system 10. The franchisee is not limited to one store. The self-service product registration system 100 is composed of the POS systems 20 of one or more franchisee stores and the server system 10.

The server system 10 and the POS system 20 enable bidirectional data communication via a network 30 utilizing the Internet Protocol. Network 30 is a wide-area network using public or dedicated lines as relay networks and wired LANs (Local Area Networks), wireless LANs, mobile communication networks, and cell phone communication networks as access networks.

The self-service product registration system 100 requires an information terminal 40 that functions as a product registration terminal. The information terminal 40 is, for example, a portable wireless communication terminal that can access the server system 10 using a mobile phone communication network. The information terminal 40 is used by the user to manually input the data necessary for registering purchased products at a participating store. For example, a smartphone or tablet owned by a general consumer can serve as the information terminal 40.

The server system 10 comprises a support server 11 and a router 12, which are connected by a communication line 13. The router 12 is also connected to the network 30 and serves as a relay point for data communication between the support server 11 and the POS system 20 using the network 30.

The support server 11 is a computer that assists customers visiting affiliated stores with self-registration, where they input the necessary data for registering purchased items using the information terminal 40. To provide this assistance, the support server 11 has at least the following two functions: The first function is to generate transaction data with the customer using the information terminal 40, based on the data necessary for registering purchased items entered on the terminal. The second function is to provide the POS system 20 with the data necessary for settling the transaction with the customer using the information terminal 40, in response to accounting instructions from the terminal 40.

Furthermore, the support server 11 has a third function: the ability to distribute notification information to the information terminal 40. Notification information refers to information that member stores should notify consumers of. For example, information related to sales promotions, such as information on special offers, new products, campaigns, and time-limited sales, constitutes notification information. The notification information distributed to the information terminal 40 is displayed, for example, on a display device, notifying the consumer who is the user of the information terminal 40.

The support server 11 has at least a member data file 14, a store data file 15, and a distribution data file 16 in order to realize the third function. The member data file 14 is a collection of member data 141 (see Figure 2) created for each member. The store data file 15 is a collection of store data 151 (see Figure 3) created for each affiliated store. The distribution data file 16 is a collection of distribution data 161 (see Figure 4) created for each announcement information.

Figure 2 is a schematic diagram showing the main components of member data 141. As shown, member data 141 includes member ID, number of favorite stores k, store IDs for those k stores, and an active flag Fa.

The Member ID is a unique code assigned to each member to identify them. A member is a consumer who has registered to input the necessary data for registering purchased items using the information terminal 40. Consumers who wish to self-register at a participating store must register in advance. Member registration is performed by installing a dedicated application software, the self-registration program, on the information terminal 40. Upon registration, a consumer who is a user of the information terminal 40 is assigned a unique Member ID.

The number of favorite stores (k) is the number of affiliated stores that a member, identified by their member ID, has set as a favorite store. A member can set one or more stores as favorites from among the affiliated stores. When a member sets a favorite store, the store ID of that favorite store is included in the member's data (141). The store ID is a unique code assigned to each affiliated store to identify them individually.

The "Running" flag Fa is a one-bit data value used to identify whether the self-registration program is running on the information terminal 40, where the user is a member identified by a member ID. In this embodiment, the "Running" flag Fa is set to "1" to indicate that the program is running, and the "Running" flag Fa is set to "0" to indicate that the program is not running. That is, when the self-registration program is started on the information terminal 40, the "Running" flag Fa of the member data 141, which describes the member ID of the member who is the user of the information terminal 40, becomes "1". Subsequently, when the self-registration program terminates, the "Running" flag Fa becomes "0".

Figure 3 is a schematic diagram showing the main components of store data 151. As shown, store data 151 includes store ID, store name, and number of distributed data (n). As mentioned earlier, the store ID is a unique code assigned to each member store to individually identify them. The store name is the unique name of the member store identified by the store ID. The number of distributed data (n) is the number of currently valid announcements among the announcements held by that member store. As will be described later, announcements have a defined distribution period. Currently valid announcements are those whose current date and time fall within the distribution period. Announcements whose current date and time fall outside the distribution period are invalid.

Figure 4 is a schematic diagram showing the main components of the distribution data 161. As shown, the distribution data 161 includes a data ID, store ID, distribution start date and time, distribution end date and time, distribution in progress flag Fb, and notification information. As mentioned above, the notification information is information that the affiliated store should notify consumers of. The data ID is a unique code assigned to each data item to individually identify the distribution data 161 stored in the distribution data file 16. The store ID is the store ID of the affiliated store that has the notification information. The distribution start date and time and distribution end date and time are the start and end dates and times of the distribution period for the notification information. The distribution in progress flag Fb is a 1-bit data that identifies whether the current date and time is within the distribution period of the notification information. In this embodiment, the distribution in progress flag Fb indicating the distribution period from the distribution start date and time to the distribution end date and time is set to "1," and the distribution in progress flag indicating outside the distribution period (before the distribution start date and time or after the distribution end date and time) is set to "0."

Let's return to the explanation of Figure 1.
The POS system 20 includes a store server 21, a monitoring terminal 22, a POS terminal 23, and a dedicated cashier 24, which are connected via an in-store network 25. The POS system 20 also connects a router 26 to the in-store network 25, and connects to network 30 via this router 26. Furthermore, the POS system 20 connects an access point 27 to the in-store network 25, enabling wireless LAN data communication with the information terminal 40 via this access point 27.

The store server 21 is a computer that manages sales information, product inventory information, and order information for the affiliated store where the POS system 20 is installed, based on transaction information settled at that store.

The monitoring terminal 22 is a terminal for monitoring customers who are using the information terminal 40 to self-register their purchased items. The monitoring terminal 22 is equipped with a monitor that displays customer behavior within the store, data related to the customer's purchased items, etc.

The POS terminal 23 is an accounting machine that processes settlements for transactions with customers who do not use the information terminal 40. The POS terminal 23 is operated by a store employee. The POS terminal 23 may be separated into a registration machine and a payment machine, with the registration machine operated by a store employee and the payment machine operated by the customer (a semi-self-service system). Alternatively, the POS terminal 23 may be fully self-service, operated by the customer.

The dedicated accounting machine 24 is an accounting machine that processes settlements for transactions with customers using the information terminal 40. The customer acts as the operator of the dedicated accounting machine 24. The dedicated accounting machine 24 has functions such as scanning the accounting barcode displayed on the information terminal 40, payment processing functions supporting various payment methods such as electronic money, credit cards, and cash, and an electronic money charging function.

Note that the POS system 20 shown in Figure 1 is just one example. The configuration of the POS system 20 may differ for each participating store.

[Explanation of the support server configuration]
Next, we will explain the configuration of the support server 11.
Figure 5 is a block diagram showing the main circuit configuration of the support server 11. The support server 11 comprises a processor 111, main memory 112, auxiliary storage device 113, clock 114, communication interface 115, and system transmission path 116. The system transmission path 116 includes an address bus, data bus, control signal lines, etc. The support server 11 connects the processor 111, main memory 112, auxiliary storage device 113, clock 114, and communication interface 115 to the system transmission path 116. In the support server 11, the computer is composed of the processor 111, main memory 112, auxiliary storage device 113, clock 114, and communication interface 115, and the system transmission path 116 connecting them.

The processor 111 corresponds to the central part of the computer described above. The processor 111 controls various components to realize various functions as a support server 11, according to the operating system or application program (application software). The processor 111 is, for example, a CPU (Central Processing Unit).

The main memory 112 corresponds to the main memory portion of the computer described above. The main memory 112 includes both a non-volatile memory area and a volatile memory area. The non-volatile memory area of the main memory 112 stores the operating system or application programs. The volatile memory area of the main memory 112 stores data necessary for the processor 111 to perform processing for controlling various parts. This data may also be stored in the non-volatile memory area. The volatile memory area of the main memory 112 is used as a work area where data is rewritten as needed by the processor 111. The non-volatile memory area is, for example, ROM (Read Only Memory). The volatile memory area is, for example, RAM (Random Access Memory).

The auxiliary storage device 113 corresponds to the auxiliary storage portion of the computer described above. For example, an EEPROM (Electric Erasable Programmable Read-Only Memory), HDD (Hard Disk Drive), or SSD (Solid State Drive) can serve as the auxiliary storage device 113. The auxiliary storage device 113 stores data used by the processor 111 for various processing tasks, or data created by the processing performed by the processor 111. The auxiliary storage device 113 may also store the application program described above.

Clock 114 measures the date and time. Support server 11 obtains the date and time measured by clock 114 as the current date and time.

The communication interface 115 is a circuit for transmitting and receiving data between devices connected via the network 30, according to a predetermined communication protocol.

The support server 11 uses a portion of the volatile area in its main memory 112 as storage for transaction files 51 and store lists 52. Both transaction files 51 and store lists 52 are data sets created for each user of the information terminal 40; therefore, the storage area is designed to accommodate multiple transaction files 51 and multiple store lists 52.

Figure 6 is a schematic diagram showing the main data sets stored in the transaction file 51. As shown, the transaction file 51 stores the member ID, store ID, number of item data points (m), item data for those m points, total number of items, total amount, accounting code, etc. This data is necessary for settling transactions. In other words, in the transaction file 51, the member ID functions as a transaction identification code to identify transactions with customers. The transaction identification code does not have to be the member ID. The transaction identification code may also be a code for identifying the information terminal 40; for example, the device ID of the information terminal 40, a mobile phone number, etc., can serve as the transaction identification code. The transaction identification code may also be, for example, a transaction number for identifying a transaction, or it may be a combination of the transaction number, store ID, and date and time information such as the date and time of entry.

The store ID is the store ID of the affiliated store where the customer, identified by the member ID, self-registers purchased items using the information terminal 40. The product details data includes items such as the product code, product name, price, number of items sold, and sales amount for the purchased items. The total number of items is the sum of the sales amounts for several m item details. The total amount is the sum of the sales amounts for several m item details. The sales amount is calculated by multiplying the price by the number of items sold. The accounting code is the code used by the customer, identified by the member ID, when making a payment at that store.

Figure 7 is a schematic diagram showing the main data sets stored in the store list 52. As shown in the figure, the store list 52 stores member IDs. In addition, list data describing the store name, favorite flag Fc, and number of distributed data n are stored, associated with each affiliated store's store ID. In the list data, the favorite flag Fc is a 1-bit data that identifies whether the member identified by the member ID has registered the affiliated store identified by the associated store ID as a favorite store. In this embodiment, the favorite flag Fc is set to "1" if the store is registered as a favorite store, and to "0" if it is not. The number of distributed data n is, as mentioned above, the number of currently valid announcements among the announcement information held by the affiliated store identified by the associated store ID.

[Explanation of the information terminal configuration]
Next, the configuration of the information terminal 40 will be described.
Figure 8 is a block diagram showing the main circuit configuration of the information terminal 40. The information terminal 40 includes a processor 41, internal memory 42, external memory 43, touch panel 44, camera 45, wireless unit 46, and system transmission line 47. The system transmission line 47 includes an address bus, data bus, control signal lines, etc. The information terminal 40 connects the processor 41, internal memory 42, external memory 43, touch panel 44, camera 45, and wireless unit 46 to the system transmission line 47. In the information terminal 40, the computer is composed of the processor 41, internal memory 42, external memory 43, and the system transmission line 47 connecting them.

The processor 41 corresponds to the central part of the computer described above. The processor 41 controls various components to realize various functions as an information terminal 40, according to the operating system or application program (application software). The processor 41 is, for example, a CPU.

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

External memory 43 corresponds to the auxiliary storage portion of the computer described above. For example, an SD memory card, USB memory, etc., can serve as external memory 43. External memory 43 stores data used by the processor 41 for various processing tasks, or data created by processing performed by the processor 41. External memory 43 may also store the application program described above.

The touch panel 44 is a device that combines a display unit and a touch sensor unit. The display has a screen for displaying various images. The touch sensor detects the position on the screen touched by the operator. The touch panel 44 acquires data input by the operator from the position on the screen detected by the touch sensor and the image information displayed at that position. Thus, the touch panel 44 is both an example of a display device and an example of an input device.

The camera 45 is an imaging device built into the information terminal 40. The processor 41 functions as a reader, reading codes such as barcodes and 2D codes from images captured by the camera 45. Many products have barcodes that represent the product code according to a predetermined barcode system. The processor 41 obtains the product code of the purchased item by reading the barcode attached to the product from the image captured by the camera 45. Thus, the camera 45 functions as an input device for the information terminal 40.

The wireless unit 46 is a communication device that performs data communication with the access point 27 according to the wireless LAN communication protocol.

In the information terminal 40 with this configuration, a self-registration program is installed in the internal memory 42 or external memory 43. The method of installing the self-registration program in the internal memory 42 or external memory 43 is not particularly limited. The self-registration program can be installed in the internal memory 42 or external memory 43 by recording it on a removable recording medium or by distributing the self-registration program via communication over a network. The recording medium can be of any form as long as it can store a program and is readable by the device, such as an SD memory card or USB memory.

In an information terminal 40 with the self-registration program installed, a portion of the external memory 43 is designated as the member ID area 431. Additionally, a portion of the internal memory 42 is designated as the store list area 421, the number of favorite stores k area 422, the total number of notifications N area 423, and the notification information area 424. At least one of each of the areas 421, 422, 423, and 424 may be formed in the external memory 43.

In an information terminal 40 with the self-registration program installed, the processor 41 functions as a setting unit 411, a first acquisition unit 412, a second acquisition unit 413, a notification unit 414, an output unit 415, a notification unit 416, and a specific unit 417.

The setting unit 411 has the function of setting the consumer's favorite store from among multiple affiliated stores. The setting unit 411 can be rephrased as the setting means. The first acquisition unit 412 has the function of acquiring data from the support server 11 via wireless communication that indicates whether or not each of the multiple affiliated stores has information to notify the consumer, that is, valid notification information. Such data is the data of the store list 52. The first acquisition unit 412 can be rephrased as the first acquisition means. The second acquisition unit 413 has the function of acquiring information that the user's favorite store has to notify the consumer from the support server 11 via wireless communication. The second acquisition unit 413 can be rephrased as the second acquisition means. The notification unit 414 has the function of notifying the user if the user's favorite store has information to notify the consumer based on the data acquired by the first acquisition unit 412. The notification unit 414 also has the function of notifying the user each time the information that the user's favorite store has to notify the consumer is updated. The notification unit 414 can be rephrased as the notification means. The output unit 415 has the function of outputting the information acquired by the second acquisition unit 413. The output unit 415 can be rephrased as an output means. The notification unit 416 has the function of notifying the support server 11 of the favorite stores specified by the user from among the favorite stores that have notification information reported by the notification unit 414. The identification unit 417 has the function of identifying the affiliated store that the user has entered. The notification unit 416 also has the function of notifying the support server 11 of the favorite store if the affiliated store identified by the identification unit 417 is a favorite store. The notification unit 416 can be rephrased as a notification means. The identification unit 417 can be rephrased as an identification means. These functions 411 to 417 are realized by the processor 41 performing various information processing according to the self-registration program.

[Explanation of the operation of the self-service product registration system]
Next, the operation of the self-service product registration system will be explained based on the information processing procedures performed by the processor 41 of the information terminal 40 and the information processing procedures performed by the processor 111 of the support server 11.
Figures 9 to 17 are flowcharts showing the main information processing steps performed by the processor 41 of the information terminal 40 in accordance with the self-registration program. Figures 18 to 26 are flowcharts showing the main information processing steps performed by the processor 111 of the support server 11 in cooperation with the information terminal 40. Figures 27 to 34 are examples of various screens displayed on the touch panel 44 of the information terminal 40. Note that the information processing procedures and contents described below are examples only. The procedures or contents can be changed as appropriate if similar effects can be achieved. Also, the layout, images, text, etc. of each screen are not limited to those shown.

When the self-registration program is started on the information terminal 40, the processor 41 begins information processing according to the procedure shown in the flowcharts in Figures 9 to 17. First, the processor 41 obtains the member ID from area 431 as ACT1 in Figure 9. Then, the processor 41 controls the wireless unit 46 to send a startup notification command as ACT2. This control causes the startup notification command to be wirelessly transmitted from the wireless unit 46. The startup notification command is sent to the support server 11 via the network 30, which uses the mobile phone communication network as its access network. The startup notification command includes the member ID obtained in ACT1.

Upon receiving the startup notification command, the processor 111 of the support server 11 begins the information processing procedure shown in the flowchart of Figure 18, which is the so-called startup notification command reception processing. The processor 111 obtains the member ID from the startup notification command as ACT 201. Then, as ACT 202, the processor 111 searches the member data file 14 and changes the operational flag Fa of the member data 141 containing the obtained member ID from "0" to "1".

Processor 111 reads member data 141, including the acquired member ID, from member data file 14 as ACT 203. Processor 111 also reads store data 151 for all member stores from store data file 15 as ACT 204. Then, as ACT 205, processor 111 saves the member ID acquired from the startup notification command and creates a store list 52 using the store data 151 for all member stores read from store data file 15 as list data. At this time, as ACT 206, processor 111 sets all favorite flags Fc in the list data to "0".

Having finished creating the store list 52, processor 111 resets the increment counter P to "0" as ACT 207. Next, processor 111 increments the increment counter P by "1" as ACT 208. Finally, processor 111 checks as ACT 209 whether the increment counter P has exceeded the maximum value Pmax. The maximum value Pmax is the total number of store data entries 151 stored in the store data file 15.

If the increment counter P does not exceed the maximum value Pmax, the processor 111 proceeds from ACT 209 to ACT 210. As ACT 210, the processor 111 retrieves the P-th store ID from the store list 52. The "P" in P is the count value of the increment counter P. The P-th store ID is the P-th store ID from the beginning of the list data in the store list 52.

If the P-th store ID is obtained, the processor 111 compares it with the member data 141 read from the member data file 14 as ACT 211. Hereinafter, the member data 141 read from the member data file 14 will be referred to as the target member data 141. The processor 111 checks whether the target member data 141 contains the P-th store ID as ACT 212. If the target member data 141 contains the P-th store ID, that is, if the affiliated store identified by the P-th store ID is a favorite store of the member identified by the member ID, the processor 111 proceeds from ACT 212 to ACT 213. As ACT 213, the processor 111 changes the favorite flag Fc associated with the P-th store ID from the beginning of the list data in the store list 52 from "0" to "1". After that, the processor 111 returns to ACT 208. In contrast, if the P-th store ID does not exist in the target member data 141, that is, if the affiliated store identified by the P-th store ID is not a favorite store of the member identified by the member ID, the processor 111 skips the processing of ACT 213 and returns to ACT 208.

The processor 111, having returned to ACT 208, executes the processing of ACTs 208 through 213 in the same manner as described above until the increment counter P exceeds the maximum value Pmax. That is, the processor 111 increments the increment counter P by "1" each time, and each time, retrieves the P-th store ID from the beginning of the list data and checks whether that store ID is included in the target member data 141. If it is included, the processor 111 changes the favorite flag Fc associated with the P-th store ID from the beginning of the list data from "0" to "1".

When the summation counter P exceeds the maximum value Pmax, the processor 111 proceeds from ACT 209 to ACT 214. The processor 111 saves the store list 52 to the main memory 112 as ACT 214. The processor 111 also controls the communication interface 115 to send the store list 52 to the information terminal 40, the source of the startup notification command, as ACT 215. This control wirelessly transmits the store list 52 data to the information terminal 40 via the network 30. With this, the processor 111 completes the startup notification command reception process.

Thus, upon receiving the startup notification command, the support server 11 creates and stores a store list 52 containing the member IDs included in the startup notification command, and then transmits the store list 52 to the information terminal 40 that sent the startup notification command. The store list 52 includes data that identifies whether a store is a favorite of the member identified by the member ID, i.e., a favorite flag Fc, and the number of currently valid announcements among the announcements held by the participating store, i.e., the number of distributed data items n.

By the way, the number of currently valid notification information items, i.e., the number of distributed data items n, is updated as time passes. Therefore, the support server 11 has the function of updating the created store list 52 in accordance with the update of the number of distributed data items n, and sending the updated store list 52 to the information terminal 40 where the member ID of the store list 52 is set. This update is achieved by the timer interrupt processing described below.

Figure 19 is a flowchart showing the essential steps of the timer interrupt processing performed by the processor 111 of the support server 11. The processor 111 starts the timer interrupt processing each time it receives a timer interrupt signal. The timer interrupt signal is generated, for example, each time a predetermined period of time has elapsed, as measured by the clock 114. The predetermined period is preferably one minute, assuming the distribution start and end times are measured in minutes.

When processor 111 starts timer interrupt processing, it resets the add counter Q to "0" as ACT221. Next, processor 111 increments the add counter Q by "1" as ACT222. Then, processor 111 checks as ACT223 whether the add counter Q has exceeded the maximum value Qmax. The maximum value Qmax is the number of distribution data 161 stored in the distribution data file 16.

If the addition counter Q does not exceed the maximum value Qmax, the processor 111 reads the Qth distribution data 161 from the distribution data file 16 as ACT224. The "Q" in "Qth" is the count value of the addition counter Q. The Qth distribution data 161 is the Qth distribution data 161 from the beginning among the distribution data 161 stored in the distribution data file 16.

If the Qth distribution data 161 is read from the distribution data file 16, the processor 111 checks, as ACT 225, whether the Qth distribution data 161 is within the distribution period. The processor 111 determines that the distribution period is active if the current date and time, measured by the clock 114, falls within the period from the distribution start date and time to the distribution end date and time of the distribution data 161. The processor 111 determines that the distribution period is outside the active period if the current date and time is before the distribution start date and time or after the distribution end date and time.

If the Qth data distribution 161 is outside the distribution period, processor 111 proceeds from ACT 225 to ACT 226. Processor 111 checks the distribution flag Fd of the Qth data distribution 161 as ACT 226. If the distribution flag Fd is "0", processor 111 returns from ACT 226 to ACT 222. Then, processor 111 executes the processing from ACT 222 onward in the same manner as described above.

If the distribution flag Fd is "1", processor 111 proceeds from ACT 226 to ACT 227. In ACT 227, processor 111 changes the distribution flag Fd of the Qth distribution data 161 from "1" to "0". Also, in ACT 228, processor 111 obtains the store ID from the Qth distribution data 161. Then, in ACT 229, processor 111 reduces the number of distribution data n in the store data file 15, which includes the store ID obtained in ACT 228, by "1".

On the other hand, if the Qth distribution data 161 is within the distribution period in ACT225, the processor 111 proceeds from ACT225 to ACT230. As ACT230, the processor 111 checks the distribution flag Fd of the Qth distribution data 161. If the distribution flag Fd is "1", the processor 111 returns from ACT230 to ACT222. Then, the processor 111 executes the processing from ACT222 onward in the same manner as described above.

If the distribution flag Fd is "0", processor 111 proceeds from ACT230 to ACT231. As ACT231, processor 111 changes the distribution flag Fd of the Qth distribution data 161 from "0" to "1". Then, as ACT232, processor 111 obtains the store ID from the Qth distribution data 161. Finally, as ACT233, processor 111 increments the number of distribution data n in the store data file 15, which includes the store ID obtained in ACT232, by "1".

In ACT229 or ACT233, processor 111, having updated the number of distributed data points n for store data 151, proceeds to ACT234. In ACT234, processor 111 detects members who have designated a member store identified by the store ID obtained from the Qth distributed data point 161 as their favorite store. Specifically, processor 111 detects the member ID of member data 141 stored in member data file 14 that includes the store ID obtained from the Qth distributed data point 161. Hereafter, members with the detected member IDs will be referred to as favorite members.

Once all favorite members have been detected, processor 111 proceeds to ACT 235. In ACT 235, processor 111 extracts all favorite members from the list of members whose information terminal 40's self-registration program is currently running, i.e., favorite members whose running flag Fa stored in member data 141 is "1". In ACT 236, processor 111 updates the number of distribution data entries n in the store list 52, which includes the member IDs of the extracted favorite members. Specifically, if the number of distribution data entries n in store data 151 is decreased by "1" in ACT 229, the number of distribution data entries n in store list 52 is decreased by "1". If the number of distribution data entries n in store data 151 is increased by "1" in ACT 233, the number of distribution data entries n in store list 52 is increased by "1".

Once the number of distribution data points n in the store list 52, which includes the member IDs of favorite members, has been updated, the processor 111 controls the communication interface 115 to send the updated store list 52 (with the updated number of distribution data points n) to the information terminal 40, which is configured with the member IDs stored in the store list 52, as ACT 237. This control ensures that the updated store list 52 is transmitted to the information terminal 40, which is configured with the member IDs of the store list 52 with the updated number of distribution data points n.

After completing the transmission of the updated store list 52 with the number of distributed data points n, processor 111 returns to ACT 222. Processor 111 then executes the processing from ACT 222 onward in the same manner as described above. Thus, when the increment counter Q exceeds the maximum value Qmax in ACT 223, processor 111 terminates the timer interrupt processing.

Thus, the store list 52, created in response to the activation notification command and sent to the information terminal 40 that sent the activation notification command, is resent in real time to the information terminal 40 that sent the activation notification command each time the number of distributed data points n is updated.

Let's return to the explanation of Figure 9.
The processor 41 of the information terminal 40 that sent the startup notification command waits for the store list 52 as ACT3. When the processor 41 receives the store list 52 via the wireless unit 46, it proceeds from ACT3 to ACT4. As ACT4, the processor 41 stores the store list 52 in the memory area 421.

Processor 41, as ACT5, counts the number S of store IDs in the store list 52 whose favorite flag Fc is set to "1". If the number S is "0", that is, if the user of the information terminal 40 has not set a favorite store, processor 41 proceeds from ACT5 to ACT6. As ACT6, processor 41 sets the number of favorite stores k in area 422 to "0". Also, as ACT7, processor 41 sets the total number of notifications N in area 423 to "0".

In contrast, if the number S is 1 or greater, that is, if the user of the information terminal 40 has set a favorite store, the processor 41 proceeds from ACT 5 to ACT 8. In ACT 8, the processor 41 sets the number k of favorite stores in area 422 as number S. Then, in ACT 9, the processor 41 retrieves all the number n of distribution data described in the store list 52, associated with the store IDs where the favorite flag Fc is set to "1". Finally, in ACT 10, the processor 41 sets the total number n of distribution data retrieved as the total number N of notifications in area 423.

After completing the processes of ACT6 and ACT7, or ACT8 through ACT10, the processor 41 proceeds to ACT11. As ACT11, the processor 41 displays the top screen SCa (see Figure 27) on the touch panel 44.

Figure 27 is a schematic diagram showing one example of the display on the top screen SCa. As shown in the figure, the top screen SCa has various soft keys: a shopping start button BTa, a store search button BTb, a favorites button BTc, a notification button BTd, and an exit button BTe. The shopping start button BTa is a soft key that the user of the information terminal 40 inputs when entering a participating store and starting self-registration of purchased items. The store search button BTb is a soft key that the user inputs when searching for participating stores. The user can set a desired store from the participating stores found in the search as a favorite store. The favorites button BTc is a soft key that the user inputs when checking participating stores that have been set as favorites. The user can remove the favorite status of a favorite store that has been checked. The notification button BTd is a soft key that the user inputs when checking notification information for a favorite store. The total number of notifications N stored in area 423 is displayed on the notification button BTd. The total number of notifications N is displayed, for example, enclosed in a circle in the upper right corner of the notification button BTd. If the total number of notifications N is "0", it may or may not be displayed. Furthermore, the display format for the total number of notifications N is not limited to that shown in Figure 27. Essentially, any display format that allows the user to see the total number of notifications N is acceptable. The exit button BTe is a soft key that the user inputs when ending the self-registration program.

The processor 41 of the information terminal 40, which displays the top screen SCa, checks whether it has received the updated store list 52 as ACT 12. If it has not received the updated store list 52, the processor 41 proceeds from ACT 12 to ACT 13. As ACT 13, the processor 41 checks whether any of the soft keys located on the top screen SCa have been pressed. If no soft keys have been pressed, the processor 41 returns to ACT 12. In this way, the processor 41 waits for either the updated store list 52 to be received or for a soft key on the top screen SCa to be pressed in ACT 12 and ACT 13.

When the updated store list 52 is received while the system is in the waiting state for ACT 12 and ACT 13, the processor 41 proceeds from ACT 12 to ACT 14. As ACT 14, the processor 41 updates the store list 52 in area 421 with the updated store list 52. Afterward, the processor 41 returns to ACT 5 and executes the processing from ACT 5 onward in the same manner as described above. Therefore, the new number of favorite stores k and the total number of notifications N are derived from the updated store list 52, and the values in areas 422 and 423 are updated. The total number of notifications N displayed on the top screen SCa is also changed to the updated value. Then, the processor 41 returns to the waiting state for ACT 12 and ACT 13.

Here, the processor 41 realizes its function as the first acquisition unit 412 by executing the processing of ACT3 and ACT4, and further, the processing of ACT12 and ACT14. The processor 41 also realizes its function as the notification unit 414 by cooperating with the touch panel 44 to execute the processing of ACT5 through ACT11.

Thus, when a user of the information terminal 40 launches the self-registration program, the touch panel 44 displays the top screen SCa. The notification button BTd on the top screen SCa displays the total number of notifications N. The total number of notifications N is the number of currently valid notifications from the affiliated stores that the user has set as their favorite stores. Therefore, the user can easily check whether there are currently valid notifications simply by launching the self-registration program.

If either soft key is pressed during the standby state of ACT 12 or ACT 13, the processor 41 proceeds from ACT 13 to ACT 15. The processor 41 checks whether the soft key pressed during ACT 15 is the exit button BTe. If the exit button BTe soft key is pressed, the processor 41 proceeds from ACT 15 to ACT 16. The processor 41 controls the wireless unit 46 to send an exit notification command as ACT 16. This control causes the wireless unit 46 to wirelessly transmit the exit notification command. The exit notification command is sent to the support server 11 via the network 30, which uses the mobile phone communication network as its access network. The exit notification command includes the member ID. Having sent the exit notification command, the processor 41 terminates the information processing according to the self-registration program.

Upon receiving the termination notification command, the processor 111 of the support server 11 begins the information processing procedure shown in the flowchart of Figure 20, which is the so-called termination notification command reception processing. The processor 111 retrieves the member ID from the termination notification command as ACT 251. Hereinafter, the member ID retrieved from the termination notification command will be referred to as the retrieved member ID. The processor 111 deletes the store list 52 containing the retrieved member ID from the main memory 112 as ACT 252. The processor 111 also resets the operational flag Fa of the member data containing the retrieved member ID to "0" as ACT 253. With these steps, the processor 111 completes the termination notification command reception processing.

Thus, when the user of the information terminal 40 touches the exit button BTe on the top screen SCa, the self-registration program stops. Also, the store list 52 related to that user, which was stored in the main memory 112 of the support server 11, is cleared.

Let's return to the explanation of Figure 9.
If, during the standby state of ACT12 and ACT13, a soft key other than the exit button BTe located on the top screen SCa is pressed, the processor 41 proceeds from ACT15 to ACT21 in Figure 10. The processor 41 checks whether the soft key pressed as ACT21 is the shopping start button BTa. If it is not the shopping start button BTa, the processor 41 checks whether the soft key pressed as ACT22 is the store search button BTb. If it is not the store search button BTb either, the processor 41 checks whether the soft key pressed as ACT23 is the favorites button BTc. If it is not the favorites button BTc either, the processor 41 checks whether the soft key pressed as ACT24 is the notification button BTd. If it is not the notification button BTd either, the processor 41 executes another process as ACT25. Other processing refers to the process executed when a button other than the "Start Shopping" button BTa, "Store Search" button BTb, "Favorites" button BTc, "Notifications" button BTd, and "Exit" button BTe is pressed on the top screen SCa. After completing the other processing, the processor 41 returns to the waiting state of ACT12 and ACT13 in Figure 9.

When the store search button BTb is pressed while ACT12 and ACT13 are in standby mode, the processor 41 proceeds from ACT22 to ACT31 in Figure 11. For ACT31, the processor 41 sets the touch panel 44 screen to the affiliated store list screen SCb (see Figure 28).

Figure 28 is a schematic diagram showing one example of the display of the merchant list screen SCb. As shown in the figure, the merchant list screen SCb displays the names of all merchants stored in the store list 52 in order. A soft key for the close button BTf is also displayed. Furthermore, for merchants whose favorite flag Fc is set to "1", a mark MAa indicating that it is a favorite store is displayed. For merchants whose favorite flag Fc is set to "0", a mark MAb indicating that it is not a favorite store is displayed. Note that the forms of marks MAa and MAb are not limited to those shown in Figure 28. The main point is that the user of the information terminal 40 should be able to distinguish between merchants they have set as favorite stores and those they have not.

To add a new favorite store, a user who has viewed the merchant list screen (SCb) should touch the store name displaying the MAb mark. To close the merchant list screen (SCb), the user should touch the close button (BTf).

Let's return to the explanation of Figure 11.
The processor 41 of the information terminal 40 displaying the merchant list screen SCb waits for either the close button BTf to be pressed as ACT32, or for one of the merchant names to be selected by touch as ACT33. If a merchant name is selected while in the waiting state of ACT32 and ACT33, the processor 41 proceeds from ACT33 to ACT34. As ACT34, the processor 41 checks the favorite flag Fc stored in the merchant list 52 in association with the merchant ID of the selected merchant name. If the favorite flag Fc is "1", that is, if the user has selected the merchant name of a favorite merchant, the processor 41 returns to the waiting state of ACT32 and ACT33.

In contrast, if the favorite flag Fc is "0," that is, if the user selects a store name of a member store that is not a favorite store, the processor 41 proceeds from ACT 34 to ACT 35. The processor 41 controls the wireless unit 46 to send a favorite notification command as ACT 35. This control causes the favorite notification command to be wirelessly transmitted from the wireless unit 46. The favorite notification command is sent to the support server 11 via the network 30, which uses the mobile phone communication network as its access network. The favorite notification command includes the member ID, along with the store ID described in the store list 52 in association with the selected store name.

Upon receiving a favorite notification command, the processor 111 of the support server 11 begins the information processing procedure shown in the flowchart in Figure 21, which is the so-called favorite notification command reception processing. The processor 111 obtains the member ID and store ID from the favorite notification command as ACT 261. Hereafter, the member ID obtained from the favorite notification command will be referred to as the obtained member ID. Similarly, the store ID obtained from the favorite notification command will be referred to as the obtained store ID.

Processor 111, as ACT 262, detects member data 141 containing the acquired member ID from the member data file 14. Then, as ACT 263, processor 111 adds the acquired store ID to the member data 141 containing the acquired member ID. Furthermore, as ACT 264, processor 111 increments the number of favorite stores k in the member data 141 containing the acquired member ID by "1".

Processor 111 detects the store list 52 containing the acquired member ID as ACT 265. Then, as ACT 266, Processor 111 changes the favorite flag Fc associated with the acquired store ID in the store list 52 containing the acquired member ID from "0" to "1". Subsequently, as ACT 267, Processor 111 controls the communication interface 115 to send the store list 52 with the changed favorite flag Fc to the information terminal 40 that sent the favorite notification command. This control wirelessly transmits the data of the store list 52 with the changed favorite flag Fc to the information terminal 40 that sent the favorite notification command via the network 30. This completes the receiving process of the favorite notification command.

Let's return to the explanation of Figure 11.
The processor 41, which controls the sending of the favorite notification command, returns to the waiting state of ACT 32 and ACT 33. In this waiting state, if another store name is selected, the processor 41 executes the processing of ACT 34 and ACT 35 in the same manner as described above. Therefore, each time a store name of a member store that is not a favorite store is selected from the store names displayed on the member store list screen SCb, the processor 41 sends a favorite notification command to the support server 11, including the store ID and member ID of that member store. In response, the support server 11 executes the favorite notification command reception processing described using Figure 21. Therefore, the favorite flag associated with the store ID in the store list 52, which includes the member ID, is updated from "0" to "1", and the updated store list 52 is sent to the information terminal 40 that sent the favorite notification command.

When the close button BTf is pressed while ACT32 and ACT33 are in standby mode, the processor 41 returns to the standby mode of ACT12 and ACT13 as shown in Figure 9. Therefore, upon receiving the updated store list 52 with the favorite flag Fc changed from the support server 11, the processor 41 changes the store list 52 in area 421 to the updated store list 52.

If the favorite button BTc is pressed while in the standby state of ACT12 and ACT13, the processor 41 proceeds from ACT23 to ACT26 in Figure 10. In ACT26, the processor 41 checks whether the number of favorite stores k in area 422 is "1" or greater. If the number of favorite stores k is "0," that is, if the user has not set any favorite stores, the processor 41 returns to the standby state of ACT12 and ACT13 in Figure 9.

If the number of favorite stores k is "1" or greater, the processor 41 proceeds from ACT 26 to ACT 51 in Figure 12. As ACT 51, the processor 41 detects the store ID and store name of affiliated stores whose favorite flag Fc is set to "1" from the store list 52 stored in area 421. That is, the processor 41 detects the store ID and store name of affiliated stores that the user of the information terminal 40 has set as a favorite store. Then, as ACT 52, the processor 41 sets the screen of the touch panel 44 as the favorite screen SCc (see Figure 29).

Figure 29 is a schematic diagram showing an example of the display of the Favorites screen SCc. As shown in the figure, the Favorites screen SCc displays the names of the stores detected from the store list 52, i.e., the names of the favorite stores, in order. A soft key for the close button BTg is also displayed. Furthermore, a mark MAa indicating that it is a favorite store is displayed next to each store name.

To remove a favorite store from a user's favorites screen (SCc), the user touches the store's name. To close the favorites screen (SCc), the user touches the close button (BTf).

Returning to the explanation of Figure 12.
The processor 41, which controls the display of the favorites screen SCc, waits for either the close button BTg to be pressed as ACT 53, or for one of the store names to be selected by touch operation as ACT 54. If a store name is selected during the waiting state of ACT 53 and ACT 54, the processor 41 proceeds to ACT 55. As ACT 55, the processor 41 displays a confirmation screen on the touch panel 44 to ask the user whether or not to remove the favorites status. The confirmation screen is, for example, a screen with a confirmation message such as "Do you want to remove the favorite store?" along with "Yes" and "No" buttons. The confirmation screen is displayed as a pop-up, for example, on top of the favorites screen SCc.

Processor 41 checks whether a command to cancel the favorite status is issued as ACT 56. If the "No" button is touched, processor 41 recognizes that the cancellation has been reversed. Processor 41 returns to the waiting state for ACTs 53 and 54.

If the "Yes" button is touched, the processor 41 recognizes that a command to remove the favorite item has been issued. The processor 41 then proceeds to ACT 57. The processor 41 controls the wireless unit 46 to send a removal notification command as ACT 57. This control causes the wireless unit 46 to wirelessly transmit the removal notification command. The removal notification command is sent to the support server 11 via the network 30, which uses the mobile phone communication network as its access network. The removal notification command includes the member ID and the store ID of the merchant whose favorite item has been removed.

Upon receiving the cancellation notification command, the processor 111 of the support server 11 begins the information processing procedure shown in the flowchart in Figure 22, which is the so-called cancellation notification command reception processing. The processor 111 obtains the member ID and store ID from the cancellation notification command as ACT 271. Hereafter, the member ID obtained from the cancellation notification command will be referred to as the "obtained member ID." Similarly, the store ID obtained from the cancellation notification command will be referred to as the "obtained store ID."

Processor 111, as ACT 272, detects member data 141 containing the acquired member ID from the member data file 14. Then, as ACT 273, processor 111 removes the acquired store ID from the member data 141 containing the acquired member ID. Furthermore, as ACT 274, processor 111 reduces the number of favorite stores k in the member data 141 containing the acquired member ID by "1".

Processor 111 detects the store list 52 containing the acquired member ID as ACT 275. Processor 111 then changes the favorite flag Fc associated with the acquired store ID in the store list 52 containing the acquired member ID from "1" to "0" as ACT 276. Subsequently, processor 111 controls the communication interface 115 to send the store list 52 with the changed favorite flag Fc to the information terminal 40 that sent the cancellation notification command as ACT 277. This control wirelessly transmits the data of the store list 52 with the changed favorite flag Fc to the information terminal 40 that sent the cancellation notification command via the network 30. This completes the receiving process of the cancellation notification command.

Returning to the explanation of Figure 12.
The processor 41, which controlled the transmission of the cancellation notification command, returns to the waiting state for ACT 53 and ACT 54. In this waiting state, if another store name is selected, the processor 41 executes the processing of ACT 56 to ACT 57 in the same manner as described above. Therefore, each time a store name is selected from the store names displayed on the favorites screen SCc and a command to cancel the favorite is issued, the processor 41 sends a cancellation notification command to the support server 11, which includes the store ID and member ID of the affiliated store of that store name. In response, the support server 11 executes the receiving process for the cancellation notification command, as explained using Figure 22. Therefore, the favorite flag associated with the store ID in the store list 52, which includes the member ID, is updated from "1" to "0", and the updated store list 52 is sent to the information terminal 40 that sent the cancellation notification command.

When the close button BTg is pressed while ACT 53 and ACT 54 are in standby mode, the processor 41 returns to the standby mode of ACT 12 and ACT 13 as shown in Figure 9. Therefore, upon receiving the updated store list 52 with the favorite flag Fc changed from the support server 11, the processor 41 changes the store list 52 in area 421 to the updated store list 52.

Here, the processor 41 realizes its function as a setting unit 411 by executing the processes of ACT31 to ACT35 in Figure 11 and the processes of ACT51 to ACT57 in Figure 12.

Thus, when a user of the information terminal 40 presses the store search button BTb on the top screen SCa, the touch panel 44 displays the affiliated store list screen SCb. This affiliated store list screen SCb allows the user to view a list of affiliated stores where they can self-register purchased items using the information terminal 40. Furthermore, the user can distinguish between affiliated stores they have set as favorites and those they have not. To set a new favorite store, the user touches the store name displayed on the affiliated store list screen SCb along with the mark MAb. This operation registers the touched affiliated store as the user's favorite store in the support server 11. Therefore, the user can easily set their desired affiliated store as a favorite store.

On the other hand, when the user presses the Favorites button BTc on the top screen SCa, the touch panel 44 screen changes to the Favorites screen SCc. This Favorites screen SCc allows the user to see the member stores they have set as favorites. To remove a store from the favorites list, the user touches the store name displayed on the Favorites screen SCc along with the mark MAa. This operation causes the support server 11 to manage the touched member store as no longer a favorite of the user. Therefore, the user can easily remove a store from their favorites list with a simple operation.

If the notification button BTd is pressed while ACT12 and ACT13 are in standby mode, the processor 41 proceeds from ACT24 to ACT27 in Figure 10. In ACT27, the processor 41 checks whether the total number of notifications N in area 423 is "1" or greater. If the total number of notifications N is "0," that is, if there is no valid notification information at this time, the processor 41 returns to the standby mode of ACT12 and ACT13 in Figure 9.

If the total number of notifications N is "1" or greater, the processor 41 proceeds from ACT 27 to ACT 61 in Figure 13. As ACT 61, the processor 41 detects the store ID and store name of member stores from the store list 52 stored in area 421 where the favorite flag Fc is set to "1" and the number of distributed data n is "1" or greater. That is, the processor 41 detects the store ID and store name of member stores that are the user's favorite stores and currently have one or more valid notification items. As ACT 62, the processor 41 sets the touch panel 44 screen to the notification store screen SCd (see Figure 30).

Figure 30 is a schematic diagram showing one example of the display of the notification store screen SCd. As shown in the figure, the notification store screen SCd displays the names of stores detected from the store list 52, that is, the names of member stores that are favorite stores and currently have one or more active notification items, in order. A soft key for the close button BTh is also displayed. Furthermore, the number of distributed data items n, i.e., the number of currently active notification items, is displayed for each store name, for example, by a circled number.

A user who has viewed the Store Notifications screen (SCd) can touch the store name of their favorite store to view its notification information. To close the Store Notifications screen (SCd), the user touches the close button (BTh).

Let's return to the explanation of Figure 13.
The processor 41, which controls the display of the notification store screen SCd, waits for either the close button BTh to be input as ACT 63, or for one of the store names to be selected as ACT 64. If a store name is selected during the waiting state of ACT 63 or ACT 64, the processor 41 proceeds to ACT 65. The processor 41 controls the wireless unit 46 to send a notification request command as ACT 65. This control causes the notification request command to be transmitted wirelessly from the wireless unit 46. The notification request command is sent to the support server 11 via the network 30, which uses the mobile phone communication network as the access network. The notification request command includes the member ID and the store ID of the affiliated store of the selected store name.

Upon receiving the notification request command, the processor 111 of the support server 11 begins the information processing procedure shown in the flowchart in Figure 23, which is the so-called notification request command reception processing. The processor 111 obtains the member ID and store ID from the notification request command as ACT 281. Hereafter, the member ID obtained from the notification request command will be referred to as the "obtained member ID." Similarly, the store ID obtained from the notification request command will be referred to as the "obtained store ID."

Processor 111 resets the count counter r to "0" as ACT 282. Processor 41 detects the distribution data 161 stored in the distribution data file 16 as ACT 283. Then, processor 111 confirms whether or not the distribution data 161 was detected as ACT 284.

If no undetected distribution data 161 is stored in the distribution data file 16, distribution data 161 cannot be detected. If undetected distribution data 161 is stored in the distribution data file 16 and it can be detected, the processor 111 proceeds from ACT 284 to ACT 285. Hereinafter, the detected distribution data 161 will be referred to as detected distribution data 161. As ACT 285, the processor 111 checks whether the store ID of the detected distribution data 161 matches the acquired store ID. If the two store IDs do not match, the processor 111 returns to ACT 283. The processor 41 detects the undetected distribution data 161 from the distribution data file 16.

If the store ID of the detected distribution data 161 matches the acquired store ID, processor 111 proceeds to ACT 286. Processor 111 checks the distribution flag Fb of the detected distribution data 161 as ACT 286. If the distribution flag Fb is "0", meaning the detected distribution data 161 contains notice information outside the distribution period, processor 111 returns to ACT 283. Processor 41 detects undetected distribution data 161 from the distribution data file 16.

If the distribution flag Fb of the detected distribution data 161 is "1," meaning the detected distribution data 161 contains notification information within the distribution period, the processor 111 proceeds to ACT 287. As ACT 287, the processor 111 stores the detected distribution data in a temporary memory area. The processor 111 also increments the count counter r by "1" as ACT 288. The temporary memory area is, for example, a part of the volatile memory area of the main memory 112. Afterward, the processor 111 returns to ACT 283. The processor 41 detects undetected distribution data 161 from the distribution data file 16.

Thus, each time the processor 111 detects a distribution data 161 from the distribution data file 16, it repeatedly executes the processes of ACT 285 to ACT 288. Once all distribution data 161 has been detected, the processor 111 proceeds to ACT 284 to ACT 289. As ACT 289, the processor 111 controls the communication interface 115 to send a response command to the information terminal 40, the source of the notification request command. The response command includes r entries of detected distribution data 161 stored in the temporary memory area. With this, the processor 111 terminates the notification request command reception process. The detected distribution data 161 stored in the temporary memory area is cleared after the processing of ACT 290.

Let's return to the explanation of Figure 13.
The processor 41 of the information terminal 40 that sent the notification request command is waiting for a response command as ACT 66. When it receives a response command from the store server 21, the processor 41 stores the notification information for r items of detection and distribution data included in the response command in area 424 as ACT 67. Then, the processor 41 displays the notification screen SCe (see Figure 31) on the touch panel 44 as ACT 68.

Figure 31 is a schematic diagram showing an example of the display of the notification screen SCe. As shown in the figure, the notification screen SCe displays the store name selected on the notification store screen SCd and the text of the notification information stored in area 424. A close button BTi is also displayed. Furthermore, the notification screen SCe displays the number of detected and distributed data items r in a circled number along with the store name. This number r matches the circled number displayed in association with the store name selected on the notification store screen SCd.

Let's return to the explanation of Figure 13.
The processor 41 of the information terminal 40, which is displaying the notification screen SCe, waits for the close button BTi to be input as ACT 69. When the close button BTi is input, the processor 41 proceeds to ACT 70. As ACT 70, the processor 41 clears the notification information stored in area 424. After that, the processor 41 returns to ACT 62. That is, the processor 41 returns the screen of the touch panel 44 from the notification screen SCe to the notification store screen SCd. Then the processor 41 enters a waiting state for ACTs 63 and 64.

If the close button BTh of the notification store screen SCd is pressed while ACT63 and ACT64 are in standby mode, the processor 41 returns to the standby mode of ACT12 and ACT13 as shown in Figure 9.

Here, the processor 41 realizes the function of a notification unit 416 by executing the processes of ACT 61 to ACT 65 in Figure 13. The processor 41 also realizes the function of a second acquisition unit 413 by executing the processes of ACT 66 and ACT 67. Furthermore, the processor 41 realizes the function of an output unit 415 by working in cooperation with the touch panel 44 to execute the process of ACT 68 in Figure 13.

Thus, when a user of the information terminal 40 presses the notification button BTd on the top screen SCa, the touch panel 44 displays the notification store screen SCd. This notification store screen SCd allows the user to see the number of currently active notification messages for each of the participating stores they have set as their favorite stores.

Furthermore, when a user touches any of the store names displayed on the notification store screen SCd, the touch panel 44 screen changes to the notification screen SCe. This notification store screen SCd allows the user to see the currently valid notification information held by the selected store's affiliated store. Therefore, with simple operation, the user can check the currently valid notification information for each of their favorite stores. Thus, the user can obtain information related to sales promotions, such as information on special offers, new products, campaigns, and time-limited sales, in advance, and decide which store to go shopping at.

Now, the user, having arrived at their favorite store, presses the "Start Shopping" button BTa on the top screen SCa. Upon receiving the "Start Shopping" button BTa, the processor 41 of the information terminal 40 proceeds from ACT21 in Figure 10 to ACT71 in Figure 14. The processor 41 then uses the touch panel 44 screen as the reading screen SCf (see Figure 32).

Figure 32 is a schematic diagram showing an example of the display of the reading screen SCf. As shown in the figure, the reading screen SCf includes guidance for scanning the entry code, along with a frame CM indicating the code reading area. The entry code is provided, for example, at the entrance of the store. The entry code is a two-dimensional code system that encodes the store's configuration information. The configuration information includes the store ID, in-store LAN data, mobile communication data, etc. The in-store LAN data includes the SSID, password, security information, etc., necessary for the information terminal 40 to connect to the access point 27 using wireless LAN. The mobile communication data includes the timeout period, number of retries, etc., necessary for the information terminal 40 to communicate with each device of the self-service product registration system 100.

When a user holds the camera 45 of the information terminal 40 over the entry code so that it fits within the frame CM of the reading screen SCf, the camera 45 reads the entry code. This operation of holding the camera 45 of the information terminal 40 over the entry code is called a check-in operation. After confirming the reading screen SCf, the user performs the check-in operation before starting their shopping.

The processor 41 of the information terminal 40, displaying the reading screen SCf, waits for a check-in operation as ACT 72. When a check-in operation is performed and the entry code is read by the camera 45, the processor 41 proceeds to ACT 73. The processor 41 controls the wireless unit 46 to send a check-in request command as ACT 73. This control causes the wireless unit 46 to connect to the access point 27 via wireless LAN based on the in-store LAN data obtained from the entry code. After connecting to the access point 27, the wireless unit 46 wirelessly transmits the check-in request command. The check-in request command is received by the access point 27 and transmitted to the support server 11 via the router 26 of the POS system 20. The check-in request command includes the member ID set in the information terminal 40. The store ID obtained from the entry code is also included in the check-in request command.

Upon receiving a check-in request command, the processor 111 of the support server 11 begins the information processing procedure shown in the flowchart of Figure 24, which is the so-called check-in request command reception processing. Processor 111 obtains the member ID from the check-in request command as ACT 301. Processor 111 also obtains the store ID from the check-in request command as ACT 302. Then, as ACT 303, processor 111 creates a new transaction file 51 in main memory 112 and saves the member ID and store ID obtained from the check-in request command. After that, as ACT 304, processor 111 sends an acceptance response command to the information terminal 40 that sent the check-in request command. With this, processor 111 completes the check-in request processing.

Returning to the explanation of Figure 14.
The processor 41, which controlled the transmission of the check-in request command, waits for an acceptance response command as ACT 74. Upon receiving the acceptance response command via the wireless unit 46, the processor 41 proceeds to ACT 75. As ACT 75, the processor 41 sets the screen of the touch panel 44 to the registration screen SCg (see Figure 33).

Next, processor 41 retrieves the store ID obtained from the entry code as ACT 76. Then, as ACT 77, processor 41 searches the store list 52 stored in area 421 and checks whether the favorite flag Fc associated with the store ID obtained from the entry code is "1". If the favorite flag Fc is "1", meaning the entered store is the user's favorite store, processor 41 proceeds to ACT 78. As ACT 78, processor 41 searches the store list 52 and checks whether the number of distribution data n associated with the store ID obtained from the entry code is "1" or greater.

If the favorite flag Fc associated with the store ID obtained from the entry code is "1" and the number of distributed data n is "1" or greater, the processor 41 proceeds to ACT 79. As ACT 79, the processor 41 adds the notification button BTj (see Figure 33) soft key to the registration screen SCg. If the favorite flag Fc associated with the store ID obtained from the entry code is "0", or if the number of distributed data n is "0", the processor 41 skips the ACT 79 process. Therefore, the notification button BTj soft key is not added to the registration screen SCg.

Figure 33 is a schematic diagram showing one example of the display of the registration screen SCg with the addition of a notification button BTj soft key. As shown in the figure, the registration screen SCg includes, in addition to the notification button BTj, a scan button BTk, a barcode-less button BTm, and a payment button BTn. Furthermore, the registration screen SCg is divided into two sections: a total transaction display section ARa and a detailed list display section ARb. The detailed list display section ARb is divided into, for example, five detail areas, and can display information related to up to five purchased items, such as product name, tax category, sales amount, and number of items sold. If there are more than six purchased items, the product names, etc., will be removed from the detailed list display section ARb in order of oldest registered items. However, by swiping the detailed list display section ARb up or down, information related to older registered purchased items can be displayed in the detailed list display section ARb. The sales amount is calculated by multiplying the price by the number of items sold.

The Notification button BTj is an operator that instructs the user to check notification information. The Scan button BTk is an operator that instructs the user to scan the barcode attached to the product. The No Barcode button BTm is an operator that instructs the user to register a product that does not have a barcode. The Payment button BTn is an operator that instructs the user to pay the transaction price.

After confirming the registration screen SCg, the user of the information terminal 40 begins shopping. Upon finding a product to purchase in the store, the user checks whether the product has a barcode. If the product has a barcode, the user touches the scan button BTk. Touching the scan button BTk changes the touch panel 44 screen to the scan screen. The scan screen is a screen with a frame indicating the barcode reading area. The user holds the camera 45 of the information terminal 40 over the product so that the barcode is within the frame. The barcode is then read by the reading unit of the information terminal 40. Thus, the registration operation for the barcoded product is completed.

On the other hand, if the purchased item does not have a barcode, the user touches the "No Barcode" button BTm. Touching the BTm button displays a list of items without barcodes on the touch panel 44. The user then selects the item they wish to purchase from the list. This registers the item without a barcode.

Furthermore, if the user wishes to check notification information during their shopping, they should touch the notification button BTj. When they have finished shopping and are ready to proceed to checkout, they should touch the payment button BTn.

Returning to the explanation of Figure 14.
The processor 41 of the information terminal 40 displaying the registration screen SCg waits for a product registration operation to be performed by touching the scan button BTk or the no-barcode button BTm as ACT 80, or by touching the payment button BTn as ACT 81, or by touching the notification button BTj as ACT 82. If the processing of ACT 79 is skipped and the notification button BTj has not been added to the registration screen SCg, the processing of ACT 82 is omitted.

When the aforementioned product registration operation is performed, the product code is entered into the information terminal 40. Upon receiving the product code, the processor 41 proceeds to ACT 91 in Figure 15. The processor 41 controls the wireless unit 46 to send a registration request command as ACT 91. This control causes the wireless unit 46 to wirelessly transmit the registration request command. The registration request command is received by the access point 27 and transmitted to the support server 11 via the router 26 of the POS system 20. The registration request command includes the product code, which is the identification information for the purchased product. The registration request command also includes the member ID.

Upon receiving the registration request command, the processor 111 of the support server 11 begins the information processing procedure shown in the flowchart of Figure 25, which is the so-called registration request command reception processing. The processor 111 obtains the member ID from the registration request command as ACT 311. Then, as ACT 312, the processor 111 selects the transaction file 51 in which the member ID is stored. Hereafter, the selected transaction file will be referred to as the target transaction file 51.

Processor 111 retrieves the product code of the purchased product included in the registration request command as ACT 313. Then, as ACT 314, processor 111 retrieves product data, including the pre-set price associated with that product code. As ACT 315, processor 111 creates product detail data based on the product data and saves it to the target transaction file 51. At this time, processor 111 increments the number of detail data entries m in the target transaction file 51 by "1" and calculates the total number of items and the total amount.

After completing ACT315, processor 111 sends an acceptance response command as ACT316 to the information terminal 40 that sent the registration request command. The acceptance response command includes product detail data for several m items stored in the target transaction file 51, along with the total number of items and the total amount. With this, processor 111 completes the information processing for when it received the registration request command.

Let's return to the explanation of Figure 15.
The processor 41, which controlled the transmission of the registration request command, waits for the acceptance response command as ACT 92. Upon receiving the acceptance response command via the wireless unit 46, the processor 41 proceeds to ACT 93. As ACT 93, the processor 41 updates the registration screen SCg with the product detail data, total points, total amount, etc., for several m items of detail data included in the acceptance response command. Specifically, the processor 41 displays the total points and total amount in the total display unit ARa. The processor 41 also displays the product name, tax category, sales amount, number of items sold, etc., of the purchased products in each detail area of the detail list display unit ARb. After finishing updating the registration screen SCg, the processor 41 returns to ACT 77 in Figure 14. The processor 41 then executes the processing from ACT 77 onward in the same manner as described above.

In the waiting states of ACT 80, ACT 81, and ACT 82 in Figure 14, if the payment button BTn is pressed, the processor 41 proceeds to ACT 101 in Figure 16. The processor 41 controls the wireless unit 46 to perform a payment request as ACT 101. This control causes the wireless unit 46 to wirelessly transmit a payment request command. The payment request command is received by the access point 27 and transmitted to the support server 11 via the router 26 of the POS system 20. The payment request command includes the member ID.

Upon receiving a payment request command, the processor 111 of the support server 11 begins the information processing procedure shown in the flowchart of Figure 26, which is the so-called payment request command reception processing. The processor 111 obtains the member ID from the payment request command as ACT 321. Then, as ACT 322, the processor 111 selects the target transaction file 51 where the member ID is stored. The processor 111 creates a unique accounting code as ACT 323. Then, as ACT 324, the processor 111 saves this accounting code to the target transaction file 51. Afterward, as ACT 325, the processor 111 sends an acceptance response command to the information terminal 40 that sent the payment request command. The acceptance response command includes the accounting code.

Let's return to the explanation of Figure 16.
The processor 41, which controls the transmission of the payment request command, waits for an acceptance response command as ACT 102. Upon receiving an acceptance response command via the wireless unit 46, the processor 41 proceeds to ACT 103. The processor 41 then sets the screen of the touch panel 44 to the accounting screen SCh (see Figure 34) as ACT 013.

Figure 34 is a schematic diagram showing one example of the accounting screen SCh. As shown in the diagram, the accounting code included in the acceptance response command is displayed as barcode BC on the accounting screen SCh. A back button BTp is also located on the screen.

The customer, after viewing the payment screen SCh, scans the barcode BC on the payment screen SCh using the scanner on the dedicated payment machine 24. A payment command is then sent from the dedicated payment machine 24 to the support server 11. The payment command includes the data from barcode BC, i.e., the payment code.

Upon receiving the payment command, the processor 111 of the support server 11 retrieves the accounting code from the payment command. The processor 111 then sends the data from the transaction file 51 containing the accounting code to the dedicated accounting machine 24, the source of the payment command. This displays the transaction details on the dedicated accounting machine 24's display, allowing the user at the information terminal to confirm the details and then pay the amount due. Once payment is complete, the dedicated accounting machine 24 sends a payment completion command to the support server.

The processor 111, having transmitted the data from transaction file 51 to the dedicated accounting machine 24, awaits a settlement completion command. Upon receiving the settlement completion command, the processor 111 sends a settlement termination command to the information terminal 40, which contains the member ID from transaction file 51.

Let's return to the explanation of Figure 16.
The processor 41 of the information terminal 40 displaying the accounting screen SCh waits for a settlement completion command as ACT 104. Upon receiving the settlement completion command via the wireless unit 46, the processor 41 proceeds to ACT 105. The processor 41 clears the accounting screen SCh as ACT 105. After that, the processor 41 returns to ACT 5 in Figure 9. Then the processor 41 executes the processing from ACT 5 onward in the same manner as described above.

In the standby states of ACT80, ACT81, and ACT82 in Figure 14, if the notification button BTj is pressed, the processor 41 proceeds to ACT111 in Figure 17. The processor 41 controls the wireless unit 46 to send a notification request command as ACT111. This control causes the wireless unit 46 to wirelessly transmit the notification request command. The notification request command is received by the access point 27 and transmitted to the support server 11 via the router 26 of the POS system 20. The notification request command includes the member ID set in the information terminal 40. The store ID obtained from the entry code is also included in the notification request command.

Upon receiving the notification request command, the processor 111 of the support server 11 executes the notification request command reception processing shown in the flowchart of Figure 23, as described above. Specifically, the processor 111 obtains the member ID and store ID from the notification request command. The processor 111 then detects distribution data 161 from the distribution data file 16 where the store ID matches the store ID obtained from the notification request command and the distribution flag Fb is "1". The processor 111 then controls the communication interface 115 to send a response command containing the detected distribution data 161 to the information terminal 40 that sent the notification request command.

Returning to the explanation of Figure 17.
The processor 41 of the information terminal 40 that sent the notification request command is waiting for a response command as ACT 112. When it receives a response command from the store server 21, the processor 41 stores the notification information of the distribution data 161 included in the response command in area 424 as ACT 113. Then, the processor 41 displays the notification screen SCe (see Figure 31) on the touch panel 44 as ACT 114.

The processor 41 of the information terminal 40, which is displaying the notification screen SCe, waits for the input of the close button BTh as ACT 115. When the close button BTh is input, the processor 41 proceeds to ACT 116. The processor 41 clears the notification screen SCe as ACT 116. Afterward, the processor 41 returns to ACT 77 in Figure 14. The processor 41 executes the processing from ACT 77 onward in the same manner as described above.

Here, the processor 41 implements the functions of the identification unit 417 by executing the processes of ACT 71 to ACT 76 in Figure 14. The processor 41 also implements the functions of the notification unit 416 by executing the processes of ACT 77 to ACT 79 in Figure 14 and the process of ACT 111 in Figure 17, which notifies the support server 11 of the favorite store if the store identified by the identification unit 417 is a favorite store. Furthermore, the processor 41 implements the functions of the second acquisition unit 413 by executing the processes of ACT 112 and ACT 113 in Figure 17, which retrieves currently valid notification information from the support server among the notification information of the favorite store notified by the notification unit 416. Finally, the processor 41, in cooperation with the touch panel 44, implements the functions of the output unit 415 by executing the process of ACT 114 in Figure 17, which outputs the information acquired by the second acquisition unit 413.

Thus, when a user of the information terminal 40 visits a participating store and performs a check-in operation, the registration screen SCg is displayed on the touch panel. At this time, if the store is a favorite store and has currently valid notification information, the notification button BTj is displayed on the registration screen SCg. Therefore, the user can easily know that the favorite store they have entered has currently valid notification information because the notification button BTj is displayed on the registration screen SCg.

When the user touches the notification button BTj, a notification screen SCe, displaying currently valid notification information, is displayed on the touch panel 44. The notification information displayed on this notification screen SCe is from the affiliated store the user is currently in. Therefore, the user can easily check currently valid notification information at the affiliated store they are visiting. As a result, they can obtain promotional information such as information on special offers, new products, campaigns, and time-limited sales in real time, which increases the user's purchasing intent and, consequently, enhances the store's sales promotion effectiveness.

[Variations]
The above embodiment illustrates how to remove a favorite store from the favorites screen SCc. The method for removing a favorite store is not limited to this. For example, on the merchant list screen SCb, touch the store name displayed together with the mark MAa. This merchant is a favorite store. When the store name displayed together with the mark MAa is selected by touch, the processor 41 controls the wireless unit 46 to send a removal notification command. By adopting this configuration, the favorite store can be removed from the merchant list screen SCb.

The notification information is not limited to promotional information. For example, information regarding the stock availability of products searched by category, or information regarding the retrieval of pre-ordered products, may be notified to the user of the information terminal 40 as notification information.

The list of affiliated stores displayed on the affiliated store list screen SCb does not necessarily have to be a list of all stores stored in the store data file 15. For example, it could be a list of affiliated stores located near the user using the GPS function of the information terminal 40, or a list of affiliated stores found through keyboard search.

You could also make it so that touching the notification information displayed on the notification screen (SCe) displays more detailed information. For example, if the notification information displayed on the notification screen (SCe) is "New products have arrived," touching this notification information could display a list of the newly arrived products.

In the above embodiment, an example was given where, within the store, the information terminal 40 connects to the store network 25 via the access point 27, and further communicates with the support server 11 of the server system 10 via the communication network 30. However, even within the store, the information terminal 40 may communicate directly with the support server 11 via the communication network 30.

In addition, several embodiments of the present invention have been described, but these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be carried out in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their variations are included within the scope of the invention, as well as within the scope of the invention and its equivalents as described in the claims.
The invention described in the original claims of this application is listed below.
[1] A portable information terminal for a user to self-input data necessary for registering purchased products at a store, comprising: a setting unit for setting the user's favorite store from among multiple stores; a first acquisition unit for wirelessly acquiring data from a server indicating whether or not each of the multiple stores has information that should be notified to the consumer; and a notification unit for notifying the user's favorite store if, based on the data acquired by the first acquisition unit, the store has information that should be notified to the consumer.
[2] An information terminal as described in Appendix [1], further comprising: a second acquisition unit that wirelessly acquires information that the user's favorite stores have that should be notified to the consumer from the server; and an output unit that outputs the information acquired by the second acquisition unit.
[3] An information terminal as described in Appendix [2], further comprising: a notification unit that notifies the server of a favorite store designated by the user from among the favorite stores that the notification unit has notified that have information to be notified to the consumer, the second acquisition unit that acquires from the server the information to be notified to the consumer that the favorite store notified by the notification unit has.
[4] An information terminal as described in Appendix [3], further comprising an identification unit that identifies the store entered by the user, and the notification unit further notifies the server of the favorite store if the store identified by the identification unit is the favorite store.
[5] The notification unit is an information terminal according to any one of the appendices [1] to [4], which notifies whenever information that the user's favorite store has that should be notified to the consumer is updated.
[6] A program to cause a portable information terminal computer, which allows a user to self-input data necessary for registering purchased items at a store, to function as a setting means for setting a user's favorite store from among multiple stores, a first acquisition means for wirelessly acquiring data from a server indicating whether or not each of the multiple stores has information that should be notified to the consumer, and a notification means for notifying the user's favorite store if, based on the data acquired by the first acquisition means, the store has information that should be notified to the consumer.

10...Server system, 11...Support server, 14...Member data file, 15...Store data file, 16...Distribution data file, 20...POS system, 21...Store server,
22... Monitoring terminal, 23... POS terminal, 24... Dedicated accounting machine, 27... Access point, 30... Network, 40... Information terminal, 41... Processor, 42... Internal memory, 43... External memory, 44... Touch panel, 45... Camera, 46... Wireless unit, 47... System transmission path, 51... Transaction file, 52... Store list, 100... Self-service product registration system, 411... Setting unit, 412... First acquisition unit, 413... Second acquisition unit, 414... Notification unit, 415... Output unit, 416... Notification unit, 417... Identification unit.

Claims (7)

A portable information terminal for users to self-enter data necessary for registering purchased items in a store,
A settings section where the user can select their favorite store from among multiple stores,
A first acquisition unit acquires data from a server via wireless communication that indicates whether or not each of the aforementioned multiple stores has information that should be notified to consumers.
A display control unit that displays a screen on a display device which has a first operator for confirming information that the user's favorite store should notify the consumer of,
Based on the data acquired by the first acquisition unit, if the user's favorite store has information that should be notified to the consumer , the notification unit notifies by displaying the number of pieces of information to be notified on the first operator ;
An information terminal equipped with the following features. The information terminal according to claim 1, wherein the display control unit displays a second operator for deselecting the user's favorite stores on the display device, together with the first operator on the same screen. A second acquisition unit acquires information that the user's favorite store should notify the consumer from the server via wireless communication,
An output unit that outputs the information acquired by the second acquisition unit,
The information terminal according to claim 1, further comprising: The system further comprises a notification unit that notifies the server of the favorite stores designated by the user from among the favorite stores that the notification unit has notified the consumer that they have information to be notified to the consumer,
The information terminal according to claim 3 , wherein the second acquisition unit acquires from the server information that the favorite store, notified by the notification unit, has to notify the consumer. A special unit that identifies the store that the aforementioned user entered,
Furthermore, it is equipped with,
The information terminal according to claim 4 , wherein the notification unit further notifies the server of the favorite store if the store identified by the identification unit is the favorite store. The information terminal according to any one of claims 1 to 5 , wherein the notification unit notifies whenever information that the user's favorite store has to notify the consumer is updated. A portable information terminal computer that allows users to self-enter data necessary for registering purchased items in stores.
A setting method for users to select their favorite store from among multiple stores.
A first acquisition means that acquires data from a server via wireless communication indicating whether or not each of the aforementioned multiple stores has information that should be notified to consumers.
A display control means that causes a display device to display a screen on which a first operator is placed for confirming information that the user's favorite store should notify the consumer of, and
A notification means that, based on the data acquired by the first acquisition means, notifies the user if their favorite store has information that should be notified to the consumer by displaying the number of pieces of information to be notified on the first operator .
A program designed to function as such.