JP4005455B2 - Product sales registration device - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a merchandise sales registration device such as an electronic cash register or a POS (Point Of Sales) terminal, and in particular, sells merchandise in two or more sales forms such as over-the-counter sales and delivery sales. The present invention relates to a merchandise sales registration device for retailers who sell.
[0002]
[Prior art]
Some merchandise sales registration apparatuses that register sales in a memory area by inputting data related to merchandise sales have a PLU (Price Look Up) registration function. The apparatus having this function is provided with a PLU file storing item data such as unit price, number of sales points, sales amount, etc. corresponding to each PLU code set for each product. When the PLU code of the sales product is input, the unit price stored in correspondence with the PLU code is read, the sales price of the sales product is calculated from the unit price and the sales point, and the sales point and sales price are calculated. Are added to the sales point data and sales amount data corresponding to the PLU code of the PLU file, respectively. With this function, sales of each product can be aggregated by product.
[0003]
In addition, corresponding to each product group code set for each product group that classifies each product, a product group file storing item data such as the number of sales points and sales amount is provided, and the product item is stored in the data item of the PLU file. Add a group code. When the PLU code of the sales product is input, the product group code is read together with the unit price stored in correspondence with the PLU code, and the sales score and the sales price are registered in the PLU file. In some cases, registration processing is added to the sales point data and sales amount data corresponding to the product group code. With this function, sales of each product can be classified and totaled by product group.
[0004]
[Problems to be solved by the invention]
In the conventional merchandise sales registration device, although sales of products for which a PLU code has been input can be tabulated separately for each PLU code and for each product group, there is only one type of product group code that can be set in the PLU file. Sales of products to which one PLU code is assigned cannot be aggregated as sales of different product groups due to, for example, differences in sales forms.
[0005]
Many retail stores that sell liquor, rice, etc., provide services that deliver products purchased by customers to places specified by customers, such as homes. In such stores, there is a demand to manage the sales of products separately for the sales at the store where the sales products are delivered at the store and the sales at the delivery where the sales products are delivered later by the delivery service. By performing such management, for example, it becomes easy to grasp the ratio of over-the-counter sales and delivery sales for each product or product group. However, in the conventional merchandise sales registration device, the sales of each product cannot be classified and tabulated according to the sales form, and thus the above-mentioned demand cannot be satisfied.
[0006]
Therefore, the present invention is intended to provide a product sales registration apparatus that can classify and tabulate sales of each product according to the sales form.
[0007]
[Means for Solving the Problems]
The product sales registration apparatus of the present invention is Corresponding to the PLU code set for each product, a PLU file for storing the sales price per product, the department code to which the product belongs, and the department file for storing the sales amount for each department code, Input means for inputting the PLU code of the product for sale; Sales form declaration means for declaring a specific sales form And Establishment The Enter By force When the PLU code is input, the file search means searches the PLU file and acquires the sales price and the department code corresponding to the input PLU code. Also, The sales form judgment means For products for which a PLU code has been entered Determine whether a specific form of sale has been declared. as a result, It is determined that no specific form of sale has been declared. Then, the sales price searched by the file search means is added to the sales amount corresponding to the department code searched by the file search means of the department file. To do. In contrast, It is judged that a specific sales form has been declared Then, a predetermined number is added to the department code searched by the file search means. Then, the sales price searched by the file search means is added to the sales amount corresponding to the calculated department code of the department file. To do.
[0008]
With this configuration, a specific sales form is declared by the sales form declaring means. Not State by input means PLU code of the product for sale Is entered, The sales price stored in the PLU file corresponding to the PLU code is added to the sales amount of the department file corresponding to the department code stored in the PLU file corresponding to the PLU code. Is done. On the other hand, by means of sales form declaration A specific form of sale is declared Ru State by input means PLU code for this product Is entered, A predetermined number is added to the department code stored in the PLU file corresponding to the PLU code to change the department code. Then, the sales price stored in the PLU file corresponding to the input PLU code is added to the sales amount corresponding to the changed department code in the department file. Is done. Therefore, even if the product is the same, when a specific form of sale is declared and when it is not declared The sales price of the product is added to the sales amount corresponding to the different department code in the department file. Is done.
[0009]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, an embodiment of the present invention will be described with reference to the drawings.
In this embodiment, in an electronic cash register used in retail stores, for example, liquor stores, which have two types of sales forms of over-the-counter sales and delivery sales, the over-the-counter sales are set as the basic sales form, and delivery sales are specified. This is the case of sales form.
[0010]
FIG. 1 is a perspective view showing an external configuration of an electronic cash register 1 according to the present embodiment. The electronic cash register 1 is provided with a keyboard 2 and a mode switch 3 on the front side of the top surface, and for the operator on the back side of the top surface. A display 4 and a customer display 5 are provided. Further, a printer 6 for performing receipt printing and journal printing is built in, and a receipt printed by this printer is discharged from a receipt issuing port 7 on the upper left side. Furthermore, the drawer 9 for accommodating cash etc. is formed in the front lower part.
[0011]
As shown in FIG. 2, the keyboard 2 has a numeric key 21 of “00” and “0” to “9”, a plurality of preset PLU keys 22 each preset with a different PLU code, and a PLU key 23. Various function keys such as a multiplication key 24, a clear key 25, a subtotal key 26, a deposit / current total key 27 as a registration closing key, a delivery declaration key 28, and a cancel key 29 are arranged. The delivery declaration key 28 functions as a sales form declaring means for declaring a delivery sale which is a specific sales form.
[0012]
The mode switch 3 is a control switch for selecting various business modes such as “registration”, “inspection”, “settlement”, “setting” and instructing the execution thereof, and is switched by a key. Incidentally, “registration” is a business mode in which sales of products are registered in the memory area based on data related to product sales input via the input means. “Inspection” is a business mode in which data in the memory area registered by “registration” is printed out on a recording sheet as a sales inspection report. “Checkout” is a mode of business in which the memory area is cleared after the data in the memory area is printed on a recording sheet as a sales checkout report in the same manner as “check”. “Setting” is a job mode in which data necessary for executing various jobs is set in a memory area in advance.
[0013]
FIG. 3 is a block diagram showing the internal configuration of the electronic cash register 1. The electronic cash register 1 includes a CPU (Central Processing Unit) 10 as a control unit body. Further, a ROM (Read Only Memory) 11 in which fixed data such as a program executed by the CPU 10 is stored in advance, a RAM (Random Access Memory) 12 in which a memory area for registering sales of each product is formed, A clock unit 13 for measuring the date and time of the device, a signal from the mode switch 3 is input, an I / O port 14 for outputting a drive signal to the opening mechanism of the drawer 9, and a keyboard controller for capturing key input data from the keyboard 2 15. The first display controller 16 for controlling the operator display 4 to display data, the second display controller 17 for controlling the customer display 5 to display data, and the printer 6 to perform data printing. A printer controller 18 and the like are provided. Then, the CPU 10, the ROM 11, the RAM 12, the clock unit 13, the I / O port 14, the keyboard controller 15, the first and second display controllers 16, 17 and the printer controller 18 are connected to a bus line such as an address bus or a data bus. 19 is connected to constitute a control circuit for the electronic cash register 1.
[0014]
The electronic cash register 1 having such a configuration, as shown in FIG. 4 in the RAM 12, has a PLU name corresponding to each PLU code set for each product, and a unit price that is a selling price per product. , Link department code (this link department code is the first memory area setting information), PLU file 41 storing item data such as the number of sales points, sales amount, etc., and the department name and sales corresponding to each department code A department file 42 that stores item data such as points and sales amount, a totalizer 43, a work memory 44, and a flag memory 45 for a delivery flag are formed.
[0015]
The department code is a store sales department code assigned to each of a plurality of groups obtained by classifying each product sold at the store, and a predetermined number “10” for each store sales department code (this predetermined number “10”). "Is the second memory area setting information), and the delivery department code is calculated. In the PLU file 41, the store sales of the group to which the product belongs corresponds to the PLU code of each product. Department codes are stored as link department codes on a one-to-one basis. The department file 42 also includes a first memory area 42-1 storing item data such as department name, number of sales points, sales amount, etc. corresponding to each store sales department code, and each delivery department code. A second memory area 42-2 is formed, which stores item data such as the department name, the number of sales points, and the sales amount. Each store department code is set as a link department code of the PLU file 41, but each delivery department code is not set as a link department code of the PLU file 41.
[0016]
Thus, when the delivery declaration key 28 of the keyboard 2 is input in the state where the “registration” mode is selected by the mode switch 3, the CPU 10 executes the processing shown in the flowchart of FIG. First, as ST (step) 1, it is determined whether or not the delivery flag in the flag memory 45 is set to “1”. If the delivery flag is not set, the delivery flag is set to “1” as ST2. Thereafter, if the comment “Declaring delivery” is displayed on the operator display 4 in ST3, the delivery declaration key process is terminated. If the delivery flag is set in ST1, this delivery declaration key process is terminated without performing the processes in ST2 and ST3.
[0017]
Similarly, when the cancel key 29 is input while the “registration” mode is selected, the CPU 10 executes the process shown in the flowchart of FIG. First, in ST11, it is determined whether or not the delivery flag in the flag memory 45 is set to “1”. If the delivery flag is set, the delivery flag is reset to “0” as ST2. Thereafter, if the comment “Declaring delivery” displayed on the operator display 4 is deleted in ST3, the cancel key process is terminated. If the delivery flag is not set, the immediately preceding cancellation process for canceling the sales of the product registered immediately before is executed.
[0018]
Similarly, when the “registration” mode is selected and the PLU code is input by the preset PLU key 22 or the numeric key 21 and the PLU key 23, the CPU 10 performs the processing shown in the flowchart of FIG. Execute. First, in ST21, each item data of name, unit price and link department code stored in correspondence with the input PLU code is read from the PLU file 41. Next, in ST22, it is determined whether or not the delivery flag is set to “1” (sales form determination means).
[0019]
If the delivery flag is not set, the link department code read from the PLU file 41 is overwritten and stored in the work memory 44 as ST23. Next, in ST24, the sales points (if a multiplier is input by the numeric key 21 and the multiplication key 24 immediately before the input of the PLU code) are input to the unit price read from the PLU file 41 as ST24. If not, the sales amount is calculated by multiplying 1), and this sales amount is displayed on the operator display 4 and the customer display 5 together with the name read from the PLU file 41. In ST25, the name and the sales amount are printed on the receipt paper and the journal paper by the printer 6. Further, in ST26, the sales amount is added to the totalizer 43. Thereafter, in ST27, the sales point number and the sales amount data are added and registered to the sales point number data and the sales amount data of the PLU file 41 corresponding to the input PLU code. In ST28, the sales score and sales amount data are added and registered to the sales point data and sales amount data of the department file 42 corresponding to the department code in the work memory 44 (first sales registration processing means). Thus, the current PLU code input process is completed.
[0020]
On the other hand, if the delivery flag is set in ST22, the link department code read from the PLU file 41 is overwritten and stored in the work memory 44 in ST29, and then the department code in the work memory 44 is predetermined as ST30. The number N (N = 10 in this embodiment) is added. Next, as ST31, the unit price read from the PLU file 41 is multiplied by the sales points to calculate the sales amount, and the sales amount is loaded on the operator display 4 and the customer display 5 together with the name read from the PLU file 41. Display. Next, after the character information “delivery” is printed on the receipt paper and the journal paper by the printer 6 in ST32, the name and the sales amount are similarly printed on the receipt paper and the journal paper by the printer 6 in ST33. Next, in ST34, the sales amount is added to the totalizer 43. In ST35, the sales point number and the sales amount data are added and registered to the sales point number data and the sales amount data of the PLU file 41 corresponding to the input PLU code. Further, as ST36, the sales point number and the sales amount data are added and registered to the sales point number data and the sales amount data of the department file 42 corresponding to the department code in the work memory 44 (second sales registration processing means). Thereafter, the delivery flag is reset to “0” as ST37 (declaration canceling means), and if the comment “delivery declaration” displayed on the operator display 4 is deleted as ST38, the current PLU code input process is performed. Exit.
[0021]
Similarly, when the deposit / cash key 27 is input in a state where the “registration” mode is selected, the CPU 10 calculates the total amount and deposit amount calculated based on the amount data in the totalizer 43. The change amount is calculated from (if the numeric data is entered immediately before the deposit / actual key 27 is input, the numeric value is entered, and if not, the total amount is entered). Then, the change amount is displayed on the operator display 4 and the customer display 5. Further, the total amount, deposit amount, change amount, etc. are printed on receipt paper and journal paper by the printer 6 and a receipt is issued from the receipt issuing port 7. Thereafter, when a drive signal is output from the I / O port 14 to the opening mechanism of the drawer 9 to automatically open the drawer 9, the totalizer 43 is cleared and the deposit / cash key input processing is terminated. .
[0022]
In the electronic cash register of the present embodiment configured as described above, when the PLU code of the sales product is input from the keyboard 2 as data related to the product sales in the “registration” mode, the sales score and the sales amount of this product are obtained. Addition registration processing is performed on the PLU file 41 and the department file 42, respectively. Sales are registered for the PLU file 41 in accordance with the input PLU code.
[0023]
On the other hand, for the department file 42, the memory areas in which sales are registered differ depending on whether the delivery flag is set or not. That is, when the delivery flag is not set, registration processing is performed in the memory area 42-1 of the link department code (store department code) set in the PLU file 41 corresponding to the input PLU code. When the delivery flag is set, registration processing is performed in the memory area 42-2 of the department code (delivery department code) calculated by adding a predetermined number (10 in this embodiment) to the link department code.
[0024]
The delivery flag is set when the delivery declaration key 28 is input immediately before the input of the PLU code. Thereafter, when the PLU code is input and the sales registration process for the product is executed, the delivery flag is automatically reset. Therefore, for example, when registering a product that a customer purchases at a store, when registering a product that the customer takes home, that is, a product sold at the store, the PLU code is input without inputting the delivery declaration key 28, and the delivery is performed. When registering the product requested for service, that is, the product for delivery sale, the delivery declaration key 28 is entered and then the PLU code is entered. Registration processing is performed in the memory area 42-1, and sales of the delivery sale product are registered in the second memory area 42-1.
[0025]
For example, in the state where the data shown in FIG. 4 is stored in the PLU file 41, one customer purchases two products A and one product B, of which only one product A is taken home, and the remaining products A And product B are requested to be delivered. In this case, the cashier inputs only the PLU code of the merchandise A when registering the sales of the take-out merchandise A, but when registering the sales of the merchandise A and B for which the delivery request is received, After inputting the delivery declaration key 28, the PLU code of the product A or the product B is input. As a result, the sales score “1” and the sales amount “1200” of the product A are registered in the first memory area 42-1 corresponding to the link department code DP11 of the product A in the department file 42. . On the other hand, in the second memory area 42-2 corresponding to the department code DP21 calculated by adding the predetermined number “10” to the link department code DP11 of the goods A and B, the sales score “1” of the goods A and The sales amount “1200”, the sales number “1” of the product B, and the sales amount “1000” are registered.
[0026]
Thereafter, when the cashier inputs the deposit / cash total key 27 and declares the closing of registration of the commercial transaction with the customer, a receipt 50 as shown in FIG. 8 is issued. The receipt 50 is printed with character information “delivery” on the product for sale, and is distinguished from the product for over-the-counter sales. Therefore, the delivery product and the over-the-counter product are easily identified from the contents of the receipt 50. it can.
[0027]
Note that the delivery flag set in response to the input of the delivery declaration key 28 is also reset when the cancel key 29 is input before the PLU code is input. Therefore, if the delivery declaration key 28 is input by mistake when registering the sales of the over-the-counter product, the cancel key 29 may be input. In this case, the comment “Delivery Declaration” is displayed on the operator display 4 in response to the input of the delivery declaration key 28, so that the cashier can easily notice the erroneous operation of the delivery declaration key 28.
[0028]
By the way, the sales data collected by the department code in the department file 42 is printed out as a settlement report 60 as shown in FIG. 9 by instructing the settlement of the department file 42 in the “settlement” mode, for example. . Therefore, the store side can confirm the sales by department of each product sold as over-the-counter sales and the sales by department of each product sold as delivery sale from the contents of the settlement report 60. As a result, even if it is the same product, it is possible to separately manage sales for sales sold at stores and sales for sales sold as deliveries.
[0029]
In the “inspection” mode, even if the content of the department file 42 is printed out as an inspection report by instructing the check calculation work of the department file 42, the sales and delivery by department of each product sold as over-the-counter sales. It goes without saying that it is possible to confirm the sales by department of each product sold as a sale.
[0030]
In the present embodiment, as information for designating the first memory area 42-1 of the department file 42, the store department code of each product is set as a link department code in the PLU file 41, and the store department code is predetermined. The number is calculated to calculate a delivery department code which is information for designating the second memory area 42-2. Accordingly, since the link department code set in the PLU file 41 is one type as in the conventional case, the existing PLU file can be applied as it is.
[0031]
The present invention is not limited to the one embodiment.
For example, in the above embodiment, the delivery flag is automatically reset in the process of ST37 of the PLU code input process, and then the comment “Delivery declaration in progress” is deleted in the process of ST38. The delivery flag may be reset only by inputting the cancel key 29, and the comment “Declaring delivery” may be deleted. In this way, when there are a plurality of products sold by delivery sales among products purchased by one customer, the sales declaration key 28 is entered first by continuously registering sales of these products. Can be simplified to one time.
[0032]
In the above-described embodiment, the case where the sales of the product for which the PLU code is input is registered with different department codes at the time of over-the-counter sales and at the time of delivery sales has been described. Registration processing may be performed. For example, in the case of over-the-counter sales, registration processing is performed in the memory area of the inputted PLU code, and in the case of delivery selling, “1” is added to the least significant digit of the inputted PLU code to generate a delivery selling PLU code. Registration processing is performed on the delivery sales PLU code. By doing so, it is possible to easily confirm the sales by item of each product sold as store sales and the sales by product of each product sold as delivery sale.
[0033]
In addition, as another embodiment for facilitating the confirmation of the sales by individual item of each product sold as over-the-counter sales and the sales by individual item of each product sold as delivery selling, the following configuration is also possible. . That is, as shown in FIG. 10, the PLU file 41 corresponds to each PLU code set for each product, along with the PLU name and unit price, and the sales amount and sales amount in the first memory area. It is assumed that the PLU file 70 is formed with an area 71 and a sales sales area 72 of sales points and sales amounts as the second memory area.
[0034]
Thus, in the state where the “registration” mode is selected, when the PLU code is input by the preset PLU key 22 or the numeric key 21 and the PLU key 23, the CPU 10 displays the flowchart of FIG. The process shown in is executed. It should be noted that the same parts as those in FIG.
[0035]
That is, the CPU 10 reads each item data of the name, unit price and link department code stored in correspondence with the input PLU code from the PLU file 41 as ST21, and then sets the delivery flag to “1” as ST22. If it is not set, the process of ST23 is omitted and the processes of ST24 to ST26 are executed. Thereafter, in place of the processing of ST27, the sales score and the sales amount are added and registered in ST41 to the sales point data and sales amount data in the store sales area 71 of the PLU file 70 corresponding to the input PLU code. Thus, the current PLU code input process is terminated, and the process of ST28 is omitted.
[0036]
On the other hand, if the delivery flag is set to “1” in ST22, the processes in ST29 and ST30 are omitted, and the processes in ST31 to ST34 are executed. Thereafter, instead of the process of ST35, the sales score and the sales amount are added and registered to the sales point data and the sales amount data in the delivery sales area 72 of the PLU file 70 corresponding to the input PLU code as ST42. Thereafter, the process of ST36 is omitted, and if the processes of ST37 and ST38 are executed, the current PLU code input process is terminated.
[0037]
In other embodiments configured as described above, in the “payment” mode, by instructing the settlement operation of the PLU file 70, the store sales area 71 and the delivery sales area 72 of the PLU file 70 are each classified by PLU code. Aggregated sales data is printed out as a settlement report. In this case, for example, by selecting and specifying the store sales area 71, as shown in FIG. 12A, a sales settlement report 81 for each single item only for products sold as store sales is obtained, or a delivery sales area 72 is obtained. By selecting and designating, as shown in FIG. 12B, it is possible to easily obtain a sales settlement report 82 for each item only for products sold as delivery sales.
[0038]
In each of the above-described embodiments, the over-the-counter sales are set as the basic sales mode, and the delivery sales are set as the specific sales mode. However, the delivery sales can be set as the basic sales mode, and the over-the-counter sales can be set as the specific sales mode. It is. The present invention can be similarly applied to sales forms other than store sales and delivery sales.
In addition to the above, it goes without saying that various modifications can be made without departing from the spirit of the present invention, such as scanning input of PLU codes.
[0039]
【The invention's effect】
As described above in detail, according to the present invention, it is possible to provide a merchandise sales registration apparatus capable of classifying and summing up sales of each merchandise according to sales form.
[Brief description of the drawings]
FIG. 1 is an external perspective view of an electronic cash register according to an embodiment of the present invention.
FIG. 2 is a view showing a keyboard of the electronic cash register.
FIG. 3 is a block diagram showing an internal configuration of the electronic cash register.
FIG. 4 is a view showing main memory areas of the electronic cash register.
FIG. 5 is a flowchart showing a main part of a delivery declaration key process executed by the CPU of the electronic cash register.
FIG. 6 is a flowchart showing a main part of a cancel key process executed by the CPU of the electronic cash register.
FIG. 7 is a flowchart showing the main part of PLU code input processing executed by the CPU of the electronic cash register.
FIG. 8 is a view showing an example of a receipt printed and issued in the electronic cash register.
FIG. 9 is a view showing an example of a department settlement report printed and issued in the electronic cash register.
FIG. 10 is a schematic diagram showing the structure of a PLU file according to another embodiment of the present invention.
FIG. 11 is a flowchart showing a main part of PLU code input processing executed by the CPU in the other embodiment;
FIG. 12 is a diagram showing an example of a single product sales settlement report printed and issued in the other embodiment;
[Explanation of symbols]
1 ... Electronic cash register
2 ... Keyboard
3. Mode switch
4 ... Display for operator
5 ... Customer display
6 ... Printer
9 ... Drawer
10 ... CPU
11 ... ROM
12 ... RAM
28 ... Delivery declaration key
29 ... Cancel key
41, 70 ... PLU file
42 ... Department file
50 ... Receipt

Claims (1)

A PLU file that stores the selling price per product, the department code to which the product belongs, etc., corresponding to the PLU code set for each product,
A department file that stores the sales amount for each department code,
An input means for inputting the PLU code of the product for sale;
A sales form declaring means for declaring a specific sales form;
When a PLU code is input by the input means, a file search means for searching the PLU file and obtaining a sales price and a department code corresponding to the input PLU code;
Sales form determination means for determining whether or not the specific sales form has been declared by the sales form declaration means for the product for which the PLU code has been input by the input means;
When the specific sales form by the sales mode determination unit Ru is judged not to be declared, it searched by the file search unit in the sales amount corresponding to the department code retrieved by the file retrieval means of the section file A first sales registration processing means for adding a sales price ;
When the specific sales form by the sales mode determination unit Ru is judged to be declared, and the code calculation means for adding a predetermined number to the department code retrieved by the file retrieval means,
Second sales registration processing means for adding the sales price searched by the file search means to the sales amount corresponding to the department code calculated by the code calculation means of the department file ;
A product sales registration apparatus comprising:

Images