JP2012173852A - Merchandise sales data processing device and control program for the same - Google Patents

Abstract

PROBLEM TO BE SOLVED: To prevent validation of a return-processed merchandise in a validation waiting-state.SOLUTION: A merchandise sales data processing device 1 transmits certification data of a value card to a server 3 when sales-processed merchandise sales data includes sales data of the value card that requires the certification data certifying that the merchandise has been normally sold be transmitted to the server. If the server 3 does not approve a validation request responsive to the transmitted certification data, the device 1 repeats retransmission of the certification data until the validation request is approved. The device 1 terminates the retransmission of the certification data when the return-processed merchandise sales data includes the data of the value card for which the retransmission of the certification data is repeated.

Description

  An embodiment of the present invention relates to a merchandise sales data processing apparatus for a store that sells a merchandise, for example, a value card, that is required to transmit proof data that the merchandise has been properly sold to the server. About.

  There is a prepaid value card as one of the payment methods for purchasing contents, products, or services such as music and electronic books using the Internet. Value cards are sold at home appliance mass retailers and convenience stores. At the store, customers can pick up their own cards before purchase and freely select the cards they want to purchase. Therefore, the value cards are individually displayed and displayed as individual products. At this time, the value information of each value card is not yet valid. The store clerk reads the barcode printed on the value card selected by the customer with a scanner of a POS (Point Of Sales) terminal. The bar code is a bar code symbol formed from a card ID uniquely set for the value card. When the barcode is read, the barcode data is transmitted from the POS terminal to the external value card management server via the store server.

  The value card management server includes a database that stores value information and status information in association with card IDs (barcode data) of all value cards to be managed. When the barcode data read by the POS terminal is received, the value card management server searches the database and switches the status information corresponding to the barcode data from the invalid state to the valid state. When the status information becomes valid, the value card specified by the card ID of the barcode data becomes valid. The value information of the activated value card is used to pay for the content purchased online.

JP 2008-204448 A

  When the barcode of the value card is read by the scanner of the POS terminal, the barcode data is not correctly transmitted to the value card management server due to an abnormality in the network connecting the POS terminal and the value card management server. Value cards are not activated. In such a case, conventionally, the store server temporarily holds the barcode data of the value card that has failed to be activated, and periodically transmits it to the value card management server. Therefore, the value card is activated at a relatively early time even if it is not at the time of purchase. For this reason, customers are informed that the card will be valid later and sell value cards.

  However, some customers cease purchasing value cards if they are not activated at the time of purchase. Even in such a case, conventionally, the barcode data of the value card whose activation has failed is transmitted from the store server to the value card management server. For this reason, since the value card treated as returned goods becomes effective later, there is a possibility of inducing unauthorized use by a store clerk, for example.

  The problem to be solved by the present invention is to provide a merchandise sales data processing apparatus and a control program for the merchandise sales data that can prevent the validation of the merchandise that has been treated as returned goods.

  In order to solve such a problem, a merchandise sales data processing apparatus according to an embodiment includes a sales processing unit, a return processing unit, an validation request unit, an validation re-request unit, and a re-request stop unit. The sales processing means performs sales processing on the product sales data based on the data of the purchased purchased product. The return processing means returns the product sales data based on the data of the input return product. The validation request means includes the sales data of the product for which it is required to send proof data to the server that the product has been properly sold in the sale of the product in the product sales data processed by the sales processing means. The proof data of the product is transmitted to the server. The validation re-requesting unit repeats the retransmission of the certification data until the validation request is approved when the validation request is not approved by the server for the transmission of the certification data by the validation requesting unit. The re-request stop unit terminates the re-transmission of the proof data when the product sales data processed by the return processing unit includes the data of the product for which the proof data is re-transmitted by the validation re-request unit. .

The system block diagram which shows one Embodiment of a merchandise sales data processing apparatus. The top view which shows the value card used in the embodiment. The figure which shows an example of the data memorize | stored in a value card database in the same embodiment. The block diagram which shows the hardware constitutions of the POS terminal in the same embodiment. The block diagram of the transaction buffer formed in RAM of the POS terminal in the embodiment. The block diagram which shows the hardware constitutions of the store server in the embodiment. The block diagram of the re-request buffer formed in RAM of the store server in the embodiment. 4 is a flowchart showing a main procedure of subtotal key processing executed by the CPU of the POS terminal in the embodiment. 4 is a flowchart showing the main procedure of a closing key process executed by the CPU of the POS terminal in the embodiment. The figure which shows an example of the transaction receipt issued from the POS terminal in the same embodiment. The figure which shows an example of the value card sales receipt issued from the POS terminal in the same embodiment. 5 is a flowchart showing the main procedure of a return key process executed by the CPU of the POS terminal in the embodiment. The figure which shows an example of the value card return receipt issued from the POS terminal in the same embodiment. 4 is a flowchart showing a main procedure of transaction reception processing executed by the CPU of the store server in the embodiment. 5 is a flowchart showing the main procedure of timer interrupt processing executed by the CPU of the store server in the embodiment. The flowchart which shows the principal part procedure of the subtotal key process which CPU of a POS terminal performs in 2nd Embodiment. The figure which shows an example of the validation error message screen displayed on the display for operators of a POS terminal in 2nd Embodiment. The figure which shows an example of the validation error message screen displayed on the display for customers of a POS terminal in 2nd Embodiment.

  Hereinafter, an embodiment of a merchandise sales data processing apparatus will be described with reference to the drawings. This embodiment exemplifies a prepaid value card as a product that is required to transmit proof data that it has been properly sold to the server when the product is sold. First, the first embodiment will be described with reference to FIGS.

[First Embodiment]
FIG. 1 is a system configuration diagram of the first embodiment. This system includes a POS system 1 constructed at each store and a value card management server 3 that manages a value card database 2. The POS system 1 includes a plurality of POS terminals 4 and a store server 5 that centrally manages each POS terminal. The POS terminals 4 and the store server 5 are connected by a LAN (Local Area Network) 6. ing. The store server 5 of the POS system 1 of each store and the value card management server 3 are connected by a network line 7 such as the Internet.

  As shown in FIG. 2, a barcode 9 is printed on the value card 8 used in the present embodiment. The barcode 9 is obtained by converting a card ID for uniquely identifying the value card 8 into a barcode symbol.

  As shown in FIG. 3, the value card database 2 stores value information and a status flag in association with the card ID of each value card 8. The value information is an amount that can be paid with the value card 8 specified by the corresponding card ID. In the status flag, for example, “0” indicates an invalid state, and “1” indicates a valid state. The value information is not limited to the amount. It may be a point where the amount of money per point can be variably set.

  FIG. 4 is a block diagram showing a main configuration of the POS terminal 4. The POS terminal 4 includes a CPU (Central Processing Unit) 11 as a control unit main body. The CPU 11 is connected to a ROM (Read Only Memory) 13, a RAM (Random Access Memory) 14, a clock unit 15, a LAN controller 16, a keyboard controller 17, and a display controller 18 via a bus line 12 such as an address bus and a data bus. A display controller 19, a printer controller 20, a scanner controller 21 and the like are connected to constitute a control circuit of the POS terminal 4.

  The ROM 13 stores a program for causing the CPU 11 to realize the function as the POS terminal 4. Further, the ROM 13 stores various setting data necessary for realizing the function as the POS terminal 4.

  The RAM 14 forms a memory area for temporarily storing variable data. In particular, as shown in FIG. 5, a transaction buffer 30 is formed for storing information on a product code, a sales point, a sales amount, and a cancellation flag of each product sold as one transaction. The product code is product identification data. The number of sales points and the sales amount are the points and the amount sold in the one transaction of the product specified by the corresponding product code. The cancel flag is set to “1” when the purchase of the product specified by the corresponding product code is canceled.

  The clock unit 15 measures the current date and time. The LAN controller 16 controls data transmission / reception with the store server 5 connected via the LAN 6.

  The keyboard controller 17 controls the keyboard 22 and captures key signals corresponding to the operation keys. The keyboard 22 is provided with various keys necessary for the function as the POS terminal 4 such as a numeric key, a subtotal key, a closing key, a cancel key, and a return key.

  The display controller 18 controls the screen display of the operator display 23. The display controller 19 controls the screen display of the customer display 24. The operator display 23 displays a screen of information to be provided to the operator of the POS terminal 4 called a cashier. The customer display 24 displays a screen of information to be provided to a customer who purchases a product for settlement.

  The printer controller 20 controls the printer 25 for printing data on the receipt paper, and issues a receipt (receipt) or the like. The scanner controller 21 controls a scanner 26 for optically reading a barcode attached to a product and takes in the read barcode data.

  FIG. 6 is a block diagram showing a main configuration of the store server 5. The store server 5 is equipped with a CPU 41 as a control unit main body. A ROM 43, RAM 44, clock unit 45, LAN controller 46, HDD controller 47, communication interface 48, etc. are connected to the CPU 41 via a bus line 42 such as an address bus, a data bus, etc. Is configured.

  The ROM 43 stores a program for causing the CPU 41 to realize the function as the store server 5. The ROM 43 stores various setting data necessary for realizing the function as the store server 5.

  The RAM 44 forms a memory area for temporarily storing various variable data. In particular, as shown in FIG. 7, the RAM 44 forms a re-request buffer 50 for storing each information of card ID, transaction date / time, POSID, transaction number, and deletion flag.

  The re-request buffer 50 stores information on the value card 8 that has failed the activation request at the time of purchase. The transaction date / time is date / time data when a transaction including the purchase of the value card 8 specified by the card ID is performed. The POSID is an identification code of the POS terminal 4 that has processed a transaction including purchase of the value card 8. The transaction number is data for uniquely identifying a transaction including purchase of the value card 8. The deletion flag is set to “1” when deleting the record of the corresponding card ID, transaction date / time, POSID, and transaction number.

  The clock unit 45 measures the current date and time. The LAN controller 46 controls data transmission / reception with each POS terminal 4 connected via the LAN 6. The HDD controller 47 controls writing and reading of data with respect to various data files such as a product data file and a sales data file stored in an HDD (Hard Disk Drive) 49. The communication interface 48 controls data communication with an external server such as the value card management server 3 connected via the network line 7.

  The POS system 1 including the POS terminal 4 and the store server 5 having such a configuration functions as a merchandise sales data processing apparatus. That is, when a customer offers to pay for the purchased product, the cashier operating the POS terminal 4 reads and operates the barcode attached to the purchased product one by one with the scanner 26. When the barcode of the purchased product is read by the scanner 26, the CPU 11 searches the product data file with the product code obtained by analyzing the barcode, and reads the product data such as the product name and unit price of the sold product. The CPU 11 then selects a product code. Transaction data relating to the sales product such as the number of sales points and the sales price is stored in the transaction buffer 40. Further, detailed data such as a product code, a product name, a unit price, a sales point, and a sales price are displayed on the operator display 23 and the customer display 24. The CPU 11 executes the above sales process every time the barcode is read (sales processing means).

  Thus, when the barcode reading operation for all purchased products is completed, the cashier presses the subtotal key on the keyboard 22. When the subtotal key is pressed, the CPU 11 executes the subtotal key process shown in the flowchart of FIG.

  First, the CPU 11 searches the transaction buffer 30 (ST1). Then, the CPU 11 determines whether or not the transaction data of the value card 8 is included in the transaction buffer 30 (ST2). For example, the product code (card ID) set for the value card 8 has the same first two-digit numerical value. Therefore, the CPU 11 determines whether or not there is a product code in which the first two digits match the value unique to the value card 8. When there is such a product code, the CPU 11 determines that the transaction data of the value card 8 is included in the transaction buffer 30. When there is no such product code, the CPU 11 determines that the transaction data of the value card 8 is not included in the transaction buffer 30.

  When the transaction data of the value card 8 is not stored in the transaction buffer 30 (NO in ST2), the CPU 11 shifts to normal subtotal processing (ST6). That is, the sales amount of all the transaction data stored in the transaction buffer 30 is added up to calculate the subtotal amount and displayed on the operator display 23 and the customer display 24.

  When transaction data of the value card 8 is stored in the transaction buffer 30 (YES in ST2), the CPU 11 requests activation of the value card (ST3). That is, an activation request inquiry command including a product code (card ID) which is proof data of the value card 8 is generated and transmitted to the value card management server 3 via the store server 5 (validation request means).

  When the validation request command is normally transmitted to the value card management server 3, the value card management server 3 searches the value card database 2. Then, the status flag corresponding to the card ID included in the validation request command is changed from “0” indicating invalidity to “1” indicating validity. Further, the value card management server 3 returns a normal response to the POS terminal 4 that is the command transmission source. Therefore, for example, when the validation request command is not transmitted to the value card management server 3 due to communication abnormality, the status flag corresponding to the card ID included in the command remains “0”, and a normal response is also returned. Absent.

  The CPU 11 of the POS terminal 4 that has transmitted the validation request inquiry command in the process of step ST3 waits for a normal response (ST4). If a normal response is received within a predetermined time (YES in ST4), the CPU 11 proceeds to subtotal processing (ST6).

If the normal response cannot be received even after the predetermined time has elapsed (NO in ST4), the CPU 11 sets the validation error flag stored in the flag area of the RAM 44 to “1” (ST5). Thereafter, the CPU 11 shifts to a subtotal process (ST6).
When the subtotal processing ends, the subtotal key processing ends.

  After confirming the subtotal amount, the cashier asks the customer to pay the price. When the payment is received, the cashier operates the lock key. When detecting the operation of the closing key, the CPU 11 executes the process shown in the flowchart of FIG.

  First, the CPU 11 executes a transaction closing process (ST11). This processing includes change calculation and change display, and storage of transaction data related to settlement such as total amount, deposit amount, change amount, transaction date, transaction number, and POSID. When the transaction closing process is completed, the CPU 11 drives the printer 25 to issue a transaction receipt 60 (ST12).

  Next, the CPU 11 determines whether or not a value card activation error has occurred in the current transaction (ST13). If the validation error flag is set in the flag area of the RAM 14, it is judged that there is an validation error, and if the validation error flag is not set, it is judged that there is no validation error.

  If there is no validation error (NO in ST13), the CPU 11 transmits the transaction data stored in the transaction buffer 30 to the store server 5 (ST14). Thereafter, the transaction buffer 30 is cleared (ST18), and the closing key process is terminated.

  If there is an validation error (YES in ST13), the CPU 11 issues a value card sales receipt 70 (ST15). Further, the CPU 11 transmits the transaction data stored in the transaction buffer 30 to the store server 5. At this time, the CPU 11 adds information indicating an validation error to the transaction data (ST16). After that, the CPU 11 resets the validation error flag to “0” (ST17), clears the transaction buffer 30 (ST18), and ends the closing key process.

  An example of the transaction receipt 60 issued in step ST12 is shown in FIG. An example of the value card sales receipt 70 issued in the process of step ST15 is shown in FIG. FIG. 10 illustrates a transaction receipt 60 issued to a customer who purchases two gift cards (gift card 1000, gift card 500), which are value cards, and three items of product AAA. FIG. 11 shows an example of a value card sales receipt 70 issued because the request for the activation of two gift cards resulted in an error during the subtotal key input process.

  The transaction receipt 60 is printed with the name of the sales product, the sales amount, the total amount, the transaction date and time 61, the POSID 62, the transaction number 63, and the like. On the value card sales receipt 70, in addition to the card IDs 71a and 71b, transaction date and time 72 and POSID 73 of each gift card, a message 74 indicating that each gift card is valid within 24 hours is printed.

  When the value card sales receipt 70 is issued, the cashier is reliably activated if the value card (gift card 1000, gift card 500) is not yet activated and cannot be used immediately, but within 24 hours. Therefore, the customer is notified that it can be used after that.

  Here, when the customer takes the value card as it is, the commercial transaction with the customer is terminated. However, if the customer offers to return the value card, the cashier presses the return key. When the return key is pressed, the CPU 11 executes the process shown in the flowchart of FIG.

  First, the CPU 11 waits for input of a transaction number (ST21). When the transaction number 62 of the transaction receipt 60 is input by inputting a numerical value using the numerical key (YES in ST21), the CPU 11 obtains transaction data of the same transaction number stored in the store server 5 (ST22).

  If the transaction data is acquired and expanded in the transaction buffer 30, the CPU 11 waits for a product code to be input (ST23). When the product code is input by scanning the barcode (YES in ST23), the CPU 11 executes a return process (ST24). That is, the cancellation flag of transaction data of the same product code is set to “1”. Further, the product name and unit price specified by the product code of the transaction data are displayed on the operator display 23 and the customer display 24 (return processing means).

  The CPU 11 determines whether the returned product is a value card (ST25). When the first two digits of the scanned product code coincide with a value specific to the value card 8, the CPU 11 determines that the returned product is a value card. In other cases, the CPU 11 determines that the returned merchandise is other than the value card. When the returned merchandise is other than the value card (NO in ST25), the CPU 11 waits for the return tightening operation (ST27).

  On the other hand, if the returned merchandise is a value card (YES in ST25), the CPU 11 issues a card return receipt 80 (ST26). An example of issuing the card return receipt 80 is shown in FIG. As shown in the figure, the card return receipt 80 is printed with a card ID 81 and a card name 82 of the returned value card, and a message 83 indicating that the card has been returned.

  After issuing the card return receipt 80, the CPU 11 waits for an operation for closing the return (ST27).

  If the return goods closing operation is not performed (NO in ST27), and the product code of the next returned goods is input (YES in ST23), the CPU 11 repeats the processes in steps ST24, 25, and 26 described above. Therefore, if the returned merchandise is a value card, a return receipt 80 for that card is issued.

  When the return key is declared by operating the closing key (YES in ST27), the CPU 11 transmits the data in the transaction buffer 30 with information indicating the return transaction data (ST28). This is the end of the return key process.

  When the CPU 41 of the store server 5 receives the transaction data from the POS terminal 4 connected via the LAN 6, the CPU 41 executes the processing shown in the flowchart of FIG.

  First, the CPU 41 determines whether or not the received transaction data is returned transaction data (ST31). When the received transaction data is added with information indicating return transaction data, it is recognized as return transaction data, and when it is not added, it is recognized as normal sales transaction data.

  When the received transaction data is sales transaction data (NO in ST31), the CPU 41 analyzes the received transaction data (ST32). Then, it is determined whether or not information indicating an validation error is added to the transaction data (ST33). When the information indicating the validation error is not added to the transaction data (NO in ST33), the CPU 41 adds the received transaction data to the transaction file on the HDD (ST40).

  On the other hand, when the information indicating the validation error is added to the transaction data (YES in ST33), the CPU 41 determines the sales data of the value card from the transaction data, that is, the first two digits are the value card 8 Data on the product code that matches the specific numerical value is acquired (ST34). Then, the value card sales data is stored in the re-request buffer 50 (ST35). Thereafter, the CPU 41 adds the received transaction data to the transaction file on the HDD (ST40).

  When the received transaction data is returned transaction data (YES in ST31), the CPU 41 analyzes the received transaction data (ST36). Then, it is determined whether or not information indicating an validation error is added to the transaction data (ST37). When the information indicating the validation error is not added to the transaction data (NO in ST37), the CPU 41 adds the received transaction data to the transaction file on the HDD (ST40).

  When information indicating an activation error is added to the transaction data (YES in ST37), the CPU 41 acquires value card sales data from the transaction data (ST38). Then, the same data as the value card sales data is deleted from the re-request buffer 50. Specifically, the deletion flag of the same data is set to “1” (ST39: re-request stop unit). Thereafter, the CPU 41 adds the received transaction data to the transaction file on the HDD (ST40).

  Further, the CPU 41 of the store server 5 executes the process shown in the flowchart of FIG. 15 in response to a timer interrupt signal generated every time one hour is counted by the clock unit 45, for example.

  First, the CPU 41 searches the re-request buffer 50 (ST51). Then, CPU 41 determines whether or not value card sales data is stored in re-request buffer 50 (ST52). If it is not stored, or if a deletion flag is set for what is stored (NO in ST52), the CPU 41 ends the current interrupt process.

  When the value card sales data for which the deletion flag is not set is stored in the rerequest buffer 50 (YES in ST52), the CPU 41 generates an validation request inquiry command with the value card sales data in the rerequest buffer 50. And sent to the value card management server 3 (ST53: validation re-request means). Then, the CPU 41 waits for a normal response (ST54).

  If a normal response is received from the value card management server 3 within a predetermined time (YES in ST54), the CPU 41 clears the re-request buffer 50 (ST55). On the other hand, if a normal response cannot be received even after a predetermined time has elapsed (NO in ST54), the re-request buffer 50 is not cleared. Thus, the CPU 41 ends the current interrupt process.

  As described above, in the POS system 1 including the merchandise sales data processing apparatus according to the present embodiment, that is, the POS terminal 4 and the store server 5, when a commercial transaction including the purchase of the value card 8 occurs, the value card 8 is validated. The request is executed to the value card management server 3. If the value card 8 is validated in the value card management server 3, the value card 8 can be used immediately.

  However, when the value card 8 fails due to a temporary failure of the network line 7, for example, the value card 8 cannot be used immediately. In this case, a value card sales receipt 70 is issued from the POS terminal 4. In the store server 5, information including the card ID of the value card 8 is stored in the re-request buffer 50.

  When information including the card ID of the value card 8 that has failed to be activated is stored in the re-request buffer 50, the store server 5 validates the value card 8 with respect to the value card management server 3, for example, at one hour intervals. Execute the request. Therefore, a message 74 indicating that the value card 8 becomes valid within 24 hours is printed on the value card sales receipt 70.

  Here, when the customer offers to return the value card, the cashier presses the return key and causes the POS terminal 4 to execute the return process. Then, the information on the value card 8 stored in the rerequest buffer 50 of the store server 5 is deleted. For this reason, the activation request for the value card 8 by the store server 5 is not executed. Therefore, the returned value card 8 is not activated. Therefore, it is possible to prevent the value card that has been treated as returned goods from becoming valid and preventing unauthorized use by a store clerk, for example.

[Second Embodiment]
Next, a second embodiment will be described with reference to FIGS.
In the first embodiment, when the activation of the value card 8 fails, the value card sales receipt 70 is issued by the operation of the closing key for declaring the closing of one commercial transaction, and the activation of the value card 8 has failed. Is notified to the user (the cashier and the customer). For this reason, when the customer cancels the purchase of the value card 8, it is dealt with by a return transaction.

  In the second embodiment, when the activation of the value card 8 fails, the user is notified before the closing of one commercial transaction is declared. In this way, when the customer cancels the purchase of the value card 8, it can be dealt with in the same transaction by the single item cancellation processing.

  Such a 2nd embodiment is realizable by changing a part of subtotal key process which CPU11 of POS terminal 4 performs from a 1st embodiment. Others are the same as the first embodiment. For this reason, the second embodiment will be described by assigning the same reference numerals to the parts common to the first embodiment.

  FIG. 16 is a flowchart showing a subtotal key process procedure according to the second embodiment. In FIG. 16, the same step code (STx) is attached to the processing block common to the first embodiment.

  That is, the second embodiment is different from the first embodiment in processing when a normal response cannot be received within a predetermined time in response to a value card activation request. If the normal response cannot be received within the predetermined time (NO in ST4), the CPU 11 displays an validation error message screen on the operator display 23 and the customer display 24 (ST61: display control means).

  An example of the validation error message screen 91 displayed on the operator display 23 is shown in FIG. An example of the validation error message screen 92 displayed on the customer display 24 is shown in FIG. As shown in the figure, on the activation error message screens 91 and 92, the name of the value card (gift card 1000, gift card 500) that has failed to be activated, and the value card is not yet activated but is used immediately. It is displayed that it cannot be used, but if it is within 24 hours, it will be validated without fail. In addition, the validation error message screen 91 displayed on the operator display 23 includes a guidance (continuation declaration → X key) indicating an operation key when the customer does not cancel the purchase of the value card 8, and a notification when the purchase is canceled. A guidance (cancellation declaration → cancel key) indicating the operation key is displayed.

  The CPU 11 waits for the operation key (X key) for the continuation declaration or the operation key (cancel key) for the cancellation declaration to be operated (ST62: selection accepting means). If the continuation declaration operation key is input, the CPU 41 proceeds to subtotal processing (ST6).

  On the other hand, when a cancel declaration operation key is input, the CPU 41 deletes the transaction data of the value card 8 from the transaction buffer 30. Specifically, the deletion flag of the corresponding data is set to “1” (ST63: sales cancellation processing means). Thereafter, the CPU 11 shifts to a subtotal process (ST6).

  As described above, in the merchandise sales data processing apparatus according to the second embodiment, when activation of the value card 8 fails, the activation error message screens 91 and 92 notify the cashier and the customer.

  Here, when the customer purchases the value card 8 that has failed to be validated as it is, the closing key process is executed following the subtotal process. Accordingly, the value card sales receipt 70 is issued, and information including the card ID of the value card 8 is stored in the re-request buffer 50 of the store server 5. As a result, for example, an activation request for the value card 8 is executed from the store server 5 to the value card management server 3 at one hour intervals.

  On the other hand, when the customer cancels the purchase of the value card 8 that has failed to be activated, the transaction data of the value card 8 is deleted from the transaction buffer 30. For this reason, even if the closing key process is executed subsequent to the subtotal process, information including the card ID of the value card 8 is not stored in the re-request buffer 50. Therefore, the value card 8 whose purchase has been canceled is not activated. Therefore, it is possible to prevent the value card that has been treated as returned goods from becoming valid and preventing unauthorized use by a store clerk, for example.

Hereinafter, modifications of the embodiment will be described.
For example, in the closing key process of FIG. 9, after the transaction closing process of ST11, the validation error determination process of ST13 is executed, and when there is no validation error (NO of ST13), after issuing the transaction receipt, Send data (ST14), clear transaction buffer (ST18), and if there is an validation error (YES in ST13), issue a value card sales receipt (ST15), issue a transaction receipt, Thereafter, the processes of steps ST16, 17, and 18 may be executed. In this way, if the activation of the value card 8 fails, the value card sales receipt is issued first, and then the transaction receipt is issued, so that the cashier has issued the value card sales receipt, In other words, it is possible to reliably recognize that the activation of the value card 8 has failed.

  Further, in the second embodiment, the validation error message is notified in the display format, but the notification method is not limited to the display format. For example, the content of the validation error message may be notified by voice. Further, the customer display 24 is used as a touch panel, and the operation button images of the operation key for continuation declaration and the operation key for cancellation declaration are displayed on the validation error message screen 92 displayed on the customer display 24. By doing so, the customer can select whether or not to purchase a value card that has failed to be activated.

  In the first and second embodiments, the POS system 1 including the POS terminal 4 and the store server 5 is the merchandise sales data processing apparatus, but includes the re-request buffer 50 provided in the store server 5, for example. By providing an essential configuration on the POS terminal 4 side, the POS terminal 4 may be a merchandise sales data processing apparatus.

  In the first and second embodiments, it is assumed that control programs for realizing the functions of the invention are recorded in advance in the program storage units (ROMs 13 and 43) inside the devices of the store server 5 and the POS terminal. However, the present invention is not limited to this, and a similar program may be downloaded from the network to the apparatus. Alternatively, a similar program recorded on the recording medium may be installed in the apparatus. The recording medium may be in any form as long as it can store a program such as a CD-ROM or a memory card and can be read by the apparatus. Further, the function obtained by installing or downloading the program may be realized in cooperation with an OS (operating system) in the apparatus.

  In addition, although several embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the scope of the invention. These embodiments and modifications thereof are included in the scope and gist of the invention, and are included in the invention described in the claims and the equivalents thereof.

  DESCRIPTION OF SYMBOLS 1 ... POS system, 2 ... Value card database, 3 ... Value card management server, 4 ... POS terminal, 5 ... Store server, 8 ... Value card, 30 ... Transaction buffer, 50 ... Re-request buffer.

Claims (6)

A sales processing means for processing product sales data based on the data of the input purchased product;
Returns processing means for processing product sales data based on the returned product data entered,
When the product sales data processed by the sales processing means includes sales data of a product that is required to be transmitted to the server as proof data that the product has been properly sold when the product is sold, the proof of the product Validation request means for sending data to the server;
An validation re-requesting unit that repeats retransmission of the certification data until the validation request is approved when the validation request is not approved by the server for sending the certification data by the validation request unit;
When the merchandise sales data processed by the return processing means includes the data of the merchandise for which the re-sending of the certification data is repeated by the validation re-requesting means, the re-request stop means for terminating the retransmission of the certification data When,
A product sales data processing apparatus characterized by comprising: A re-request buffer for storing certification data of a product whose activation request has not been approved by the server;
The validation re-request means re-sends proof data of a product whose data is stored in the re-request buffer,
2. The merchandise sales data processing apparatus according to claim 1, wherein the re-request stop means clears proof data of merchandise included in the merchandise sales data processed by the return processing means from the re-request buffer. A printer that prints a receipt showing details of the merchandise sales data processed by the sales processing means;
The returned goods processing means is such that when the returned goods are goods for which the certification data is required to be sent to the server, the goods for which the printer is operated and the certification data is required to be sent to the server are returned. 2. The merchandise sales data processing apparatus according to claim 1, further comprising a process of printing information for specifying the information on a receipt sheet. A sales processing means for processing product sales data based on the data of the input purchased product;
When the product sales data processed by the sales processing means includes sales data of a product that is required to be transmitted to the server as proof data that the product has been properly sold when the product is sold, the proof of the product Validation request means for sending data to the server;
A selection accepting means for accepting a selection input as to whether or not to cancel the purchase of the product when the validation request is not approved by the server for the transmission of the certification data by the validation request means;
When the selection accepting unit accepts the selection input for non-cancellation of purchase of the product, the validation re-requesting unit that repeats retransmission of the certification data until the validation request is approved;
When the selection accepting unit accepts a selection input for canceling the purchase of the product, a sales cancellation processing unit that deletes the product data from the product sales data processed by the sales processing unit;
A product sales data processing apparatus characterized by comprising: Display control means for displaying on the display for customer that the authorization request is not approved when the validation request is not approved by the server for the transmission of the certification data by the validation request means;
The product sales data processing device according to claim 4, further comprising: Sales processing means for sales processing of the product sales data based on the data of the input purchased product, return processing means for return processing of the product sales data based on the input data of the returned goods, and processing by the sales processing means When the product sales data includes the sales data of a product that is required to be sent to the server as proof data that the product was properly sold when the product was sold, the proof data of the product is sent to the server A computer connected via a communication line to a POS (Point Of Sales) terminal provided with an enabling request means for
An validation re-request function that repeats retransmission of the certification data until the validation request is approved when the validation request is not approved by the server for sending the certification data;
A re-request stop function for ending the re-transmission of the certification data when the product sales data processed by the return processing means includes the data of the product for which the re-transmission of the certification data is repeated by the validation re-request function When,
A program to realize

Images