JP6402446B2 - Product sales data processing apparatus and program - Google Patents

Description

  The present invention relates to a merchandise sales data processing apparatus and program.

  Conventionally, a POS register that displays a product registration screen is known (see, for example, Patent Document 1). In general, the POS register registers tickets (for example, gift certificates) used for payment at any time during the registration process, and stores registered registration data (for example, product data and ticket data). Display in a list.

JP 2011-186949 A

  However, since registration data is displayed in a list in the order of registration, it takes time and effort to find desired registration data from the list display when there is a lot of registration data. For example, if a customer requests to cancel the use of a ticket after registering the ticket according to a request to use a ticket, the ticket data of the ticket is displayed in a list. Although it is necessary to search and cancel, it took time and effort to find the corresponding ticket data.

  The present invention has been made in consideration of such circumstances, and the object thereof is a product sales data processing apparatus that can easily find desired registration data (for example, ticket data of tickets to be canceled). Is to provide.

In order to solve the above-described problem, a merchandise sales data processing apparatus according to an aspect of the present invention registers a ticket used for payment in addition to a product purchased by a customer in a merchandise sales data processing apparatus having a display unit. Display control for displaying possible registration means, product data of products registered by the registration means, and ticket data of tickets registered by the registration means side by side in a predetermined area of the display unit as registration data Means for displaying registration data up to a predetermined upper limit number simultaneously, and the display control means includes at least one product data and at least one ticket data If you are a registered data of the upper limit number are displayed side by side in the predetermined area, when the ticket class is newly registered by the registration means, is displayed in the predetermined area The product data of the inner tickets such data registered data causes erased from the predetermined area with priority that is characterized by displaying the ticket class data of the newly registered ticket acids in the predetermined region.

In the merchandise sales data processing apparatus, the display control means displays the upper limit number of registration data including at least two merchandise data side by side in the predetermined area and displays the tickets by the registration means. When newly registered, product data at the bottom of the product data displayed in the predetermined area may be deleted from the predetermined area.

In the product sales data processing apparatus, the display control means may display the product data and the ticket data in different display modes in the predetermined area.

In order to solve the above-described problem, a program according to an aspect of the present invention has a display unit, and product sales data capable of simultaneously displaying registration data up to a predetermined upper limit number in a predetermined area of the display unit. A program that causes a computer to function as a processing device, in addition to products purchased by customers, registration means capable of registering tickets used for payment, product data of products registered by the registration means, The ticket data of the tickets registered by the registration means is caused to function as display control means for displaying the registered data side by side in a predetermined area of the display unit as registration data, and the display control means includes at least one product data and at least when the registration data of the upper limit number including the one ticket such data being displayed side by side in the predetermined region, by the registration means When the ticket class is newly registered, that together than ticket such data in favor of the product data is erased from the predetermined region, and displays the ticket class data of the newly registered ticket acids in the predetermined area It is a featured program.

  According to the present invention, it is possible to reduce the trouble of searching for already registered data during the registration process.

It is an example of the external view of the merchandise sales data processing apparatus 1 by one Embodiment of this invention. FIG. 2 is an example of a block diagram showing a configuration of an electric circuit of a POS register 10 constituting the merchandise sales data processing apparatus 1. It is an example of a product registration screen. It is explanatory drawing explaining a goods registration screen. 3 is a flowchart showing an operation example of the merchandise sales data processing apparatus 1. It is explanatory drawing explaining the case where ticket data and merchandise data are displayed on the same area | region.

  Hereinafter, an embodiment of the present invention will be described with reference to the drawings. FIG. 1 is an example of an external view of a merchandise sales data processing apparatus 1 according to an embodiment of the present invention. Specifically, it is an external perspective view of the merchandise sales data processing apparatus 1 installed on the counter table 9. As shown in FIG. 1, the merchandise sales data processing apparatus 1 includes a POS register 10 (registered settlement apparatus) and an automatic change machine (hereinafter also simply referred to as a change machine) 20.

  The POS register 10 is a registration process for registering a product to be purchased (a product to be purchased) and a settlement process (also referred to as a settlement process or an accounting process) for performing a payment for the registered product (payment settlement or accounting). And execute. The POS register 10 includes, for example, a scanner unit 104, a store clerk display unit 105, an operation unit 108, a printing unit 111, and the like, as shown in FIG. Details will be described later.

  The change machine 20 is used in the settlement process in the POS register 10. As shown in FIG. 1, for example, the change machine 20 includes an operation unit 205, a coin slot 210, a coin outlet 211, a bill slot 212, a bill outlet 213, a storage unit (not shown in FIG. 1), and the like. . Details will be described later.

  FIG. 2 is an example of a block diagram showing the configuration of the electric circuit of the POS register 10 constituting the merchandise sales data processing apparatus 1. The POS register 10 includes, for example, a CPU (Central Processing Unit) 101, a ROM 102, a RAM 103, a scanner unit 104, a store clerk display unit 105, a customer display unit 106, a hard disk 107, an operation unit 108, a communication, as shown in FIG. Unit 109, buzzer 110, printing unit 111, and connection unit 112.

  The CPU 101 controls the entire POS register 10 by developing a program stored in the ROM 102 in the RAM 103 and executing it. Details will be described later.

  The ROM 102 stores various information. For example, the ROM 102 stores a program executed by the CPU 101, a device number of the own device (device identification information), and the like.

  The RAM 103 temporarily stores various information. For example, the RAM 103 temporarily stores a program read from the ROM 102 and information acquired or generated by executing the program. For example, the RAM 103 stores person identification information (for example, person-in-charge code, person-in-charge name) registered using the scanner unit 104 or the like, the transaction unit registered using the scanner unit 104 or the store clerk display unit 105, or the like. All registration data, various determination results, transaction information, etc. are temporarily stored. The RAM 103 may temporarily store a product file.

  In addition, all the registration data of the transaction described above includes all the registered product data in the transaction (registration process) (that is, product data of all products already registered as the customer's purchased products), And all registered ticket data in the transaction (registration process) (that is, ticket data of all tickets already registered as tickets used by the customer). The product data includes, for example, a product name (or product code) and a sales price. The ticket data is, for example, information used to specify the registration order of the tickets when a plurality of tickets are registered (for example, the registration time of the tickets, the number is assigned when the tickets are registered). Serial number) and the usable amount set for the ticket. In addition to the above, the ticket data may further include information specifying the ticket type (ticket type) and usage conditions (usable period, usable store) of the ticket. Good.

  The scanner unit 104 optically reads a barcode attached to a product and acquires a product code of the product (acquires the product code that has been encoded by reverse conversion). The scanner unit 104 notifies the CPU 101 of the acquired product code. When a barcode is attached to the ticket, the scanner unit 104 optically reads the barcode attached to the ticket and acquires the ticket data. The scanner unit 104 notifies the CPU 101 of the acquired ticket data. Further, the scanner unit 104 optically reads a barcode attached to a name tag or the like of a store clerk (operator), and acquires person-in-charge identification information for identifying the store clerk. The scanner unit 104 notifies the CPU 101 of the acquired person-in-charge identification information.

  The clerk display unit 105 is, for example, a liquid crystal touch display device that displays information to the clerk and can accept operations of the clerk. The salesclerk display unit 105 includes, for example, the latest registration data (for example, product name, sales price, purchase quantity), total registration data (history data) of the transaction, total amount, deposit amount, change amount , Display messages for shop assistants, etc. Note that the total amount based on the entire product data may be displayed as the total amount, or the amount after subtraction after subtracting the registered ticket types may be displayed as the total amount.

  In addition, icons for accepting various operations are displayed on the store clerk display unit 105. For example, one or more buttons for switching the display state of all registered data (product data, ticket data) of the transaction temporarily stored in the RAM 103 to a predetermined content are displayed. For example, the display state of all the product data of the transaction temporarily stored in the RAM 103 is displayed in descending order (new order) or ascending order (old order) of the registration order, or descending order (highest order) of the amount (sales amount). Or you may display the sort button to rearrange in an ascending order (cheap order). In addition, the display state of all the ticket data of the transaction temporarily stored in the RAM 103 is set in descending order of registration order (new order) or ascending order (old order), or descending order of money (usable amount) (high). Sort buttons for rearranging may be displayed in order) or ascending order (lowest order).

  The store clerk display unit 105 may display a preset button for registering a predetermined product (for example, fresh food) or a preset button for registering various tickets. Further, the clerk display unit 105 may display a button having the same function as a button (described later) provided in the clerk operation unit 108. In the store clerk display unit 105, when a store clerk operates (a sort button or preset button is pressed (touched)), an operation signal is notified to the CPU 101.

  More specifically, a merchandise registration screen (which may be a screen common to the checkout process) is displayed on the clerk display unit 105 under the control of the CPU 101 during the registration process. All the registered product data is displayed as a list of history data in one position (for example, the upper part) in the history display area (for example, the left side of the product registration screen), and other positions ( For example, a list of all registered ticket data is displayed as history data in the lower part. However, when the number of history data is large, it may be displayed in a scrolling manner without displaying all of them at the same time. As described above, all the registered product data and all the registered ticket data are displayed as history data in the history display area which is the same area in the product registration screen which is the same screen. However, the position in the history display area where all registered product data is displayed in a list is different from the position in the history display area where all registered ticket data is displayed in a list.

  The sort button described above may be a dedicated button that provides a sorting function, or may be a button that is also used as another function. For example, a button for accepting a sort instruction exclusively from a store clerk displayed as “sort” may be arranged as a sort button on the product registration screen (for example, in the vicinity of the history display area), or a list display item in the history display area The name (for example, the ticket name and amount in the list display of ticket data) is displayed to the store clerk, and the product registration screen (for example, the display of the item name in the history display area) is used with a sort button as a sort button. (Position).

  The number of sort buttons arranged on the product registration screen may be one or more. For example, one sort button (one sort button commonly used for sorting both product data and ticket data) may be arranged on the product registration screen, and 2 sort buttons may be placed on the product registration screen. Sort buttons (one sort button used to sort product data, one sort button used to sort ticket data) may be arranged, and four sort buttons (product Two sort buttons used for sorting data and two sort buttons used for sorting ticket data may be arranged. Further, three or five or more sort buttons may be arranged according to the type of display state to be sorted.

In an aspect in which one sort button (one sort button used in common for sorting both product data and ticket data) is arranged on the product registration screen, for example, a sort target is designated and sorted. Each time the button is pressed, the display state of the specified target may be sequentially switched. For example, when the display state (initial state) before pressing the sort button is the display state a, a series of pressing operations such as specifying ticket data (for example, pressing a list display portion of ticket data) and pressing the sort button The display state of the designated ticket data may be sequentially switched as follows: display state a → display state b → display state c → display state d → display state a → display state b →.
Display state a: Product data is displayed in descending order of registration order (new order), and ticket data is displayed in descending order of registration order (new order).
Display state b: The display state of the designated ticket data is switched to the ascending order (oldest order) of the registration order. Note that the display state of the product data that has not been specified is maintained in the descending order of the registration order (the display state c and the display state d are also the same).
Display state c: The display state of the designated ticket data is switched in descending order (highest order) of the amount.
Display state d: The display state of the designated ticket data is switched in ascending order (cheap order) of money.

  When a special pressing operation (for example, long pressing) is performed on the one sort button, the display state a may be returned to the initial display state regardless of the current display state.

  In an aspect in which two sort buttons (one sort button used for sorting product data and one sort button used for sorting ticket data) are arranged on the product registration screen, for example, the sort button is pressed. Each time, the display state of the object corresponding to the pressed sort button may be sequentially switched. For example, when the display state before pressing the sort button is the above-described display state a, a sort button used for sorting ticket data (for example, one sort button is arranged in the vicinity of the product data, and the vicinity of the ticket data When one sort button is arranged on the screen, every time the sort button arranged in the vicinity of the ticket data is pressed, the display state a → display state b → display state c → The display state of designated ticket data may be sequentially switched as in display state d → display state a → display state b →. The same applies when the sort button used for sorting the product data is pressed, although the sort target is different.

  When a special pressing operation (for example, long pressing) is performed on the sort button used for sorting the ticket data, the display of the display state a that is the initial state is displayed for the ticket data regardless of the current display state. You may make it return to a state. Even when a special pressing operation (for example, long pressing) is performed on the sort button used for sorting the product data, the object to be returned to the initial state is different, but is the same.

  In an aspect in which four sort buttons (two sort buttons used for sorting product data and two sort buttons used for sorting ticket data) are arranged on the product registration screen, each time the sort button is pressed, The display state may be sequentially switched according to the content corresponding to the pressed sort button for the target corresponding to the pressed sort button. For example, when the display state before pressing the sort button is the above-described display state a, the sort button that sorts according to the amount of money among the two sort buttons used for sorting the ticket data (for example, corresponding to the registration order of the product data) One sort button is arranged, one sort button corresponding to the amount of the product data is arranged, one sort button corresponding to the registration order of the ticket data is arranged, and the sort corresponding to the amount of the ticket data is arranged. When one button is arranged, every time the sort button corresponding to the amount of the ticket data is pressed, the display state a → display state e → display state f → display state e → display state f → The display state of the ticket data may be sequentially switched as in the display state e.

Display state a: Product data is displayed in descending order of registration order (new order), and ticket data is displayed in descending order of registration order (new order).
Display state e: The display state of the target ticket data is switched in descending order of money (highest order). Note that the display state of the product data that is not the object is maintained in the descending order of the registration order (the display state f is also the same).
Display state f: The display state of the designated ticket data is switched in ascending order (cheap order) of money.

  Note that the same applies to the case where a sort button other than the sort button used for sorting the product data is pressed, although the target and contents differ depending on the pressed sort button. For example, each time the sort button corresponding to the registration order of the product data is pressed, the product data is sequentially switched between the ascending order (old order) and the descending order (new order) of the registration order (display of ticket data) The state is maintained in descending order of registration order).

  The customer display unit 106 is, for example, a liquid crystal display device that displays information to the customer. The customer display unit 106 includes the most recent registration data, total amount, deposit amount, change amount, customer message, advertisement, and the like. Note that the customer display unit 106 may be, for example, a liquid crystal touch display device that can accept customer operations, like the store clerk display unit 105. For example, the customer display unit 106 accepts an operation for a message for a customer (for example, confirmation of the amount of a utility bill). When a customer operation is performed on the customer display unit 106, an operation signal is notified to the CPU 101.

  The hard disk 107 stores various information. For example, the hard disk 107 stores a product file transmitted from a store controller (not shown) and received by the communication unit 109. Note that the hard disk 107 may store the above-described program instead of the ROM 102.

  The clerk operation unit 108 includes various buttons (operation keys). For example, the clerk operation unit 108 includes numeric buttons (numeric keys) for inputting numbers, subtotal buttons (subtotal keys), current total buttons (current total keys), cancel buttons (cancel keys), and the like. The salesclerk operation unit 108 may include the above-described preset button (preset key). That is, a preset button for registering a predetermined product (for example, fresh food) and various tickets may be provided. Moreover, you may provide the sort button which rearranges the display state of registration data (product data, ticket data). In the clerk operation unit 108, when a clerk operates, an operation signal is notified to the CPU 101.

  The communication unit 109 is a communication interface for communicating with an external device via the LAN 40. The buzzer 110 is a sound generating unit for generating a confirmation sound, a warning sound, and the like. The printing unit 111 prints and issues a receipt and the like. The connection unit 112 is a communication interface for connecting to the change machine 20.

  When the CPU 101 acquires person-in-charge identification information via the scanner unit 104 (when a barcode attached to a name tag or the like is read by the scanner unit 104), the CPU 101 temporarily stores the person-in-charge identification information in the RAM 103.

  The CPU 101 displays a product registration screen on the store clerk display unit 105, and executes a product registration process. For example, when the CPU 101 acquires a product code via the scanner unit 104 (when a barcode attached to the product is read by the scanner unit 104), the CPU 101 refers to the product file stored in the hard disk 107 and stores the product code. The name and sales price are specified, and temporarily stored in the RAM 103 as product data. Further, for example, when the CPU 101 acquires ticket data via the scanner unit 104 (when the barcode attached to the ticket is read by the scanner unit 104), the CPU 101 temporarily stores the ticket data in the RAM 103. Further, for example, when a preset button for registering a predetermined product is pressed, the CPU 101 temporarily stores the product name and sales price associated with the preset button in the RAM 103 as product data. Further, for example, when a preset button for registering various tickets is pressed, the CPU 101 temporarily stores the ticket data associated with the preset button in the RAM 103. When a quantity is declared when registering a product (for example, when a numeric key is pressed), the purchase quantity is temporarily stored in association with the product data of the product. Similarly, when the quantity is declared when registering the ticket, the used quantity is temporarily stored in association with the ticket data of the ticket.

  The CPU 101 recognizes that it is a product code when the barcode attached to the product is read, and recognizes it as ticket data when the barcode attached to the ticket is read. The identification method for identifying whether the bar code is a product code or ticket data is not particularly limited. For example, if the barcode system attached to a ticket is different from the barcode system attached to a product, whether the barcode read is a product code or ticket data May be identified. Also, depending on whether or not a predetermined operation (for example, pressing a predetermined button declaring the registration of the ticket) is requested to the store clerk before the ticket is registered, and the predetermined operation is performed immediately before reading the barcode, You may identify whether the read barcode is a product code or ticket data.

  Further, during the registration process, the CPU 101 displays all registration data (product data, ticket data) of the transaction temporarily stored in the RAM 103 as described above as history data in the history display area of the product registration screen. Specifically, the CPU 101 displays a list of all registered product data at one position (for example, the upper part) in the history display area of the product registration screen. In addition, the CPU 101 displays a list of all registered ticket data at other positions (for example, the lower part) in the history display area of the product registration screen. For example, each time a product is newly registered, the CPU 101 adds the product data of the product to the top of the list of products already displayed, and whenever a ticket is newly registered, The ticket data may be added to the top in the list of ticket already displayed. In other words, the merchandise and the tickets may be displayed in a list in descending order (new order) of the registration order at each registration. Note that, as described above, when the number of registered data is large, scroll display may be performed without displaying all of the data at the same time.

  Further, when the sort button is pressed, the CPU 101 refers to all registered data of the transaction temporarily stored in the RAM 103 and sorts the history data (product data, ticket data) displayed in the history display area. . For example, in an aspect in which four sort buttons (two sort buttons used for sorting product data and two sort buttons used for sorting ticket data) are arranged on the product registration screen, the CPU 101 performs processing as described above. Depending on the type of the sort button that was pressed and the display state before the button was pressed, either the product data or the ticket data displayed in the history display area should be sorted in descending or ascending order of registration order, Sort in descending or ascending order (sales amount, available amount).

  The CPU 101 communicates with the change machine 20 via the connection unit 112. For example, the CPU 101 transmits a control command to the change machine 20. For example, the CPU 101 receives deposit information from the change machine 20.

  In addition, after the transaction ends (after the registration process and the settlement process end), the CPU 101 generates transaction information of the transaction, controls the communication unit 109, and transmits the generated transaction information to a store controller (not shown). To do. The transaction information includes a transaction number and detailed information. The transaction number is a number that uniquely identifies the transaction (transaction information). The detailed information includes, for example, a device number, person-in-charge identification information, transaction date and time, product name (or product code), purchase quantity, total amount, and the like. The detailed information may include registered ticket data. Further, after the transaction ends, the CPU 101 controls the printing unit 111 to issue a receipt on which the detailed information of the transaction is printed.

  The change machine 20 constituting the merchandise sales data processing apparatus 1 includes, for example, a control unit 201 (not shown), a connection unit 202 (not shown), an operation unit 205 (see FIG. 1), and a coin slot 210 (see FIG. 1). , A coin payout exit 211 (see FIG. 1), a bill insertion slot 212 (see FIG. 1), a bill payout exit 213 (see FIG. 1), a storage unit 216 (not shown), and a transport unit 220 (not shown). .

  The connection unit 202 is a communication interface for connecting to the POS register 10. The display operation unit 205 is a touch panel, for example. The storage unit 216 stores deposits and changes. The storage unit 216 has a storage space for each type of money. The coin slot 210 is a coin slot. The coin payout exit 211 is a coin payout exit. The bill insertion slot 212 is a bill insertion slot. The banknote outlet 213 is a banknote outlet. Note that the bill insertion slot and the bill payment outlet may be common, and the coin insertion slot and the coin payment outlet may be common.

  The conveyance unit 220 conveys money between the insertion slot (coin insertion slot 210, bill insertion slot 212) and the storage unit 216. Moreover, the conveyance part 220 identifies and counts the money seed | species of the money (The money inserted or discharged | emitted) conveyed. The transport unit 220 notifies the control unit 201 of the number of coin types (identification result, count result). The control unit 201 controls the transport unit 220 so as to store the money put into the insertion slot in the storage unit 216, generates deposit information based on the number of each money type acquired from the carry-out unit 220, and Transmit to the register 10. Further, when the control unit 201 receives a control command indicating that money should be discharged via the connection unit 202, the control unit 201 controls the transport unit 220 so as to release the money stored in the storage unit 216.

  As described above, the change machine 20 transmits the deposit information to the POS register 10 and stores the inserted money in the storage unit 216 when the money is inserted into the insertion slot. Further, the change machine 20 discharges the money stored in the storage unit 216 to the payout opening (coin payout exit 211, bill payout exit 213) according to the control of the POS register 10.

  FIG. 3 is an example of a product registration screen. FIG. 4 is an explanatory diagram for explaining the product registration screen (specifically, a display example in the area (D2) for displaying a list of ticket data). The product registration screen shown in FIG. 3 includes an area for displaying a preset button for registering a predetermined product (A in the figure), an area for displaying the latest registration data (B in the figure), a total amount, and the like. There are a display area (C in the figure), a history display area (D in the figure) for displaying all registered data (history data) of the transaction. In the history display area, there are an area (D1 in the figure) for displaying a list of all registered product data as history data, and an area (D2 in the figure) for displaying a list of all ticket data registered as history data. Exists. In the area (A), there is a correction button for correcting the registration.

  In the example shown in FIG. 3, the ticket data list display area (D2) includes ticket data with a ticket name “XX” and an amount “¥ 100”, and a ticket name “XX”. The ticket data with the amount “¥ 300” and the ticket data with the ticket name “□□” and the amount “¥ 200” are listed in descending order of registration order (new order). It is displayed. The □□ ticket is registered first, the XX ticket is registered second, and the XX ticket is registered third. FIG. 4A shows the above three display states.

  For example, when there are a large number of registered tickets, the ticket data cannot be displayed in the area (D2) at one time and a part of the ticket data becomes invisible. However, scrolling is performed by an operation on the screen (for example, slide, flick). Can be seen by The same applies to the product data in the area (D1) where the product data is displayed as a list.

  Reference numeral 320 denotes a sort button for displaying the item name “ticket name” to the store clerk and receiving a sort instruction from the store clerk according to the registration order. When the sort button 320 is pressed once in the display state of FIG. 4A, the display state is switched in ascending order of registration order (old order) as shown in FIG. 4A to FIG. 4B. Further, when the sort button 320 is pressed once in the display state of FIG. 4B, the display state is switched in descending order of registration order (new order) as shown in FIG. 4B → FIG. 4A. Thereafter, each time the sort button 320 is pressed, the display is switched as shown in FIG. 4 (b) → FIG. 4 (a) → FIG. 4 (b) →.

  If the sort button 320 is pressed once in the display state of FIG. 4C or the display state of FIG. 4D, FIG. 4C → FIG. 4A or FIG. The display state is switched from 4 (d) to FIG. 4 (a). However, when the sort button 320 is pressed once in the display state of FIG. 4C (descending order of amount), the display state is switched to the display state of FIG. 4A (descending order of registration order). When the sort button 320 is pressed once in the display state (ascending order of amount) in (d), the display state (ascending order of registration order) in FIG. 4B may be switched. That is, the sort target is switched by pressing, but “descending order” or “ascending order” may be maintained.

  Reference numeral 321 denotes a sort button for displaying the item name “amount” to the store clerk and receiving a sort instruction by the amount from the store clerk. When the sort button 321 is pressed once in the display state of FIG. 4A, the display state is switched in descending order (highest order) of monetary order as shown in FIG. 4A → FIG. 4C. Further, when the sort button 321 is pressed once in the display state of FIG. 4C, the display state is switched in ascending order (lowest order) of monetary order as shown in FIG. 4C → FIG. 4D. Further, when the sort button 321 is pressed once in the display state of FIG. 4D, the display state is switched in descending order of monetary order as shown in FIG. 4D → FIG. 4C. Thereafter, each time the sort button 321 is pressed, the display is switched as shown in FIG. 4D → FIG. 4C → FIG. 4D →.

  When the sort button 321 is pressed once in the display state of FIG. 4B, as in the case where the sort button 321 is pressed once in the display state of FIG. 4A, FIG. The display state is switched as shown in FIG. However, when the sort button 321 is pressed once in the display state of FIG. 4A (descending order of registration order), the display state is switched to the display state of FIG. When the sort button 321 is pressed once in the display state (ascending order of registration order) in FIG. 4B, the display state may be switched to the display state (ascending order of amount) in FIG. That is, the sort target is switched by pressing, but “descending order” or “ascending order” may be maintained.

  In the example shown in FIG. 3, the product data list display area (D1) includes one item of product data with the item name “mandarin orange”, the number “3”, the unit price “¥ 300”, and the discount “− ¥ 200”. Are listed. Reference numeral 310 denotes a sort button for receiving a sort instruction based on the registration order. Reference numeral 311 denotes a sort button for accepting a sort instruction by amount. Since the operation after the sort buttons 310 and 311 are pressed is the same as the operation after the sort buttons 320 and 321 are pressed, the description thereof is omitted.

  The amount to be sorted by pressing the sort button 311 is preferably the sales price after discount (¥ 700 in FIG. 3), but may be the sales price before discount (¥ 900 in FIG. 3). . Further, it may be possible to designate whether the amount to be sorted is the sales price before the discount or the sales price after the discount.

  In addition, regarding the product data in the product data list display area (D1), it is possible to know whether the current display state is the descending order of the registration order, the ascending order of the registration order, the descending order of the amount of money, or the ascending order of the amount of money. Also good. For example, a symbol, mark, design, wording, or the like for notifying the store clerk of the current display state may be displayed inside or outside the area (D1) or inside or outside the history display area (D). The same applies to the ticket data in the area (D2) where the ticket data is displayed as a list.

  In addition, the display state of the product data in the product data list display area (D1) may be different from or the same as the display state of the product data in the area (B) displaying the latest registered data. May be. The display state of the ticket data in the area (D2) for displaying the ticket data list may be different from or the same as the display state of the ticket data in the area (B) for displaying the latest registered data. There may be.

  FIG. 5 is a flowchart showing an operation example of the merchandise sales data processing apparatus 1. Specifically, the flowchart of FIG. 5 illustrates an operation example of one transaction of the merchandise sales data processing apparatus 1. It is assumed that the merchandise sales data processing apparatus 1 displays the merchandise registration screen shown in FIG. 3 on the salesclerk display unit 105 at the start of the flowchart of FIG.

Step S1: It is determined whether or not a product or ticket has been registered. If registered, the process proceeds to step S2. If there is no registration, the process proceeds to step S3.
Step S2: The display is updated. Specifically, when the product is registered in step S1, the product data of the product is overwritten and displayed (switched display) in the area (B) for displaying the latest registered data and the like, and the history display area (D ) Are additionally displayed in the area (D1). On the other hand, when the ticket is registered in step S1, the ticket data of the ticket is overwritten in the area (B) for displaying the latest registered data and the like, and the area in the history display area (D) An additional display is made at (D2). Registration data is also added to the RAM 103.

Step S3: It is determined whether or not the sort button has been pressed. If it has been pressed, the process proceeds to step S4. If not, the process proceeds to step S5.
Step S4: Sort history data (product data, ticket data). Specifically, when the sort button 310 is pressed in step S3, the product data is sorted in descending or ascending order of the registration order in the area (D1) for displaying the list. When the sort button 311 is pressed in step S3, the product data is sorted in descending or ascending order of the amount in the area (D1) for displaying the list. If the sort button 320 is pressed in step S3, the ticket data is sorted in descending or ascending order of the registration order in the area (D2) for displaying the list of ticket data. When the sort button 321 is pressed in step S3, the ticket data is sorted in descending or ascending order of the amount in the area (D2) for displaying the list of ticket data.

Step S5: It is determined whether or not a correction button (see area A in FIG. 3) has been pressed. If it has been pressed, the process proceeds to step S6. If not, the process proceeds to step S7.
Step S6: The designated registration data is deleted from the history data. For example, when the store clerk specifies the ticket data by pressing a certain ticket data display area in the ticket data list display area (D2), and then the correction button is pressed in step S5. First, the ticket data is deleted in the area (D2). The ticket data is also deleted from the RAM 103.

Step S7: It is determined whether or not the subtotal key has been pressed. If not pressed, the process returns to step S1. If it has been pressed, the process proceeds to step S8.
Step S8: A deposit amount and a change amount are displayed. That is, the clerk receives money from the customer after pressing the subtotal key and puts it into the change machine 20, whereby the merchandise sales data processing apparatus 1 calculates the deposit amount, and calculates the deposit amount and the registered merchandise. The change amount is calculated on the basis of the total amount and displayed on the store clerk display unit 105 and the customer display unit 106. Note that the merchandise sales data processing apparatus 1 displays (redisplays) the total price in the area (C) for displaying the total price on the merchandise registration screen before pressing the subtotal key (every time the merchandise is registered). Also good. Note that the store clerk display unit 105 may display the deposit amount and change amount on the product registration screen, or may display the deposit amount and change amount on a screen different from the product registration screen.
Step S9: The current key is pressed.
Step S10: Checkout is executed. That is, when the store clerk presses the current total key, the merchandise sales data processing apparatus 1 releases change from the change machine 20. Then, the flowchart of FIG. 5 ends.

  In the flowchart of FIG. 5, if there is no sorting in step S4, new registration data (product data, ticket data) in step S1 is added to the history display area (D) in descending order of registration order (new order). The In other words, when the display state of the history display area (D) immediately before the new registration is in descending order of the registration order, the new registration data is added to the top of the corresponding area (D1 or D2). On the other hand, when the display state of the history display area (D) immediately before the new registration is a display state other than the descending order of the registration order (ascending order of registration order, descending order of money, ascending order of money), the new registration data is The additional display may be performed as in any of the following method 1, method 2, and method 3.

(Method 1 / additional display at the position according to the previous display state, including additional parts)
For example, in step S1, which is first executed after the display state of the ticket data displayed in the area (D2) in step S4 is rearranged in descending order of the amount of money as shown in FIG. Is registered, the new ticket data is additionally displayed at a position where all the ticket data including the new ticket data is arranged in descending order of the amount of money.

(Method 2 / Return to the initial state and display the added part at the top)
For example, in the above case, all the ticket data including the new ticket data is rearranged in the initial state (descending order of registration order). Therefore, new ticket data is additionally displayed at the top of the area (D2).

(Method 3 / Additional additions are displayed at the top while maintaining the previous display status except for additions)
For example, in the above case, for the ticket data excluding new ticket data, the previous display state (descending order of money amount) is maintained, and new ticket data is additionally displayed at the top of the area (D2). .

  Method 2 above changes the display state to the initial state (descending order of the registration order) without pressing the sort button. However, in the case of changing the display state to the initial state without pressing the sort button. The timing of changing to the initial state is not limited to the timing of new registration (in the case of the above method 2). For example, when the ticket data is deleted in step S6, the display state of the ticket data is changed to a display state other than the initial state (ascending order of registration order, amount of money) unconditionally or after pressing a predetermined button. You may return to the initial state from the descending order and the ascending order.

  The flowchart of FIG. 5 shows the execution of sorting at the stage before the subtotal key is pressed. In addition to the stage before the subtotal key is pressed, the stage before the current key is pressed after the subtotal key is pressed. Sorting may also be executed at. The same applies to correction.

  As described above, the merchandise sales data processing apparatus 1 according to the embodiment of the present invention has been described. However, according to the merchandise sales data processing apparatus 1, the merchandise data and the ticket data are displayed at different positions. It is possible to easily find ticket data and product data of the corresponding product from each position. Therefore, it is possible to reduce time and labor when canceling registration of registered data.

  Further, in the above embodiment, the position of the history display area is provided on the left side of the product registration screen as shown in FIG. 3, but the position of the history display area may be provided on the right side of the product registration screen, It may be provided on the lower side. Moreover, in the said embodiment, although the area | region which displays a list of ticket data is provided below the area | region which displays product data as a list, the area | region which displays a list of ticket data may be made into the upper side, and goods An area for displaying a list of data and an area for displaying a list of ticket data may be arranged side by side.

  Note that the ticket data may be displayed with priority over the product data. For example, the area (D2) for displaying the list of ticket data may be widened (for example, a product) when the ticket data to be displayed increases so that the entire ticket data can be displayed even if the ticket data increases. The area (D2) for displaying a list of data may be secured by narrowing the area (D1) for displaying a list of data).

  In the above-described embodiment, the initial display state of the history data is set to the descending order of the registration order, but it may be switched to another display state depending on the setting. In the above embodiment, the ticket data is sorted according to either the registration order or the amount (usable amount), but the ticket data may be sorted according to other conditions. For example, the remaining expiration dates may be sorted in the order of length (shortest order, longest order).

  In the above embodiment, the history data is classified into product data and ticket data, but the type and number of classifications are not limited to this. For example, the product data may be further classified according to whether or not it is a point grant target. Further, the product data may be classified according to whether it is taxable or may be classified according to whether it is a product with age restriction (for example, alcohol, tobacco). Further, the product data may be classified according to whether or not there is a discount. In addition, when there are a plurality of discounts such as a mixed match discount, the individual commodities that are configured may be excluded from the single product classification. Moreover, you may classify | categorize according to whether it is specific registration, such as registration (reading of an invoice etc.) for payment of a utility bill. Further, the ticket data may be classified according to whether or not there is an expiration date. Note that these classifications may be set for each individual device.

  In the above embodiment, the history data is displayed in the history display area of the product registration screen of the salesclerk display unit 105, but the history data may also be displayed on the customer display unit 106. Even when the history data is displayed on the customer display unit 106, the product registration screen is not displayed on the customer display unit 106. That is, the display mode of the history data displayed on the customer display unit 106 is different from the display mode of the history data displayed on the store clerk display unit 105. Further, considering the display area, the history data displayed on the customer display unit 106 may be limited as compared to the history data displayed on the store clerk display unit 105. For example, the customer display unit 106 may display either product data or ticket data as history data. Further, for example, the number of history data displayed on the customer display unit 106 may be smaller than the number of history data displayed on the store clerk display unit 105. Further, for example, the information amount of one piece of history data displayed on the customer display unit 106 may be smaller than the information amount of one piece of history data displayed on the store clerk display unit 105 (for example, a customer Only the ticket name of the ticket data may be displayed on the display unit 106, and the amount may be hidden.

  As shown in FIG. 3, in the above embodiment, the history display area (D) includes an area (D1) for displaying product data in a list and an area (D2) for displaying ticket data in a list, The product data is displayed in the area (D1) and the ticket data is displayed in the area (D2). If the product data and the ticket data are classified, the ticket data and the product data are the same. It may be displayed in the (common) area.

  FIG. 6 is an explanatory diagram for explaining the case where the ticket data and the product data are displayed in the same area. More specifically, each of FIGS. 6 (a) to 6 (i) represents a display example in the history display area (D), but the history in each of FIGS. 6 (a) to 6 (i). The display area (D) does not distinguish between an area (D1) for displaying product data as a list and an area (D2) for displaying ticket data as a list.

  FIG. 6A shows the history display area (D) when “shrimp fried” is registered first, “bakery bread” is registered second, “rose cancer return” is registered third, and so on. It is a display example. As shown in FIG. 6A, the product data is displayed in a list in descending order of registration order (new order) in the history display area (D) (displayed from the top to the bottom).

  When a □□ ticket is registered from the state of FIG. 6A, the ticket data of the □□ ticket is displayed in the history display area (D) as in the case of the product data, as shown in FIG. 6B. However, in the history display area (D), ticket data and product data are classified and displayed. For example, the ticket data of the □□ ticket may be displayed at the lower part of the history display area (D) instead of the “Rose cancer return” as shown in FIG. (It may be displayed in the lower part of the area (D)), as shown in FIG. 6 (c), following the product data at the bottom (product data of “shrimp fry” in FIG. 6 (c)) (somewhat If there is a gap, it is also included in “continue”), and may be displayed (that is, displayed at the bottom of the history display area (D)).

  In FIG. 6C and FIG. 6D, the product name is used for convenience as the item name corresponding to the product name of the product data and the ticket name of the ticket data, but other names may be used. Good.

  FIG. 6D is a display example when the sort button for products is pressed from the state of FIG. FIG. 6E is a display example when the sort button for products is pressed from the state of FIG. As shown in FIG. 6D and FIG. 6E, when the sort button for products is pressed, the product data is sorted, but the ticket data is not sorted. In addition, in the example of FIG.6 (d) and FIG.6 (e), merchandise data are sorted in the descending order (high order) of money amount.

  FIG. 6F shows a display example when “rose raising” is registered from the state of FIG. As shown in FIG. 6 (f), the product data of the fourth registered “rose production” is displayed on the third registered “rose cancer return”. FIG. 6G is a display example when a □□ ticket is registered from the state of FIG. It is assumed that the registration data (product data, ticket data) in the history display area (D) is full when the ticket data of □□ ticket is displayed.

  When a xx ticket is registered from the state shown in FIG. 6 (g), the ticket data of the xx ticket is stored in the product data at the bottom ("Shrimp fry" in FIG. 6 (g)) as shown in FIG. 6 (h). (Product data) may be displayed instead. That is, as it is, there is no area for displaying the ticket data of the xx ticket in the history display area (D), so in order to secure the area for displaying the ticket data of the xx ticket, It may be erased. In other words, the ticket data may be displayed with priority over the product data. Needless to say, the product data of “shrimp fly” is not deleted from the RAM 103 (simply deleted from the history display area (D)). The product data at the bottom to be deleted does not necessarily have to be the product data of the first registered product (“shrimp fry” in FIG. 6). For example, the product data is displayed at the bottom after sorting. Product data (for example, product data of a product with the lowest price when sorted in descending order (highest order) of the price).

  In addition, when a 000 ticket is further registered from the state of FIG. 6 (h), the lowermost product data (product data of “bakery bread” in FIG. 6 (h)) is deleted. That is, every time a ticket is registered, the product data is deleted in order to newly display the ticket data. However, at least one product data (for example, product data of the last registered product when displayed in descending order of registration order (newest order)) is displayed in the history display area (D). preferable.

  The mode in which the ticket data is displayed with priority over the product data is not limited to the mode in which the display of the product data is deleted. For example, if a xx ticket is registered from the state of FIG. 6 (g), the product data display or display area may be reduced and the ticket data of the xx ticket may be displayed as shown in FIG. 6 (i). Good. In FIG. 6 (g), the top and bottom intervals of the display areas of “rose growth”, “rose gambling”, “bakery bread”, and “shrimp fried” are narrowed, and the ticket data of xx tickets is displayed. That is, as it is, there is no area for displaying the ticket data of the XX ticket in the history display area (D), and therefore, the product data is displayed or displayed in order to secure an area for displaying the ticket data of the XX ticket. The area may be reduced.

  Moreover, you may use together the aspect which erase | eliminates the display of merchandise data of the lowest part, and the aspect which makes the display or display area of merchandise data small. For example, even if the display or display area of the product data is reduced, the display of the product data at the bottom may be deleted when it becomes impossible to secure an area for displaying new ticket data.

  Although it has been described that it is preferable that at least one product data is displayed in the history display area (D), if all product data display is not deleted, all registered ticket data is displayed. When it cannot be displayed, the ticket data display or display area may be reduced.

  Note that different display modes may be used for the product data and the ticket data. For example, the ticket data may be displayed with a character color different from the character color of the product data, or the background color of the characters of the ticket data may be different from the background color of the characters of the product data. Thereby, for example, registered ticket data can be found more easily.

  The merchandise sales data processing apparatus 1 of the above embodiment includes a POS register 10 and a change machine 20 that execute a registration process and a settlement process (excluding functions related to the conveyance of money executed by the change machine 20). The merchandise sales data processing apparatus according to the present invention is not necessarily required to have a settlement processing function. Therefore, the merchandise sales data processing apparatus according to the present invention may be the POS register 10 or a POS register (not shown; for convenience, referred to as the POS register 11) that mainly executes a registration process. When the POS register 11 is installed, a settlement apparatus (not shown) that performs a settlement process based on registered data registered in the POS register 11 may be separately installed. The merchandise sales data processing apparatus according to the present invention may not be a fixed type apparatus, but may be a portable type apparatus (for example, a handy terminal) having a wireless communication function. The merchandise sales data processing apparatus according to the present invention may be a vending machine or an automatic ticket vending machine.

  Note that the tickets are not limited to those printed on a medium such as paper. For example, the tickets may be electronic. For example, it may be one that is displayed on the screen of the customer's mobile terminal (for example, a smartphone), or may be received from the customer's mobile terminal by, for example, short-range communication. When the barcode displayed on the screen of the customer's mobile terminal includes a barcode (when an image relating to the ticket including the barcode is displayed), the scanner unit 104 displays the barcode. The ticket data may be acquired by optically reading.

  Note that the electronic ticket as described above may be consumed when the ticket is used. For example, when the scanner unit 104 reads the barcode of a ticket displayed on the screen of the mobile terminal and acquires ticket data, the POS register 10 indicates to the mobile terminal that the ticket has been consumed. The mobile terminal prohibits the subsequent use of the ticket (in the case of a ticket that can be used only once) or subtracts the number of times of use (can be used a predetermined number of times). In the case of a certain ticket), processing corresponding to the use may be performed. Similarly, when the use is canceled, the POS register 10 transmits information indicating that the consumption of the ticket is canceled to the portable terminal, so that the portable terminal Processing according to the cancellation of the use may be performed, such as canceling the prohibition of subsequent use or canceling the subtraction of the number of times of use.

  As mentioned above, although embodiment of this invention was explained in full detail, the concrete structure is not restricted to this embodiment, The design etc. of the range which does not deviate from the summary of this invention are included.

  A program for executing each process of the merchandise sales data processing apparatus 1 (or the POS register 10 or the POS register 11) of the present embodiment is recorded on a computer-readable recording medium and recorded on the recording medium. The above-described various processes related to each process of the merchandise sales data processing apparatus 1 (or the POS register 10 and the POS register 11) may be performed by causing the computer system to read and execute the program. Here, the “computer system” may include an OS and hardware such as peripheral devices. Further, the “computer system” includes a homepage providing environment (or display environment) if a WWW system is used. The “computer-readable recording medium” means a flexible disk, a magneto-optical disk, a ROM, a writable nonvolatile memory such as a flash memory, a portable medium such as a CD-ROM, a hard disk built in a computer system, etc. This is a storage device.

  Further, the “computer-readable recording medium” means a volatile memory (for example, DRAM (Dynamic DRAM) in a computer system that becomes a server or a client when a program is transmitted through a network such as the Internet or a communication line such as a telephone line. Random Access Memory)), etc., which hold programs for a certain period of time. The program may be transmitted from a computer system storing the program in a storage device or the like to another computer system via a transmission medium or by a transmission wave in the transmission medium. Here, the “transmission medium” for transmitting the program refers to a medium having a function of transmitting information, such as a network (communication network) such as the Internet or a communication line (communication line) such as a telephone line. The program may be for realizing a part of the functions described above. Furthermore, what can implement | achieve the function mentioned above in combination with the program already recorded on the computer system, what is called a difference file (difference program) may be sufficient.

The embodiment of the present invention has been described in detail with reference to the drawings. However, the specific configuration is not limited to this embodiment, and includes designs and the like that do not depart from the gist of the present invention.
Additional notes are disclosed below.
(Appendix 1)
A merchandise sales data processing apparatus according to an aspect of the present invention provides a merchandise sales data processing apparatus for registering merchandise purchased by a customer, registration means for registering data used for price settlement including at least merchandise data, and the registration means It is characterized by comprising display means for classifying the registered customer registration data by type and displaying them at different positions in the display area.
According to the merchandise sales data processing apparatus, the registered data is classified by type and displayed at different positions in the display area, so that data to be canceled can be easily found based on the type. Therefore, for example, it is possible to reduce the trouble of canceling registration of registered data during the registration process.
(Appendix 2)
In the product sales data processing apparatus, the registration unit registers the product data and ticket data of tickets used for the price settlement of the product as data used for the price settlement, and the display unit The product data registered by the registration unit and the ticket data may be classified and displayed at different positions in the display area.
According to the product sales data processing apparatus described above, there is a situation in which the use of a ticket registered with a stack to be used is canceled after registration, or the purchase of a product registered with a stack to be purchased is canceled after registration. When it occurs, the ticket data of the corresponding ticket and the product data of the corresponding product can be easily found from the respective positions. In other words, for example, it is possible to reduce the trouble of canceling registration of registered data during the registration process.
(Appendix 3)
The merchandise sales data processing apparatus is configured to display the ticket data classified and displayed by the display means at a position where the ticket data in the display area is displayed, in descending order or ascending order of registration order, or You may make it further provide the sorting means rearranged in order of descending or ascending order of the amount of money that can be used.
According to the merchandise sales data processing apparatus, the sorted ticket data is displayed, so that the corresponding ticket data can be found more easily. That is, for example, it is possible to reduce time and labor when canceling registration of registered ticket data during the registration process.
(Appendix 4)
The merchandise sales data processing device is configured to display the merchandise data classified and displayed by the display means at a position where the merchandise data is displayed in the display area, in descending or ascending order of registration order, or sales amount Sorting means for rearranging in descending order or ascending order may be further provided.
According to the merchandise sales data processing apparatus, the sorted merchandise data is displayed, so that the corresponding merchandise data can be found more easily. That is, for example, it is possible to reduce time and labor when canceling registration of registered product data during the registration process.
(Appendix 5)
In the product sales data processing apparatus, the display unit may display the classified and displayed ticket data in preference to the product data of the registered product.
According to the product sales data processing device, ticket data is displayed in the display area with priority over product data, so even when many products are registered, it becomes easier to grasp the registration status of tickets, or It becomes easier to process tickets.
(Appendix 6)
A program according to an aspect of the present invention registers a product registration step for registering the product and tickets used for payment for the product in a computer of a product sales data processing apparatus for registering a product purchased by a customer. A ticket registration step; and a display step of classifying the registered product data and the registered ticket data into different positions within a display area. And
According to the program, the same effect as described above can be obtained.
(Appendix 7)
The merchandise sales data processing apparatus according to one aspect of the present invention is a merchandise sales data processing apparatus having a display unit. In the merchandise sales data processing apparatus, a registration unit capable of registering tickets used for payment in addition to a product purchased by a customer; Display control means for displaying the product data of the products registered by the registration means and the ticket data of the tickets registered by the registration means side by side as registration data in a predetermined area of the display unit, Is capable of simultaneously displaying registration data up to a predetermined upper limit number, and the display control means displays the upper limit number of registration data including at least one product data side by side in the predetermined area. When a new ticket is registered by the registration means, the product data is deleted from the predetermined area, and the ticket data of the newly registered ticket is updated. Characterized in that to be displayed in a predetermined area.
(Appendix 8)
In the merchandise sales data processing apparatus according to appendix 7, the display control means allows the registration means to display a voucher by the registration means when the upper limit number of registration data including at least two pieces of merchandise data is displayed side by side in the predetermined area. When a category is newly registered, the lowest product data may be deleted from the predetermined area.
(Appendix 9)
In the merchandise sales data processing apparatus according to attachments 7 and 8, the display control unit may display the registration data and the ticket data in different display modes in the predetermined area.
(Appendix 10)
In order to solve the above-described problem, a program according to an aspect of the present invention has a display unit, and product sales data capable of simultaneously displaying registration data up to a predetermined upper limit number in a predetermined area of the display unit. A program that causes a computer to function as a processing device, in addition to products purchased by customers, registration means capable of registering tickets used for payment, product data of products registered by the registration means, The ticket data of the tickets registered by the registration means is caused to function as display control means for displaying the data in a predetermined area of the display unit as registration data, and the display control means includes at least one product data When tickets are newly registered by the registration means when the upper limit number of registered data is displayed side by side in the predetermined area. Together to erase the product data from the predetermined area, which is the ticket class data of the newly registered ticket class program characterized by displaying on the predetermined region.

DESCRIPTION OF SYMBOLS 1 ... Merchandise sales data processing apparatus 9 ... Counter stand 10 ... POS register (registration settlement apparatus)
DESCRIPTION OF SYMBOLS 11 ... POS register (registration device) 20 ... Change machine 101 ... CPU 102 ... ROM 103 ... RAM 104 ... Scanner unit 105 ... Salesperson display unit 106 ... Customer display unit 107 ... Hard disk 108 ... Operation unit 109 ... Communication unit 110 ... Buzzer 111 ... Printing section 112 ... Connection section 205 ... Operation section 210 ... Coin slot 211 ... Coin slot 212 ... Banknote slot 213 ... Banknote slot

Claims (4)

In a product sales data processing apparatus having a display unit,
In addition to products purchased by customers, registration means that can register tickets used for payment,
Display control means for displaying the product data of the product registered by the registration means and the ticket data of the tickets registered by the registration means in a predetermined area of the display unit as registration data;
The predetermined area can simultaneously display registration data up to a predetermined upper limit number,
The display control means includes
When the registration means is newly registered by the registration means when the upper limit number of registration data including at least one product data and at least one ticket data is displayed side by side in the predetermined area. In the registered data displayed in the predetermined area, the commodity data is deleted from the predetermined area with priority over the ticket data, and the ticket data of the newly registered ticket is displayed in the predetermined area. A product sales data processing apparatus characterized by that. The display control means includes
In the case where the upper limit number of registration data including at least two product data is displayed side by side in the predetermined area, when a ticket is newly registered by the registration means, it is displayed in the predetermined area. and merchandise sales data processing apparatus according to the bottom of the product data of the product data to claim 1, characterized in that to erase from the predetermined area has. The display control means includes
The product sales data processing apparatus according to claim 1 or 2, wherein the product data and the ticket data are displayed in different display modes in the predetermined area. A program for causing a computer to function as a product sales data processing apparatus having a display unit, and capable of simultaneously displaying registration data up to a predetermined upper limit number in a predetermined area of the display unit,
The computer,
In addition to products purchased by customers, registration means that can register tickets used for payment,
The product data of the product registered by the registration unit and the ticket data of the ticket registered by the registration unit function as a display control unit that displays the registration data side by side in a predetermined area of the display unit,
The display control means includes
When the registration means is newly registered by the registration means when the upper limit number of registration data including at least one product data and at least one ticket data is displayed side by side in the predetermined area. In the registered data displayed in the predetermined area, the commodity data is deleted from the predetermined area with priority over the ticket data, and the ticket data of the newly registered ticket is displayed in the predetermined area. A program characterized by that.

Images