JPS6051994A - Goods sales data processor - Google Patents

Abstract

(57) [Summary] This bulletin contains application data before electronic filing, so abstract data is not recorded.

Description

[Detailed Description of the Invention] [Technical Field of the Invention] The present invention relates to a product sales data processing device having a product data file that stores product data such as product code, name, unit price, etc. [Technical background of the invention and its Problem] Electronic carrier, single register (ECR, hereinafter abbreviated as register), or PO8 (Point of Sales) with multiple registers connected to one terminal control unit
Some product sales data processing devices such as systems include FL
Some products are provided with a product data file in the storage section that stores a plurality of product data unique to each product, such as a product code such as a U code or JAN code, name (product name), and unit price, for each product code. Then, when registering the product for sale, read the product code attached to the product's label or coupon using a reader such as a barcode scanner or optical reader (OCR), and search the above product data file using the read product code. and the product corresponding to this product code r-
Read out the evening.

The sales registration for the above product is then executed based on this product data. In addition, it is also possible to input the above-mentioned product code using the number keys provided on the key board without using the reader.

In such a product sales data processing device, it is necessary to previously store and set product data of products to be sold in a product data file before starting sales registration work. In conventional devices, the product data is stored in a product data file by operating a registration key provided on the card. That is, the apparatus was set to the "setting" business mode, and the product name, price, department number, etc. were entered by operating a combination of numeric keys and various function keys.

However, since the number of keys provided in the key date is limited, kana characters other than numbers.

When inputting alphabetic characters, etc., the combination of the numeric key and each of the 7 anonymous keys is complicated, and the number of key operations required to input one product data is large. There is a problem in that the work time increases and the work efficiency of the entire sales registration process decreases.Furthermore, since complicated key operations must be performed, there is a risk of incorrectly inputting product data.

[Purpose of the invention]

The present invention was made based on the above circumstances, and its purpose is to read product data with a reader such as a scanner or an optical reader, thereby converting the product data into a product data file. It is an object of the present invention to provide a product sales data processing system that can shorten the working time required for storage settings, improve the efficiency of the entire sales registration work, and greatly suppress erroneous settings.

[Summary of the invention]

In the present invention, a written object such as a label that describes the product data of each product to be stored and set in a product data file is created in advance, and the product data written in this written object is read with a reader. This product sales data processing device stores the read product data in the product data file.

[Embodiments of the invention]

Hereinafter, a product sales data processing device according to an embodiment of the present invention will be explained with reference to the drawings. Fig. 1 is a perspective view showing an electronic carrier and a system register (register) as a product sales data processing device. In other words, the key provided on the front of the housing 1? In addition to number keys 3 for inputting the sales amount and product code of the product, the code 2 includes a department key indicating the classification of the product, a control key 5, various funxy keys 6, and the like.

In addition, an electronic display section 7 is provided on the front upper part of the housing 1 to display the total amount of purchased products, etc., and a receipt issuing port 8 is formed in the middle part. Furthermore, the housing 1
A scanner 9 as a reader and an optical reader (OCR) are attached to the external connector of the J O is the code 1.
1. The scanner 9 is a device that reads data encoded in the code sb, and the optical reader 10 is a device that directly reads data such as two numbers. 5- The control key 5 controls the power on and off. This is a control switch for instructing the central processing unit to execute various tasks such as "registration,""acalculation," and "setting." Furthermore, "registration" is the process of storing the price of sold products in the storage unit, calculating the total price, etc., and printing the results on receipts and recording paper.
In addition, "settlement" means, for example, "settlement" at the end of the day's work.
This is a job to print out the total sales amount, total sales points, etc. accumulated in the storage section, and then clear the contents of the storage section.

Furthermore, "setting" is a task of presetting product data of a product to be sold in a product data file before starting the sales registration task.

FIG. 2 is a block diagram of the register.

A CPU (central processing unit*) 12 has a built-in arithmetic circuit, command register, etc., and a scanner 9 and an optical reading device 10.
．． The key performs various arithmetic processing based on input information from the address bus J3, data bus 14, etc.
, control signal 1#s6, the ROM J 6 stores fixed data of GLODARAM such as "registration", "payment", "setting", inputted sales data of each product and the above-mentioned product data file. The RAM Z7 which stores the data etc. is operated. Further, a reader input circuit 18 receives data signals from the scanner 9 and the optical reading device 10, a key input circuit 19 receives key signals from the keypad 2, and commands from the control key 5. A control key input circuit 20 to which signals are input, a display control circuit 21 to send display drive signals to the display section 7, and a printer 22 to print out receipts.
The printer control circuits 23 each connect to the aforementioned data bus 1.
4 and the CPU l 2 via control signals 1!15
It is connected to the.

In the RAM 17, in addition to an area for storing sales data, as shown in FIG.
Two product data files, an AN file 25, and a confirmation buffer 26 are formed. PLU file 2
4 contains PLU (Pr1ce L) as the product code.
(look up) Code 24a1 Product name 24b1 Unit price 24c1 A plurality of product data are stored in order of PLU code number, including the department 24d to which it belongs, status, etc. On the other hand, in the yAN file 25, JAN: y-do 25a1 name 25b1 unit price 25
Product data consisting of c1 department 25d, etc. is stored. Further, the confirmation buffer 26 is for temporarily storing product data read by the scanner 9 or the optical reading device 10.

In such a register, when setting product data to be stored in the product data file of the PLU file 24 or the JAN file 25, the CPU 12 is configured to carry out the setting work according to the flowcharts of FIGS. 4 to 6. There is. First, before starting Grodarum, the product code of the product that should be stored and set is the PLU code or JAN code.

Product data consisting of name, unit price, etc. is encoded and printed on a label or the like. Accordingly, in the flowchart of FIG. 4, the control key 5 of the register is set to the "setting" task. Then, use the number key 3 to enter a number indicating the content of the "setting" task. For example, in the example, “
73" specifies the setting task for FLU 7 isle 24, and inputting r75J specifies the JAN file 25.
Setting tasks are specified. Next, the operator presses a specific function key 6 indicating that the selection of the setting task has been completed. After confirming that the 7th Angle key 6 has actually been pressed in P1, "73" is pressed in the numeric key 3 in P2, and the setting task for PLU 7 isle 24 is specified. If it is specified, move to rPAJ in FIG. 5. That is, in the flowchart of FIG. 5, the scanner 9 or the optical reading device 10 is operated to read the coded product r-type printed on the label. At P4, it is determined whether or not the product data has actually been read, and if it has not been read, it is read again using the scanner 9 or the optical reading device 10.

If it has been read in P4, search for the PLU code 24a of the PLU file 24 in RAM 17,
It is checked whether a PLU code 24a that is the same as the PI and U code of the product data read in P5 exists, and if the same PLU code does not exist, the read product data is checked once and sent to the PLU code 24a. Store. Next, the product data of the same label read earlier is read by the scanner 9 or the optical reader IO. After confirming that it has actually been incorporated in step P6, this read product data is compared with the previously read product data stored in the confirmation buffer 26.

Pl determines whether the above two product data are equal or not. If they are equal, it is determined that the product data has been read correctly, and the product data stored in the confirmation buffer 26 is newly stored in the PLU 7 fill 2J. After setting the storage, the contents of the confirmation buffer 26 are cleared. In addition, if the two product data are not equal in PLU, it is determined that one of the product data has been read by mistake, and PLU7 isle 2
Clear the contents of the confirmation buffer 10-26 without setting it to 4. Thus, the setting of the product data of one product in the PLU file 24 is completed. Next, in P8, it is determined whether the product data settings for all products have been completed, and if there is product data that has not been set, return to 1-PAJ and read the product code printed on the label again. start something. When the setting of all product codes is completed in P8, this setting work is ended. In addition, P5
If the same PLU code exists, it is determined that duplicate product data has been read, and the process proceeds to P8 without setting the PLU file 24.

On the other hand, at P2 in FIG.
3", proceed to P3, determine whether "75" is entered as a key and the setting task to the JAN file 25 is specified, and if it is specified, proceed to rPBJ in Fig. 6, Performs setting work for product data in the JAN file 25. In addition, the JAN file 2 of rPB J in Figure 6
5 is almost the same as the pitching task to the PLU file 24 of rPAJ shown in FIG. 5, so a description thereof will be omitted.

Furthermore, at P3, the key power of the iW number key is "75"
Otherwise, it is determined that this is a setting task other than the product data file setting task, and the process proceeds to P9.

If the register has such a configuration, when setting the product data file to store the product data of the product for sale, the product data of the product to be stored can be coded in advance and printed or handwritten on a label, etc. This product data is automatically stored in the PLU file 24 or the JAN 7 file 25 simply by reading the product data with a reader such as the scanner 9 or the optical reader 10 . Therefore, it is not necessary to perform a combination key operation of the number key 3 provided on the key 71 and the various function keys 6 to input the product data. As a result, the work time required to store and set product data in a product data file can be significantly reduced, and the efficiency of the entire sales registration process can be improved. Furthermore, since there is no need to perform complicated key operations, erroneous settings of product data can also be suppressed.

In particular, in this embodiment, the product data printed on the label is read twice, and only when the two times of data are equal, the product data is stored in the product data file, so product data may be incorrectly set. can be further suppressed.

In addition, in cases where many registers are installed in the same sales floor, such as Deno J F and large-scale supermarkets, it is only necessary to prepare one set of labels with each product data printed on them, so the above-mentioned The efficiency of the entire sales registration work can be further improved.

Note that the present invention is not limited to the embodiments described above. In the example, two product data files, the PLU file 24 and the JAN 7 file 25, are provided.
A product data file for only one of them may be provided. Furthermore, in the embodiment, the scanner 9 and the optical reading device 1
0 is used, but either one may be used.

13- FIG. 7 is a block diagram showing a POS system as a product sales data processing device according to yet another embodiment of the present invention. This POS system has a plurality of registers 31 connected in series to one terminal control unit 33 via a transmission line 32, and a scanner 9 and an optical reading device 10 are respectively connected to each register 3I.

Further, the terminal control section 33 includes a file control section 36 to which a ROM 34 and a RAM 35 are connected, and a file unit 38 to which an output device such as a printer 37 is connected.
It is made up of. Then, R of the file control unit 36
AM 35 contains the PLU file shown in Figure 3,
A product data file such as a JAN file is created.

In the POS system having such a configuration, the terminal control unit 33 performs tasks such as responding to the timing of product data from each register 3I and collecting sales data of sales products transmitted from each register 31. And RAM
When storing the product data of each product in the product data file in the register 35, the product data printed on the label is read using the scanner 9 or the optical reader 10 provided in the register 3, and the product data is stored in the register once. The data is stored in the confirmation file provided in 31. Then, after reading the same product data again and confirming that the two product data are the same, this product data is transmitted to the file control section 36 of the terminal control section 33 via the transmission path 32. After confirming that the input product data has not been read in duplicate, the file control unit 33 stores and sets the product data in the product data file in the RAM 35.

Even with the product sales data processing device configured in this way, the product data is read by a reader such as the scanner 9 or the optical reader 10, so it is possible to obtain the same effect as the above-mentioned embodiment. It is possible.

Furthermore, in this embodiment, it is only necessary to input product data from any one of the plurality of registers 31.

Note that it is also possible to connect a reader to the terminal control section 33 and read product data directly without going through the register 31.

〔Effect of the invention〕

As explained above, according to the present invention, product data to be stored and set in a product data file is read by a reader such as a scanner or an optical reader. Therefore, it is possible to shorten the work time required to store and set product data in a product data file, improve the efficiency of the entire sales registration process, and significantly suppress erroneous settings.

[Brief explanation of drawings]

1 to 6 show a product sales data processing device according to an embodiment of the present invention. FIG. 1 is a perspective view 1, FIG. 4 to 6 are flowcharts showing the operation, and FIG. 7 is a professional configuration diagram showing a product sales data processing device according to another embodiment of the present invention. 〇2...Key is -de, 3...Number key, 5...Control key, 6...Function key, 9...
Scanner, 10... Optical reader (OCR), 12
...CPU, 77...Interval M124...PLU file, 25...JAN file, 26...Confirmation log, 31...Register, 33...Terminal control unit, 36... -File control section. Applicant's agent Patent attorney Takehiko Suzue 17-

Claims (1)

[Claims] It has a product data file that stores a plurality of product data unique to each product, which is made up of a plurality of data codes including at least a product code, for each product code. In a product sales data processing device that reads out product data and registers sales of the sales product based on the read product data, the product data file is used to store and set the product data of each product in the product data file. A product sales data processing device comprising: a reader for reading the product data; and means for storing the product data read by the reader in the product data file.