JP2014132498A - Commodity transaction data processor and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To enable a print format of a printed and issued receipt to be changed in response to each transaction while reducing the size of the receipt.SOLUTION: A commodity transaction data processor in this embodiment includes: an input part for inputting a commodity code corresponding to each commodity; generation means for generating transaction data including a total amount in one transaction on the basis of the commodity code input by the input part; first determination means for determining whether predetermined prescribed conditions concerning a receipt issue are satisfied; and a printing part for issuing the receipt which is printed in a first printing form including the total amount in the one transaction generated by the generation means and information showing disclosure destination of the transaction data in the one transaction when the first determination means determines that the prescribed conditions are satisfied.

Description

Embodiments described herein relate generally to a merchandise sales data processing apparatus and program used for settlement of merchandise transactions.

When a transaction is made between a store and a customer, for example, a receipt paper on which the sales data sold in this transaction is printed by a merchandise sales data processing device such as a POS (Point-of-sales) terminal is issued. Is done.

By the way, in recent years, when issuing a receipt on which sales data is printed in order to reduce the environmental burden, the receipt information is printed together with the URL information of the Internet where the transaction data is disclosed, and a shortened receipt is printed. The POS terminal to be issued is already known.

However, the POS terminal or the like that prints an Internet URL or the like on a receipt sheet always issues a receipt sheet on which the URL is described. For example, when a transaction is performed with a small number of items, In spite of being able to issue with a short receipt length, it is necessary to print information such as URL on the receipt.

JP 2000-30154 A

For this reason, the problem to be solved by the embodiments of the present invention is to provide a merchandise sales data processing apparatus and program for saving a receipt and changing the print format of a receipt that is printed and issued according to a transaction mode. It is.

The merchandise sales data processing apparatus of this embodiment generates transaction data including a total amount of one transaction based on an input unit that inputs a product code associated with a product and the product code input by the input unit. A generating unit; a first determining unit that determines whether or not a predetermined condition regarding receipt issuance is satisfied; and when the first determining unit determines that the predetermined condition is satisfied, the generating unit generates And a printing unit that issues a receipt printed in a first printing format including information indicating a total amount of the one transaction and a disclosure destination of the transaction data of the one transaction.

The program of the present embodiment is a control program for a merchandise sales data processing apparatus that includes an input unit that inputs a merchandise code associated with a merchandise and a printing unit that issues a receipt. A generation function for generating transaction data including the total amount of one transaction based on the product code input by the input unit, and a first determination function for determining whether a predetermined condition regarding receipt issuance is satisfied When it is determined that the predetermined condition is satisfied by the first determination function, the total amount of the one transaction generated by the generation function and information indicating a disclosure destination of the transaction data of the one transaction are displayed on the printing unit. And a function for printing.

The block diagram which shows the whole structure of the receipt provision system of this embodiment. The figure which shows the structure of the web server of this embodiment. The flowchart which shows the flow of the merchandise sales data process of 1st Embodiment. The flowchart which shows the flow of the process which the server of 1st Embodiment performs. The figure which shows the browsing process of the receipt information which the web server of 1st Embodiment performs. The figure which shows the receipt printed with the 1st receipt format of 1st Embodiment. The figure which shows the receipt information displayed on a web page with the 2nd receipt format of 1st Embodiment. The figure which shows the receipt printed with the 1st receipt format of 1st Embodiment. The figure which shows the receipt information displayed on the web server of 1st Embodiment. The figure which shows the receipt printed with the 1st receipt format of 1st Embodiment. The flowchart which shows the flow of the merchandise sales data processing of 2nd Embodiment. The flowchart which shows the flow of the process which the server of 2nd Embodiment performs. The figure which shows the data structure of the payment classification master file which HDD of the POS terminal of this embodiment memorize | stores The figure which shows the receipt printed with the 3rd receipt format of 2nd Embodiment. The figure which shows the receipt information displayed on the web server of 2nd Embodiment. The figure which shows the receipt printed with the 4th receipt format of 2nd Embodiment. The figure which shows the receipt information displayed on the web server of 2nd Embodiment.

Hereinafter, a product sales data processing apparatus according to an embodiment of the present invention will be described in detail with reference to the accompanying drawings. In the present embodiment, a POS terminal will be described as an example of the product sales data processing apparatus.

(First embodiment)
The merchandise sales data processing apparatus according to the first embodiment has a case where the score of a product purchased by a customer is greater than a predetermined score or / and the price of the purchased product is higher than a predetermined amount In this case, the print format of the receipt to be printed is changed and the detailed receipt data is disclosed on the web server.

FIG. 1 is a block diagram showing the overall configuration of the receipt providing system 1. The receipt providing system 1 is mainly composed of a web server 30 connected to the Internet 50 and a POS (Point-Of-Sales) system 40.

The POS system 40 includes a POS terminal (product sales data processing device) 10 and a store computer (server) 20. A plurality of POS terminals 10 are individually installed at a cash register counter in a store. The store computer 20 is connected to the POS terminal 10 through a network so that data can be transmitted / received via the Internet 50, for example.

In FIG. 1, a POS terminal 10 has a CPU (Central Processing Unit) 101 mounted as a control unit body. The CPU 101 is connected to a ROM (Read Only Memory) 102 and a RAM (Random Access Memory) 103 memory unit, an HDD (Hard Disk Drive) 104, and input / output devices described later via a bus line 105 such as an address bus and a data bus. An interface unit (I / F) 106 with 107 to 112 and a communication controller 112 for controlling data communication with the store computer 20 are connected.

The input / output devices are described below. The printer 107 is a so-called printing unit, and issues a receipt on which transaction details data such as the product name, price, and total amount of goods sold in one transaction are printed under the control of the CPU 11.

The keyboard 108 is a part of an input unit that accepts input from the outside, and is set by “00” and “0” to “9” numeric keys for numeric data, and the numeric keys. A PLU key that commands that the numeric data is a PLU (Price Look Up) code, a × key that commands that the numeric data is a multiplier, a discount key that commands that the numeric data is a discount rate, Discount key for commanding the discount amount, Clear key for commanding clearing of numerical data, etc., subtotal key for commanding subtotal output for transactions, deposit / current total key for commanding cash closing for transactions, merchandise for sale Has an exclusion key or the like that declares to be excluded from the point calculation.

Similarly, the scanner 109 is a part of the input unit, and reads a barcode attached to each product. Each product has a barcode indicating a product code unique to the product. The scanner 109 functions as an input unit for product identification data. For example, the product code of a product without a barcode can be input as a PLU code using the numeric keys and the PLU key of the keyboard 108.

The card reader 110 reads card data including a customer code recorded on a point card, for example.

The display 111 displays, for the operator of the POS terminal 10, the product name, price, total amount, etc. of the products sold as one transaction taken in by the scanner. Moreover, the display 112 for customers displays the same information as the display 111 with respect to the customer of this one transaction.

The POS terminal 10 has an HDD 104. For example, the HDD 104 stores a product master file 1041 and a payment type master file 1042 (shown in FIG. 9). The product master file 1041 stores a unique product code, which is product identification data set for each product, in association with the department code, product name (product name), and unit price that is the price per product. ing.

The payment type master file 1042 is defined in association with the receipt printing format and the presence / absence of data transmission corresponding to, for example, “cash”, “credit”, and “electronic money” which are closing means of one transaction. (See FIG. 9). For example, when one transaction is closed by payment with “cash”, it is determined in association with which print format the issued receipt is printed and issued.

In the POS terminal 10 according to the present embodiment, receipt data, which will be described later, is generated by the CPU 101 for each transaction as the merchandise sales data process is executed. The receipt data includes a unique receipt code.

The “receipt code” is composed of a combination of a “POS terminal code” for identifying the POS terminal 10 and a transaction code for identifying one transaction. For example, when the “POS terminal code” is “01” and the “transaction code” is “0001”, the “receipt code” is “010001” by combining the “POS terminal code” and the “transaction code”. . The “transaction code” is incremented by the CPU 101 every time one transaction is performed. That is, the “receipt code” generated in the next transaction is “010002”.

FIG. 2 is a diagram illustrating the web server 30. The web server 30 has a form of a general server computer, and is installed, for example, in a server room of an Internet service provider.

As shown in FIG. 2, the web server 30 has a CPU 301 mounted as a control unit main body. A communication controller 305 is connected to the CPU 301 via a bus line 306 such as an address bus and a data bus, connected to the memory unit of the ROM 302 and RAM 303, the HDD 304, and the Internet to control data communication between the server and the external device. Is done.

The ROM 302 stores fixed data in a fixed manner. The RAM 303 stores variable data in a rewritable manner and is used as a work area.

The HDD 304 stores web server software having a web information transmission function used in the Internet 50. The HDD 304 stores web page data. Web page data stored in the HDD 304 is acquired by a browser function of a predetermined external device. Then, the web page is displayed on the display unit of the predetermined external device by the browser function. As such an external device, for example, a communication terminal such as a home personal computer or a mobile phone is assumed.

FIG. 3 is a flowchart showing the flow of merchandise sales data processing. This will be described with reference to FIGS. As shown in FIG. 3A, the CPU 101 of the POS terminal 10 shown in FIG. 1 waits until a product code is input via the keyboard 108 or the input unit of the scanner 109 (Act 301). When the CPU 101 determines that a product code has been input (Y in Act 301), the CPU 101 temporarily stores the input product code in the RAM 103. Then, product information corresponding to the temporarily stored product code is acquired from the product master file 1041 of the HDD 104 (Act 302).

The CPU 101 temporarily stores the acquired product information in the RAM 103. Then, the CPU 101 waits until the “subtotal key” that is the temporary fastening key of the keyboard 108 is pressed (Act 303). For example, in this state, when the CPU 101 detects that a product code has been input from the scanner 109 without pressing the temporary tightening key “subtotal key” (N in Act 303), the CPU 101 returns to the processing of Act 301 and Act 302. These processes are executed. The processing from Act 301 to Act 303 corresponds to generating means for generating transaction data of one transaction based on the product code input by the input unit.

On the other hand, in Act 303, when the CPU 101 determines that the “subtotal key” that is the temporary closing key has been pressed (Y in Act 303), the settlement amount of one transaction is obtained by summing the amounts such as unit prices stored in the RAM 103. (Total amount) is calculated (Act 304). Basically, the settlement amount (total amount) is the total amount of each unit price. If a discount amount is included, the settlement amount reflects the discounted amount, that is, the total amount of one transaction.

Next, the CPU 101 waits until the closing key displayed as “deposit / cash” on the keyboard 108 is pressed (Act 305). When determining that the closing key has been pressed (Y in Act 305), the CPU 101 determines whether the total number of purchased products in the current transaction is greater than a predetermined score (Act 306). The processing of Act 306 corresponds to first determination means. Here, the “predetermined predetermined number of points” means, for example, (1) when three identical products to which the same product code is assigned are purchased, (2) products to which different product codes are assigned This is the case when 3 items are purchased. In any case, the number of purchase points may be handled as 3 points. Further, the case of (1) and the case of (2) may be distinguished. Further, the score is not limited to three points. In the present embodiment, the following description will be continued by taking the case of (1) as an example.

In Act 306, if the CPU 101 determines that the customer purchases more points than the predetermined score (Y in Act 306), receipt data is generated, and the generated receipt data is stored in the web server. 30 (Act 307). Here, the receipt data transmitted to the web server 30 is, for example, data that is temporarily stored in the RAM 103 and includes, for example, all product information, a settlement amount, a deposit amount, a change amount, and a current time that specifies a transaction date and time. . The receipt data also includes a unique “receipt code”. Thereafter, the CPU 101 waits until information for identifying the web page generated based on the receipt data transmitted in Act 307 is received from the web server 30 (Act 308).

Next, as illustrated in FIG. 3B, the CPU 301 of the web server 30 illustrated in FIG. 2 receives the receipt data transmitted from the POS terminal 10 via the communication controller 305 (Y in Act 401). And the data of the web page which described the receipt information based on the received receipt data are produced | generated (Act402). The data of the web page is composed of product information included in the receipt data, settlement data, deposit amount, change amount, text data of transaction date / time information, and layout information by HTML. The generated web page data is stored in the HDD 304 of the web server 30.

The CPU 301 of the web server 30 transmits URL information for specifying the data of the generated web page to the POS terminal 10 (Act 403). This URL information is composed of, for example, alphanumeric text, and is “http://xxx.co.jp/receipt/010001”. “Xxx.co.jp/” in the URL is a host name indicating the web server 30 that is a host, and “/ recept // 010001” is information for specifying a web page stored in the web server 30. is there.

Returning to FIG. 3 (a), when the CPU 101 of the POS terminal 10 receives the URL information transmitted from the web server 30 via the communication controller 112 (Y in Act 308), the CPU 101 adds the web data to the previously generated receipt data. The receipt data is generated by adding the URL information transmitted from the server 30 (Act 309). Then, the CPU 101 prints receipt data generated by operating the printer 107 (Act 309). FIG. 5A shows an example of a printed receipt. Details will be described later.

On the other hand, if the CPU 101 determines in Act 306 that the predetermined number of points (three points) determined in advance is greater than the number of points purchased by the customer (N in Act 306), the processing proceeds to Act 311. The CPU 101 compares the purchase amount purchased by the customer with a predetermined amount, and determines whether or not the amount purchased by the customer is higher than the predetermined amount (Act 311). The processing of Act 311 corresponds to second determination means.

When the CPU 101 determines that the amount purchased by the customer is higher than a predetermined amount (Y in Act 311), the receipt data is generated in the same manner as in the previous Act 307, and the generated receipt data Is transmitted to the web server 30 (Act 312). On the other hand, if it is determined that the amount purchased by the customer is lower than a predetermined amount (N in Act 311), the product information, settlement amount, deposit amount, change amount, and transaction date / time temporarily stored in the RAM 103 are specified. Receipt data is generated based on the current time (Act 313).

After the receipt data is generated in Act 313, the CPU 101 prints the receipt data generated by operating the printer 107 (Act 309). FIG. 7A shows an example of a printed receipt. Details will be described later.

FIG. 4 is a diagram illustrating receipt information browsing processing executed by the web server 30. The CPU 301 of the web server 30 waits until receiving a receipt data browsing request (Act 501). For example, when the customer accesses the web server 30 via the Internet by inputting the URL information printed on the receipt and entering the password printed on the receipt via an external device such as a personal computer, that is, When a receipt data browsing request is received from the customer (Y in Act 501), the web page data of the receipt data stored for each transaction stored in the HDD 304 of the web server 30 is searched (Act 502).

Then, it is determined whether or not the receipt data that matches the receipt data of the URL information input from the customer's personal computer is stored in the HDD 304 (Act 503). If there is a matching receipt data (Y in Act 503), It is determined whether the input passwords match (Act 504). If the CPU 301 determines that the passwords match (Y in Act 504), the CPU 301 discloses the receipt data.
Accordingly, the customer receives the detailed transaction information receipt data of the current time specifying the transaction date and time, the name of each purchased product and the number of points purchased, the unit price of each product, the settlement amount, the deposit amount, and the change amount. View detailed receipt information on a computer display screen.

On the other hand, when the CPU 301 determines in Act 504 that the passwords do not match (N in Act 504), error processing is performed (Act 506). The “error processing” here ends, for example, by transmitting information indicating that the requested receipt information cannot be disclosed to the customer's personal computer. In Act 503, when the CPU 301 determines that there is no receipt data matching the HDD 304 (N in Act 503), error processing is performed (Act 506).

Details of the receipt display examples shown in FIGS. 5, 6, and 7 will be described below.
Here, using FIG. 5A, when it is determined in Act 306 of FIG. 3 that the total number of purchased products in the current transaction is greater than a predetermined score (Y in Act 306), An image of a receipt printed and issued will be described. For example, it is assumed that a predetermined number of points that is a criterion for Act 306 is set to “5 points”. In this case, the customer “Product A” is “2”, “Product B” is “1”, “Product C” is “1”, “Product D” is “1”, “Product E”. “6 points”, “product F” “1 point”, and a total of 12 points. In this case, in Act 306, the CPU 101 determines that the product score “12 points” actually purchased by the customer is larger than the predetermined score “5 points”, and the receipt issued in Act 310 of FIG. Then, the receipt RT1 of the shortened first receipt format shown in FIG.

The receipt RT1 in the first receipt format shown in FIG. 5A has a plurality of receipt areas including a first receipt area T1, a second receipt area T2, and a third receipt area T3. In the first receipt area T1 in the receipt RT1, the transaction date and time “YYYY year MM month DD day” and the transaction code “No. 010001” are printed, and in the second receipt area T2 in the receipt RT1, the product score “12” is printed. "Point", settlement amount (total) "11,580 yen", deposit amount (cash) "12,000 yen", change amount (change) "420 yen" are printed. In the third receipt area T3 of the receipt RT1, access destination URL information of detailed receipt information (detailed information such as purchase points and unit prices for each product), a collation number “010001”, and an access password “aaaaaa1” are stored. And are printed.

FIG. 5B is a diagram showing receipt information acquired by the customer accessing the access destination of the URL printed in the third receipt area T3 of the receipt paper RT1 via, for example, a personal computer. Here, as shown in FIG. 5 (b), detailed transaction information such as the number of purchases of each product, the unit price, and the amount of money for each product is provided in a second receipt format different from the first receipt format. The web page WP1 is disclosed through the screen of the personal computer.

Next, referring to FIG. 6A, when the CPU 101 determines in Act 306 of FIG. 3 that the total number of purchased products in the current transaction is less than a predetermined score (N in Act 306). ) And the image of the receipt paper issued when it is determined that the amount purchased by the customer is higher than a predetermined amount (Y in Act 311).

For example, it is assumed that a predetermined number of points that is a judgment criterion of Act 306 is “5 points”, and a predetermined amount of money that is a judgment criterion of Act 311 is “10,000 yen”. . In this case, it is assumed that the customer purchases “4 items” of “product F” having a unit price of “3,000 yen”. In this case, in Act 306, the CPU 101 compares the customer's purchase score “4 points” with a predetermined score “5 points” (Act 306). The CPU 101 determines that the purchase points are less than the predetermined score (N in Act 306), and in Act 311, the purchase price (here, “12,000 yen”) and a predetermined price (here, “10,000”) are determined. Yen ") (Act 311). In Act 311, the CPU 101 determines that the purchase amount purchased by the customer is higher than a predetermined amount, and prints and issues a receipt in the first receipt format shown in FIG.

In this case, the receipt RT2 to be printed is displayed in the first receipt area R1 of the receipt RT2 in the form of the first receipt format as shown in FIG. 6 (a), the transaction date and time “YYYY year MM month DD day”. ”And the transaction code“ No. 010002 ”are printed, and in the second receipt area R2 of the receipt RT2, the product score“ 4 points ”, the settlement amount“ 12,000 yen ”, the deposit amount“ 12,000 yen ”, the change The amount “0 yen” is printed. Then, in the third receipt area R3 of the receipt RT2, the URL information of the access destination of the detailed receipt information, the collation number “010002”, and the access password “aaaaaa2” are printed.

FIG. 6B is a diagram showing receipt information acquired by the customer accessing the access destination of the URL printed in the third receipt area R3 of the receipt paper RT2 via, for example, a personal computer. Here, as shown in FIG. 6 (b), detailed transaction information such as the number of purchases of each product, the unit price, and the amount of money for each product is provided in a second receipt format different from the first receipt format. The web page WP2 is disclosed through the screen of the personal computer.

Next, referring to FIG. 7, when the CPU 101 determines in Act 306 that the total number of purchased products in the current transaction is less than a predetermined score (N in Act 306), The image of the receipt paper issued when it is determined that the purchased amount is lower than the predetermined amount (N in Act 311) will be described.

Customer “Product A” is “1”, “Product B” is “1”, “Product C” is “1”, “Product D” is “1”, 4 points in total, “3” , 080 yen "transaction. In this case, it is determined in Act 306 that the total number of purchased products (4 points) in the current transaction is less than a predetermined score (for example, 5 points) (N in Act 306) and the customer purchased It is determined that the amount (3,080 yen) is lower than a predetermined amount (for example, 10,000 yen) (N in Act 311). The receipt RT3 issued at Act 310 based on the receipt data generated at Act 313 is the receipt image shown in FIG. That is, printing is performed in a second receipt format different from the receipt in the first receipt format. Specifically, various transaction details (product name, product unit price, payment amount, deposit amount, change amount, etc.) are printed in the receipt area R4. The receipt format printed and issued in this case is the same print form as the receipt format (second receipt format) disclosed by the web server 30 described above.

As described above, according to the first embodiment, when it is determined that the number of products actually purchased by the customer is greater than a predetermined number of points, printing is performed in the first receipt format that is shorter than usual. Since this is done, receipt paper can be saved. Also, in one transaction, a shortened receipt is not always printed and issued, and the format of the receipt is changed according to the purchased points, so if you shop beyond the range of the predetermined points, A shortened receipt can be obtained, and the customer can be made aware that a product exceeding a predetermined number has been purchased.

Further, since the URL information that can be accessed separately by a computer is described in the shortened receipt, the customer can acquire detailed receipt information by accessing the URL printed on the receipt.

In addition, even when it is determined that the total score of purchased products in one transaction is less than a predetermined predetermined score, and the amount of money purchased by a customer is determined to be higher than a predetermined predetermined amount Shortened receipts are issued. For this reason, it is possible to save the receipt paper and make the customer aware that the purchase has exceeded the predetermined amount due to the difference in the receipt format.

Although the first embodiment has been described above, this embodiment is presented as an example and is not intended to limit the scope of the invention. For example, the first embodiment is a case where the number of merchandise actually purchased by the customer is greater than a predetermined score, and the number of merchandise actually purchased by the customer is less than a predetermined score. However, when the payment amount in one transaction is higher than a predetermined amount, a form that prints and prints a shortened receipt is explained. It may be set to issue a receipt.

(Second Embodiment)
Next, a second embodiment will be described. This embodiment is different from the first embodiment in the following points. That is, in the second embodiment, it is determined whether or not to issue a shortened receipt according to the type of the closing processing means for one transaction, and a predetermined receipt issuing method is executed based on the determination result. The In the following description, the description of the configuration / process common to the first embodiment will be omitted, and different parts will be described.

The receipt issuing process of the second embodiment will be described with reference to FIG. The difference between the first embodiment and the second embodiment is that an Act 806 process for determining the type of the tightening process executed in Act 805 is added, and the payment type after the determination process of Act 806. With reference to the master file 1042 (see FIG. 9), the format of the receipt to be printed and the presence / absence of data transmission to the web server 30 are determined in accordance with the payment type.

In FIG. 8A, since the processes from Act 801 to Act 805 are the same as those in the first embodiment, description thereof will be omitted. If the CPU 101 determines in Act 805 that the closing process has been performed (Y in Act 805), it determines which closing operation in the payment type master file 1042 shown in FIG. 9 is the closing process specified in Act 805. (Act 806).

For example, when one transaction is paid in cash by the customer, the operator operates the “deposit / cash key”. In this case, the CPU 101 determines in Act 805 that the closing process has been performed, and refers to the payment type master file 1042 in FIG. 9 based on the information that the “deposit / cash key” has been pressed. Then, the receipt type information stored in association with the payment type in the payment type master file 1042 and the information on the presence / absence of data transmission are acquired. In this case, in the payment type master file 1042, the receipt type to be printed and issued in association with the payment type “cash” is the second receipt format RT3 (see FIG. 7) for printing the points and unit price of each product in detail on the receipt. ), “None” that does not execute data transmission to the web server is stored in association with each other, so the CPU 101 acquires these pieces of information. Then, the CPU 101 issues a print based on these pieces of information. That is, in this case, since the payment is cash, only the receipt on which the transaction data is printed is issued.

As a next case, an example of a receipt to be printed and issued by the CPU 101 is shown in FIG. 10A, and a receipt display that can be viewed on the web server 30 will be described with reference to FIG. 10B as an example.

For example, the customer selects “product A” as “1 point”, “product B” as “1 point”, “product C” as “1 point”, “product D” as “1 point”, and “product E” as “product E”. Assume that a transaction of “1 point”, a total of 5 points, and a total of “5,080 yen” is performed, and the customer executes a settlement process using a credit card. In this case, the CPU 101 stores the payment type master stored in the HDD 104 as to whether the type paid in Act 806 of FIG. 8A is “cash”, “electronic money”, or “credit”. The determination is made with reference to the file 1042 (Act 806). The processing of Act 806 corresponds to first determination means. As a result of the determination, since the payment type is “credit”, the CPU 101 obtains the receipt type information stored in correspondence with the payment type “credit” from the payment type master file 1042 and the data transmission presence / absence information to the web server. get. Here, “receipt type information” is the third receipt format, and “data transmission presence / absence information to web server 30” is “present”. The process is executed.

That is, the receipt RT4 printed in this case has a transaction date “YYYY MM month DD day” and a transaction code “No. 010004” in the first receipt region R1 of the receipt RT4 as shown in FIG. Is printed, and in the second receipt area R2 of the receipt RT1, the characters “5 points” for the product, “5,080 yen” for the settlement amount, and “credit payment” as the payment type are printed. In addition, in the third receipt area T3 of the receipt RT1, access destination URL information of detailed receipt information (information such as purchase points and unit prices for each product is described), a collation number “010004”, and an access password “Aaaaaa4” is printed. The difference from the first receipt format shown above is that the payment amount and change amount printed in the second receipt area T2 of the first receipt format are “credit payment” in the third receipt format. It is a point that has been replaced with the character.

FIG. 10B is a diagram showing receipt information obtained by the customer accessing the URL access destination printed on the third receipt area R3 of the receipt paper RT4 via a personal computer or the like. As shown in FIG. 10B, in a second receipt format different from the first receipt format, detailed transaction information such as the number of items purchased, unit price, amount of money for each item is stored in a personal computer. It is disclosed on the web page WP4 through the screen.

FIG. 11A is a diagram showing a fourth receipt format that is printed and issued as a result of performing a transaction using a payment means (electronic money) different from the above. In the receipt RT5 to be printed, the first receipt area R1 and the third receipt area R3 of the receipt RT5 are the same as those in the first receipt format. That is, the transaction date and time and transaction code are printed in the first receipt area R1, and the URL information of the access destination, the verification number, and the access password are printed in the third receipt area R3. The difference from the first receipt format is the second receipt area R2, in which the payment amount and the balance amount of electronic money are printed in this area R2. FIG. 11B is a diagram showing receipt information acquired by the customer accessing the URL access destination printed in the third receipt area R3 of the receipt paper RT5 via a personal computer or the like. As shown in FIG. 11B, detailed transaction information such as the number of purchases of each product, unit price, and the amount of each product is stored in a personal computer in a second receipt format different from the fourth receipt format. It is disclosed on the web page WP5 through the screen.

As described above, according to the second embodiment, the type of receipt to be issued is determined in advance by the method of payment type for one transaction. For this reason, if the customer wishes to issue a printed receipt of a shortened receipt, the customer can make a payment by using a method of a payment type that is predetermined so that the shortened receipt is issued. Receipts can be received.

For example, the receipt type and the presence / absence of data transmission stored in association with the payment type master file 1042 used in the second embodiment are not necessarily limited to the associated format, and may be appropriately determined by the operator. It can be changed by setting. As an example of changing, for example, the business mode of the POS terminal 10 can be set to the inspection mode, and the receipt type corresponding to the payment type can be appropriately changed under this inspection mode.

As mentioned above, although embodiment of this invention was described, this embodiment is shown as an example and is not intending limiting the range of invention. The novel embodiment can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the scope of the invention. This embodiment is included in the scope and gist of the invention, and is also included in the invention described in the claims and the equivalent scope thereof.

10 POS terminal (product sales data processing device)
101 CPU
102 ROM
103 RAM
104 HDD
20 store computer 30 web server 1041 product master file 1042 payment type master file

Claims (7)

An input unit for inputting a product code associated with the product;
Generating means for generating transaction data including the total amount of one transaction based on the product code input by the input unit;
First determination means for determining whether a predetermined condition relating to receipt issuance is satisfied;
A first print including information indicating a total amount of the one transaction generated by the generation unit and a disclosure destination of the transaction data of the one transaction when the first determination unit determines that the predetermined condition is satisfied. A print section for issuing a receipt printed in a format;
A product sales data processing device comprising: 2. The commodity sales data processing apparatus according to claim 1, wherein the first determination means determines whether or not the number of commodities traded in one transaction as a predetermined condition exceeds a predetermined score. . The said printing part issues the receipt of the 2nd printing format different from the said 1st printing format, when it determines with the said predetermined condition not being satisfy | filled by the said 1st determination means, The claim 1 characterized by the above-mentioned. 2. The product sales data processing device according to 2. A second determination means for determining whether or not the total amount in the one transaction exceeds a predetermined amount,
When the first determination unit determines that the predetermined condition is not satisfied, and the second determination unit determines that the predetermined total amount is exceeded, the receipt of the first print format is received. The product sales data processing device according to any one of claims 1 to 3, wherein the product sales data processing device is issued. The merchandise sales data processing apparatus according to claim 1, wherein the first determination unit determines a type of a closing unit that performs the closing process of the one transaction. The storage unit further stores a plurality of different print formats according to the type of the fastening unit, and the print unit stores the print format stored in the storage unit according to the determination result of the first determination unit. 6. The merchandise sales data processing apparatus according to claim 5, wherein the receipt is issued in a print format corresponding to the type of fastening means determined from the above. An input unit for inputting a product code associated with the product, a printing unit for issuing a receipt,
A product sales data processing apparatus control program comprising:
In the processing device,
A generation function for generating transaction data including the total amount of one transaction based on the product code input by the input unit;
A first determination function for determining whether or not a predetermined condition regarding receipt issuance is satisfied;
When it is determined that the predetermined condition is satisfied by the first determination function, the print unit displays information indicating the total amount of the one transaction generated by the generation function and the disclosure destination of the transaction data of the one transaction. A function to print,
A program to realize

Images