Sales data processor and program

Abstract

To reduce the number of times to register sales from external orders in an existing system.SOLUTION: A sales data processor is used together with a management device that manages order information, which is information on orders accepted by a store, performs accounting based on the order information, and registers the order information that has been accounted for as sales information. A sales data processor includes: an acquisition unit acquires the order information that has not yet been registered as the sales information from the management device; and a registration unit that generates and registers the sales information based on the order information acquired by the acquisition unit.SELECTED DRAWING: Figure 7

Description

[Technical field]

[0001] An embodiment of the present invention relates to a sales data processing device and a program. [Background technology]

[0002] Conventionally, systems in which order terminals, kitchen equipment, and POS are managed centrally at an order station have been widespread in restaurants and other establishments. In recent years, a business model has become established in which restaurants and other establishments receive takeout orders online from outside the store while the store is open. Various systems for this purpose have been devised (for example, Patent Document 1).

[0003] In the recent business model described above, when managing store sales using existing systems, it is necessary to register sales from online orders. This task is cumbersome because it is unrelated to the task of handing over take-out orders, and there is also the risk that the task may be forgotten. There are no existing systems that solve this problem.

[0004] In addition, even for orders other than those received from outside the store, for items that do not require payment at the time of delivery, the sales registration process may be perceived as cumbersome, or the sales registration process may be put off and forgotten. Summary of the Invention [Problem to be solved by the invention]

[0005] The problem to be solved by the present invention is to provide a sales data processing device and program that can reduce the amount of work required to register sales from external orders into an existing system. [Means for solving the problem]

[0006] The sales data processing device of the embodiment is used together with a management device that manages order information, which is information on orders accepted by a store, performs accounting based on the order information, and registers the accounted order information as sales information.The sales data processing device includes an acquisition unit that acquires, from the management device, order information that is information on orders accepted by a store but has not yet been registered as sales information, and a registration unit that generates and registers the sales information based on the order information acquired by the acquisition unit. [Brief description of the drawings]

[0007] [Figure 1] FIG. 1 is a diagram illustrating an example of a system configuration according to an embodiment. [Diagram 2] FIG. 2 is a block diagram showing an example of the hardware configuration of the order station 3 and the order server 1. As shown in FIG. [Diagram 3] FIG. 3 is a block diagram showing an example of the hardware configuration of the POS 5. As shown in FIG. [Figure 4] FIG. 4 is a block diagram showing an example of a functional configuration of each of the control units 10, 30, and 50. As shown in FIG. [Diagram 5] FIG. 5 is a sequence diagram illustrating the cooperation between the devices. [Figure 6] FIG. 6 is a diagram showing an example of the flow of in-store transaction processing executed by the control unit 50 of the POS 5. [Figure 7] FIG. 7 is a diagram showing an example of the flow of the batch reflection process executed by the control unit 50 of the POS 5. [Figure 8] FIG. 8 is a diagram showing an example of the flow of the daily settlement process executed by the control unit 50 of the POS 5. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] (First embodiment) An embodiment will be described with reference to the drawings. Fig. 1 is a diagram showing an example of a system configuration of an embodiment. This system includes an order server 1, an order station 3, a POS 5, an order terminal 6, a kitchen device 7, an application server 8, and the like.

[0009] The order server 1 and the application server 8 are cloud servers. The order server 1 manages information on orders (order information) from outside the store. The application server 8 accepts product orders from an application program running on a customer terminal 9, and provides the order server 1 with information on the order (order information).

[0010] Devices such as the order station 3, POS 5, order terminal 6, and kitchen equipment 7 are installed within the store.

[0011] Communication between the order server 1 and the order station 3 is performed via an external network 21, an internal network 22, and a store router 23. The store router 23 connects the external network 21 and the internal network 22. The external network 21 is realized, for example, by the Internet. The internal network 22 is realized, for example, by a LAN (Local Area Network). The internal network 22 connects each device in the store so that they can send and receive information (communicate) with each other.

[0012] The order station 3 is an example of a management device that manages order information, which is information on orders received by the store. The order station 3 also comprehensively manages information handled by other devices in the store (such as the POS 5, order terminals 6, and kitchen equipment 7). The order station 3 also communicates with the order server 1 to share the information they manage (such as order information and product master data).

[0013] The POS 5 is an example of a sales data processing device that performs accounting based on order information and registers the order information as sales information. The POS 5 generates and stores sales information on products provided by the store based on the order information managed by the order station 3.

[0014] Here, "POS" is an abbreviation of "Point Of Sale" and means "point of sale information management." The POS5 is a terminal that performs point of sale information management. In this embodiment, the POS5 includes a master terminal and a satellite terminal. The POS5 that is the master terminal manages information of the POS5 that is the satellite terminal.

[0015] The order terminal 6 is a device for inputting information about ordered products. The order terminal 6 is used when a store clerk receives orders from customers in the store.

[0016] The kitchen equipment 7 is a display or printer installed in the kitchen and is used by the kitchen staff. The kitchen equipment 7, which is a display, acquires and displays (outputs) order information managed by the order station 3. The kitchen equipment 7, which is a printer, issues (outputs) an order slip on which the order information is printed.

[0017] It is preferable that a code symbol is printed on the order slip to make it easier to obtain the order information at the POS 5. The code symbol is, for example, a barcode or a two-dimensional code. It is preferable that the information obtained by decoding the code symbol is, for example, identification information (such as an order ID) that makes it possible to identify the order.

[0018] 2 is a block diagram showing an example of the hardware configuration of the order station 3 and the order server 1. In the following, the order station 3 will be described as an example, but the order server 1 is substantially the same.

[0019] First, the order station 3 includes a central processing unit (CPU) 31, a read only memory (ROM) 32, a random access memory (RAM) 33, a communication unit 34, a storage unit 39, and the like.

[0020] The CPU 31 is an example of a processor, and controls each part of the order station 3. The ROM 32 stores various programs. The RAM 33 is a workspace for expanding the programs and various data. The CPU 31, the ROM 32, and the RAM 33 are connected via a bus or the like, and constitute a control unit 30 having a computer configuration.

[0021] The order server 1 has substantially the same configuration as described above, but the CPU, ROM, and RAM of the order server 1 constitute a control unit 10.

[0022] The communication unit 34 is a communication interface that enables the control unit 30 to communicate with other devices (for example, the order server 1, the POS 5, the order terminal 6, and the kitchen appliances 7) via a network.

[0023] The storage unit 39 has a storage medium such as a hard disk drive (HDD), a solid state drive (SSD), or a flash memory, and maintains the stored contents even when the power is cut off. The storage unit 39 stores various setting information such as a program 391 executable by the CPU 31 and a product master 392. The storage unit 39 also stores order information 393.

[0024] The product master 392 is an example of product information, and is information about products handled by a store (product information) compiled, for example, in the form of a table. Items in the product master 392 are, for example, as follows. Product Code ·Product name ·Classification ·unit price

[0025] The product code is an example of information (identification information) capable of identifying a product, such as a JAN code. Other information (product name, category, unit price, etc.) is stored in association with the product code.

[0026] The "Product Name" field records the name of the product (food). The "Classification" field records the classification (department, category) of the product, with values ​​such as "meals" or "drinks." The "Unit Price" field records the price of one product.

[0027] The order information 393 is information on the products (food) ordered by the customer, which is compiled, for example, in the form of a table. Items of the order information 393 are, for example, as follows. Order ID Date and Time Store ID Device ID ·Staff ID ·Product information ·total

[0028] The order ID is an example of information (identification information) for identifying an order. The date and time is the date and time when the order in the record was placed. The store ID, terminal ID, and salesperson ID are identification information for the store, terminal (e.g., the order terminal 6 or the customer terminal 9), and salesperson who received the order in the record.

[0029] Here, for a combination of an order ID, date and time, and store ID, there is only one item in total, but multiple items of product information may be associated with it. The product information includes, for example, the following items: Product Code ·quantity ·price

[0030] The total is the sum (total amount) of the prices of all the products purchased in the order of the record. The product code is as described above. The quantity is the quantity (number, weight, volume, etc.) of the product indicated by the product code purchased in the order of the record. The price is the unit price multiplied by the quantity.

[0031] Here, the order information 393 includes information on orders within the store (internal orders) and information on orders from outside the store (external orders), but records relating to internal orders and records relating to external orders have different characteristics. For example, a store clerk ID is not entered in a record of an external order. Also, for example, while a terminal ID in a record of an internal order indicates the order terminal 6 used within the store, in a record of an external order, information capable of identifying a customer terminal 9 is entered as the terminal ID, and the terminal ID does not indicate the order terminal 6 used within the store. In this way, the order information 393 makes it possible to distinguish between internal orders and external orders based on the characteristics of the information (records) without having to provide a dedicated flag or the like.

[0032] It is not necessary for the program 391 , the product master 392 and the order information 393 to be stored in the same storage unit 39 .

[0033] The storage unit of the order station 3 may store, for example, the following setting information: Store Information Device information Staff information

[0034] The store information is information about the store itself, and includes, for example, a store ID and a store name associated with the store ID. The store name is the name of the store.

[0035] The terminal information is information about each device installed in a store, and includes, for example, a terminal ID and a terminal type associated with the terminal ID. The terminal type may be, for example, a personal computer (PC), a tablet type, a smartphone type, etc.

[0036] The salesperson information is information about salespersons working at the store, and includes, for example, a salesperson ID and the name of the salesperson associated with the salesperson ID.

[0037] 3 is a block diagram showing an example of a hardware configuration of the POS 5. The POS 5 includes a CPU 51, a ROM 52, a RAM 53, a communication unit 54, a display unit 55, an operation unit 56, a scanner 57, an audio output unit 58, a cash deposit / withdrawal unit 60, a memory unit 59, and the like.

[0038] The CPU 51 is an example of a processor and controls each part of the POS 5. The ROM 52 stores various programs. The RAM 53 is a workspace for developing programs and various data. The CPU 51, the ROM 52, and the RAM 53 are connected via a bus or the like to constitute a control unit 50 having a computer configuration.

[0039] The communication unit 54 is a communication interface that connects the control unit 50 and an external device (for example, the order station 3) so that they can communicate with each other via a network. The communication unit 54 also mediates the input and output of information between the control unit 50 and peripheral devices.

[0040] The display unit 55 has a display device such as an LCD (Liquid Crystal Display), and displays various information under the control of the CPU 51.

[0041] The operation unit 56 has input devices such as a touch panel provided over the surface of the display unit 55, a keyboard, and a pointing device, and outputs to the CPU 51 the contents of operations input via the input devices.

[0042] The operation unit 56 includes a reflection key 561. The reflection key 561 may be a hardware key provided on a keyboard, or may be a software key displayed on a display device. The reflection key 561 accepts an instruction to execute a batch reflection process, which will be described later. When the reflection key 561 is operated, the control unit 50 executes the batch reflection process.

[0043] The scanner 57 reads a code symbol (e.g., a barcode or a two-dimensional code) displayed on the exterior of a product and outputs the decoded value. In other words, if the code symbol is an encoded product code, the scanner 57 outputs the product code.

[0044] The audio output unit 58 has a speaker and a buzzer, and outputs audio under the control of the CPU 51.

[0045] The deposit / withdrawal unit 60 is, for example, a change machine (or a drawer) that stores cash (coins and bills) and receives deposits and dispenses change during settlement.

[0046] The storage unit 59 has a storage medium such as an HDD, an SSD, or a flash memory, and maintains the stored contents even when the power is cut off. The storage unit 59 stores a program 591 that the CPU 51 can execute, and sales information 593.

[0047] The program 591 is application software for causing the POS 5 to function.

[0048] The sales information 593 is information on products for which a customer has completed a transaction, compiled, for example, in the form of a table. The items in the sales information 593 are substantially the same as those in the order information 393. The POS 5 registers (generates and records) new sales information 593 each time a transaction is completed, and also transmits a request to the order station 3 to delete the corresponding order information 393.

[0049] The storage unit 59 may store setting information such as terminal information (terminal ID and terminal mode) of the device itself.

[0050] Fig. 4 is a block diagram showing an example of a functional configuration of each of the control units 10, 30, 50. The control units 10, 30, 50 each provide various functional units shown in Fig. 4 by executing a program.

[0051] The control unit 10 of the order server 1 functions as an information acquisition unit 101 and a notification unit 105. The control unit 30 of the order station 3 functions as an information acquisition unit 301 and an order notification unit 302. The control unit 50 of the POS 5 functions as an information acquisition unit 501, an in-store accounting unit 502, a lump-sum reflection unit 503, and a daily settlement unit 504.

[0052] The information acquisition unit 101 acquires order information from the application server 8. When the notification unit 105 receives an order notification from the order station 3, it notifies the application server 8 of the receipt of the order.

[0053] The information acquiring unit 301 acquires order information from the order server 1, and stores it in its own memory unit 39 as order information 393. All orders that are treated as order information 393 in this process have already been paid for (settlement) by the customer. The information acquiring unit 301 repeatedly executes the above process at predetermined time intervals.

[0054] The information acquiring unit 301 also stores the order information transmitted from the in-store order terminal 6 in its own storage unit 39 as order information 393. In this process, the accounting (payment by the customer) for the order that is treated as the order information 393 is pending.

[0055] The order notification unit 302 transmits the newly added order information 393 to the kitchen appliance 7, and transmits a notification to the effect that the order has been received (order notification) to the order server 1 and the order terminal 6.

[0056] The information acquiring unit 501 is an example of an acquiring unit that acquires order information that is information on orders received by a store but is not registered as sales information from the management device (order station 3). The information acquiring unit 501 of this embodiment acquires order information 393 that is information on orders received from outside the store (external orders) but is not registered as sales information 593 from the order station 3. Note that since the information acquiring unit 501 of this embodiment is executed during non-business hours, it is not necessary to distinguish whether the record is an external order or not. However, if there is a possibility that the batch reflection process will be executed while the store is open, it is preferable to distinguish whether the order is placed inside or outside the store based on the characteristics of the record of the order information 393 and acquire only the order information 393 from outside the store.

[0057] The in-store accounting unit 502 processes transactions within the store, generates sales information 593 based on the order information 393 to be processed, and stores (registers) the sales information 593 in the storage unit 59.

[0058] In-store accounting section 502 receives payment from customers who have finished eating for orders placed within the store (internal orders) in the accounting process. In addition, in-store accounting section 502 does not receive payment from people who receive the ordered items at the store (hand them over by a store clerk) for external orders.

[0059] The batch reflection unit 503 is an example of a registration unit that generates and registers sales information based on order information acquired by the acquisition unit (information acquisition unit 501). The batch reflection unit 503 performs a batch reflection process. The batch reflection process is a process of registering, as sales, order information 393 that has not been registered as sales information 593. The batch reflection process can be executed at any time in response to an operation by a store clerk, but is preferably executed during non-business hours, for example, between daytime and evening business hours.

[0060] The daily settlement unit 504 is an example of a registration unit that generates and registers sales information based on order information acquired by the acquisition unit (information acquisition unit 501). The daily settlement unit 504 performs daily settlement processing. Daily settlement processing is processing that is executed, for example, during the cash register closing operation after closing the store at the end of the day's business. In the daily settlement processing, the control unit 50 finalizes the day's sales and issues a settlement receipt detailing the day's deposits and withdrawals. The daily settlement unit 504 of this embodiment performs a lump-sum reflection process when the above-mentioned daily settlement begins.

[0061] FIG. 5 is a sequence diagram illustrating the cooperation between the devices.

[0062] First, an order in a store will be described. In the store, a store clerk takes an order from a customer by operating the order terminal 6. The order terminal 6 receives order information input by the store clerk (step S11), and transmits the received order information to the order station 3 (step S12).

[0063] The control unit 30 of the order station 3, functioning as the information acquisition unit 301, stores the order information received from the order terminal 6 in the storage unit 39 as order information 393 (step S13). Next, the control unit 30, functioning as the order notification unit 302, sends an order notification to the order terminal 6 (step S14), and further sends the order information 393 to the kitchen appliance 7 (step S15).

[0064] The kitchen appliance 7 outputs the received order information 393 (step S16). In this step, the display of the kitchen appliance 7 displays the order information, and the printer prints out an order slip.

[0065] Next, an order from outside the store will be described. The customer launches an application program installed on the customer terminal 9 and performs operations related to ordering and settlement (payment). As a result, the application program of the customer terminal 9 performs order processing and transmits information related to the order (order information) to the application server 8, and further performs payment processing and transmits information related to the payment (payment information) to the application server 8 (step S21). Since the payment processing here is an online payment, it is completed by a method that does not involve the exchange of cash. An example of a payment method that does not involve the exchange of cash is electronic payment such as credit card payment.

[0066] When the application server 8 receives the order information and payment information from the customer terminal 9, it stores them in its own storage unit (step S22).

[0067] The control unit 10 of the order server 1, as the information acquisition unit 101, repeatedly acquires the settled order information stored in the application server 8 at predetermined time intervals (step S23). In addition, the control unit 10 of the order server 1 stores the order information acquired from the application server 8 in its own memory unit (step S24).

[0068] The control unit 30 of the order station 3, functioning as the information acquisition unit 301, repeatedly acquires the order information stored by the order server 1 at predetermined time intervals (step S25). The control unit 30 also stores the order information acquired from the order server 1 in its own memory unit 39 as order information 393 (step S26). All orders in the order information 393 have already been paid for (settlement) by the customer.

[0069] Next, the control unit 30 of the order station 3, functioning as the order notification unit 302, sends the order information 393 newly added in step S26 to the kitchen appliance 7 (step S27), and further sends an order notification to the order server 1 (step S28).

[0070] When the control unit 10 (notification unit 105) of the order server 1 receives the order notification from the order station 3, it notifies the application server 8 of the receipt of the order (step S29).

[0071] When the application server 8 receives the notification from the order server 1, it notifies the customer terminal 9 of the same (step S30). This completes the order process in the application program of the customer terminal 9.

[0072] The kitchen appliance 7 outputs the received order information 393 (step S31), similar to step S16. In this step, the display of the kitchen appliance 7 displays the order information, and the printer prints out an order slip. This allows the kitchen staff to refer to the order information 393.

[0073] The control unit 50 of the POS 5 performs in-store accounting processing (see FIG. 6, described below) according to the operation of the operator (clerk) (step S40). The control unit 50 also performs a batch reflection process (see FIG. 7, described below) according to the operation of the operator (clerk) (step S50). The control unit 50 also performs a daily settlement process (see FIG. 8, described below) according to the operation of the operator (clerk) (step S80).

[0074] 6 is a diagram showing an example of the flow of in-store transaction processing executed by the control unit 50 of the POS 5. First, the control unit 50, functioning as the information acquisition unit 501, acquires new order information 393 (step S41).

[0075] In step S41, the waiter, for example, has the scanner 57 read the code symbol printed on the order slip. The order slip is either handed over by a customer who has finished their meal, or attached to the food packaging given to them by kitchen staff. When the POS 5 obtains the order ID from the output of the scanner 57, it sends a request to the order station 3 together with the order ID. In response to the request, the order station 3 sends the order information 393 corresponding to the order ID to the POS 5.

[0076] Thereafter, control unit 50 performs the processes of steps S42 to S48 as in-store accounting unit 502. First, control unit 50 prompts the store clerk via display unit 55 and operation unit 56 to select either an operation to instruct the store clerk to carry out the transaction, or an operation to instruct the store clerk to proceed with the transaction as if payment had been completed (step S42).

[0077] When a transaction execution instruction is received in step S42 (Yes in step S42), the control unit 50 performs transaction processing (step S43). In transaction processing, the control unit 50 receives payment for the order from the customer. The control unit 50 then issues a receipt and a journal (step S44), and if there is change (Yes in step S45), it pays it out through the deposit / withdrawal unit 60 (step S46).

[0078] Here, a receipt is a piece of paper that is handed over to a customer who has paid for food and drink consumed in a store, or to a person who has received a product (such as a delivery person). Also, a journal is recorded in the POS 5. If the journal is a paper journal, it is printed by a built-in printer, and if it is an electronic journal, it is stored in, for example, the memory unit 59.

[0079] Next, the control unit 50 registers (updates) new sales information 593 based on the information of the order processed in step S43 (step S47). Furthermore, the control unit 50 transmits a request to delete the order information 393 that has the same order ID as the sales information 593 registered in step S47 to the order station 3 (step S48).

[0080] In step S42, if an instruction to proceed with the process assuming the payment has been made is received (No in step S42), the control unit 50 skips the accounting process in step S43 and proceeds to step S44. In addition, in step S45, if there is no change (No in step S45), the control unit 50 skips the change payment in step S46 and proceeds to step S47.

[0081] Through the above-mentioned in-store accounting process, the control unit 50 receives payment on the spot for customers who eat and drink in the store and registers sales information 593, and also registers sales information 593 for orders from outside the store (where payment has been made outside the store) without carrying out accounting.

[0082] Next, the batch reflection process will be described. First, when the reflection key 561 of the operation unit 56 is operated, the control unit 50 executes the batch reflection process in response.

[0083] 7 is a diagram showing an example of the flow of the batch reflection process executed by the control unit 50 of the POS 5. When an instruction to start batch reflection is received (step S51), the control unit 50, functioning as the information acquisition unit 501, acquires unpaid order information 393 (step S52).

[0084] Unpaid order information 393 is order information 393 for which an order ID does not exist in sales information 593. As explained in steps S47 to S48 above, when sales information 593 is registered, a request is made to delete the corresponding order information 393. Therefore, unless an error occurs in the cooperation between the order station 3 and the order server 1, the order ID of order information 393 does not exist in sales information 593.

[0085] Thereafter, the control unit 50 performs the processes from step S53 as the batch reflection unit 503. First, the control unit 50 displays a list of the order information 393 acquired in step S52 on the display unit 55 (step S53). As a result, the display unit 55 displays each record of the acquired order information 393 in the form of a list with one record per row, for example.

[0086] Next, the control unit 50 accepts a selection operation from the list by the store clerk via the operation unit 56 (step S54). The store clerk uses the operation unit 56 to select rows (records) that are to be subject to the batch reflection process.

[0087] Next, the control unit 50 receives an operation from the operation unit 56 to instruct execution of a batch reflection process for the selected order information 393 (step S55). Upon receiving the execution instruction, the control unit 50 enters a loop process for the batch reflection process, which will be described next.

[0088] The control unit 50 determines whether there are any more records to be processed (order information 393) (step S56), and if there are (Yes in step S56), reads out one target record (step S57). The control unit 50 then executes accounting for the read out order information 393 (step S58). However, because this order information 393 is an order from outside the store and has already been paid for, no payment is made by the customer (or the person who received the product at the store) in the accounting process of step S58.

[0089] Next, the control unit 50 skips issuing a receipt, issues a journal (step S59), and updates the sales information 593 based on the targeted order information 393 (step S60).

[0090] Next, the control unit 50 judges whether the update of the sales information 593 has been successful (step S61). If the update has been successful (Yes in step S61), the control unit 50 transmits a request to delete the corresponding order information 393 to the order station 3 (step S62).

[0091] Next, the control unit 50 judges whether the deletion of the order information 393 was successful based on a response from the order station 3 (step S63). If it was successful (Yes in step S63), one transaction is completed (step S64), and the process returns to step S56.

[0092] If the deletion has failed in step S63 (No in step S63), the control unit 50 stores the order information 393 that has failed to be deleted in its own storage unit 59 (step S65), and the process proceeds to step S64.

[0093] If the update has failed in step S61 (No in step S61), the control unit 50 stores the unsuccessfully updated sales information 593 in its own storage unit 59 (step S66), and the process proceeds to step S64.

[0094] In step S56, if there are no more records (order information 393) to be processed (No in step S56), the control unit 50 determines whether there is any unsuccessfully updated sales information 593 (step S71). If unsuccessfully updated sales information 593 is stored in the memory unit 59 (No in step S71), the control unit 50 edits the unsuccessfully updated sales information 593 and inserts it into the data for printing out a failed receipt (step S72). If there is no unsuccessfully updated sales information 593 (Yes in step S71), the control unit 50 skips step S72 and proceeds to step S73.

[0095] Next, the control unit 50 determines whether there is any order information 393 that has failed to be deleted (step S73). If there is any order information 393 that has failed to be deleted stored in the memory unit 59 (No in step S73), the control unit 50 edits the order information 393 that has failed to be deleted and inserts it into the data for printing out a failed receipt (step S74). If there is no order information 393 that has failed to be deleted (Yes in step S73), the control unit 50 skips step S74 and proceeds to step S75.

[0096] Next, the control unit 50 uses the data for printing out a failed receipt to print out a failed receipt (step S75), and ends this process. There are cases where the data for printing out a failed receipt does not include the sales information 593 for which the update was unsuccessful or the order information 393 for which the deletion was unsuccessful, in which case it is possible to tell from the failed receipt that there was no failure in this process.

[0097] Next, the daily settlement process will be described with reference to Fig. 8. Fig. 8 is a diagram showing an example of the flow of the daily settlement process executed by the control unit 50 of the POS 5. When the control unit 50 receives an instruction to start daily settlement (step S81), it acquires unaccounted order information 393 as the information acquisition unit 501 (step S82). As described above, unaccounted order information 393 is order information 393 in which an order ID does not exist in sales information 593.

[0098] Thereafter, the control unit 50 performs the process from step S83 as the daily settlement unit 504. First, the control unit 50 judges whether there is any order information 393 acquired in step S82 (step S83). If there is any order information 393 (Yes in step S83), the control unit 50 displays on the display unit 55 that there is order information 393 that has been paid but not yet accounted for (step S84), and accepts an operation to select whether or not to reflect all at once through the operation unit 56 (step S85). If an operation to reflect all at once is accepted through the operation unit 56 (Yes in step S85), the control unit 50 performs a process to reflect all at once (step S86). This process to reflect all at once is the same as the process in steps S56 to S66 in FIG. 7, and therefore a description thereof will be omitted.

[0099] Next, the control unit 50 judges whether or not there has been a failure in the batch reflection process (step S87). Here, if the memory unit 59 stores order information 393 that has failed to be deleted or sales information 593 that has failed to be updated, the control unit 50 judges that there has been a failure (Yes in step S87).

[0100] If it is determined in step S87 that there has been a failure (Yes in step S87), the control unit 50 accepts an operation from the operation unit 56 to select whether or not to forcibly execute (step S88). If an operation to not forcibly execute is accepted from the operation unit 56 in step S88 (No in step S88), the control unit 50 cancels the daily settlement (step S89) and ends this process.

[0101] In step S88, if an operation to forcibly execute is received from the operation unit 56 (Yes in step S88), the control unit 50 advances the process to step S90. If it is determined in step S87 that there is no failure (No in step S87), the control unit 50 advances the process to step S90. If an operation to not reflect all at once is received in step S85 (No in step S85), the control unit 50 advances the process to step S90.

[0102] In step S90, the control unit 50 accepts an operation by the operator (store clerk) via the operation unit 56 to permit or prohibit the execution of daily settlement when there are settled but unaccounted records (step S90). If permitted (step S90: permitted), in step S91, the control unit 50 performs daily settlement if there are no settled but unaccounted records, and even if there are, (step S91), and ends this process. If prohibited (step S90: prohibited), the control unit 50 stops daily settlement if there are settled but unaccounted records (step S92), and ends this process.

[0103] As described above, according to this embodiment, when handing over an item ordered from outside the store to a third party, it is possible to register sales information 593 based on order information 393 related to outside orders by performing a batch reflection process during non-business hours or a daily settlement process after closing time without having to perform in-store accounting each time. Therefore, it is possible to reduce the effort required to register sales from external orders in an existing system.

[0104] Furthermore, even if the batch reflection process fails, according to this embodiment, the information about the failure is stored, so that measures can be taken, such as re-executing the process.

[0105] The above-described embodiment can be modified as appropriate by changing part of the configuration or function of each of the above-described devices.

[0106] For example, in the above embodiment, the batch reflection process is executed by manual operation, but the implementation is not limited to this. For example, the batch reflection process may be configured to be executed automatically at a fixed time or when the processing load is low.

[0107] Furthermore, in the case of the above-mentioned automatic execution configuration, if there is a possibility that the batch reflection process will be executed while the store is open, it is preferable for the information acquisition unit 501 to distinguish whether the order is placed inside or outside the store based on the characteristics of the record of the order information 393, and to acquire only the order information 393 from outside the store.

[0108] Furthermore, in the above embodiment, the order server 1 and the application server 8 are described as cloud servers, but this is not a limitation in practice, and the order server 1 and the application server 8 may be installed within a store. Furthermore, the order server 1 and the application server 8 do not have to be separate devices, that is, the functions of the order server 1 and the application server 8 may be performed by a single device.

[0109] In the above embodiment, an example has been described in which an order from outside the store has already been paid for by the customer, but the present invention is not limited to this. In the above embodiment, an item is not prepared for an order from outside the store that has not yet been paid for, but it is also possible to configure the order station 3 to retrieve unpaid order information. In this case, for example, a customer who comes to the store to pick up an order from outside the store may use a device installed in the store to make a payment before receiving the item, and in this case, the collective reflection process and daily settlement process of the above embodiment may be utilized in the sales registration of the POS 5. Furthermore, the collective reflection process and daily settlement process of the above embodiment may be utilized in the sales registration of the POS 5 in the case where a customer uses a device in the store to perform an order operation and settlement by himself.

[0110] The programs executed by each device of the above-described embodiments are provided by being pre-installed in a ROM, etc. The programs executed by each device of the above-described embodiments may be provided by being recorded in an installable or executable format on a computer-readable recording medium such as a CD-ROM, a flexible disk (FD), a CD-R, or a digital versatile disk (DVD).

[0111] Furthermore, the programs executed by each device of the above-described embodiments may be stored on a computer connected to a network such as the Internet and provided by being downloaded via the network. Also, the programs executed by each device of the above-described embodiments may be provided or distributed via a network such as the Internet.

[0112] Although some embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, substitutions, modifications, and combinations can be made without departing from the spirit of the invention. These embodiments and their modifications are included in the scope and spirit of the invention, and are included in the scope of the invention and its equivalents described in the claims. [Explanation of symbols]

[0113] 1 ... order server, 10... control unit, 101... information acquisition unit, 105... notification unit, 21...external network, 22...internal network, 23...store router, 3 ... Order station (an example of a management device), 30...control unit, 301...information acquisition unit, 302...order notification unit, 31...CPU, 32...ROM, 33...RAM, 34...Communication section, 39... memory unit, 391... program, 392... product master, 393... order information, 5 ... POS (an example of a sales data processing device), 50...control unit, 501: information acquisition unit (an example of an acquisition unit), 502: in-store accounting unit, 503... a batch reflection unit (an example of a registration unit), 504... a daily settlement unit (an example of a registration unit), 51...CPU, 52...ROM, 53...RAM, 54...Communication section, 55: display unit, 56: operation unit, 561: reflection key, 57: scanner; 58: voice output unit; 60: cash deposit / withdrawal unit; 59... memory unit, 591... program, 593... sales information, 6 … Order terminal, 7...Kitchen equipment, 8 … application server, 9...Customer terminal. [Prior art documents] [Patent documents]

[0114] [Patent Document 1] JP 2023-048187 A

Claims

1. A sales data processing device is used together with a management device that manages order information, which is information on orders received by a store, performs accounting based on the order information, and registers the order information after the accounting as sales information, an acquisition unit that acquires, from the management device, order information that has been accepted by a store and that has not yet been registered as the sales information; a registration unit that generates and registers the sales information based on the order information acquired by the acquisition unit; A sales data processing device comprising:

2. The registration unit stores the sales information related to the failed registration in a predetermined storage unit when the registration of the sales information fails. The sales data processing device according to claim 1 .

3. When the registration of the sales information fails, the registration unit outputs a failure receipt summarizing the sales information related to the failed registration. The sales data processing device according to claim 1 .

4. The registration unit transmits a request to delete the order information to the management device in response to the registration of the sales information. The sales data processing device according to any one of claims 1 to 3.

5. When the deletion of the order information fails, the registration unit outputs a failure receipt summarizing the order information related to the failure in deletion. A sales data processing device according to claim 4.

6. A computer is provided in a sales data processing device that is used together with a management device that manages order information, which is information on orders received by a store, performs accounting based on the order information, and registers the order information after the accounting as sales information. an acquisition unit that acquires, from the management device, order information that has been accepted by a store and that has not yet been registered as the sales information; a registration unit that generates and registers the sales information based on the order information acquired by the acquisition unit; A program that functions as a

Images