JPS5840225B2 - Customer-specific transaction data processing device at gas stations - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION The present invention relates to a customer-specific transaction data processing device at a gas station, and more particularly to a customer-specific transaction data processing device that prints, for example, transaction data of gasoline sold to each customer on a slip.

Recently, POS is being introduced at gas stations.

In such a POS gas station, a central processing unit (hereinafter referred to as a CPU) is installed in the control room, and a terminal (card reader or printer) for the POS system is installed near the weighing machine.

Then, the salesperson selects a weighing machine according to the customer's request (high-octane, regular, etc.), refuels the vehicle, and inserts the customer card held by the customer into the card league.

Accordingly, the CPU provides data necessary for issuing a slip to the printer based on transaction data such as the product code representing gasoline, unit price, and quantity from the meter and the customer code read from the customer card.

The printer prints data given from the CPU on the slip.

On the other hand, the memory provided in the CPU sequentially stores sold data, such as the type of gasoline, its quantity, and its price, for each transaction category such as cash sales and credit sales.

That is, transaction data for sales to each customer is sequentially stored in the sales layer.

These transaction data are also recorded on cassette magnetic tape.

When the store is closed, when the daily sales are totaled and a daily report is created, the quantity and amount for each transaction category or product are printed on the slip using a printer.

However, some customers have multiple vehicles,
These vehicles may visit alternately during the day.

In this case, each customer may want to know the details for each day in order to know which vehicle has filled which gasoline and how much fuel each day.

However, since the memory within the CPU does not store transaction data for each customer all at once, for example, when a cassette magnetic tape is sent to a calculation center, data can be calculated based on the transaction data randomly stored on the cassette magnetic tape. It processed transaction data for each customer and printed the details on the slip.

However, processing at the above-mentioned calculation center requires a considerable number of days, and even if a customer requests details, it is not possible to immediately create a daily report for that day.

Therefore, the main purpose of this invention is to provide a gasoline system that can store transaction data for each customer's vehicle and quickly create a daily report for each customer's vehicle of sold products each time gasoline is sold for each customer's vehicle. An object of the present invention is to provide a customer-side transaction data processing device at a stand.

To summarize this invention, a plurality of recording media are allocated to each customer in which the customer code specified by each customer and the vehicle number of the vehicle owned by that customer are recorded, and each customer code and its vehicle number are stored in the first storage means in advance, and when the reading means reads the customer code and vehicle number from the recording medium, the customer code and vehicle number are stored in the first storage means. The stored customer code and vehicle number are sequentially compared, and the transaction data derived from the weighing machine is stored in the second storage means corresponding to the matched customer code and vehicle number, and a daily report is created. Sometimes, the transaction data for each customer and vehicle stored in the second storage means is configured to be printed.

The present invention will be described in more detail below along with embodiments shown in the drawings.

FIG. 1 is a schematic block diagram of an embodiment of the present invention.

In the figure, metering machines 11 and 12 are for refueling different gasolines, such as high-octane and regular gasoline, respectively.
When a vehicle is refueled with each refueling gun 111 and 121, transaction data such as the type and quantity of gasoline is recorded in C.
Give to PU4.

The card reader 2 reads a customer code and a vehicle code recorded on a magnetic card 3 as a recording medium held by each customer.

The customer code and vehicle code read by the card reader 2 are given to the CPU 4.

The CPU 4 as a control means includes a memory 5.

Further, in conjunction with the CPU 4, a printer 6 as a printing means and a cassette magnetic tape recording device 7 are provided.

2 to 7 are diagrams schematically showing the data stored in the memory 5. FIG. 2 shows an output data area, FIG. 3 shows a daily report aggregation area, and FIG. 5 shows the transaction data registration area, FIG. 6 shows the registered data editing buffer area, and FIG. 7 shows the print buffer area.

First, referring to FIG. 2, the output data area 500 includes an area 501 for storing transaction classification data such as cash sales and credit sales read by the card reader 2, an area 502 for storing customer codes, An area 503 for storing the vehicle number, an area 504 for storing the product code representing the type of gasoline given from the weighing machine 11 or 12, and an area 505 for storing the quantity given from the weighing machine 11 or 12. It includes an area 506 for storing the amount calculated based on the unit price and quantity, and an area 507 for storing other data necessary for output.

With reference to FIG. 3, the daily report tally ff, IJA510,
An area 511 for storing transaction data for cash sales for each transaction category, and an area 51 for storing transaction data for credit sales.
2, and an area 513 for storing transaction data from other transactions.

And areas 511, 512, 513 for each transaction category
includes an area for storing the quantity and price of each type, such as high-octane and regular.

Furthermore, this daily report aggregation area 510 includes an area 514 for storing an end mark at the last address.

Referring to FIG. 4, a specific customer designation area 520 constitutes a first storage means, and areas 52L522, 523, 52L, and 52L sequentially store a plurality of customer codes predetermined for each customer.
... Area 52a for storing 52N and end mark
including.

Referring to FIG. 5, a transaction data registration area 530 is an area 531 to 53N for storing transaction data for each customer.
including.

Each area 531 to 53N includes areas 541 to 554 for storing transaction data by vehicle number.

Areas 541, 554 for each vehicle are areas 541, 545, 551 that store the registered order for each customer code.
and areas 542, 546° 55 for storing product codes.
2 and the area 543゜547.55 for storing the vehicle number.
3 and areas 544, 548, and 554 for storing quantities.

This transaction data registration area 530 also includes an area 560 for storing an end mark at the last address.

Referring to FIG. 6, register data editing buffer area 5
60 is an area 56 for storing the customer code and registration order number.
1. Area 562 for storing the product code, area 563 for storing the vehicle number, and area 564 for storing the quantity.
including.

Referring to FIG. 7, print buffer area 600 includes areas 601 to 604 corresponding to the respective areas of registered data editing buffer area 560 described above, and area 605 for storing amounts.

8 to 10 are flowcharts for explaining the specific operation of one embodiment of the present invention, in particular, FIG. 8 shows the flow of the refueling sales operation, and FIG. 9 shows the flow at the time of registration. FIG. 10 shows the flow when daily reports are compiled.

FIG. 11 is a diagram schematically showing a registered content list and a daily report content list created according to an embodiment of the present invention.

Next, the specific operation of one embodiment of the present invention will be described with reference to FIGS. 1 to 11.

A salesperson receives a magnetic card 3 from a customer requesting refueling and inserts it into a card reader 2.

The card reader 2 reads the transaction classification data, customer code, and vehicle number recorded on the magnetic card 3 and enters the CP.
Give to U4.

The salesperson returns the magnetic card to the customer.

Then, the customer operates the refueling gun 111 or 121 of the weighing machine 11 or 12 to refuel the customer's vehicle.

At this time, the product code, unit price, and quantity of the refueled gasoline are provided to the CPU 4 from the measuring machine 11 or 12.

The CPU 4 outputs the output data area 5 shown in FIG. 2 according to the transaction classification data read from the card and the transaction data given from the customer code weighing machine 11 or 12.
Transaction classification data in each area 501 to 507 of 00,
Store customer code, vehicle number, product code and quantity.

At the same time, the unit price and quantity given from the weighing machine 11 or 12 are calculated to calculate the amount, and the amount is transferred to the area 50.
Store it in 6.

Each piece of data stored in this output data area 500 is immediately given to the cassette magnetic tape recording device 7 and recorded on the cassette magnetic tape.

Next, the process proceeds to the operation for daily report aggregation shown in FIG.

First, it is determined whether the customer code read from the magnetic card 3 stored in the area 502 of the output data area 500 matches the customer code stored in the specific customer designation area 521. .

If they do not match, the address is updated and the customer code in area 522 is read.

Then, it is determined whether or not an end mark is stored in the next address, and if it is not an end mark, it is determined whether the customer code read from area 522 and the customer code in output data area 500 match. Determine.

If they match, the transaction data stored in the output data area 500 is transferred to the registered data editing buffer area 5.
Transfer to 60.

That is, the customer code in area 502 is transferred to area 561, and it is determined which customer code is registered in the same customer code, and that number is also stored at the same time.

Then, the product code in area 504 is transferred to area 562, the vehicle number in area 503 is transferred to area 563, and the quantity in area 505 is transferred to area 564.

Next, the transaction data stored in the registered data editing buffer area 560 is registered in the transaction data registration area 530.

That is, area 5 of transaction data registration area 530 corresponding to the customer code and registration order number 1 stored in area 561 of registered data editing buffer area 560
41 address.

Then, the product code, vehicle number, and quantity in areas 562 to 564 are registered in areas 542 to 564, respectively.

Next, the transaction data described above is stored in the daily report aggregation area 510 shown in FIG.

That is, based on transaction classification data such as cash sales and credit sales entered in advance from the keyboard, specify the address of the corresponding area (for example, area 511 for cash sales), and then specify the address of that area in area 511 based on the product code. The address of the area corresponding to the product is specified, the quantity and amount are added to the area of the corresponding address, and the operation of daily report aggregation is completed.

Next, the process proceeds to the slip issuing operation shown in FIG.

In the print buffer area 600 shown in FIG. 7, the customer code, registration order number, product code, vehicle number, and quantity stored in the output data area 500 described above are stored in areas 601 to 604, respectively.

These transaction data are then given to the printer 6,
Printed on the slip.

Next, the operation of issuing the daily report content list and registered content list will be explained with reference to FIG.

If a daily report list is required, a key switch (not shown) included in the keyboard for creating a daily report list is operated.

In response, the CPU 4 reads out the quantities and amounts corresponding to each product for each transaction category from the daily report aggregation area 510 and stores them in the print buffer area 600.

Each data stored in this print buffer area 600 is stored in the daily report list 1 shown in FIG. 11 by the printer 6.
One line is printed on 31.

Then, the quantity and amount for each product are printed in one line for each transaction category in the daily report totaling area 510, and the above-described operation is repeated until the end mark in the area 514 is detected.

When the end mark is detected, it is determined whether a customer-specific transaction data content list is required.

Whether or not this transaction data content list for each customer is required is input by operating a corresponding switch (not shown) from the keyboard when each customer requests it.

If a list is required, it is determined whether the customer code printed last time and the customer code to be printed this time match.

If they do not match, each transaction data stored in areas 541 to 544 of transaction data registration area 530 is read out and stored in print buffer 600.

Then, the customer-specific transaction data content list 132 in FIG.
As shown in , first, the customer code is printed on one line, and the product code, vehicle number, and quantity are printed on the next line.

After printing is completed, it is determined whether or not the end mark in area 560 is detected. If the end mark is not detected, it is determined that the previous customer code and this customer code match, and the area 5
45 to 548 product code, vehicle number, and quantity are printed.

Note that at this time, since the previous customer code and the current customer code are the same, the customer code is not printed.

The above-described operations are repeated to print transaction data for each customer and vehicle number in the customer-specific transaction data content list 132.

In the above-described embodiment, transaction data is stored corresponding to each of a plurality of vehicles owned by each customer. may be provided.

As described above, according to the present invention, the first storage means stores a plurality of predetermined customer codes and the vehicle numbers of the vehicles owned by the customers, and the transaction data is stored for each customer's vehicle. A second storage means is provided, and when selling gasoline, transaction data is stored in the area corresponding to the customer's vehicle, so a list of transaction data can be quickly generated for each customer's vehicle. can be created.

[Brief explanation of the drawing]

FIG. 1 is a schematic block diagram of an embodiment of the present invention. Figures 2 to 7 are diagrams schematically showing the data stored in the memory included in Figure 1. In particular, Figure 2 shows the output data area, and Figure 3 shows the daily report aggregation area. , FIG. 4 shows the specific customer designation area, FIG. 5 shows the transaction data registration area, FIG. 6 shows the registered data editing buffer area, and FIG. 7 shows the print buffer area. 8 to 10 are flowcharts for explaining specific operations of an embodiment of the present invention, in particular, FIG. 8 shows a fuel sales operation, FIG. 9 shows a daily report aggregation operation, 1st
Figure 0 shows operations for creating a daily report and a customer-side registered data list. FIG. 11 is a diagram schematically showing an example of a daily report list and a customer-specific transaction data content list created according to an embodiment of the present invention. In the figure, 11.12 is a weighing machine, 2 is a card reader,
3 is a magnetic card, 4 is a central processing unit, 5 is a memory, 50
0 is the output data area, 510 is the daily report aggregation area, 5
20 is a specific customer designation area, 530 is a transaction data registration area, 560 is a registered data editing buffer area, 600
indicates a print buffer area, and 6 indicates a printer.

Claims (1)

[Scope of Claims] 1. A customer-by-customer transaction data processing device that processes transaction data of gasoline sold at a gas station for each of a plurality of vehicles owned by each customer. A weighing machine for deriving transaction data, a recording medium in which a plurality of customer codes assigned to each customer and predetermined for each customer and vehicle numbers of vehicles owned by the customer are recorded; a reading means for reading the customer code and the vehicle number; a first storage means for storing a plurality of different customer codes and their vehicle numbers in advance; provided corresponding to each customer and owned by the customer; A second storage means including a plurality of customer-specific storage areas for storing the transaction data for each vehicle, a printing means for printing the transaction data for each customer on a slip, and a reading means for reading the transaction data from the recording medium. In response to reading the customer code and the vehicle number, sequentially comparing the customer code and the vehicle number with a plurality of customer codes and their vehicle numbers stored in the first storage means, The transaction data derived from the weighing machine is stored in the storage area of the second storage means corresponding to the matched customer code and vehicle number, and the transaction data of each customer stored in the second storage means is stored. A customer-by-customer transaction data processing device at a gas station, comprising a control means for causing the printing means to print transaction data for each vehicle. 2. The transaction data includes at least a code representing the type of gasoline, a unit price, and a quantity, and the second storage means has a storage area for storing the code representing the type of gasoline, the unit price, and the quantity. A customer-specific transaction data processing device at a gas station according to claim 1.