JPH05250571A - Marchandise sale data processor - Google Patents

Abstract

PURPOSE:To perform unit-price sales control even over the same marchandise. CONSTITUTION:An marchandise sale data processor with a marchandise unit- price setting varying function generates a sales registration data file (13B) so that individual and the respective sales amounts of money can be stored by different marchandise unit prices for the same marchandise code (JAN2) while made to correspond to each other, and is equipped with storage field specifying means (11 and 12), unit-price sales amount adding means (11 and 12), and cumulative sales amount rewriting means (11 and 12); and the cumulative sales amounts of money of respective new unit prices which are varied by the setting varying function are stored individually, not to mention original unit prices.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a product sales data processing device having a product unit price setting changing function. In particular, it relates to a processing device capable of managing sales by unit price.

[0002]

2. Description of the Related Art FIG. 6 shows a POS system type product sales data processing device. In the figure, mass terminal 1
0M, multiple satellite terminals 10A, 10B, 1
0C, ... Are connected to loop transmission lines, each of which is formed of an electronic cash register. A file controller 40 manages all terminals (10),
Furthermore, data can be transmitted to the higher-level device 100.
A center table 50 is composed of a product data file 50A and a sales registration data file 50B common to all terminals (10).

In such a configuration, the product code is entered at each terminal (10) and the file controller 4
Product data transferred from 0 (product name, unit price, etc.)
Use to register sales, and display or print out the contents. Further, the sales registration data is stored in the sales registration data file 50 via the file controller 40.
Stored in B. Therefore, the product data file 50
Common product data stored in A can be used for smooth product sales data processing, and sales registration data file 50B
By creating a report from the contents of, it is possible to comprehensively manage sales indicators including sales management. Further, since the sales registration file 50B stores the total sales amount for each product code (for example, JAN code), the sales management for each terminal (10) and the sales management for each product code can be performed.

By the way, in many stores, for example, fresh food may be sold at a discounted unit price during the period just before the store is closed and during seasons during a certain period. In terms of equipment, the unit price corresponding to the product code in the product data file 50A is set and changed by the setting change function, or the original unit price stored in the product data file 50B is not changed and stored in another memory only during the discount period. Sales are registered using the temporarily set discount unit price.

In addition, an independent electronic cash register (1) which does not take the POS system format and which has a product data file (50A) and a sales registration data file (50B) built therein.
Even when the apparatus is configured only with 0), the sales data is similarly processed.

[0006]

However, it has been pointed out that the above-mentioned conventional structure cannot quantitatively grasp the effect of discount (discount) sales. That is, even if the total sales amount of products of the same product code can be grasped, it is impossible to understand how the discount effect relates to the sales performance because the ratio of the fixed price sales amount and the discount sales amount is unknown. In addition, there is a problem in that it is difficult to know what percentage of the discount rate will be effective.

An object of the present invention is to provide a product sales data processing device capable of managing sales by unit price of the same product.

[0008]

A product sales data processing device according to the present invention, in a product sales data processing device having a function of changing a unit price of a product, associates a product code of a product registered for sales with its sales amount. And a sales registration data file that can be stored and stored separately for each different product unit price for the same product code, corresponding to each product code, and each sales registration procedure A storage column specifying means for searching the sales registration data file to identify the storage column in which the product code and the product code and the product unit price that are the same as the product code and the product unit price corresponding to the sales registration procedure are stored, and the sales registration procedure. Each unit price is calculated by adding the current sales amount to the total sales amount up to that point stored in the specified memory column An upper amount adding means and a total sales amount rewriting means for rewriting the total sales amount stored in the specified storage column to the current total sales amount obtained by the unit price sales amount adding means are provided. Characterize.

[0009]

In the present invention having the above-described structure, when the sales registration procedure is performed, the storage column specifying means searches the sales registration data file and the corresponding product code and the same product code and the same product unit price are stored correspondingly. Specify the memory column that has Then, the unit price-based sales amount adding means adds the current sales amount to the total sales amount up to that time stored in the specific storage field to obtain the current total sales amount. Here, the cumulative sales amount rewriting means operates to rewrite the cumulative sales amount up to that time stored in the specific storage column to the calculated current sales amount. Therefore, even for products with the same code, it is possible to know the cumulative amount of sales by unit price, so that it is possible to easily manage sales by unit price.

[0010]

Embodiments of the present invention will be described with reference to the drawings.
As shown in FIG. 1, the product sales data processing device is composed of an electronic cash register 10 having a product data file 13A and a sales registration data file 13B built therein, and the sales registration data file 13B has a unit price for the same product code. It is formed so that the sales amount can be stored for each different type, and the storage column specifying means (1
1, 12), unit price sales amount adding means (11, 12) and cumulative sales amount rewriting means (11, 12) are provided so that sales management by unit price can be performed for the same product.

First, as shown in FIG. 1, the electronic cash register 10 includes a control unit including a CPU 11, a ROM 12, a RAM 13, etc., and a scanner 19 (scanner circuit 1).
5), a keyboard 20 (keyboard circuit 16), a display 21 (display control circuit 17), a printer 22 (printer drive circuit 24), a drawer 23 (drawer opening device 25), etc. connected via the input / output port 18. It is formed including. Reference numeral 14 is a clock circuit, and 31 is an interface.

Here, the product data file 13A is R
It is formed with a partial area of the AM 13 and stores product data including the product name, unit price, etc. for each product code (for example, JAN code) as shown in FIG. On the other hand, the sales registration data file 13B is also formed with a partial area of the RAM 13, and as shown in FIG. 3A, the unit price and the total sales amount (DATA) for each product code (CODE).
Store sales registration data such as. In the case of FIG. 3B, the cumulative sales amount of the product with the product code (JAN2) is “200 yen”. The unit price storage area is provided in relation to the present invention, and its value (“0
00 ") has no relation to the unit price of the product, and the details will be described later.

In the electronic cash register 10 as described above,
When the cashier inputs the product code using the scanner 19 or the keyboard 20, the CPU 11 reads the product data from the product data file 13A in FIG.
Temporarily store in M13. When the sales registration procedure is performed using the total key or the like, the sales registration data file 13B is registered and stored. The sales registration data is displayed on the display unit 21 at a proper time and printed by the printer 22. Therefore, the sales amount for each product code can be managed. Since the electronic cash register 10 itself is publicly known, further description will be omitted.

Here, the technical feature of the present invention is that the sales registration data file 13B is first shown in FIG.
(F) As shown in (a) to (d), product unit prices (“000”, “200” for the same product code (JAN2).
The product code (JAN2) and each sales amount (55 yen)
0,400,150,0 yen) is formed correspondingly. Therefore, in the sales registration data file 13B, it is possible to store all target product codes and fixed prices (original unit prices) corresponding to the respective product codes, as well as all changed unit prices that will be changed later. Although a storage field may be provided in advance in this embodiment, in order to mainly reduce the capacity of the sales registration data file 13B and speed up the search, the unit price is changed by the setting change tracking program shown in FIG. 5 in this embodiment. When the procedure is performed, the storage field is formed as a new one.

That is, in FIG. 5, the unit price of the product data file 13A of FIG. 2 is changed from the original unit price (eg, 200 yen) to the new unit price (eg, 150) by the general unit price change procedure.
When the setting is changed to (Yen) (ST20), as shown in FIG. 3 (C), if there is no storage field for the old unit price (unit price previously changed) (NO in ST21), the original unit price (200 yen) )
(ST23) to create a memory field [FIG. 3 (D) (b)]
DATA in the storage field (a) that is the unit price (“000”)
The accumulated sales amount stored in the area (for example, 40
(0 yen) is additionally stored as the cumulative sales amount (400 yen) of the storage column [same (D) (b)] (ST24). In addition,
When there is no unit price (“000”) storage field (ST2
No storage unit for new unit price is created in No. 2). Continued,
A storage field [same (D) (c)] of the new unit price (150 yen) is created (ST25). On the other hand, there is a storage field for the old unit price (ST
If the storage unit for the same unit price still exists (YES in 21) (YES in ST26), the storage unit for the new unit price is not created,
A storage unit for a new unit price is created only when there is no storage unit for the same unit price (NO in ST26) (ST25).

In other words, while the product is being sold at the original unit price (200 yen) of the product code (JAN2), it is shown in FIG.
As shown in (H), only the storage column (a) may be provided. However, if there is a unit price change, since the total amount of each sales amount of each unit price is stored in the storage column (a) after that, the accumulated sales amount (400 yen) of the original unit price (200 yen) is sold. ST to remember as clear
A memory column (b) is newly provided at 23 and 24. Here, the value stored in the unit price storage area of the storage column (a) is set to "0" above.
00 ".

However, for example, in the state shown in FIG. 3 (E), when the storage column (c) of the old unit price (150 yen) exists (YES in ST21), the unit price is further increased from 150 to 170.
When the setting is changed to yen, a new storage unit [same (F) (d)] of the new unit price (170 yen) is newly created (ST25).
Just enough.

Now, the storage column specifying means searches the sales registration data file 13B of FIG. 3 every time the sales registration procedure is performed, and the same product code as the product code (eg JAN2) and the unit price (eg 150 yen). (JAN2)
And a unit for identifying a storage field in which the unit price of goods (150 yen) is stored correspondingly, which comprises a CPU 11 and a ROM 12 and is executed in ST14 of FIG. For example, FIG. 3 (D)
In the state shown in (1), when the product with the product code (JAN2) is sold at the unit price (150 yen) and the sales registration procedure is performed, the storage column [(c)] is specified.

Next, the unit-by-unit-sale-amount-addition means adds up the accumulated sales amount up to that point (0 yen) stored in the storage column [eg (D) (c)] specified each time the sales registration procedure is performed. ) Is added to the present sales amount (150 yen) to obtain the present total sales amount (150 yen = 0 + 150), which is composed of the CPU 11 and the ROM 12, and is ST15 of FIG.
Run on.

Here, the cumulative sales amount rewriting means calculates the cumulative sales amount of this time calculated by adding instead of the cumulative sales amount (0 yen) stored in the DATA storage area of the storage column (c). Rewrite to the amount of money (150 yen), CPU
11 and ROM 12. Therefore, the contents of the memory column [(c)] are rewritten from 0 yen in FIG. 3 (D) (c) to 150 yen shown in (E) (c) (ST1).
6).

It should be noted that the unit for adding the sales amount by unit price and the unit for rewriting the total sales amount are integrated into the current sales amount (150
The cumulative sales amount (0) in the specific memory column [(D) (c)]
It can also be implemented by directly adding to (yen).

Next, the operation of this embodiment will be described. The product data file 13A shown in FIGS. 1 and 2 stores the fixed price (original unit price) of each product of the product codes JAN2 and JAN4, and the sales registration data file 1 shown in FIG.
It is assumed that no sales are registered in 3B.

Here, there is a procedure for registering sales of a JAN2 product at the original unit price (200 yen) (ST in FIG. 4).
10), and the CPU 11 causes the sales registration data file 13B
It is determined whether or not there is a storage field [(a)] for the original unit price (unit price storage area is "000") (ST11). If not, a storage field [(a)] of "000" shown in FIG. 3B is created (ST12). Then, the sales amount (20%) is added to the DATA storage area of this newly established storage column [(a)].
0 yen) is added and stored (ST13). The result is the same (B)
It is as shown in (a). Furthermore, the fixed price (original unit price) [2
When sales are registered for [00 yen], it becomes as shown in (C) (a). That is, the storage column (a) stores the total sales amount of the products related to the code so far.
However, the procedure so far is the same as that of the conventional example.

Here, by operating the keyboard 20, the original unit price of the product of the product code (JAN2) (200
Suppose that the yen was changed to a new unit price (150 yen). In this case, the value in the unit price storage area of the product data file 13A shown in FIG. 2 is 200 → 150 yen (ST2 in FIG. 5).
0).

Then, the setting change following program works,
The new unit price (150) in the sales registration data file 13B
The memory column of is newly established. That is, as shown in FIG. 3C, the sales registration data file 13B has no storage field for the old unit price [unit price previously changed (non-original unit price)] (S
Since there is a storage column for (NO in T21) and unit price "000" (YES in ST22), a storage column [(b)] for the original unit price (200 yen) is created as shown in (D) (ST23).
In addition, the cumulative sales amount (400 yen) stored in the DATA area of the memory column (a) registered for sale at the original unit price (200 yen) up to that time is converted into the DA of the memory column [(b)].
It is stored in the TA storage area (ST24). Here, in the same (D), from the storage column [(a)] to the total sales amount of the corresponding code (JAN2) products so far (400
The total sales amount (400 yen) sold at the original unit price (200 yen) from the memory column [(b)]
Can know. However, at this stage both 400
It is a circle.

After the above treatment, a storage field [(c)] of the changed unit price, that is, the new unit price (150 yen) is created (ST25). It should be noted that "0 yen" is stored in the DATA storage area of the storage column (c) of FIG. 3D because sales have not been registered yet.

Then, the new unit price of the product code JAN2 (1
If one item is sold for 50 yen and the sales registration procedure is performed (ST10 in FIG. 4), YES in ST11.
Since the determination is made, 150 yen is added to the storage field (a) of the same (D). In other words, the DA of the memory column (a) of the same (D)
The value of TA storage area is 550 yen (= 400 + 150)
(ST13).

Here, the storage column specifying means (11, 12) operates and the product code (JA) for which the sales registration procedure has been performed.
N2) and the storage column in which the same product code and unit price as the unit price (150 yen) are stored correspondingly are specified. In this case, there is a storage field (c) with the same unit price shown in FIG. 3D (YES in ST14). Then, the unit price-based sales amount adding means (11, 12) reads the total sales amount up to that time (“0” in this case) read from the specific storage column [(D) (c)].
Yen ”) and the current sales amount (150 yen) are added to obtain the current cumulative sales amount of 150 yen (= 0 + 150) (ST
15). Continued sales amount rewriting means (11, 12)
Is the cumulative sales amount up to that point (0 yen) stored in the DATA storage column of the specific storage column [(D) (c)],
It is rewritten to the cumulative sales amount (150 yen) obtained this time (ST16). Therefore, the unit price (1
The memory column of (50 yen) is as shown in FIGS.

In the states shown in (E) and (c), the unit price of the product code JAN2 is 150 → 170.
When the setting is changed to a circle, this time YE in ST21 of FIG.
S determination is made and NO determination is made at ST26. In other words, the same unit (E) has the storage unit (c) for the old unit price (150 yen) but does not have the storage unit for the same unit price (170 yen).
In this case, as shown in (F), a new unit price (170 yen) storage field (d) is immediately established (ST25). ST2
3, 24 are bypassed. If YES is determined in ST26, the new unit price storage field is not created.

The same applies to products having a product code (JAN4) as shown in (H). The same (H) shows the case where the original unit price (400 yen) shown in FIG. 2 is changed to the new unit price (350 yen) and one product is registered for sale at the new unit price (350 yen). This is the case where there was no sales at the original unit price (400 yen).

According to this embodiment, however, the sales registration data file 13B is separately formed for the same product code for each different product unit price so that the product code and each sales amount can be stored in correspondence with each other. Memory column identification means (11,
12), unit price-based sales amount adding means (11, 12) and cumulative sales amount rewriting means (11, 12) are provided, and the cumulative sales amount of each new unit price changed by the setting change function as well as the original unit price Since the amount of money can be stored separately, it is possible to easily manage sales by unit price of the same product. In other words, since the ratio between the fixed price sales amount and the discount sales amount becomes clear, it is possible to quantitatively and accurately determine how the discount effect relates to the sales results, and what percentage of the discount rate the sales amount will rapidly increase. Can be managed.

The sales registration data file 13B also stores the total amount of sales for products of the same code that have been registered for sales regardless of the sales unit price. Performance evaluation is also possible.

Further, since the setting change follow-up program shown in FIG. 5 is provided and a unit price storage field is newly created (ST25) when the unit price is actually changed, the sales registration data file 13B is formed. The capacity can be reduced and the search speed can be increased.

Although the present embodiment is formed by using the independent electronic cash register 10 in the above embodiment,
This may be implemented as the POS system type shown in FIG. 6 above. In this case, the product data file (13A)
And the sales registration data file (13B) are controlled by the file controller 40, the center table 50.
It is better to store in.

When sales are registered (ST in FIG. 4)
Create a unit price storage field of "000" in YES of 10 (ST1)
2) and when there is a storage field for "000" unit price (Fig. 5)
Create a new unit price storage field in (ST22: YES) (ST2
5) As a thing to do, it was easy to manage the unit price with sales registration, but a new unit price storage field was created and changed every time the unit price was changed regardless of whether sales registration was made or not. The unit price can also be configured and implemented so that it can be determined that it is difficult to sell.

[0036]

According to the present invention, the sales registration data file is formed so that the product code and each sales amount can be separately stored for the same product code for each different product unit price, and the storage column is specified. A means, a unit for adding sales amount by unit price, and a unit for rewriting total sales amount are provided so that the total sales amount can be separately stored not only for the original unit price but also for each new unit price changed by the setting change function. Therefore, it is possible to easily manage sales by unit price of the same product. In other words, since the ratio between the fixed price sales amount and the discount sales amount becomes clear, it is possible to quantitatively and accurately determine how the discount effect relates to the sales results, and what percentage of the discount rate the sales amount will rapidly increase. Can be managed.

[Brief description of drawings]

FIG. 1 is an overall configuration diagram showing an embodiment of the present invention.

FIG. 2 is likewise a diagram for explaining a product data file.

FIG. 3 is also a diagram for explaining a sales registration data file.

FIG. 4 is a flow chart for explaining sales registration operation by unit price.

FIG. 5 is likewise a flowchart for explaining the operation of creating a storage field for each unit price.

FIG. 6 is a diagram for explaining a conventional example.

[Explanation of symbols]

10 Electronic Cash Register (Merchandise Sales Data Processing Device) 11 CPU (Memory Column Specification Means, Unit Sales Price Addition Means, Cumulative Sales Rewriting Means) 12 ROM (Memory Column Specification Means, Unit Price Sales Price Addition Means, Cumulative Sales) Amount rewriting means) 13 RAM 13A Product data file 13B Sales registration data file 19 Scanner 20 Keyboard 21 Display 22 Printer

Claims (1)

[Claims] 1. A product sales data processing device having a product unit price setting change function, wherein a product code of a product registered for sale and its sales amount can be stored in correspondence with each other, and a product unit price of the same product code can be stored. Sales registration data file that can be stored separately for each different product code and sales amount, and the product for which sales registration data file is searched each time sales registration procedure is performed and sales registration procedure is performed A storage column specifying means for specifying a storage column in which the same product code and unit price as the product code and the corresponding product unit price are stored, and it is stored in the storage column specified each time the sales registration procedure is performed. The total amount of sales up to is added to the total amount of sales this time to calculate the total amount of sales this time. Commodity sales data processing apparatus, characterized in that it provided, and written replace total sales amount rewriting means to the current total sales amount of money obtained by the unit price sales amount adding means the total sales amount.