JP5143922B2 - Data processing apparatus and program - Google Patents

Description

  The present invention relates to a data processing apparatus and program used in a system for providing services to customers.

  In general, merchandise sales stores and the like perform accounting processing of purchased merchandise using a merchandise sales data processing device such as a POS (Point Of Sales) terminal. For example, at that time, points corresponding to the transaction amount are calculated and accumulated for each customer in the storage medium owned by the customer, management server, etc., and a discount ticket etc. is issued when the predetermined number of reference points is reached In addition, point management systems that provide services such as cash back from the accounting amount according to the number of points are also widespread.

  In the point management system with the provision of the service as described above, when a service based on the number of points is provided at the time of selling the product, a predetermined number of points is subtracted from the accumulated points to 0 points. Close situation. When a customer returns a product after a transaction involving the provision of such a service is performed, the number of points corresponding to the amount of the returned product is subtracted from the accumulated number of points. At that time, even if the result of subtraction becomes negative, it is generally operated to raise it to 0 points. As described above, for example, a point management apparatus and a merchandise sales data processing apparatus described in Patent Document 1 are known as techniques for subtracting points during merchandise return processing.

JP 2000-322656 A

  However, even if the predetermined points are subtracted from the accumulated points at the time of merchandise return processing, discount cards that have already been issued are not usually collected. Some customers deliberately perform such actions and illegally obtain discount coupons. As a result, there has been a problem that the store side suffers damage due to use of illegally obtained discount coupons.

  The present invention has been made based on the circumstances as described above, and its purpose is to easily identify a customer who intends to carry out unauthorized return processing and to prevent damage to the store in advance. It is to provide a device and a program.

A data processing apparatus according to an embodiment includes a customer code input unit that inputs a customer code assigned to a customer, a sales processing unit that sells a customer's purchased product, and a service providing that provides a predetermined service during the sales process And a customer code input by the customer code input means, and when the service is provided by the service providing means, the customer code input by the customer code input means and the transaction provided by the service providing means The history creation means for creating history information including the identification information, the identification information input means for entering the identification information of the transaction in which the product to be returned at the time of return processing is sold, and the history information created by the history creation means Of these, the same information as the history information having the identification information input by the identification information input means is used. It has a code, and the number of history information return processing has been performed in the past and a, and informing means for informing a warning when has reached a predetermined reference value.

  According to the present invention in which such measures are taken, it is possible to provide a data processing device and a program that can easily identify a customer who intends to perform an illegal return process and prevent damage to the store.

The schematic block diagram of the point management system in this Embodiment. The block diagram which shows the principal part structure of the POS terminal in the embodiment. The block diagram which shows the principal part structure of the management server in the embodiment. The schematic diagram which shows an example of the data structure of the customer master in the embodiment. The schematic diagram which shows an example of the data structure of the ticket issue log | history data file in the embodiment. The flowchart of the process which CPU of a POS terminal performs in the sales process in the embodiment. The flowchart of the process which CPU of a management server performs in the point inquiry process in the embodiment. The flowchart of the process which CPU of a management server performs in the ticket issue log | history data creation process in the embodiment. The flowchart of the process which CPU of a POS terminal performs by the returned goods process in the embodiment. The flowchart of the process which CPU of a management server performs in the defective customer inquiry process in the embodiment.

The best mode for carrying out the present invention will be described below with reference to the drawings.
FIG. 1 is a schematic configuration diagram of a point management system to which the present invention is applied. The point management system includes, for example, a plurality of stores 2 such as retail stores and a headquarter 1 that supervises each store 2 via a network such as a LAN (Local Area Network). The headquarters 1 is provided with a management server 3 that performs cumulative management of points given to customers, and each store has one or more POS terminals 4 and a card reader / writer (R / W) 5. A ticket issuing printer 6 is connected and installed. The card reader / writer 5 can read and write data stored in a storage medium 7 such as a point card possessed by the customer, and the customer code uniquely assigned to each customer is stored in the storage medium 7. Is remembered. On the other hand, the ticket issuing printer 6 issues a receipt on which transaction details are printed and a predetermined discount ticket by driving control of the POS terminal 4.

  In this embodiment, the number of points corresponding to the transaction amount is given to the customer during the sale processing of the product, and the number of points is added to the number of points possessed by the management server 3 and accumulated. As a result, a case where a discount ticket is issued on the spot when a predetermined number of points is reached will be described.

  FIG. 2 is a block diagram showing a main configuration of the POS terminal 4. The POS terminal 4 includes a CPU (Central Processing Unit) 10 as a control entity, a ROM (Read Only Memory) 11 in which fixed data such as a program is stored, and various memories for storing various data in a rewritable manner. Random Access Memory (RAM) 12 in which an area is formed, a clock unit 13 that measures the date and time, a communication unit 14 that controls data communication with devices connected to the outside via a communication line, and a display that performs various displays A display controller 15 that controls the screen display of the device 20, an input controller 16 that captures input signals from an input device 21 such as a keyboard, an I / O port 17 that outputs an open command signal to the drawer 22, and a ticketing printer 6 are controlled. The printer controller 19 is connected by a bus line 23 such as an address bus or a data bus.

  FIG. 3 is a block diagram showing a main configuration of the management server 3. The management server 3 is connected to a CPU 30 as a control subject through a ROM 31 in which fixed data such as programs are stored, a RAM 32 in which various memory areas for storing various data are rewritable, and a communication line. A communication unit 33 that controls data communication with an externally connected device, a display controller 34 that controls screen display of a display device 37 that performs various displays, an input controller 35 that captures input signals from an input device 38 such as a keyboard, A hard disk drive controller 36 for controlling a hard disk drive (HDD) 39 for storing various data is connected by a bus line 23 such as an address bus or a data bus.

  The hard disk drive 39 has a customer master 50 (customer information storage means) for storing predetermined customer information for each customer, and a transaction history relating to the sales process when the POS terminal 4 issues a discount ticket during the sales process. And a ticketing history data file 51 (history storage means) are stored.

  FIG. 4 is a schematic diagram showing an example of the data structure of the customer master 50. The customer master 50 has a storage area for storing the customer name of the customer, the number of points possessed by the customer, the address of the customer, the contact information, and the defective customer flag for the customer code of the specific customer. Assigned. Normally, “0” is stored in the defective customer flag, but “1” is stored for a probable fraud customer. That is, the defective customer flag has a role of discriminating customer information of a customer who is likely to be fraud and other customer information (customer information distinguishing means). The process of determining a likely customer (hereinafter referred to as a bad customer) who is fraudulent will be described later with reference to FIGS.

  FIG. 5 is a schematic diagram showing an example of the data structure of the ticketing history data file 51. The ticket issuance history data stored in the file 51 is a transaction history created for a transaction when a discount ticket is issued to a customer during the sale processing of the product. In the ticketing history data, the customer code read by the card reader / writer 5 from the storage medium 7, the store code for specifying the store where the transaction was performed, the POS code for specifying the POS terminal 4 that performed the sales process, and the transaction are performed. The transaction date assigned to the transaction, the ticketing points that are the number of points corresponding to the issued discount coupon, and the return flag that distinguishes whether or not the product purchased by the customer in the transaction has been returned A storage area is allocated.

  The transaction number identifies a sales process performed by the POS terminal 4 on a specific date, for example, is issued with a serial number for each sales process at each store and is reset whenever the date changes. In the data area of the return flag, “0” is normally stored, and “1” is stored when the product is returned. That is, the return flag has a role of distinguishing the transaction history in which the return process has been performed from other transaction histories (history distinguishing means).

Next, the operation of the point management system having the above configuration will be specifically described.
FIG. 6 is a flowchart of a process performed by the CPU 10 of the POS terminal 4 in the merchandise sales process. A customer who wants to purchase a product carries the product to a cash register and presents the storage medium 7 owned by the customer to the cashier. Then, the cashier inserts the storage medium 7 into the card reader / writer 5. At this time, the CPU 10 drives and controls the card reader / writer 5 via the card reader / writer controller 18 as ST101, reads the customer code stored in the inserted storage medium 7, and stores it in the RAM 12.

  Next, the cashier inputs the product code by reading the barcode attached to the product to be purchased by the customer with a barcode scanner (not shown). At this time, the CPU 10 obtains product data from the product master based on the product code input as ST102 and performs registration processing. Next, the CPU 10 determines whether or not the tightening key disposed on the input device 21 has been operated in ST103, and when determining that the tightening key has not been operated (No in ST103), the CPU 10 determines the next product. Registration processing is performed (ST102). On the other hand, when the CPU 10 determines that the closing key has been operated (Yes in ST103), the CPU 10 calculates the total amount of the goods registered in the accounting process, that is, the process in ST102, and drives and controls the ticket issuing printer 6. The receipt is issued, and the drawer 22 is opened through the I / O port 17. At this time, for example, transaction details, transaction date, transaction number, etc. are printed on the receipt.

  Next, the CPU 10 calculates the number of points to be given to the customer according to the total amount calculated in the accounting process as ST105. After that, the CPU 10 sends the point calculated as ST106 and the customer code stored in the RAM 12 in the processing of ST101 to the management server 3 together with the point inquiry command to inquire about the number of points possessed by the customer. At this time, the number of points possessed by the customer is returned from the management server 3, and the processing performed in the management server 3 during that time will be described later in the description of FIG.

  When receiving the number of points possessed by the customer from the management server 3, the CPU 10 determines whether or not the number of points has reached a predetermined number of ticket issuing points necessary for issuing a discount ticket as ST107. This determination is made, for example, by previously storing the predetermined number of ticket issuing points in the ROM 11 and comparing the number of ticket issuing points with the number of points possessed by the customer. When the CPU 10 determines that the ticket issuing point has been reached (Yes in ST107), the CPU 10 drives and controls the ticket issuing printer 6 via the printer controller 19, for example, and issues a predetermined discount ticket as ST108. Then, the CPU 10 transmits the customer code, the store code, the POS code, the transaction date, the transaction number, and the ticket issuing point stored in the RAM 12 in the process of ST101 to the management server 3 as ST109 together with a notification that the discount ticket has been issued. . The processing performed in the management server 3 at this time will be described later with reference to FIG. The CPU 10 ends the accounting process.

  FIG. 7 is a flowchart of the point inquiry process executed by the CPU 30 when the management server 3 receives the point number, customer code, and point inquiry command transmitted by the POS terminal 4 in the process of ST106. First, the CPU 30 searches the customer master 50 for customer information having the same customer code as the customer code received from the POS terminal 4 in ST201, and receives the points received from the POS terminal 4 in the number of points stored in the corresponding customer information. Add a number. Thereafter, the CPU 30 returns the point number after adding the number of points received from the POS terminal 4 in the process of ST201 as ST202 to the POS terminal 4 and ends the point inquiry process.

  FIG. 8 shows the case where the management server 3 receives a notification that a customer code, a store code, a POS code, a transaction date, a transaction number, a ticketing point, and a discount ticket transmitted by the POS terminal 4 in the process of ST109 are issued. It is a flowchart of the ticket issue history data creation process which CPU30 performs. First, the CPU 30 retrieves customer information from the customer master 50 using the customer code received from the POS terminal 4 in ST301, and subtracts a predetermined number of points from the number of points stored in the corresponding customer information. Thereafter, the CPU 30 creates new ticket issuing history data in the ticket issuing history data file 51 as ST302. Specifically, the customer code, store code, POS code, transaction date, transaction number, and ticketing point received from the POS terminal 4 as new ticketing history data are stored in the data area of the ticketing history data file 51, and the return flag is stored. Set to “0”. After the process of ST302, the CPU 30 ends the ticket issue history data creation process.

Next, a return process for returning a product purchased by a customer will be described. When returning a product, for example, the customer brings a receipt issued at the time of the sales process of the product together with the product to be returned to the store where the product was purchased.
FIG. 9 is a flowchart of processing executed by the CPU 10 of the POS terminal 4 in the return processing. First, the CPU 10 stands by until the cashier inputs the transaction number printed on the receipt and the transaction date in ST401 (No in ST401). When the transaction number and the transaction date are input (Yes in ST401), the CPU 10 transmits, for example, the store code, the POS code, the input transaction number, and the transaction date to the management server 3 together with the defective customer inquiry command as ST402. Then, it is inquired whether or not the customer who performs the return processing is a defective customer. At this time, when the management server 3 determines that the customer is a defective customer, a warning notification to that effect is returned. The processing performed in the management server 3 during this period will be described later with reference to FIG. To do.

  Next, the CPU 10 determines whether or not a warning notification is received from the management server 3 in ST403. When it is determined that a warning notification is received from the management server 3 (Yes in ST403), the CPU 10 displays the warning on the display device 20, for example, and notifies the cashier as ST404 (notification means). After this notification, or when it is determined that a warning notification has not been received from the management server 3 in the process of ST403 (No in ST403), the CPU 10 performs a return process for the product that the customer intends to return as ST405. In the merchandise return processing, the POS terminal 4 and the management server 3 perform a refund of the transaction price to the customer and a subtraction of the number of points based on the refund amount. After the process of ST405, the CPU 10 ends the return process.

  FIG. 10 shows the bad customer inquiry process executed by the CPU 30 when the management server 3 receives the store code, POS code, transaction number, transaction date, and bad customer inquiry command transmitted by the POS terminal 4 in the process of ST402. It is a flowchart. First, the CPU 30 searches whether or not the ticket issuing history data of the corresponding transaction is stored in the ticket issuing history data file 51 based on the store code, POS code, transaction number and transaction date received as ST501. Then, the CPU 30 determines whether or not the corresponding ticket issue history data has been found in ST502 (history determination means). When determining that the corresponding ticketing history data has been found (Yes in ST502), the CPU 30 sets the return flag of the ticketing history data found in ST503 to “1”. After that, the CPU 30 searches the ticket issue history data file 51 for ticket issue history data having the same customer code as the customer code of the ticket issue history data discovered in ST504 and having the return flag “1”, and issues the corresponding ticket issue. The number n of history data (n> 0; integer) is calculated (calculation means).

  Then, the CPU 30 determines whether or not the number n is greater than or equal to a reference value m (m> 1; integer) in ST505 (number determination unit). The reference value m is a determination reference value for determining whether the customer is a defective customer, and is set in advance and stored in, for example, the ROM 31. When it is determined that the number n is equal to or greater than the reference value m (Yes in ST505), the CPU 30 determines a defective customer flag identified from the customer master 50 by the customer code included in the ticketing history data found in ST501 as ST506. Is set to “1”. Then, the CPU 30 issues a warning notification to the effect that the customer who returns to the POS terminal 4 is likely to be fraudulent (warning notification means) in ST507, and ends the defective customer inquiry processing. .

  On the other hand, when it is determined that the corresponding ticketing history data has not been found in the process of ST502 (No in ST502) and when it is determined in the process of ST505 that the number n is not greater than the reference value m (No in ST505). The CPU 30 ends the defective customer inquiry process.

  As described above, in the point management system, when the POS terminal 4 provides the service during the sale processing of the product (ST108), the management server 3 creates ticketing history data for the transaction in the ticketing history data file 51. (ST302). On the other hand, when the POS terminal 4 accepts the return processing, it makes a bad customer inquiry to the management server 3 (ST402). In response to this, the management server 3 performs a bad customer inquiry process and is likely to be fraudulent. When it is determined that this is the case, a warning is sent to the POS terminal 4 (ST501 to ST507). Upon receiving this notification, the POS terminal 4 displays a predetermined warning on the display device 20 and notifies the cashier (STST 404). That is, the cashier can easily determine that the customer is performing a return process for an unauthorized purpose by looking at the warning displayed on the display device.

  Further, the customer master 50 that stores customer information for each customer is provided with a defective customer flag so that a customer who has performed the illegal return processing of the predetermined number m or more can be distinguished from other customers. Therefore, the manager of the point management system, etc., determines which customer is performing the return processing with an unauthorized intention by checking the bad customer flag in the customer master 50, and uses the storage medium 7 of the customer. By taking measures such as making it impossible, it is possible to prevent damage to the store.

  In addition, this invention is not limited to the said embodiment as it is, In an implementation stage, in the range which does not deviate from the summary, each component can be deform | transformed and embodied suitably.

  For example, the customer code is input by reading the storage medium 7 with the card reader / writer 5, but the present invention is not limited to this, and the cashier may be input from the input device 21 of the POS terminal 4.

  In addition, a discount ticket may not be issued according to the number of points that the customer has at the time of product sales, but other services such as cash cashback or gifts may be provided.

  Further, the history distinguishing means is not limited to the form using the return flag of the ticketing history data. For example, the ticket issuing history data that has been returned may be managed by moving it from the ticket issuing history data file 51 to another file. In such a case, the history distinguishing means is the control process for moving the other file and the ticketing history data that has been returned to the file.

  Moreover, it is good also as a structure which does not perform the process of ST504-ST507 in a defective customer inquiry process. That is, the ticket issue history data that has been returned by the return flag in the process of ST503 can be distinguished from other ticket issue history data, and the defective customer inquiry process is terminated. Even in this case, by processing the ticketing history data file 51, it is possible to identify a probable fraud customer, so that the effects of the present invention can be obtained.

  Further, the bad customer flag stored in the customer master 50 may be evaluated in more stages than “0” or “1”. In this case, a plurality of reference values that can be evaluated in more detail, for example, s, t, u (s <t <u; integer) are prepared instead of the reference value m. Then, the number n of ticketing history data whose return flag is “1” for a specific customer code is calculated from the ticketing history data file 51, and 0 ≦ n <s, s ≦ n <t, t ≦ n <u, u ≦. It is determined which range of n corresponds. Then, evaluation is performed by weighting “0”, “1”, “2”, “3” according to the corresponding range. If such an evaluation method is adopted, the store side can evaluate the fraud of the customer step by step, so that measures that act more effectively can be taken.

  In addition, various inventions can be formed by appropriately combining a plurality of constituent elements disclosed in the embodiment.

DESCRIPTION OF SYMBOLS 1 ... Headquarters, 2 ... Store, 3 ... Management server, 4 ... POS terminal, 5 ... Card reader / writer, 6 ... Ticket issuing printer, 7 ... Storage medium, 10 ... CPU, 11 ... ROM, 12 ... RAM, 13 ... Clock part , 14 ... communication section, 18 ... card reader / writer controller, 20 ... display device, 21 ... input device, 30 ... CPU, 31 ... ROM, 32 ... RAM, 33 ... communication section, 37 ... display device, 38 ... input device, 39 ... Hard disk drive, 50 ... Customer master, 51 ... Ticketing history data file

Claims (6)

A data processing device used in a system for providing services to customers,
A customer code input means for inputting a customer code assigned to the customer;
A sales processing means for selling and processing the customer's purchased products;
Service providing means for providing a predetermined service during the sales process;
When the customer code is input by the customer code input means and the service is provided by the service providing means, the customer code input by the customer code input means and the identification information of the transaction provided by the service providing means A history creation means for creating history information including
An identification information input means for inputting identification information of a transaction in which a product to be returned is sold during the return processing;
Of the history information created by the history creation means, the history information having the same customer code as the history information having the identification information input by the identification information input means and having been returned in the past. Informing means for informing a warning when the number has reached a predetermined reference value;
A data processing apparatus comprising: The service providing means provides a service to a customer corresponding to the customer code input by the customer code input means when a predetermined number of points given according to the sales processing by the sales processing means reaches a predetermined number. The data processing apparatus according to claim 1, wherein: When the service is provided by the service providing means, the apparatus further comprises subtracting means for subtracting a predetermined point from the points given to the customer corresponding to the customer code input by the customer code input means. The data processing apparatus according to claim 2, wherein the data processing apparatus is characterized in that: A printer,
Service provided by the service providing means, the data processing device according to any one of claims 1 to 3, characterized in that it is issuing a discount coupon to the printer, it is.   5. The apparatus according to claim 1, further comprising a receipt issuing unit that issues a receipt printed with the identification information included in the history information created by the history creating unit. Data processing device. A data processing apparatus having customer code input means for inputting a customer code assigned to a customer and identification information input means for inputting transaction identification information;
A sales processing function that sells the customer's purchases;
A service providing function for providing a predetermined service during the sales process;
When a customer code is input by the customer code input means and a service is provided by the service providing function, the customer code input by the customer code input means and identification information of a transaction provided by the service providing function History creation function to create history information including
When the identification information of a transaction in which a product to be returned at the time of the return processing is sold is input via the identification information input means, the input identification information among the history information generated by the history generation function is A notification function for notifying a warning if the number of pieces of history information that has the same customer code as the history information and that has been returned in the past has reached a predetermined reference value;
A program to realize

Images