JP3975743B2 - Product pricing and registration system - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a pricing system for measuring goods such as meat and a registration system for goods priced by this pricing system.
[0002]
[Prior art]
In recent years, due to the impact of “mad cow disease” becoming a social problem, customers want to know the production route of purchased fresh products in order to confirm the safety of fresh products such as meat and fish they purchase. The demand is growing.
On the other hand, the store side wants to secure fixed customers by appealing to such customers that their products have a clear production route and are safe.
[0003]
[Problems to be solved by the invention]
However, no system has been developed to meet such demands of customers and stores.
The present invention has been made in view of the above circumstances, and an object of the present invention is to provide a product pricing and registration system capable of easily confirming the production route information of a purchased product if the customer desires. And
[0004]
[Means for Solving the Problems]
  In order to achieve the above-mentioned object, the invention according to claim 1, when pricing a weighing product, an identification number (pack ID) for identifying the product for each item is printed on the price label with a barcode.Identification number(Pack ID)A pricing device that stores production data including an identification number (original ID) that identifies a raw material block (original) of the product corresponding toProduction route storage means for storing production route information of the original corresponding to the original ID;SaidIdentification number(Pack ID)When registering a productThe production route information stored in association with the identification number (original ID) corresponding to the identification number (pack ID) read in is printed on the receipt.And a registration device.
  According to the first aspect of the invention, since the production route information of the purchased product is printed on the receipt, the customer can confirm the production route information of the purchased product by the receipt, so that a sense of security can be obtained.
[0011]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
FIG. 1 is a layout diagram of a retail store that sells products such as fresh food, and shows an example of a retail store to which a pricing and registration system for fresh products according to an embodiment of the present invention is applied.
[0012]
The back room in the upper right part of Fig. 1 is an area for processing fresh foods and pricing, especially for weighing, packaging and pricing machines AW (label printers), weighing label printers DPS and flat-rate labels. A pricing machine such as a printer DP is arranged, and a price label issued by these pricing machines is pasted at the time of production / processing of goods. Details of the label and the label printer will be described later.
[0013]
The sales floor in the lower part of FIG. 1 is an area where merchandise shelves are arranged, and a POS register PR equipped with a bar code reader is provided in the checkout hall, whereby the customer pays for the merchandise to be purchased.
In addition, an information output terminal MT for displaying fresh food production route information and the like is provided near the entrance. Details of the information output terminal MT will be described later.
[0014]
The office in the upper left in FIG. 1 is an area where business processes such as data aggregation and accounting processes, and decision-making regarding the amount of purchase, production and processing, etc. are made based on this data. It has been.
[0015]
FIG. 2 is a block diagram showing a system configuration for explaining the flow of data processing in the retail store. The backroom LAN (N1) is connected to a file server FS for holding various data files in addition to the above-described weighing / packaging / price-making machine AW, weighing label printer DPS, and flat-rate label printer DP. A pricing system is configured. Further, 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. .
[0016]
As will be described later, the handy terminal HT has a function of printing and issuing a bar code label. 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 the local area LAN (N3), and data can be exchanged between these two LANs.
Further, the information output terminal MT described above is connected to the local area LAN (N3) so that various data stored in the file server FS and the store controller SC can be displayed and printed as necessary. It has become.
[0017]
In addition, a web server WS connected to the Internet is connected to the local area LAN (N3), and various data are uploaded to the external device as needed via the Internet, and necessary data is downloaded from the external device as appropriate. It is the structure which can do.
[0018]
Next, the weighing label printer DPS will be described with reference to FIG. FIG. 3 is an electrical configuration diagram of the weighing label printer DPS. In the figure, reference numeral 1 denotes a CPU (central processing unit) that controls the entire operation of the label printer DPS, and is connected to other components as shown in the figure. Reference numeral 2 denotes a ROM that stores a program to be executed by the CPU 1, and stores a program that defines the processing of the CPU 1 in the operation description to be described later. Reference numeral 3 denotes a RAM (Random Access Memory) used in the arithmetic processing of the CPU 1, and a PLU file (product file) for pricing processing described later is transmitted from the file server FS and stored therein.
[0019]
Reference numeral 4 denotes a display unit that displays predetermined information in accordance with a display instruction from the CPU 1. Reference numeral 5 denotes an operation unit provided with input means for inputting a product number of a product, setting input of a product file, and the like, and supplies input data to the CPU 1. Reference numeral 6 denotes a printing unit that prints the product name, price, barcode, and the like on the label in accordance with a printing instruction from the CPU 1. Reference numeral 7 denotes a weighing unit that measures the weight (internal capacity) of a product placed on a weighing pan (not shown), and supplies a measured value to the CPU 1. Reference numeral 8 denotes a communication unit that exchanges data with the outside through communication via a LAN. Reference numeral 9 indicates the month. Day. Time. It is a clock unit that counts and minutes and supplies it to the CPU 1.
[0020]
Next, the POS register PR will be described with reference to FIG.
FIG. 4 is an electrical configuration diagram of the POS register PR. In the figure, reference numeral 21 denotes a CPU that controls the entire operation of the POS register PR, and is connected to other components as shown in the figure. Reference numeral 22 denotes a ROM that stores a program to be executed by the CPU 21, and stores a program that defines the processing of the CPU 21 in the operation description to be described later. Reference numeral 23 denotes a RAM used in the arithmetic processing of the CPU 1.
[0021]
Reference numeral 24 denotes a display unit that displays predetermined information in accordance with a display instruction from the CPU 1. Reference numeral 25 denotes an operation unit provided with input means for inputting the completion of product registration or inputting numeric data such as the amount of money deposited from the customer at the time of payment, and supplies the input data to the CPU 21. Reference numeral 26 denotes a clock unit that measures the month, date, hour, and minute and supplies them to the CPU 21. Reference numeral 27 denotes a printing unit that prints a receipt or the like of a product registered and settled in accordance with a printing instruction from the CPU 21. Reference numeral 28 denotes a scanner unit that reads a barcode attached to a product and supplies the data to the CPU 21.
[0022]
Reference numeral 29 denotes a communication unit that exchanges data with the outside through communication via a LAN. For example, the communication unit 29 downloads the product data from a PLU file (product file) for registration processing held by the store controller SC, and conversely uploads sales data to the store controller SC.
[0023]
Next, the information output terminal MT will be described with reference to FIG. FIG. 5 is an electrical configuration diagram of the information output terminal MT. The components are almost the same as the POS register PR. That is, in the figure, reference numeral 31 denotes a CPU that controls the overall operation of the information output terminal MT, and is connected to other components as shown. Reference numeral 32 denotes a ROM in which a program executed by the CPU 31 is stored, and reference numeral 33 denotes a RAM used in the arithmetic processing of the CPU 31.
[0024]
Reference numeral 34 denotes a display unit that displays predetermined information in accordance with a display instruction from the CPU 31. Reference numeral 35 denotes an operation unit provided with an input means for inputting numeric data such as a pack ID number and a base material ID number, which will be described later, and supplies the input data to the CPU 31.
Reference numeral 36 denotes a clock unit that measures the date, date and time, minute, and second and supplies the time to the CPU 31. Reference numeral 37 denotes a printing unit that prints production route information, which will be described later, in accordance with a command from the CPU 31.
[0025]
Reference numeral 38 denotes a scanner unit that reads a barcode added to a product and supplies the data to the CPU 31. Reference numeral 39 denotes a communication unit that exchanges data with the outside through communication via a LAN. The communication unit 39 is used, for example, when calling and displaying various files stored in the file server FS and the store controller SC.
[0026]
A storage device (for example, RAM) (not shown) included in the file server FS includes a PLU file for pricing processing described above, a production result file (aggregation file and production log file) described later, and a raw material block file described later. A production route information file is stored.
FIG. 6 shows the data structure of the PLU file for pricing processing. As shown in this figure, the PLU file holds pricing data for effective days indicating the product name, unit price, tare weight, shelf life, classification, etc. for each product number.
[0027]
Here, the unit price is the price per product in the case of a fixed amount product, and the price per 100 grams of net weight in the case of a metered product. Further, the tare weight is a weight of a package such as a tray in the weighing product. This PLU file is referred to by the weighing / packaging / pricing machine AW, the weighing label printer DPS, the label printer DP, the store controller SC, the POS register PR, or the handy terminal HT as necessary, or used after being downloaded. The
Details of the production record file will be described later.
[0028]
Next, the operation of the product pricing and registration system according to an embodiment of the present invention will be described.
The processing performed by this system is as follows:
(1) Product pricing process
(2) Discount processing for part-off products
(3) Product registration / checkout / sales data aggregation processing
(4) Production and sales data processing output processing
(5) Production route information output processing
And divided. Hereinafter, each process will be described.
[0029]
(1) Product pricing process
This process produces and processes products (for example, “for beef sukiyaki”, “for beef steak”) from raw material blocks (for example, “beef block”) and issues price labels (barcode labels) for the processed products. The price labeling process for attaching the price label to the product and the totaling process for totalizing the production process data (label issuing data).
The price label is issued by the weighing / packaging / pricing machine AW or the weighing label printer DPS for fixed-price products and weighing products whose contents differ for each item, and for fixed-price products by the flat label printer DP. Do.
[0030]
FIG. 7 is a flowchart showing an outline of the procedure of the pricing process and the aggregation process. Hereinafter, a case where the pricing process is performed using the weighing label printer DPS will be described.
First, the person in charge of pricing identifies a raw material block (raw material) of a product to be priced from now on, and inputs and sets a raw material block number (hereinafter referred to as a block ID number) which is a specified number (FIG. 6). Step S50).
[0031]
The block ID number (original ID number) is an identification number given by the store as appropriate to identify the raw material block. That is, when a raw material block is received in the store, (1) purchase date and time, (2) raw material block product name, (3) raw material block code, and (4) individual identification code for each block ID number using the weighing label printer DPS , (5) Purchase price, (6) Purchase weight, (7) Purchase unit price, (8) Supplier code, (9) Person in charge code, etc. are entered.
Among these, the purchase date and time of (1) is automatically set by the clock data of the clock unit 9 of the weighing label printer DPS, and the purchase weight of (6) is automatically set by the weighing unit. The purchase unit price of (7) is calculated from the purchase amount and the purchase weight.
[0032]
The individual identification code (4) is a code for identifying the individual that produced the raw material block. For example, when the raw material block is beef, one identification number (beef) is assigned to each beef. Number). This identification number (cow number) is entered in the raw material block shipping slip at the meat processing plant and sent to the store together with the raw material block.
After inputting the data, a block ID label on which a block ID number, a block product name, a purchase date and time, etc. are printed is printed and issued. The issued block ID label is attached to the raw material block, and is used for an operator to recognize the raw material block when producing a product from the raw material block.
[0033]
The data input for each block ID number is transmitted to the file server FS and stored in a raw material block file (see FIG. 8) of the file server FS.
At this time, an area (inventory field) for storing inventory data is added for each block ID number, and the inventory information is updated in real time for each block ID number by subtracting the processing weight from the purchased weight. Details of the inventory data will be described later.
[0034]
Further, the block ID number is a raw material handwritten or printed on a bat (storage tray) or cart (moving cart) for transporting the product when the person in charge of the product produces the product from the raw material block (original). By attaching a vote, the person in charge of pricing is notified.
[0035]
The person in charge of pricing confirms the block ID number of the raw material slip attached to the bat or the like of the product to be priced, and inputs the block ID number from the operation unit or the like.
Next, the person in charge of pricing inputs the product number of the product (step S51). As a result, the CPU 1 provided in the weighing label printer DSP reads product data such as the product name, unit price, and tare weight regarding the product number from the PLU file stored in the RAM 3 (step S52). In this embodiment, the PLU file stored in the RAM 3 is used. However, the PLU file stored in the file server FS may be used.
[0036]
Next, when the person in charge of pricing places the product to be produced and processed on the weighing pan, the weighing label printer DSP measures the weight of the product (step S53), and the net value obtained by subtracting the tare weight from the measured weight. The price is calculated by multiplying the weight by the unit price (step S54). And, including data such as processing date, processing time, serial number, etc., a barcode (pack ID barcode) and other information (for example, product name, price, content, The expiration date, unit price, etc.) are printed and a price label is issued (step S55). The expiration date is obtained by adding the effective date to the processing date.
[0037]
As a result, a bar code consisting of information on the processing date, processing time, and serial number as shown in FIG. 9 is displayed in the lower left row, and the product name, processing date, and taste are displayed at other positions. A price label on which predetermined characters such as an expiration date, a unit price, an internal capacity, and a price are displayed is issued. This price label is affixed to products weighed automatically or manually.
[0038]
Subsequently, when the pricing process is completed by performing the series of processes described above, the price label data that has been issued is recorded in the production result file of the file server FS (step S56). Details of the production result file will be described later.
Subsequently, it is determined whether or not there are products that have the same product number and are still priced (step S57). As a result, if there is still a product to be priced, the processing from step S53 is repeated.
[0039]
On the other hand, if it is determined that the pricing of all products having the same product number has been completed, the pricing process for this product is terminated, and the processing in step S50 and subsequent steps is repeated for other products.
Next, the configuration of the barcode described above will be described with reference to FIG. As shown in this figure, the pack ID barcode in this embodiment is composed of a 13-digit JAN one-level barcode, a flag of the first two digits (1), (2), and a third digit (3). Serial number of the machine number, fourth digit (4), fifth digit (5) to eighth digit (8), ninth digit (9) to eighth digit (12) selling price (price), 13 digits It consists of a check digit for the eye (13).
[0040]
Generally, the flag “FF” can set data from 01 to 99, but in the case of a pack ID barcode, a country code used in a general PLU barcode, for example, “49” or normal Other than the flag used in the NON / PLU bar code. That is, data other than the flag already used in the store is used.
[0041]
The flag data indicates that the barcode is a pack ID barcode, and indicates a product classification. For example, “03” to “07” are used as pack ID barcode flags, the flag “03” is “meat”, the flag “04” is “fresh fish”, the flag “05” is “fruits and vegetables”, the flag It is determined that “06” indicates “garden” and the flag “07” indicates “other”. This product classification can be set to “beef”, “pork”, “chicken”, “other meat”, etc. by increasing the types of flags to be used.
The product classification is preset for each product number in the product file for pricing (see FIG. 6).
[0042]
The machine number “M” indicates the device number of the device that has printed and issued the barcode label of the pack ID number, “1” to “8” indicate the pricing device, and “9” indicates the handy terminal HT.
The day of the week “W” indicates the day of the week when the barcode label is printed and issued, “0” indicates “Sunday”, “1” indicates “Monday”, and “6” indicates “Saturday”.
The serial number “CCCC” is a number from “0001” to “9999”. The devices (valued devices and handy terminals HT) that issued each barcode label generate and manage serial numbers.
[0043]
The selling price “PPPP” is a value from “0” to “9999”, and indicates the selling price (price) of the product. When the selling price “PPPP” is “0”, it means that the price of the product is 5 digits or more and cannot be displayed with 4 digits. Normally, it is considered extremely rare if the price of a fresh product is 5 digits or more, but in special cases such as a special sale at the end of the year and the beginning of the year, such an expensive product may be available, so the price is It is possible to process even more than 5 digits.
The check digit “C / D” is data for checking whether or not the bar code is normally read.
[0044]
Among the above barcodes, the 6-digit numerical value of the third to eighth digits functions as an identification number (pack ID number) for identifying each weighing product.
With such a configuration, since one identification number (pack ID number) is given as a barcode to one weighing product, it is possible to identify each weighing product for each product. Each bar code also includes selling price data.
[0045]
Next, a production result file (aggregation process) that is aggregated in the aggregation process will be described. FIG. 11 is a diagram showing a data structure of a production record file. The production result file includes a first file (total file) in which the cumulative number, cumulative weight, and cumulative amount are associated with each product number shown in FIG. 11A, and each pack shown in FIG. 11B. Each ID number includes a second file (production log file) in which individual production data such as a product number, product name, content, price, processing date / time, expiration date, block ID number, and flag are associated.
[0046]
The product number stores the number input in step S51 of the pricing process described above, the product name stores the product name of the product number, and the block ID number also uses the pricing process. The block ID number set in step S50 is stored. The flag indicates the sales status of the produced product, and “0” is stored at the time of pricing. This flag is rewritten as “1” when the product is sold at the normal price, “2” when the product is sold at the discount price, and “3” when the product is disposed of. By checking this flag, the subsequent status of the product can be determined.
[0047]
Details will be described later. In addition, the production log file has a sales amount column for storing the actual sales amount for each block ID number. Details of the sales amount column will be described later.
The production result file (total file and production log file) and raw material block file are transmitted to the store controller SC of the POS system via the LAN.
[0048]
(2) Discount processing for part-off products
The produced products are displayed on the sales floor. However, in the case of fresh foods, side dishes, etc., the quality of the products deteriorates with the passage of time after production. For this reason, processing for appropriately discounting products that have passed a certain period of time after production (closed products) and products that are unsold near the closing (closed products) is performed. Such discount processing for part-off products is performed by the following method.
[0049]
(1) The store clerk has the handy terminal HT, goes to the sales floor, and selects a discounted product from the displayed products.
(2) Enter the discount amount or discount price of the product to be discounted from the handy terminal HT, and read the barcode of the product with the scanner.
(3) According to (2) above, the handy terminal HT replaces the sales price data in the read barcode with the discounted price data, prints the barcode label and issues it.
(4) The clerk puts the issued bar code label on the bar code of the price label affixed to the product.
(5) The store clerk affixes a discount POP label, for example, a “50 yen discount” label, etc. to the product.
[0050]
For example, when discounting “50 yen” on a product A with a certain price of 500 yen (the barcode of this product is “031102340500 C / D”, for example), the discount amount “50 yen” is given to the handy terminal HT of the store clerk. When the barcode of the commodity A is read in the input state, the handy terminal HT prints and issues a pack ID barcode of 450 yen, which is an amount obtained by subtracting 50 yen from 500 yen.
[0051]
In this case, the data other than the price (aside from the check digit) is the same barcode (that is, “03110234450 C / D”). The store clerk puts the printed bar code on top of the original bar code and pastes the discounted “50 yen discount” POP label to the customer indicating that this product is 50 yen discount. Affix to Thereby, the discount process of the product A is completed.
[0052]
(3) Product registration / checkout / aggregation processing
Next, product registration / settlement / aggregation processing will be described.
This processing is performed in the POS register PR for the purchase desired product that the customer has taken from the product shelf.
FIG. 12 is a flowchart showing the procedure of product registration / settlement / counting processing. In this figure, first, products are registered based on the barcode data read by the scanner unit 28 of the POS register PR (step S61, details will be described later), and registration is completed until all products are registered (step S62). Repeat the process.
[0053]
Next, the total price of the registered products is displayed (step S63), and the settlement process is performed (step S64).
In the checkout process, the printing unit 27 issues a receipt on which the purchase details of the product and the checkout data are printed and hands it to the customer along with the change. In the present invention, the purchase ID details ( When a product with a pack ID is registered, the original ID number is printed together with the product name, price, etc. of the pack ID product (see FIG. 19A). As will be described later, when the production log data cannot be read at the time of product registration, the pack ID number is printed together with the classification name, price, etc. of the pack ID product in the purchased product details print column (FIG. 19B). )).
[0054]
Next, the detailed procedure of the merchandise registration process in step S61 for weighing priced merchandise according to the present invention will be described with reference to FIGS. FIG. 13 shows product registration processing when the production log of the production result file stored in the store controller SC is read out. FIG. 14 shows the product registration process when the production log data cannot be read because the store controller SC is down. In FIG. 13, first, the barcode added to the product, that is, the pack ID number (identification information) and price of the product is read by the scanner unit 28 of the POS register PR (step S71).
[0055]
Thus, when the pack ID number of the product is acquired, the production data such as the product number / price corresponding to the ID number from the production log file of the production result file stored in the store controller SC via the communication unit (FIG. 10) is read (step S72).
Subsequently, the read-out expiration date data is referred to and it is determined whether or not the expiration date has expired (step S73). This determination is made by comparing with the clock date and time of the POS register PR.
[0056]
If the result of the determination is that it has expired ("YES" in step S73), an alarm is displayed to notify the operator of the POS register PR to that effect (step S74). In addition, a warning sound may be generated along with the display.
[0057]
On the other hand, if the result of determination in step S73 is that it has not expired ("NO" in step S73), it is determined whether or not the price data included in the barcode read in step S71 is "0" ( Step S75). As a result, when the price data is “0” (“YES” in step S75), the price is 5 digits or more and cannot be represented by a 4-digit number, and the price label is displayed to the operator. It requests to input the price that is printed, and waits until the price data is input (step S76).
[0058]
If the determination in step S75 is “NO”, and if the price is key-input in step S76, the barcode price P read in step S71 or the price P key-input in step S76, and step S72 It is determined whether or not the price P0 of the production log data read out in (1) is different (step S77). Here, when the prices are different (“YES” in step S77), it is the case where the above-described discount processing is performed, and the barcode price P is subtracted from the price P0 read from the production log data. A discount amount is calculated (step S78).
[0059]
Thereafter, in step S79, the registered data, for example, the product name, price, discount amount (if any), content, etc. are displayed and stored in the receipt buffer.
In step S80, the sales record file and production record file are updated for the registered product. That is, the registration data is transmitted to the store controller SC, the sales record file of the store controller SC is updated, and the flag of the corresponding product in the production log file described above is rewritten. The registration data to be transmitted to the store controller SC is a product number and a price for a product that is not discounted, and a product number, a price, and a discount amount for a product that is discounted.
[0060]
The above-described flag is rewritten as “1” for products sold at a normal price without discounting, and “2” for products sold at a discount. When the flag is rewritten to “2”, that is, when discount sales are performed, the amount after discount is also stored in the sales amount column described above in association with the pack ID number.
[0061]
Further, as shown in FIG. 15, the sales record file is composed of a file (total file) in which data of cumulative sales quantity and data of cumulative sales amount are associated with each product number.
[0062]
When the product is disposed of, the flag of the corresponding product in the production log file described above is rewritten to “3”.
Moreover, the input of the discarded product can be performed not only in the case of discarding in the process of step S73 but also by the store clerk scanning and inputting the pack ID number of the expired product from the handy terminal HT at the sales floor.
[0063]
As described above, the process shown in FIG. 13 is a case where the production log data stored in the store controller SC is read and processed at the time of product registration. However, the store controller SC is down, or a failure occurs in the LAN. A detailed procedure of the product registration process when the production log data cannot be read will be described with reference to FIG.
[0064]
First, the scanner unit 28 of the POS register PR reads the barcode added to the product, that is, the pack ID number (identification information) and the price of the product (step S81). The classification of the product is judged from the flag of the first two digits of the read barcode, and the classification name is called (step S82). Each POS register PR includes a classification name file that stores a classification name corresponding to the classification (code), and the classification name is called using this classification name file.
[0065]
Thereafter, it is determined whether or not the price data of the barcode read in step S81 is “0” (step S83). Here, when the price is “0” (“YES” in step S83), the price is 5 digits or more and cannot be expressed by a 4-digit number, and the price printed on the price label by the operator. To wait for key input of price data (step S84).
If the determination in step S83 is “NO”, or if the price is keyed in step S84, the registered data, for example, the classification name and price are displayed and stored in the receipt buffer (step S85).
[0066]
Thereafter, in step S86, the barcode data (pack ID number and price) of the registered product is stored in the memory of the POS register PR as sales performance data.
The sales record data stored in the memory of the POS register PR is transmitted to the store controller SC when communication with the store controller SC becomes possible, and the sales record file and production log data of the store controller SC are respectively stored. Update.
[0067]
(4) Production and sales data processing output processing
This processing is performed when necessary by a device connected to the store controller or LAN by wire or wirelessly, and the processing result is displayed on the display unit and printed and output as necessary.
As described above, the block ID number is stored for each pack ID number in the production log file, and the flag indicating the sales status is further stored. Therefore, by extracting and tabulating data based on the block ID number, For example, various types of aggregated data as shown in FIG. 16 can be acquired in units of block ID numbers.
From the total data, the following information can be acquired in units of block ID numbers.
[0068]
(1) Production data, sales data, loss data for each product number and total
(2) Inventory data for each product number and total
Inventory data (Z) = Production data (S)-Sales data (H)
The inventory data after the expiration date is theoretical loss data.
(3) Sales rate and loss rate for each product number and total
Sales rate = Sales data / Production data x 100 (%)
Loss rate = loss data / production data x 100 (%)
(4) Gross profit (gross profit of purchased raw material blocks)
Gross profit = total sales price (HPT)-purchase price of block ID number
In the above formula, the purchase price of the block ID number is stored in the raw material block file described above.
[0069]
Even after the discard data is input, the product whose flag is “0” is a product that has been lost in the middle due to shoplifting or the like, and the aggregation of the lost product data can be performed in units of block ID numbers.
In addition, since the production log file stores the processing date / time data for each pack ID number, various data is aggregated for each processing date / time data, and the actual inventory, gross profit, and loss in all processes from purchase to sales Can be grasped.
[0070]
In FIG. 17, 5.3 kg of beef piece loin (block ID number = # 12, purchase weight 5.3 kg, purchase price 12,190 yen) was purchased on June 20th, and all sales were completed from June 20th to 22nd. The case is described as an example. Further, FIG. 18 illustrates the gross profit / loss analysis results in units (blocks) in the case illustrated in FIG.
FIG. 17A is a change in purchase, processing (production), and sales process of block ID number = # 12, FIG. 17B is a product loss of block ID number = # 12, and FIG. 17C is a block. ID number = # 12 value input, gross profit, loss calculation, FIG. 17D shows loss analysis of block ID number = # 12.
[0071]
In FIG. 17, each item is calculated based on the following formula.
Price rate = (Production unit price-Purchase unit price) / Production unit price x 100 (%)
Price = Purchase price / (1−Price rate) −Purchase price
Gross profit = total selling price (total selling price)-purchase price
Gross margin = gross profit / total selling price (total selling price)
Loss = Value input-Gross profit
[0072]
(5) Production route information output processing
Next, the production route information output process will be described. This process displays or prints production route information of a product (pack ID product) that the customer (customer) has purchased or intends to purchase using the information output terminal MT installed in the store. Is. That is, in the storage means of the store controller SC and the file server FS, as shown in FIGS. 20 and 21, for each individual identification code (cow number) described above, production route information of the individual (beef cattle), for example, (1) Type, (2) Gender, (3) Date of birth, (4) Birth farm (code), (5) Father cow identification code, (6) Mother cow identification code, (7) Breeding farm (code) ), Period, (8) meat processing plant, (9) production route data file (SDF) that stores the processing date, and ranch name (processing plant name), address, phone number for each ranch code or processing code The ranch data file (BDF) storing the person in charge is stored.
[0073]
The data of these data files SDF and BDF may be made into a database at their own stores, but an individual identification code management center is established throughout the industry, and each data is collected and managed at the management center to create a database. Data collection and management can be ensured accurately and reliably by avoiding other than beef cattle whose data are being collected and managed. The production route data file (SDF) and the ranch data file (BDF) are downloaded from the management center via the Internet as necessary, and stored in the storage means of the store controller SC and the file server FS.
[0074]
When the customer wants to know the production route information of the purchased pack ID product, the customer inputs the original ID number or pack ID number printed on the receipt from the operation unit 35 of the information output terminal MT.
Further, when the purchased product is at hand or when it is desired to know the production route information of the product to be purchased, the pack ID number may be input by causing the scanner unit 38 to read the barcode of the product.
When the pack ID number is input, the information output terminal MT reads the original ID number of this pack ID number from the production log file of the store controller SC.
[0075]
Then, the individual identification code is read from the raw material block file of the store controller SC based on the input original ID number or the read original ID number. Then, the read production route data of the individual identification code is read from the production route data file (SDF), and the production route data is displayed on the display unit 34 with reference to the data of the ranch data file (BDF) ( (See FIG. 22). The customer confirms the data displayed on the display unit 34, and when printing is desired, the print command key of the operation unit 35 is operated and the print unit 37 performs printing.
[0076]
In the above description, the production route data of the purchased pack ID product is displayed or printed by the customer operating the information output terminal MT installed in the store. The contents of the file (SDF) and the ranch data file (BDF) can be called and displayed from the web server WS by the browsing software (browser) of the personal computer at home via the Internet. Therefore, if the customer wants to check the production route information of the purchased pack ID product after returning home, he / she can check at any time by operating the home PC and connecting to the homepage of the store where the product was purchased. can do. For this reason, the address of the homepage of the store is printed in the store data print column of the receipt (see FIGS. 19A and 19B).
[0077]
As described above, according to the product pricing and registration system according to this embodiment,
(1) Individual production data of fresh products can be managed for each product.
(2) Since a 13-digit JAN code is used as a bar code, it can be read using a conventional scanner capable of reading a bar code of NONPLU for fresh food.
(3) Since the bar code includes the product classification and price in addition to the pack ID number, the check-out process can be performed based on the read bar code without referring to the production log data. In this case, the classification name of the classification to which the product belongs can be displayed and printed.
[0078]
(4) Since the price data is included in the barcode, it is possible to perform discount processing similar to that of the conventional NONPLU barcode by pasting the barcode with the changed price data. When a discount is made, the discount amount can be displayed and printed.
(5) The above-mentioned various processes can be performed even when the price of the product is a high-priced product with 5 digits or more.
(6) It is possible to prevent mistakes in selling products whose expiration date has expired.
[0079]
(7) Since production data, block ID numbers, and flags indicating sales status are stored for each pack ID number in the production log file, production data, sales data, and loss data can be aggregated in units of block ID numbers. Inventory management, loss management, and gross profit management for each block ID number can be performed. For this reason, it becomes possible to clarify the loss in the entire process from purchasing to sales.
(8) Further, since the production date and time data is stored for each pack ID number in the production log file, various tabulations can be made for each production time zone.
[0080]
(9) Since the original product ID number or pack ID number is printed on the purchase product details printing field on the receipt, the customer can place the production route information of the purchased product (pack ID product) in the store if desired. You can check the information output terminal by operating it yourself or by operating your home computer.
[0081]
<Other embodiments>
In the case of the above-described embodiment, the receipt is printed and issued by the printing unit. However, instead of printing, the receipt data is written to the storage medium brought by the customer, or transmitted by e-mail or Alternatively, it may be issued by FAX transmission. Of course, these issuing methods may be combined.
In the above-described embodiment, the original ID number or the pack ID number is printed on the receipt. However, the production path data is read based on the pack ID number at the time of product registration, and the read production path data is read out. May be printed directly on the receipt. In this case, the production route data is not printed on receipts of all customers, but is printed only on receipts of desired customers.
[0082]
If a customer management system is used, it is possible to automatically determine whether or not to print the production route data in the customer data and enter the member number. Become.
In the above-described embodiment, beef cattle are used, but other meat such as pigs, sheep, and birds, or fish and fruits and vegetables are stored in association with the original ID number. May be.
The storage of the production route data is not limited to a specific storage method as long as it is stored in association with the original ID number and can be read based on the original ID number.
[0083]
In the case of the above-described embodiment, sales data and discard data for each pack ID number are tabulated using a flag indicating the sales status provided in the production log file, but the pack ID number of the sales product is stored. You may make it tabulate using the sales record log file which memorize | stores the pack ID number of a sales performance log file (When discount sales are carried out, it also memorize | stores a discount amount or a price after discount) and a discarded product pack ID number.
[0084]
Even in this case, the same block ID number and pack ID number are extracted from the production log file, and various data for each block ID number is obtained by searching the sales record log file and the discarded product log file based on the pack ID number. Can be extracted and aggregated.
Thus, the totaling method of sales data and discard data for each pack ID number is not limited to the method described in the above-described embodiment.
[0085]
Further, as shown in FIG. 11, since the production log data includes the processing date / time data, the discount processing can be automated.
For example, in a discount file as shown in FIG. 23, a discount condition (discount time) and a discount amount (or discount rate) are set in advance for each product number. For example, in the product number 23456 shown in FIG. 23, a setting is made to reduce the price by 50% when two days have passed since processing.
[0086]
The discount time is represented by 4 digits, with the first 2 digits representing “day” and the subsequent 2 digits representing “time”. For example, when “0112” is set as the discount time, the discount is performed after 1 day + 12 hours, and when “0004” is set, the discount is performed after 4 hours. . This discount file is stored in the store controller SC and the file server FS.
[0087]
Then, at the time of checkout, the product number and the processing date / time data of the production log data are read from the read pack ID number, and the process after processing based on the processing date / time data and the time of the clock unit 26 of the POS register PR Calculate time. On the other hand, based on the product number, the discount data of this product number is read out from the discount file and calculated, and it is determined whether the elapsed time exceeds the discount time. I do.
[0088]
In the case of the discount file in FIG. 23, there is one discount condition for each product number. However, a plurality of discount conditions may be stored for each product number. For example, “10% discount after 1 hour”, “30% discount after 2 hours”, “50% discount after 3 hours” can be set to the elapsed time after processing. A detailed automatic discount process can be performed accordingly.
[0089]
Moreover, when performing this automatic discount process, it is necessary to display an explanation to that effect on the merchandise display and report it to the customer.
Although this explanation is for automatic discount processing, according to the present invention, it is possible to simplify the “(2) discount processing for closed products” in the above-described embodiment. That is, in the above-described embodiment, the bar code label of the discounted amount is printed and issued at the handy terminal HT, and is overlaid on the bar code label that has been pasted. In this case, the store clerk must bring a handy terminal HT having a label printing function or a portable label printer, and the issued label must be overlaid on the price label of the product. It is a troublesome work.
[0090]
The problem is that the bar code label of the discounted amount is not issued, but the pack ID number of the product is scanned and input at the handy terminal HT, and the discount amount or the discounted amount is input to the file server FS or the store. It is transmitted to the controller SC and stored. At the time of check-out, when the barcode attached to the product is read by the scanner unit 28 of the POS register PR, the discount amount or the discount amount described above is stored for the pack ID number of this barcode. If so, the discount process is performed using the stored discount information. As a result, the store clerk can print and issue a discount barcode label at the handy terminal HT or the like, and can perform the same discount process without performing an operation of overlaying and sticking on the price label of the product. .
[0091]
In the above-described embodiment, the case where the fresh food is an indefinite product has been described. However, the present invention can be applied to a fixed amount product as long as it is a product produced by processing a raw material block. It is.
However, in the case of fixed-price products, the amount data is constant, so the amount can be determined by referring to the product file for pricing (PLU file), so it is not necessary to store the amount data in the production log file. Good.
Further, when the weight is not measured for each product, the weight data is not stored in the production log file. However, the weight data may be measured for each product and stored in the production log file.
[0092]
In the present invention, since the fresh food is identified for each product by the pack ID number, the following applications can be considered. That is, transaction data (registered merchandise details information and checkout information) for each customer checked out by the POS register PR is stored as an electronic journal (electronic log) for a predetermined time by the POS register PR and the store controller SC. When the customer wishes to return the product by bringing it in or when he / she wants to confirm the transaction data, the electronic log is called up and displayed. Conventionally, electronic log data is called up by inputting a receipt number printed on a receipt, and reading and displaying transaction data of the receipt number.
[0093]
When a product with a pack ID number added is registered, if the pack ID number is also stored in the electronic log data, the pack ID number can be entered from the electronic log data by inputting the pack ID number. By reading and displaying the transaction data including the commodity with the number, it is possible to call the desired transaction data without inputting the receipt number.
As a result, when the customer wishes to return the pack ID product, the return process can be performed without bringing a receipt. (Note that the same pack ID number may be used every predetermined period, so if there is more than one transaction data by entering the pack ID number, the latest transaction data will be given priority. To display it.)
[0094]
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 and the like within a scope not departing from the gist of the present invention.
For example, in the above-described embodiment, the price of the product is printed with the barcode together with the pack ID number, but the price may not be printed. In addition, the flag of the first two digits of the one-step barcode is also used as the product classification, but the present invention is not limited to this. It is also conceivable to use the “machine number” information in the barcode as “classification” information.
[0095]
However, in this case, it is necessary to provide that a certain pricing machine always prices the products of the same product classification. However, in the case of a store of a certain size or more, usually, a dedicated pricing machine is arranged and used for each work place in the back room, for example, each work place in the meat part, fresh fish part, fruit and vegetable part, and side dish part. Therefore, if the product classification is a rough classification, there is no practical problem even if the machine number = product classification.
[0096]
Further, “classification data” may be printed in place of the “day of the week” in the fourth digit of the first-order barcode. That is, the classification data may be included in the pack ID number portion.
Further, when the production log data cannot be read, it is not necessary to include the classification data in the barcode if the product classification need not be printed on the receipt.
[0097]
In the case of the above embodiment, the pack ID number includes the machine number, and each device performs serial number issuance management. However, a management apparatus such as the file server FS collectively issues the pack ID number and Management may be performed. However, since the pack ID number is based on the premise that each product can be individually identified, it must be unique at least within a certain period (more than the best-before period of the pack ID product).
[0098]
Furthermore, in the above-described embodiment, the pack ID number and the price are printed with one-step barcode. However, it is possible to individually identify the product produced by reading the barcode and determine the price of the product. For example, the barcode may be any configuration, for example, a two-level barcode, a barcode based on a code system other than JAN such as the code 39, or a two-dimensional barcode, and the specific configuration is not limited.
[0099]
Further, the production data stored in association with the pack ID number is not limited to the above-described embodiment, and necessary data for management may be stored as appropriate. For example, “machine number”, “lot number”, “person in charge code”, “purchase code”, etc. may be stored.
[0100]
In the above-described embodiment, the production result data needs to be stored in a storage device in the necessary period file server FS, the store controller SC, etc., but after the necessary period has elapsed (for example, after a predetermined period from the processing date and time) ) May be erased, stored in a storage medium such as a CD-R, or printed out and stored.
[0101]
In the above-described embodiment, the production data of the weighing price system is configured to be transmitted to the store controller SC of the POS system via the LAN, but is stored in a recording medium such as a CD-R and transmitted offline. You may do it.
[0102]
In addition, any system configuration may be used as long as the method for pricing and registering a fresh product according to the present invention can be realized. For example, one POS register may be a parent-child system having a store controller function. Further, the store controller SC of the POS system and the file server FS of the measurement value added system may be configured by one file server.
[0103]
【The invention's effect】
  As explained above, the claims1According to the invention described inSince the production route information of the purchased product is printed on the receipt, the customer can confirm the production route information of the purchased product with the receipt, so that a sense of security can be obtained.
In addition, stores can appeal that their products are clear and safe.
[Brief description of the drawings]
FIG. 1 is a layout diagram of a retail store that sells products such as fresh food, and shows a schematic configuration of a retail store to which a pricing and registration system for products such as fresh products according to an embodiment of the present invention is applied. FIG.
2 is a block diagram showing the configuration of a product pricing and registration system for explaining the flow of data processing in the retail store shown in FIG. 1; FIG.
FIG. 3 is an electrical configuration diagram of a weighing label printer DPS.
FIG. 4 is an electrical configuration diagram of a POS register PR.
FIG. 5 is an electrical configuration diagram of an information output terminal MT.
FIG. 6 is a data configuration diagram of a PLU file for pricing processing.
FIG. 7 is a flowchart showing an outline of a procedure of a pricing process and a totaling process.
FIG. 8 is a data configuration diagram of a raw material block file.
FIG. 9 is a view showing a display example of a price label according to the present invention.
FIG. 10 is a diagram showing a configuration of a barcode according to the embodiment.
FIG. 11 is a diagram showing a data configuration of a production performance file.
FIG. 12 is a flowchart showing a procedure of product registration / settlement / aggregation processing according to the embodiment;
FIG. 13 is a flowchart showing a procedure of product registration processing when a production log of a production result file is read and executed.
FIG. 14 is a flowchart showing a procedure of product registration processing when a production log of a production result file cannot be read.
FIG. 15 is a diagram showing a data structure of a sales record file.
FIG. 16 is a diagram showing total data for each raw material block ID number.
17A is a diagram showing changes in the purchasing, processing, and sales processes of block ID number = # 12, FIG. 17B is a diagram showing product loss of block ID number = # 12, and FIG. 17C is a block ID. The figure which shows the calculation of the value input of the number = # 12, the gross profit, and the loss, FIG.
FIG. 18 is a diagram showing an example of gross profit / loss analysis in units of originals (blocks).
FIG. 19 is an explanatory diagram illustrating an example of printing a receipt.
FIG. 20 is an explanatory diagram showing a data structure of a production route data file (SDF).
FIG. 21 is an explanatory diagram showing a data structure of a ranch data file (BDF).
FIG. 22 is an explanatory diagram showing a display example of production route data of pack ID products displayed on the display unit.
FIG. 23 is a diagram showing a data structure of a discount file.
[Explanation of symbols]
1, 21, 31 ... CPU, 2, 22, 32 ... ROM, 3, 23, 33 ... RAM, 4, 24, 34 ... display unit, 5, 25, 35 ... operation unit, 6, 27, 37 ... printing unit 7, measuring unit 9, 26, 36 clock unit 28, 38 scanner unit 8, 29, 39 communication unit DPS measuring label printer FS file server TR transceiver HT handy Terminal, MT ... Information output terminal, N1 ... Weighing pricing system (LAN in back room) (pricing device), N2 ... POS system (LAN in store), PR ... POS register (registration device), SC ... Store controller

Claims (1)

When pricing a weighed product, an identification number (pack ID) for identifying the product for each item is printed on the pricing label with a barcode, and the raw material block (pack ID ) of the product corresponding to this identification number ( pack ID ) A pricing device that stores production data including an identification number (original ID) for identifying the original)
Production route storage means for storing production route information of the original corresponding to the original ID;
Registration for printing the identification number (pack ID) Production route information stored in association with the corresponding identification number (conformal ID) the identification number (pack ID) read when registering a product identified by the receipt Equipment,
A product pricing and registration system characterized by comprising:

Images