JP2007200242A - History search code management server and system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To obtain a system usage frequency of each commodity supplier, for which history information is provided by a traceability system, for determining a utilization rate of the traceability system by each supplier. <P>SOLUTION: An individual body code distribution server 10 receives an individual body code acquisition request showing a supplier code allowing specification of the commodity supplier as an application target of the individual body code, and according to the individual body code acquisition request, issues the individual body code. The individual body code distribution server 10 accumulates individual body code distribution history information associating the supplier code presented by the individual body code acquisition request with history search code relevant information (information such as the number and the issue date of the issued individual body codes) related to the individual body code issued by the individual body code acquisition request. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention provides a history search code management for issuing a history search code assigned to a product for searching history information and managing the issued history search code so that the history information of the product can be provided in the traceability system The present invention relates to a server and a history search code management system.

  2. Description of the Related Art In recent years, traceability systems that provide consumers and the like who have purchased specific vegetables and meat with a history of production and distribution of the vegetables and meat via a communication network such as the Internet have come to be used.

  The traceability system searches the production / distribution history of a product by using the traceability code printed on a product tag attached to a container such as a pack that contains products such as vegetables and meat as a search key. It is possible to browse (see, for example, Patent Document 1).

JP 2005-31875 A

  In the conventional system described in Patent Document 1 described above, the production / distribution history of products is provided, but the products for which history information is provided by the traceability system (fruits, meat, chicken eggs, processed foods, seasonings) To determine the extent to which the traceability system is used by each supplier because it is not possible to grasp the degree of use of the traceability system for each supplier (supplier: producer or seller). There was a problem that could not.

  The present invention solves the above-mentioned problems, can grasp the system usage of each supplier of products for which history information is provided in the traceability system, and how much the traceability system is used for each supplier. It is an object of the present invention to provide a history search code management server and a history search code management system that can determine whether or not there is a search.

  The history search code management server (for example, the individual product code distribution server 10) of the present invention is provided with a history search code assigned to a product to search for history information so that the history information of the product can be provided in the traceability system. Is a history search code management server that manages the issued history search code, and obtains a history search code acquisition request that presents a supplier code that can identify the supplier of the product to which the history search code is assigned A receiving means, a history search code issuing means for issuing a history search code in response to a history search code acquisition request, a supplier code presented in the history search code acquisition request, and a history in response to the history search code acquisition request History search code related information related to the history search code issued by the search code issuing means Characterized by comprising a code issuing history information storage means for storing correspondence with code issuance history information.

  By configuring as described above, it is possible to grasp the system usage of each supplier of products for which historical information is provided by the traceability system, and how well the traceability system is used by each supplier. Can be judged.

  The history search code related information is, for example, the number of history search codes issued by the history search code issuing means, or the history search code itself issued by the history search code issuing means.

  Based on the code issuance history information, there may be provided a billing amount calculation means for calculating a billing amount to be charged to the supplier as a consideration for the service provided to the supplier including the history search code issuance work. If comprised in this way, the charge amount with respect to each supplier according to the system utilization of each supplier of the goods for which historical information is provided in the traceability system can be calculated.

  The supplier code is, for example, at least one of a producer code that can specify the producer of the product and a seller code that can specify the seller of the product.

  The acquisition request receiving means receives a history search code acquisition request that presents a supplier code that can identify a supplier in a plurality of products to which a history search code is to be assigned, and the history search code issuing means responds to the history search code acquisition request. Accordingly, a plurality of history search codes to be assigned to each of a plurality of products may be issued.

  In addition, the history search code management system of the present invention issues a history search code given to a product for searching history information so that the history information of the product can be provided in the traceability system. A history search code management system for managing codes, an acquisition request execution means for making a history search code acquisition request that presents a supplier code that can identify a supplier of a product to which a history search code is to be assigned, and execution of the acquisition request Acquisition request receiving means for receiving a history search code acquisition request from the means via a communication network, history search code issuing means for issuing a history search code in response to a history search code acquisition request, and a history search code acquisition request The provided supplier code and the history search code in response to the history search code acquisition request Communicates the code issuance history information accumulating means for accumulating the code issuance history information associated with the history retrieval code related information related to the history retrieval code issued by the execution means, and the history retrieval code issued by the history retrieval code issuing means A history search code receiving means for receiving via a network, and a history search code printing / pasting means for printing or pasting the history search code received by the history search code receiving means on a product to be given It is characterized by.

  According to the present invention, it is possible to grasp the system usage of each supplier of products for which historical information is provided in the traceability system, and to determine how much the traceability system is used by each supplier. It is possible to provide a history search code management server and a history search code management system.

Hereinafter, an embodiment of the present invention will be described with reference to the drawings.
FIG. 1 is a block diagram showing an example of the configuration of a code management system 100 showing an embodiment of the present invention. As shown in FIG. 1, the code management system 100 includes an individual product code distribution server 10, a product master server 20, an in-store weighing machine server 30, weighing machines 41 to 4N (N: any positive integer), including.

  The individual product code distribution server 10, the product master server 20, and the in-store weighing machine server 30 are each connected to a communication network 50 such as the Internet. Further, the in-store weighing machine server 30 and the weighing machines 41 to 4N are respectively connected to a communication network 60 such as a LAN arranged in the shop A, for example.

  In FIG. 1, the in-store weighing machine server 30 and the weighing machines 41 to 4N installed in the store A are shown, but are managed by a store general manager who manages a plurality of stores including the store A. The code management system 100 may include an in-store weighing machine server and a weighing machine installed in other stores. Moreover, although one merchandise master server 20 is shown in FIG. 1, the code management system 100 may include a plurality of merchandise master servers each managed by a large number of store general managers.

  The individual product code distribution server 10, the product master server 20, and the in-store weighing machine server 30 are each configured by an information processing device such as a WWW server.

  The individual product code distribution server 10 is a central server managed by a system administrator of the code management system 100, for example, and distributes individual product codes (traceability code, history search code) and provides history information in the traceability system. Various processes such as processes are executed. The individual product code distribution server 10 identifies individual product code distribution history information (supplier usage information) for identifying the usage of the system 100 of each supplier, who is a product provider, and individual products codes that can be distributed. A distribution history information DB 11 for storing individual product code information and the like.

  The product master server 20 is managed by, for example, a store general manager who manages a plurality of stores including the store A, and stores a product master including various product information related to each product sold at each managed store. The product master DB 21 is provided. In the product master, for example, for each product, the case code, product name, unit price (price per unit weight, price per unit) given to the case when the product is transported from the production area, producer Including various product information such as production area. The product master DB 21 may be inside or outside the product master server 20.

  The in-store weighing machine server 30 is managed by, for example, a store manager who manages the store A, exchanges information with each of the weighing machines 41 to 4N via the communication network 60, and an individual product code via the communication network 50. Information is exchanged with the distribution server 10 and the product master server 20.

  Each weighing machine 41 to 4N identifies a product in a traceability system, for example, in addition to the function of weighing products such as meat, vegetables, fish, and eggs, the function of dividing (separating and sorting) meat and vegetables, etc. Various functions, such as a function to attach a label with a product identification number (label code: traceability code, history search code) assigned for management and a function to manage a part of history information inquired in the traceability system . In addition, since each weighing machine 41-4N is the same structure, the weighing machine 41 is mainly demonstrated in the following description.

  FIG. 2 is an explanatory diagram showing an example of individual product code distribution history information. The individual product code distribution history information is a specific example of supplier usage information that can specify the usage of the system 100 for each supplier of products for which history information is provided by the traceability system. That is, in this example, the usage of the system 100 of each supplier who is a product provider is specified based on the individual product code distribution history information stored in the distribution history information DB 11.

  As shown in FIG. 2, the individual product code distribution history information includes a producer code that identifies the producer of the product, a store code that identifies the store where the product is sold, and an individual product code for the product. It includes a distribution date and time specifying the distribution date and a distributed individual product code number indicating the number of individual product codes distributed at the distribution date and time corresponding to the product. That is, the individual product code distribution history information is information in which a distribution date and the number of distributed individual product codes are associated with a code specifying a producer of a product as a supplier and a store where the product is sold.

  In addition to the producer code and the store code, the individual product code distribution history information may include information that can identify other types of suppliers, such as a manufacturer code that identifies the manufacturer of the product. Moreover, only one piece of information that can specify a supplier among information that can specify a supplier such as a producer code, a store code, and a manufacturer code may be included in the individual product code distribution history information.

  FIG. 3 is a block diagram illustrating an example of the configuration of the weighing machine 41. As shown in FIG. 3, the weighing machine 41 includes a case code reading unit 411, an individual product code request unit 412, a data communication unit 413, a product master data request unit 414, an article dividing unit 415, and an article weighing unit. 416, a price calculation unit 417, a label code determination unit 418, a label printing unit 419, a label pasting unit 420, a packaging processing unit 421, a data input unit 422, a data output unit 423, and a weighing machine DB 424. including.

  Note that a storage medium such as a ROM provided in the weighing machine 41 stores a control program for causing the units 411 to 423 constituting the weighing machine 41 to execute various processes.

  In addition, the weighing machine 41 is provided with a transport path for transporting an article (product) to be processed and a transport mechanism for transporting the transport path in order to sequentially execute various processes.

  The case code reading unit 411 has a function of reading a code (case code) attached to a case in which an article such as meat is carried into a store. Specifically, the case code reading unit 411 is configured by a barcode reader when the case code is written in a barcode, and when the case code is stored in an RFID (Radio Frequency Identification) tag. Consists of a tag reader.

  The individual product code request unit 412 performs processing for requesting an individual product code that can be assigned to the individual product code distribution server 10. The data communication unit 413 has a function of exchanging various data via the communication networks 50 and 60.

  The product master data request unit 414 performs processing for requesting the product master server 20 to provide part or all of the product information indicated by the product master.

  The article dividing unit 415 performs a process of cutting the received partial meat, a meat processing for converting the partial meat of one or more raw meat individuals into minced meat, and the like. In addition, you may make it the person in charge of a store perform the division | segmentation operations, such as cutting of a partial meat, and the meat processing which meat-throws to minced meat etc. In this case, it is not necessary to provide the article dividing unit 415.

  The article weighing unit 416 includes a placing table on which products are placed, and performs processing for weighing the products placed on the placing table. The placement on the placement table may be automatically performed by a transport mechanism that transports the product, or may be performed by a person in charge at the store. The price calculation unit 417 performs processing for calculating the price of the product based on the measurement result by the article measurement unit 416.

  The label code determination unit 418 performs processing for determining a code (label code) to be printed on the label. The label printing unit 419 has a printing mechanism such as a print head, and performs a process of printing label information including a label code on a label. When an IC tag is used as a label, the label printing unit 419 is configured by an IC tag writer.

  The label affixing unit 420 performs a process of affixing the label on which the label information is printed on a packaging medium (for example, a packaging container or a packaging cover) for packaging the product. The packaging processing unit 421 performs a process of packaging the product with the packaging medium to which the label is attached.

  The data input unit 422 is configured by an input device such as a keyboard, for example, and has a function of inputting various information to the weighing machine 41. The data output unit 423 is configured by a display device such as a liquid crystal display device and has a function of displaying various information.

  The weighing machine DB 424 is configured by a storage medium such as a RAM, for example, and stores various types of information such as weighing related information (see FIG. 6) described later, which is a part of information used for history inquiry in the traceability system. .

Next, the operation of the code management system 100 of this example will be described.
The weighing machine 41 in this example mainly measures meat products such as a partial meat of a raw pig individual or minced meat mixed with a partial meat of a plurality of raw pig individuals, and assigns a label code to the partial meat or the meat product. It has the function to do. Here, the process until the articles carried into the store A are processed by the weighing machine 41 and packaged for each product unit will be described. In addition, here, in order to simplify the explanation, the raw meat partial meat B is divided and weighed, and a case where a label printed with a label coat is attached to the packaging will be described as an example, and is particularly related to the present invention. Except for processing, the description may be omitted.

  FIG. 4 is a flowchart showing an example of code management processing in the code management system 100 of the present example. In the code management process, first, the case code reading unit 411 reads the case code attached to the case in which the raw pork meat B is accommodated, and stores the read case code in the weighing machine DB 424 (step S101). . Here, the case code is an individual identification number of the corresponding raw pig. In addition, the case code reading part 411 reads the case code attached | subjected to each case, when using the partial meat | flesh of the multiple types of raw pig accommodated in two or more cases.

  Next, the individual product code request unit 412 presents the case code read in step S101 to the individual product code distribution server 10 and the weighing machine number for uniquely identifying the weighing machine 41, and performs communication. Distribution of usable individual product codes is requested via the network 60, the in-store weighing machine server 30, and the communication network 50 (step S102). In this example, the store code indicating the store A, which is the corresponding store, is added to the data to be transmitted by the in-store weighing machine server 30.

  Upon receiving a request from the weighing machine 41, the individual item code distribution server 10 selects a predetermined number of individual item codes that are not yet used in the code management system 100 (step S103), and transmits them to the weighing machine 41 in a batch. (Step S104). The individual product code distribution server 10 updates the individual product code distribution history information (step S105) and updates the individual product code distribution destination information (step S106).

  In this example, the individual product code distribution server 10 selects and transmits, for example, 20 individual product codes in steps S103 and S104. The number of individual product codes to be selected is determined in advance for each weighing machine serving as a distribution destination, for each producer code specified by the case code, or for each product specified by the case code. The same number of individual product codes may be distributed for all weighing machines, producer codes, or products. The number determined for each weighing machine, producer code, or product to be distributed may be a constant or non-constant. In the case of an indefinite number, for example, a parameter for determining the number of individual product codes may be changed in accordance with the amount of usage (operating rate) per certain time of the target weighing machine. Also, a step of temporarily storing and using codes that have been distributed but not used, or returning them to the headquarter server 10 and updating them may be set.

  In step S103, the individual item code information for specifying the individual item codes that can be distributed is referred to, and an individual item code that has not been issued is selected. That is, each individual product code is selected to be a unique code.

  Further, the individual product code distribution server 10 updates the above-described individual product code distribution history information (see FIG. 2) in step S105. Specifically, the producer code specified by the case code, the store code added by the in-store weighing machine server 30, the date and time when the individual product code was distributed, and the distributed number indicating the number of individual product codes distributed The number of product codes is associated with each other and stored in the individual product code distribution history information.

  Further, the individual product code distribution server 10 updates individual product code distribution destination information as shown in FIG. 5 in step S106. That is, the distributed individual product code and the weighing machine number for specifying the distribution-destination weighing machine 41 are associated with each other and stored as individual product code distribution destination information. The individual product code distribution destination information is stored in a DB (for example, distribution history information DB 11) provided in the individual product code distribution server 10.

  The weighing machine 41 acquires a predetermined number of unused individual product codes from the individual product code distribution server 10 via the communication network 50, the in-store weighing machine server 30, and the communication network 60 by the data communication unit 413.

  Next, the merchandise master data request unit 414 presents the case code read in step S <b> 101 to the merchandise master server 20 via the communication network 60, the in-store weighing machine server 30, and the communication network 50. Then, specific product information about the product specified by the case code is requested (step S107). The specific product information means specific information included in the product information indicated by the product master. In this example, the specific product information is assumed to be information including the unit price of the product and the product name.

  In response to a request from the product master data request unit 414, the product master server 20 extracts specific product information about the product specified by the received case code from the product master stored in the product master DB 21, and performs weighing. Transmit to the machine 41 (step S108).

  The weighing machine 41 acquires specific product information from the product master server 20 via the communication network 50, the in-store weighing machine server 30, and the communication network 60 by the data communication unit 413. That is, specific product information including the product name and unit price of the partial meat B specified by the case code is acquired.

  Next, in this example, the article dividing unit 415 performs processing for dividing the partial meat B and dividing it into product units (step S109).

  When divided into product units, the article weighing unit 416 measures the products in the product unit, and stores the measurement results in the weighing machine DB 424 in association with the corresponding case codes (step S110).

  Based on the measurement result of the article weighing unit 416 and the product unit price included in the acquired specific product information, the price calculation unit 417 calculates the price of the weighed product and applies the calculation result to the corresponding case. The data is stored in the weighing machine DB 424 in association with the code (step S111).

  Then, the label code determination unit 418 assigns one of the individual product codes that have not been used among the plurality of individual product codes distributed by the individual product code distribution server 10 to the product to be processed. Then, a label code to be given to the product is determined (step S112). That is, any one of the plurality of individual product codes acquired from the individual product code distribution server 10 becomes a label code to be given to the product to be processed. The label code determination result is stored in the weighing machine DB 424 by the label code determination unit 418 in association with the corresponding case code.

  When the label code is determined, the label printing unit 419 prints label information such as a label code on the label, and the label sticking unit 420 sticks the label printed with the label information on the packaging medium (step S113).

  The label information includes, for example, various information such as a label code, current date and time, product name, product type, product weight, product price, store name, quality assurance date, expiration date, and production location. included.

  Then, the packaging processing unit 421 packages the product to be processed with the packaging medium to which the label is attached (Step S114).

  Furthermore, the weighing machine 41 transmits the label code and the measurement related information to the product master server 20 (step S115). The merchandise master server 20 stores the received label code and measurement related information (step S116).

  When the processing up to the packaging of one unit of the plurality of products as the product unit is completed, the weighing machine 41 returns to step S110 if the product to be processed remains (step S117). By repeatedly executing the processing of step S110 to step S117, the processing from weighing to packaging is completed for all of the plurality of products in the product unit.

  In addition, the process of step S110-step S115 may not be sequentially performed for every goods, but the process of step S110-step S115 may be sequentially performed for every process unit. That is, for example, product A may be weighed, product B may be weighed and product A price may be calculated, product C may be weighed, product B price calculated, and product A label code may be determined. The processing procedure for a plurality of products may be determined in any way as long as it is a procedure that enables the weighing to packaging of each product.

  The weighing machine 41 of the present example determines the weighing result (weight) in step S110, the calculation result (price) in step S111, and the determination in step S112 in the case code read in step S101 in the weighing label pasting process described above. The measurement-related information is created by sequentially associating the label code and the contents of label information other than the label code printed in step S113, for example, the quality guarantee deadline. Therefore, by executing the above-described measurement label attaching process, for example, measurement related information as shown in FIG. 6 stored in the weighing machine DB 424 is created.

  In the above-described measurement label affixing processing, weighing is performed after the article contained in the case is divided, but the article contained in the case is processed as one product without being divided. However, even if a single product (for example, sashimi assortment) is formed by a plurality of types of articles (for example, tuna and machi) accommodated in a plurality of cases, a plurality of items accommodated in one case are also included. You may make it process each article (for example, 60 apples) or every predetermined number (for example, every 3 pieces) as one goods.

  Further, in the above-described measurement label affixing process, a predetermined number of individual product codes are distributed together and distributed as a label code to each product obtained by dividing an article. If the number of divided products is small, the individual product code that has not been used may be notified to the individual product code distribution server 10. In this way, since the individual product codes that are not used in the individual product code distribution server 10 can be handled as unused individual product codes, the individual product codes can be distributed without waste. become. If the number of products divided into the number of individual product codes is large, the individual product code distribution server 10 may be requested to additionally distribute individual product codes.

Next, history providing processing based on product history inquiry in the traceability system will be described.
FIG. 7 is a block diagram illustrating an example of a history inquiry system including a consumer terminal 70 used by a consumer who has purchased a product. In FIG. 7, the same components as those in the system 100 shown in FIG.

  The consumer terminal 70 is configured by an information processing apparatus such as a personal computer or a portable information terminal, for example, and includes an environment including software and hardware for connecting to the communication network 50.

  Here, a case where the consumer X who has purchased the product Y requests a history inquiry of the product Y using the consumer terminal 70 will be described as an example.

  First, the consumer terminal 70 accesses the headquarters server 10 according to the operation of the consumer X and presents the label code written on the label attached to the product Y.

  When the headquarters server 10 receives the history inquiry request that presents the label code, the head office server 10 refers to the individual product code distribution destination information (FIG. 5) stored in the DB provided therein, and presents the label coat (individual product code) The distribution-destination weighing machine number associated with is searched, and the weighing machine that performed processing such as weighing of the product Y is identified from the retrieved distribution-destination weighing machine number. Here, it is assumed that the weighing machine 41 is specified.

  Next, the headquarter server 10 presents the label code presented from the consumer terminal 70 to the specified weighing machine 41 and makes an acquisition request for weighing related information. Then, the weighing machine 41 extracts the measurement related information including the presented label code in response to a request from the headquarter server 10 and transmits it to the headquarter server 10.

  When the headquarter server 10 receives the measurement related information, the headquarter server 10 searches the production information including the production place and the producer from the case code (individual identification number) included in the received measurement related information. The production information is stored in a DB provided in the headquarter server 10 in association with, for example, a case code. The production information may be managed by another server. In this case, the headquarter server 10 inquires of the server that manages the production information using the case code as a key, and the production of the product Y from that server. What is necessary is just to acquire information.

  Then, the headquarter server 10 provides part or all of the information indicated by the acquired measurement-related information to the consumer terminal 70 as part or all of the distribution history, and part or all of the acquired production information. Provide as part or all of the production history.

  Note that the measurement related information may be stored in the headquarter server 10, and the process for acquiring the measurement related information from the weighing machine 41 may be omitted as the measurement related information when the history inquiry request is received.

  FIG. 8 is a flowchart showing an example of billing information aggregation processing in the code management system 100 of this example. The billing information totaling process is executed periodically, for example, every day, every week, every month, or in response to an instruction from a billing collection system (not shown) connected to the system administrator or the communication network 60.

  In this example, individual product code distribution history information (see FIG. 2) is accumulated as supplier usage information for deriving the usage fee of the system 100 that charges each supplier in step S105 described above. Here, a case where the charge amount to the supplier Z is calculated will be described as an example.

  In the accounting information totaling process, first, the individual product code distribution server 10 refers to the individual product code distribution history information, and within a predetermined period (for example, a predetermined one month when charging monthly), All the distributed individual product code numbers associated with the Z supplier code (producer code or store code) and the distribution date and time are extracted (step S201). That is, the number of distributed individual product codes indicating the number of individual product codes distributed for the supplier Z within the target period and the distribution date and time are all extracted.

  Next, the individual item code distribution server 10 refers to a charging amount table (not shown) (a table in which the charging amount per individual item code is posted), and distributes it to the supplier Z at the distribution date and time and each distribution date and time. A billing list in which the number of individual codes is associated with the billing amount is generated (step S202). In the billing amount table, for example, as shown in FIG. 9, the billing amount per individual product code may vary depending on the supplier, or may vary depending on the distribution date and distribution amount.

  Then, the individual product code distribution server 10 refers to the generated charging list, and calculates the total amount charged for the supplier Z as consideration for using the system 100 during a predetermined period (step S203). The calculated charge amount is settled by the charge collection system based on, for example, the credit card information of the supplier registered in advance.

  As described above, in the above-described embodiment, in order to be able to provide the history information of a product in the traceability system, a history search code given to the product is issued and issued to search the history information. The individual item code distribution server 10 that manages the history search codes received receives an individual item code acquisition request that presents a supplier code that can identify the supplier of the item to which the individual item code is to be assigned, and responds to the individual item code acquisition request. Issue the individual code, supply the supplier code presented in the individual code acquisition request, and the history search code related information related to the individual code issued in response to the individual code acquisition request (issued individual item Traceability system because it is configured to store individual product code distribution history information that associates information such as the number of codes and issue date and time) The system usage of each supplier of products for which historical information is provided can be ascertained using the accumulated individual code distribution history information, and it is determined how much the traceability system is used by each supplier. can do.

  In the embodiment described above, since the individual product code distribution server 10 is configured to calculate the charge amount for the supplier based on the individual product code distribution history information, the history information is provided by the traceability system. It is possible to calculate the billing amount for each supplier according to the system usage of each supplier of the merchandise.

  In the above-described embodiment, the individual code acquisition request for uniquely identifying each product is made by presenting the weighing machine number to the individual code distribution server 10 that manages the individual code. Thus, the individual product code is acquired from the individual product code distribution server 10 via the communication networks 50 and 60, and the acquired individual product code is determined to be a label code to be given to the product to be processed. A label with the label code is pasted on the product packaging, and weighing-related information including the label code is stored, and the individual machine code and the weighing machine number indicating the weighing machine to which the individual code is distributed In response to a history information acquisition request from the individual product code distribution server 10 that manages the individual product code distribution destination information managing the individual product code distribution destination information, the measurement related information including the label code is obtained. Since the product code distribution server 10 is provided via the communication networks 50 and 60, the data amount of the label code assigned to identify the product in the traceability system can be greatly reduced, and the traceability system It is possible to provide a weighing machine 41 that functions effectively in order to reduce the information management burden in the individual product code distribution server 10 that manages the information necessary for the history inquiry.

  In other words, it is sufficient that the number of digits of the label code is sufficient to cover the number of products handled by the entire system, and it is not necessary to include information such as date and individual identification number in the label code. The amount of code data can be greatly reduced. Therefore, the required storage capacity of the storage medium for storing the label code can be reduced, and the processing load when transmitting the label code over the communication network and the search processing load when searching using the label code as a key are reduced. It can be reduced.

  Further, in the above-described embodiment, a plurality of individual product codes are collectively acquired from the individual product code distribution server 10, and any unused individual product code among the acquired individual product codes is a processing target. Since the label code to be assigned to the merchandise is determined, the label code can be quickly and smoothly assigned to each of a plurality of same-type merchandise.

  In the above-described embodiment, the case code attached to the case in which the article to be the product is stored is read, and the read case code is presented to the product master server 20 that manages the product information. The specific product information is acquired from the product master server 20 via the communication networks 50 and 60, and the unit price of the product indicated by the acquired specific product information and the measurement result of the product are obtained. Necessary for querying history in the traceability system because the price is calculated according to the above, and a label with the calculated price is affixed to the product packaging, and the measurement related information including the calculated price is stored. Information can include the price.

  In the embodiment described above, meat products such as minced meat mixed mainly with raw pork individuals and minced meat mixed with plural raw pork individuals are weighed, and the label code is applied to the partial meat and meat products. In the case of products, food products other than pigs (for example, cattle, sheep, chickens, marine products (for example, fish, shellfish, etc.)) are products. Alternatively, the present invention can be applied even when other foods such as eggs and fruits and vegetables (for example, vegetables and fruits) become products. For example, when the product is a marine product, a label code is given to a product such as a fish processed by carving or the like, or a product such as a fish or a shellfish divided into a predetermined number or a predetermined weight. Further, when the product is a fruit or vegetable, a label code is given to the fruit or vegetable processed by cutting or the like (for example, cut fruit) or the fruit or vegetable divided into a predetermined number or a predetermined weight. In addition, you may make it make a drink into goods, In this case, a label code will be given to the drink product (goods) in which the drink was divided into drink containers (for example, a bottle, a pack).

  Further, in the above-described embodiment, the individual product code distribution server 10 is configured to issue a plurality of individual product codes all together, but may be issued one by one.

  In the above-described embodiment, the individual code distribution history information includes the number of individual code issued for each issue date and time. However, the content of the issued individual code is not the number of individual codes. (In other words, the issued individual product code itself) may be included in the individual product code distribution history information. Even in this case, since the number of individual product codes issued can be calculated, each supplier according to the system usage of each supplier of the product for which history information is provided in the traceability system The charge amount for the supplier can be calculated.

  In the above-described embodiment, the case code is the individual identification number. However, any code such as a bit image may be used as long as the production information of the corresponding product can be specified.

  According to the present invention, it is useful for grasping the system usage of each supplier of products for which historical information is provided in the traceability system and determining how much the traceability system is used by each supplier. It is.

It is a block diagram which shows the example of a structure of the code | cord | chord management system containing the weighing machine in one embodiment of this invention. It is explanatory drawing which shows the example of individual goods code distribution log | history information. It is a block diagram which shows the example of a structure of a weighing machine. It is a flowchart which shows the example of a code management process. It is explanatory drawing which shows the example of individual product code distribution destination information. It is explanatory drawing which shows the example of measurement relevant information. It is a block diagram which shows the example of the code | cord | chord management system containing the consumer terminal used for the consumer who purchased goods. It is a flowchart which shows the example of an accounting information total process.

Explanation of symbols

10 Item code distribution server (headquarters server)
20 Product Master Server 21 Product Master DB
30 In-Store Weighing Machine Server 41-4N Weighing Machine 50, 60 Communication Network 70 Consumer Terminal 100 Code Management System 411 Case Code Reading Unit 412 Individual Product Code Requesting Unit 413 Data Communication Unit 414 Product Master Data Requesting Unit 415 Product Dividing Unit 416 Item weighing unit 417 Price calculating unit 418 Label code determining unit 419 Label printing unit 420 Label pasting unit 421 Packaging processing unit 422 Data input unit 423 Data output unit 424 Weighing machine DB

Claims (10)

A history search code management server that issues a history search code given to a product to search for history information and manages the issued history search code so that the history information of the product can be provided in the traceability system ,
An acquisition request receiving means for receiving a history search code acquisition request that presents a supplier code that can identify a supplier of a product for which a history search code is to be assigned;
History search code issuing means for issuing a history search code in response to the history search code acquisition request;
The supplier code presented in the history search code acquisition request is associated with the history search code related information related to the history search code issued by the history search code issuing means in response to the history search code acquisition request. A history search code management server comprising code issue history information storage means for storing code issue history information. The history search code management server according to claim 1, wherein the history search code related information is the number of history search codes issued by the history search code issuing means or the history search code itself issued by the history search code issuing means. 3. A charge amount calculation means for calculating a charge amount to be charged to the supplier as a consideration for a service provided to the supplier including a history search code issue operation based on the code issue history information. The history search code management server described. The supplier code is at least one of a producer code that can identify the producer of the product and a seller code that can identify the seller of the product. History search code management server. The acquisition request reception means receives a history search code acquisition request that presents a supplier code that can identify a supplier in a plurality of products to which a history search code is assigned,
The history search code issuing means issues a plurality of history search codes to be assigned to each of the plurality of products in response to the history search code acquisition request. Search code management server. A history search code management system that issues a history search code given to a product to search for history information and manages the issued history search code so that the history information of the product can be provided in the traceability system ,
An acquisition request execution means for making a history search code acquisition request that presents a supplier code that can identify a supplier of a product for which a history search code is given,
An acquisition request receiving means for receiving a history search code acquisition request from the acquisition request executing means via a communication network;
History search code issuing means for issuing a history search code in response to the history search code acquisition request;
The supplier code presented in the history search code acquisition request is associated with the history search code related information related to the history search code issued by the history search code issuing means in response to the history search code acquisition request. Code issue history information storage means for storing code issue history information;
A history search code receiving means for receiving the history search code issued by the history search code issuing means via a communication network;
A history search code management system comprising: a history search code printing / pasting means for printing or pasting a history search code received by the history search code receiving means on the product to be given. The history search code management system according to claim 6, wherein the history search code related information is the number of history search codes issued by the history search code issuing means or the history search code itself issued by the history search code issuing means. 8. A charge amount calculation means for calculating a charge amount to be charged to the supplier as a consideration for a service provided to the supplier including a history search code issuance operation based on the code issuance history information. The history search code management system described. The supplier code is at least one of a producer code that can identify the producer of the product and a seller code that can identify the seller of the product. History search code management system. The acquisition request reception means receives a history search code acquisition request that presents a supplier code that can identify a supplier in a plurality of products to which a history search code is assigned,
The history search code issuing means issues a plurality of history search codes to be assigned to each of the plurality of products in response to the history search code acquisition request. Search code management system.

Images