Information providing device and information processing program

Abstract

To reduce a trouble of a customer for confirming a transaction history.SOLUTION: An information providing device of an embodiment includes collecting means, acquiring means, generating means, and output means. The collecting means collects electronic receipt data including an identifier of a product that has been a target of a performed transaction from a plurality of data management devices. The acquiring means acquires an identifier. The generating means generates historical data representing a transaction history of the product identified by the identifier acquired by the acquiring means based on the electronic receipt data collected by the collecting means. The output means outputs the historical data generated by the generating means.SELECTED DRAWING: Figure 5

Description

[Technical Field]

[0001] An embodiment of the present invention is an information providing device and Information Processing Program Mu Regarding. [Background technology]

[0002] Electronic receipt services that allow customers to view electronic receipt data, which is the digitization of receipts for transactions such as product sales, are already available. However, such electronic receipt services are provided individually by multiple service providers. The electronic receipt service that is applied is generally determined by the circumstances of the retailer, etc., and customers cannot generally choose which service to use.

[0003] For example, Electronic Receipt Service A applies to transactions with Retailer X, which is a member of Electronic Receipt Service A, and Electronic Receipt Service B applies to transactions with Retailer Y, which is a member of Electronic Receipt Service B. In this case, a customer who uses both Retailer X and Retailer Y must use both Electronic Receipt Service A and Electronic Receipt Service B. If a customer wants to check their past purchase history when repurchasing a product that they have previously purchased from both Retailer X and Retailer Y, they must check the purchase history in both Electronic Receipt Service A and Electronic Receipt Service B. This has caused a lot of work for customers to check their purchase history. Given these circumstances, it was desirable to reduce the effort required for customers to check their transaction history. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2016-218835 Summary of the Invention [Problem to be solved by the invention]

[0005] The problem to be solved by the present invention is to provide an information providing device that can reduce the effort required for customers to check their transaction history. and Information Processing Program M The purpose is to provide. [Means for solving the problem]

[0006] The information providing device of the embodiment includes a collection means, an acquisition means, a generation means, and , determination means, first display means and an output means. The collection means collects electronic receipt data including identifiers of products that have been the subject of completed transactions from a plurality of data management devices. The acquisition means acquires the identifiers. The generation means generates history data representing transaction histories of products identified by the identifiers acquired by the acquisition means based on the electronic receipt data collected by the collection means. The determination means determines whether the identifier acquired by the acquisition means belongs to a special identifier that can be used to identify different products in a plurality of stores. The first display means displays a store selection screen on the display device when the determination means determines that the identifier belongs to a special identifier. The output means outputs the history data generated by the generation means. The generating means further generates history data to represent a transaction history at a store selected by the user via the store selection screen. [Brief explanation of the drawings]

[0007] [Figure 1] FIG. 2 is a block diagram showing a main circuit configuration of an information providing device according to an embodiment. [Figure 2] FIG. 2 is a diagram schematically showing the structure of a data record included in the management database in FIG. 1. [Figure 3] FIG. 2 is a diagram schematically showing the structure of a data record contained in the history database in FIG. 1. [Figure 4] 10 is a flowchart of a receipt client process. [Figure 5] 10 is a flowchart of a receipt client process. [Figure 6] FIG. 10 is a diagram showing an example of a designation screen. [Figure 7] FIG. 10 is a diagram showing an example of a purchase history screen. DETAILED DESCRIPTION OF THE INVENTION

[0008] An information providing device according to an embodiment will be described below with reference to the accompanying drawings. FIG. 1 is a block diagram showing the main circuit configuration of an information providing device 10 according to this embodiment. The information providing device 10 provides the purchase history of a specified product based on electronic receipt data collected from a plurality of receipt servers 20 via a communication network 30.

[0009] The receipt server 20 acquires transaction data representing transaction details managed by the POS system 40 via the communication network 30 and stores electronic receipt data based on the transaction data. For each transaction, the electronic receipt data indicates the product code, quantity, unit price, etc. for each product involved in the transaction. The product code is an identifier assigned to each product to identify it. Multiple receipt servers 20 are operated by different service providers. Each of the multiple receipt servers 20 provides a different electronic receipt service. The receipt server 20 may also collect and store electronic receipt data generated by the POS system 40. Thus, the receipt server 20 is an example of a data management device that manages electronic receipt data including the identifiers of products involved in completed transactions.

[0010] The communication network 30 can be the Internet, a virtual private network (VPN), a local area network (LAN), a public communication network, a mobile communication network, or the like, either alone or in appropriate combination. Note that, for example, a mobile communication network and the Internet are used for communication between the information providing device 10 and the receipt server 20, and the Internet or a VPN is used for communication between the receipt server 20 and the POS system 40.

[0011] The POS system 40 performs processes such as registering transaction details such as product sales at a store and accounting. If the customer involved in the transaction is a user of an electronic receipt service, the POS system 40 sends transaction data indicating the details of the transaction to the receipt server 20. Multiple POS systems 40 each process transactions at different stores. The POS system 40 then obtains the transaction data from the receipt server 20 corresponding to the electronic receipt service to which the store is affiliated.

[0012] A portable information processing device such as a smartphone, a mobile phone, or a tablet terminal is typically used as the hardware of the information providing device 10. The information providing device 10 includes a processor 11, a main memory 12, an auxiliary storage unit 13, a touch panel 14, a camera 15, a communication interface 16, and a transmission path 17. The processor 11 is connected to the main memory 12, the auxiliary storage unit 13, the touch panel 14, the camera 15, and the communication interface 16 via the transmission path 17.

[0013] In the information providing device 10, the processor 11, main memory 12, and auxiliary storage unit 13 are connected via a transmission line 17 to form a computer that performs information processing to realize various functions of the information providing device 10.

[0014] The processor 11 corresponds to the central part of the computer and controls each part to realize various functions of the information providing device 10 in accordance with information processing programs such as an operating system, middleware, and application programs.

[0015] The main memory 12 corresponds to the main storage portion of the computer. The main memory 12 includes a nonvolatile memory area and a volatile memory area. The main memory 12 stores information processing programs in the nonvolatile memory area. The main memory 12 may also store data required for the processor 11 to execute processes for controlling each component in either the nonvolatile or volatile memory area. The main memory 12 uses the volatile memory area as a work area where data is rewritten by the processor 11 as needed.

[0016] The auxiliary storage unit 13 corresponds to the auxiliary storage portion of the computer. The auxiliary storage unit 13 is, for example, an EEPROM (electric erasable programmable read-only memory). A hard disk drive (HDD), a solid state drive (SSD), or the like may also be used as the auxiliary storage unit 13. The auxiliary storage unit 13 stores data used by the processor 11 when performing various processes and data generated by the processes in the processor 11. The auxiliary storage unit 13 stores an information processing program.

[0017] One of the information processing programs stored in the auxiliary storage unit 13 is an application program (hereinafter referred to as the receipt client app) APA for operation as a receipt client. However, the receipt client app APA is typically downloaded via the Internet, for example, in response to an operation by the user of the information providing device 10, and written to the auxiliary storage unit 13. In other words, when the information providing device 10 is transferred to its user, the receipt client app APA is not stored in the auxiliary storage unit 13. However, the information providing device 10 may also be transferred to the user of the information providing device 10 with the receipt client app APA stored in the auxiliary storage unit 13.

[0018] The touch panel 14 functions as an input device and a display device for the information providing device 10 . The camera 15 captures an image of an arbitrary subject and generates image data representing an image including the subject. As the camera 15, a well-known imaging device using a CMOS (complementary metal oxide semiconductor) image sensor or the like can be used.

[0019] The communication interface 16 is an interface for data communication via the communication network 30. As the communication interface 16, for example, a well-known communication device for performing data communication via a mobile communication network can be used. The transmission path 17 includes an address bus, a data bus, and control signal lines, and transmits data and control signals exchanged between the connected components.

[0020] A part of the storage area of ​​the auxiliary storage unit 13 is used as a management database DBA and a history database DBB. The management database DBA is a database for managing the electronic receipt service used by the user of the information providing device 10. The history database DBB is a database representing the product purchase history of the user of the information providing device 10. In other words, the auxiliary storage unit 13 is an example of a storage device that stores a database representing the transaction history.

[0021] FIG. 2 is a diagram showing a schematic structure of a data record DRA contained in the management database DBA. The management database DBA is a collection of data records DRA associated with multiple electronic receipt services provided by multiple receipt servers 20, respectively. The data record DRA includes fields FAA, FAB, FAC, FAD, and FAE. A service identifier for identifying the associated electronic receipt service is set in field FAA. A user identifier for identifying the user in the associated electronic receipt service is set in field FAB. A password determined for the user in the associated electronic receipt service is set in field FAC. Address data for accessing the receipt server 20 corresponding to the associated electronic receipt service is set in field FAD. The address data is, for example, a URL (uniform resource locator). The date and time of the latest download of electronic receipt data for the associated electronic receipt service is set in field FAE.

[0022] FIG. 3 is a diagram showing a typical structure of a data record DRB contained in the history database DBB. The history database DBB is a collection of data records DRB, each associated with a product. Data record DRB includes fields FBA and FBB. Data record DRB may include one or more fields starting with field FBC. Field FBA contains a product code for identifying the associated product. The product code is typically a JAN (Japanese article number) code or an in-store code. Field FBB contains detailed data. The detailed data is associated with a transaction involving the associated product and provides details about that transaction. The in-store code is a product code that can be used to identify different products in multiple stores, and is an example of a unique identifier.

[0023] In this embodiment, the detailed data includes fields FCA, FCB, FCC, and FCD. Field FCA is set with a store identifier for identifying the store where the associated transaction took place. Field FCB is set with data representing the date and time the associated transaction took place. Field FCC is set with a numerical value representing the transaction points for the associated transaction. Field FCD is set with a numerical value representing the unit price applied in the associated transaction.

[0024] Next, a description will be given of the operation of the information providing device 10 configured as above. Note that the content of the process described below is an example, and various processes that can obtain similar results can be used as appropriate.

[0025] A user installs the receipt client application APA on an information processing device such as a smartphone owned by the user, enabling the information processing device to function as the information providing device 10. The user also performs user registration for the electronic receipt services they wish to use from among the services provided by the multiple receipt servers 20. If the user intends to use multiple electronic receipt services, the user performs user registration for each of the multiple electronic receipt services. This user registration determines a user identifier for identifying the user on the receipt server 20, and associates a password with this user identifier. At least one of the user identifier and password may be specified by the user, or both may be determined by the receipt server 20 or the service provider.

[0026] The user registers the electronic receipt service to be used, as well as the user identifier and password for that electronic receipt service, as usage settings of the information providing device 10. In response to this registration operation, the processor 11 adds a new data record DRA to the management database DBA. The processor 11 sets the service identifier of the electronic receipt service designated by the user to be used in field FAA of the new data record DRA. This associates the new data record DRA with the electronic receipt service designated by the user. The processor 11 sets the user identifier and password designated by the user in fields FAB and FAC of the new data record DRA, respectively. The processor 11 sets the address of the receipt server 20 corresponding to the associated electronic receipt service in field FAD of the new data record DRA. The processor 11 sets invalid data, which is predetermined to not represent an actual date and time, in field FAE of the new data record DRA. The processor 11 may leave field FAE blank.

[0027] If a user uses multiple electronic receipt services, the user must register each of the multiple electronic receipt services. In this case, the management database DBA will contain multiple data records DRA associated with each of the multiple electronic receipt services.

[0028] When a user completes a transaction at a store that is a member of a registered electronic receipt service, transaction data is sent from the POS system 40 installed in the store to the receipt server 20 that supports the corresponding electronic receipt service. The receipt server 20 stores electronic receipt data based on the transaction data sent in this manner, in association with the user's user identifier. That is, the electronic receipt data is associated with a transaction and includes the store identifier of the store where the transaction took place and the transaction date and time. The electronic receipt data also includes information about the product that was the subject of the transaction, such as the product code, number of items, and unit price. When a user makes repeated transactions at stores that are members of a certain electronic receipt service, multiple pieces of electronic receipt data are stored in the receipt server 20 that supports that electronic receipt service, in association with the user identifier of the corresponding user. Typically, in an electronic receipt service, a user accesses the receipt server 20 from any information terminal, and a receipt screen showing details of each transaction is displayed on the information terminal, which the user can view.

[0029] When an instruction to execute an application based on the receipt client application APA is issued, the processor 11 of the information providing device 10 starts information processing based on the receipt client application APA (hereinafter referred to as receipt client processing). 4 and 5 are flowcharts of receipt client processing.

[0030] 4, the processor 11 displays a home screen on, for example, the touch panel 14. The home screen is a screen for starting operations of the various functions provided by the receipt client process.

[0031] In ACT2, the processor 11 checks whether the history inquiry mode has been designated. If the processor 11 cannot confirm that the designation has been made, it determines NO and proceeds to ACT3. In ACT3, the processor 11 checks whether or not another operation has been performed. If no valid operation has been performed, the processor 11 determines the answer as NO and returns to ACT2. Thus, in ACT2 and ACT3, processor 11 waits for some valid operation, including specifying the history inquiry mode. If some operation other than specifying the history inquiry mode is performed, processor 11 proceeds to processing for executing a function corresponding to that operation. The processing of processor 11 in this case is not a feature of this embodiment, so its description will be omitted. One example of processing in this case may be the processing for displaying a receipt screen showing details of each transaction, as described above.

[0032] For example, when a user is browsing products in a store and wants to check the purchase history of a certain product, the user performs a predetermined operation to activate the history inquiry mode, for example, on the touch panel 14. Note that this operation is, for example, tapping a soft key located on the home screen.

[0033] If the processor 11 confirms the above operation, it judges YES in ACT2 and proceeds to ACT4. In ACT4, the processor 11 downloads undownloaded electronic receipt data for one of the electronic receipt services registered in the information providing device 10. For example, the processor 11 selects one of the data records DRA included in the management database DBA. The processor 11 then sends a download request to the address set in field FAD of the selected data record DRA, along with notification of the user identifier, password, and date and time set in fields FAB, FAC, and FAE. Upon receiving this request, the receipt server 20 authenticates the user using the notified user identifier and password, and downloads electronic receipt data acquired for the user after the notified date and time to the information providing device 10. When the electronic receipt data is received via the communication interface 16 in the information providing device 10, the processor 11 stores the electronic receipt data in the main memory 12 or the auxiliary storage unit 13. As a result, electronic receipt data including identifiers of products that were the subject of completed transactions is collected from multiple receipt servers 20, each of which corresponds to a data management device. Thus, the processor 11 executes information processing based on the receipt client application APA, and the computer with the processor 11 as its central part functions as a collection means.

[0034] In ACT 5, processor 11 updates the management database to reflect this download. For example, processor 11 updates the date and time set in field FAE of the data record DRA selected in ACT 4 to indicate the most recent download date and time. For example, processor 11 rewrites field FAE to a number indicating the date and time the download was requested.

[0035] In ACT6, the processor 11 checks whether there is an electronic receipt service that has not yet been downloaded. For example, if the data records DRA included in the management database DBA include a data record DRA other than the data record DRA selected in ACT4, the processor 11 determines that the corresponding electronic receipt service is present and returns to ACT4, YES. The processor 11 then repeats ACT4 and ACT5 in the same manner as above. However, when executing ACT4 for the second or subsequent times, the processor 11 selects an electronic receipt service other than the one previously selected in ACT4.

[0036] Thus, the processor 11 downloads the undownloaded electronic receipt data for all registered electronic receipt services. After completing the download for all registered electronic receipt services, the processor 11 determines NO in ACT6 and proceeds to ACT7.

[0037] In ACT7, the processor 11 updates the history database DBB based on the currently downloaded electronic receipt data. For example, if the history database DBB does not contain a data record DRB in which the product code is set in field FBA for each product code included in the currently downloaded electronic receipt data, the processor 11 adds a new data record DRB to the history database DBB. The processor 11 sets the product code in field FBA of the new data record DRB and sets detailed data in field FBB. The processor 11 sets the store identifier and transaction date and time indicated in the corresponding electronic receipt data, and the number of items and unit price indicated in the corresponding electronic receipt data for the product code, in fields FCA to FCD of the detailed data, respectively. Furthermore, for example, if the history database DBB already contains a data record DRB in which the product code is set in field FBA for each product code included in the currently downloaded electronic receipt data, the processor 11 adds new detailed data to the data record DRB. The processor 11 then sets the store identifier and transaction date and time indicated in the electronic receipt data, and the number of items and unit price indicated in the electronic receipt data for the relevant product code, in the fields FCA to FCD of the new detailed data. Note that the processor 11 adds the detailed data to the data record DRB in order, starting with the oldest transaction date and time, for example. In this way, the processor 11 executes information processing based on the receipt client application APA, and the computer with the processor 11 as its central part functions as an update means.

[0038] The processor 11 as ACT8 displays a designation screen on, for example, the touch panel 14. The designation screen is a screen for allowing the user to designate a product for which history confirmation is to be performed. FIG. 6 is a diagram showing an example of the specification screen SCA. The specification screen SCA includes a display area ARAA, messages MEAA and MEAB, and a button BUAA. The display area ARAA displays the image obtained by the camera 15 with vertical and horizontal center lines superimposed on it. However, in FIG. 6, the image obtained by the camera 15 is not shown. The message MEAA is a text message that informs the user that the device is in an operating state for checking the product purchase history. The message MEAB is a text message that prompts the user to scan the barcode of the product whose purchase history is to be checked. The button BUAA is a soft key that the user uses to instruct the device to exit the history inquiry mode.

[0039] In ACT9, the processor 11 checks whether or not a product has been designated. If the processor 11 cannot confirm that the product has been designated, it determines NO and proceeds to ACT10. In ACT 10, the processor 11 checks whether an instruction to end the history inquiry mode has been issued. If the processor 11 cannot confirm that such an instruction has been issued, it determines that the answer is NO and returns to ACT 9. Thus, in ACT9 and ACT10, the processor 11 waits for a product to be specified or for an end instruction to be given.

[0040] The user specifies the product for which the purchase history is to be checked by a predetermined operation. For example, the user points the camera 15 at the product so that the barcode of the product is reflected in the display area ARAA. While the specification screen SCA is displayed, the processor 11 analyzes the image captured by the camera 15 and attempts to read the product code represented by the barcode. This barcode reading may be performed as a process based on the receipt client application APA, or as a process based on a separate application program for reading barcodes. If the product code is read, the processor 11 determines YES in ACT 9, assuming that the product identified by that product code has been specified, and proceeds to ACT 11. At this time, the processor 11 acquires the product code represented by the read barcode as the product identifier. Thus, by the processor 11 executing information processing based on the receipt client application APA, the computer, with the processor 11 as its core, functions as an acquisition means.

[0041] In ACT11, processor 11 checks whether there is a purchase history for the specified product. For example, processor 11 searches the history database DBB for a data record DRB in which the product code of the specified product is set in field FBA. If processor 11 cannot find the corresponding data record DRB, it determines NO and proceeds to ACT12. In ACT12, the processor 11 displays a non-purchase screen, for example, on the touch panel 14. The non-purchase screen is a predetermined screen for notifying the user that there is no purchase history. The non-purchase screen may be, for example, a screen that displays a text message indicating that there is no purchase history, instead of the message MEAA on the specified screen SCA. The processor 11 then returns to the standby state of ACT9 and ACT10.

[0042] If the processor 11 finds a data record DRB in which the product code of the specified product is set in the field FBA, it determines that there is a purchase history and determines YES in ACT 11, and proceeds to ACT 13 in FIG. In ACT 13, the processor 11 checks whether the product code of the specified product is an in-store code. If it is not an in-store code, the processor 11 determines NO and proceeds to ACT 14.

[0043] As ACT14, the processor 11 generates a purchase history screen and displays it on, for example, the touch panel 14. For example, the processor 11 selects one of all the detailed data contained in the data record DRB found as described above and generates a purchase history screen to display the data contained in the selected detailed data. For example, the processor 11 selects the detailed data set in the last field of the data record DRB. In this way, the detailed data related to the most recent transaction will be selected first. However, the processor 11 may also select the detailed data set in field FBB of the data record DRB. In this way, the detailed data related to the oldest transaction will be selected first. The processor 11 simply selects the detailed data that meets predetermined conditions. These conditions may be determined as appropriate by, for example, the creator of the receipt client application APA or the user.

[0044] Fig. 7 is a diagram showing an example of the purchase history screen SCB. In Fig. 7, the same display elements as those included in the specification screen SCA shown in Fig. 6 are denoted by the same reference numerals, and their description will be omitted. In this embodiment, the purchase history screen SCB includes a character string CSBA, a display area ARBA, and buttons BUBA and BUBB instead of the message MEAA on the specification screen SCA. The character string CSBA indicates the product name of the specified product. The display area ARBA indicates the data included in the detailed data. The buttons BUBA and BUBB are soft keys that allow the user to instruct the display of another purchase history.

[0045] In ACT 15, the processor 11 checks whether an instruction to change the purchase history to be displayed has been issued. If the processor 11 cannot confirm that such an instruction has been issued, it determines the answer as NO and proceeds to ACT 16. In ACT 16, the processor 11 checks whether or not a product has been designated. If the processor 11 cannot confirm that the product has been designated, it determines "NO" and proceeds to ACT 17. In ACT 17, the processor 11 checks whether an instruction to end the history inquiry mode has been issued. If the processor 11 cannot confirm that such an instruction has been issued, it determines that the answer is NO and returns to ACT 15. Thus, in ACT15 to ACT17, the processor 11 waits for an instruction to change or end the process, or for a product to be specified.

[0046] If the user wishes to check a purchase history other than the purchase history shown on the displayed purchase history screen, the user can instruct a change of the purchase history to be displayed by performing a predetermined operation, such as touching either the BUBA or BUBB button on the purchase history screen SCB. In response to this, the processor 11 determines YES in ACT15, executes ACT14 in the same manner as described above, and then returns to the standby state of ACT15 to ACT17. When the processor 11 executes ACT14 for the second or subsequent time, it selects detailed data different from the detailed data previously selected in ACT14 and updates the display area ARBA to display the data included in the selected detailed data. The conditions for the processor 11 to select new detailed data may be appropriately determined, for example, by the creator of the receipt client application APA or the user. For example, in response to touching the button BUBA, the processor 11 selects new detailed data set in the field immediately following the field in which the selected detailed data is set. In addition, in response to touching the button BUBB, the processor 11 selects new detailed data set in the field immediately preceding the field in which the selected detailed data is set. In this way, if the detailed data in the data record DRB is set in the earlier fields, the older the transaction date and time, as described above, the purchase history screen SCB is updated to display the purchase history in chronological order.

[0047] In this way, the data of the multiple purchase history screens SCB that represent the purchase history in chronological order corresponds to history data that represents the transaction history of the specified product. In other words, sequentially generating data that represents the purchase history screens SCB and sequentially displaying the purchase history screens SCB according to that data corresponds to generating and outputting purchase history data. Thus, by having the processor 11 execute information processing based on the receipt client application APA, the computer with the processor 11 as its central part functions as a generating means and an output means.

[0048] If the product code of the specified product is an in-store code, the processor 11 determines YES in ACT13 and proceeds to ACT18. In ACT18, the processor 11 displays a store selection screen, for example, on the touch panel 14. The store selection screen is a screen for allowing the user to select one of the stores from which the specified product has been purchased. For example, the processor 11 displays, as options on the store selection screen, the store names identified by the store identifiers set in field FCA of the detailed data included in the data record DRB in which the product code of the specified product is set in field FBA.

[0049] After the user selects the store for which the user wishes to check the purchase history from among the stores displayed as options on the store selection screen, the user performs a predetermined operation to specify the store. In ACT 19, processor 11 waits for a store to be specified. If a store has been specified as described above, processor 11 determines YES and proceeds to ACT 20. At this point, processor 11 has determined that the specified store is the store for which history is to be checked. Thus, by processor 11 executing information processing based on the receipt client application APA, the computer with processor 11 as its central part functions as a determination means.

[0050] In ACT 20, processor 11 narrows down the detailed data to be referenced for displaying the purchase history to only those related to the specified store. For example, processor 11 extracts detailed data in which the store identifier of the specified store is set in field FCA from the detailed data included in data record DRB in which the product code of the specified product is set in field FBA, and sets the corresponding detailed data as the detailed data to be referenced. In ACT21, the processor 11 generates the purchase history screen SCB in the same manner as in ACT14, and displays it on, for example, the touch panel 14. However, in ACT21, the processor 11 selects one of the detailed data narrowed down in ACT20.

[0051] In ACT 22, the processor 11 checks whether an instruction to change the purchase history to be displayed has been issued. If the processor 11 cannot confirm that such an instruction has been issued, it determines the answer as NO and proceeds to ACT 23. In ACT 23, the processor 11 checks whether or not a product has been designated. If the processor 11 cannot confirm that the product has been designated, it determines NO and proceeds to ACT 24. In ACT 24, the processor 11 checks whether an instruction to end the history inquiry mode has been issued. If the processor 11 cannot confirm that such an instruction has been issued, it determines the answer as NO and returns to ACT 22. Thus, in ACT22 to ACT24, the processor 11 waits for an instruction to change or end the process, or for a product to be specified.

[0052] When the user instructs to change the purchase history in the same manner as described above, the processor 11 determines YES in ACT 22, executes ACT 21, and then returns to the standby state of ACT 22 to ACT 24. When the processor 11 executes ACT 21 for the second or subsequent time, it selects detailed data different from the detailed data previously selected in ACT 14 from the detailed data narrowed down in ACT 20.

[0053] If the user wishes to check the purchase history of another product while the unpurchased screen is displayed, the user points camera 15 toward the product so that the product's barcode is reflected in the display area ARAA of the unpurchased screen. Processor 11 then determines YES in ACT9 in FIG. 4, as described above, and proceeds to ACT11. If the user wishes to check the purchase history of another product while the purchase history screen SCB is displayed, the user points camera 15 toward the product so that the product's barcode is reflected in the display area ARAA of the purchase history screen SCB. Processor 11 then determines YES in ACT16 or ACT23 in FIG. 5, and proceeds to ACT11 in FIG. 4. Processor 11 then executes ACT11 and subsequent steps in the same manner as described above. Processor 11 then displays the purchase history of the newly specified product.

[0054] Furthermore, when the user has finished checking the purchase history while the designated screen SCA, the unpurchased screen, or the purchase history screen SCB is displayed, the user instructs the end by performing a predetermined operation such as touching the button BUAA on each screen. If an end command is issued in this way, the processor 11 determines YES in ACT10 in FIG. 4 or ACT17 or ACT24 in FIG. 5, returns to ACT1 in FIG. 4, and executes ACT1 and subsequent steps in the same manner as described above.

[0055] As described above, the information providing device 10 displays a purchase history spanning multiple electronic receipt services, thereby reducing the effort required for the customer to check their transaction history.

[0056] Furthermore, the information providing device 10 successively updates the history database DBB stored in the auxiliary storage unit 13, and then displays the purchase history based on that history database DBB. This reduces the amount of transaction data collected for one update of the history database DBB, and shortens the processing time for updating the history database DBB and for displaying the purchase history based on the updated history database DBB.

[0057] Furthermore, when an in-store code is specified to identify a product, the information providing device 10 displays only the purchase history for the specified store. This prevents the display of a mixed purchase history even if the same in-store code is used to identify different products at multiple stores.

[0058] Furthermore, the information providing device 10 allows the user to easily check the purchase history by displaying it on the built-in display device.

[0059] This embodiment can be modified in various ways as follows. The transaction may take any form, such as the sale of goods to a customer in a store, the sale of goods to a customer by mail order, the provision of food, drink, etc. to be consumed by a customer in a store, or the provision of an intangible service to a customer.

[0060] The product code of the product to be displayed as a purchase history may be obtained by any method other than reading a barcode, such as by specifying the product code from a list of products with purchase history.

[0061] The collected electronic receipt data may be stored directly in the main memory 12 or the auxiliary storage unit 13, and a history screen may be generated from this electronic receipt data.

[0062] The electronic receipt data may be downloaded from the receipt server 20 each time the history inquiry mode is activated.

[0063] Instead of displaying the purchase history screen SCB, a purchase history screen showing a list of multiple purchase histories may be displayed.

[0064] The purchase history may be output by any method other than display, such as outputting a voice message, printing, or outputting data to another device.

[0065] When the product code of the specified product is an in-store code, the store to which the purchase history is to be provided may be determined by automatically determining the store the user is visiting using a known determination method, for example.

[0066] Some or all of the functions realized by the processor 11 through information processing can be realized by hardware that executes information processing not based on a program, such as a logic circuit, etc. Each of the above functions can also be realized by combining the above hardware, such as the logic circuit, with software control.

[0067] Although several embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be embodied 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 modifications are included within the scope and spirit of the invention, and are also included in the scope of the invention and its equivalents as defined in the claims. The inventions described in the original claims of this application are set forth below. [Appendix 1] A collection means for collecting electronic receipt data including identifiers of products that have been the subject of completed transactions from a plurality of data management devices; an acquisition means for acquiring the identifier; a generating means for generating history data representing a transaction history of the product identified by the identifier acquired by the acquiring means based on the electronic receipt data collected by the collecting means; an output means for outputting the history data generated by the generation means; An information providing device equipped with the above. [Supplementary Note 2] The collection unit repeatedly collects the electronic receipt data that has not yet been collected, a storage device that stores a database representing transaction histories for each of the products that have been the subject of transactions; an update unit that updates the database based on the electronic receipt data newly collected by the collection unit; Furthermore, the generating means generates the history data based on the database. 10. The information providing device according to claim 1. [Supplementary Note 3] The system further includes a determination unit that determines a store to be the target of history check when the identifier acquired by the acquisition unit belongs to a unique identifier that can be used to identify different products in a plurality of stores, If the identifier acquired by the acquisition means belongs to the special identifier, the generation means generates the history data as representing a transaction history at the store determined by the determination means. 10. The information providing device according to claim 1 or 2. [Appendix 4] Equipped with a display device, the output means causes the display device to display a screen based on the history data; 4. The information providing device according to any one of claims 1 to 3. [Appendix 5] A computer provided in an information processing device, a collection means for collecting electronic receipt data including identifiers of products that have been the subject of completed transactions from a plurality of data management devices; an acquisition means for acquiring the identifier; a generating means for generating history data representing a transaction history of the product identified by the identifier acquired by the acquiring means based on the electronic receipt data collected by the collecting means; an output means for outputting the history data generated by the generation means; An information processing program that makes it function as such. [Appendix 6] Collecting electronic receipt data including identifiers of products that have been the subject of transactions from multiple data management devices; obtaining the identifier; generating history data representing a transaction history of the product identified by the acquired identifier based on the collected electronic receipt data; outputting the generated history data; Information provision method. [Explanation of symbols]

[0068] 10...information providing device, 11...processor, 12...main memory, 13...auxiliary storage unit, 14...touch panel, 15...camera, 16...communication interface, 17...transmission path, 20...receipt server, 30...communication network, 40...POS system

Claims

1. a collection means for collecting electronic receipt data including identifiers of products that have been the subject of completed transactions from a plurality of data management devices; an acquisition means for acquiring the identifier; a generating means for generating history data representing a transaction history of the product identified by the identifier acquired by the acquiring means based on the electronic receipt data collected by the collecting means; a determination means for determining whether the identifier acquired by the acquisition means belongs to a unique identifier that can be used to identify different products in a plurality of stores; a first display means for displaying a store selection screen on a display device when the determination means determines that the identifier belongs to a special identifier; an output means for outputting the history data generated by the generation means; Equipped with the generating means generates the history data so as to represent a transaction history at a store selected by the user via the store selection screen. Information provision device.

2. The first display means displays, on the store selection screen, as options, store names of stores where the product identified by the identifier acquired by the acquisition means has been purchased. The information providing device according to claim 1 .

3. A second display means for displaying on the display device a purchase history screen showing the purchase history of a product identified by the identifier acquired by the acquisition means when the determination means does not determine that the product belongs to a special identifier; The information providing device according to claim 2 , further comprising:

4. A computer provided in an information providing device, a collection means for collecting electronic receipt data including identifiers of products that have been the subject of completed transactions from a plurality of data management devices; an acquisition means for acquiring the identifier; a generating means for generating history data representing a transaction history of the product identified by the identifier acquired by the acquiring means based on the electronic receipt data collected by the collecting means; a determination means for determining whether the identifier acquired by the acquisition means belongs to a unique identifier that can be used to identify different products in a plurality of stores; a first display means for displaying a store selection screen on a display device when the determination means determines that the identifier belongs to a special identifier; an output means for outputting the history data generated by the generation means; and make it work, Furthermore, the generation means generates the history data so as to represent a transaction history at a store selected by the user via the store selection screen. Information processing program.

5. The first display means displays, as options, on the store selection screen, store names of stores where the product identified by the identifier acquired by the acquisition means has been purchased. The information processing program according to claim 4.

6. The computer: a second display means for displaying, on the display device, a purchase history screen showing a purchase history of a product identified by the identifier acquired by the acquisition means, when the determination means does not determine that the product belongs to a special identifier; 6. The information processing program according to claim 5, further functioning as:

Images