JPH07320158A - Commodity sale price management device - Google Patents

Abstract

PURPOSE:To perform the processing adapted to the sale condition by extracting commodities, whose actual result values of sales are smaller than a sales target reference value for the number of days elapsed in sales, as discount object commodities to reduce the artificial burden to discount processing. CONSTITUTION:The number of days elapsed from the initial date in reckoning to the present date counted by a clock part 24 is calculated as the number of days elapsed in sales. Achieving rate table data on a RAM 23 is referred to determine a reference achieving rate for the calculated number of days elapsed in sales. A sales achieving rate is calculated in accordance with the supply quantity and the sold quantity of a commodity record. Thereafter, this sales achieving rate is compared with the reference achieving rate. Only when the sales achieving rate is lower than the reference achieving rate, the pertinent commodity is extracted as a discount object commodity, and the counting item code and (exclusion flag) = OFF of the pertinent commodity are registered in a discount commodity extraction file correspondingly to the pertinent extraction number.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a commodity selling price management device which stores and manages selling prices of respective commodities, and outputs corresponding selling prices when a selling price inquiry of a selling product is made.

[0002]

2. Description of the Related Art POS for registering sales data for multiple products
(Point-of-sale information management) A POS in which a terminal and a store processor composed of a host computer are connected via a communication line, and product sales data registration processing at each POS terminal is centrally managed by the store processor.
The system generally includes a product master file that stores product information such as a selling price and a product name corresponding to a unique product code assigned to each product in the store processor.

Upon receiving the product code inquiry message from each POS terminal, the store processor retrieves the product master file and reads the product information such as the selling price and product name corresponding to the product code inquired. , Responds to the POS terminal that made the inquiry.

On the other hand, when the product code of the customer-purchased product is input to each POS terminal by operating the keyboard or scanner, an inquiry message of the product code is created and transmitted to the store processor, and the product information is sent from the store processor. Upon receiving the response, the product sales data is registered based on the product information.

Here, the store processor of the POS system stores and manages the selling price of each product, and functions as a product selling price management device which outputs the corresponding selling price when the selling price of the selling product is inquired.

By the way, some products, such as clothing, have a limited sales period. For example, summer clothing will start selling around May and end at the latest in August. Then, when the sale ends, the unsold products have to be disposed of and are recorded as a loss.

Therefore, in order to reduce such a loss as much as possible, the store manager analyzes the sales situation of the product within a few weeks after the start of the sales, and lowers the price of the product with the poor sales to increase the customer's willingness to purchase. Was doing.

[0008]

[Problems to be Solved by the Invention] However, conventionally, the store manager or the like analyzes the sales situation of each product, selects the product with poor sales and processes the price reduction, so that the product with poor sales can be determined. It was hard to find and the human burden was great. In addition, since the person in charge was responsible for determining whether sales were good or bad, the products with good sales could be reduced in price to reduce profits, or the products with poor sales could not be reduced in price, resulting in unsold items. was there.

Therefore, the present invention intends to provide a commodity price control device which can reduce the human burden on the price reduction processing and at the same time enable highly reliable price reduction processing consistent with the sales situation to increase the profit. To do.

[0010]

The present invention includes a product file in which selling price information is stored in correspondence with a unique product code attached to each product, and corresponds to a selling price inquiry of a selling product. In a product selling price management device that outputs a selling price, a sales performance value managing means for storing and managing a sales performance value for each product, and a process of calculating the elapsed days from the predetermined calculation date to the present as the sales elapsed days for each product The number of days calculation means, the reference value storage means for presetting and storing the sales target reference value for the elapsed sales days, and the sales calculated by the elapsed sales day calculation means with reference to the stored contents of the reference value storage means for each product The sales target standard value for the number of days elapsed is determined, and the product whose sales actual value managed by the sales actual value management means is smaller than this standard value is extracted as the target product for the discount. It is obtained by a product extraction means.

In addition to the above-mentioned structure, the present invention further comprises an automatic price reduction for changing the selling price information stored in the product file of the product extracted as the price reduction target product by the price reduction target product extraction means to the reduced price. Means are provided.

It should be noted that the elapsed days calculating means may compare the first day of the sales period set for each product with the sales start date of the corresponding product, and calculate the elapsed sales days with the later date as the start date. desirable.

[0013]

According to the present invention having such a structure, the sales record value managing means stores and manages the sales record value for each product. Further, the reference value storage means presets and stores the sales target reference value for the number of days elapsed from the sale.

However, when the elapsed days calculation means calculates the elapsed days from the predetermined calculation date to the present as the sales elapsed days for each product, the stored contents by the reference value storage means are referred to for each product. A sales target reference value for the elapsed sales days is determined, and a product having a sales actual value smaller than this reference value is extracted as a reduction target product.

[0015]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment in which the product selling price management device of the present invention is incorporated into a store processor of a POS system in a clothing store will be described below with reference to the drawings.

FIG. 1 is a schematic diagram of a POS system in this embodiment, in which a plurality of P's for registering product sales data are registered.
An OS terminal 1 and a store processor 2 that centrally manages product sales data registration processing in each POS terminal 1 are connected in a closed loop by a communication line 3 to construct a POS system.

Each POS terminal is equipped with various input / output devices such as a keyboard, a display, a receipt / journal printer, a bar code scanner, a drawer, etc., and the product code of the customer's purchase product is input through the keyboard or the bar code scanner. Then, the inquiry message of the product code is created and transmitted to the store processor 2, and when the response of the product information such as the selling price and the product name is received from the store processor 2, the product sales data is obtained based on the product information. Perform the registration process. That is, the selling price is calculated by multiplying the selling price by the selling point, and the selling price and the selling point are registered in the storage unit together with the product code. Further, the product name, the sales amount, etc. are displayed on the display, and the product code, the product name, the selling price, the number of sales, the sales amount, etc. are printed on the receipt paper and the journal paper by the printer.

As shown in FIG. 2, the store processor 2 is equipped with a CPU (central processing unit) 21 as a main control unit, and a ROM (Read Only Memory) as a main storage unit controlled by the CPU 21. 22 and RA
An M (random access memory) 23 is installed.

The ROM 22 stores fixed data such as program data for the CPU 21 to execute various tasks. In the RAM 23, the CP
Various memory areas for temporarily storing variable data generated when the U21 executes various tasks are formed.

The store processor 2 also has a clock unit 24 for measuring the current date and time, and a communication controller 25 for controlling data transmission / reception with each POS terminal 1 via the communication line 3. A keyboard controller 26a for fetching a key signal from the keyboard 26, a display controller 27a for controlling driving of the display 27,
Printer controller 2 for controlling driving of the printer 28
8a, an HDD controller 29a for controlling the drive of the HDD (hard disk driver) 29, and the like are mounted.

The CPU 21, the ROM 22,
RAM 23, clock unit 24 and controllers 25, 26
The a, 27a, 28a and 29a are connected by bus lines such as an address bus and a data bus.

Incidentally, the keyboard 26 is a general-purpose one provided with numeric keys, character keys, execution keys, print keys, cursor keys, etc., and the display 27 is a liquid crystal display, CRT display, etc. Functions as an input device for workstations. In addition, the printer 28
Is used for printing various slips and lists.

In the HDD 29, the product master file 30 and the season master file 4 are stored as shown in FIG.
0, discounted product extraction file 50, digestibility setting file 6
0, various data files of the price range setting file 70 are formed.

FIG. 3 is a diagram showing a main structure and data example of a record registered in the product master file 30. In the product master file 30, a unique product code attached to each product is shown. Classification code 32, season code 33, product name data 34, initial input date data 35, initial selling price data 36,
Current selling price data 37, price range code 38, price reduction data 39, input quantity data 310, sales quantity data 311
Etc. are registered in advance.

Here, the classification code 32 is a code assigned to each department that classifies each product. By the way, in the case of clothing, "ladies dress", "ladies blouse",
It is classified into categories such as "women's skirt", "men's slacks", and "men's jacket".

The season code 33 is a code assigned to each sales period of the product. By the way,
As for the sale period of clothing, in addition to about three months of "Spring", "Summer", "Autumn", "Winter", "Early Spring", "Late Spring", "Early Summer", "Midsummer"
There are 1 to 2 months such as "late summer", "early autumn", "early winter" and "middle winter", and about 6 months unit such as "spring and summer""autumn and winter".

The initial input date data 35 is data indicating the date when the sale of the product is started, and the selling price at this time becomes the initial selling price data 36. Further, the current selling price data 37 is the selling price of the corresponding product at the present time, and the POS terminal 1
The current selling price data 37 is responded to as a selling price in response to the inquiry about the product code from.

The price range code 38 is a code assigned to each of a plurality of price ranges preset in the price range setting file 70 described later, and is a price range in which the initial selling price and the initial value of the corresponding product match. Code is set. Then, the number of times the price has been reduced from the initial selling price based on the corresponding price band becomes the price reduction data 39.

The input quantity data 310 is a cumulative value of the number of products arranged in the sales floor, and is added and updated every time the input quantity of the corresponding product is input from the keyboard 26. The sales quantity data 311 is a cumulative value of the number of sold products, and is added and updated each time the product sales data (score, amount of money, etc.) registered in each POS terminal 1 is collected. here,
The product master file 30 functions as a sales record value management unit that stores and manages a sales record value for each product.

FIG. 4 is a diagram showing a main structure and data example of records registered in the season master file 40. In the season master file 40, the start date of the corresponding sales period is classified according to the season code 33. The date data 41 shown and the date data 42 showing the end date are registered in advance.

FIG. 5 is a diagram showing a main configuration and data example of a record registered in the discounted product extraction file 50. In this discounted product extraction file 50, a series of extraction numbers corresponding to the number of records stored. The single item code 31 of the product selected as the price reduction target product corresponding to 51 and the exclusion flag (exclude = 1, not exclude = 0) 52 that specifies whether or not to exclude the price reduction of the product are registered. To be done.

FIG. 6 is a diagram showing a main structure and data example of records registered in the digestion rate setting table 60. In the digestion rate setting table 60, digestion is performed for each season code 33 and classification code 32. The rate table data 61 is registered in advance.

As shown in the figure, the digestion rate table data 61 belongs to the corresponding classification code 32 in correspondence with the number of days elapsed from the predetermined start date in the sales period of the corresponding season code 33, so-called elapsed sales number 61a. It is a table in which a target reference value of the sales digestion rate of the product, a so-called reference digestion rate 61b is preset.

Here, the sales digestion rate is defined as the ratio of the sales quantity to the input quantity of the corresponding product. Further, the reference consumption rate 61b is a threshold value for determining whether or not the product is a reduction target product, and by the way, if the sales consumption rate of the product with respect to the elapsed sales days is smaller than the reference consumption rate 61b, the value is a value. It is judged as a target product. Here, the digestion rate setting table 60 functions as a reference value storage unit that presets and stores the sales target reference value for the elapsed sales days.

FIG. 7 is a diagram showing an essential structure and data example of a record registered in the price range setting file 70.
In the price range setting table 70, price range table data 71 for each season code 33 and classification code 32 is provided.
Is registered in advance.

As shown in the figure, the price range table data 71 is a table in which the price range of the selling price after the price reduction is set with respect to the number of price reductions 39 according to the initial selling price of the product belonging to the corresponding season code 33 and classification code 32. A unique price range code 38 is attached to each price range.

Therefore, the CPU 21 is programmed so as to be able to execute, in particular, the extraction work of the discount target product, the maintenance work of the discount product extraction file 50, and the discount execution work.

FIG. 8 is a flow chart showing the processing procedure of the price reduction target product extraction work. That is, when starting the price reduction target product extraction operation, the CPU 21 first receives an input of the condition (sales period and department) of the product to be extracted as the price reduction target product in ST (step) 1. And the keyboard 26
When the season code 33 corresponding to the sales period of the product and the classification code 32 corresponding to the department are input by the key input of, the season code 33 and the classification code 32 are temporarily stored in the RAM 23.

Next, as ST2, this season code 3
The digestion rate setting file 60 is searched by using 3 and the classification code 32 as a retrieval key, and the digestion rate table data 61 corresponding to the retrieval key is read and temporarily stored in the RAM 23.

Further, as ST3, the season code 3 is set.
3 and the classification code 32 are used as search keys to search the product master file 30, and all product records in which the search key matches the season code 33 and the classification code 32 are read out and temporarily stored in the RAM 23.

Further, in ST4, the season master file 40 is searched using the season code 33 as a search key, and the start date data 41 corresponding to the search key is read out and temporarily stored in the RAM 23.

Thereafter, in ST5, the first product record is selected from the product records on the RAM 23. Then, first, at ST6, the initial insertion date data 35 of the product record is compared with the start date data 41 on the RAM 23, and the later date is set as the start date as ST7a or ST7b. If the sales period is set at the year change, such as from December 1st to February 29th, the date of January or February will be later than the date of December. .

Next, in ST8, the number of days elapsed from the start date to the current date measured by the clock unit 24 is calculated as the number of sales days 61a by the following equation (1) (elapsed days calculating means).

Elapsed sales days = (current date−counting date) +1 [days] (1) Then, as ST9, the digestion rate table data 61 on the RAM 23 is referred to, and the reference consumption is calculated for the calculated elapsed sales days 61a. Determine the rate 61b.

Next, at ST10, the sales consumption rate is calculated from the input quantity 310 and the sales quantity 311 of the product record by the following equation (2).

Sales digestibility = (sales quantity ÷ input quantity) × 100 [%] (2) Then, in ST11, the sales digestion rate and the reference digestion rate 61b are compared. Then, only when the sales digestion rate is smaller than the reference digestion rate 61b, the product is extracted as a reduction target product, and as ST12, the individual product code 31 of the product corresponding to the extraction number 51 corresponding to the reduction product extraction file 50. And the exclusion flag 52 = OFF is registered (value reduction target product extraction means).

After that, if the process returns to ST5 and the next product record on the RAM 23 is selected, the above-mentioned ST6 to ST1.
The process 2 is executed. In this way, when the processes of ST6 to ST12 have been executed for all the product records on the RAM 23, this job ends.

FIG. 9 is a flow chart showing the processing procedure for the maintenance work of the discounted product extraction file. That is, the CPU 21
When the maintenance operation of the discounted product extraction file is started, first, at ST21, all the records registered in the discounted product extraction file 50 are read and temporarily stored in the RAM 23. Next, in ST22, the product master file 30 is searched, the product records corresponding to the individual product codes 31 of all the records read from the discounted product extraction file 50 are read, and temporarily stored in the RAM 23.

Thereafter, a reduced-price product list is created based on the information of the product record temporarily stored in the RAM 23 and displayed on the display 27. That is, the classification code 32, the season code 33, the product name 34, the first insertion date 35, the first selling price 36, the current selling price 37, the number of times of price reduction 3 of all the products registered in the discounting product extraction file 50 as the reduction target product.
9, the input quantity 310, the sales quantity 311 and the like are displayed as a reduced price product list.

Next, in ST24, the end of business is declared, or in ST25, the price exclusion product is waited for to be designated. Then, if there is a product designated as a price reduction excluded product among the products displayed in the price reduction product list by the key operation of the keyboard 26, the RAM 23 is set as ST26.
The exclusion flag 52 corresponding to the single item code 31 of the product designated as the price-reduced product is turned on among all the records of the price-reduced product extraction file 50.

On the other hand, when the operation end is declared by the key operation of the keyboard 26, the RAM 2 is set as ST27.
HDD2 in all records of the discounted product extraction file 50 on 3
9 to update the discounted item extraction file 50. After that,
This work ends.

FIG. 10 is a flow chart showing the processing procedure of the price reduction execution work. That is, when starting the discount execution task, the CPU 21 first sets the discount item extraction file 5 in ST31.
All the records registered in 0 are read out and temporarily stored in the RAM 23.

Next, in ST32, the top record of the discounted product extraction file 50 is selected from the RAM 32. Then, in ST33, the exclusion flag 52 of this record is checked. Here, when the exclusion flag 52 is OFF, the product is a price reduction target product, so the product master file 30 is searched using the single product code 31 of the record as a search key in ST34, and the product corresponding to the search key is searched. The record is read and temporarily stored in the RAM 23.

Next, in ST35, the number of price reductions of the commodity record stored in the RAM 23 is incremented by "+1".

Next, in ST36, the price range setting file 70 is searched using the season code 33 and the classification code 32 of the product record as search keys, and the price range table data in which the search key matches the season code 33 and the classification code 32 are searched. When 71 is read, it is temporarily stored in the RAM 23.

Next, in ST37, the price range table data 71 on the RAM 23 is referred to, and the selling price data corresponding to the price range code 38 and the number of times of reduction 39 of the merchandise record is read out and used as the new selling price after the reduction. The current selling price 37 of the product record is changed to the new selling price after this price reduction. Thereafter, in ST38, the corresponding product record in the product master file 30 is updated with the product record on the RAM 23 (automatic price reduction means).

The exclusion flag 52 is turned on in ST33.
If so, the product is a price exclusion product,
The processes of ST34 to ST38 are not performed.

After that, returning to ST32, if the next record of the discounted product extraction file 50 on the RAM 23 is read, the processes of ST33 to ST38 are executed. In this way, S for all records of the discounted product extraction file 50
If the processes of T33 to ST38 are executed, ST39
After clearing the price-reduced product extraction file 50, the operation is finished.

In the store processor 2 of the present embodiment configured as described above, the product master file 30, the season master file 40, the digestion rate setting file 60 and the price range setting file 70 are now stored in FIGS. 3 and 4, respectively. ，
It is assumed that the data shown in FIGS. 6 and 7 are set. Further, the discounted product extraction file 50 is assumed to be cleared.

In this state, after the store is closed on April 30, the operator of the store processor 2 operates the key operation of the keyboard 26 to select the price reduction target product extraction operation, and the season code "1" is selected as the price reduction target product extraction condition. (“Spring” in this case) and the classification code “1001” (“Ladies dress” in this case) are input.

Then, from the digestion rate setting table 60, the season code "1" and the classification code "1001" are obtained.
The digestion rate table data 61 corresponding to is read. Further, the product record in which the season code “1” and the classification code “1001” match from the product master file 30 (in this case, the record of the single product code “nn ... n1” and the record of the single product code “nn ... n2”). Is read. Further, the start date data 41 (in this case, "0301": March 1st) corresponding to the season code "1" is read from the season master file 40.

Next, the single item code "nn ... n1"
First-charge date data 35 of the record (in this case, "020
1 ": February 1) and the start date data 41 are compared, and the later one is set as the start date. That is, March 1 is set as the start date.

Next, the number of days elapsed from the date of calculation to the current date is calculated as the number of sales days 61a. That is, “61 days” is calculated as the elapsed sales days 61a, and the reference digestion rate 61 corresponding to the elapsed sales days 61a is calculated.
“60%” is determined as b.

Further, the sales consumption rate is calculated from the input quantity 310 (“500” in this case) and the sales quantity 311 (“250” in this case) of the record of the single item code “nn ... n1”. That is, the sales digestion rate “50%” is calculated.

As a result, the sales digestion rate is lower than the reference digestion rate, so that the product is extracted as a reduction target product, and the single product code "nn" is associated with the extraction number "1" in the reduction product extraction file 50. ...... n1 "is registered. In addition,
At this time, the exclusion flag 52 is OFF.

Next, the single item code "nn ... n2"
First-charge date data 35 of the record (in this case, "031
5 ": March 15) and the start date data 41 are compared, and the later one is set as the start date. That is, March 15
The day is set as the start date.

Next, the number of days elapsed from the date of calculation to the current date is calculated as the number of sales days 61a. That is, “47 days” is calculated as the elapsed sales days 61a, and the reference consumption rate 61 corresponding to the elapsed sales days 61a is calculated.
“50%” is determined as b.

Further, the sales consumption rate is calculated from the input quantity 310 (“300” in this case) and the sales quantity 311 (“135” in this case) of the record of the single item code “nn ... n2”. That is, the sales digestion rate “45%” is calculated.

As a result, the sales digestion rate is lower than the reference digestion rate, so that the product is extracted as a reduction target product, and the individual product code "nn" corresponds to the extraction number "2" of the reduction product extraction file 50. ...... n2 "is registered. In addition,
At this time, the exclusion flag 52 is OFF.

Incidentally, for example, a single item code "nn ... n"
If the sales quantity of the product of “1” is “350”, the sales digestion rate is “70%”, and the sales digestion rate is higher than the reference digestion rate, so the relevant commodity is not extracted as a target product for price reduction. . Further, for example, a product with the single item code “nn ... n2” has the first introduction date of March 31st and the elapsed sales days is “3”.
If it is “1 day”, the standard digestibility is “30%”, and the sales digestibility is larger, so that it is not extracted as a target product.

When the price reduction target product extraction work is completed in this way, the operator next selects the price reduction product extraction file maintenance work. Then, the discounted product list is displayed on the display 27. Here, if the operator specifies the price reduction exclusion of the product of the individual product code “nn ... n1” by the key operation, the exclusion flag 52 of the record of the individual product code “nn ... n1” in the discounted product extraction file 50 is set. It is turned on (see the data example in FIG. 5).

When the price-reduced item extraction file maintenance work is completed in this way, the operator next selects the price-reduction execution work. Then, first, the record of the extraction number "1" in the discounted product extraction file 50 is selected. However, since the exclusion flag 52 of this record is ON and the product is not subject to the price reduction, the price reduction process for the current selling price 37 is not performed.

Next, the record of the extraction number "2" in the discounted product extraction file 50 is selected. Since the exclusion flag 52 of this record is OFF and the product is a target for price reduction, the number of times of price reduction 39 of the product record corresponding to the corresponding single product code “nn ... n2” is counted up to “2”.

The season code 33 (“1” in this case) and the classification code 32 (“1001” in this case) of the product record are used as search keys to search the price range setting file 70, and the search key and season. The price range table data 71 in which the code 33 and the classification code 32 match is read. Then, in the row of the price range code 38 (“2” in this case) of the product record in the price range table data 71, the selling price data set in the column of the number of reductions 39 (“2” in this case) is the value. The new selling price after the price reduction is read, and the current selling price 37 of the product record is changed to the new selling price after the price reduction. That is, the selling price data “1480” is read from the price range table data 71, and the current selling price “1980 yen” is automatically reduced to the new selling price “1480 yen”.

As described above, in this embodiment, the store processor 2 functioning as a product price management device calculates the ratio of the sales quantity to the input quantity, which is the actual sales value of the product, as the sales extinction rate and is related to the product. The number of days elapsed from the predetermined start date to the present is calculated as the number of sales days. Then, by referring to the digestion rate setting file 60, a reference digestion rate with respect to the number of elapsed sales days which is a sales target reference value is determined, and it is checked whether or not the sales digestion rate is smaller than this reference digestion rate. If the product is smaller, the product is extracted as the product targeted for price reduction.

Therefore, since the product whose sales digestion rate is lower than the reference digestion rate, that is, the product whose sales are poor, are automatically selected, the store manager or the like can easily know the products whose sales are poor. , The human burden on the reduction processing is greatly reduced.

Further, since the criterion for determining whether the sales are good or bad is uniquely determined by the setting data of the digestion rate setting table 60, the price can be reduced with a high degree of reliability that always matches the sales situation regardless of the experience of the person in charge. Can be executed. Therefore, it is possible to reduce the profit by reducing the price of the product that sells well due to a selection error of the price-reduced product, or to reduce the profit of the product that sells poorly, and to avoid the inconvenience of unsold products, thereby increasing the profit.

Further, in the present embodiment, the current selling price 37 stored in the product master file 30 of the product extracted as the price reduction target product is automatically changed to the amount reduced based on the setting information of the price range setting file 70. is doing. Therefore,
Since the work of changing the selling price for the product master file 30 is also unnecessary, the human burden is further reduced.

Further, in the present embodiment, the single-item code 31 of the product extracted as the price-reduced product is registered in the price-reduced product extraction file 60, and is excluded from the price-reduced products in the maintenance work of the price-reduced product extraction file 60. The operator can freely select whether or not. Therefore,
Even if the sales are bad, even products that do not need to be price cut will not be automatically priced down, which is practical.

In this embodiment, an appropriate sales period is set as the season code 33 for each product, and the first day of the sales period is compared with the sales start date of the product, and the product with the later date is sold. It is used as the starting date for calculating the elapsed days. Therefore, the sales at the time when it is out of the sales period does not affect the automatic price reduction processing, so that the reliability of the automatic price reduction processing is further enhanced.

The effect of the present invention can be achieved by adding an item for the date of calculation to the record of the product master file 30 and artificially setting an appropriate calculation date for each product in advance.

Further, in the above-mentioned embodiment, the function as the commodity selling price management device of the present invention is provided in the store processor in the POS system, but it may be provided in a single electronic cash register.

Further, by providing means for externally inputting the input quantity and the sales quantity of each product, it is possible to function as a product price management device independent of the POS system. In this case, for example, a structure in which a label printer is connected and a priced label of the corresponding selling price is printed out when the selling price of the sale item is inquired can be considered.

Further, in the above embodiment, the price range setting file 70 is provided to set the price after the price reduction according to the number of price reductions for each initial selling price. A rate may be set and the current selling price may be multiplied by (1-reduction rate) to calculate the reduced price. In this case, a reduction rate for the number of price reductions may be set for each initial selling price, or a reduction rate for the number of price reductions may be set for each initial selling price. Further, if all the price reduction rates are common, the price reduction rate can be set in the ROM 22 or the RAM 23 and the price range setting file 70 can be deleted.

In the above embodiment, the sales target reference value is the sales consumption rate, but the sales quantity may be used as it is as the sales target reference value. Using the quantity value as the sales target standard value has an advantage that it becomes easy to judge the sales of a product having a high unit price and a small input quantity. Therefore, depending on the product, whether to use the sales digestibility as the target reference value or the sales quantity as the target reference value may be used properly.

In addition to this, various modifications can be made without departing from the scope of the present invention.

[0087]

As described above in detail, according to the present invention, it is possible to significantly reduce the human burden on the price reduction processing, and it is possible to perform highly reliable price reduction processing which always matches the sales situation, thereby increasing the profit. It is possible to provide a product sales price management device.

[Brief description of drawings]

FIG. 1 is a schematic diagram of a POS system according to an embodiment of the present invention.

FIG. 2 is a block diagram showing a main configuration of a store processor according to the first embodiment.

FIG. 3 is a diagram showing a main configuration and data example of a record registered in a product master file 30 in the embodiment.

FIG. 4 is a season master file 40 in the same embodiment.
FIG. 4 is a diagram showing a main part configuration and data example of a record registered in FIG.

FIG. 5 is a diagram showing a main configuration and data example of a record registered in a discounted product extraction file 50 in the embodiment.

FIG. 6 is a diagram showing a main configuration and data example of a record registered in a digestibility setting table 60 in the embodiment.

FIG. 7 is a diagram showing a main configuration and data example of a record registered in a price range setting file 70 in the embodiment.

FIG. 8 is a flowchart showing a processing procedure of a value-reduction target product extraction operation executed by the CPU of the store processor in the embodiment.

FIG. 9 is a flowchart showing a processing procedure of a discounted article extraction file maintenance work executed by the CPU of the store processor in the embodiment.

FIG. 10 is a CPU of the store processor according to the embodiment.
10 is a flowchart showing the processing procedure of the price reduction execution job executed by.

[Explanation of symbols]

 1 ... POS terminal 2 ... Store processor 30 ... Merchandise master file 40 ... Season master file 50 ... Inferior product extraction file 60 ... Digestion rate setting file 70 ... Price range setting file

Claims (3)

[Claims] 1. A product selling price management device comprising a product file storing selling price information corresponding to a unique product code attached to each product, and outputting the corresponding selling price when the selling price of the selling product is inquired. In the above, the sales record value management means for storing and managing the sales record value for each product, the elapsed days calculation device for calculating the elapsed days from the predetermined calculation date to the present as the sales elapsed days for each product, and the sales progress A reference value storage means for presetting and storing a sales target reference value for the number of days, and a sales target reference for the elapsed sales day calculated by the elapsed sales day calculating means with reference to the stored contents of the reference value storage means for each product. A value-decreasing target product extractor that determines a value and extracts a product whose sales performance value managed by the sales performance value management means is smaller than the reference value as a price-reduction target product. Commodity selling price management device, characterized in that it comprises a door. 2. The automatic price reduction means for changing the selling price information stored in the product file of the product extracted as the price reduction target product by the price reduction target product extraction means to the reduced price. Commodity selling price management device. 3. The elapsed days calculating means compares the first day of the sales period set for each product with the sales start date of the corresponding product, and calculates the elapsed sales days with the later date as the start date. The product selling price management device according to claim 1 or 2, characterized in that.