JP7381662B1 - Receipt output system, receipt output method, and program - Google Patents

Abstract

[Challenge] Smooth the transition to electronic receipts. A transaction data acquisition unit (101) of a receipt output system (1) acquires transaction data regarding the details of transactions performed at a store. The electronic receipt data generation unit (102B) generates electronic receipt data regarding the electronic receipt of the transaction based on the transaction data. The paper receipt output unit (103A) outputs a paper receipt related to a transaction summary, including a code related to outputting an electronic receipt, based on the transaction data. The electronic receipt output unit (103B) outputs an electronic receipt based on the electronic receipt data when the code is read by the user terminal. [Selection diagram] Figure 5

Description

The present disclosure relates to a receipt output system, a receipt output method, and a program.

Conventionally, when a transaction is made at a store, it has been considered to output an electronic receipt instead of a paper receipt. For example, Patent Document 1 describes that an electronic receipt is output in place of a paper receipt to a user who requests issuance of an electronic receipt. For example, Patent Document 2 discloses that a store terminal eliminates the need for paper receipts by displaying a two-dimensional code based on identification data that can identify a transaction and transaction data that indicates the details of the transaction. is listed.

Japanese Patent Application Publication No. 2015-049525 Special Publication No. 2016-507819

However, users who are not accustomed to electronic receipts such as those disclosed in Patent Document 1 and Patent Document 2 may be confused because they cannot understand whether the transaction has been completed unless a physical paper receipt is output. This point is not limited to the electronic receipts of Patent Document 1 and Patent Document 2, but applies to electronic receipts in general. There is a need to make the transition to electronic receipts smooth so that users who are not used to electronic receipts are not confused.

One of the objectives of the present disclosure is to smooth the transition to electronic receipts.

A receipt output system according to the present disclosure includes a transaction data acquisition unit that acquires transaction data regarding the details of a transaction performed at a store, and an electronic receipt that generates electronic receipt data regarding an electronic receipt of the transaction based on the transaction data. a data generation unit; a paper receipt output unit that outputs a paper receipt related to a summary of the transaction including a code related to outputting the electronic receipt based on the transaction data; when the code is read by a user terminal; and an electronic receipt output unit that outputs the electronic receipt based on the electronic receipt data.

According to the present disclosure, the transition to electronic receipts becomes smooth.

FIG. 1 is a diagram showing an example of the overall configuration of a receipt output system. It is a diagram showing an example of how a user uses a store. It is a figure which shows an example of a summary receipt and a regular receipt. It is a figure showing an example of an electronic receipt screen. FIG. 2 is a diagram illustrating an example of functions realized by a receipt output system. FIG. 3 is a diagram showing an example of a user database. It is a diagram showing an example of a store database. FIG. 3 is a diagram illustrating an example of a process in which summary receipt data is generated by a summary receipt converter. FIG. 3 is a diagram illustrating an example of a process in which electronic receipt data is generated by an electronic receipt converter. FIG. 2 is a diagram illustrating an example of processing executed by the receipt output system. FIG. 2 is a diagram illustrating an example of processing executed by the receipt output system. It is a figure which shows an example of the function implement|achieved by the modification regarding the 1st structure. FIG. 7 is a diagram showing an example of a summary receipt of Modification 1-1. 7 is a diagram showing an example of a summary receipt of Modification 1-2. FIG. 7 is a diagram illustrating an example of a summary receipt of Modification 1-3. FIG. FIG. 3 is a diagram illustrating an example of how membership registration for a point service is prompted. It is a figure which shows an example of the function implement|achieved by the modification regarding the 2nd structure.

[1. Overall configuration of receipt output system]
An example of an embodiment according to the present disclosure will be described. In this embodiment, a receipt output system will be taken as an example. The receipt output system is an example of a benefit granting system in the second configuration described below. Therefore, in the second configuration described later, the part described as a receipt output system can be read as a privilege granting system.

FIG. 1 is a diagram showing an example of the overall configuration of a receipt output system. For example, the receipt output system 1 includes a server 10, a store terminal 20, and a user terminal 30. Each of the server 10, store terminal 20, and user terminal 30 can be connected to a network N such as the Internet or a LAN.

Server 10 is a server computer. For example, the server 10 includes a control section 11, a storage section 12, and a communication section 13. Control unit 11 includes at least one processor. The storage unit 12 includes volatile memory such as RAM and nonvolatile memory such as flash memory. The communication unit 13 includes at least one of a communication interface for wired communication and a communication interface for wireless communication.

The store terminal 20 is a store computer. In FIG. 1, only one store terminal 20 is shown, but in this embodiment, it is assumed that there are store terminals 20 for each of a plurality of stores. A store has at least one store terminal 20. Note that the receipt output system 1 may not be a system compatible with a plurality of stores, but may be a system compatible only with one specific store. In this case, the receipt output system 1 may include only one store terminal 20.

For example, the store terminal 20 is a POS (Point Of Sales) terminal, a personal computer, a tablet terminal, a smartphone, or a handy terminal. For example, the store terminal 20 includes a control section 21, a storage section 22, a communication section 23, an operation section 24, and a display section 25. The physical configurations of the control section 21, the storage section 22, and the communication section 23 are the same as those of the control section 11, the storage section 12, and the communication section 13, respectively. The operation unit 24 is an input device such as a touch panel. The display unit 25 is a liquid crystal display or an organic EL (Electro Luminescence) display.

For example, a reading device 26 and an output device 27 are connected to the store terminal 20. The reading device 26 is a device that reads images or storage media. In this embodiment, a case will be described in which the reading device 26 is a code reader, but the reading device 26 may be another device. For example, the reading device 26 may be a camera, a scanner, an NFC (Near Field Communication) reader, or a magnetic card reader. The reading device 26 may have not only a reading function but also a writing function.

The output device 27 is an image forming device. In this embodiment, a case will be described in which the output device 27 is a receipt printer, but the output device 27 may be another device. For example, the output device 27 may be a printer other than a receipt printer, an image forming device that is not classified as a printer, a copy machine, or a multifunction device. The receipt may be output as an electronic image rather than a physical paper.

Hereinafter, a physical paper receipt will be referred to as a paper receipt. An electronic image receipt is called an electronic receipt. When not distinguishing between paper receipts and electronic receipts, they are simply called receipts. In this embodiment, a case where a receipt roll paper is used as a paper receipt will be described, but other types of paper may be used as the paper receipt. For example, general copy paper may be used as a paper receipt.

The user terminal 30 is a computer of a user who uses the store. In FIG. 1, only one user terminal 30 is shown, but in this embodiment, it is assumed that each user terminal 30 of a plurality of users exists. A user has at least one user terminal 30. The user may use the store without using the user terminal 30.

For example, the user terminal 30 is a smartphone, a personal computer, a tablet terminal, or a wearable terminal. The physical configurations of the control unit 31, storage unit 32, communication unit 33, operation unit 34, and display unit 35 are the same as those of the control unit 11, storage unit 12, communication unit 13, operation unit 24, and display unit 25, respectively. be. The reading unit 36 may be the same as the reading device 26, but in this embodiment, it is assumed that the user terminal 30 is a smartphone and the reading unit 36 is a camera of the smartphone.

Note that the programs stored in the storage units 12, 22, and 32 may be supplied via the network N. In addition, a program stored in a computer-readable information storage medium can be used as a reading section (for example, an optical disk drive or a memory card slot) for reading the information storage medium, or an input/output section for inputting and outputting data with external equipment. (e.g., a USB port).

Further, the receipt output system 1 only needs to include at least one computer, and the computers included in the receipt output system 1 are not limited to the example shown in FIG. For example, the receipt output system 1 may include only the server 10. In this case, the store terminal 20 and the user terminal 30 exist outside the receipt output system 1. For example, the receipt output system 1 may also include the server 10 and computers other than the store terminal 20 and the user terminal 30.

[2. Overview of receipt output system]
In this embodiment, a member store of a point service will be described as an example of a store. The point service is a service that grants points to users who use a store according to the amount spent. Hereinafter, a retail store will be taken as an example, but the store itself may be of any type and is not limited to a retail store. For example, the store may be a store that provides services, such as a restaurant or a beauty salon, and is not limited to a store that sells products.

FIG. 2 is a diagram illustrating an example of how a user uses a store. In this embodiment, a case will be described in which the user is a member of a point service, but the user does not need to be a member of a point service. Furthermore, although a case will be described in which the point card screen SC1 displayed on the display unit 35 of the user terminal 30 is used as a point card, the point card may be of other types. For example, an IC card, a magnetic card, or an IC chip of the user terminal 30 may be used as a point card.

For example, a point app that is a point service application is installed on the user terminal 30. When the point app starts, a login process to the point service is executed. If the login process is successful, a point card screen SC1 is displayed on the display section 35. On the point card screen SC1, a barcode BC in which a temporary ID that can temporarily identify the user is encoded is displayed together with the points held by the user. The temporary ID may be encoded in a two-dimensional code instead of the barcode BC.

For example, the store clerk causes the reading device 26 to read the barcode of the product and the barcode BC on the point card screen SC1. In the case of a self-checkout, the user allows the reading device 26 to read these items himself/herself. When the barcode BC on the point card screen SC1 is read, the user can be identified by the temporary ID, so the points held by the user can be used. The user may complete the transaction using all or part of the points that he or she owns, or may complete the transaction without using the points that he or she owns.

In this embodiment, when the user completes the transaction, the output device 27 outputs a summary receipt SR, which is a paper receipt showing the general details of the transaction. For example, the store name, telephone number, address, date and time of use, receipt number, person in charge, total amount, deposit, change, amount eligible for points, and earned points are printed on the summary receipt SR. Product details regarding details of individual products are not printed on the summary receipt SR. The summary receipt SR is shorter than a normal receipt, which is a paper receipt on which product details are printed.

FIG. 3 is a diagram showing an example of a summary receipt SR and a regular receipt. In FIG. 3, summary receipt SR and normal receipt NR are shown when transactions are conducted under the same conditions. The normal receipt NR can also be a paper receipt before being simplified by the summary receipt SR, or a full version paper receipt with all items printed. In this embodiment, the normal receipt NR will be explained for comparison with the summary receipt SR, but the normal receipt NR is not actually output from the output device 27.

As shown in FIG. 3, the normal receipt NR includes product details indicating the product name and unit price of each product. In the example of FIG. 3, since 15 products have been purchased, the product details include 15 items (combinations of product names and unit prices). As the number of products increases, the number of items in the product details increases, so the receipt NR usually becomes longer. On the other hand, since the product details are not printed on the summary receipt SR, it is basically shorter than the normal receipt NR. The items omitted in the summary receipt SR may be any items and are not limited to product details. For example, in the summary receipt SR, other items such as store name, telephone number, address, or person in charge may be omitted.

In this embodiment, the user can use the summary receipt SR to display an electronic receipt containing more information than the summary receipt SR. For example, a two-dimensional code TC in which data for displaying the electronic receipt is encoded is printed on the summary receipt SR. This data may be encoded into a barcode rather than the two-dimensional code TC. When the user reads the two-dimensional code TC with the reading section 36, an electronic receipt screen is displayed on the display section 35.

FIG. 4 is a diagram showing an example of an electronic receipt screen. In this embodiment, a case will be described in which the electronic receipt screen SC2 is displayed on a browser, but the electronic receipt screen SC2 may be displayed on a point application or other application. For example, the electronic receipt screen SC2 may be displayed after it is confirmed that the person who read the two-dimensional code TC is the user who performed the transaction indicated by the electronic receipt ER.

For example, an electronic receipt ER including product details is displayed on the electronic receipt screen SC2. In the example of FIG. 4, a case will be described in which the electronic receipt ER has the same content as the normal receipt NR, but the electronic receipt ER may have different content from the normal receipt NR. For example, the electronic receipt ER may have more or less information than the normal receipt NR. The user may be able to specify how much information to include in the electronic receipt ER.

In this embodiment, points are awarded according to the amount of paper consumption reduced by the summary receipt SR. Hereinafter, this amount of consumption will be referred to as the amount of reduction. For example, the electronic receipt screen SC2 displays the amount of reduction and points corresponding to the amount of reduction. In this embodiment, it is assumed that 0.01 point is given per 1 cm of reduction amount. In the example of FIG. 4, the reduction amount is 5 cm, so 0.05 points are given. Note that fractions less than 1 point cannot be used in stores. Further, the amount of reduction may be calculated or displayed using an index in accordance with a general method of calculating the effect of reducing environmental load, such as LCA (Life Cycle Assessment). For example, changes in the amount of reduction and the amount of energy consumed can be expressed using any index such as "ten trees," carbon footprint, or energy intensity.

In this embodiment, the summary receipt data necessary for outputting the summary receipt SR and the electronic receipt data necessary for outputting the electronic receipt ER are generated by the server 10 instead of the store terminal 20. The summary receipt SR is output based on summary receipt data generated by the server 10. The electronic receipt screen SC2 is displayed based on electronic receipt data generated by the server 10. Hereinafter, when summary receipt data and electronic receipt data are not distinguished, they will simply be referred to as receipt data.

As described above, the receipt output system 1 of this embodiment mainly includes a first configuration that outputs a summary receipt SR on which a two-dimensional code TC is printed, and a second configuration that provides points according to the amount of reduction. , and a third configuration in which receipt data is generated on the server 10 side. Hereinafter, details of the first to third configurations will be explained. Note that the receipt output system 1 may include only one or two of the first to third configurations, and does not have to include all of the first to third configurations. . This point will be explained in detail in a modified example below.

[3. Functions realized by the receipt output system]
FIG. 5 is a diagram showing an example of functions realized by the receipt output system 1. Hereinafter, when summary receipt SR and normal receipt NR are not distinguished, they will simply be referred to as paper receipts. Furthermore, when the summary receipt SR, normal receipt NR, and electronic receipt ER are not distinguished from each other, they are simply referred to as receipts.

[3-1. Functions related to the first configuration]
First, an example of a function related to the first configuration will be explained.

[3-1-1. Functions related to the first configuration realized by the server]
For example, the server 10 includes a data storage section 100, a transaction data acquisition section 101, a receipt data generation section 102, and a receipt output section 103 as functions related to the first configuration. The data storage section 100 is realized by the storage section 12. Each of the transaction data acquisition section 101, the receipt data generation section 102, and the receipt output section 103 is realized by the control section 11.

[Data storage unit]
The data storage unit 100 stores data necessary for outputting a receipt. For example, the data storage unit 100 stores a user database DB1, a store database DB2, a summary receipt converter SRC, and an electronic receipt converter ERC. Hereinafter, when the summary receipt converter SRC and the electronic receipt converter ERC are not distinguished, they will simply be referred to as converters.

FIG. 6 is a diagram showing an example of the user database DB1. The user database DB1 is a database that stores various data regarding users. For example, the user database DB1 stores user IDs, passwords, temporary IDs, names, addresses, telephone numbers, email addresses, points held, transaction data, summary receipt data, and electronic receipt data. Any data may be stored in the user database DB1, and the data stored in the user database DB1 is not limited to the example shown in FIG. 6.

Each of the user ID and temporary ID is an example of user identification data that can identify a user. Therefore, the portions where the user ID or temporary ID is explained can be replaced with user identification data. The user identification data may be any data that can identify the user in some way, and may be, for example, a telephone number, email address, or point card number. The user ID and password are used to log into the point service. The temporary ID is used to present the barcode BC at the store.

The temporary ID is issued based on predetermined issuance rules so as not to overlap with other temporary IDs. For example, an expiration date may be set for the temporary ID. The temporary ID can be updated at any timing, such as when the point application is started or when the user instructs the update. Other user identification data such as a user ID may be encoded in the barcode BC instead of the temporary ID. In this case, a temporary ID need not be issued.

The transaction data is data related to the details of transactions performed at the store. A transaction is the purchase of a product or the use of a service. The transaction content is the specific details of the transaction. For example, the transaction data includes a plurality of items such as a transaction ID, a person in charge, product details, a total amount, a deposit, change, an amount eligible for points, and earned points. Transaction data can include arbitrary items. Items included in transaction data are not limited to the examples of this embodiment.

The transaction ID is an example of transaction identification data that can identify a transaction. Therefore, the portion explaining the transaction ID can be read as transaction identification data. The transaction identification data may be any information that can identify the transaction in some form, and may be data called by a name other than the transaction ID.

In this embodiment, a case will be described in which a combination of a store ID, a store terminal ID, a transaction date and time, and a receipt number corresponds to a transaction ID, but the transaction ID only needs to be able to identify the transaction in some way, and in this embodiment It is not limited to the example of the form. For example, the transaction ID may be only the receipt number. The transaction ID may be an ID issued with a serial number so as not to overlap with transaction IDs of other transactions. Each time a transaction is performed at an individual store, the transaction ID may be incremented by one so that it becomes a sequential number. In this case, the transaction ID may be reset on the next day.

The store ID is an example of store identification data that can identify a store. Therefore, the portion explaining the store ID can be replaced with store identification data. The store identification data may be any information that can identify the store in some way, and is not limited to the store ID. For example, the store identification data may be a store name, address, telephone number, or email address. A store terminal ID, which is data that can identify each store terminal 20 in a certain store, also corresponds to store identification data. The receipt numbers are issued sequentially within a certain store terminal 20.

The summary receipt data is data regarding the summary receipt SR. In this embodiment, a case will be described in which the summary receipt data is image data such as JPEG or GIF, but the summary receipt data may be in any data format. For example, the summary receipt data may be in other data formats such as text data, document data, or CSV data. The summary receipt data may be data only for the two-dimensional code TC portion of the summary receipt SR. The summary receipt data may be sent to the store terminal 20 and then discarded without being stored in the user database DB1.

The electronic receipt data is data related to the electronic receipt ER of a transaction performed at a store. In this embodiment, a case will be described where the electronic receipt data is image data such as JPEG or GIF, but the electronic receipt data may be in any data format. For example, the electronic receipt data may be in other data formats such as text data, document data, or CSV data from which an image is generated. The electronic receipt data may not be stored in the user database DB1, but may be generated on the spot based on transaction data when display of the electronic receipt ER is requested.

FIG. 7 is a diagram showing an example of the store database DB2. The store database DB2 is a database that stores various data regarding stores. For example, store database DB2 stores store ID, store name, address, telephone number, email address, store terminal ID, store terminal name, and receipt paper information. The receipt paper information is information regarding the receipt paper set in the output device 27 of the store terminal 20. For example, the receipt paper information indicates the manufacturer, model number, width, and paper quality of the receipt paper. Any data may be stored in the store database DB2, and the data stored in the store database DB2 is not limited to the example shown in FIG. 7.

FIG. 8 is a diagram illustrating an example of a process in which summary receipt data is generated by the summary receipt converter SRC. Summary receipt converter SRC is a program that converts transaction data into summary receipt data. In this embodiment, an example is given in which a summary receipt converter SRC exists for each store, but a common summary receipt converter SRC may be used in a plurality of stores.

For example, a summary receipt converter SRC generates summary receipt data when transaction data is input. For example, the summary receipt converter SRC defines a process of arranging all or some items of transaction data at predetermined positions in the format FSR of the summary receipt SR to generate image data. In other words, the summary receipt converter SRC defines processing for converting the data format of transaction data into the data format of summary receipt data.

For example, the summary receipt converter SRC defines a coding process for generating and coding the URL of the electronic receipt screen SC2, and an information placement process for placing information in the format FSR of the summary receipt SR. In the example in Figure 8, in the encoding process, the transaction ID is set as an argument for the URL "https://www.xxxpoint.com/e-receipt/" for electronic receipt ER, and the URL including the argument is encoded. Ru. The URL of the electronic receipt ER is not limited to the example shown in FIG. 8, and may be any URL. However, it is assumed that the URL includes information that allows the electronic receipt ER to be displayed to be identified in some way.

In the example of FIG. 8, in the information placement process, the store name, telephone number, and address associated with the store ID included in the transaction data are placed in area A1 of the format FSR. In the information arrangement process, the transaction date and time, receipt number, person in charge, total amount, deposit, change, point target amount, and earned points included in the transaction data are arranged in areas A2 to A9 of the format FSR, respectively. In the information placement process, the two-dimensional code TC generated by the encoding process is placed in area A10. When the process defined in the summary receipt converter SRC is executed, summary receipt data of the summary receipt SR is generated.

FIG. 9 is a diagram illustrating an example of a process in which electronic receipt data is generated by the electronic receipt converter ERC. Electronic receipt converter ERC is a program that converts transaction data into electronic receipt data. In this embodiment, an example is given in which an electronic receipt converter ERC exists for each store, but a common electronic receipt converter ERC may be used in a plurality of stores.

For example, an electronic receipt converter ERC generates electronic receipt data upon input of transaction data. For example, the electronic receipt converter ERC defines a process of arranging all or some of the items included in transaction data at predetermined positions in the format FER of the electronic receipt ER to generate image data. In other words, the electronic receipt converter ERC defines processing for converting the data format of transaction data into the data format of electronic receipt data.

For example, the electronic receipt converter ERC defines an information arrangement process for arranging information in the format FER of the electronic receipt ER. In the example of FIG. 9, in the information placement process, the store name, telephone number, and address associated with the store ID included in the transaction data are placed in the area A11 of the format FER. In the information arrangement process, the transaction date and time, receipt number, person in charge, product details, total amount, deposit, change, point target amount, and earned points included in the transaction data are arranged in areas A12 to A20 of the format FSR, respectively. Ru. The length of the product details area A15 is variable. When the processing defined in the electronic receipt converter ERC is executed, electronic receipt data of the electronic receipt ER is generated.

Note that the data storage unit 100 may store other data. For example, the data storage unit 100 may store a product database in which various data related to products are stored. The product database stores data such as product IDs, product names, and unit prices. The product ID is an example of product identification data that can identify the product. The product ID may be a JAN (Japanese Article Number) code, a code according to other standards, or an ID uniquely defined by the store.

[Transaction data acquisition department]
Transaction data acquisition unit 101 acquires transaction data. For example, the store terminal 20 generates transaction data based on a product ID obtained by reading the barcode of the product with the reading device 26 or a product ID input from the operation unit 24 . The data format of the transaction data itself may be the same as the data format used in known point services or other services. Therefore, the process by which the store terminal 20 generates transaction data may also be the same as the process used in known point services or other services.

It is assumed that the product database storing various data related to products is stored in advance in the store terminal 20 or another computer in the store. The product database may be stored in the data storage unit 100. The store terminal 20 acquires the product name and unit price associated with the product ID. If the same product ID is acquired multiple times, the store terminal increases the quantity of the product. The quantity of products may be input from the operation unit 24.

For example, the store terminal 20 issues a new transaction ID when a checkout operation indicating that checkout is completed is performed. The accounting operation may be any operation, for example, an operation of pressing a predetermined key on the operation unit 24 or an operation of reading a point card. In this embodiment, the combination of store ID, store terminal ID, transaction date and time, and receipt number corresponds to the transaction ID, so the store terminal 20 acquires these combinations as the transaction ID. The store terminal 20 generates transaction data including a transaction ID, person in charge, product details, total amount, deposit, change, point target amount, and earned points. The store terminal 20 transmits the temporary ID acquired from the barcode BC and the generated transaction data to the server 10.

For example, upon acquiring a temporary ID and transaction data from the store terminal 20, the transaction data acquisition unit 101 stores the acquired transaction data in the record in which the acquired temporary ID is stored in the user database DB1. . The transaction data acquisition unit 101 can acquire transaction data from the user database DB1 at any timing. If there is no need to save the transaction data, the transaction data may be discarded after the summary receipt data and electronic receipt data are generated.

In this embodiment, since there are a plurality of stores, the transaction data acquisition unit 101 acquires transaction data regarding the details of transactions performed at the store from the store terminal 20 of each of the plurality of stores. For example, the transaction data acquisition unit 101 acquires the temporary ID of the user who made the transaction from the store terminal 20 of each of a plurality of stores. For example, the transaction data acquisition unit 101 acquires a store ID and a store terminal ID from each store terminal 20 of a plurality of stores.

As described above, the store ID and the store terminal ID are examples of store identification data that can identify the store terminal 20. The transaction data acquisition unit 101 may acquire only the store ID or store terminal ID as the store identification data. In this embodiment, a case will be described in which the store ID and the store terminal ID are included in the transaction data, but the store ID and the store terminal ID may be data different from the transaction data.

[Receipt data generation section]
The receipt data generation unit 102 generates receipt data regarding transaction receipts based on transaction data. For example, the receipt data generation section 102 includes a summary receipt data generation section 102A and an electronic receipt data generation section 102B. The summary receipt data generation unit 102A is an example of a paper receipt data generation unit. The paper receipt data generation unit may generate normal receipt data, which is receipt data of normal receipt NR, instead of summary receipt data.

[Summary receipt data generation section]
The summary receipt data generation unit 102A generates summary receipt data based on the transaction data. In this embodiment, summary receipt data corresponds to paper receipt data. Therefore, the portion described as summary receipt data can be read as paper receipt data. The paper receipt data may be data related to paper receipts other than the summary receipt SR. For example, when outputting a regular receipt NR instead of a summary receipt SR, the paper receipt data may be data regarding the regular receipt NR.

For example, the summary receipt data generation unit 102A generates summary receipt data based on transaction data. In this embodiment, since a summary receipt converter SRC is prepared for each store, the summary receipt data generation unit 102A generates a transaction based on the summary receipt converter SRC associated with the store of the store terminal 20 that transmitted the transaction data. Generate summary receipt data by converting the data.

For example, the summary receipt data generation unit 102A generates summary receipt data by executing the code generation process and the information arrangement process described with reference to FIG. 8, and generates image data of the summary receipt SR. When the summary receipt data generation unit 102A generates the summary receipt data, it stores the generated summary receipt data in the record in the user database DB1 in which the temporary ID received together with the transaction data is stored.

[Electronic receipt data generation section]
The electronic receipt data generation unit 102B generates electronic receipt data based on the transaction data. In this embodiment, since an electronic receipt converter ERC is prepared for each store, the electronic receipt data generation unit 102B generates a transaction based on the electronic receipt converter ERC associated with the store of the store terminal 20 that transmitted the transaction data. Generate electronic receipt data by converting the data.

For example, the electronic receipt data generation unit 102B generates electronic receipt data by executing the information arrangement process described with reference to FIG. 9 and generating image data of the electronic receipt ER. When the electronic receipt data generation unit 102B generates the electronic receipt data, it stores the generated electronic receipt data in the record in the user database DB1 in which the temporary ID received together with the transaction data is stored.

[Receipt output section]
The receipt output unit 103 outputs a receipt based on the receipt data. Outputting a receipt means having the store terminal 20 output a physical paper receipt, transmitting receipt data, or displaying some kind of image related to the receipt. For example, the receipt output section 103 includes a summary receipt output section 103A and an electronic receipt output section 103B. The summary receipt output unit 103A is an example of a paper receipt output unit. The paper receipt output unit may output the normal receipt NR instead of the summary receipt SR.

[Summary receipt output section]
The summary receipt output unit 103A outputs a summary receipt SR. In this embodiment, the summary receipt output unit 103A outputs a summary receipt SR regarding the summary of the transaction, including a two-dimensional code TC regarding the output of the electronic receipt ER, based on the transaction data. The two-dimensional code TC is an example of a code related to the output of the electronic receipt ER. Therefore, the part written as the two-dimensional code TC can be read as a code related to the output of the electronic receipt ER.

The code related to the output of the electronic receipt ER is a code in which information for outputting the electronic receipt ER is encoded. In this embodiment, a case will be described in which this information is a URL shown in FIG. 8, but this information may be any information that can identify transaction data or electronic receipt data. For example, this information may be just the transaction ID, rather than a URL that includes the transaction ID.

Note that if information other than the transaction ID is associated with the electronic receipt data as information that allows identification, the other information may be encoded. The URL may be issued for each electronic receipt ER, or may be common to multiple electronic receipts ER. Data other than the URL may also be encoded in the code related to the output of the electronic receipt ER. The code related to the output of the electronic receipt ER is not limited to the two-dimensional code TC, but may be another code such as a bar code.

Outputting the summary receipt SR means outputting a physical summary receipt SR or outputting electronic summary receipt data. In this embodiment, since the summary receipt output unit 103A is included in the server 10, transmitting the summary receipt data to the store terminal 20 corresponds to outputting the summary receipt SR. That is, in this embodiment, transmitting the summary receipt data generated based on the transaction data to the store terminal 20 corresponds to outputting the summary receipt SR based on the transaction data.

For example, the summary receipt output unit 103A outputs the summary receipt SR by transmitting the summary receipt data generated by the summary receipt data generation unit 102A based on the transaction data to the store terminal 20. The summary receipt data may be generated by the summary receipt output unit 103A instead of the summary receipt data generation unit 102A. That is, the summary receipt output section 103A may include the functions of the summary receipt data generation section 102A.

For example, the summary receipt output unit 103A outputs a summary receipt SR in which at least some of the items included in the electronic receipt ER are omitted. In this embodiment, a case will be described in which the product details of the electronic receipt ER are omitted in the summary receipt SR, but the items omitted in the summary receipt SR may be any items and are not limited to the product details. For example, at least one of the store name, telephone number, address, date of use, receipt number, total amount, point eligible amount, and earned points may be omitted in the summary receipt SR. Which items are omitted are defined in the summary receipt converter SRC.

[Electronic receipt output section]
The electronic receipt output unit 103B outputs an electronic receipt ER based on the electronic receipt data. Outputting the electronic receipt ER means transmitting electronic receipt data, transmitting display data (for example, HTML data or image data) of the electronic receipt screen SC2, or displaying the electronic receipt screen SC2. In this embodiment, since the electronic receipt output unit 103B is included in the server 10, transmitting the electronic receipt data to the store terminal 20 corresponds to the electronic receipt output unit 103B outputting the electronic receipt ER.

In this embodiment, when the two-dimensional code TC is read by the user terminal 30, the electronic receipt output unit 103B outputs the electronic receipt ER based on the electronic receipt data. For example, a URL including a transaction ID is encoded in the two-dimensional code TC. When the user terminal 30 reads the two-dimensional code TC, it transmits the transaction ID included as an argument to the server 10. Upon receiving the transaction ID, the electronic receipt output unit 103B acquires electronic receipt data of the electronic receipt ER to be displayed from the user database DB1. The electronic receipt output unit 103B outputs the electronic receipt ER by transmitting the acquired electronic receipt data to the user terminal 30.

Note that the electronic receipt data of the electronic receipt ER to be displayed may be specified by data other than the transaction ID. For example, if receipt numbers are issued for all transactions so as not to be duplicated, the electronic receipt data of the electronic receipt ER to be displayed may be specified by the receipt number. For example, since it is unlikely that the same user will conduct multiple transactions at a certain transaction date and time, the electronic receipt data of the electronic receipt ER to be displayed may be specified by a combination of the user ID and the transaction date and time.

[3-1-2. Functions related to the first configuration realized by the store terminal]
For example, the store terminal 20 includes a data storage section 200 and a summary receipt output section 201 as functions related to the first configuration. The data storage section 200 is realized by the storage section 22. The summary receipt output unit 201 is realized by the control unit 21. The summary receipt output unit 201 is an example of a paper receipt output unit. The paper receipt output unit may output the normal receipt NR instead of the summary receipt SR.

[Data storage unit]
The data storage unit 200 stores data necessary for outputting the summary receipt SR. For example, the data storage unit 200 stores a product database in which various data related to products handled at the store are stored. It is assumed that the information necessary for the product details is stored in the product database. For example, the data storage unit 200 also stores data such as a store ID, a store terminal ID, a store name, a telephone number, an address, a transaction ID, and the name of a person in charge. For example, the data storage unit 200 may store a history of transaction data.

[Summary receipt output section]
Summary receipt output section 201 outputs summary receipt SR. Since the summary receipt output unit 201 is included in the store terminal 20, the summary receipt output unit 201 forms an image on the receipt paper set in the output device 27, and discharges the summary receipt SR on which the image is formed. outputs a summary receipt SR. As for the method of discharging the summary receipt SR, a method suitable for the known output device 27 can be used.

In this embodiment, the summary receipt data is generated by the server 10, so the summary receipt output unit 201 outputs the summary receipt SR based on the summary receipt data acquired from the server 10. Summary receipt output unit 201 controls output device 27 to form an image according to summary receipt data. The output device 27 outputs a summary receipt SR on which an image according to the summary receipt data is formed based on the control of the summary receipt output unit 201.

Note that the summary receipt output unit 201 may include the same function as the summary receipt data generation unit 102A. In this case, it is assumed that the summary receipt converter SRC is stored in the data storage section 200. Summary receipt output unit 201 generates summary receipt data based on transaction data and summary receipt converter SRC. The summary receipt output unit 201 outputs a summary receipt SR based on the generated summary receipt data. The method of generating the summary receipt data itself is the same as described in the process of the summary receipt data generation unit 102A.

[3-1-3. Functions related to the first configuration realized by the user terminal]
For example, the user terminal 30 includes a data storage section 300 and an electronic receipt output section 301 as functions related to the first configuration. The data storage section 300 is realized by the storage section 32. The electronic receipt output section 301 is realized by the control section 31.

[Data storage unit]
The data storage unit 300 stores data necessary for outputting the electronic receipt ER. For example, the data storage unit 300 stores a browser for displaying the electronic receipt screen SC2. The electronic receipt screen SC2 may be displayed on the point application. In this case, the data storage unit 300 stores the point application. The electronic receipt screen SC2 may be displayed on a dedicated application for displaying the electronic receipt ER instead of the point application.

[Electronic receipt output section]
The electronic receipt output unit 301 outputs an electronic receipt ER. Since the electronic receipt output unit 301 is included in the user terminal 30, the electronic receipt output unit 301 outputs the electronic receipt ER by displaying the electronic receipt ER on the display unit 35. In this embodiment, a case will be described in which the electronic receipt output unit 301 displays the electronic receipt ER on a browser, but the electronic receipt output unit 301 may also display the electronic receipt ER on a point app or other application. good.

In this embodiment, since the electronic receipt data is generated by the server 10, the electronic receipt output unit 301 outputs the electronic receipt ER based on the electronic receipt data acquired from the server 10. For example, the electronic receipt output unit 301 causes the display unit 35 to display an electronic receipt screen SC2 that includes the electronic receipt ER and other information such as the reduction amount. The electronic receipt screen SC2 may have any layout and is not limited to the example shown in FIG. 4. For example, the electronic receipt ER displayed on the electronic receipt screen SC2 may not have a layout imitating a paper receipt, but may display items such as product details in a table format.

Note that the electronic receipt output section 301 may include the same function as the electronic receipt data generation section 102B. In this case, it is assumed that the electronic receipt converter ERC is stored in the data storage section 300. The electronic receipt output unit 301 generates electronic receipt data based on the transaction data and the electronic receipt converter ERC. The electronic receipt output unit 301 outputs an electronic receipt ER based on the generated electronic receipt data. The electronic receipt data generation method itself is the same as described in the processing of the electronic receipt data generation unit 102B.

[3-2. Functions related to second configuration]
Next, functions related to the second configuration will be explained. The second configuration has some of the same functions as the first configuration, so the description may overlap to some extent.

[3-2-1. Functions related to the second configuration realized by the server]
For example, the server 10 includes a data storage section 100, a transaction data acquisition section 101, a reduction amount calculation section 104, and a benefit provision section 105 as functions related to the second configuration. Each of the reduction amount calculation unit 104 and the benefit provision unit 105 is realized by the control unit 11.

[Data storage unit]
The data storage unit 100 may be similar to the first configuration.

[Transaction data acquisition department]
The transaction data acquisition unit 101 may have the same configuration as the first configuration.

[Reduction amount calculation section]
The reduction amount calculation unit 104 calculates the reduction amount regarding the paper receipt of the transaction based on the transaction data. The amount of reduction is the amount by which the consumption of paper receipts can be reduced. In other words, the reduction amount is the consumption amount of paper receipts that could have been output if the same transaction had been performed, but were not actually output. In this embodiment, the summary receipt SR is, in principle, shorter than the normal receipt NR, so by outputting the summary receipt SR, the amount shortened compared to the normal receipt NR corresponds to the amount of reduction.

In this embodiment, since the summary receipt SR is output to the user, the reduction amount calculation unit 104 calculates the amount of reduction based on the transaction data, which is a paper receipt that has more information than the summary receipt and is not actually output. The difference between the consumption amount of the receipt NR and the consumption amount of the summary receipt SR is calculated as the reduction amount. The consumption amount is the amount of receipt paper consumed. In this embodiment, a case will be described in which the length of the receipt paper corresponds to the consumption amount, but the area of the receipt paper may correspond to the consumption amount.

For example, a normal receipt converter that is a converter for normal receipt NR may be stored in the data storage unit 100. In this embodiment, since the contents of the normal receipt NR and the electronic receipt ER are the same, a case will be described in which the normal receipt converter executes the same processing as the electronic receipt converter ERC. may perform different processing.

For example, the information arrangement process of the normal receipt converter may be different from the information arrangement process of the electronic receipt converter ERC so that the information arrangement is unique to the normal receipt NR. The reduction amount calculation unit 104 generates normal receipt data regarding the normal receipt NR based on the normal receipt converter and transaction data. The data format of normal receipt data may be the same as summary receipt data or electronic receipt data.

In this embodiment, a case will be described in which the receipt data generation unit 102 generates normal receipt data and summary receipt data, but the reduction amount calculation unit 104 may generate normal receipt data and summary receipt data. The reduction amount calculation unit 104 may calculate the consumption amount of the normal receipt NR and the consumption amount of the summary receipt SR based on the normal receipt data and summary receipt data generated based on the transaction data.

In the example of FIG. 3, the summary receipt SR is longer for the two-dimensional code TC, but shorter for the product details. That is, if the length L10 of the two-dimensional code TC portion in the summary receipt SR is shorter than the length L20 of the product details portion in the normal receipt NR, the amount of reduction will be positive. In the example of FIG. 3, the reduction amount calculation unit 104 calculates a length L0 obtained by subtracting the entire length L11 of the summary receipt SR from the entire length L21 of the normal receipt NR as the reduction amount.

Note that the method of calculating the reduction amount is not limited to the example of this embodiment. The method of calculating the reduction amount differs depending on what kind of paper receipt is actually output. Since a paper receipt may not be output in the first place, the calculation method is different in this case as well. Furthermore, the reduction amount may be calculated without converting the normal receipt data and summary receipt data into image data. Other calculation methods will be explained in modified examples below.

For example, the reduction amount calculation unit 104 may calculate the reduction amount based on the reference consumption amount and the consumption amount of the summary receipt SR instead of the normal receipt NR. In the above example, the standard consumption amount is the consumption amount of the normal receipt NR, but it may also be specified by the point service administrator, or it may be the consumption amount of the summary receipt SR output by each of a plurality of users. It may be a statistical value such as an average value and a median value. In order to calculate the reduction amount, the consumption amount of the normal receipt NR does not need to be calculated.

Further, the reduction amount may be multiplied by a coefficient depending on the user. For example, the higher the rank of the user in the point service, the larger the coefficient may be. In this case, the higher the user's rank, the more points that can be acquired, and the more interesting the game becomes. For example, the coefficient may become larger as the amount spent by the user increases. In this case, the user can be motivated to purchase products at the store.

[Bonus Grant Department]
The benefit granting unit 105 grants points to the user based on the reduction amount calculated by the reduction amount calculation unit 104. Points are an example of a benefit. Therefore, the parts that explain points can be read as benefits. The benefits are compensation for reducing paper receipts. Various known benefits can be used as the benefit itself, and for example, the benefit may be a coupon, electronic money, content such as a video, or a physical product. The parts described as points can be read as various other benefits.

Note that it is assumed that point calculation data for calculating points given to the user from the reduction amount is stored in the data storage unit 100 in advance. The point calculation data may be in any format, for example, a mathematical formula format, a table format, or a program code. The benefit granting unit 105 calculates points to be given to the user based on the reduction amount and the point calculation data, and gives the calculated points to the user.

For example, these relationships are defined in the point calculation data such that the greater the amount of reduction, the more points are given to the user. In this case, the benefit granting unit 105 increases the number of points given to the user as the reduction amount increases. For example, the point calculation data may define a relationship between a threshold value and points such that when the amount of reduction exceeds a threshold value, points associated with this threshold value are given. In this case, when the reduction amount is equal to or greater than the threshold value, the benefit granting unit 105 grants the user points associated with this threshold value.

In this embodiment, the benefit granting unit 105 grants points to the user by increasing the points held by the user stored in the user database DB1. In the example of FIG. 4, it is defined in the point calculation data that 0.01 point is given per 1 cm, so the benefit giving unit 105 gives the user 0.05 points corresponding to the reduction amount of 5 cm. Increase the points you have. Points may be awarded immediately after the transaction is completed, or after several hours to several days have passed. Further, the timing at which points are awarded may be the timing when the benefits (held points) according to the reduction amount reach a predetermined amount. Specifically, the benefit granting unit 105 may grant points to the user at the timing when the points corresponding to the reduction amount reach, for example, 1 point.

Note that the method of providing the benefit may be any method as long as it is in accordance with the content of the benefit. For example, when a coupon corresponds to a benefit, the benefit granting unit 105 grants the benefit by printing the coupon on the summary receipt SR, or grants the benefit by transmitting the coupon to the user terminal 30. Bye. For example, if electronic money corresponds to a benefit, the benefit granting unit 105 may grant the benefit by increasing the user's electronic money balance. For example, if the content corresponds to a benefit, the benefit granting unit 105 may grant the benefit by transmitting the content to the user terminal 30. For example, if a physical product corresponds to a benefit, the benefit granting unit 105 may grant the benefit by executing processing for delivering the product.

[3-2-2. Functions related to the second configuration realized by the store terminal]
For example, the store terminal 20 includes a data storage section 200 and a summary receipt output section 201 as functions related to the second configuration. Each of the data storage unit 200 and the summary receipt output unit 201 may have the same configuration as the first configuration. Note that in the second configuration, the summary receipt SR does not need to be output, so in this case, the store terminal 20 does not include the summary receipt output unit 201.

[3-2-3. Functions related to the second configuration realized by the user terminal]
For example, the user terminal 30 includes a data storage section 300 and an electronic receipt output section 301 as functions related to the second configuration. Each of the data storage unit 300 and the electronic receipt output unit 301 may have the same configuration as the first configuration. Note that in the second configuration, the electronic receipt does not need to be output, so in this case, the user terminal 30 does not include the electronic receipt output unit 301.

[3-3. Functions related to third configuration]
Finally, functions related to the third configuration will be explained. The third configuration has some functions that overlap with at least one of the first configuration and the second configuration, so the description may overlap to some extent.

[3-3-1. Functions related to the third configuration realized by the server]
For example, the data storage section 100 of the server 10 includes a transaction data acquisition section 101, a receipt data generation section 102, and a receipt output section 103 as functions related to the third configuration.

[Data storage unit]
The data storage unit 100 may be similar to the first configuration.

[Transaction data acquisition department]
The transaction data acquisition unit 101 may have the same configuration as the first configuration.

[Receipt data generation section]
Although the receipt data generation unit 102 may be the same as the first configuration, the third configuration does not necessarily need to generate summary receipt data and electronic receipt data. That is, only either the summary receipt data or the electronic receipt data may be generated. Therefore, the function of the third configuration is a receipt data generation unit that is a higher-level concept of the summary receipt data generation unit 102A and the electronic receipt data generation unit 102B described in the functions of the first configuration and the second configuration. This will be explained as 102.

For example, the receipt data generation unit 102 generates receipt data based on the temporary ID acquired by the transaction data acquisition unit 101 and the transaction data acquired by the transaction data acquisition unit 101. The receipt data generation unit 102 determines whether the temporary ID is stored in the user database DB1. If an expiration date is set for the temporary ID, the expiration date may be confirmed.

For example, when it is determined that the temporary ID is stored in the user database DB1, the receipt data generation unit 102 generates receipt data based on the transaction data. The receipt data generation unit 102 does not generate receipt data if it is determined that the temporary ID is stored in the user database DB1. In this case, the summary receipt data may be generated by the store terminal 20.

In this embodiment, since a converter exists for each store, for example, the receipt data generation unit 102 identifies a converter related to receipt data generation based on the store ID and store terminal ID acquired by the transaction data acquisition unit 101. , generate receipt data based on the identified converter and transaction data. The receipt data generation unit 102 generates receipt data based on the store converter specified by the store ID and store terminal ID acquired by the transaction data acquisition unit 101.

Note that the converter is an example of a generator. Therefore, parts that describe converters can be read as generators. The generator is a program for generating receipt data from transaction data. When at least one item included in the transaction data is input, the generator generates and outputs receipt data according to the at least one item. A generator may also be a program called another name than a converter.

[Receipt output section]
The receipt output unit 103 may be the same as the first configuration, but in the third configuration, the summary receipt SR and electronic receipt ER do not necessarily need to be output. That is, only either the summary receipt SR or the electronic receipt ER may be output. Therefore, the function of the third configuration will be explained as a receipt data output unit that is a higher-level concept of the summary receipt output unit 103A and the electronic receipt output unit 103B described in the functions of the first configuration and the second configuration. do. The receipt data output unit may have only the function of outputting the summary receipt SR based on the summary receipt data, or may have only the function of outputting the electronic receipt ER based on the electronic receipt data. .

[3-3-2. Functions related to the third configuration realized by the store terminal]
For example, the store terminal 20 includes a data storage section 200 and a summary receipt output section 201 as functions related to the third configuration. The data storage unit 200 and the summary receipt output unit 201 may be the same as the first configuration. Note that in the third configuration, the summary receipt SR does not need to be output, so in this case, the store terminal 20 does not include the summary receipt output unit 201.

[3-3-3. Functions related to the third configuration realized by the user terminal]
For example, the user terminal 30 includes a data storage section 300 and an electronic receipt output section 301 as functions related to the third configuration. The data storage unit 300 and the electronic receipt output unit 301 may be the same as the first configuration or the second configuration. Note that in the third configuration, the electronic receipt ER does not need to be output, so in this case, the user terminal 30 does not include the electronic receipt output section 301.

[4. Processing executed by the receipt output system]
10 and 11 are diagrams showing an example of processing executed by the receipt output system 1. This is executed by the control units 11, 21, and 31 operating according to programs stored in the storage units 12, 22, and 32, respectively.

As shown in FIG. 10, the store terminal 20 reads the barcode of the product with the reading device 26 (S1). The store terminal 20 determines whether the barcode BC as a point card has been read by the reading device 26 (S2). If it is determined that the barcode BC has been read (S2: Y), the store terminal 20 executes a point inquiry process with the server 10 (S3). In S3, the store terminal 20 transmits the temporary ID acquired from the barcode BC to the server 10. The server 10 refers to the user database DB1, acquires the held points associated with the temporary ID, and transmits them to the store terminal 20. The store terminal 20 causes the display unit 25 to display the points held.

The store terminal 20 determines whether a checkout operation has been performed from the operation unit 24 (S4). If it is not determined that a checkout operation has been performed (S4: N), the process returns to S1. If it is determined that the checkout operation has been performed (S4: Y), the store terminal 20 determines whether the barcode BC as a point card has been read before the checkout operation is performed (S5 ). If it is determined that the barcode BC has not been read (S5: N), the store terminal 20 outputs a normal receipt NR that does not include information regarding points from the output device 27 (S6), and this process ends. . In S6, the store terminal 20 generates normal receipt data of the normal receipt NR based on the transaction data and the normal receipt converter stored in the storage unit 22, and outputs the normal receipt NR. Normal receipt data may be generated by the server 10.

In S5, if it is determined that the barcode BC has been read (S5: Y), the store terminal 20 generates transaction data and transmits it to the server 10 together with the temporary ID (S7). Upon receiving the temporary ID and transaction data (S8), the server 10 identifies the store's summary receipt converter SRC and electronic receipt converter ERC based on the store ID or store terminal ID included in the transaction data (S9).

The server 10 generates summary receipt data based on the transaction data and the summary receipt converter SRC and stores it in the user database DB1 (S10). The server 10 transmits the summary receipt data generated in S10 to the store terminal 20 (S11). When the store terminal 20 receives the summary receipt data (S12), it outputs the summary receipt SR from the output device 27 based on the summary receipt data (S13). The user receives the summary receipt SR and the product and leaves the store.

The server 10 calculates the difference between the consumption amount of the normal receipt NR, which is not actually output, and the consumption amount of the summary receipt SR, as the paper reduction amount (S14), and moves to FIG. 11 to notify the user of the reduction amount. Points are awarded according to the amount (S15). The server 10 generates electronic receipt data based on the transaction data and the electronic receipt converter ERC, and stores it in the user database DB1 (S16).

The user terminal 30 determines whether the two-dimensional code TC has been read by the reading unit 36 (S17). If it is not determined that the two-dimensional code TC has been read (S17: N), this process ends. If it is determined that the two-dimensional code TC has been read (S17: Y), the user terminal 30 accesses the URL for the electronic receipt ER acquired from the two-dimensional code TC (S18). When accessing in S18, the transaction ID as an argument is also transmitted.

When the server 10 receives an access from the user terminal 30 (S19), it acquires the electronic receipt data of the electronic receipt ER to be displayed from the user database DB1 based on the transaction ID included as an argument (S20). ). The server 10 generates display data for the electronic receipt screen SC2 based on the electronic receipt data and transmits it to the user terminal 30 (S21). When the user terminal 30 receives the display data (S22), it displays the electronic receipt screen SC2 on the display unit 35 (S23), and this process ends.

[Summary of first configuration]
The first configuration of this embodiment outputs a summary receipt SR including a two-dimensional code TC based on transaction data. The first configuration outputs an electronic receipt ER based on electronic receipt data when the two-dimensional code TC is read by the user terminal 30. As a result, even if users are not familiar with electronic receipt ER, they can display electronic receipt screen SC2 with a simple operation such as reading the two-dimensional code TC of summary receipt SR, making the transition to electronic receipt ER smooth. . Even if a user is not familiar with the electronic receipt ER, the summary receipt SR, which is a physical paper receipt, will ensure that the transaction has been completed. The summary receipt SR, which is an intermediate between the regular receipt NR and the electronic receipt ER, allows the user to become accustomed to the electronic receipt ER in stages. Furthermore, the summary receipt SR can reduce the amount of receipt paper, thereby reducing the burden on the global environment.

Furthermore, the first configuration outputs a summary receipt SR in which at least some of the items included in the electronic receipt ER are omitted. Thereby, the summary receipt SR can be output by simple processing such as omitting items. By omitting items, the summary receipt SR can be made shorter, thereby reducing the burden on the global environment. For example, since the processing of the summary receipt converter SRC and the electronic receipt converter ERC can be shared to some extent, the effort of creating these converters can be saved.

[Summary of second configuration]
The second configuration of this embodiment provides points to the user based on the amount of reduction. As a result, the points are increased or decreased according to the amount of reduction, so the points given to the user are more interesting than when a uniform number of points are given. For example, if the points awarded increase as the amount of receipt paper is reduced, it is possible to motivate the user to reduce the amount of receipt paper. By creating a correlation between the amount of reduction and the points awarded, gamification can be used to motivate the user to reduce the amount of receipt paper used. Furthermore, since the amount of receipt paper can be reduced, the burden on the global environment can be reduced.

Furthermore, the second configuration calculates the difference between the consumption amount of the normal receipt NR, which is not actually output, and the consumption amount of the summary receipt SR, which is actually output, as the reduction amount. This allows for accurate calculation of paper reduction. For example, since the user can receive the summary receipt SR with an awareness of the amount of reduction compared to the regular receipt NR received until the second configuration was introduced, it is possible to strongly motivate the user to reduce the amount of receipt paper used. can.

[Summary of third configuration]
The third configuration of the present embodiment generates receipt data based on transaction data of transactions performed at a plurality of stores, acquired from the store terminal 20 of each store. The third configuration outputs a receipt based on the generated receipt data. Thereby, the receipt data can be generated on the server 10 side, and the modification on the store terminal 20 side can be eliminated or reduced, so that the effort required to introduce a function related to receipt output can be reduced. For example, the store terminal 20 can output the summary receipt SR and the electronic receipt ER simply by transmitting transaction data in a predetermined format to the server 10, so that modifications on the store terminal 20 side can be eliminated or reduced.

Further, the third configuration generates receipt data based on the temporary ID and transaction data acquired from the store terminals 20 of each of the plurality of stores. With this, it is possible to output the summary receipt SR and electronic receipt ER after confirming that the user is using the point service. For example, since the user can be identified by the temporary ID, the summary receipt SR and electronic receipt ER can also be personalized.

Further, the third configuration specifies the summary receipt converter SRC and the electronic receipt converter ERC based on the store ID and store terminal ID acquired from the store terminal 20 of each of the plurality of stores. The third configuration generates summary receipt data and electronic receipt data based on the identified summary receipt converter SRC and electronic receipt converter ERC and transaction data. As a result, conversion can be performed according to the store, so that a summary receipt SR and an electronic receipt ER can be output.

[5. Modified example]
Note that the present disclosure is not limited to the embodiments described above. Changes can be made as appropriate without departing from the spirit of the present disclosure. Modifications of each of the first to third configurations will be described below.

[5-1. Modification example regarding the first configuration]
FIG. 12 is a diagram illustrating an example of functions realized in a modification of the first configuration. The membership registration determining section 106, the membership registration section 107, and the storage section 108 are realized by the control section 11.

[Modification 1-1]
For example, in the embodiment, a case has been described in which the summary receipt SR is summarized by omitting the product details normally printed on the receipt NR, but the summary receipt SR may be summarized by other methods. This is not limited to omitting product details. In modification 1-1, a case will be exemplified in which summarization is performed by summarizing a plurality of items and creating new items.

FIG. 13 is a diagram showing an example of a summary receipt of Modification 1-1. The summary receipt output unit 103A of modification 1-1 outputs a summary receipt SR in which at least some of the items included in the electronic receipt ER are summarized. Summarizing is to summarize information of each of a plurality of items into one piece of information. The summary is the same as the omission described in the embodiment in that the item itself is not printed. However, while omission means that no information regarding items that are not printed is printed, the summary is printed with information that combines the items that are not printed. A summary can also be referred to as a composition or a grouping.

For example, the summary receipt output unit 103A outputs a summary receipt SR that is at least partially summarized, based on the classification associated with each of the plurality of items, so that items of the same classification are grouped together. Classification is an attribute of an item. When each product purchased by a user corresponds to an item, the genre or category of the product corresponds to a classification. The data storage unit 100 of Modification 1-1 stores a product database in which product classifications are defined.

For example, the product database may be the same as the product database stored in the data storage unit 200 of each store terminal 20, but since each store may issue its own product ID, it may be modified. In Example 1-1, it is assumed that the product database is common to multiple stores. For example, the product database stores product names and product categories. The summary receipt output unit 103A refers to the product database stored in the data storage unit 100 and identifies the classification associated with the product name included in the transaction data.

Note that the classification identification method may be any method and is not limited to a method using a product database. For example, a machine learning model that has learned the relationship between training product names and product classifications may be used. In this case, the summary receipt output unit 103A may input the product name to be estimated to the trained machine learning model, and specify the classification output from the machine learning model as the product classification.

For example, the summary receipt output unit 103A identifies the categories of all products included in the product details of the transaction data, and calculates the total price of products in the same category. For each specified category, the summary receipt output unit 103A calculates the total amount of products belonging to the category. The summary receipt output unit 103A outputs the summary receipt SR so that the pair of classification and total amount is printed as product details. In the example of FIG. 13, three categories are specified: the category "food and drink," the category "daily necessities," and the category "stationery."

For example, the summary receipt output unit 103A outputs "fried chicken", "oolong tea", "rice crackers", "almonds", "green tea", "sweet bread", "rice balls", "candy", " The total price of 10 products such as ``orange juice'' and ``coffee'' is calculated as ``1,470 yen.'' The summary receipt output unit 103A calculates the total amount of ``500 yen'' for two items, ``wet tissue'' and ``toothpaste,'' which belong to the category ``daily necessities.'' The summary receipt output unit 103A calculates the total amount of ``500 yen'' for three items belonging to the category ``stationery'', ``ballpoint pen'', ``eraser'', and ``notebook''.

For example, the summary receipt output unit 103A indicates that the category "food and drink" is "1,470 yen", the category "daily necessities" is "500 yen", and the category "stationery" is "500 yen". Generate product details. The summary receipt output unit 103A outputs a summary receipt SR on which the generated product details are printed. Other items of the summary receipt SR may be the same as in the embodiment. The product details of the summary receipt SR of Modification 1-1 include three items. Since the product details of the normal receipt NR are 15 items, the summary receipt SR is reduced by 12 items.

Note that the method of summarizing items for generating the summary receipt SR is not limited to the method using classification. For example, summarization may be performed such that products specified in advance by the user or the store are grouped together regardless of their classification. For example, summarization may be performed such that products specified in advance by a point service administrator are grouped together. For example, summarization may be performed using the summarization method described in Modifications 1-2 and 1-3 below. It is assumed that the process of summarizing items is defined in the summary receipt converter SRC. In modification 1-1, a case has been described in which the summary receipt output unit 103A executes the main processing, but similarly to the embodiment, the summary receipt data generation unit 102A generates summary receipt data, and the summary receipt output unit 103A However, the summary receipt SR shown in FIG. 13 may be output based on the generated summary receipt data. This point is the same for the modifications after Modification 1-2.

The first configuration of Modification 1-1 outputs a summary receipt SR in which at least some of the items included in the electronic receipt ER are summarized. As a result, a certain amount of information can be included in the summary receipt SR, thereby reducing the discomfort felt by users who are not accustomed to the electronic receipt ER. As a result, the user can comfortably receive the summary receipt SR and read the two-dimensional code TC to use the electronic receipt ER, making the transition to the electronic receipt ER smoother.

Furthermore, the first configuration outputs a summary receipt SR that is at least partially summarized, based on the classification associated with each of the plurality of items, so that items of the same classification are grouped together. This makes it possible to create a summary receipt SR that includes an easy-to-understand summary, thereby increasing convenience for the user.

[Modification 1-2]
For example, as a summary method other than Modification 1-1, the summary receipt output unit 103A can summarize items whose usage frequency satisfies a predetermined criterion based on the usage frequency associated with each of the plurality of items. A summary receipt SR that is at least partially summarized may be output. When a product is purchased, the frequency of purchase of the product corresponds to the frequency of use. When a service is used, the frequency of use of the service corresponds to the frequency of use described above. The frequency of use can also be called the number of times of use.

FIG. 14 is a diagram showing an example of the summary receipt SR of Modification 1-2. For example, the summary receipt output unit 103A refers to the user database DB1 and obtains the purchase frequency for each product by referring to the user's past transaction data. The summary receipt output unit 103A aggregates past transaction data associated with a certain user and calculates the purchase frequency for each product. The purchase frequency may be calculated in advance and stored in the user database DB1. The purchase frequency may cover the entire past period, or may cover only a part of the past period.

For example, the summary receipt output unit 103A outputs the summary receipt SR so that products whose purchase frequency is equal to or higher than a threshold value are grouped together. The threshold value may be a value depending on the user, or may be a value common to multiple users. The threshold value may be specified by the user or the store. In the example of FIG. 14, the receipt output unit 103 outputs that among the 15 products purchased by the user, the purchase frequency of "deep-fried chicken" and "green tea" is equal to or higher than the threshold value, so the amounts of these products are combined and displayed as " A total amount such as ``400 yen'' is calculated for the item ``Frequently Purchased Items,'' and a summary receipt SR is output.

Note that in Modification 1-2, a case has been described in which the usage frequency being equal to or greater than the threshold value corresponds to the predetermined criterion, but the predetermined criterion may be that the usage frequency is less than the threshold value. In this case, the summary receipt output unit 103A may calculate the total amount of items whose usage frequency is less than a threshold value as items of "items that are not usually purchased" and output the summary receipt SR. For example, the predetermined criterion may also be that the change in usage frequency is greater than or equal to a threshold value or less than a threshold value. In this case, the summary receipt output unit 103A calculates the total amount of items for which the change in usage frequency is greater than or equal to the threshold value or less than the threshold value as items of "items I started buying recently" or "items I stopped buying recently," A summary receipt SR may also be output.

The first configuration of Modification 1-2 is a summary that is at least partially summarized so that items whose usage frequency satisfies a predetermined criterion are summarized based on the usage frequency associated with each of a plurality of items. Output receipt SR. As a result, a certain amount of information can be printed on the summary receipt SR, thereby further reducing the discomfort experienced by users who are not accustomed to the electronic receipt ER. As a result, the user can comfortably receive the summary receipt SR and read the two-dimensional code TC to use the electronic receipt ER, making the transition to the electronic receipt ER smoother.

[Modification 1-3]
For example, as a summarization method other than Modifications 1-1 and 1-2, the summary receipt output unit 103A selects items whose amount satisfies a predetermined standard based on the amounts associated with each of a plurality of items. At least a partially summarized paper receipt may be output so that the information can be summarized. In Modification 1-3, a case will be described in which the amount of money equal to or greater than the threshold value corresponds to the predetermined standard, but the amount of money less than the threshold value may correspond to the predetermined standard. The threshold value may be a fixed value or a variable value. For example, when the threshold value is a variable value, the user may specify the threshold value, or the threshold value may be set according to the average value of past usage amounts by users.

FIG. 15 is a diagram showing an example of the summary receipt SR of Modification 1-3. For example, the summary receipt output unit 103A determines whether the amount of each product is equal to or greater than a predetermined threshold. The summary receipt output unit 103A outputs a summary receipt SR so that products whose amounts are equal to or greater than a predetermined threshold are grouped together. The summary receipt output unit 103A outputs a summary receipt SR that includes the total amount of these products as one item.

In the example of FIG. 15, it is assumed that the predetermined threshold value is "10,000 yen". If a user purchases wine for 15,000 yen, a glass for 20,000 yen, and ``almonds'', ``cheese'', and ``chocolate'' for less than 10,000 yen, the summary The receipt output unit 103A calculates the total amount of "35,000 yen" of "15,000 yen" for wine and "20,000 yen" for a glass, and selects "35,000 yen" as the item of "luxury item". ,000 yen" is output.

The first configuration of Modified Example 1-3 is a summary receipt SR that is at least partially summarized so that items whose amounts meet a predetermined standard are summarized based on the amounts associated with each of the plurality of items. Output. As a result, a certain amount of information can be printed on the summary receipt SR, thereby further reducing the discomfort experienced by users who are not accustomed to the electronic receipt ER. As a result, the user can comfortably receive the summary receipt SR and read the two-dimensional code TC to use the electronic receipt ER, making the transition to the electronic receipt ER smoother.

[Modification 1-4]
For example, in the embodiment, a case has been described in which the summary settings for the summary receipt SR are common to all users, but each user may be able to specify the summary settings according to their own preferences. It's okay. For example, the user may specify whether to perform the summarization described in Modifications 1-1 to 1-3.

The summary receipt output unit 103A of Modification 1-4 obtains user settings related to the summary specified by the user based on the user ID that can identify the user who made the transaction, and outputs the summary receipt according to the obtained user settings. A summary receipt SR is output as a summary. In modification 1-4, it is assumed that user settings are stored in the user database DB1. For example, a user specifies user settings from a browser, points app, or other application.

The user settings are settings related to summarization. For example, user settings include items to be omitted in summary receipt SR, items not to be omitted in summary receipt SR, items to be summarized in summary receipt SR, items not to be summarized in summary receipt SR, summary method for summary receipt SR, or items to be summarized in summary receipt SR. It's the layout. In modification 1-4, a case will be exemplified in which the items that are not omitted in the summary receipt SR correspond to user settings. Items that are not omitted on the summary receipt SR are items that are printed on the summary receipt SR.

For example, assume that user X specifies user settings so that only the category "food and drink" is printed as product details on the summary receipt SR. In this case, the summary receipt output unit 103A outputs the summary receipt SR so that among the products purchased by the user, only products classified as "food and drink" are included in the product details. It is assumed that user Y has specified user settings so that only the category "stationery" is printed as a product detail on the summary receipt SR. In this case, the summary receipt output unit 103A outputs the summary receipt SR so that among the products purchased by the user, only products classified as "stationery" are included in the product details.

Note that the user settings are not limited to the above classifications. For example, the user settings may include whether to print at least one of the following items: store name, phone number, address, transaction date and time, receipt number, person in charge, total amount, deposit, change, amount eligible for points, and earned points. It may be For example, the user settings may be the arrangement of each item. In this case, the user can freely specify the layout of the summary receipt SR. For example, the user settings may be the summarization methods described in Modifications 1-1 to 1-3.

The first configuration of Modification 1-4 outputs the summary receipt SR so that the summary corresponds to the user settings acquired based on the user ID. Thereby, it is possible to output a summary receipt SR according to the user's preference, thereby increasing convenience for the user.

[Modification 1-5]
For example, in Modification 1-4, a case was explained where the user settings are specified so that the summary receipt SR is tailored to the user, but the store settings are specified so that the summary receipt SR is tailored to the store. It's okay. Store settings differ from user settings in that they are specified by the store, but are similar to user settings in other respects. For example, store settings may include items to be omitted in summary receipt SR, items not to be omitted in summary receipt SR, items to be summarized in summary receipt SR, items not to be summarized in summary receipt SR, summary method for summary receipt SR, or items to be summarized in summary receipt SR. It's the layout.

In modification 1-5, it is assumed that the store settings are stored in the store database DB2. For example, a store personnel operates the store terminal 20 to specify store settings. The summary receipt output unit 103A of modification 1-5 obtains the store settings regarding the summary specified by the store, and outputs the summary receipt SR so that the portions not included in the user settings are summarized according to the store settings. A summary receipt SR is output.

For example, assume that there are n (n is a natural number) setting items in the user settings and store settings. Assume that the user specifies only k out of n setting items (k is a natural number smaller than n). Furthermore, it is assumed that the person in charge of the store specifies all n setting items. In this case, the summary receipt output unit 103A outputs the summary receipt SR using the user settings for the k setting items and using the store settings for the remaining n−k setting items. For example, assume that only settings related to product details are specified in the user settings, and settings for other items such as store name are not specified. In this case, store settings are given priority for other items such as store name.

The first configuration of Modification 1-5 outputs the summary receipt SR so that the portion of the summary receipt SR that is not included in the user settings becomes a summary according to the store settings. As a result, the summary receipt SR can be output without the user having to specify user settings for all items, increasing convenience for the user. Since the store can output a summary receipt SR according to the user's preferences, the convenience of the store is increased.

[Modification 1-6]
For example, in Modification 1-5, an example was given in which the store settings compensate for the insufficiency of the user settings, but the user may not specify the user settings in the first place. In this case, the summary receipt SR may be output using only the store settings. In modification 1-6, it is assumed that the numerical value of k described in modification 1-5 is 0, and the user does not specify any setting item.

The summary receipt output unit 103A of Modification 1-6 obtains the store settings regarding the summary specified by the store, and if the user has not specified the user settings, the summary receipt output unit 103A obtains the store settings regarding the summary specified by the store. The summary receipt SR is output so that the summary is as follows. In Modification 1-4, we have explained the case where the summary receipt SR is output based on the user settings, but if the explanation of the user settings in Modification 1-4 is replaced with store settings, then the process is executed. good.

In the first configuration of Modification 1-6, if the user has not specified user settings, the summary receipt SR is output so that the summary corresponds to the store settings regarding the summary specified by the store. This makes it possible to output a summary receipt SR according to the store's preferences, thereby increasing the convenience of the store. Since the user can receive the summary receipt SR without specifying the user settings himself, the user's convenience is also improved.

[Modification 1-7]
For example, the barcode BC displayed on the point card screen SC1 may be a code for payment. The payment code is not limited to the barcode BC, but may be a two-dimensional code. On the user terminal 30 of Modification 1-7, a barcode BC for payment in which a temporary ID is encoded is displayed.

In Modification 1-7, when the barcode BC displayed on the user terminal 30 is read by the store terminal 20, payment processing regarding the transaction is executed. Various types of processing can be used for the payment processing itself. For example, point payment, credit card payment, electronic money payment, bank debit payment, or crypto asset payment may be executed. The payment process may be executed by the server 10 or by a server computer of an external payment service. It is assumed that payment information (credit card information, etc.) necessary for payment processing can be obtained based on the temporary ID.

The summary receipt output unit 103A of Modification 1-7 outputs the summary receipt SR based on the temporary ID obtained by reading the barcode BC displayed on the user terminal 30. This embodiment differs from the embodiment in that the barcode BC is a payment code, but the flow for outputting the summary receipt SR is similar to the embodiment.

The first configuration of Modification 1-7 outputs the summary receipt SR based on the temporary ID obtained by reading the payment barcode BC displayed on the user terminal 30. As a result, the payment process and the process for outputting the summary receipt SR and electronic receipt ER can be executed at the same time without having to read the code multiple times, increasing convenience for the user.

[Modification 1-8]
For example, in the embodiment, a case has been described in which the electronic receipt ER is output to a user who is a member of a point service, but the electronic receipt ER may be output to a user who is not a member of a point service. The data storage unit 100 of Modification 1-8 stores a transaction database for storing transaction data of transactions by users who are not members of the point service. The transaction database stores transaction IDs, transaction data, and electronic receipt data.

The electronic receipt data generation unit 102B of Modification 1-8 records the transaction ID and electronic receipt data in association with each other. The method of generating electronic receipt data itself may be the same as in the embodiment. The two-dimensional code TC of Modification 1-8 includes a transaction ID and a link regarding the electronic receipt. This link may be the URL explained in FIG. 8, or may be another URL. Furthermore, the link may be information that can identify a page within an application such as a point application, instead of a URL. For example, the transaction ID may not be an argument of the URL, but may be encoded as information separate from the URL. When the user terminal 30 reads the two-dimensional code TC, it transmits the transaction ID to the destination indicated by the link.

The electronic receipt output unit 103B of Modification 1-8 outputs an electronic receipt ER based on electronic receipt data associated with the transaction ID when the linked destination receives the transaction ID. In Modification 1-8, the link destination is assumed to be the server 10, but the link destination may be another computer other than the server 10. For example, the electronic receipt output unit 103B outputs an electronic receipt ER based on electronic receipt data associated with the received transaction ID in the transaction database. The output of the electronic receipt ER itself may be the same as in the embodiment.

In the first configuration of Modification 1-8, when a transaction ID is received from the user terminal 30, an electronic receipt ER is output based on electronic receipt data associated with the transaction ID. This allows the electronic receipt ER to be output to users who are not point card members, thereby increasing convenience for users who are not point card members.

[Modification 1-9]
For example, as in Modification 1-8, when outputting the electronic receipt ER to a user who is not a point card member, the user may be prompted to become a point card member. The receipt output system 1 of Modification 1-9 includes a membership registration determining section 106 and a membership registration section 107. The member registration determination unit 106 determines whether the user of the user terminal 30 has completed membership registration in the point service when the linked destination receives the transaction ID. In order to determine whether membership registration is complete, input of a user ID and password may be requested, or authentication information such as a temporary ID recorded in the point application may be used.

The point service is an example of a service related to the output of electronic receipts ER. This service may be a service other than a point service. This service may be any service that provides electronic receipt ER. For example, the other services may be a service solely for outputting electronic receipts ER, a payment service, an electronic commerce service, a financial service, a travel reservation service, or a communication service.

FIG. 16 is a diagram illustrating an example of how membership registration for a point service is prompted. If it is determined that membership registration for the point service is not completed, the member registration unit 107 prompts the user to register as a member for the point service. In the example of FIG. 16, the member registration unit 107 prompts member registration by displaying a message indicating that the user will become a member of the point service and a link to a page for member registration on the electronic receipt screen SC2. . Note that membership registration may be prompted on another screen instead of the electronic receipt screen SC2. For example, membership registration may be prompted without displaying the electronic receipt ER. In this case, a message may be displayed stating that if you become a member of the point service, you can display the electronic receipt ER.

The electronic receipt output unit 103B of Modification 1-9 outputs an electronic receipt when it is determined that membership registration for the service is completed. This process is as described in the embodiment. The electronic receipt screen SC2 in this case may be similar to the embodiment. Furthermore, in Modification 1-9, a benefit corresponding to the amount of reduction may be given to the user at the timing when it is determined that membership registration for the service is completed. In addition, in Modification 1-9, for the benefits granted at the timing when it is determined that the membership registration for the service is completed, in addition to the benefits according to the amount of reduction, it is possible to add the benefits according to the membership registration. .

The first configuration of Modification 1-9 prompts the user to register as a member of the point service when it is determined that membership registration of the point service is not completed. Thereby, the number of members of the point service can be increased by using the summary receipt SR.

[Modification 1-10]
For example, on the point card screen SC1, not only the transaction of the summary receipt SR on which the two-dimensional code TC is printed, but also the electronic receipt ER regarding the past transaction may be output. The receipt output system 1 includes a storage section 108. The storage unit 108 associates a user ID that can identify a user with electronic receipt data related to transactions made by the user in the past and stores them in the user database DB1. When a certain user uses a store and electronic receipt data is generated, the storage unit 108 stores the electronic receipt data in the user database DB1 in association with the temporary ID of this user. This process has been explained as a process of the electronic receipt data generation unit 102B in the embodiment, but will be explained as a process of the storage unit 108 in Modification 1-10.

When the two-dimensional code TC is read, the electronic receipt output unit 103B of modification 1-10 determines whether the user has read the two-dimensional code TC based on the electronic receipt data associated with the user ID of the user who has read the two-dimensional code TC. Outputs electronic receipts ER regarding past transactions. For example, the electronic receipt screen SC2 selectably displays not only transactions whose transaction IDs are encoded in the two-dimensional code TC, but also a list of past transactions by the same user. If the user has made multiple transactions in the past, the electronic receipt output unit 103B may output the electronic receipt ER of the transaction selected by the user. The electronic receipt ER for past transactions may be displayed from a screen other than the electronic receipt screen SC2.

The first configuration of Modification 1-10 is that when a two-dimensional code TC is read, based on the electronic receipt data associated with the user ID of the user who read the two-dimensional code TC, the user is Outputs an electronic receipt ER related to the transaction made. As a result, electronic receipts ER for past transactions can also be output, increasing user convenience.

[Modification 1-11]
For example, in the embodiment, a case has been described in which the summary receipt data is generated by the server 10, but the summary receipt data may also be generated by the store terminal 20. The store terminal 20 of each of the plurality of stores in Modification 1-11 includes a summary receipt output unit 201. The summary receipt output unit 201 of Modification 1-11 has the same function as the summary receipt data generation unit 102A described in the embodiment. Therefore, the summary receipt output unit 201 generates summary receipt data based on the transaction data.

For example, the summary receipt output unit 201 of each store terminal 20 of a plurality of stores generates a code so that links do not overlap with other stores, and outputs a paper receipt containing the generated code. For example, the link includes a store ID and a store terminal ID as arguments. Since these combinations do not overlap with other stores, the finally generated links also do not overlap with other stores. The link may be generated so as not to be confused with other stores, and may include only either the store ID or the store terminal ID.

In the first configuration of Modification 1-11, the two-dimensional code TC is generated by the store terminal 20 of each of the plurality of stores so that the links do not overlap with other stores. As a result, even if summary receipt data is generated at each store, the electronic receipt ER can be reliably output without duplication of links.

[Other variations regarding the first configuration]
For example, in the first configuration, at least one of the second configuration and the third configuration may be omitted. If the receipt output system 1 including the first configuration does not include the second configuration, the summary receipt SR is output without being awarded points according to the amount of reduction to the user.

For example, if the receipt output system 1 including the first configuration does not include the third configuration, the store terminal 20 may generate summary receipt data and electronic receipt data. In this case, the store terminal 20 includes the receipt data generation unit 102 described in the embodiment. The data storage unit 200 stores a summary receipt converter SRC and an electronic receipt converter ERC. The store terminal 20 transmits summary receipt data and electronic receipt data to the server 10. When the user presents a point card, the store terminal 20 also transmits a temporary ID to the server 10. The server 10 associates the temporary ID with the summary receipt data and the electronic receipt data and stores them in the user database DB1.

[5-2. Modification example regarding second configuration]
FIG. 17 is a diagram illustrating an example of functions realized by a modification of the second configuration. The cumulative amount updating section 109, the display control section 110, the location data acquisition section 111, and the travel route data acquisition section 112 are realized by the control section 11.

[Modification 2-1]
For example, even in the second configuration, user settings may be specified, as in Modification 1-4 of the first configuration. The reduction amount calculation unit 104 of Modification 2-1 calculates the reduction amount based on the transaction data and user settings. For example, the reduction amount calculation unit 104 obtains the paper consumption amount based on the user settings, and calculates the reduction amount based on the obtained paper consumption amount and the paper consumption amount according to the default settings. Calculate. The default setting may be a setting for outputting the normal receipt NR, or may be another setting corresponding to a receipt different from the normal receipt NR. Even in the case of other settings, the reduction amount calculation unit 104 may calculate the paper consumption amount using a converter for calculating the paper consumption amount according to other settings.

The second configuration of modification 2-1 calculates the reduction amount based on transaction data and user settings. As a result, users who want to increase the amount of paper they use can configure the user settings to create a simpler summary, and users who want to increase the amount of information in the summary receipt SR can configure the user settings to increase the amount of information. This makes it possible to improve user convenience. The simpler the summary receipt SR is, the greater the amount of reduction and the more points that can be earned, making the point awarding mechanism more interesting.

[Modification 2-2]
For example, in the embodiment, a case has been described where the summary receipt SR is output and the electronic receipt ER is output, but the electronic receipt ER may be output without paper receipts including the summary receipt SR being output. Good too. In modification 2-2, it is assumed that the user can select whether to output the summary receipt SR or the electronic receipt ER on the point application.

For example, the selection results by the user are stored in the user database DB1 as user settings. When the user presents the point card and uses the store, the receipt data generation unit 102 refers to the user database DB1 and obtains the selection result by the user. When the user selects the summary receipt SR, the summary receipt data generation unit 102A generates summary receipt data based on the transaction data. The processing in this case is as described in the embodiment.

For example, when the user selects the electronic receipt ER, the electronic receipt data generation unit 102B generates electronic receipt data based on the transaction data. The electronic receipt output unit 103B outputs an electronic receipt ER in response to a request from the user terminal 30. In this case, since the summary receipt SR described in the embodiment is not output, it is assumed that the electronic receipt ER can be displayed at any timing from the point application rather than by reading the two-dimensional code TC. For example, a list of past transactions of the user is displayed on the point application, and when the user selects any transaction, the electronic receipt ER of this transaction is displayed.

The reduction amount calculation unit 104 of Modification 2-2 calculates the consumption amount of the summary receipt SR, which is not actually output, as the reduction amount based on the transaction data. The reduction amount calculation unit 104 calculates the paper consumption amount of the summary receipt SR based on the transaction data. The reduction amount calculation unit 104 calculates the paper consumption amount of the summary receipt SR as the reduction amount. In the example of FIG. 3, the length L11 directly becomes the reduction amount. The length L21 of the normal receipt NR instead of the summary receipt SR may be used as the reduction amount.

In the second configuration of modification 2-2, an electronic receipt ER is output to the user, and based on the transaction data, the consumption amount of the summary receipt SR, which is not actually output, is calculated as the reduction amount. As a result, the amount of reduction can be increased without outputting the summary receipt SR, so that the points awarded to the user are more interesting. Since receipt paper can be effectively reduced, the burden on the global environment can be reduced.

[Modification 2-3]
For example, at a store, the user may be able to select whether or not to output a paper receipt. In Modification 2-3, the user selects whether or not to output a paper receipt. In Modification 2-3, a normal receipt NR will be explained as an example of a paper receipt, but the paper receipt may also be a summary receipt SR.

In modification 2-3, the receipt output system 1 does not include the function of outputting the electronic receipt ER and summary receipt SR. For example, the user selects whether or not to output the normal receipt NR on the point app. This selection result is stored in the user database DB1 as a user setting. Whether or not to output the normal receipt NR may be verbally communicated at the store or input to the store terminal 20 instead of being recorded as a user setting. In this case, data indicating the selection result as to whether or not to output the normal receipt NR is transmitted from the store terminal 20 to the server 10. Based on this data, the server 10 can determine whether or not to output the normal receipt NR.

For example, when a checkout operation is performed, the store terminal 20 transmits a temporary ID and transaction data to the server 10. Upon receiving the temporary ID and transaction data, the server 10 refers to the user settings stored in the user database DB1. When the user settings indicate that a normal receipt NR is to be output, the receipt data generation unit 102 generates normal receipt data of the normal receipt NR based on the transaction data. The receipt output unit 103 of the server 10 transmits normal receipt data to the store terminal 20. Upon receiving the normal receipt data, the store terminal 20 outputs a normal receipt NR.

For example, when the user settings indicate that the receipt NR is not normally output, the server 10 executes processing for the user to earn points and processing for storing transaction data in the user database DB1. In this case, the process of generating normal receipt data is not executed. Modification 2-3 does not support electronic receipt ER, so processing for generating electronic receipt data is not executed. Note that Modification 2-3 may also support electronic receipt ER, and in this case, electronic receipt data is generated and stored in user database DB1.

The reduction amount calculation unit 104 of Modification 2-3 calculates the consumption amount of the normal receipt NR, which is not actually output, as the reduction amount, based on the transaction data when it is selected not to output the normal receipt NR. do. The method for calculating this reduction amount may be the same as in Modification 2-2. The benefit granting unit 105 grants points to the user based on the amount of reduction when it is selected not to output a paper receipt. The process itself of awarding points according to the amount of reduction is the same as described in the embodiment.

In the second configuration of Modified Example 2-3, when it is selected not to output the normal receipt NR, the consumption amount of the normal receipt NR that is not actually output is calculated as the reduction amount based on the transaction data. , give points to the user. As a result, the amount of reduction can be increased without outputting the normal receipt NR, thereby increasing the interest in points awarded to the user. Since receipt paper can be effectively reduced, the burden on the global environment can be reduced.

[Modification 2-4]
For example, as described in the embodiment, the reduction amount calculation unit 104 calculates the first consumption amount of the normal receipt NR that is not actually output and the second consumption amount of the summary receipt SR that is actually output based on the transaction data. The difference between the amount and the amount may be calculated as the amount of reduction. The first consumption amount may not be the normal receipt NR, but may be the consumption amount of the summary receipt SR according to the user settings of another user, or the consumption amount of the summary receipt SR according to the default settings. good. The first consumption amount may be a predetermined consumption amount that is a comparison standard with the second consumption amount. The second consumption amount is the consumption amount of the summary receipt SR described in the embodiment.

The second configuration of Modified Example 2-4 is based on the transaction data, the difference between the first consumption amount of the normal receipt NR that is not actually output and the second consumption amount of the summary receipt SR that is actually output. is calculated as the amount of reduction. This allows the amount of reduction to be calculated accurately.

[Modification 2-5]
For example, in the embodiment, the length L0 is calculated as the reduction amount as described with reference to FIG. The amount is obtained as the first consumption amount, the amount of the second character string in the summary receipt SR that is actually output is obtained as the second consumption amount, and the amount of the first character string and the amount of the second character string are obtained. The reduction amount may be calculated as the difference between and.

The amount of character strings is the number of characters or lines. In modification 2-5, a case where the number of lines corresponds to the amount of character strings will be exemplified. When reducing the number of paper receipts by outputting the summary receipt SR as in the embodiment, the reduction amount calculation unit 104 calculates the number of lines in the first row, which is the number of lines when it is assumed that the normal receipt NR is output. calculate numbers. The reduction amount calculation unit 104 calculates a second number of lines, which is the number of lines in the summary receipt SR. The reduction amount calculation unit 104 calculates the number of lines obtained by subtracting the second number of lines from the first number of lines as the reduction amount.

The second configuration of Modified Example 2-5 obtains the amount of the first character string in the normal receipt NR that is not actually output as the first consumption amount, and obtains the amount of the first character string in the summary receipt SR that is actually output. is obtained as the second consumption amount, and the difference between the amount of the first character string and the amount of the second character string is calculated as the amount of reduction. This allows the amount of reduction to be calculated accurately.

[Modification 2-6]
For example, the paper receipt may have a width depending on the store or the store terminal 20 of the store. In this case, the reduction amount calculation unit 104 calculates the reduction amount based on the transaction data and the width. When receiving transaction data from a store terminal 20 of a certain store, the reduction amount calculation unit 104 refers to the store database DB2 and acquires the width indicated by the receipt paper information associated with this store or store terminal 20. The reduction amount calculation unit 104 calculates the reduction amount based on the obtained width. For example, the reduction amount calculation unit 104 calculates the area obtained by multiplying the obtained width by the length L0 described as the reduction amount in the embodiment as the reduction amount.

The second configuration of Modification 2-6 calculates the reduction amount based on the transaction data and the width of the receipt paper depending on the store or store terminal 20. In this way, for example, the reduction amount is calculated such that the longer the width, the greater the reduction amount, so the reduction amount of the receipt paper can be calculated accurately.

[Modification 2-7]
For example, the paper receipt may be of a type depending on the store or the store terminal 20. The type of paper receipt refers to the paper quality. It is assumed that the type of paper receipt is indicated in the receipt paper information of the store database DB2. It is assumed that data indicating the relationship between the type of paper receipt and the points given to the user is stored in the data storage unit 100. This data may be in mathematical formula form, table form, or program code.

The benefit granting unit 105 of Modification 2-7 grants points to the user based on the amount of reduction and the type of paper receipt. The benefit granting unit 105 determines points to be given to the user based on the reduction amount, the type of paper receipt, and data indicating the above relationship. For example, the benefit award unit 105 awards points to the user such that the higher the paper quality indicated by the type of paper receipt, the more points are awarded. The benefit award unit 105 awards points to the user in such a way that the better the material indicated by the type of paper receipt, the more points are awarded.

In the second configuration of Modification 2-7, points are awarded to the user based on the amount of reduction and the type of paper receipt depending on the store or store terminal 20. As a result, it is possible to motivate the user to use the store or the store terminal 20 that has introduced paper receipts so that more points can be earned, thereby increasing the user's interest.

[Modification 2-8]
For example, in the electronic receipt screen SC2 of FIG. 4, only the reduction amount in one transaction is displayed, but the past accumulated amount by the user may be displayed. It is assumed that the user database DB1 of Modification 2-8 stores not only the reduction amount in each transaction but also the cumulative amount. In Modification 2-8, a case will be described in which the entire past period is the target for calculating the cumulative amount, but the period for calculating the tracking amount may be any period. For example, the period for which the cumulative value is calculated may be a partial period in the past. This period may be the most recent period, or may be a past period that does not include the most recent period.

The receipt output system 1 of Modification 2-8 includes a cumulative amount updating section 109 and a display control section 110. The cumulative amount updating unit 109 updates the cumulative amount regarding paper receipt reduction based on the reduction amount. For example, when the reduction amount calculating section 104 calculates the reduction amount, the cumulative amount updating unit 109 updates the cumulative amount by adding the reduction amount to the cumulative amount stored in the user database DB1. The display control unit 110 causes the user terminal 30 to display the cumulative amount. In modification 2-8, a case will be exemplified in which the cumulative amount is displayed on a cumulative amount screen different from the electronic receipt screen SC2. Refer to the user database DB1 to obtain the cumulative amount of users. The display control unit 110 causes the display unit 35 to display a cumulative amount screen including the acquired cumulative amount.

The benefit granting unit 105 of Modification 2-8 grants points to the user based on the cumulative amount corresponding to the reduction amount. It is assumed that data regarding the relationship between the cumulative amount and the points given to the user is stored in the data storage unit 100 in advance. This data may be in any format, such as mathematical formulas, tables, or program code. The benefit granting unit 105 grants points associated with the cumulative amount updated by the cumulative amount updating unit 109 to the user. For example, the benefit granting unit 105 grants points to the user in such a manner that the greater the accumulated amount, the more points are awarded. The benefit granting unit 105 may grant points associated with the threshold to the user each time the cumulative amount is equal to or greater than the threshold.

In the second configuration of Modification 2-8, points are awarded to the user based on the cumulative amount corresponding to the reduction amount. This further increases the interest in the points given to the user.

[Modification 2-9]
For example, points may be awarded based not only on the amount of paper saved but also on the location of the store. The data storage unit 100 of Modification 2-9 stores a store database DB2 regarding each of a plurality of stores. It is assumed that the store database DB2 stores location data regarding store locations. The location data may be any data that can identify a location on the earth, such as an address or latitude and longitude. The location data need not indicate a pinpoint location, but may indicate a general area.

The receipt output system 1 of Modification 2-9 includes a location data acquisition unit 111. The location data acquisition unit 111 acquires location data regarding the location of the store. For example, the location data acquisition unit 111 refers to the store database DB2 and acquires the location data of the store of the store terminal 20 that transmitted the transaction data. The benefit granting unit 105 grants points to the user based on the reduction amount and location data.

It is assumed that data indicating the relationship between the amount of reduction, the location of the store, and the points awarded is stored in the data storage unit 100. This data may be in mathematical formula form, table form, or program code. The benefit granting unit 105 determines points to be given to the user based on the reduction amount, the location of the store, and the data indicating the above relationship, and gives the points to the user. For example, the formula for calculating points from the amount of reduction may vary depending on the location of the store.

For example, the benefit award unit 105 may award points to the user such that the more paper receipts consumed at the location indicated by the location data, the more points are awarded. It is assumed that the amount of paper receipts consumed at each location is counted each time a paper receipt is output from the output device 27 of the store terminal 20. In this way, more points can be awarded to users who reduce the output of paper receipts in areas where paper receipt consumption is high.

In the second configuration of Modification 2-9, points are awarded to the user based on the reduction amount and store location data. This makes the points awarded to the user more interesting.

[Modification 2-10]
For example, the benefit granting unit 105 may grant points to the user based on a cumulative amount corresponding to the amount of reduction by the user during a specific period. This period may be the entire past period or a part of the most recent period. In modification 2-10, it is assumed that the specific period is a campaign period in a point service. The cumulative amount explained in Modification 2-8 is the total value of the reduction amount during the campaign period.

For example, the benefit granting unit 105 determines the extent to which the user has contributed to the reduction of paper receipts using the electronic receipt ER or the summary receipt SR, based on the accumulated amount in a specific period. The benefit granting unit 105 grants points to the user in such a manner that the larger the cumulative amount, the more points are awarded. For example, the benefit granting unit 105 may grant points to the user depending on the period or number of times the user continuously issues the electronic receipt ER or summary receipt SR.

In the second configuration of Modification 2-10, points are awarded to the user based on the accumulated amount according to the amount of reduction by the user in a specific period. This further increases the interest in the points given to the user.

[Modification 2-11]
For example, points may be awarded not only based on the amount of paper saved, but also based on the travel route to the store. The receipt output system 1 of Modification 2-11 includes a travel route data acquisition section 112. The travel route data acquisition unit 112 acquires travel route data regarding the travel route taken by the user to the store. The method of acquiring the movement route itself may be any method. In Modification 2-11, a case will be described in which GPS is used, but a method using GNSS other than GPS, a mobile base station, or a wireless LAN access point may also be used.

For example, the user terminal 30 acquires current location data regarding the user's current location based on a detection signal from a GPS sensor of the user terminal 30. The user terminal 30 repeatedly acquires current position data and sequentially transmits the current position data to the server 10. The travel route data acquisition unit 112 acquires travel route data based on current position data received one after another from the user terminals 30. The travel route data may be generated not on the server 10 side but on the user terminal 30 side. In this case, the user terminal 30 transmits movement route data to the server 10. The travel route data acquisition unit 112 acquires travel route data from the user terminal 30.

The benefit granting unit 105 grants a benefit to the user based on the amount of reduction and the travel route data. It is assumed that data regarding the relationship between the amount of reduction, the travel route, and the points given to the user is stored in the data storage unit 100 in advance. This data may be in any format, such as mathematical formulas, tables, or program code.

For example, the benefit granting unit 105 grants points associated with the amount of reduction and the travel route to the user. For example, the benefit award unit 105 awards points to the user such that the shorter the travel route, the more points are awarded. For example, if the travel route is on a road and it is detected that the traveler traveled at a speed such as walking or cycling, the benefit granting unit 105 grants the benefit more than if the travel route is on a road and the traveler travels at a speed such as walking or cycling, rather than if the travel route is on a road, and the traveler travels at a speed such as walking or cycling. Points may be awarded to the user so that the number of points earned increases.

In the second configuration of Modification 2-11, points are awarded to the user based on the reduction amount and travel route data regarding the user's travel route to the store. This further increases the interest in the points given to the user.

[Modification 2-12]
For example, the user may select whether or not to include additional additional information on the paper receipt. The additional information is not information indicating the details of the transaction itself, but information that is output together with the details of the transaction. In Modification 2-12, a case will be described in which an advertisement corresponds to additional information, but the additional information may be other information such as a coupon, for example. It is assumed that the data necessary for outputting the additional information is stored in the data storage section 100 or the data storage section 200. What additional information is output may be determined in advance, or may be determined according to the user's transaction.

If the user selects to include additional information, the reduction amount calculation unit 104 of Modification Example 2-12 calculates the reduction amount without regarding the additional information portion as having consumed the paper receipt. . The length of the advertisement portion, which is additional information, of the summary receipt SR is not counted as the consumption amount of paper receipts. The reduction amount calculation unit 104 counts the length of the portion of the summary receipt SR other than the advertisement, which is additional information, as the consumption amount of paper receipts.

In the second configuration of Modification 2-12, when the user selects to include additional information, the reduction amount is calculated for the additional information portion without considering that the paper receipt has been consumed. This can prevent points from being lowered for users who view additional information such as advertisements.

[Other variations regarding the second configuration]
For example, in the second configuration, at least one of the first configuration and the third configuration may be omitted. When the receipt output system 1 including the second configuration does not include the first configuration, points are given to the user according to the amount of reduction without outputting the summary receipt SR. For example, if the receipt output system 1 including the second configuration does not include the third configuration, the store terminal 20 may generate receipt data and output the receipt. In this case, the store terminal 20 includes the receipt data generation unit 102 described in the embodiment. Data storage unit 200 stores converters. Furthermore, the second configuration does not need to include a function related to receipt output. In this case, the benefit award system according to the second configuration may have only the function of awarding points, and the receipt output may be executed by an external system.

[5-3. Modification example regarding third configuration]
A modification regarding the third configuration will be described.

[Modification 3-1]
For example, even in the third configuration, user settings may be specified, as in Modification 1-4 of the first configuration or Modification 2-1 of the second configuration. The receipt data generation unit 102 of Modified Example 3-1 acquires user settings specified by the user based on the user ID, and generates receipt data based on the acquired user settings and transaction data. do. The flow of generating this receipt data is as explained in Modification 1-4.

The receipt in Modification 3-1 is a summary receipt SR regarding a summary of a transaction, which is output on paper at a store. User settings are settings related to summaries. The receipt data generation unit 102 generates receipt data such that the summary corresponds to user settings. The receipt data of the summary receipt SR is as described in the embodiment. Note that the user settings are not limited to settings related to summaries. The user settings may be the presence or absence of additional information described in Modification 2-12, or may be the various settings described above.

The third configuration of Modified Example 3-1 generates receipt data based on user ID, user settings specified by the user, and transaction data. Thereby, it is possible to output a summary receipt SR according to the user's preference, thereby increasing convenience for the user.

Further, the third configuration generates receipt data so as to have a summary according to user settings. This makes it possible to create a summary according to the user's preferences.

[Modification 3-2]
For example, in the third configuration, the same store settings as in Modification 1-5 of the first configuration may be specified. As described in the embodiment, the transaction data acquisition unit 101 acquires a store ID or store terminal ID that can identify a store or store terminal 20, and a user ID from each store terminal 20 of a plurality of stores. . In this case, the receipt data generation unit 102 acquires the store settings related to the summary specified by the store identified by the store ID or store terminal ID, and the portion of the summary receipt SR that is not included in the user settings is Receipt data may be generated to provide a summary according to the settings. This process is as described in Modification 1-5.

The third configuration of Modified Example 3-2 acquires the store settings specified by the store identified by the store ID or store terminal ID, and the portion of the summary receipt SR that is not included in the user settings is stored in the store settings. Generate receipt data so that it becomes a summary according to. As a result, the summary receipt SR can be output without the user having to specify user settings for all items, increasing convenience for the user. Since the store can output a summary receipt SR according to the user's preferences, the convenience of the store is increased.

[Modification 3-3]
For example, the user settings may indicate whether to output a summary receipt SR or a regular receipt that contains more information regarding transactions than the summary receipt SR. The receipt data generation unit 102 generates summary receipt data when the user settings indicate that a summary receipt is to be output, and generates normal receipt data when the user settings indicate that a normal receipt is to be output. The flow of generating summary receipt data and normal receipt data is as described above.

In the third configuration of Modification 3-3, if the user settings indicate that the summary receipt SR is to be output, summary receipt data is generated, and if the user settings indicate that the normal receipt NR is to be output, the normal receipt data is generated. generate. With this, it is possible to output a receipt according to the user's preference, thereby increasing the user's convenience.

[Modification 3-4]
For example, in the third configuration as well, as in Modification 2-12 of the second configuration, the user settings may indicate whether or not additional information regarding the transaction is included in the receipt. If the user settings indicate that the additional information is not included in the receipt, the receipt data generation unit 102 generates receipt data so that the additional information is not included in the receipt, and if the user settings indicate that the additional information is not included in the receipt. If so, the receipt data is generated so that the additional information is included in the receipt. This process is as described in Modification 2-12.

The third configuration of Modified Example 3-4 generates receipt data and includes the additional information in the receipt so that the additional information is not included in the receipt when the user settings indicate that the additional information is not included in the receipt. If the user settings indicate this, the receipt data is generated so that the additional information is included in the receipt. With this, it is possible to output a receipt according to the user's preference, thereby increasing the user's convenience.

[Modification 3-5]
For example, if user settings are specified, a common converter may be used for portions of the receipt that are common to other users. In this case, an individual converter may be used to perform processing according to user settings. For example, at least one of the summary receipt converter SRC and the electronic receipt converter ERC may include a common converter that performs common processing for all users and individual converters that perform individual processing according to user settings. good. For these converters, encoding processing and information arrangement processing may be defined.

The receipt data generation unit 102 of Modified Example 3-5 generates intermediate receipt data by executing common processing common to other users different from the user based on the transaction data, and generates intermediate receipt data based on the transaction data. Receipt data is generated by executing individual processing according to user settings based on intermediate receipt data. For example, the receipt data generation unit 102 executes a common information arrangement process as a common process for parts of the receipt that are common to all users (for example, store name, telephone number, and address). The receipt data generation unit 102 generates receipt data by executing individual information arrangement processing as individual processing for a portion of the receipt (for example, product details) that corresponds to each user.

The third configuration of Modified Example 3-5 generates intermediate receipt data by executing common processing common to other users different from the user based on transaction data, and Receipt data is generated by executing individual processing according to user settings based on the receipt data. Thereby, the process of generating receipt data can be made more efficient.

[Modification 3-6]
For example, in the third configuration as well, as in Modification 1-7 of the first configuration, a barcode BC for payment in which a temporary ID is encoded may be displayed on the user terminal 30. When the barcode BC is read by the store terminal 20, payment processing for the transaction is executed. The transaction data acquisition unit 101 acquires a temporary ID and transaction data when the barcode BC is read. These series of processes are as described in Modification 1-7.

In the third configuration of modification 3-6, when the barcode BC for payment displayed on the user terminal 30 is read, a temporary ID and transaction data are acquired. As a result, the payment process and the process for outputting the receipt can be executed at the same time without having to read the document multiple times, increasing convenience for the user.

[Modification 3-7]
For example, in Modification 3-1, a case has been described in which the receipt is personalized by the user specifying user settings, but the receipt may also be automatically personalized based on the user's past transactions. . In modification 3-7, transaction data in past transactions stored in the user database DB1 is referred to as past data.

The receipt data generation unit 102 of Modification 3-7 acquires past data regarding past transactions performed by the user based on the temporary ID, and based on the acquired past data and transaction data, Generate receipt data so that receipts are personalized according to past transactions. For example, the receipt data generation unit 102 identifies products that users often purchase based on past data, and generates summary receipt data so that the identified products are summarized. For example, the receipt data generation unit 102 calculates the average price of products purchased by the user based on past data, and generates summary receipt data so that products whose price is equal to or more than the calculated average price are summarized. generate.

The third configuration of Modified Example 3-7 is based on past data regarding past transactions performed by the user and transaction data, so that the receipt data is personalized according to the past transactions. generate. As a result, a receipt corresponding to the user's past transactions is output, thereby increasing convenience for the user.

[Modification 3-8]
For example, the personalization in Modification 3-7 may be performed based on past transactions in services other than point services. A case will be described in which the past data in Modification 3-8 is data related to past transactions performed by the user in a payment service different from the point service. The point service is an example of the first service. The payment service is an example of the second service. Therefore, the portion described as "point service" can be read as "first service". The portion described as payment service can be read as second service.

The first service is a service related to receipt output. The second service is a different service from the first service. The combination of the first service and the second service may be any combination. For example, the first service may be an electronic receipt service and the second service may be an electronic commerce service. For example, the first service may be a payment service and the second service may be a communication service.

The receipt data generation unit 102 of Modification 3-8 generates receipt data so that the receipt is personalized according to past transactions in the payment service. This differs from Modification 3-7 in that past transactions in the payment service are used, but is similar to Modification 3-7 in other respects.

In the third configuration of Modification 3-8, receipt data is generated so that the receipt is personalized according to past transactions in a payment service different from the point service. As a result, a receipt corresponding to the user's past transactions is output, thereby increasing convenience for the user. For example, even if a user has only a short history of using point services, if the user has a long history of using payment services, optimal personalization can be achieved based on sufficient past data.

[Modification 3-9]
For example, the user may be able to specify user settings for each store. It is assumed that the user database DB1 of Modification 3-9 stores user settings for each store. The user can make the first user settings for the first store and the second user settings for the second store different from each other. The content of each user setting may be the content of the modified example described above. The transaction data acquisition unit 101 of Modification 3-9 acquires a store ID or store terminal ID, and a temporary ID from each store terminal 20 of a plurality of stores.

The receipt data generation unit 102 of Modification 3-9 acquires the user settings specified for the store identified by the store ID or store terminal ID, and generates the user settings based on the acquired user settings and transaction data. and generate receipt data. Receipt data is generated based on the user settings specified for the store of the store terminal 20 that transmitted the transaction data etc. among the user settings of the users stored in the user database DB1. This process differs from the process described above in that user settings depending on the store are used, but is similar in other respects.

The third configuration of Modification 3-9 generates receipt data based on transaction data and user settings specified for the store identified by the store ID or store terminal ID. As a result, it is possible to output a receipt according to the store, increasing convenience for the user.

[Other variations regarding the third configuration]
For example, in the third configuration, at least one of the first configuration and the second configuration may be omitted. If the receipt output system 1 including the third configuration does not include the first configuration, electronic receipt data is generated on the server 10 side without outputting the summary receipt SR to the user. For example, the two-dimensional code TC may be printed on the regular receipt NR instead of the summary receipt SR. When the receipt output system 1 including the third configuration does not include the second configuration, receipt data is generated on the server 10 side without being awarded points according to the amount of reduction to the user.

For example, summary receipt data may be generated on the store terminal 20 side, and electronic receipt data may be generated on the server 10 side. In this case, the server 10 generates information regarding the URL to be included in the two-dimensional code TC, and transmits it to the store terminal 20. Upon receiving this information, the store terminal 20 may generate summary receipt data based on this information and transaction data and output the summary receipt SR. In the third configuration, the store terminal 20 that outputs the normal receipt NR and the store terminal 20 that outputs the summary receipt SR may coexist.

[5-4. Other variations]
For example, the modifications described above may be combined.

For example, although the case where the receipt output system 1 is applied to a point service is given as an example, the receipt output system 1 can be applied to any other arbitrary service. For example, the receipt output system 1 may be applied to an electronic receipt service that outputs an electronic receipt ER, a retail service, a food and drink provision service at a restaurant, a payment service, an electronic commerce service, a travel reservation service, or a communication service. For example, the store where the receipt is output may be an online store.

For example, the functions described as being implemented by the server 10 may be implemented by the store terminal 20, the user terminal 30, or another computer. For example, functions described as being implemented by one computer may be shared among multiple computers. Each function may be realized by at least one computer.

[6. Additional notes]
For example, the receipt output system can also have the following configuration.
(1)
a transaction data acquisition unit that acquires transaction data regarding the details of transactions conducted at the store;
an electronic receipt data generation unit that generates electronic receipt data regarding the electronic receipt of the transaction based on the transaction data;
a paper receipt output unit that outputs a paper receipt related to a summary of the transaction, including a code related to the output of the electronic receipt, based on the transaction data;
an electronic receipt output unit that outputs the electronic receipt based on the electronic receipt data when the code is read by a user terminal;
Receipt output system including.
(2)
The paper receipt output unit outputs the paper receipt in which at least some of the plurality of items included in the electronic receipt are omitted.
The receipt output system described in (1).
(3)
The paper receipt output unit outputs the paper receipt in which at least some of the plurality of items included in the electronic receipt are summarized.
The receipt output system according to (1) or (2).
(4)
The paper receipt output unit outputs the at least partially summarized paper receipt, based on the classification associated with each of the plurality of items, so that the items of the same classification are grouped together.
The receipt output system described in (3).
(5)
The paper receipt output unit outputs the at least partially summarized paper receipt so that the items whose usage frequency satisfies a predetermined criterion are summarized based on the usage frequency associated with each of the plurality of items. output a receipt,
The receipt output system according to (3) or (4).
(6)
The paper receipt output unit outputs the at least partially summarized paper receipt, based on the amount associated with each of the plurality of items, so that the items whose amounts meet a predetermined criterion are grouped together. Output,
The receipt output system according to any one of (3) to (5).
(7)
The paper receipt output section is
Obtaining user settings regarding the summary specified by the user based on user identification data that can identify the user who made the transaction;
outputting the paper receipt so that the summary corresponds to the acquired user settings;
The receipt output system according to any one of (1) to (6).
(8)
The paper receipt output section is
obtaining store settings regarding the summary specified by the store;
Outputting the paper receipt so that the portion of the paper receipt that is not included in the user settings becomes the summary according to the store setting;
The receipt output system described in (7).
(9)
The paper receipt output section is
obtaining store settings regarding the summary specified by the store;
If the user has not specified the user settings, outputting the paper receipt so that the summary corresponds to the store settings regarding the summary specified by the store;
The receipt output system according to (7) or (8).
(10)
A payment code encoded with the user identification data is displayed on the user terminal of the user;
When the code displayed on the user terminal is read by a store terminal of the store, a payment process regarding the transaction is executed;
The paper receipt output unit outputs the paper receipt based on the user identification data obtained by reading the code displayed on the user terminal.
The receipt output system according to any one of (7) to (9).
(11)
The electronic receipt data generation unit records transaction identification data that can identify the transaction and the electronic receipt data in association with each other,
The code includes the transaction identification data and a link regarding the electronic receipt,
When the user terminal reads the code, the user terminal transmits the transaction identification data to a link destination indicated by the link,
The electronic receipt output unit outputs the electronic receipt based on the electronic receipt data associated with the transaction identification data when the linked destination receives the transaction identification data.
The receipt output system according to any one of (1) to (10).
(12)
The receipt output system is
a membership registration determination unit that determines whether the user of the user terminal has completed membership registration for the service related to outputting the electronic receipt when the linked destination receives the transaction identification data;
a membership registration unit that prompts the user to register as a member of the service when it is determined that the membership registration of the service is not completed;
further including;
The electronic receipt output unit outputs the electronic receipt when it is determined that membership registration for the service is completed.
The receipt output system described in (11).
(13)
The receipt output system further includes a storage unit that associates user identification data that can identify the user who made the transaction with the electronic receipt data related to transactions made by the user in the past and stores the association in a database;
When the code is read, the electronic receipt output unit generates an electronic receipt related to a transaction made by the user in the past based on the electronic receipt data associated with the user identification data of the user who read the code. output,
The receipt output system according to any one of (1) to (12).
(14)
Each store terminal of the plurality of stores includes the paper receipt output unit,
The paper receipt output unit of the store terminal of each of the plurality of stores generates the code so that the link does not overlap with other stores, and outputs the paper receipt including the generated code. ,
The receipt output system according to any one of (1) to (13).

1 Receipt output system, N network, 10 Server, 11, 21, 31 Control unit, 12, 22, 32 Storage unit, 13, 23, 33 Communication unit, 20 Store terminal, 30 User terminal, 24, 34 Operation unit, 25 , 35 display section, 26 reading device, 27 output device, 36 reading section, BC barcode, ER electronic receipt, NR normal receipt, SR summary receipt, TC two-dimensional code, 100 data storage section, 101 transaction data acquisition section, 102 Receipt data generation section, 102A Summary receipt data generation section, 102B Electronic receipt data generation section, 103 Receipt output section, 103A Summary receipt output section, 103B Electronic receipt output section, 104 Reduction amount calculation section, 105 Benefit granting section, 106 Membership registration Judgment unit, 107 Member registration unit, 108 Storage unit, 109 Cumulative amount update unit, 110 Display control unit, 111 Location data acquisition unit, 112 Travel route data acquisition unit, 200 Data storage unit, 201 Summary receipt output unit, 300 Data storage Section, 301 Electronic receipt output section, DB1 user database, DB2 store database, ERC electronic receipt converter, SRC summary receipt converter, FER, FSR format, SC1 point card screen, SC2 electronic receipt screen.

Claims (15)

a transaction data acquisition unit that acquires transaction data regarding the details of transactions conducted at the store;
an electronic receipt data generation unit that generates electronic receipt data regarding the electronic receipt of the transaction based on the transaction data;
Based on user identification data that can identify the user who made the transaction, obtain the user settings specified by the user regarding items to be omitted or not omitted in the paper receipt related to the summary of the transaction; The summary in which the item corresponding to the acquired user setting is omitted and other items are printed, or the summary in which the item corresponding to the acquired user setting is printed and other items are omitted. a paper receipt output unit that outputs the paper receipt including a code related to the output of the electronic receipt based on the transaction data so as to be a summary ;
an electronic receipt output unit that outputs the electronic receipt based on the electronic receipt data when the code is read by a user terminal;
Receipt output system including. The paper receipt output unit outputs the paper receipt in which at least some of the plurality of items included in the electronic receipt are omitted.
The receipt output system according to claim 1. The paper receipt output unit outputs the paper receipt in which at least some of the plurality of items included in the electronic receipt are summarized.
The receipt output system according to claim 1 or 2. The paper receipt output unit outputs the at least partially summarized paper receipt, based on the classification associated with each of the plurality of items, so that the items of the same classification are grouped together.
The receipt output system according to claim 3. The paper receipt output unit outputs the at least partially summarized paper receipt so that the items whose usage frequency satisfies a predetermined criterion are summarized based on the usage frequency associated with each of the plurality of items. output a receipt,
The receipt output system according to claim 3. The paper receipt output unit outputs the at least partially summarized paper receipt, based on the amount associated with each of the plurality of items, so that the items whose amounts meet a predetermined criterion are grouped together. Output,
The receipt output system according to claim 3. The paper receipt output section is
obtaining store settings regarding the summary specified by the store;
Outputting the paper receipt so that the portion of the paper receipt that is not included in the user settings becomes the summary according to the store setting;
The receipt output system according to claim 1 or 2 . The paper receipt output section is
obtaining store settings regarding the summary specified by the store;
If the user has not specified the user settings, outputting the paper receipt so that the summary corresponds to the store settings regarding the summary specified by the store;
The receipt output system according to claim 1 or 2 . A payment code encoded with the user identification data is displayed on the user terminal of the user;
When the code displayed on the user terminal is read by a store terminal of the store, a payment process regarding the transaction is executed;
The paper receipt output unit outputs the paper receipt based on the user identification data obtained by reading the code displayed on the user terminal.
The receipt output system according to claim 1 or 2 . The electronic receipt data generation unit records transaction identification data that can identify the transaction and the electronic receipt data in association with each other,
The code includes the transaction identification data and a link regarding the electronic receipt,
When the user terminal reads the code, the user terminal transmits the transaction identification data to a link destination indicated by the link,
The electronic receipt output unit outputs the electronic receipt based on the electronic receipt data associated with the transaction identification data when the linked destination receives the transaction identification data.
The receipt output system according to claim 1 or 2. The receipt output system is
a membership registration determination unit that determines whether the user of the user terminal has completed membership registration for the service related to outputting the electronic receipt when the linked destination receives the transaction identification data;
a membership registration unit that prompts the user to register as a member of the service when it is determined that the membership registration of the service is not completed;
further including;
The electronic receipt output unit outputs the electronic receipt when it is determined that membership registration for the service is completed.
The receipt output system according to claim 10 . The receipt output system further includes a storage unit that associates user identification data that can identify the user who made the transaction with the electronic receipt data related to transactions made by the user in the past and stores the association in a database;
When the code is read, the electronic receipt output unit generates an electronic receipt related to a transaction made by the user in the past based on the electronic receipt data associated with the user identification data of the user who read the code. output,
The receipt output system according to claim 1 or 2. Each store terminal of the plurality of stores includes the paper receipt output unit,
The paper receipt output unit of the store terminal of each of the plurality of stores generates the code so that links do not overlap with other stores, and outputs the paper receipt including the generated code. ,
The receipt output system according to claim 1 or 2. The computer is
a transaction data acquisition step of acquiring transaction data regarding the details of transactions conducted at the store;
an electronic receipt data generation step of generating electronic receipt data regarding an electronic receipt of the transaction based on the transaction data;
Based on user identification data that can identify the user who made the transaction, obtain the user settings specified by the user regarding items to be omitted or not omitted in the paper receipt related to the summary of the transaction; The summary in which the item corresponding to the acquired user setting is omitted and other items are printed, or the summary in which the item corresponding to the acquired user setting is printed and other items are omitted. a paper receipt outputting step of outputting the paper receipt including a code related to outputting the electronic receipt based on the transaction data so as to be a summary;
an electronic receipt output step of outputting the electronic receipt based on the electronic receipt data when the code is read by a user terminal;
Receipt output method to execute . a transaction data acquisition unit that acquires transaction data regarding the details of transactions conducted at the store;
an electronic receipt data generation unit that generates electronic receipt data regarding an electronic receipt of the transaction based on the transaction data;
Based on user identification data that can identify the user who made the transaction, obtain the user settings specified by the user regarding items to be omitted or not omitted in the paper receipt related to the summary of the transaction; The summary in which the item corresponding to the acquired user setting is omitted and other items are printed, or the summary in which the item corresponding to the acquired user setting is printed and other items are omitted. a paper receipt output unit that outputs the paper receipt including a code related to the output of the electronic receipt based on the transaction data so as to be a summary ;
an electronic receipt output unit that outputs the electronic receipt based on the electronic receipt data when the code is read by a user terminal;
A program that allows a computer to function as a computer.