JPH0619785B2 - Sales data management device - Google Patents

Description

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a sales data management device. More specifically, the present invention relates to a device that manages data when repeatedly sold to a fixed customer.

2. Description of the Prior Art Generally, the following two selling methods are known as methods for selling goods or articles. The first method is a sales method adopted in department stores, supermarkets, and various shops, where a product is displayed in advance, and a customer comes to the store to purchase a desired product from the displayed products and conduct a commercial transaction. Is a way to do. The second method is a sales method called delivery sales or door-to-door sales. Delivery sales is a sales method adopted by liquor stores (liquor stores), rice grain stores (rice stores), and the like, where products ordered by the customer over the telephone are delivered to the customer's home for sale. Is the way. In addition, for delivery and sales, there are cases where various products are loaded in a car in advance and sold while individually visiting a customer's house. Further, door-to-door sales of cosmetics and the like are similar to delivery sales. However, delivery sales or door-to-door sales (hereinafter collectively referred to as delivery sales)
However, the reduction of delivery efficiency has become a problem due to the small size of delivery products and traffic congestion. Further, due to the reduced delivery efficiency, the labor cost rises and the profit margin is lowered.

By the way, in general households, when a product such as alcohol or rice is purchased by delivery sale, the type of product and the order interval are often fixed.

SUMMARY OF THE INVENTION In summary, the present invention registers data that is repeatedly sold for each customer, obtains scheduled date data to be sold next time based on the registered data, and stores the scheduled date data in the storage means. Further, the sales area is divided into a plurality of areas or districts, a district code is set for each district, and a district code for each customer is registered. And for each customer in the same area,
This is to facilitate the creation of a table showing the correspondence between the scheduled sale date and the customer next time.

According to this invention, for each customer in the same district or area,
Since it is easy to create a table showing the relationship between the next scheduled sale date and the customer, the sales data can be managed so that the sales can be performed efficiently, and the sales can be efficiently performed to the customers in the same district.

Therefore, an object of the present invention is to provide a sales data management device capable of easily and quickly creating materials for efficiently performing sales by district.

Specific embodiments of the present invention will be described below with reference to the drawings.

DESCRIPTION OF PREFERRED EMBODIMENTS FIG. 1 is a block diagram of a delivery sales data management device 10 according to an embodiment of the present invention. In the configuration, the delivery sales data management device 10 of this embodiment includes a central processing unit (hereinafter C
PU) 11. A clock 12, a display 13, a printer 14 as an example of a printing unit, a magnetic recording / reading device 15, a keyboard 20, and a memory 30 are connected to the CPU 11. Here, the clock 12 generates data of the current date and time. The display 13 is, for example, a CRT display, and displays a table created based on registered data or filed data. The printer 14 is, for example, a dot printer, and is used to print and record a table for forecasting delivery sales by district or by customer. Magnetic recording / reading device 15
Is for reading data recorded or stored in the floppy disk 40 or recording data to be filed in the floppy disk 40. Keyboard 2
0 is used as a registration means for registering delivery sales data by an operator's operation, and its detailed configuration is shown in FIG. 2 described later. Memory 30
Includes a writable / readable memory (eg, random access memory; RAM) and a read-only memory (eg, read-on memory; ROM). Details of the RAM storage area included in the memory 30 will be described in detail with reference to FIG. The ROM stores a program for the CPU 11 to perform the operations of FIGS. 6A to 6D described later.

FIG. 2 is a diagram showing details of the keyboard 20. In the figure, the keyboard 20 is a key switch 2 on the operation panel.
One and a plurality of switch groups 22 to 26 are arranged. The key switch 21 switches the operation mode depending on the selected position of the lock, and selects, for example, the delivery mode or the preset mode. Here, the delivery mode is selected when a voucher is issued when delivering a product or when it is desired to create a material for predicting delivery sales. The preset mode is selected when setting an item name or product name for each item key, which will be described later, and for setting a customer name for each customer key, which will be described later.

Further, the switch group includes a numerical key 22 and function key groups 23 to 26. The function key group includes a plurality of item keys 23 and a plurality of customer keys 2
4, including a kana / alphabet key 25 and other function keys 26. The plurality of item keys 23 are assigned different item numbers for each product or each product name. The customer keys 24 are assigned different numbers for each customer.

Other function keys 26 are designated date keys 26
a, delivery key 26b, district key 26c, prediction key 26d
And a quantity key 26e. The designated date key 26a is
Used to specify the next door-to-door sales date.
The delivery key 26b is used to input registration data each time delivery and sale are made. The district key 26c is used to input district data to which the customer's address belongs when the sales area of the store is divided into a plurality of areas. Prediction key 26d
Will be used to create materials that record the forecast data needed for the next delivery sale. The quantity key 26e is used to enter the quantity of a product for each delivery sale.

FIG. 3 is a diagram schematically showing a storage area of the RAM included in the memory 30. In the figure, the RAM of the memory 30
Is a search buffer area 31, a numeric buffer area 32,
It includes a flag area 33, a customer name conversion table 34, and an item name conversion table 35. The search buffer area (hereinafter abbreviated as buffer) 31 is a customer code storage area 31.
0, district code storage area 311, item code storage area 312, quantity data storage area 313, previous delivery date data storage area 314, next scheduled delivery date data storage area 315, delivery count data storage area 316
It includes a periodic data storage area 317 and a temporary periodic data storage area 318. In the following description, each storage area is abbreviated as an area. The area 318 is a storage area that is one less than the fixed number in order to temporarily store the number of times of delivery and sales to the same customer, that is, the delivery sales cycle until the number of times of delivery reaches a fixed number (for example, 6 times). including.

The numerical buffer area (hereinafter abbreviated as a buffer) 32 is
The numerical data input by operating the numerical keys 22 is stored.

The flag area 33 includes a plurality of flags F1 to F8. The flag F1 stores that numeric data has been input by operating the numeric key 22, that is, that there is numeric data. The flag F2 stores that the kana / alphabet key 25 has been operated. The flag F3 stores that any one of the customer keys 24 has been operated. Flag F4
Stores that any of the item keys 23 has been operated. The flag F5 stores that the quantity key 26e has been operated. The flag F6 stores that the designated date key 26a has been operated. The flag F7 stores that the delivery key 26b has been operated. Flag F8 is district key 26
Remember that c has been operated.

The customer name conversion table 34 includes an area for setting and storing a customer code and a customer name corresponding to each of the customer keys 24. The customer code and customer name corresponding to each customer key 24 are set by the following operations.
That is, the setting registration of the customer name conversion table 34 is performed by selecting the key switch 24 in the preset mode, pressing the desired customer key 24 to be set, and then the numerical key 24.
Is operated to input numerical information corresponding to the customer code, and the kana / alphabet key 25 is operated to input the customer name.

The item name conversion table 35 includes an item code storage area and an item name storage area corresponding to each of the plurality of item keys 23. The item code and the item name for each item key are set as follows. That is, in the setting of the item name conversion table 35, first, the key switch 21 is selected to the preset mode, the item key 23 to be set is pressed, and then the numerical key 22 is operated to input the item code corresponding to the item key. Kana / alphabet key 25
This can be done by operating and inputting the item name.

FIG. 4 is a diagram schematically showing file data stored (or recorded) in the floppy disk 40 which is an example of a storage means. The storage area (file area) of the floppy disk 40 includes a plurality of areas 410 to 418 for each customer code and each item code. Each area 410
The types of data stored in ˜418 are the same as the types of data stored in the areas 310-318 of the buffer 31 shown in FIG. That is, it means that the floppy disk 40 has a plurality of areas corresponding to each area of the buffer 31 for each customer code and for each item code. Registration data for each customer code and each item code, that is, one line of data shown in FIG. 4 is one unit.

The storage means may use a memory such as a MOSIC, instead of the one that stores (or records) the data by magnetically recording the floppy disk 40. However, the use of the floppy disk has an advantage over the one using the memory in that the storage capacity is not limited and a large number of data for each customer code and each item code can be stored.

FIG. 5A and FIG. 5B are diagrams schematically showing the key operation procedure when managing the delivery sales data by the delivery sales data management device of this embodiment, and in particular, FIG. 5A shows the registration for each delivery sales. FIG. 5B shows an operation procedure for issuing a slip, and FIG. 5B shows an operation procedure for creating a prediction table based on the data registered in the floppy disk 40.

First, an outline of an operation procedure when registering delivery sales data will be described with reference to FIG. 5A. For delivery and sales, the customer key 24 corresponding to the customer of the delivery destination is pressed, the numeric key 22 is operated to input the customer's area code, and then the area key 26c is pressed. In addition, when registering the items of the same customer and the same product, the input of the district code and the operation of the district key 26c can be omitted. Subsequently, the operator presses the item key 23 representing the item of the product to be delivered, and then operates the numerical key 22 to input the quantity data of the delivered product, and then the numerical key 22 to input. The quantity key 26e indicating that the numerical data is quantity is pressed. When the number of delivered products is one, the input of the quantity data and the operation of the quantity key 26e may be omitted. Then, the operator operates the numerical keys 22 to input the date data for delivering the product, presses the designated date key 26a, and then presses the delivery key 26b. If the delivery date is not the designated date, that is, if the delivery is made on the same day generated by the clock 12, it is not necessary to input date data and press the designated date key 26a. By performing such a series of operations, registration is performed for each customer who has delivered and sold and for each item. In response to this, a delivery slip is created.

Next, with reference to FIG. 5B, an outline of an operation procedure for creating a prediction table will be described. In the case of creating a prediction table for a day other than the year, month, and day in which the prediction table should be created, the operator operates the numeric keys 22 to input date data, and then presses the designated date key 26a, and then the prediction key. 26d is pressed. As a result, a forecast table for the designated scheduled delivery date is created. In this case, in order to improve the efficiency of delivery and sales, customers who are scheduled to deliver and sell in the period from the number of days specified by a certain number of days (2 days, for example) to the number of days specified by a certain number of days. Also, the item may be printed on the forecast table. The day when the forecast table is created is clock 1
If it is the current day of the year, month, and day, the date data need not be input.

By the way, it is also possible to create a forecast table for each customer or each item as needed. Creating a forecast table for each customer can be advantageously used when a certain product needs to be delivered to the same customer and an order is placed for another product that does not correspond to the next scheduled delivery date. In that case, customer key 2
After pressing 4 to specify the desired customer, the prediction key 26d
This is done by pressing.

By creating a forecast table for each item, it is possible to know when and how many items will be delivered and sold, and can be used for stocking and inventory management of items. In this case, after operating the item key 23 corresponding to the item for which you want to create a forecast table,
This is done by pressing the prediction key 25d.

Further, in the case where the delivery and sales are divided for each area, the efficiency of the delivery and sales can be further improved by creating a forecast table for each customer in the same area. In that case,
This is done by operating the numeric keys 24 to enter the district code for which the prediction table is to be created, pressing the district key 26c, and then pressing the prediction key 26d.

6A to 6D are time charts for explaining the operation of this embodiment. Next, a specific embodiment of the present invention will be described with reference to FIGS. 1 to 6D.

(1) Delivery Sales Data Registration Operation First, the operation when registering the delivery sales data will be described according to the operation procedure shown in FIG. 5A. In this case, the key switch 21 is selected in the delivery mode. CPU11
In step 1, it is repeatedly determined whether or not there is any key input. If any of the customer keys 24 is pressed first, it is determined in step 1 that there is a key input, and the process proceeds to step 2. In step 2, it is determined that it is not a numerical key, in step 3 it is determined that it is not kana / alphabet key 25, in step 4 it is determined that it is not in preset mode, and in step 5 the prediction key 26
If it is not d, it proceeds to step 6. When it is determined in step 6 that the key is the customer key 24,
Go to step 7. In step 7, the key code of the customer key 24 that has been operated is the area 31 of the buffer 31.
Stored at 0. Then, in step 8, the customer name corresponding to the customer key 24 just pressed is read from the customer name conversion table 34 and displayed on the display unit 13.
In step 9, a logic "1" is set in the flag F3 (that is, the flag F3 is set). After that, the process returns to step 1 and the next key input is made.

When it is necessary to input the district code of the customer who will be delivered and sold this time, the district code is input by operating the numerical keys 22. Accordingly, in step 2, it is determined that the numerical key 22 has been operated, and the process proceeds to step 10. In step 10, the flag F1 is set. In step 11, the input numerical data is buffer 3
Stored in 2. In step 12, the numerical data is displayed on the display 13. Then, when the district key 26c is pressed, after the judgments in steps 1 to 6 are made,
Go to step 13. In step 13, it is determined that the district key 26c has been pressed. In step 14, it is determined that the flag F1 is set. In step 15, the numerical data (that is, district code) stored in the buffer 32 is stored in the buffer 3
It is transferred to 11 and stored. In step 16, the district code is displayed on the display 13. Step 17
At, the flag F8 is set and the flag F1 is reset. Then return to step 1.

Next, the item key 2 corresponding to the item delivered and sold this time
When No. 3 is pressed, the above-described judgments of Steps 1 to 6 and 13 are made, and then the routine proceeds to Step 18. In step 18, it is determined that the item key is the item key 23, and the process proceeds to step 19. In step 19, the key code (that corresponds to the item code) input by pressing the item key 23 is the area 312 of the buffer 31.
Will be stored in. In step 20, the item name corresponding to the item code just input is the item name conversion table 35.
Read out and displayed on the display unit 13. Step 21
At, flag F4 is set. Then, the process returns to step 1 described above.

If the number of items to be delivered and sold this time is two or more, the numeric key 22 is operated to input the quantity data. In response to this, it is determined in step 2 that the numeric key 22 has been operated, and the process proceeds to step 10. Step 10
At, the flag F1 is set. In step 11, the numerical data input by operating the numerical keys 22 is stored in the puffer 32. In step 12, the numerical data is displayed on the display 13. continue,
When the quantity key 26e is pressed, steps 1 to 6, 1
After the judgments of 3 and step 18 are made, the routine proceeds to step 22. In step 22, quantity key 26e
It is determined that the button has been pressed, and the process proceeds to step 23. In step 23, it is determined that the flag F1 is set. In step 24, the quantity data stored in the buffer 32 is the area 3 of the buffer 31.
13 and stored. In step 25,
The quantity data is displayed on the display 13. In step 26, the flag F5 is set, the flag F1 is reset, and then the process returns to step 1.

Then, the numeric key 22 is operated to input the date data, and the designated date key 26a is pressed. Accordingly
The above-mentioned steps 1, 2, 10 to 12 are performed,
The date data is stored in the buffer 32. Then, in response to the pressing of the designated date key 26a, the determinations in steps 1 to 6, 13, 18 and 22 are made, and the process proceeds to step 27. In step 27, it is determined that the date designating key 26a has been pressed. Step 28
At, it is determined that the flag F1 is set. In step 29, the date data stored in the buffer 32 is transferred to and stored in the area 314 of the buffer 31. In step 30, the date data is displayed on the display 13. In step 31, the flag F6 is set and the flag F1 is reset.

If only the designated date key 26a is pressed without inputting date data, it is determined in step 28 that the flag F1 has been reset, and the process proceeds to step 32. In step 32, the date of the day generated from the clock 12 is read out, and then the operations of steps 29 to 31 are performed.

Then, when the delivery key 26b is pressed, the above-described determination operations of steps 1 to 6, 13, 18, 22, and 27 are performed, and then the process proceeds to step 33. In step 33, it is determined that the delivery key 26b has been pressed. In step 34, it is determined that the flag F3 is set, and in step 35, it is determined that the flag F4 is set. In step 36, the registration data of the floppy disk 40 is searched based on the customer code stored in the area 310 and the item code stored in the area 312. Then, in step 32, it is judged whether or not there is matched data. That is, it is determined whether or not the data matching the customer code and the item code stored in the areas 310 and 312 of the buffer 31 is stored in the areas 410 and 412 of the registration data of the floppy disk 40 for each unit. . If the customer code and the item code entered this time are not stored anywhere in the areas 410 and 412 of the floppy disk 40, in other words, if the order of the customer who makes the delivery sale for the first time is received, or the customer who has delivered and sold so far. If the item to be delivered is the first item, the process proceeds to step 38. Step 3
At 8, the data stored in the buffer 31 is organized. For example, when the quantity data is not input, 1 is automatically set. Step 39
In the area 316, numerical data “1” indicating that the number of deliveries is the first is set in the area 316. Step 40
In, the contents of the areas 310 to 318 of the buffer 31 are registered in the registration data storage area (that is, the area of one line shown in FIG. 4) for each customer code and each item code of the floppy disk 40. In step 41, registration data relating to delivery and sales (for example, customer code, district code, item code, quantity data, delivery date, etc.) is given to the printer 14 and printed and recorded on the slip by the printer 14. In step 42, all the flags F1 to F8 are reset, and then the process returns to step 1.

On the other hand, if the customer code, district code, and item code of the delivered product of the customer to be delivered and sold this time are registered so far, it is determined in step 37 that there is coincident data, and the process proceeds to step 43. Step 4
In 3, the registration data in which the customer code, district code and item code in the file of the floppy disk 40 are read out and stored in the buffer 31. That is, areas 310, 311 and 31 of the buffer 31
Other data corresponding to the same customer code, district code and item code stored in 2 is read from the floppy disk 40. At step 44, it is judged if the flag F6 is set. If the flag F6 is not set, the date of delivery of the merchandise of the previously entered registration data is the current day, so the routine proceeds to step 45. In step 45, the date data of the current day is read from the clock 12. When the flag F6 is set, the delivery date has been designated, and therefore the operation proceeds to step 46 without performing the operation of step 45. At step 46, the delivery count data N read from the floppy disk 40 allows a fixed number of delivery cycles (for example, X =
It is determined whether it is larger than 6). If the number of deliveries is less than the fixed number X, a temporary period is calculated in step 47. The provisional cycle is calculated based on the previous delivery date and the current delivery date of the registration data in which the customer code and the item code corresponding to each other are previously input. The temporary cycle data thus obtained is sequentially stored in each area for storing the temporary cycle data until the number of deliveries reaches a certain number X. For example, as shown in FIG. 4, if the customer code is “00001” and the registration data is the item code “0011” and the number of deliveries is 4, the provisional cycle data for 3 times has already been registered. ing. Therefore, in this case, the provisional cycle data obtained this time is stored in the fourth provisional cycle data storage area included in the area 318.

In step 48, the scheduled date for the next delivery and sale is calculated and stored in the area 315. in this case,
When the number of deliveries is smaller than a fixed number, the next scheduled delivery date is obtained from the cycle data obtained by averaging the provisional cycle data for a plurality of times. In step 49, 1 is added to the delivery count N to obtain a new delivery count, and the delivery count data is stored in the area 316. At step 50, it is judged if the flag F5 is set. This determination is to determine whether or not the quantity of the product to be delivered and sold has changed, based on whether or not the quantity data has been input this time. If it is determined that the flag F5 is not set,
Go to step 51. In step 51, the quantity data corresponding to the registration data in which the customer code and the item code match is read from the floppy disk 40 and stored in the area 313. If it is determined that the flag F5 is set, the operation proceeds to step 52 without performing the operation of step 51. In step 52, the contents of each area of the buffer 31 are written to the registration data storage area of the floppy disk 40 in which the customer code and the item code match. Then, the operations of steps 41 and 42 are performed.

By the way, when the number of deliveries N exceeds a certain number of times X, it is necessary to calculate a fixed period from a provisional period obtained by delivering and selling a certain number of times. In this case, after it is determined in step 46 that the number of deliveries N has exceeded the predetermined number of times X, the routine proceeds to step 53, where the fixed period is calculated. That is, the fixed cycle is determined, for example, by excluding the maximum and minimum cycles of the provisional cycle data for five times and obtaining the average value of the remaining three cycle data. The fixed cycle data thus obtained is stored in the area 317. In the case of a customer whose fixed cycle has already been decided, the data in the area 318 is erased. Then, new cycle data is calculated based on the cycle data from the previous delivery date to the current delivery date and the fixed cycle data obtained so far, and is updated and stored in the area 317. It

(2) Operation of prediction table creation mode First, the case of creating a prediction table (list) of customers and items to be delivered and sold on the next scheduled delivery date will be described. When it is desired to create a prediction table for dates other than the current day, when the numeric data 22 is operated to input date data, the operations of steps 1, 2, 10 to 12 described above are performed. Note that on the current day, date data is not entered. When the designated date key 26a is pressed, the above-mentioned steps 1 to 6, 13,
The operations 18, 22, 27 to 32 are performed. afterwards,
The prediction key 26d is pressed. In response, the operations of steps 1 to 5 described above are performed, and it is determined in step 5 that the prediction key has been pressed, and the process proceeds to step 54.
At step 54, it is determined that the flag F6 is set. As a result, the designated date key 26
It is determined that a has been pressed. Then, step 5
At 5, the data contained in the next scheduled delivery date is read out. Specifically, the number n of days representing a certain range (for example, n = ± 2 or n = + 2) is added to the designated date (the current day if date data is not input), and the next delivery date is scheduled. Range is required. Then, for each customer code of the floppy disk 40, and the data of the registration data of the item code, which is included in the range of the next scheduled delivery date obtained by the calculation, is sequentially listed and the data is read. To be done. The data contents for each registration data read in this case are at least a customer code, an item code, and a quantity. In step 56, the data for each customer code and each item code read out in step 55 is given to the display 13 and displayed on the display 13. Therefore, in step 57, the customer code and item code within the range of the scheduled delivery date for the next time are listed and displayed on the display unit 13, and the data read in step 55 is given to the printer 14. To be Therefore,
Data for each customer code and item code within the next scheduled delivery date is printed and recorded by the printer 14 to create a schedule. After that, all the flags F1 to F8 are reset in step 42, and then the process returns to step 1.

As described above, there is an advantage that a list of customers corresponding to the scheduled delivery date for the next delivery can be easily and quickly created based on the registration data for each delivery sale. If you use this forecast table, you can automatically and quickly know the customers who have a strong need for delivery and sales, so you can improve the efficiency of delivery and sales and reduce the labor and cost required for delivery and sales. There is.

Next, the operation of creating a prediction table for each customer will be described. In this case, the customer code for which the prediction table is to be created is first input by the customer key 24. In response to this, the operations of steps 1 to 9 described above are performed. Then, the prediction key 26d is pressed. In response to this, the determination operation of steps 1 to 5 and 54 described above is performed. And
At step 54, it is determined that the flag F6 is not set, and the routine proceeds to step 58. Step 5
8, it is determined that the customer key 24 has been operated based on the flag F3 being set. Then, in step 59, the registration data matching the customer code designated by the operation of the customer key 24 is searched, and the registration data matching the customer code is read from the floppy disk 40. Then, in step 56, the data for each item code of the same customer code read in step 59 is displayed on the display 13. In step 57, data for each item code of the same customer code is printed and recorded by the printer 14. in this way,
If you create a forecast table for the same customer, even if you have the same customer but have different scheduled delivery dates, you can piggyback on other products when you deliver one product, making the delivery and sales more efficient. There is an advantage that it can be further improved.

Next, the case of creating a forecast table for each item code will be described.
In this case, the item key 23 is first operated to specify the desired item for which the prediction table is to be created. Accordingly, the operations of steps 1 to 6, 13, and 18 to 21 described above are performed, and thereafter, the prediction key 26d is pressed. Accordingly step 1
The determination operation of ~ 5, 54, 58 is performed. At step 58, it is determined that the flag F1 is not set, and the routine proceeds to step 60. In step 60, the item key 23 is determined based on the set state of the flag F4.
It is determined that the operation has been performed. Then, Step 61
In step 3, the registration data registered in the floppy disk 40 is searched based on the item code designated by the operation of the item key 23, and the registration data including the item corresponding to the designated item code is sequentially read. To be done. Here, the purpose of creating a schedule by item code is
This is to know when and how many kinds of products will be sold. Therefore, in this case, it is necessary to read at least the quantity data and the next scheduled delivery date data. Thereafter, the data in which the item codes match is displayed and printed, as in the case of steps 56 and 57 described above. In this way, printing data for each item code on the forecast table has an advantage that inventory management and sales forecast can be easily performed.

Next, a case of creating a prediction table for each district code, which is a feature of the present invention, will be described. In this case, first, the numeric key 22
Is operated to specify a desired district for which a forecast table is to be created. Accordingly, the same operation as in the case of steps 1, 2, 10 to 12 described above is performed. After that, when the district key 26c is pressed, the same operation as in steps 1 to 6 and 13 to 17 described above is performed. Furthermore, the prediction key 26d
When is pressed, the above steps 1 to 5, 54, 58,
A determination operation of 60 is performed. Then, in step 60, it is determined that the flag F4 is reset, and the process proceeds to step 62. In step 62, it is determined that the flag F8 is set. Accordingly, in step 63, the area 411 for each customer code registered in the floppy disk 40 is searched, and the registration data of the same district code as the district code stored in the buffer 32 is sequentially read. Thereafter, in steps 56 and 57, registration data (customer code, item quantity, next delivery date, etc.) with the same district code are displayed and printed. In this way, if it is possible to create a prediction table that prints registration data for each customer for the same district code, when delivering and selling to a certain customer, it is piggybacked on the delivery and sales to customers in the same district (neighborhood) as that customer. There is an advantage that it can be performed and the efficiency of delivery and sale can be further enhanced. As a result, it is possible to reduce costs such as gasoline costs.

As described above, according to the present invention, it is possible to create a forecast table of customers belonging to the same area based on the data sold so far, it is possible to sell efficiently, it is possible to reduce the labor and cost required for sales, It has unique effects such as improved profitability. Further, according to the present invention, the next scheduled sales date for each customer in the same area can be easily and previously known, so that it is possible to provide detailed service to the customer and increase the number of customers. is there.

[Brief description of drawings]

FIG. 1 is a block diagram of a delivery sales data management device according to an embodiment of the present invention. FIG. 2 is an illustrative view showing details of the keyboard. FIG. 3 is a diagram schematically showing a storage area of the memory. FIG. 4 is a diagram schematically showing a storage area of a floppy disk. 5A and 5B are diagrams schematically showing the operation procedure for explaining the operation of the present invention. 6A to 6D are flowcharts for explaining the operation of this embodiment. In the figure, 10 is a delivery and sales data management device, 11 is C
PU, 12 is a clock, 13 is a display, 14 is a printer (printing means), 15 is a magnetic recording / reading device, 20 is a keyboard (registration means), 30 is a memory, and 40 is a floppy disk (storage means).

 ─────────────────────────────────────────────────── ─── Continuation of the front page (72) Inventor Shunzo Tateishi 10 Tatedo-cho, Hanazono, Ukyo-ku, Kyoto City, Kyoto Prefecture Tateishi Electric Co., Ltd. (56) Reference JP-A-56-111963 (JP, A)

Claims (4)

[Claims] 1. A device for managing data obtained when repeatedly selling to a fixed customer, wherein the registration means registers sales data for each customer, and the sales for each customer registered by the registration means. Based on the data, the calculation means for obtaining the expected date data to be sold next time, the district data and the storage means for storing the expected date data obtained by the calculation means for each customer, and the district designation for designating the district where the table should be created Means for responding to the designation of the area for which a table is to be created by the area designating means, correspondence between the planned date of next sale and the customer for each common area data stored by the storage means A sales data management device equipped with a printing means for creating a table showing. 2. The registration means includes merchandise data input means for inputting data on merchandise to be sold, and the storage means stores merchandise data input by the merchandise data input means for each customer. The sales data management device according to claim 1, further comprising an area, wherein the printing unit includes a unit that creates a table showing a relationship between the customer to be sold next time and the product data. 3. The registration means includes area data input means for inputting data relating to a customer-specific area, and the storage means stores area data input by the area data input means for each customer. The sales data management device according to claim 1 or 2, including an area. 4. The registration means includes a customer-specific key, and the storage means includes a registration table that presets and registers a customer code and a district code corresponding to the customer-specific key. The sales data management device according to item 1 or 2.