JP2009093438A - Merchandise sales data processor and computer program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To prevent the occurrence of any sales chance loss even when it is determined that delivery is absent on a reception request date on the basis of a predetermined delivery date and time. <P>SOLUTION: When it is determined that the reserved acceptance of merchandise to be identified by input identification information on an input reception request date is possible (step S108: Y), a storage part is made to store the merchandise with the reception request date and time. When it is determined that the reserved acceptance of the merchandise to be identified by the input identification information on the input reception request date and time is not possible (step S108: N), the merchandise to be delivered on the reception request date and time is extracted from a delivery data file, and the input of the identification information of the extracted merchandise is permitted, and the storage part is made to store the merchandise to be identified by the input identification information with the input reception request date and time. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a merchandise sales data processing apparatus such as a POS terminal used in a store such as a convenience store and a computer program.

  Conventionally, reservation sales such as lunch boxes have been performed at convenience store stores, and reservation reception work is executed by an operation at a POS terminal installed in a convenience store. For pre-sale items, the delivery date and time is determined in advance based on the status of the delivery flight. A customer who wishes to make a product reservation visits the store and tells the operator clerk of the POS terminal the product he / she wants to make a reservation for and the date and time of receipt. If a reserved product or a customer's desired receipt date / time is input to the POS terminal, a delivery flight suitable for the input desired receipt date / time is retrieved from the POS terminal. For this reason, the storage device of the POS terminal stores a file in which the delivery date and time (scheduled date and time of delivery flights) of the pre-sold product is stored. Then, the reception of the reservation is completed by transmitting and storing the data such as the product, the desired reception date and time, and the searched delivery flight from the POS terminal to the host computer of the store management unit.

JP 2002-358443 A

  However, if a delivery flight suitable for the desired reception date / time is not searched and it is determined that there is no delivery at the desired reception date / time, an error occurs at the POS terminal, and the processing of the reservation reception work does not proceed any further. In this case, the operator store clerk tells the customer that the reservation cannot be accepted as desired, and a sales opportunity loss occurs.

  Patent Document 1 describes a technology in which a change in reservation conditions is solicited from a customer via a web screen when the number of reserved orders exceeds the number of supplies in a network (Internet) sales system. ing. However, with the technique described in Patent Document 1, there may be a case where the number of reserved ordered products again exceeds the number of supplies even if the reservation conditions are changed. In such a case, the customer feels dissatisfied and stops the reservation, and there is a possibility that a sales opportunity loss occurs.

  An object of the present invention is to prevent a loss of sales chance even when it is determined that there is no delivery at a desired reception date based on a predetermined delivery date.

  The merchandise sales data processing apparatus of the present invention includes an information processing unit that executes information processing, and an operation unit having an information input function by a user operation, and the information processing unit is operated by an operation on the operation unit. Delivery data in which product identification information is allowed to be input, the information processing unit is allowed to input a desired receipt date and time of the product by an operation on the operation unit, and the information processing unit stores the delivery date and time of the product By referring to the delivery date and time stored in the file and determining the presence or absence of delivery at the input desired reception date and time for the product identified by the input identification information, the product at the desired reception date and time is determined. When it is determined whether or not a reservation can be received, and the information processing unit determines that a reservation can be received at the input desired reception date and time for the product identified by the input identification information. The product is stored in the storage unit together with the desired reception date and time, and the information processing unit determines that the reservation received at the input desired reception date and time is not possible for the product identified by the input identification information. In this case, the product having the delivery of the desired receipt date and time is extracted from the delivery data file, the identification information of the extracted product is allowed to be input by the operation in the operation unit, and is identified by the inputted identification information. The product is stored in the storage unit together with the input desired reception date and time.

  The computer program of the present invention is installed in a computer of a product sales data processing apparatus having an operation unit having an information input function by a user's operation, and inputs identification information of the product to the computer by an operation on the operation unit. Referring to the function to allow, the function to allow the input of the desired receipt date and time of the product by the operation on the operation unit, and the delivery date and time stored in the delivery data file for storing the delivery date and time of the product. A function for determining whether or not a reservation for the product can be received at the desired reception date and time by determining the presence or absence of delivery at the input desired reception date and time for the product identified by the identification information; If it is determined that a reservation can be accepted for the product identified by the identified identification information at the input receipt date and time, When it is determined that the product can be stored in the storage unit together with the desired reception date and time, and the product identified by the input identification information cannot be reserved at the input desired reception date and time, the desired reception date and time The product having the delivery of the product is extracted from the delivery data file and the identification information of the extracted product is allowed to be input by the operation in the operation unit, and the product identified by the input identification information is input. And a function of storing in the storage unit together with the desired reception date and time.

  According to the present invention, even when it is determined that there is no delivery of the input desired date and time for the input product, the customer is allowed to input the product with the delivery of the desired date and time of receipt. You can make a reservation for alternative products on the spot. Therefore, it is possible to avoid a loss of sales chance when it is determined that there is no delivery at the desired reception date and time.

  An embodiment of the present invention will be described with reference to FIGS. The present embodiment is an application example to the POS terminal 101 that constitutes the POS system 1 installed in a store that is a convenience store.

  FIG. 1 is a system configuration diagram showing a POS system 1. The POS system 1 includes a store controller 201 as a host device installed in a store backyard, and a plurality of POS terminals 101 installed in a store accounting location. The store controller 201 and the POS terminal 101 are connected to each other via a local communication line network 251 such as a LAN so that data communication is possible. The on-premises communication line network 251 is connected to a host computer 291 installed in the general department of the store via an external communication line network 271. Therefore, the POS terminal 101 and the store controller 201 are connected to the host computer 291 so that data communication is possible. The storage device of the host computer 291 stores a reserved data file 292 to be described later.

  FIG. 2 is an external perspective view showing the POS terminal 101. The POS terminal 101 is placed on the drawer 102 and can control the opening operation of the drawer 103 of the drawer 102. A keyboard 104 and an operator display 105 are arranged on the right side of the upper surface of the POS terminal 101, and a receipt printer 106 is arranged on the left side of the upper surface. The keyboard 104 is used to start a reception work process, which will be described later, in addition to a numeric keypad for inputting numbers, a subtotal key as a temporary closing key, a deposit / current total key as a closing key (none of which are shown). It includes a reception service key 104a to be pressed. On the display screen of the operator display 105, a touch panel 112 as an operation unit is arranged. A customer display 107 is erected on the back side of the operator display 105. In FIG. 2, a groove provided in the vicinity of the right side surface of the POS terminal 101 is a card reading groove 109 for scanning a card in order to read card information by the card reader / writer 108 (see FIG. 3). . The POS terminal 101 includes an HDD 151 and a CD-ROM drive 152 as storage devices (see FIG. 3). Therefore, a CD-ROM tray (not shown) for mounting the CD-ROM 152a is provided on the right side surface of the POS terminal 101 when viewed from the operator. The POS terminal 101 is connected to a barcode reader 111 that optically reads a barcode attached to a product. As with the keyboard 104, the barcode reader 111 constitutes a product code input unit for inputting a product code.

  FIG. 3 is a block diagram illustrating a hardware configuration of the POS terminal 101. The POS terminal 101 includes a CPU 153 as an information processing unit that executes various arithmetic processes and controls each unit. The CPU 153 is connected via a bus line 156 to a ROM 154 that stores fixed data in a fixed manner and a RAM 155 that stores variable data in a rewritable manner and is used as a work area. The aforementioned HDD 151 and CD-ROM drive 152 are also connected to the CPU 153 via the bus line 156. The drawer 102, the keyboard 104, the operator display 105, the receipt printer 106, the customer display 107, the card reader / writer 108, the barcode reader 111, and the touch panel 112 all have various input / output circuits ( All are not shown) and are connected to the CPU 153 via the bus line 156 and controlled by the CPU 153. Further, the POS terminal 101 includes a communication interface 157 for connecting to a store controller 201 as a host device via a local communication line network 251 provided in the store. The communication interface 157 is also connected to the bus line 156. It is connected to the CPU 153 via.

  The HDD 151 shown in FIG. 3 is installed with an operating system and computer programs for various processes in addition to merchandise sales data processing. For example, these operating systems and computer programs are stored and stored in a recording medium called a CD-ROM 152 a, read by the CD-ROM drive 152, and installed in the HDD 151. As another example, it may be downloaded from the store controller 201 via the local communication network 251 and installed in the HDD 151. Such an operating system and merchandise sales data processing program are used by copying all or a part of the POS terminal 101 to the RAM 155 when the POS terminal 101 is activated. In addition to the product data file (not shown) in which the product name, unit price, department, etc. are stored in association with the product code, such HDD 151 also has a delivery service data file F1 ( 4) and a delivery product data file F2 (see FIG. 5) are stored. The delivery service data file F1 and the delivery product data file F2 are transmitted from the host computer 291 or the store controller 201 as needed and stored in the HDD 151.

  FIG. 4 is a schematic diagram showing a data structure of the delivery service data file F1. The delivery service data file F1 is a file that stores the delivery date and time for each submenu for each menu. Here, the relationship between the menu and the sub menu will be described. A plurality of submenus are associated with one menu. For example, the menu “Reserved lunch 1” is associated with submenus “Reserved lunch A”, “Reserved lunch B”,. Furthermore, a plurality of products (“A1 lunch”, “A2 lunch”,...) Are associated with one submenu (for example, “reserved lunch A”) (see FIG. 5).

  As shown in FIG. 4, the delivery service data file F1 more specifically stores a reservation acceptance start date and time F11 and a detailed delivery status F12 for each submenu. The reservation reception start date and time F11 stores the start date and time of the reservation reception service. The delivery status F12 stores “delivery date”, “delivery flight”, “pause (end of delivery)”, “preparing for reception”, “delivery only”. “Delivery date” stores the date and day of the week. The “delivery flight” stores the time for each delivery flight (1 flight, 2 flights, 3 flights) on the delivery date. Here, the previous day's flight at 21:00 is one flight of the day. That is, one flight on a certain delivery date is a flight at 21:00 on the previous day, two flights are on a flight at 10:00 on the delivery date, and three flights are on a flight at 18:00 on the delivery date. For example, a flight delivered at 21:00 on Tuesday, November 8 is one flight on Wednesday, November 9. In “pause (end of delivery)”, for each flight, a flag (check box in FIG. 4) is stored when the delivery is not delivered or the delivery has already been finished. . In “preparing for reception”, a flag (indicating a check box in FIG. 4) is stored for a delivery flight that has not yet started reception of reservation sales. In “Delivery Only”, a flag (a check box in FIG. 4) is stored for a day on which a product is delivered by a delivery flight but a reservation sales acceptance is finished.

  FIG. 5 is a schematic diagram showing a data structure of the delivery product data file F2. The delivered product data file F2 is a file that stores products related to each submenu. For example, the product “A1 lunch box”, “A2 lunch box”, “A3 lunch box”, and “A4 lunch box” are associated with the submenu “reserved lunch box A”. Therefore, the submenu constitutes product identification information. Further, the delivered product data file F2 stores the unit price associated with each product.

  Next, based on FIG.6 and FIG.7, the reception work process performed with the POS terminal 101 is demonstrated.

  FIG. 6 is a flowchart showing the flow of reception work processing. FIG. 7 is a schematic diagram illustrating a screen display example of the operator display 105 that transitions according to the reception operation. The reception job process is started when the reception job key 104a included in the keyboard 104 is pressed. When the reception work key 104a is pressed (step S101), the CPU 153 generates a reception work start screen 511 and displays it on the operator display 105.

  As shown in FIG. 7A, the reception work start screen 511 has a plurality of reception service keys 512. The reception service key 512 includes a reservation key 513 displayed as “reservation” for starting a reception service for a reservation product such as a reservation lunch. When the reservation key 513 is touched (step S102), the CPU 153 displays a menu input screen 521. As shown in FIG. 7B, the menu input screen 521 includes a menu key 522 for displaying a reserved product. Menu key 522 includes, for example, a key displayed as “Reserved lunch 1”. The CPU 153 displays a submenu input screen 531 by touching one menu key 522 (step S103). As shown in FIG. 7C, the submenu input screen 531 includes a submenu key 532 associated with the touch-designated menu key 522. Here, the sub-menu input screen 531 is a sub-menu that displays sub-menus associated with the menu “Reserved lunch 1”, “Reserved lunch A”, “Reserved lunch B”, “Reserved lunch C”, and “Reserved lunch D”. It has a menu key 532. In response to the touch designation of the submenu key 532 (step S104), the CPU 153 displays a desired receipt date input screen 541. Since the submenu constitutes product identification information (see FIG. 5), a function of allowing input of product identification information by a touch operation of the submenu key 532 is realized.

  As shown in FIG. 7D, the desired receipt date input screen 541 includes a desired receipt date input key 542 for inputting the desired receipt date of the customer. The desired date input key 542 displays a date. The desired receiving date input screen 541 has a calendar portion in which the date is divided into each date by a grid, and the desired receiving date input keys 542 are arranged on the grid corresponding to the date of this calendar portion. The desired receipt date input key 542 included in the desired receipt date input screen 541 is based on the data contents of the delivery flight data file F1 and the date on which the submenu is delivered (even if all flights are "pause (end of delivery)"). The key is displayed only for dates that are not “preparing for reception”. For example, when only three flights are “preparing for reception”, a key is displayed. In response to the touch designation of the desired receipt date input key 542 (step S105), the CPU 153 displays a desired receipt time input screen 551.

  As shown in FIG. 7E, the desired reception time input screen 551 includes a desired reception time input key 552 for inputting the desired reception time, and a registration key 553 displayed as “Register”. A plurality of desired reception time input keys 552 are provided, and a number is displayed on each. A number corresponding to the desired reception time input key 552 designated by touching is displayed on the time display 554. Then, when the registration key 553 is touched, the number displayed on the time display 554 is input as the desired reception time. Thus, the date input by the touch designation of the desired receipt date input key 542 on the desired receipt date input screen 541 and the hour and minute input by the touch designation of the desired reception time input key 552 of the desired reception time input screen 551 are displayed. Based on the desired receipt date and time. In response to the input of the desired reception time by the touch designation of the registration key 553 (step S106), the CPU 153 next executes a search process for determining whether or not the reservation reception at the input desired reception date and time is possible. (Step S107). Details of the search process will be described later (see FIG. 8). As a result of the search process, if it is determined that the reservation can be accepted at the input desired reception date and time (Y in step S108), the CPU 153 subsequently executes the optimum flight determination process (step S109). Details of the optimum flight determination process will be described later (see FIG. 9). As a result of the search processing, if it is determined that the reservation reception at the input desired reception date / time is not possible (N in step S108), the CPU 153 subsequently executes error processing (step S110). Details of the error processing will be described later (see FIGS. 11, 12, and 13).

  FIG. 8 is a flowchart showing the flow of search processing. First, the CPU 153 refers to the delivery service data file F1 for the submenu selected by touch designation of the submenu key 532, and the touch designation date / time of the registration key 553, that is, the input operation date / time of the desired receipt date / time is the reservation acceptance period. It is determined whether it is within (step S201). In step S201, first, with reference to the reservation reception start date and time F11, it is determined whether or not the input operation date and time of the desired reception date and time is after the reservation reception start date and time. If the input operation date / time of the desired reception date / time is after the reservation reception start date / time, then refer to “Delivery Only” in the delivery status F12 and set the input operation date / time of the desired reception date / time to the date / time of “Delivery Only”. It is determined whether or not it is applied. If the input operation date / time of the desired receipt date / time is before the reservation acceptance start date / time, or if the input operation date / time of the desired reception date / time falls on the date / time of “Delivery only”, the input operation date / time of the desired reception date / time Is outside the acceptance period (N in step S201), and error processing is executed (step S213). In the error processing in step S213, a pattern 1 error or pattern 2 error processing (see FIG. 12) described later is executed.

  If it is determined in step S201 in the flowchart of FIG. 8 that the input operation date / time of the desired reception date / time is within the reception period (Y in step S201), the input desired reception date / time is then converted to “delivery date”. (Step S202). The “delivery date” is a date corresponding to the “delivery flight” in the delivery status F12 of the delivery flight data file F1. For example, when the input desired reception date and time is “November 7, 23:00”, the “Delivery date” is November 8.

  Next, in steps S203 to S208 of the flowchart of FIG. 8, a flight search process is executed. In this flight search process, a delivery flight suitable for the input desired reception date and time is searched. More specifically, it is determined that the delivery date converted in step S202 is not closed in the order of 3 flights, 2 flights, and 1 flight (steps S203, S205, and S207). It is determined that minute <preferred time of receipt (steps S204, S206, S208). For example, if the desired reception time is 13:00, the second flight time (10: 00 + 30 minutes) <13:00, so that two flights are determined as delivery flights suitable for the desired reception date and time. If a suitable delivery flight is not found by executing the flight search process (Y in step S207, N in step S208), the same flight search process (the previous day flight search process) is performed for the delivery date the day before the converted delivery date. Execute (Step S209). If a suitable delivery flight is not found even by executing the previous day flight search process (Y in step S210), the delivery flight on the previous day delivery date has already been delivered, and an error process is executed ( Step S211). In the error process in step S211, a pattern 3 error process (see FIG. 13) described later is executed. If a suitable flight is searched by executing the flight search process (steps S203 to S208) or the previous day flight search process (step S209) (Y in step S204, Y in S206, Y in S208, N in S210), a reservation is made. With reference to the reception start date and time F11, it is determined whether or not the delivery flight is “preparing for reception” (step S213). When it is “preparing for reception” (Y in step S213), error processing is executed (step S215). In the error process in step S215, a pattern 4 error process (see FIG. 13) described later is executed. If the delivery flight is not “preparing for acceptance” (N in step S213), the optimum flight determination process is executed (step S214).

  FIG. 9 is a flowchart showing the flow of the optimum flight determination process. FIG. 10 is a schematic diagram showing a screen display example of the operator display 105 that transitions according to the optimum flight determination operation. Based on FIGS. 9 and 10, the optimum flight determination process will be described. In the optimum flight determination process, first, the CPU 153 displays the flight selection screen 611 on the operator display 105.

  As shown in FIG. 10A, the flight selection screen 611 includes a previous flight selection key 612, a recommended flight selection key 613, and a next flight selection key 614. The recommended flight selection key 613 is a key that displays a delivery flight suitable for the customer's desired reception date and time as a “recommended flight” searched by executing the flight search process or the previous day flight search process (see FIG. 8). The previous flight selection key 612 is a key for displaying a delivery flight corresponding to the previous flight of the “recommended flight” as “previous flight”. The next flight selection key 614 is a key for displaying a delivery flight corresponding to the next flight of the “recommended flight” as “next flight”. In response to the flight selection by touch designation of any of the previous flight selection key 612, the recommended flight selection key 613, and the next flight selection key 614 (step S301), the CPU 153 displays the product selection screen 621.

  As shown in FIG. 10B, the product selection screen 621 has a plurality of product selection keys 622. The product selection key 622 extracts the data of the product related to the submenu specified in the reception work process (see S104 in the flowchart of FIG. 6 and FIG. 7C) from the delivered product data file F2 and displays the key. It is a thing. That is, the CPU 153 displays selectable products (step S302). In response to the touch designation of an arbitrary product selection key 622 included in the product selection screen 621, the CPU 153 displays a quantity input screen 631.

  As shown in FIG. 10C, the quantity input screen 631 includes a quantity input key 632 for inputting the quantity of the product desired by the customer, and a quantity registration key 633 displayed as “Register”. A plurality of quantity input keys 632 are provided, and a number is displayed on each. A number corresponding to the touch-specified quantity input key 632 is displayed on the quantity display 634. Then, the number displayed on the quantity display 634 is input as a desired quantity by the touch designation of the quantity registration key 633. Thereby, product selection and quantity input are performed (step S303). In response to the touch designation of the quantity registration key 633, the CPU 153 displays a product selection screen 641.

  As shown in FIG. 10D, the product selection screen 641 is substantially the same as the product selection screen 621 shown in FIG. The product selection screen 641 is significantly different from the product selection screen 621 in that the product selection screen 641 displays an input quantity display 642 based on the input quantity in association with the product. Further, the product selection screen 641 has a confirmation key 643 at the upper right of the screen. Until the touch designation of the confirmation key 643 is made, the product selection key 644 for another product can be touch designated on the product selection screen 641. When another product selection key 644 is touched, the quantity input screen 631 is displayed again and the quantity is input. The CPU 153 displays a confirmation screen 651 in response to the touch designation of the confirmation key 643.

  As shown in FIG. 10E, the confirmation screen 651 has a status display 652. The status display 652 includes the input receipt date and time, the selected delivery flight, the selected product, the input quantity, and the amount based on the unit price and the input quantity of the selected product. The confirmation screen 651 has an inquiry key 653 displaying “inquiry” at the lower right of the screen. In response to the touch designation of the inquiry key 653 (step S304), the CPU 153 includes the contents included in the status display 652 (the input desired reception date and time, the selected delivery flight, the selected product, the input quantity, and the selection The data of the unit price of the product and the amount of money (based on the input quantity) is transmitted and output to the host computer 291 via the communication interface 157 as an order inquiry. At this time, the CPU 153 stores this data in a predetermined storage area provided in the HDD 151 serving as a storage unit. The data is stored in association with each item (input date and time of receipt, selected delivery service, selected product, input quantity, and amount based on unit price and input quantity of the selected product). The In addition, you may make it memorize | store in other memory | storage parts, such as RAM155. Data transmitted and output to the host computer 291 is transmitted to the host computer 291 via the local communication line network 251 and the external communication line network 271. During the order inquiry, a character display (not shown) “Please wait for a while” is displayed on the confirmation screen 651. In the host computer 291, the received data is stored in a reserved data file 292 (see FIG. 1). The reserved data file 292 is a file that stores reserved products together with the desired reception date and time. The transmitted data is stored in a state where each item is associated with the reserved data file 292. If the host computer 291 stores the data received in the reserved data file 292, a message to that effect is returned to the POS terminal 101. At this time, if the storage to the reserved data file 292 is not normally performed, a message to that effect is returned. The CPU 153 of the POS terminal 101 determines whether or not the reservation has been normally received in response to the reply from the host computer 291. If it is determined that it has been performed normally (Y in step S305), a reservation acceptance establishment process is executed (step S306). In the reservation acceptance process, a character display (not shown) of “accepted with the above contents” is displayed below the status display 652 on the confirmation screen 651. If it is determined that the reservation is not normally received (N in step S305), a predetermined reservation reception error process is executed (step S307). In the reservation acceptance error process, for example, the touch designation of the inquiry key 653 is requested again.

  FIG. 11 is a flowchart showing the flow of error processing. First, the CPU 153 displays an error POP-UP display (not shown) on the screen of the operator display 105 (step S401). The error POP-UP display includes an error cancel key (not shown). In response to the error cancellation by touching the error cancellation key (step S402), the CPU 153 determines the error content (steps S403 to S406). In the search process (see FIG. 8), the input operation date / time of the desired receipt date / time is earlier than the reservation acceptance start date / time (see step S201 in FIG. 8), so that the CPU 153 determines that the operation was performed before the acceptance period. In this case (Y in step S403), pattern 1 error processing is executed (step S407). When it is determined in the search process (see FIG. 8) that the input operation date / time of the desired receipt date / time is the date of “only delivery” (see step S201 in FIG. 8), (Step S404 Y), pattern 2 error processing is executed (Step S408). When there is no flight suitable for the delivery date converted by the search process (see FIG. 8), and there is no previous day flight (see step S210 in FIG. 8), the delivery flight up to the desired reception date and time has already ended. If it is determined that the period until the desired reception date and time is too short (Y in step S405), pattern 3 error processing is executed (step S409). Since the delivery flight searched in the search process (see FIG. 8) is “preparing for acceptance” (see step S213 in FIG. 8), the delivery flight has not yet received a reservation, and the operation and receipt If it is determined that the period up to the desired date and time is too long (Y in step S406), pattern 4 error processing is executed (step S410).

  FIG. 12 is a flowchart showing a flow of processing of pattern 1 error and pattern 2 error together with a screen display example. When processing a pattern 1 error, first, a pattern 1 error screen 711 is displayed on the operator display 105, and when processing a pattern 2 error, a pattern 2 error screen 721 is displayed on the operator display 105.

  As shown in FIG. 12, the pattern 1 error screen 711 displays the reservation start date and time of the selected submenu under the title “content not accepted”. The reservation start date and time is based on the reservation reception start date and time F11 of the delivery service data file F1. The pattern 1 error screen 711 further includes a key 712 on which “display menu that can be received at XX month XX day HH hour MM minute” is displayed. “XX month XX day HH hour MM minute” displayed by the key 712 is based on the input desired reception date and time.

  As shown in FIG. 12, the pattern 2 error screen 721 displays that the reservation reception of the selected submenu has already ended under the title “contents that cannot be received”. The pattern 2 error screen 721 further includes a key 722 on which “display menu that can be received at XX month XX day HH hour MM minute” is displayed. “XX month XX day HH hour MM minute” displayed by the key 722 is based on the input desired reception date and time.

  As shown in FIG. 12, the same processing is executed for the pattern 1 error and the pattern 2 error. That is, in step S501, if the key 712 or key 722 displayed as “Display menu that can be received at XX month XX day HH hour MM minute” is designated by touch (step S501), the CPU 153 receives the input. The delivery data file F1 is searched for all menus based on the desired receipt date and time (step S502), and a menu capable of delivery at the desired receipt date and time is displayed as a key (step S503). At this time, a screen display similar to the menu input screen 521 is displayed on the operator display 105. Here, the determination that the delivery at the desired receipt date and time is possible is performed by executing the same process as the flight search process and the previous day flight search process described with reference to FIG. In response to the touch designation of the displayed menu key (step S504), a submenu capable of delivery at the desired reception date and time is extracted from the delivery service data file F1 (step S505), and the extracted submenu is displayed as a key (step S505). Step S506). At this time, the operator display 105 displays a screen similar to the submenu input screen 531. Then, in response to the touch designation of the submenu key (step S507), the flight search process and the previous day flight search process described based on FIG. 8 are executed (step S508), and then based on FIG. 9 and FIG. The described optimum flight determination process is executed again (step S509).

  FIG. 13 is a flowchart showing the flow of processing of pattern 3 error and pattern 4 error together with a screen display example. When processing a pattern 3 error, first, a pattern 3 error screen 731 is displayed on the operator display 105, and when processing a pattern 4 error, a pattern 4 error screen 741 is displayed.

  As shown in FIG. 13, the pattern 3 error screen 731 displays under the title “content not acceptable” that there is no delivery in time for the input desired receiving date and time and that it is not in time. Further, the pattern 3 error screen 731 includes a key 732 displayed as “change the desired reception time” and a key 733 displayed as “display a menu that can be received at XX month XX day HH hours MM minutes”. Have.

  As shown in FIG. 13, the pattern 4 error screen 741 displays, under the title “content not accepted”, that delivery acceptance at the desired receipt date and time is being prepared and has not yet started. Further, the pattern 4 error screen 741 includes a key 742 displayed as “change the desired reception time” and a key 743 displayed as “display a menu that can be received at XX month XX day HH hours MM minutes”. Have.

  The process from step S601 to S609 shown in FIG. 13 is performed by using the key 733 of the pattern 3 error screen 731 or the pattern 4 error screen displaying “Display menu acceptable for XX month XX day HH hour MM”. The process is executed by touch designation of a key 743 of 741. The contents of this process are the same as steps S501 to S509 described with reference to FIG.

  The processing from step S701 to S704 shown in FIG. 13 is executed by touch designation of the key 732 on the pattern 3 error screen 731 or the key 742 on the pattern 4 error screen 741 where “change desired reception time” is displayed. Is done. In response to the key touch designation (step S701), the CPU 153 causes the operator display 105 to display a desired reception time input screen 551 for inputting the desired reception time shown in FIG. In the case of the pattern 4 error, the previous flight on the delivery date of the optimal flight is not “restored” or “preparing for reception”, so only the time is changed. Then, the CPU 153 performs the flight search process and the previous day flight search process described with reference to FIG. 8 according to the input of the desired reception time by the touch designation of the desired reception time input key 552 and the registration key 553 (step S702). (Step S703), and then the optimum flight determination process described with reference to FIGS. 9 and 10 is executed again (Step S704).

  As described above, according to the present embodiment, even when it is determined that there is no delivery at the input date and time of receipt, the input for the product (menu, submenu) having the delivery at the date and time of receipt is received. Because it is acceptable (pattern 1 error or pattern 4 error), the customer can book for a replacement on the spot. Therefore, it is possible to avoid a loss of sales chance when it is determined that there is no delivery at the desired reception date and time. Further, according to the present embodiment, since it is possible to change the desired reception time (pattern 3 error and pattern 4 error) when it is determined that there is no delivery at the input desired reception date and time, the customer wishes to make a reservation. It is possible to make a reservation for a product by changing the desired receipt time. Even in this case, the store can avoid loss of sales opportunities.

It is a system configuration figure showing a POS system. It is an external appearance perspective view which shows a POS terminal. It is a block diagram which shows the hardware constitutions of a POS terminal. It is a schematic diagram which shows the data structure of a delivery service data file. It is a schematic diagram which shows the data structure of a delivery goods data file. It is a flowchart which shows the flow of a reception work process. It is a schematic diagram which shows the example of a screen display of the display for operators which changes according to reception work operation. It is a flowchart which shows the flow of a search process. It is a flowchart which shows the flow of the optimal flight determination process. It is a schematic diagram which shows the example of a screen display of the display for operators which changes according to optimal flight determination operation. It is a flowchart which shows the flow of an error process. It is a flowchart which shows the flow of a process of a pattern 1 error and a pattern 2 error with a screen display example. It is a flowchart which shows the flow of a process of a pattern 3 error and a pattern 4 error with the example of a screen display.

Explanation of symbols

  101 ... POS terminal (product sales data processing device), 112 ... touch panel (operation unit), 153 ... CPU (information processing unit), F1 ... delivery service data file (delivery data file), F2 ... delivery product data file (delivery data) File)

Claims (6)

An information processing unit for executing information processing;
An operation unit having an information input function by a user operation;
Means for allowing the information processing section to input product identification information by an operation on the operation section;
Means for allowing the information processing unit to input a desired date and time of receipt of goods by an operation on the operation unit;
Presence or absence of delivery of the input desired reception date and time for the product identified by the input identification information with reference to the delivery date and time stored in the delivery data file in which the information processing unit stores the delivery date and time of the product Means for determining whether or not reservation acceptance of the product at the desired reception date and time is possible,
Means for storing the product in the storage unit together with the desired reception date and time when the information processing unit determines that the product identified by the input identification information can be reserved at the input desired reception date and time. When,
If the information processing unit determines that the product identified by the input identification information cannot be reserved at the input desired reception date and time, the product having the delivery of the desired reception date and time is selected as the delivery data. Allowing input of identification information of the extracted product extracted from the file and operated by the operation unit, and storing the product identified by the input identification information together with the input desired reception date and time in the storage unit Means to
A product sales data processing apparatus comprising: The information processing unit
When allowing the input of the desired receipt date and time, referring to the delivery date and time stored in the delivery data file, the desired receipt date and time only from the date on which the product identified by the input identification information is delivered Allow input,
The merchandise sales data processing apparatus according to claim 1. The information processing unit
When it is determined that the product identified by the input identification information cannot be reserved at the input desired reception date and time, the product can be delivered at another time on the desired reception date. If it is determined, the change to another time when the delivery is possible is allowed, and the product identified by the input identification information is stored in the storage unit together with the desired reception date and time based on the changed time. Let
The merchandise sales data processing apparatus according to claim 2. Installed in the computer of the merchandise sales data processing apparatus having an operation unit having an information input function by the user's operation,
A function that allows input of product identification information by an operation on the operation unit;
A function that allows an input of a desired receipt date and time of the product by an operation on the operation unit;
By determining the presence or absence of delivery of the input desired reception date and time for the product identified by the input identification information with reference to the delivery date and time stored in the delivery data file storing the delivery date and time of the product, A function for determining whether or not a reservation for the product can be received at the desired reception date and time;
A function for storing the product together with the desired reception date and time in a storage unit when it is determined that reservation acceptance at the input desired reception date and time is possible for the product identified by the input identification information;
When it is determined that reservation acceptance at the input desired reception date and time is not possible for the product identified by the input identification information, the product with delivery of the desired reception date is extracted from the delivery data file and A function of allowing input of identification information of the extracted product by an operation on the operation unit, and storing the product identified by the input identification information in the storage unit together with the input desired reception date and time;
A computer program that executes When allowing the input of the desired receipt date and time, referring to the delivery date and time stored in the delivery data file, the desired receipt date and time only from the date on which the product identified by the input identification information is delivered Causing the computer to execute a function that allows input of
The computer program according to claim 4. When it is determined that the product identified by the input identification information cannot be reserved at the input desired reception date and time, the product can be delivered at another time on the desired reception date. If it is determined, the change to another time when the delivery is possible is allowed, and the product identified by the input identification information is stored in the storage unit together with the desired reception date and time based on the changed time. Causing the computer to execute a function to
The computer program according to claim 5.

Images