JP2008015908A - Limited-life article managing device and limited-life article management program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To manage the retaining period of each limited-life article while managing the limited-life article by an article code. <P>SOLUTION: An article time limit file, in which a saleable period of article specified by a corresponding article code is set in advance, is respectively provided to be made correspond to each article code for identifying the types of various limited-life articles. limited-life article processing data including the article code of the article to be generated for every article, sales end date and hour and sales time limit date and hour is acquired when the selling of the limited-life article is finished, the article time limit file is retrieved by an article identification code included in the limited-life article processing data, and data of saleable period set in accordance with the article identification code is acquired. An article retaining period between the sales start and the sales end of an article specified by the article identification code is calculated by each data between the sales end date and hour and the sales time limit date and hour included in the limited-life article processing data and a saleable period obtained by retrieving the article time limit file by the article identification code included in the limited-life article processing data. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a time-limited product management device that manages data related to various time-limited products, such as fresh foods, that can be sold, and a computer reading for causing a computer to function as the time-limited product management device. It relates to a possible time-limited product management program.

  In general, a food product has a deadline that allows the food manufacturer to retain the quality expected of the food product if the food product is stored in a correct manner without being opened in a container package. A certain expiration date or expiration date (or quality retention date) is displayed.

  Usually, its quality deteriorates rapidly within 5 days including the date of manufacture, and even if it is stored in the correct way in the correct state, it will be sufficiently safe as food For items that cannot be secured, such as lunch boxes, cooked bread, side dishes, meat, and fresh confectionery, an expiration date is used, which is a demarcation of whether the food is suitable for consumption or not. On the other hand, expiration dates are used for foods whose quality is less likely to deteriorate, such as hams and sausages, milk, canned foods, frozen foods, seasonings and the like. It should be noted that these display deadlines are merely “one guide” and are not absolute.

  Such a deadline is also used as reference information for the period during which the food is available for retail sale, and foods that are about to expire can be sold as a close-off product at a price lower than the normal price or without being sold. It has been discarded.

  These time-limited products can reduce the loss of disposal by grasping the so-called product retention period from the time they are manufactured until they are sold. That is, since a product with a long product residence period is more likely to be discarded, the loss of disposal can be reduced by adjusting the number of products so that the product residence period is shortened.

Conventionally, the following systems have been known as systems for managing the residence period of time-limited products. That is, a product including a bar code including an individual identifier for identifying an individual product as an individual is attached to each product, and the individual identifier and individual information regarding the individual product identified by the identifier are stored in association with each other. Provide a database. The individual information includes information on the date of manufacture and time and information on the sales deadline as information before display. Further, sales date and time information or sales date and time information or disposal date and time information is included as information after sales or disposal. Therefore, the residence period is calculated for each individual product from the sales date and time or the disposal date and time information and the manufacturing date and time information ( For example, see Patent Document 1).
Japanese Patent Application Laid-Open No. 2004-110964

  However, in the conventional system described above, in order to manage the residence period of time-limited products, an individual identifier for identifying each product as an individual is attached to each product, and the manufacturing date is associated with this individual identifier. It was necessary to have a product database that stored information on the date and time and the date and time of sale or disposal.

  For this reason, there is an inconvenience that a time-limited product must be managed as an individual rather than a classification unit based on a product identification code used in a normal JAN code, and a large-capacity product database is required, resulting in high costs. There was concern.

  The present invention has been made based on such circumstances. The purpose of the present invention is to manage time-limited products not by individual individuals but by classification units, and without requiring a large-capacity product database. It is intended to provide a time-limited product management apparatus and a time-limited product management program for causing a computer to function as the time-limited product management apparatus.

The time-limited product management device of the present invention manages data related to various time-limited products for which sales periods are determined, and corresponds to each product identification code for identifying the type of various time-limited products. A product deadline file in which the sale period of the product specified by the product identification code is set in advance, and a product identification code, a sale end date and time of the product generated for each product when the sale of the time-limited product ends. Process data acquisition means for acquiring time-limited product processing data including the date and time of sale, and a product time limit file by searching for a product time limit file included in the time-limited product processing data obtained by the processing data acquisition means The file search means for acquiring the data of the available sales period set corresponding to the code, and the time-limited product processing data obtained by the processing data acquisition means The product identification code is specified by each data of the sales end date and time and the sales expiration date and time, and the sales possible period obtained by searching the product expiration file with the product identification code included in the synchronous limited product processing data. The product residence time calculation means for calculating the product residence period from the start of sales of the product to the end of sale, and the product residence time calculated by the product residence time calculation means for each time-limited product processing data obtained by the processing data acquisition means And a dwell period management means for managing.
In the time-limited product management program according to the present invention, a computer can be preliminarily set with a period in which the product specified by the product identification code can be sold in correspondence with each product identification code for identifying various types of time-limited products. A file storage function that stores the product expiration date file, and product processing data with a time limit including the product identification code, the sales end date and the sales expiration date generated for each product at the end of sales of the time-limited product To search for the product due date file with the processing data acquisition function to be performed and the product identification code included in the time-limited product processing data obtained by this processing data acquisition function, and sellable set according to the product identification code The file search function that acquires data for the period, the sales end date and time included in the time-limited product processing data obtained by the processing data acquisition function Selling from the start of sales of the product specified by the product identification code by each data of the sales expiration date and the sales possible period obtained by searching the product expiration file with the product identification code included in the synchronous limited product processing data A product residence period calculation function for calculating the product residence period until the end, and a residence period management function for managing the product residence period calculated by the product residence period computation function for each time-limited product processing data obtained by the processing data acquisition function; Is to realize.
Note that the product residence period is calculated by, for example, an arithmetic expression “product residence period = saleable period− (sales expiration date / time−sales end date / time)”.

  According to the present invention in which such measures are taken, a time-limited product management apparatus and a computer that can reduce the cost without requiring a large-capacity product database, as long as the time-limited product is managed in a classification unit rather than individual individuals. A time-limited product management program for functioning as the time-limited product management device can be provided.

The best mode for carrying out the present invention will be described below with reference to the drawings.
In this embodiment, the time limit product management program according to the present invention is installed in a store server of a POS (Point Of Sales) system installed in a store such as a supermarket or a convenience store. Is made to function as a time-limited product management device.

  FIG. 1 shows a schematic diagram of a POS system in the present embodiment. This POS system includes a plurality of (two in the figure) POS terminals 2 each equipped with a scanner 1 for reading a barcode, a store server 3 functioning as a host machine, and various forms and the like for printing. And a printer server 5 that controls the printer 4. Each POS terminal 2, store server 3, and printer server 5 are connected via a network 6 such as a LAN (Local Area Network).

  At a store where such a POS system is constructed, barcodes are assigned to various products to be sold. In general, the barcode includes a source marking code printed on a product at the manufacturer stage and an in-store marking code marked in a store. In Japan, a code called a JAN code is mainly used. .

  In the case of a standard type source marking code consisting of 13 digits, the breakdown consists of the two digits from the left indicating the country code, the next five digits indicating the manufacturer code, and the next five digits indicating the product identification code (hereinafter referred to as the product code). The last digit represents a check digit for preventing misreading. The product code is a code of a minimum classification unit that is set differently depending on the difference in product name, retail price, and the like. The source marking code does not include price data. For this reason, a product master file in which price data is preset corresponding to the product codes of various products is provided in the store server 3. The POS terminal 2 detects a product code from the barcode read by the scanner 1, inquires the store server for price data set corresponding to the product code, and is given the barcode based on the acquired price data. Register the sales data of the selected product. Such a method is called a PLU (Price Look Up) method.

  On the other hand, in the case of the in-store marking code, there are no particular restrictions except that the two digits from the left indicate the in-store code and the last one digit indicates the check digit, and the rest can be freely set by the user. A product code is indicated by the remaining digits, and a product that does not include price data is referred to as a PLU type. A product code and price data are indicated by the remaining digits and a price inquiry to the store server 3 is not performed, which is referred to as a NON-PLU type.

  In the present embodiment, among the various products, for non-expired products such as daily necessities that are not set as sales expiration dates or expiration dates, a source consisting of a 13-digit or 8-digit JAN code, respectively. A bar code indicating a marking code or an in-store marking code is given. On the other hand, for products with time limits such as foods for which sales are possible or called expiration dates, a 13-digit JAN code (source marking code or in-store marking code) as shown in FIG. In addition, a 26-digit bar code with a time limit is added to which information including a 12-digit time limit date and time and a 1-digit check error prevention digit are added. For example, the expiration date / time indicates the expiration month MM with two digits from the left, the expiration date DD with the next two digits, and the time HH with the next two digits. The remaining six-digit information YYYYYY is, for example, a discount price when the grace period from the sale date / time to the expiration date / time of the product to which this barcode is assigned is equal to or less than a predetermined period.

  Note that the method of expressing the deadline date / time is not limited to this. For example, the elapsed number of days from January 1 may be indicated by three digits from the left, and the time may be indicated by the next two digits. Further, instead of specifying the due date from the number of days elapsed from January 1, the date may be specified by the remaining number of days until December 31. By adopting such a method, the number of digits of the remaining information can be increased to 7 digits.

  FIG. 3 is a block diagram showing a main configuration of the POS terminal 2. The POS terminal 2 includes a CPU (Central Processing Unit) 11 as a control unit body. The CPU 11 is connected to a ROM (Read Only Memory) 13, a RAM (Random Access Memory) 14, a clock unit 15, a communication interface 16, a scanner interface 17, and an I / O port via a bus line 12 such as an address bus and a data bus. 18, a keyboard controller 19, a first display controller 20, a second display controller 21, and a printer controller 22 are connected to constitute a control circuit of the POS terminal 2.

  The I / O port 18 is connected with a mode switch 23 for selecting various business modes such as “registration”, “inspection”, “settlement”, and the mode selection signal of the mode switch 23 is input. . A drawer 24 for storing cash or the like is also connected to the I / O port 18, and an opening drive signal is output from the I / O port 18 to the drawer 24 at the time of accounting or the like. It opens automatically.

  Connected to the keyboard controller 19 is a keyboard 25 on which various keys such as numeric keys, subtotal keys, deposit / cash keys, discount keys and the like are arranged. Keys corresponding to the operation keys of the keyboard 25 are connected. A signal is input. An operator display 26 for displaying information for an operator such as a cashier is connected to the first display controller 20, and the display operation of the display 26 is controlled. The second display controller 21 is connected to a customer display 27 for displaying information for the shopper, and controls the display operation of the display 27. A printer 28 for performing receipt printing or the like is connected to the printer controller 22, and the printing operation of the printer 28 is controlled.

  The clock unit 15 measures the current date and time. The communication interface 16 manages data communication with a store server or the like connected via the network 6. The scanner interface 17 takes in the barcode data read by the scanner 1.

  In the POS terminal 2 having such a configuration, when the “register” mode is selected by the mode switch 23, when the barcode is read by the scanner 1 and the barcode data is input via the scanner interface 17, the CPU 11. Performs the scanning input process shown in the flowchart of FIG.

  First, the CPU 11 determines whether it is a sales operation or a disposal operation. The business flag is stored in the RAM 14. The business flag is “0” when the business is in sales, and is “1” when the business is in the disposal. The POS terminal 2 is normally selected for sales operations when in the “registration” mode. However, when the discard key provided on the keyboard 25 is operated and input, the operation is switched to the disposal operation. Thereafter, when a key declaring the end of the disposal operation, for example, a deposit / cash key is input, the operation returns to the sales operation. The CPU 11 can determine from the state of the business flag whether the business is a sales business or a disposal business.

  If it is determined that the sales operation is in progress (YES in ST1), since the barcode of the product purchased by the customer is read by the scanner 1, the CPU 11 performs the product sales processing specifically shown in the flowchart of FIG. Is executed (ST3).

  First, it is determined whether the read barcode is a 26-digit time-limited barcode or a 13-digit standard barcode (ST11). When it is a bar code with a time limit (YES in ST11), the CPU 11 analyzes the data of the bar code with a time limit, and acquires the data of the time limit date and time incorporated in the bar code. Then, it is determined whether or not the expiration date / time has elapsed with respect to the current date / time counted by the clock unit 15 (ST12). If the expiration date has passed (YES in ST12), an expiration warning message is displayed on the operator display 26 to prompt the cashier to give a warning (ST13). Then, the merchandise sales process ends.

  On the other hand, when the expiration date / time has not elapsed (YES in ST12) and when the read barcode is a standard barcode instead of a barcode with a limitation (NO in ST11), the CPU 11 Merchandise sales data processing is performed (ST14).

  That is, when the barcode data read by the scanner 1 is a PLU type that does not include price data, the store server 3 is inquired about the price data with the product code acquired from the barcode data. Then, the sales price is calculated by multiplying the price data returned from the store server 3 by the number of sales points. It should be noted that the sales score is the numerical value when a numerical value is entered with the numeric key immediately before the barcode is input, and is “1” when the numerical value is not entered. The CPU 11 registers the product code acquired from the barcode data, the sales points, and the sales amount in the sales memory area of the RAM 14.

  On the other hand, if the barcode data read by the scanner 1 is of the NON-PLU type including price data, the sales amount is calculated by multiplying the price data acquired from this barcode data by the number of sales points. Then, the merchandise code acquired from the barcode data, the sales points and the sales amount are registered in the sales memory area of the RAM 14.

  When the merchandise sales data processing is completed, the CPU 11 creates transaction data relating to the sales processed merchandise, so-called merchandise sales transaction data. Then, the merchandise sales transaction data is stored in the transaction buffer of the RAM 14 (ST15).

  The main data structure of the merchandise sales transaction data is shown in the schematic diagram of FIG. As shown in the figure, the item sales transaction data includes item data such as a item code, a category, a sales amount, a sales point, a sales date and a deadline date. Here, the item “product code” is obtained from the barcode data. The item “classification” is used to identify whether or not the transaction data is product sales data. In this embodiment, the item “classification” is “1” in the case of product sales transaction data. The items “sales amount” and “sales number” are values registered in the product sales data processing. The item “sales date and time” is the current date YYYYMMDD and time HH which are timed by the clock unit 15. The item “expiration date / time” is “0” (not set) in the case of a product with no expiration date, and in the case of a product with a expiration date, the date YYYYMMDD of the expiration date / time included in the barcode with the expiration date and the time HH. It is. In addition, when the time limit date and time included in the bar code with a time limit does not include the year YYYY, the current year YYYY timed by the clock unit 15 is added.

  In the scanning input process of FIG. 4, when it is determined that the business is not a sales business but a disposal business (YES in ST 2), the barcode of the product to be discarded from the sales floor is read by the scanner 1. The product discarding process specifically shown in the flowchart of FIG. 7 is executed (ST4).

  First, it is determined whether the read barcode is a 26-digit time-limited barcode or a 13-digit standard barcode (ST21). When it is a bar code with a time limit (YES in ST21), the CPU 11 analyzes the data of the bar code with a time limit, and acquires data of the time limit date and time added to the bar code. Then, it is determined whether or not the expiration date / time has elapsed with respect to the current date / time counted by the clock unit 15 (ST22). If the expiration date / time has not elapsed (YES in ST22), a warning message indicating that the expiration date has not expired is displayed on the operator display 26 to prompt the cashier to give a warning (ST23). And this merchandise disposal processing is ended.

  On the other hand, when the expiration date / time has not elapsed (YES in ST22) and when the read barcode is a standard barcode instead of a barcode with a limitation (NO in ST21), the CPU 11 Product disposal data processing is performed (ST24).

  That is, when the barcode data read by the scanner 1 is a PLU type that does not include price data, the store server 3 is inquired about the price data with the product code acquired from the barcode data. Then, the discard amount is calculated by multiplying the price data returned from the store server 3 by the discard point. Note that the discard score is set to a numerical value when a numeric value is entered with a numeric key immediately before the barcode is input, and is set to “1” when the numeric value is not entered. The CPU 11 registers the product code acquired from the barcode data, the discard point and the discard amount in the discard memory area of the RAM 14.

  On the other hand, if the barcode data read by the scanner 1 is a NON-PLU type including price data, the price data obtained from this barcode data is multiplied by the number of discard points to calculate the discard amount. Then, the product code acquired from the barcode data, the number of discarded points, and the discarded amount are registered in the discarded memory area of the RAM 14.

  When the merchandise disposal data processing is completed, the CPU 11 creates transaction data relating to the discarded merchandise, so-called merchandise disposal transaction data. Then, the merchandise discard transaction data is stored in the transaction buffer of the RAM 14 (ST25).

  The main data structure of the product disposal transaction data is shown in the schematic diagram of FIG. As shown in the figure, the product disposal transaction data includes data for each item of product code, category, disposal amount, number of disposal points, disposal date / time, and expiration date / time. Here, the item “product code” is obtained from the barcode data. The item “classification” is used to identify whether or not the transaction data is merchandise discard data. In this embodiment, the item “classification” is “2” in the case of merchandise discard transaction data. The items “discarded amount” and “discarded points” are values registered in the merchandise discard data processing. The item “discard date / time” is the current date YYYYMMDD and time HH timed by the clock unit 15. The item “expiration date / time” is “0” (not set) in the case of a product with no expiration date, and in the case of a product with a expiration date, the date YYYYMMDD of the expiration date / time included in the barcode with the expiration date and the time HH. It is. In addition, when the time limit date and time included in the bar code with a time limit does not include the year YYYY, the current year YYYY timed by the clock unit 15 is added.

  The merchandise sales transaction data and the merchandise disposal transaction data stored in the transaction buffer of each POS terminal 2 are transferred to the store server 3 via the network 6 as appropriate. In the store server 3, sales data and disposal data are aggregated for each product or for each time period based on the product sales transaction data and the product disposal transaction data collected from each POS terminal 2. Then, a sales analysis report showing these total results is printed out from the printer 4.

  In addition, the store server 3 has a time-limited product management function for managing various data related to time-limited products such as foods for which a sellable time limit called a consumption time limit or a best before date is set. This function is realized by a time-limited product management program installed in advance.

  Note that the term-limited product management program may be downloaded from the network to the store server 3 or may be installed in the store server 3 with similar functions stored in the recording medium. The recording medium may be in any form as long as it can store a program such as a CD-ROM and can be read by the store server 3. Further, the function obtained by installing or downloading in advance may be realized in cooperation with an OS (operating system) in the store server 3 or the like.

  FIG. 9 is a schematic diagram for explaining the term-limited product management function of the store server 3. In the figure, a product sales transaction file 31 is a data file for accumulating and storing product sales transaction data collected from each POS terminal 2. The product discard transaction file 32 is a data file for storing and storing product discard transaction data collected from each POS terminal 2.

  For example, at a predetermined time on every business day, the store server 3 refers to the product sales transaction file 31 and the product disposal transaction file 32 and performs a time-limited product transaction extraction process 33 specifically shown in the flowchart of FIG. Start.

  First, the store server 3 sets a transaction data extraction period in ST31. For example, the extraction period is set from a predetermined time on the previous day to a predetermined time on the current day. Next, as ST32, the record counter n is once reset to “0”. Thereafter, the record counter n is incremented by “1” as ST33. In ST34, the nth record (product sales transaction data) is read from the product sales transaction file 31 (n is the value of the record counter n).

  Here, if the nth record is stored in the product sales transaction file 31 and can be read (YES in ST35), the store server 3 determines the product sales transaction that is the nth record in ST36. It is determined whether the sales date of the data is within the extraction period. If it is outside the extraction period (NO in ST36), the process returns to ST33, the record counter n is further incremented by “1”, and the nth record is read from the merchandise sales transaction file 31.

  On the other hand, if the sales date and time of the product sales transaction data read from the product sales transaction file 31 is within the extraction period (YES in ST36), the store server 3 sets an expiration date and time in this product sales transaction data as ST37. It is judged whether it is done. If the data of the item “expiration date / time” is “0”, the expiration date / time is not set (NO in ST37), and the process returns to ST33. Then, the record counter n is further incremented by “1”, and the nth record is read from the merchandise sales transaction file 31.

  On the other hand, when the data of the item “expiration date / time” is data YYYYMMDDDHH indicating the date and time, since the expiration date / time is set (YES in ST37), the store server 3 sets this data as ST38. The product sales transaction data is stored in the time-limited product transaction file 34 (process data acquisition means). Thereafter, the process returns to ST33, and the record counter n is further incremented by "1", and the nth record is read from the merchandise sales transaction file 31.

  In this way, the store server 3 reads the merchandise sales transaction data from the merchandise sales transaction file 31 in order. If data with a sales date / time within the extraction period and data with a time limit set is detected, this data is sequentially added to the time-limited product transaction file 34.

  If the nth record can no longer be read from the merchandise sales transaction file 31 (NO in ST35), the store server 3 executes the same processing on the merchandise discard transaction file 32. That is, the record counter n is reset to “0” again in ST39. Thereafter, this record counter n is incremented by “1” as ST40. In ST41, the nth record (product discard transaction data) is read from the product discard transaction file 32 (n is the value of the record counter n).

  Here, if the nth record is stored in the product discard transaction file 32 and can be read (YES in ST42), the store server 3 determines the product discard transaction that is the nth record as ST43. It is determined whether the data discard date is within the extraction period. If it is outside the extraction period (NO in ST43), the process returns to ST40, the record counter n is further incremented by "1", and the nth record is read from the merchandise discard transaction file 32.

  On the other hand, if the discard date / time of the merchandise discard transaction data read from the merchandise discard transaction file 32 is within the extraction period (YES in ST43), the store server 3 sets an expiration date / time in this merchandise discard transaction data as ST44. It is judged whether it is done. If the data of the item “expiration date / time” is “0”, the expiration date / time is not set (NO in ST44), and the process returns to ST40. Then, the record counter n is further incremented by “1”, and the nth record is read from the merchandise sales transaction file 31.

  On the other hand, when the data of the item “expiration date / time” is data YYYYMMDDDHH indicating the date and time, since the expiration date / time is set (YES in ST44), the store server 3 sets this data as ST45. The product disposal transaction data is stored in the time-limited product transaction file 34 (process data acquisition means). Thereafter, the processing returns to ST40, the record counter n is further incremented by “1”, and the nth record is read from the merchandise discard transaction file 32.

  In this way, the store server 3 reads the product discard transaction data from the product discard transaction file 32 in order. Then, if data whose discard date / time is within the extraction period and data whose expiration date / time is set is detected, this data is sequentially added to the time-limited product transaction file 34.

  If the nth record can no longer be read from the merchandise discard transaction file 32 (NO in ST42), the store server 3 ends this time-limited merchandise transaction extraction process.

  Thus, as shown in FIG. 11, in the time-limited product transaction file 34, the transaction data extracted from the product sales transaction file 31 and the product disposal transaction file 32, that is, the sales date / time or the disposal date / time is data within the extraction period and The transaction data with time limit consisting of the items of the product code, category, sales or disposal amount, sales or discard points, sales or disposal date and time, and expiration date and time of the transaction data for which the expiration date and time has been set is stored and saved.

  Note that the sales or disposal date and time is the date and time when the corresponding product is sold or discarded, and the sale is terminated by the sale or disposal.

  Returning to FIG. The product expiration date file 35 corresponds to each product code for identifying various types of time-limited products, and is a period of time required for the product specified by the product code to become unsaleable, so-called sale possible It is a data file in which data indicating a period is preset and stored. An example of data set in the product expiration date file 35 is shown in FIG. In FIG. 12, the unit of the available sales period is time.

  The store server 9 refers to the time-limited product transaction file 34 and the product time-limit file 35, for example, when the time-limited product transaction extraction process ends on a predetermined day of the month, for example. The attached product record transaction creation process 36 is executed.

  First, the store server 3 once resets the record counter n to “0” in ST51. Next, in ST52, this record counter n is incremented by "1". In ST53, the n-th record (time-limited product transaction data) is read from the time-limited product transaction file 34 (n is the value of the record counter n).

  Here, if the n-th record is stored in the time-limited product transaction file 34 and can be read (YES in ST54), the store server 3 sets the time-limited date as the n-th record in ST55. The product code, product end date / time (sales / discard date / time), and expiration date / time are acquired from the product transaction data. Then, in ST56, the product expiration date file 35 is searched with the product code acquired from this time-limited product transaction data, and the data of the saleable period set corresponding to the product code is acquired (file search means). .

  Next, the store server 3 calculates the following equation (1) from each data of the sales end date / time and the date / time acquired from the time-limited product transaction data as ST57 and the sales possible period acquired from the product time limit file 35. Then, the product retention period from the sales start to the sales end of the product specified by the product code of the time-limited product transaction data is calculated (retention period calculation means).

Product retention period = available period-(expiration date and time-sale end date and time) (1)
Next, the store server 3 calculates the following equation (2) from each data of the product residence period calculated as ST58 and the sales end date and time included in the time-limited product transaction data, and the time-limited product The manufacturing date and time of the product specified by the product code of the transaction data is calculated (manufacturing date and time calculating means).

Production date and time = End date and time of sale-Product residence time (2)
After that, the store server 3 adds each data of the product residence time calculated in the process of ST57 and the production date and time calculated in the process of ST58 to the time-limited product transaction data read from the time-limited product transaction file 34 in ST59. In association, create product transaction data with time limit. Then, as ST60, this time-limited product result transaction data is additionally stored in the time-limited product result file 37 (residence period management means).

  Thereafter, the store server 3 returns to ST52 and further increments the record counter n by “1”. And each process shown by ST53-ST60 is repeatedly performed. That is, the store server 3 reads time-limited product transaction data in order from the time-limited product transaction file 34. Each time, the data of the sales possible period set in the product deadline file 35 corresponding to the product code in the product transaction data with time limit is acquired, and the sales in the product transaction data with the limited sales period and the synchronization limited product transaction data are acquired. The product retention period and production date / time of the product are calculated from the end date / time data and the expiration date / time data, and the processing for creating and storing the time-limited product result transaction data is repeated.

  If the nth record can no longer be read from the time-limited product transaction file 34 (NO in ST54), the store server 3 clears each data in the time-limited product transaction file 34 in ST61, and this time limit. The attached product record transaction creation process is terminated.

  Thus, as shown in FIG. 14, the time-limited product result file 37 includes the product code, category, sales or discard amount, sales or discard score of the time-limited product transaction data read from the time-limited product transaction file 34, The time-limited product result transaction data including the items of the sales end date / time (sales or disposal date / time) and the expiration date / time, the product residence period and the manufacturing date / time is accumulated and stored.

  Returning to FIG. The store server 3 can execute a time-limited product result analysis process 38 for analyzing the time-limited product result transaction data accumulated and stored in the time-limited product result file 37. By executing this analysis process 38, for example, as shown in FIG. 15, the cumulative number of sales points and disposal points, the average residence period and the shortest residence period are listed for each time-limited product and for each production date and time. It is possible to create a time-limited product result analysis report 39 for each production date and print it out by the printer 4.

  As described above, in the present embodiment, a time-limited bar code including a time limit date and time, together with the product code, for a time-limited product such as a food expiry date or a expiration date set for sale, which is set for sale, is set in this embodiment. Is granted.

  When the customer purchases this time-limited product, the POS terminal 2 reads and inputs the time-limited barcode attached to the time-limited product by the scanner 1. Thereby, product sales transaction data for this time-limited product is created. In this transaction data, in addition to the date and time data on which this time-limited product is sold, data on the date and time set in the time-limited barcode attached to this time-limited product is incorporated.

  Also, when the clerk discards the time-limited product, the POS terminal 2 reads and inputs the time-limited barcode attached to the time-limited product by the scanner 1. Thereby, the product disposal transaction data for this time-limited product is created. In this transaction data, in addition to the date and time data when the time-limited product is discarded, data on the date and time set in the time-limited barcode attached to the time-limited product is incorporated.

  In the store server 3, merchandise sales transaction data and merchandise disposal transaction data created by each POS terminal 2 are collected in a timely manner. The product sales transaction data is stored in the product sales transaction file 31, and the product disposal transaction data is stored in the product disposal transaction file 32.

  Further, in the store server 3, for example, when a predetermined time of every business day comes, a time-limited product transaction extraction process 33 is executed. As a result, data whose sales date / time is within the extraction period and whose expiration date / time has been set is extracted from the product sales transaction file 31 and stored in the time-limited product transaction file 34. Further, data whose discard date / time is within the extraction period and whose expiration date / time is set is extracted from the product discard transaction file 32 and stored in the term-limited product transaction file 34.

  Further, in the store server 3, a time-limited product result transaction creation process 36 is executed after the time-limited product transaction extraction process ends on a predetermined day of the month. As a result, the product retention period and the production date and time are derived for each time-limited product transaction data accumulated and stored in the time-limited product transaction file 34 between the end of the previous time-limited product result transaction creation process and the present time. The

  The product residence period is calculated from each data of the sales end date and time and the date and time in the time-limited product transaction data, and the sales possible period of the product set in the product time limit file 35 in advance. The production date and time is calculated from each data of the calculated product residence period and the sales end date and time in the time-limited product transaction data.

  Then, for each time-limited product transaction data, time-limited product result transaction data in which the calculated product residence period and the respective production date / time data are associated with each other is created and stored in the time-limited product result file 37.

  For example, it is assumed that the data shown in FIG. 11 is stored in the product transaction file with a time limit 34 and the data shown in FIG. 12 is set in the product time limit file 35. In this case, for the product sales transaction data that is the first record of the time-limited product transaction file 34, the sales end date and time (sales date and time) is 13:00 on July 1, 2006, and the time limit date is 20:00 on the same day. Since the marketable period is 12 hours, the product residence period is calculated to be 5 hours according to the equation (1). Further, according to the equation (2), the manufacturing date is calculated to be 8:00 on the same day.

  Further, for the product disposal transaction data, which is the seventh record from the top of the product transaction file with a time limit 34, the sales end date / time (discard date / time) and the time limit date / time are both 10:00 on July 1, 2006. Since the sales possible period is 12 hours, the product residence period is calculated to be 12 hours according to the equation (1). Further, according to the formula (2), the manufacturing date is calculated to be 8:00 on the same day.

  The same processing is performed for the other records of the term-limited product transaction file 34, so that the respective product retention periods and production dates are calculated as values corresponding to the data example of the term-limited product result file shown in FIG.

  Thereafter, when the time-limited product result analysis process 38 is executed in the store server 3, each time-limited product is manufactured based on each time-limited product result transaction data stored in the time-limited product result file 37. For each date and time, a time-limited product result analysis report 39 for each production date and time is created and issued, listing the accumulated sales points and disposal points, and the average residence time and the shortest residence time. By confirming this report by the store manager or the like, it is possible to grasp the period from the manufacture of each time-limited product to the sale, the so-called product retention period and the manufacturing date and time. By using these pieces of information, it is possible to reduce the disposal loss of time-limited products.

  By the way, in the present embodiment, time-limited products are managed in a classification unit called a product code for identifying the type of the product as in the case of products with no time limit. The product retention period and the manufacturing date and time can be calculated for each time-limited product simply by providing the product time-limit file 35 that stores the sales possible period of the time-limited product in units of the product code. Therefore, as in the conventional system, an individual identifier for identifying an individual product as an individual is attached to each product, or associated with this individual identifier, the date of manufacture and time, the date of sale or disposal In addition, since it is not necessary to provide a product database that stores time and minute information, it is possible to reduce the burden of management and reduce costs.

  The present invention is not limited to the above-described embodiment as it is, and can be embodied by modifying the constituent elements without departing from the scope of the invention in the implementation stage.

  For example, the time-limited product transaction processing procedure is not limited to that shown in FIG. 10, but the product discard transaction file 32 is searched first, the product sales transaction file 31 is searched later, and the time-limited product transaction is searched. Data may be extracted.

  Further, the merchandise sales transaction file 31 and the merchandise disposal transaction file 32 may be divided into a common transaction file.

  Further, the execution timing of the time-limited product transaction extraction process 33 and the time-limited product result transaction creation process 36 is not limited to that of the above embodiment, and may be executed when the user thinks it is necessary. That's fine.

  Moreover, in the said embodiment, although the function as a time limit goods management apparatus of this invention was given to the store server 3, the computer which gives this function is not limited to the store server 3, For example, each The headquarters server installed in the headquarters which manages the chain store may be used.

  In addition, various inventions can be formed by appropriately combining a plurality of constituent elements disclosed in the embodiment. For example, some components may be deleted from all the components shown in the embodiment. Furthermore, the constituent elements over different embodiments may be combined.

1 is a schematic diagram of a POS system according to an embodiment of the present invention. The schematic diagram which shows the data structure of the barcode with a time limit used in the embodiment. The block diagram which shows the principal part structure of the POS terminal in the embodiment. The flowchart which shows the outline of the procedure of the scanning input process which CPU of the POS terminal performs. The flowchart which shows the content of the goods sales process in FIG. 4 concretely. The schematic diagram which shows the main data structures of the merchandise sales transaction data produced | generated by the merchandise sales process shown in FIG. The flowchart which shows the content of the merchandise disposal process in FIG. 4 concretely. The schematic diagram which shows the main data structures of the merchandise disposal transaction data produced | generated by the merchandise disposal processing shown in FIG. The schematic diagram for demonstrating the goods management function with a time limit which a store server has in the embodiment. 10 is a flowchart specifically showing the content of a time-limited product transaction extraction process in FIG. The schematic diagram which shows an example of the data preserve | saved in the time limit goods transaction file of FIG. The schematic diagram which shows an example of the data preserve | saved in the product term file of FIG. 10 is a flowchart specifically showing the content of a time-limited product result transaction creation process in FIG. 9. The schematic diagram which shows an example of the data preserve | saved in the time limit goods performance file of FIG. The schematic diagram which shows an example of the term-limited goods performance analysis report of FIG.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 1 ... Scanner, 2 ... POS terminal, 3 ... Store server, 4 ... Printer, 5 ... Printer server, 31 ... Merchandise sales transaction file, 32 ... Merchandise disposal transaction file, 33 ... Deadline product transaction extraction process, 34 ... Deadline Product transaction file, 35 ... Product time limit file, 36 ... Time-limited product result transaction creation process, 37 ... Time-limited product result file, 38 ... Time-limited product result analysis process, 39 ... Time-limited product result analysis report.

Claims (4)

In a time-limited product management device that manages data related to various time-limited products for which a period that can be sold is determined,
In correspondence with each product identification code for identifying the types of the various time-limited products, a product time limit file in which the sale period of the product specified by the product identification code is set in advance,
Processing data acquisition means for acquiring time-limited product processing data including a product identification code, a sales end date / time and a sales time limit date / time generated for each product at the end of sales of the time-limited product;
The product expiration date file is searched with the product identification code included in the time-limited product processing data obtained by the processing data acquisition means, and the data of the saleable period set corresponding to the product identification code is acquired. A file search means;
Obtained by searching the product due date file with the sale end date and time contained in the time-limited product processing data obtained by the processing data acquisition means and the product identification code contained in the synchronous limited product processing data A residence period calculating means for calculating a product residence period from the sale start to the sale end of the product specified by the product identification code based on each data of the sale possible period;
A residence period management unit that manages the product residence period calculated by the residence period calculation unit for each time-limited product processing data obtained by the processing data acquisition unit;
A product management apparatus with a time limit, comprising: Included in the synchronous limited product processing data based on each data of the product residence time calculated by the residence time calculation means and the sales end date / time included in the time-limited product processing data used for the calculation of the product residence time Further comprising manufacturing date / time calculating means for calculating the manufacturing date / time of the product specified by the product identification code,
The residence period management means manages the product residence period calculated by the residence period calculation means for each time-limited product processing data obtained by the processing data acquisition means in association with the production date and time calculated by the production date and time calculation means. The time-limited product management apparatus according to claim 1, wherein On the computer,
A file storage function for storing a product time limit file in which the sale period of the product specified by the product identification code corresponding to each product identification code for identifying the type of the various time-limited products is preset;
A processing data acquisition function for acquiring time-limited product processing data including a product identification code of the product, a sales end date and time, and a sales time and date generated for each product at the end of sales of the time-limited product;
The product expiration date file is searched with the product identification code included in the time-limited product processing data obtained by the processing data acquisition function, and the data of the saleable period set corresponding to the product identification code is acquired. File search function,
Obtained by searching the product due date file with the end date and time of sale included in the product processing data with time limit obtained by the processing data acquisition function and the product identification code included in the product processing data with synchronization limitation A residence period calculation function for calculating a product residence period from the start of sales to the end of sale of the product specified by the product identification code based on each data with the available sales period;
A residence period management function for managing the product residence period calculated by the residence period calculation function for each time-limited product processing data obtained by the processing data acquisition function;
A product management program with a time limit for realizing In the computer,
Included in the synchronous limited product processing data based on each data of the product residence period calculated by the residence period calculation function and the sales end date / time included in the time-limited product processing data used for the calculation of the product residence period In addition to realizing a manufacturing date calculation function that calculates the manufacturing date of the product specified by the product identification code,
The residence period management function manages the product residence period calculated by the residence period calculation function for each time-limited product processing data obtained by the processing data acquisition function in association with the production date and time calculated by the manufacturing date and time calculation function. The time-limited product management program according to claim 3, wherein

Images