JP3891040B2 - Sales data processing system - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a sales data processing system that is used in retail stores that sell packed products produced by cutting and packaging (packing) fresh food such as purchased beef blocks and registering the products of the packed products.
[0002]
[Prior art]
In recent years, fresh food materials purchased for use in the production of packed products in retail stores (hereinafter referred to as the “original”) are, for example, beef blocks (original) in ranches where mad cow disease has occurred, or Some of them have been purchased from wholesale companies that have become a social problem due to label misrepresentation. When such a situation occurs, especially in retail stores where credit is the top priority, pack products produced from these bases are not sold by raising them from the storefront, and only products that can be reassured to customers are sold. Impressive and secure stable sales.
[0003]
For example, pack products produced from beef blocks are distinguished by product types such as “beef (for sukiyaki)” and “beef (for curry)”, and a product code indicating this product type is attached to the produced pack product. . Similarly, pack products produced from pork blocks are also distinguished by product types such as “pork (square cut)” and “pork (rose)”, and the corresponding product codes are pasted on the produced pack products. When a specific original, for example, a packed product of beef is pulled up from a store, it is determined whether the original is beef or pork based on a product code attached to the packed product, and only the packed product of beef is pulled up.
[0004]
[Problems to be solved by the invention]
However, large food retailers may purchase the same type of raw material (for example, beef blocks) from multiple wholesalers and production areas, and each product is a product type called a product code ( For example, in the method of pasting the product code on the packed product produced by discriminating between “beef (for sukiyaki)” and “pork (square cutting)”, it is possible to identify the original supplier for each packed product. There was a problem that it was not possible to determine whether or not the sale of each packed product should be prohibited.
[0005]
The present invention has been made in consideration of such circumstances, and the purpose thereof is a fresh food material (raw material) of the same type (for example, beef) for product production and different histories (suppliers and production areas). The sales data processing system that can distinguish the history of the material of each product individually even if the product has been purchased, etc., and can prohibit the sale of only the products that use the material of the problematic history There is.
[0006]
[Means for Solving the Problems]
In order to solve the above-mentioned problem, the sales data processing system according to claim 1 includes: an original file that sets and stores original data including original identification information and history information for each purchased original; A pricing unit that records pack identification information capable of individually identifying the product on a price label of the product at the time of production pricing of the product cut and packaged from A production file that sets and stores production data including the pack identification information of the product and the original product identification information used for the production of the product, input means for inputting specific history information, and a pack from the price label The identification information is read, and if the product does not include the input history, product registration is performed based on the production data, and if the history is included, the product registration is not performed and the fact is notified. It is characterized by comprising a Kkuauto means.
[0007]
In the sales data processing system according to claim 2, when a sales prohibition flag is provided in the production data and history information is input, the original identification information of the original including the history is detected from the original file. The production data including the detected substance identification information is detected from the production file, and the sales prohibition flag is set.
[0008]
In the sales data processing system according to claim 3, when the checkout unit reads the pack identification information, the checkout unit reads the corresponding original data based on the original identification information in the corresponding production data, It is determined whether or not a product includes the input history.
[0009]
5. The sales data processing system according to claim 4, wherein a sales completed flag that is set when the product registration is made is provided in the production data, and when the history information is input, the corresponding body identification information is detected. The unsold production data including the detected original substance identification information is detected and output as a list.
[0010]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, an embodiment of the present invention will be described with reference to the drawings.
FIG. 1 is a layout diagram of a retail store that sells packed products such as fresh food, and shows an example of a retail store in which a sales data processing system according to an embodiment of the present invention is installed. In the retail store, pricing machines such as a weighing / packaging / price-making machine AW (label printer), a weighing label printer DPS, and a flat-rate label printer DP are installed in the backroom. Product shelves are arranged at the sales floor, and a POS register PR is set up at the checkout area. In addition, the handy terminal HT is used by the store clerk at the sales floor. A store controller SC is installed in the office.
[0011]
Packed products are produced by cutting and packaging (packing) fresh food materials (raw materials) such as beef blocks in the backroom. A price label created by any of the above pricing machines (label printer AW, DPS, or DP) is attached to the produced pack product. The priced packed product is displayed on the product shelf and sold.
[0012]
FIG. 2 is a block diagram showing the configuration of the sales data processing system according to this embodiment. The backroom LAN (N1) is connected to a weighing / packaging / pricing machine AW, a weighing label printer DPS, a fixed amount label printer DP, and a file server FS for holding various data files. This constitutes a weighing pricing system. The file server FS is provided with a transceiver TR, and data can be exchanged between the file server FS and the handy terminal HT carried by the store clerk via the transceiver TR.
[0013]
A POS register PR and a store controller SC are connected to the in-store LAN (N2). The in-room LAN (N1) and the in-store LAN (N2) are connected to each other. This constitutes a POS system. In addition, data can be exchanged between both LANs.
[0014]
Further, a storage device (for example, RAM) (not shown) provided in the file server FS stores a pricing process PLU file (product file) 101 having the configuration shown in FIG. 3 and a production file 102 having the configuration shown in FIG. Has been. As shown in FIG. 3, the PLU file 101 records pricing data such as the product name, the unit price, the tare weight, the effective days indicating the best-before period, etc. for each product number. The PLU file 101 is used by the weighing / packaging / pricing machine AW, the weighing label printer DPS, the label printer DP, the store controller SC, the POS register PR, and the handy terminal HT as necessary.
[0015]
As shown in FIG. 4, the production file 102 includes, for each pack ID number (pack identification information), a product number, price, content, cost, processing date and time, expiration date, block ID number (element identification information), and Production data such as flags are recorded. The pack ID number is a number unique to each pack product, and the pack product can be individually identified by this pack ID number. The block ID number is a number unique to each original material such as a beef block, and the original material can be individually identified by this block ID number. The flag indicates the sales status of the corresponding packed product, and “0” is set at the time of pricing to indicate that the product is being sold. After that, this flag is banned to “1” if the product is sold at the regular price, “2” if the product is sold at a discounted price, and “3” if it is disposed of. If it is, it is rewritten to “4”. The production file 102 is downloaded to the store controller SC or vice versa.
[0016]
In addition, a raw material block file (hereinafter referred to as a raw material file) is stored in a storage device (for example, a RAM) (not shown) provided in the store controller SC. FIG. 5 shows a configuration example of the base file 103. The example of FIG. 5 is for a beef block. As shown in FIG. 5, in the original file 103, raw material block data such as the original name, history information, purchased weight, processed weight, sales weight, etc. (hereinafter referred to as original data) are stored for each block ID number. Is recorded. The history information includes information such as suppliers (wholesale companies, agricultural organizations, etc.), producers, ranches (production areas), ear tags (cow individual numbers), and the like. Purchased weight, processed weight and sold weight are information for analysis.
[0017]
Next, FIG. 6 shows an electrical configuration of the weighing label printer DPS as a configuration example of a pricer (value unit). This weighing label printer DPS constitutes a pricing processing unit from a CPU 1 for executing a program stored in the ROM 2 and a RAM 3 used for the CPU 1. The weighing label printer DPS includes a display unit 4 for displaying various information, an operation unit 5 provided with input means for inputting a product number and a product file, and a product name on the price label. A printing unit 6 for printing prices, barcodes, etc., a weighing unit 7 for weighing the weight (internal capacity) of a product placed on a weighing pan (not shown), and data externally via a LAN. And a communication unit 8 for performing communication. Further, the pricing process PLU file 101 is downloaded from the file server FS and stored in the RAM 3.
[0018]
FIG. 7 shows the structure of the price label created by the weighing label printer DPS. As shown in FIG. 7, the price label displays the product name, processing date, expiration date, unit price, content, and price. Further, a bar code indicating the pack ID number is displayed on the price label, and the corresponding pack ID number is displayed by a number (readable character) under the bar code. FIG. 8 shows the structure of the pack ID number. As shown in FIG. 8, the pack ID number is an in-store code and a first two-digit flag “FF” indicating that it is a pack ID barcode, and a two-digit manufacturing date (processing date) code for specifying the processing date. “DD”, a four-digit hour / minute code “HHHH” for specifying the time of manufacture (processing), a serial number “NNNN” consisting of four digits, and whether or not the reading of each digit is correct It consists of a one-digit check digit “C / D”.
[0019]
Note that the serial number is not assigned the same pack ID number in each pricing machine when performing pricing work using a plurality of pricing machines (label printer AW or DPS or DP) simultaneously. For example, if the first digit of the serial number is a number (machine number) for identifying a pricer, the same pack ID number is not given. Further, the file server FS may manage the assignment of sequential numbers.
[0020]
FIG. 9 is an electrical configuration diagram of the POS register PR (checkout means). The POS register PR constitutes a product registration processing unit from a CPU 21 that executes a program stored in the ROM 22 and a RAM 23 that is used by the CPU 21. The POS register PR also includes an operation unit 25 provided with a display unit 24 for displaying various types of information, and input means for inputting product registration completion or inputting numeric data such as the amount of money deposited from a customer at the time of payment. A clock unit 26 that measures the month, day, hour, and minute, a printing unit 27 that prints receipts of registered and settled products, and a scanner unit that reads barcodes from price labels attached to the products 28 and a communication unit 29 that performs data communication with the outside via a LAN.
[0021]
The POS register PR downloads product data from the PLU file 101 for registration processing held by the store controller SC, and conversely uploads sales data to the store controller SC. Also, the production data of the production file 102 is read out and received, and conversely, data for changing the flag in the production data is transmitted to the store controller SC.
[0022]
Next, the operation of the sales data processing system shown in FIG. 2 will be described. First, an outline of the overall work flow related to the goods from the purchase of the original product to the check-out of the packed product in the retail store of FIG. 1 will be described with reference to the flowchart of FIG. First, when the raw material is purchased in step S1, production and pricing of packed goods are performed in step S2. Packed products with price labels attached by this pricing are displayed on a product shelf and sold.
[0023]
Next, in step S3, when the store manager or department manager obtains history information (for example, mad cow disease from "XX Farm") that has become a problem due to reports or news from related organizations, the store controller SC From the specific history input screen, enter “Ox Ranch”. In step S4, the store controller SC refers to the base file 103 and the production file 102, and uses a general-purpose pull-up product list including items such as product name, pack ID number, and price for the packed product corresponding to the input history. Printing is output by a printer (not shown in FIG. 2).
[0024]
In the process of creating the raised product list, the store controller SC detects a block ID number corresponding to the history information input from the base file 103. The detected block ID number and the flag is neither “1 (normal price sold)” nor “2 (discounted price sold)”, that is, unsold production data is detected from the production file 102. To include in the raised product list.
[0025]
Next, in step S5, the store clerk checks the pack ID number (corresponding portion of the readable character) of the price label of the packed product displayed while viewing the raised product list. And when it corresponds with the pack ID number described in the raised product list, the packaged product is lifted from the storefront.
[0026]
Next, in step S6, the packed product that is not prohibited from sale can be purchased by the customer, and is checked out (registered product) by the POS register PR at the time of purchase. The sale-prohibited products that have been leaked and left in the pulling operation in step S5 are inspected at the time of checkout.
[0027]
Hereinafter, processing performed by the sales data processing system in steps S1 to S3 and S6 of FIG. 10 will be described in detail.
FIG. 11 shows processing at the time of purchase in step S1 of FIG. In FIG. 11, in step S11, when a raw material (raw material) is received, the store clerk operates the weighing label printer DPS to select a new raw data input screen. As a result, the weighing label printer DPS inquires of the store controller SC about a new block ID number. In response to this inquiry, the store controller SC issues a new block ID number and returns it to the weighing label printer DPS.
[0028]
Next, in step S12, the clerk selects each item such as the supplier of the original data, the producer, the ranch name, and the ear number from the arrival information or information obtained using the Internet or the like based on the arrival information. Is input to the weighing label printer DPS. As a result, the weighing label printer DPS transfers the original data including the input data and the new block ID number to the store controller SC, and the store controller SC records the received original data in the original file 103.
[0029]
Next, in step S13, the measurement label printer DPS issues a predetermined number of original labels on which the original name, block ID number, and the like are printed. The store clerk affixes this original label to the original received.
[0030]
FIG. 12 shows the production and pricing process in step S2 of FIG. In FIG. 12, in step S20, the store clerk inputs the block ID number described in the original label of the original to the weighing label printer DSP. Next, in step S21, the store clerk inputs the product number of the packed product. Thus, in step S22, the weighing label printer DSP reads product data such as the product name, unit price, and tare weight related to the product number from its own PLU file 101.
[0031]
Next, in step S23, when the packed product produced by the store clerk is placed on the weighing pan, the weighing label printer DSP measures the weight of the product. In step S24, the weighing label printer DSP calculates the price by multiplying the net weight obtained by subtracting the tare weight from the weight of the measurement result and the unit price, and issues a new pack ID number. In step S25, the configuration shown in FIG. The price label is printed and issued. The expiration date is obtained by adding the effective date to the processing date.
[0032]
Next, in step S26, the weighing label printer DSP registers new production data in the production file 102 of the file server FS. The new production data includes the block ID number and product number input in steps S20 and S21, the price label data (pack ID number etc.) issued in step S25, and the flag “0”.
[0033]
Next, in step S27, the store clerk determines whether or not there is a product with the same block ID number and the same product number that is still priced. As a result, when the packed product to be priced still remains, the processing from step S23 onward is repeated. On the other hand, if it is determined that all the pricing of the packed product having the same block ID number and the same product number has been completed, the priced product is displayed.
[0034]
FIG. 13 shows processing at the time of inputting a specific history in step S3 of FIG. Here, a process for inspecting whether or not there is an original including the input specific history in the purchased original is described. In FIG. 13, in step S31, when the store clerk operates the store controller SC to display the specific history input screen and inputs the specific history data, the store controller SC holds the specific history data in a predetermined storage area.
[0035]
Next, in step S <b> 32, the store controller SC compares each data of the first original data of the original data file 103 with the input specific history data. In step S33, the store controller SC determines whether there is the same data as the specific history data. If there is, the process proceeds to step S34, and if not, the process proceeds to step S35.
[0036]
In step S34, the store controller SC detects the production data including the block ID number that matches the block ID number in the original data since the original compared with this time includes the specific history. The store controller SC sets all detected production data flags to “4” to prohibit sales, and updates the production file 102.
[0037]
In step S35, the store controller SC returns to step S32 if there is a next original in the original file 103, and ends the process if there is not. In this way, the store controller SC checks whether or not all the originals in the original file 103 include the specific history, and the purchased originals including the specific history are prohibited from being sold.
[0038]
FIG. 14 shows processing at the time of check-out in step S6 of FIG. In FIG. 14, in step S61, the store clerk registers a product in the POS register PR for the purchase desired product brought from the product shelf by the customer. The flow of this product registration process is shown in FIG. In FIG. 15, in step S611, the store clerk causes the POS register PR to read the barcode of the price label (see FIG. 7) of the packed product. As a result, the POS register PR reads the barcode of the price label.
[0039]
In step S612, the POS register PR transmits the pack ID number in the barcode read data to the store controller SC, and reads and receives the corresponding production data in the production file 102. Next, in step 613, the POS register PR determines whether or not the flag in the received production data is “4”, that is, whether sales are prohibited. If the sales are prohibited, a message indicating that sales are prohibited is displayed in step 614. The store clerk is warned and the product registration process of FIG. 15 is terminated. In addition, you may make it alert | report to the effect of sale prohibition by a voice message or a warning sound.
[0040]
The sales clerk explains to the customer that the sale is prohibited and displays the prohibited product. Discard the merchandise you have deposited. At the time of disposal, the store clerk causes the POS register PR to read the barcode of the price label of the packed product to be discarded by the POS register PR, and performs an operation for discarding. As a result, the POS register PR transmits the pack ID number and the flag “3 (discard)” in the barcode read data to the store controller SC, and sets the flag of the corresponding production data in the production file 102 to “3”, that is, discard. To update.
[0041]
On the other hand, if the sale is not prohibited, the process proceeds to step S615, and the POS register PR adds the price in the received production data to the total purchase amount of the customer currently trading. Next, in step S616, the POS register PR transmits the pack ID number and the flag “1 (normal price sold)” or “2 (discount price sold)” in the barcode read data to the store controller SC for production. The flag of the corresponding production data in the file 102 is updated to “1” or “2”, that is, sold. The flag “1” or “2” is selected as the flag “2 (discount price sold)” when the clerk presses the discount key.
[0042]
In step S617, the POS register PR causes the store controller SC to update the sales weight of the corresponding original data in the original file 103, and ends the product registration process of FIG. The store controller SC calculates the sales weight by adding the content of the corresponding production data in the production file 102 and updates it.
[0043]
Next, the POS register PR repeats the product registration process of FIG. 15 until registration of all the products is completed (step 62). Next, in step 63, the total price of the registered product is displayed, and in step 64, the settlement process is performed.
[0044]
In the above-described embodiment, in the process at the time of inputting the specific history in FIG. 13, the presence or absence of the original body including the specific history is inspected, and the flag in the original body data including the specific history is prohibited in advance. However, the original product of the registered product may be inspected when the product is registered as shown in FIG. FIG. 16 shows the flow of processing of the store controller SC in this case. The process of FIG. 16 is a part of the specific history input process of the store controller SC, and relates to a process executed when an original inspection request for a product to be registered is received from the POS register PR.
[0045]
The store controller SC holds the input specific history data in a predetermined storage area, similarly to step S31 of FIG. In FIG. 16, when the store controller SC receives the pack ID number for the original inspection from the POS register PR (step S71), the store controller SC starts the following processing (steps S72 to S76).
[0046]
First, in step S 72, the store controller SC reads production data having the same pack ID number as the received pack ID number from the production file 102. Next, in step S73, the original data having the same block ID number as the block ID number in the read production data is read out.
[0047]
Next, in step S74, the store controller SC determines whether or not the read original data includes the same data as the specific history data held in the predetermined storage area. If there is the same data as the specific history data, the process proceeds to step S75, and the store controller SC prohibits the instruction to prohibit the sale because the original of the product requested for the original inspection includes the specific history. A signal is transmitted to the POS register PR.
[0048]
On the other hand, if there is no data that is the same as the specific history data, the process proceeds to step S76, and the store controller SC registers the read production data for the product because the original of the product requested for the original inspection does not include the specific history. For transmission to the POS register PR.
[0049]
In the above-described embodiment, the beef has been described as an example. However, the present invention is not limited to livestock such as beef and pork but can be applied to any fresh food such as fish and vegetables. Therefore, it is better to include the name of the fishing port for fish meat, whether it is aquaculture, whether it is frozen, etc. in the history information of the original file. Further, it is better to include the name of the farm, whether it is grown in a house, the type of fertilizer, the presence or absence of genetic manipulation, etc. for vegetables.
[0050]
When detecting the original including the input specific history, not only the determination of whether or not the specific history data exists in the original data in the original file, but also, for example, an ear mark number or the like It is also possible to acquire more detailed information on the original based on the original data and perform a detailed history inspection of the original. For example, by accessing another database via the Internet or the like, detailed history data of the original is acquired, and it is determined whether or not this detailed data includes specific history data. Since this method takes time to process, it is preferable to perform the processing when inputting a specific history.
[0051]
The embodiment of the present invention has been described in detail with reference to the drawings. However, the specific configuration is not limited to this embodiment, and includes design changes and the like within a scope not departing from the gist of the present invention.
[0052]
【The invention's effect】
As described above, according to the present invention, since the history of each active ingredient is managed by the original file, and further, the active substance used for each product is managed by the production file, it is read from the price label of the product. Based on the pack identification information, the original product can be identified from the production file, and the history of the original can be identified from the original file. As a result, even if a fresh food material (original) of the same type (for example, beef) is used for product production and a different history (supplier, production area, etc.) is purchased, each product is individually made of that material. Can be distinguished. As a result, if it turns out that the material of the history which becomes a problem was purchased, only the goods which used the material can be prohibited from selling surely, and the excellent effect that the credit of a store can be improved efficiently. Is obtained.
[0053]
Further, according to the invention described in claim 2, since the sales prohibition flag can be set before the checkout for the production data of the commodity using the material in question, the search for the sales prohibition is unnecessary in the checkout process. The processing can be simplified.
[0054]
According to the invention described in claim 3, since it is determined whether or not the product uses the material in question at the time of checkout, a memory such as a flag for storing the result of the determination is unnecessary. can do.
[0055]
According to the invention described in claim 4, it is possible to display and output, for example, a list of products that have been produced and have not yet been sold out of products that use the material in question. It can be raised from the store.
[Brief description of the drawings]
FIG. 1 is a diagram showing an in-store arrangement example of a retail store in which a sales data processing system according to an embodiment of the present invention is installed.
FIG. 2 is a block diagram showing a configuration of a sales data processing system according to the embodiment.
FIG. 3 is a diagram illustrating a configuration example of a PLU file (product file) 101. FIG.
FIG. 4 is a diagram showing a configuration example of a production file 102.
FIG. 5 is a diagram showing a configuration example of an original file 103. FIG.
FIG. 6 is a block diagram showing an electrical configuration of a weighing label printer DPS (value attaching means).
FIG. 7 is a diagram illustrating a configuration example of a price label.
FIG. 8 is a diagram illustrating a configuration example of pack ID numbers for bar code display.
FIG. 9 is a block diagram showing an electrical configuration of a POS register PR (checkout means).
FIG. 10 is a flowchart showing an outline of the overall work flow related to an object from purchase of an original product to check-out of a packed product according to the present invention.
11 is a flowchart for explaining processing of the sales data processing system of FIG. 2 at the time of purchase shown in FIG.
12 is a flowchart for explaining processing of the sales data processing system of FIG. 2 at the time of production and pricing shown in FIG.
13 is a flowchart for explaining the processing of the sales data processing system of FIG. 2 when inputting a specific history shown in FIG.
14 is a flowchart for explaining processing of the sales data processing system of FIG. 2 at the time of check-out shown in FIG.
15 is a flowchart showing the flow of the product registration process shown in FIG.
16 is a flowchart for explaining the processing of the sales data processing system of FIG. 2 in the case where the original of the registered product is inspected at the time of product registration.
[Explanation of symbols]
DESCRIPTION OF SYMBOLS 1,21 ... CPU, 22,22 ... ROM, 3,23 ... RAM, 4,24 ... Display part, 5,25 ... Operation part, 6,27 ... Printing part, 7 ... Measuring part, 8,29 ... Communication part , 26 ... Clock part, 28 ... Scanner part, 101 ... PLU file, 102 ... Production file, 103 ... Original file, AW ... Weighing / packaging / price machine, DP ... Flat-rate label printer, DPS ... Weighing label printer, FS ... File server, TR ... Transceiver, HT ... Handy terminal, N1 ... Weighing pricing system (LAN in backroom), N2 ... POS system (LAN in store), PR ... POS register, SC ... Store controller

Claims (4)

An original file for setting and storing original data including original identification information and history information for each purchased original,
A pricing unit that records pack identification information capable of individually identifying the product on a price label of the product at the time of production pricing of the product cut and packaged from the original,
A production file that sets and stores production data including at least the pack identification information of the product and the original product identification information used for production of the product at the time of the pricing;
An input means for inputting specific history information;
The pack identification information is read from the price label, and if the product does not include the input history, the product registration is performed based on the production data, and if the history is included, the product registration is not performed and the fact is notified. Checkout means to
A sales data processing system characterized by comprising: A sales prohibition flag is set in the production data
When history information is input, the original identification information of the original including the history is detected from the original file, and the production data including the detected original identification information is detected from the production file and the sales prohibition flag is detected. The sales data processing system according to claim 1, wherein the sales data processing system is set. The checkout means includes
When the pack identification information is read, the corresponding original data is read based on the original identification information in the corresponding production data, and it is determined whether or not the product includes the input history. The sales data processing system according to claim 1. A sales completed flag that is set when the product registration is made is provided in the production data,
4. When the history information is input, the corresponding original identification information is detected, unsold production data including the detected original identification information is detected and output as a list. The sales data processing system according to any one of the items.

Images