JP2006185200A - Pos register - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a POS register that can facilitate the maintenance of a merchandise file even when a new producer who wants to sell product of his/her own making participates. <P>SOLUTION: The POS register has a producer file including producer codes and producer names, an item file including item codes and item names, means for generating merchandise codes according to the producer codes stored in the producer file and the item codes stored in the item file, generating merchandise names according to the producer names stored in the producer file and the item names stored in the item file, and generating merchandise data including the generated merchandise codes and merchandise names, and means for adding merchandise data corresponding to the number of producers or the number of items to a merchandise file. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a POS register used in a store, and in particular, reads a barcode attached to a product purchased by a customer, reads product data corresponding to the product code therein from a product file, and registers the product. It relates to the POS register to be performed.

  In recent years, in addition to the conventional sales route, for example, a form in which local special products such as agricultural products are directly sold to consumers at agricultural products direct sales offices is often seen. In this way, in the form in which producers sell their produce, etc. at a common store, how many of which producers have been sold in order to distribute sales according to sales performance Need to know exactly.

  Therefore, conventionally, a unique number is assigned for each producer and for each item, and sales results are managed by this unique number.

In addition, the producer makes a reservation registration of the producer, sales item, unit price, quantity, and sales date in the POS register of the retail store using the Internet, receives a notification such as a reservation number from the POS register, and uses this as a barcode. A consignment sales system that prints, affixes to a sale, and ships to a retail store has been proposed (see, for example, Patent Document 1).
JP 2002-183245 A

  However, in the form of sales using stores as described above, there are many cases in which new producers who want to sell their own crops participate, and in such cases, the crops produced by the new producer each time. There is a problem that it is complicated to add the item or the like to the product file.

  Therefore, the present invention has been made in view of the above-described problems, and even when a producer who wants to sell his / her farm products newly participates, maintenance of a product file can be performed by a simple method. An object is to provide a POS register that can be executed.

In order to solve the above-described problems, the present invention proposes the following matters.
The invention according to claim 1 is a POS register for registering a product by reading out the corresponding product data from the product file including the product code and the product name when the product code is input. Production including the producer code and the producer name A product code is generated based on the producer file, the item file including the item code and the item name, the producer code stored in the producer file, and the item code stored in the item file, and the producer Product data generating means for generating a product name based on the producer name stored in the file and the item name stored in the product file, and generating product data including the generated product code and product name; And a product file update means for adding product data corresponding to the number of producers or the number of items to the product file. It has proposed a register.

  The invention according to claim 2 is the POS register according to claim 1, further comprising a classification file, storing producer data in a part of the classification file, wherein the product file includes a classification code, and the producer code Proposes a POS register that also serves as the classification code.

  According to a third aspect of the present invention, there is provided a producer file updating means for adding producer information including a producer code and a producer name to the producer file with respect to the POS register according to the first or second aspect. When the producer information is added by the producer file update means, the product file update means adds product data corresponding to the number of items of the added producer to the product file. The POS register is proposed.

  The invention according to claim 4 is provided with item file update means for adding item information including an item code and an item name to the item file for the POS register according to claim 1 or 2, and the item file A POS register is proposed in which, when item information is added by the updating means, the product file updating means adds product data corresponding to the number of producers to the product file.

  According to a fifth aspect of the present invention, in the POS register according to any one of the first to fourth aspects, the product code generated by the product data generation means is a nonplu barcode format. Has proposed.

  According to the present invention, even when a new producer frequently joins in a store or the like in which the producer sells the crops produced by the producer himself, the sales data of the new producer is recorded. There is an effect that product data that can be analyzed can be easily created.

  In addition, even when a certain producer adds a new item, product data of the same item is created for other producers, so that the labor for maintaining the product file can be reduced.

  Furthermore, according to the present invention, since the producer code also serves as the classification code, there is an effect that the sales performance for each classification can be easily analyzed.

  In addition, if you add data to the producer file, the data will be added to the product file for the corresponding number of items, and if you add data to the item file, the data will be added to the corresponding number of producers. This has the effect of reducing the labor of maintaining product files.

  Further, since the NONPLLU barcode is used by attaching a label printed with a barcode created at each store to a product, the barcode is easily matched.

Hereinafter, a POS register according to an embodiment of the present invention will be described in detail with reference to FIGS.
1A and 1B are diagrams showing a POS register according to an embodiment of the present invention. FIG. 1A is a front view and FIG. 1B is a side view.
The POS register 1 is a key operation provided with a liquid crystal touch panel 112 for making various inputs by touching the display screen, a function key that is frequently used for product registration and settlement, a numeric keypad, a current key 114a used as a closing key, and the like. Unit 114, a receipt issuing port 109 through which a receipt printed by a receipt printing unit (not shown) is discharged, and a customer display unit 116 that displays the name of the purchased product, the purchase price, the total purchase price, etc. to the customer A card reader unit 118 for reading information stored in the card when shopping with the card, a scanner unit for reading a barcode attached to a product (not shown) and registering the product, and a drawer (not shown) Yes.

FIG. 2 is a block diagram showing an electrical configuration of the POS register 1.
As shown in FIG. 2, the POS register 1 includes a CPU 100 (product data generation means, product file update means, producer file update means, item file update means), a hard disk unit 102, and a RAM (Random Access Memory) 104. The receipt printing unit 108, the scanner unit 110, the liquid crystal touch panel 112, the key operation unit 114, the customer display unit 116, the card reader unit 118, and the bus line 120.

  The CPU 100 controls each unit of the apparatus based on a control program stored in the hard disk unit 102. In the present embodiment, a product code is generated based on the producer code stored in the producer file in the hard disk unit 102 and the item code stored in the item file in the hard disk unit 102, and the producer file The product name is generated based on the producer name stored in the item name and the item name stored in the item file, and product data including the generated product code and the product name is generated.

  Further, the product data corresponding to the number of producers or items is added to the product file. Further, the producer information including the producer code and the producer name is added to the producer file, and the item information including the item code and the item name is added to the item file.

  The hard disk unit 102 stores programs executed by the CPU 100 to realize various functions of the POS register 1, various files such as a producer file, an item file, and a classification file, actual data generated in the POS register 1, and the like.

  The RAM 104 is a rewritable recording medium that temporarily stores data and the like, and includes an area for storing a flag and a register for the CPU 100 to operate. Further, the printing unit 108, the scanner unit 110, the liquid crystal touch panel 112, the key operation unit 114, the customer display unit 116, and the card reader unit 118 are as described above. Note that these electrical components are connected to each other via a bus line 120.

  FIG. 4 illustrates the producer file. The producer file in the present embodiment uses a classification file that is conventionally provided in PLU (Price Look Up), and each item of a producer code as a small classification, name, sales record, and department code. It is composed of Among these, the department code is a major classification code of a product, and the producer code is also a minor classification code on the classification file, and can be used as a minor classification file.

  Of the codes shown in the code column of FIG. 4, a code that matches the code specified in the producer code range designation table shown in FIG. 7 means the producer code, and in the producer code range designation table, A code outside the specified range means a minor classification code.

  Here, the producer code range specification table is stored in the hard disk unit 102, and defines the number of digits of the code meaning the producer data and the range in the producer file. As described above, by associating the code on the producer file with the code of the producer code range specification table, in the present embodiment, the small classification file on the classification file provided conventionally is also used as the producer data. Has realized.

  Specifically, in the case of FIG. 7, the number of digits of the producer code is 3 digits, and the usage range is set to 301 to 400. Therefore, in FIG. 4, the codes corresponding to 301 to 400 are producer codes, and information corresponding to the producer codes is stored in association with each other.

  As shown in FIG. 5, the item file is composed of a code and a name, which can be set in association with each other. Specifically, in the case of FIG. 5, the code “17” corresponds to the product “strawberry”, and the code “18” corresponds to the product “cucumber”.

  As shown in FIG. 6, the product file includes a product code, a product name, a producer code, a sales record, and a price, which can be set in association with each other. The column of producer code can also be used as a small classification code. Specifically, in the case of FIG. 6, the product code “02301117000000” corresponds to the product name “Teraoka strawberry”, the producer code “301”, and the record “0”.

Next, the processing operation of this embodiment will be described with reference to FIG.
First, when the POS register 1 is powered on, the CPU 100 determines whether or not the current operation mode is the producer file shown in FIG. 4 or the item file setting mode shown in FIG. 5 (step 101). If the CPU 100 determines that the current operation mode is not the producer file setting mode shown in FIG. 4 or the item file setting mode shown in FIG. 5, the CPU 100 next determines whether or not it is a product registration mode (step 102).

  As a result, when it is determined that the registration mode is selected, the barcode attached to the product is read using the scanner unit 110, and the product data corresponding to the product code corresponding to the barcode is stored in the hard disk unit 102. Read from the stored product file, or if the barcode is NONPLU, read the price directly from the barcode and register the product (step 103), process the payment from the customer and settle (Step 104).

  Then, the producer file shown in FIG. 4 stored in the hard disk unit 102 and the result area in the product file shown in FIG. 6 are registered or updated based on the settlement data (step 105), and then the process returns to step 101. If the CPU 100 determines that it is not in the registration mode in step 102, after performing processing other than the setting or registration mode, for example, outputting or maintaining a sales performance report for each producer (step 106), the step Return to 101.

  On the other hand, when the CPU 100 determines in step 101 that the current operation mode is the setting mode, it is next determined whether or not to set the producer file shown in FIG. 4 (step 107). . At this time, if it is determined that the producer file shown in FIG. 4 is to be set, the operator waits for input of producer data such as a code and name by the operator, and the input data is converted into the producer file shown in FIG. Add (step 108).

  Subsequently, the number of items set in the item file shown in FIG. 5 stored in the hard disk unit 102 is counted, and the count result is stored in the RAM 104 (step 109). Further, one item code and name in the item file shown in FIG. 5 are read, and product data is automatically generated using the producer code and name temporarily stored in the RAM 104.

  Specifically, when the producer code is “301”, the item code is “17”, the amount is “0000 yen”, the fixed data indicating the NONPLU code is “02”, and the check digit is “00”. Are arranged in the order of fixed data, producer code, item code, amount of money, and check digit, and a product code “02 301 017 0000 00” as shown in FIG. 6 is created (step 110). At this time, the product name is “Teraoka Strawberry” which is a combination of the producer name “301 = Teraoka” and the item “17 = Strawberry”. The product code “301” and the result “0” are used as new product data as shown in FIG. (Step 111).

  When the addition to the product file is performed, the CPU 100 determines whether or not the addition process for the count value temporarily stored in the RAM 104 has been completed, and the addition process for the count value temporarily stored in the RAM 104 has been completed. If it is determined that there is not, the process returns to step 110 (step 112).

  If the count value is the number of items, the same processing is performed based on the next item data in the item file shown in FIG. When the count value is the number of producers, processing is performed based on the next data in the producer file shown in FIG. Here, the number of producers and producer data are obtained from the producer file shown in FIG. 4 and the producer code range designation table shown in FIG. If the CPU 100 determines that the addition process for the count value temporarily stored in the RAM 104 has ended, the process returns to step 101.

  On the other hand, if it is determined in step 107 that the CPU 100 does not set the producer file shown in FIG. 4, it is next determined whether or not to set the item file shown in FIG. 5 (step 113). . If it is determined that the item file shown in FIG. 5 is to be set, the item file addition process shown in FIG. 5 is executed in the same manner as step 108 (step 114).

  When the item file addition process shown in FIG. 5 is completed, the number of producers is counted from the producer file shown in FIG. 4 and the producer code range designation table shown in FIG. 7 (step 115). Then, the count value is temporarily stored in the RAM 104, and the process returns to Step 110. If the item file shown in FIG. 5 is not set in step 113, the process returns to step 101 after performing other processes (step 116).

  Therefore, according to this embodiment, even if a new producer frequently joins in a store or the like in a form where the producer sells the crops produced by the producer himself, the new producer's Product data that can analyze sales data can be easily created. Further, even when a certain producer adds a new item, merchandise data for the same item is created for other producers, so the labor for maintaining the merchandise file can be reduced.

  As described above, the embodiments of the present invention have been described in detail with reference to the drawings, but the specific configuration is not limited to these embodiments, and includes design changes and the like within a scope not departing from the gist of the present invention. It is. For example, in the present embodiment, the processing when a producer or item is added has been described. However, when data is deleted in the producer file and the item file, what is the case of adding data? Conversely, all the product data including the deleted data may be deleted from the product file to return to the state before the data addition. The file names of the producer file and the item file are not limited to this, and any file having the same meaning may be used. In addition to adding or deleting product files in synchronization with the addition or deletion of producer files or item files, whether or not there is product data corresponding to producer data and item data is regularly checked. You may make it check and add a shortage.

It is an external view of a POS register according to the present embodiment. It is an electrical configuration block diagram of a POS register according to the present embodiment. It is an operation flow of the POS register according to the present embodiment. It is the figure which illustrated the producer file concerning this embodiment. It is the figure which illustrated the item file which concerns on this embodiment. It is the figure which illustrated the goods file concerning this embodiment. It is the figure which illustrated the producer code range specification table concerning this embodiment.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 ... POS register, 100 ... CPU, 102 ... Hard disk part, 104 ... RAM, 108 ... Receipt printing part, 109 ... Receipt issue port, 110 ... Scanner part, 112 ... Liquid crystal touch panel, 114 ... Key operation part, 114a ... Current key, 116 ... Display part for customer, 118 ... Card reader part, 120 ... Bus line,

Claims (5)

When the product code is input, the corresponding product data is read from the product file including the product code and the product name, and the product is registered in the POS register.
A producer file containing the producer code and producer name, and
An item file containing the item code and item name;
A product code is generated based on the producer code stored in the producer file and the item code stored in the item file, and the producer name stored in the producer file and stored in the item file Product data generating means for generating product data based on the item name and generating product data including the generated product code and product name;
Product file update means for adding product data corresponding to the number of producers or items to the product file;
A POS register comprising: With a classification file,
Producer data is stored in a part of the classification file,
The POS register according to claim 1, wherein the product file includes a classification code, and the producer code also serves as the classification code. A producer file update means for adding producer information including a producer code and a producer name to the producer file;
When producer information is added by the producer file update means, the product file update means adds product data corresponding to the number of items of the added producer to the product file. The POS register according to claim 1 or 2. An item file updating means for adding item information including an item code and an item name to the item file;
2. The item file update unit adds item data corresponding to the number of producers to the item file when item information is added by the item file update unit. 2. The POS register described in 2. The POS register according to any one of claims 1 to 4, wherein the product code generated by the product data generation means is in a nonplu barcode format.

Images