JPH05250566A - Marchandise management system - Google Patents

Abstract

PURPOSE:To lighten the load of maintenance on a shop side by transferring history data to a center, comparing the data with the data of the center and taking an analysis, and generating shop management data. CONSTITUTION:A history data storage means 15 is stored with the PLU codes and prices of marchandise and maintenance records at the time of temporary registration or selling price alteration, and the batch transfer of the respective data is performed. The center 500 compares the received history data with data in a data base 19 to analyze them and when it is decided that shop control data marchandise are required, shop control data such as registration data on are generated; and further a document for shop report wherein sales totals by shops, etc., are described is generated and the respective data are transferred to a shop system 400 by facsimile, electronic mailing, etc. The shop system 400, on the other hand, automatically performs maintenance such as the registration, deletion, etc., of data of an marchandise master 13 by a store controller 11.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a product management system, and more particularly to a product management system in a POS (Point of Sales) system.

[0002]

2. Description of the Related Art Today, POS is used to manage food miscellaneous goods.
The system is widely used. The POS system includes a POS terminal provided in each store, a store controller that manages these POS terminals on the store side, and a center that controls and manages each store.

FIG. 2 shows the configuration of a general POS system. The system shown in the figure includes a store system 100 and a center 200. The store system 100 includes a store controller 1 and a terminal 2 connected to the store controller 1. The store controller 1 is composed of a microcomputer or the like and has a function of controlling each terminal 2. In addition, the store controller 1
A product master 3 that stores all the product information and a sales data file 4 that stores the sales data of the products are provided, and all data related to the products as the store system 100 is governed and managed.

The terminal 2 has a product management table 5 corresponding to each product. This product management table 5 is a product management symbol (PL) such as a bar code assigned to each product.
U: Price Look Up), which stores data of items such as unit price, name, and department for each product. The center 200 is a headquarters system that controls and manages each store system 100, and is connected to each store system 100 via a communication line 300.
A database 6 for storing data of all store systems 100 is provided.

In such a structure, when a certain product is sold, the barcode attached to the product is read by the scanner or the like provided in the terminal 2. As a result, the product management table 5 is referred to, the data such as the unit price and the name is searched, and the data is stored in the storage device (not shown) in the terminal 2. Also, at the time of product sales,
If there is no data corresponding to the bar code of the product in the product management table 5, the terminal 2 performs temporary registration and sells the product. This temporary registration is to register the PLU code given to the product, the department, the price, etc. of the product, and then to this temporary registration until the main registration is made in the product master 3 in the store controller 1. Data is used to sell and manage products.

Sales by the terminal 2 for a certain period, for example, sales for one day are recorded in the sales data file 4 as sales data of the store controller 1. Further, the product master 3 records the PLU code, price, name, etc. for each product, and the product temporarily registered in the terminal 2 is also main-registered in the product master 3.

On the other hand, the sales data on the side of the store system 100 is transferred to the center 200 via the communication line 300 after business hours, or recorded on a recording medium such as a floppy disk or the like. Will be mailed to. In the center 200, the sales data sent from the store system 100 side is stored in the database 6.

In the store system 100, for example, when the price of a certain product is to be changed, the center 20
The price is set on the side of the store system 100 regardless of 0. That is, when the price is changed, the price data of the product master 3 in the store controller 1 is changed, and the content of the product management table 5 in the terminal 2 is changed.

[0009]

In the conventional product management system, as described above, the maintenance / management of the product master 3 is performed by the maintenance work on the side of the store system 100. However, such a configuration has the following problems. That is, there is a problem in that performing the maintenance work on the shop side imposes a heavy burden on the operator on the shop side. Further, since the store side manages the product master 3 regardless of the center 200, there is a problem that the product master 3 on the store system 100 side and the product master in the database 6 on the center 200 side cannot be matched. Further, there is a problem that the operation status of the store cannot be grasped by the center 200 side.

In addition, in the conventional product management system, if there is no corresponding data in the product management table 5 of the terminal 2 at the time of sale of the product, a procedure such as temporary registration at that time and subsequent main registration is required. Therefore, the efficiency of the product sales business was very poor. The present invention has been made to solve the above-mentioned conventional problems, and an object of the present invention is to provide a product management system that can reduce the burden on the store side and can reliably manage the store on the center side.

[0011]

The product management system of the first invention of the present invention controls the terminal for inputting the sales data of the product and the terminal, and stores the data of the product handled by the terminal. In a product management system including a store controller that has a product master and manages product information of store systems, and a center that has a database that aggregates product information of each store system and collectively manages data of each store system History data storage means provided in the store controller for storing maintenance records on the side of the store system, history data transfer means for transferring the history data stored in the history data storage means to the center, and the center Store management by comparing the history data transferred in the And a product master management unit that manages the data of the product master of the store controller based on the store management data transferred from the center. is there.

A product management system of a second invention has a product management table corresponding to a product, controls a terminal for inputting sales data of each product with reference to the product management table, and controls the terminal. It has a product master that stores the data of the products handled by the terminal, has a store controller that manages the product information of the store system, and a database that aggregates the product information of each store system, and collectively stores the data of each store system. In a product management system including a center for managing the product, if the terminal does not have data corresponding to a product in the product management table,
Product management data searching means for searching the data from at least one of the store controller or the center; product management data notifying means for notifying the terminal of the presence or absence of the data searched by the product management data searching means; If there is no data in the result notified by the product management data notifying means or if there is no notification from the product management data notifying means within a predetermined time from the start of the data inquiry from the terminal, the product is set to the product management table. And a provisional registration control means for provisionally registering.

[0013]

In the merchandise management system of the present invention, a terminal is connected to the store controller, and the sales data of the merchandise is input by this terminal. Further, the store controller is provided with history data storage means for storing a record of maintenance in the store system such as a change in selling price. The history data in the history data storage means is transferred to the center by the history data transfer means provided in the store controller. In the center, the store management data generation means compares and analyzes the historical data and the data in the database, generates store management data, and sends it to the store system. The product master management means of the store controller manages the product master data based on the store management data. Therefore, the burden on the store side is reduced, and the operation status on the store side can be grasped on the center side.

[0014]

Embodiments of the present invention will be described in detail below with reference to the drawings. FIG. 1 is a block diagram showing a first embodiment of the product management system of the present invention. The system shown in the figure includes a store system 400, a center 500, and a communication line 600 connecting these. In addition, the store system 400
Is composed of a store controller 11 and a plurality of terminals 12 connected to the store controller 11 as in the conventional case.

The store controller 11 is the product master 1
3, sales data file 14, history data storage means 1
5, history data transfer means 16, product master management means 17
It consists of The product master 13 and the sales data file 14 are the same as the conventional product master 3 and the sales data file 4. Also, the history data storage means 1
Reference numeral 5 is a maintenance history file, in which data such as temporary registration history and selling price change history are recorded. In addition, here
The selling price change history refers to a record of the PLU code, changed price, etc. of the product when the selling price is changed at the terminal 12. Further, the history data transfer means 16 is the history data storage means 1
5, the means for transferring the history data stored in No. 5 to the center 500 via the communication line 600, the product master management means 17
Is the store management data generation means 2 of the center 500 described later.
Product master 1 based on the store management data generated by 0
3 is a means for managing the data.

The terminal 12 is equipped with a scanner (not shown) for reading the bar code of the commodity as in the conventional case, and
It has a product management table 18 which is a data table corresponding to the bar code data, and is for inputting sales data of products. The center 500 has a database 19 that stores data of all store systems 400, and store management data generation means 20. The store management data generation means 20 compares and analyzes the history data transferred from the store system 400 and the data corresponding to the store in the database 19, and stores the instructions to the store system 400, the product price data, and the like. It has the function of generating management data.

Next, the operation of the product management system thus configured will be described. FIG. 3 is an explanatory diagram relating to the data flow of the product management system of this embodiment. Further, FIG. 4 is a flowchart showing the operation of the product management system of this embodiment. First, as shown in FIG. 3, the history data storage unit 15 records the PLU code, price, etc. of the product at the time of temporary registration and change of the selling price. In addition to this, various maintenance records performed on the shop system 400 side are also stored. Such history data storage means 15
Data is batch-transferred daily to the center 500 (step S1 in FIG. 4). The batch transfer is performed, for example, after the store is closed for business hours.

The center 500 compares the received historical data with the data in the database 19 and analyzes the data (step S2) to determine whether store management data is generated (step S3). What is this store management data?
Store system 4 by registering, deleting or changing selling prices
This data is generated when the product master 13 of 00 requires maintenance. When it is determined in step S3 that store management data is necessary, store management data such as product registration data is created (step S4), and further, for store reporting in which sales totals for each store are described. Is created (step S5), and these data are transferred to the store system 400 by facsimile or mail (step S6). If it is not necessary to create store management data in step S3, step S3
Go to 5 and create only the store report book.

On the other hand, in the store system 400, the center 5
Based on the store management data transferred from 00, maintenance such as registration and deletion of the data of the product master 13 is performed (step S7). The maintenance work is automatically performed by the store controller 11. Further, the maintained data of the product master 13 is reflected in the product management table 18 of the terminal 12.

As described above, in the above embodiment, the terminal 12 or the store controller 11 on the side of the store system 400.
Then, the history of temporary registration and various maintenance work is created as a file, which is analyzed by the center 500, and the result is reflected in the store system 400, so that the following effects can be obtained.

(1) If the product temporarily registered on the store system 400 side is in the database 19 on the center 500 side, it is reflected on the store system 400, so that it is not necessary for the store side to carry out the main registration work of the product. The burden on the store is reduced. (2) Since the product master can be matched between the center 500 side and the store system 400 side, it is not necessary for the store system 400 side to have unnecessary product data. (3) Since the center 500 can know the maintenance history of the store system 400, the store system 400
It is possible to grasp the operation status on the side, and it can be useful for sales guidance from the center 500 to the store system 400.

Next, a second embodiment in which the efficiency of temporary registration is improved will be described. FIG. 5 is a block diagram showing the configuration. The system shown in the figure comprises a store system 700, a center 800, and a communication line 900, and their relationships are the same as in the first embodiment. In addition, the store system 7
00 consists of the store controller 21 and the terminal 22,
These relationships are also the same as in the first embodiment.

The store controller 21 is the product master 2
3, a sales data file 24, a maintenance history file 25, and a product management data search means 26 and a product management data notification means 27. Here, the product master 23, the sales data file 24, and the maintenance history file 25 are the product master 13, the sales data file 14, and the history data storage means 1 in the first embodiment.
Since the configuration is the same as that of 5, the description thereof is omitted here.
Further, the product management data search means 26 is a means for searching the product master table 23 for this data when there is no data corresponding to the PLU code of a product in the product management table 28 at the terminal 22. Further, the product management data notifying means 27 causes the product management data searching means 26 to
It is means for notifying the terminal 22 of the corresponding data when there is the corresponding data.

The terminal 22 is provided with a product management table 28 as in the conventional and first embodiments, and when the product is sold, the sales data of each product is input to the store controller 21 by referring to the product management table 28. It is a device. Further, the terminal 22 is provided with temporary registration control means 29. The temporary registration control means 29 starts an inquiry from the terminal 22 when there is no corresponding data in the result notified from the product management data notification means 27 or the product management data notification means 32 of the center 800 described later. If there is no notification within a predetermined time after that, the product has a function of temporarily registering the product in the product management table 28.

The center 800 includes a database 30 for storing all the data of each store system 700, and in the same manner as the product management data search means 26 and the product management data notification means 27 of the store controller 21 described above, the product management data. It has a search means 31 and a product management data notification means 32.

Next, the operation of the second embodiment will be described. FIG. 6 is an explanatory diagram relating to the data flow of the product management system of this embodiment. FIG. 7 is a flow chart showing the operation of the product management system of this embodiment.

First, as shown in FIG. 6, when a certain commodity is sold and its barcode is scanned by the scanner 33 provided in the terminal 22, the terminal 22 refers to the commodity management table 28, It is searched whether there is PLU data of the product (step S1). In step S1, if there is the corresponding PLU data, the process proceeds to step S2 and normal sales processing is performed. On the other hand, the corresponding PLU
If the data does not exist in the product management table 28 of the terminal 22, the store controller 21 is inquired whether the data exists (step S3). As a result, the store controller 21 searches the product master 23 to check whether there is corresponding PLU data (step S4),
If there is, the PLU data is notified to the terminal 22 (step S5). When this notification is received by the terminal 22 within the predetermined time (step S6), the process proceeds to step S2 and normal sales processing is performed.

If there is no corresponding PLU data in the product master 23 of the store controller 21 in step S4, the store controller 21 inquires of the data to the center 800 (step S7). The center 800 searches the database 30 and determines whether there is corresponding PLU data (step S8). Here, if there is corresponding PLU data, the PLU data is notified to the terminal 22 (step S9), and if this is received by the terminal 22 within a predetermined time (step S10), the data is Check if is the headquarters selling price (step S1)
1). That is, there are two types of selling prices in the PLU data notified from the center 800: the headquarters selling price and the standard selling price desired by the headquarters. The selling price at the headquarters is the price for which the selling price at each store is determined. The selling price is a price at which the selling price at each store has a certain degree of freedom.

In step S11, when the selling price of the PLU data notified from the center 800 is not the headquarters selling price, the terminal 22 inquires whether the selling price is acceptable, and the operator changes the selling price. When it is determined (step S12), the operator inputs the amount of money (step S13), the sales process of step S2 is performed, and the sale price changed data is temporarily sent to the store controller 21 for maintenance. It is recorded in the history file 25 (step S14).

On the other hand, in step S8, the center 80
When there is no corresponding PLU data in the database 30 of 0, the center 800 notifies the terminal of “no corresponding data” (step S15). In the terminal 22, in this case, the store controller 21 or the center 80
If normal data is not returned within a predetermined time from 0 (steps S6 and S10), the product is provisionally registered (step S16). This temporary registration is performed by inputting the department code to which the product belongs and the amount of money, as in the case of the first embodiment. Then, the sales process of step S2 is performed by the temporarily registered data, and the data is recorded in the maintenance history file 25 in the store controller 21 (step S14), and is sent to the center 800 together with various maintenance data. Processed daily. Since this daily processing is the same as the method of the first embodiment, the description thereof is omitted here.

As described above, by having the function of performing the above-described series of procedures, unregistered products, new products, etc. can be previously stored in the terminal 22.
Even if the PLU data is not set in the
Registered in the database 30 of
The PLU data is automatically registered in the terminal 22. Also,
Even if there is no corresponding data in the database 30 of the center 800, by temporarily registering on the terminal 22 side,
If the official data is sent back from the center 800 on a daily basis, the official product name is input to the temporarily registered data and the main registration is made to the PLU data.

In each of the above-mentioned embodiments, an example of a POS system by reading a barcode of a product has been described as a product management system, but the present invention is not limited to this.
The system can be applied to various systems as long as it is a system that identifies and manages each product.

[0033]

As described above, according to the merchandise management system of the first aspect of the invention, the history data storage means for storing the record of the maintenance on the shop side is provided, and the history stored by the history data storage means is provided. The data is transferred to the center, compared and analyzed with the data in the center, and as a result, store management data for the store is generated, and the store manages the data of the product based on this store management data. Therefore, the load of maintenance work on the store side is reduced, and the product data on the center side and the store side are matched, so that the operation status on the store side can be accurately grasped at the center.

Further, according to the product management system of the second invention, when the terminal does not have the data corresponding to a certain product, the store controller and the center are inquired, and the data of the store controller and the center are not found. Only because the product is temporarily registered at the terminal, even if there is no corresponding data in the product management table of the terminal at the time of product sales, it is not necessary to perform the temporary registration each time as in the past, and the operator The burden can be reduced and the efficiency of sales operations can be improved.

[Brief description of drawings]

FIG. 1 is a configuration diagram of a first embodiment of a product management system of the present invention.

FIG. 2 is a configuration diagram of a general POS system.

FIG. 3 is an explanatory diagram of data processing of the first embodiment in the product management system of the present invention.

FIG. 4 is an operation flowchart of the first embodiment of the product management system of the present invention.

FIG. 5 is a configuration diagram of a second embodiment of the product management system of the present invention.

FIG. 6 is an explanatory diagram of data processing of the second embodiment in the product management system of the present invention.

FIG. 7 is an operation flowchart of the second embodiment of the product management system of the present invention.

[Explanation of symbols]

 11, 21 Store controller 12, 22 Terminal 13, 23 Product master 15 History data storage means 16 History data transfer means 17 Product master management means 19 Database 20 Store management data generation means 26, 31 Product management data search means 27, 32 Product management Data notification means 28 Product management table 29 Temporary registration control means 400, 700 Store system 500, 800 Center

Claims (2)

[Claims] 1. A store controller for inputting sales data of a product, a store controller for controlling the terminal, storing a data of a product handled by the terminal, and managing product information of a store system, In a product management system having a database that aggregates product information of each store system, and a center that collectively manages data of each store system, in the store controller, a maintenance record on the store system side is provided. History data storage means for storing, history data transfer means for transferring the history data stored in the history data storage means to the center, history data provided in the center and transferred, and database data of the center And the store management data generating means for generating store management data, and the transfer from the center. A product management system comprising a product master management means for managing the data of the product master of the store controller based on the sent store management data. 2. A terminal which has a product management table corresponding to a product and which inputs sales data of each product by referring to the product management table, and which controls the terminal and which handles data of the product handled by the terminal. A product that has a product master that stores the product information, a store controller that manages product information of the store system, a database that aggregates product information of each store system, and a center that collectively manages the data of each store system In the management system, in the terminal, when data corresponding to a certain product is not in the product management table, a product management data search unit that searches the data from at least one of the store controller and the center; A product management device that notifies the terminal of the presence or absence of data retrieved by the data retrieval means. If the result notified by the product management data notification unit is no data or if there is no notification from the product management data notification unit within a predetermined time from the start of the data inquiry from the terminal, A product management system comprising: a temporary registration control means for temporarily registering a product in the product management table.