Sales data processing device 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] Embodiments of the present invention relate to a sales data processing apparatus and a program.

Background Art

[0002] Conventionally, in stores such as restaurants, a system in which an order terminal, kitchen equipment, and a POS are centrally managed at an order station has become widespread. Among these, in recent years, a business model has been established in which stores such as restaurants receive takeout orders via the Internet from outside the store during store business hours. Also, various systems have been proposed for this purpose (for example, Patent Document 1).

[0003] In the recent business models as described above, when managing store sales with an existing system, it is necessary to register sales from orders via the Internet. This work is complicated because it has nothing to do with the work of handing over the products for takeout orders, and there is also a risk of forgetting the work. There is no existing system that solves such problems.

[0004] In addition, even for items that do not require payment at the time of product delivery other than orders received from outside the store, there is a risk that the sales registration work will feel complicated or that the postponed sales registration work will be forgotten.

Summary of the Invention

Problems to be Solved by the Invention

[0005] The problem to be solved by the present invention is to provide a sales data processing apparatus and a program that can reduce the procedures for registering sales from orders via an external route in an existing system.

Means for Solving the Problems

[0006] The sales data processing device of this embodiment is used together with a management device that manages order information, which is information about orders received by a store, and performs accounting based on the order information, and the accounted-up order information is used as sales information. In the designated storage unit It is something to register, The system includes a control unit that performs a batch update process upon receiving a predetermined operation, and the control unit that performs the batch update process, From the aforementioned control device ,before Order information Of these, those that were received outside the store, paid for by the customer, and not registered as sales information in the storage unit. of 、 An acquisition unit that acquires information, and a unit that generates sales information based on the order information acquired by the acquisition unit. The memory unit It includes a registration section for registration. [Brief explanation of the drawing]

[0007] [Figure 1] Figure 1 shows an example of the system configuration of the embodiment. [Figure 2] Figure 2 is a block diagram showing an example of the hardware configuration of the order station 3 and the order server 1. [Figure 3] Figure 3 is a block diagram showing an example of the POS5 hardware configuration. [Figure 4] Figure 4 is a block diagram showing an example of the functional configuration of each control unit 10, 30, and 50. [Figure 5] Figure 5 is a sequence diagram illustrating the coordination of each device. [Figure 6] Figure 6 shows an example of the in-store accounting process performed by the control unit 50 of POS5. [Figure 7] Figure 7 shows an example of the flow of the batch update process executed by the control unit 50 of POS5. [Figure 8] Figure 8 shows an example of the daily settlement process performed by the control unit 50 of POS5. [Modes for carrying out the invention]

[0008] (First Embodiment) The embodiments will be described with reference to the drawings. Figure 1 is a diagram showing an example of the system configuration of the embodiment. This system includes an order server 1, an order station 3, a POS 5, an order terminal 6, kitchen equipment 7, an application server 8, etc.

[0009] Order Server 1 and Application Server 8 are cloud servers. Order Server 1 manages order information from outside the store. Application Server 8 receives product orders from application programs running on customer terminals 9 and provides the order information to Order Server 1.

[0010] The order station 3, POS 5, order terminal 6, kitchen equipment 7, and other devices are installed within the store.

[0011] Communication between order server 1 and order station 3 takes place via external network 21, internal network 22, and store router 23. The store router 23 connects the external network 21 and the internal network 22. The external network 21 is implemented as, for example, the internet. The internal network 22 is implemented as, for example, a LAN (Local Area Network). The internal network 22 connects each device within the store so that they can send and receive information (communicate) with each other.

[0012] Order Station 3 is an example of a management device that manages order information, which is information about orders received by a store. Order Station 3 also centrally manages information handled by other devices within the store (POS 5, order terminal 6, kitchen equipment 7, etc.). Furthermore, Order Station 3 communicates with Order Server 1 to share information they manage (such as order information and product master data).

[0013] POS5 is an example of a sales data processing device that performs accounting based on order information and registers the accounted-for order information as sales information. POS5 generates and stores sales information for products offered by the store based on the order information managed by Order Station 3.

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

[0015] The order terminal 6 is a device for inputting information on products related to an order. The order terminal 6 is used when a store clerk accepts an order from a customer in the store.

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

[0017] It is preferable that a code symbol for facilitating acquisition of order information by the POS5 is printed on the order slip. The code symbol is, for example, a barcode or a two-dimensional code. The information obtained by decoding the code symbol is preferably, for example, identification information (such as an order ID) that enables the order to be identified.

[0018] FIG. 2 is a block diagram showing an example of the hardware configuration of the order station 3 and the order server 1. Hereinafter, 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 CPU (Central Processing Unit) 31, a ROM (Read Only Memory) 32, a RAM (Random Access Memory) 33, a communication unit 34, a storage unit 39, and the like.

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

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

[0022] The communication unit 34 is a communication interface through which the control unit 30 is communicably connected to other devices (for example, the order server 1, the POS 5, the order terminal 6, and the kitchen equipment 7) via a network.

[0023] The storage unit 39 has a storage medium such as an HDD (Hard Disk Drive), an SSD (Solid State Drive), or a flash memory, and maintains the stored content even when the power is turned off. The storage unit 39 stores programs 391 executable by the CPU 31 and various setting information such as 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 information on products handled by the store (product information) is summarized in a table format, for example. The items of the product master 392 are as follows, for example. · Product code · Product name · Classification · Unit price

[0025] The product code is an example of information (identification information) that can identify a product, and is, for example, a JAN code. Other information (product name, classification, unit price, etc.) is stored in association with the product code.

[0026] The "Product Name" field records the name of the product (dish). The "Classification" field records the product's classification (department, category), with values ​​such as "Meal" or "Drink." The "Unit Price" field records the price per item.

[0027] Order information 393 is a document that summarizes the information about the items (dishes) ordered by the customer, for example, in a table format. The items in order information 393 are, for example, as follows: Order ID · Date and time Store ID • Device ID • Employee ID ·Product information ·total

[0028] The Order ID is an example of information used to identify an order (identification information). The Date and Time is the date and time the order for that record was placed. The Store ID, Terminal ID, and Employee ID are identification information for the store, terminal (e.g., Order Terminal 6 or Customer Terminal 9), and employee who received the order for that record.

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

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

[0031] Here, order information 393 includes information on orders placed within the store (internal orders) and information on orders placed outside the store (external orders), but the records for internal orders and external orders have different characteristics. For example, the employee ID is not entered in the records for external orders. Also, for example, in the records for internal orders, the terminal ID will indicate the order terminal 6 used within the store, whereas in the records for external orders, the terminal ID will contain information that can identify the customer terminal 9, and will not indicate the order terminal 6 used within the store. In this way, order information 393 can be distinguished between internal orders and external orders based on the characteristics of the information (records), without the need to set up separate dedicated flags or the like.

[0032] Note that the program 391, product master 392, and order information 393 do not need to be stored in the same storage unit 39.

[0033] Furthermore, the memory unit of Order Station 3 may store the following setting information, for example. • Store information • Device information • Staff information

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

[0035] Terminal information refers to information about each device installed in the store, and includes, for example, a terminal ID and the terminal type associated with that terminal ID. The terminal type can be, for example, a PC (Personal Computer), a tablet, or a smartphone.

[0036] Employee information refers to information about employees working at the store, and includes, for example, an employee ID and the name of the employee associated with that employee ID.

[0037] Figure 3 is a block diagram showing an example of the hardware configuration of POS5. POS5 includes a CPU 51, ROM 52, RAM 53, communication unit 54, display unit 55, operation unit 56, scanner 57, audio output unit 58, deposit / withdrawal unit 60, storage unit 59, etc.

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

[0039] The communication unit 54 is a communication interface that connects the control unit 50 and an external device (e.g., the order station 3) to enable communication via a network. The communication unit 54 also mediates the input and output of information with 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 a touch panel superimposed on the surface of the display unit 55, as well as input devices such as a keyboard and a pointing device, and outputs the operation content input via the input devices to the CPU 51.

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

[0043] Scanner 57 reads the code symbol (e.g., barcode or QR code) displayed on the product's exterior and outputs the decoded value. In other words, if the code symbol is a coded representation of the product code, scanner 57 outputs the product code.

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

[0045] The deposit / withdrawal unit 60 is, for example, a change dispenser (or drawer) that holds cash (coins and banknotes) and accepts deposits and dispenses change during settlement.

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

[0047] Program 591 is application software for making POS5 functional.

[0048] Sales information 593 is a summary of the items a customer has paid for, for example, in a table format. The items in sales information 593 are almost the same as those in order information 393. Each time a transaction occurs, POS 5 registers (generates and records) new sales information 593 and sends a request to order station 3 to delete the corresponding order information 393.

[0049] The memory unit 59 may also store, for example, setting information such as the device's terminal information (terminal ID and terminal type).

[0050] Figure 4 is a block diagram showing an example of the functional configuration of each control unit 10, 30, and 50. Each control unit 10, 30, and 50 provides the various functional units shown in Figure 4 through the execution of 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 batch 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 this fact.

[0053] The information acquisition unit 301 acquires order information from the order server 1 and stores it in its own storage unit 39 as order information 393. All orders designated as order information 393 in this process have been paid for (settled) by the customer. The information acquisition unit 301 repeats the above process at predetermined time intervals.

[0054] Furthermore, the information acquisition unit 301 stores the order information transmitted from the order terminal 6 in the store as order information 393 in its own storage unit 39. In this process, the payment (payment by the customer) for the order designated as order information 393 is not yet completed.

[0055] The order notification unit 302 transmits the newly added order information 393 to the kitchen equipment 7 and sends an order notification to the order server 1 and order terminal 6 indicating that the order has been received.

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

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

[0058] In the accounting process, the in-store accounting department 502 receives payment from customers who have finished their meals for orders placed within the store (internal orders). However, for external orders, the in-store accounting department 502 does not receive payment from the person who receives the ordered goods at the store (handed them over by a store employee).

[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 batch reflection processing. Batch reflection processing is the process of registering unregistered order information 393 as sales information 593. Batch reflection processing can be performed at any time in response to the actions of the store staff, but it is preferable to perform it during non-business hours, for example, between lunch service and dinner service.

[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 a process that is performed, for example, during the cash register closing process after the store has finished business for the day. In daily settlement processing, the control unit 50 performs tasks such as confirming the day's sales and issuing settlement receipts that show the details of the day's deposits and withdrawals. In this embodiment, the daily settlement unit 504 performs batch reflection processing when the above-mentioned daily settlement begins.

[0061] Figure 5 is a sequence diagram illustrating the coordination of each device.

[0062] First, let's explain the ordering process within the store. Within the store, the staff member takes orders from customers by operating the order terminal 6. The order terminal 6 receives the order information input by the staff member (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, acting as an information acquisition unit 301, stores the order information received from the order terminal 6 as order information 393 in the storage unit 39 (step S13). Subsequently, the control unit 30, acting as an 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 equipment 7 (step S15).

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

[0065] Next, we will explain orders placed from outside the store. The customer launches the application program installed on the customer terminal 9 and performs the operations related to ordering and payment. As a result, the application program on the customer terminal 9 processes the order and sends order information to the application server 8, and then processes the payment and sends payment information to the application server 8 (step S21). Since the payment process here is an online payment, it is completed using a method that does not involve the exchange of cash. Examples of payment methods that do not involve the exchange of cash include electronic payments such as credit card payments.

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

[0067] The control unit 10 of the order server 1, acting as an information acquisition unit 101, repeatedly acquires the settled order information stored by the application server 8 at predetermined intervals (step S23). The control unit 10 of the order server 1 also 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, acting as an information acquisition unit 301, repeatedly acquires order information stored by the order server 1 at predetermined intervals (step S25). The control unit 30 also stores the order information acquired from the order server 1 in its own storage unit 39 as order information 393 (step S26). Here, all orders designated as order information 393 are those for which payment (settlement) has been completed by the customer.

[0069] Next, the control unit 30 of the order station 3, acting as an order notification unit 302, transmits the newly added order information 393 from step S26 to the kitchen equipment 7 (step S27), and then transmits 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 an order notification from the order station 3, it notifies the application server 8 of this fact (step S29).

[0071] When the application server 8 receives a notification from the order server 1, it notifies the customer terminal 9 of this fact (step S30). As a result, the order processing is completed in the application program on the customer terminal 9.

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

[0073] The control unit 50 of POS5 performs in-store accounting processing (see Figure 6, described later) based on the operator's (store clerk's) input (step S40). The control unit 50 also performs batch update processing (see Figure 7, described later) based on the operator's (store clerk's) input (step S50). The control unit 50 also performs daily settlement processing (see Figure 8, described later) based on the operator's (store clerk's) input (step S80).

[0074] Figure 6 shows an example of the in-store payment processing flow performed by the control unit 50 of POS 5. First, the control unit 50, acting as an information acquisition unit 501, acquires new order information 393 (step S41).

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

[0076] From this point onward, the control unit 50, acting as the in-store accounting unit 502, performs the processing in steps S42 to S48. First, the control unit 50, via the display unit 55 and the operation unit 56, requests the store clerk to choose between performing an operation to execute the accounting or proceeding with processing as if the transaction has already been settled (step S42).

[0077] When the control unit 50 receives an accounting execution instruction in step S42 (Yes in step S42), it performs accounting processing (step S43). In accounting processing, the control unit 50 receives payment from the customer for the order. Subsequently, the control unit 50 issues a receipt and a journal (step S44), and if there is change (Yes in step S45), it is dispensed by the cash inflow / outflow unit 60 (step S46).

[0078] Here, a receipt is a piece of paper handed to a customer who has paid for food and drinks consumed in the store, or to a person who has received goods (for example, a delivery person). The journal, on the other hand, is recorded in POS5. If it is a paper journal, it is printed by the built-in printer, and if it is an electronic journal, it is stored, for example, in the storage unit 59.

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

[0080] In step S42, if the control unit 50 receives an instruction to proceed with processing as settled (No. of step S42), it skips the accounting processing in step S43 and proceeds to step S44. Also, in step S45, if there is no change available (No. of step S45), the control unit 50 skips the change dispensing in step S46 and proceeds to step S47.

[0081] As described above, the in-store accounting process allows the control unit 50 to receive payment on the spot from customers who dine in the store and register sales information 593, while for orders placed outside the store (payment already made outside the store), it registers sales information 593 without performing accounting processing.

[0082] Next, the batch update process will be explained. First, when the update key 561 of the operation unit 56 is operated, the control unit 50 executes the batch update process accordingly.

[0083] Figure 7 shows an example of the flow of the batch update process executed by the control unit 50 of POS5. Upon receiving the instruction to start the batch update (step S51), the control unit 50, as the information acquisition unit 501, acquires unpaid order information 393 (step S52).

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

[0085] From this point onward, the control unit 50, acting as a batch reflection unit 503, performs the processing from step S53. First, the control unit 50 displays the order information 393 acquired in step S52 in a list 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, for example, with one record per row.

[0086] Next, the control unit 50 accepts a selection operation from the store clerk via the operation unit 56 (step S54). The store clerk uses the operation unit 56 to select the rows (records) to be processed in a batch update.

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

[0088] The control unit 50 determines whether there are still records to be processed (order information 393) (step S56), and if there are (Yes in step S56), it reads one record (step S57). The control unit 50 then performs accounting processing on the read order information 393 (step S58). However, since this order information 393 is an order from outside the store and has already been settled, no payment is made by the customer (or the person who received the goods at the store) in the accounting processing in step S58.

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

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

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

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

[0093] Furthermore, if step S61 is unsuccessful (No. of step S61), the control unit 50 stores the sales information 593 that failed to be updated in its storage unit 59 (step S66) and 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 are any sales information 593 that failed to update (step S71). If the storage unit 59 holds sales information 593 that failed to update (No. in step S71), the control unit 50 edits the sales information 593 that failed to update and incorporates it into the data for printing failed receipts (step S72). If there are no sales information 593 that failed to update (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 failed to be deleted (step S73). If the storage unit 59 holds order information 393 that failed to be deleted (No in step S73), the control unit 50 edits the order information 393 that failed to be deleted and incorporates it into the data for printing the failed receipt (step S74). If there is no order information 393 that 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 prints a failed receipt using the data for printing failed receipts (step S75), and terminates the process. In some cases, the data for printing failed receipts may not include sales information 593 for failed updates or order information 393 for failed deletions. In such cases, the failed receipt indicates that there were no failures in this process.

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

[0098] From this point onward, the control unit 50, acting as the daily settlement unit 504, performs the processing from step S83. First, the control unit 50 determines whether there is order information 393 acquired in step S82 (step S83). If there is (Yes in step S83), the control unit 50 displays on the display unit 55 that there is order information 393 that has been settled but not yet accounted for (step S84), and accepts an operation from the operation unit 56 to select whether or not to reflect the data in bulk (step S85). If the operation unit 56 accepts an operation to reflect the data in bulk (Yes in step S85), the control unit 50 performs the bulk reflection process (step S86). This bulk reflection process is the same as the processing in steps S56 to S66 in Figure 7, so the explanation is omitted.

[0099] Next, the control unit 50 determines whether there were any failures in the batch update process (step S87). Here, if the memory unit 59 has stored order information 393 that failed to be deleted or sales information 593 that failed to be updated, the control unit 50 determines that there were failures (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 force execution (step S88). If the operation unit 56 accepts an operation in step S88 that does not force execution (No in step S88), the control unit 50 cancels the daily settlement (step S89) and terminates this process.

[0101] In step S88, if the operation unit 56 receives a request to force execution (Yes in step S88), the control unit 50 proceeds to step S90. Also, if it is determined in step S87 that there were no failures (No in step S87), the control unit 50 proceeds to step S90. Also, if the operation to not apply all changes at once is received in step S85 (No in step S85), the control unit 50 proceeds to step S90.

[0102] In step S90, the control unit 50 receives an operation from the operation unit 56 indicating whether the operator (store clerk) permits or prohibits the daily settlement when there are settled but unaccounted items (step S90). If permitted (step S90: permitted), in step S91, the control unit 50 performs the daily settlement, whether there are settled but unaccounted records or not (step S91), and terminates this process. If prohibited (step S90: prohibited), the control unit 50 cancels the daily settlement if there are settled but unaccounted records (step S92), and terminates this process.

[0103] As described above, according to this embodiment, when handing over goods ordered from outside the store to the customer, it is not necessary to perform in-store accounting processing each time. Instead, by performing batch processing during non-business hours or daily settlement processing after closing, it is possible to register sales information 593 based on order information 393 for orders placed outside the store. Therefore, the effort required to register sales from external orders into the existing system can be reduced.

[0104] Furthermore, even if the batch processing fails, this embodiment retains information about the failed operations, allowing for corrective actions such as re-execution.

[0105] Furthermore, the embodiments described above can be modified and implemented as appropriate by changing some of the configurations or functions of each of the devices described above.

[0106] For example, in the above embodiment, the batch update process is performed by manual operation, but the implementation is not limited to this. For example, the implementation may be configured so that the batch update process is performed automatically at regular intervals or when the processing load is low.

[0107] Furthermore, if the system is configured to run automatically as described above, and there is a possibility that the batch update process may be performed during store business hours, it is preferable for the information acquisition unit 501 to distinguish between orders placed inside and outside the store based on the characteristics of the order information records 393, and to acquire only order information 393 from outside the store.

[0108] Furthermore, although the above embodiment described the order server 1 and application server 8 as cloud servers, the implementation is not limited to this, and the order server 1 and application server 8 may be located within the store. Moreover, the order server 1 and application server 8 do not have to be separate devices; in other words, a single device may perform the functions of both the order server 1 and the application server 8.

[0109] Furthermore, although the above embodiment was described using an example of an order placed from outside the store and paid for by the customer, the implementation is not limited to this. In the above embodiment, goods are not prepared for orders placed from outside the store that have not been paid for, but it is also possible to configure the system to import unpaid order information into the order station 3. In that case, for example, a customer who comes to the store to pick up an order placed from outside the store may be configured to make a payment using a device installed in the store before receiving the goods, and the batch reflection process and daily settlement process of the above embodiment may be used in the sales registration of POS 5 in this case. Moreover, the batch reflection process and daily settlement process of the above embodiment may also be used in the sales registration of POS 5 when a customer places an order and makes a payment themselves using a device in the store.

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

[0111] Furthermore, the programs executed by each 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. Alternatively, the programs executed by each of the above-described embodiments may be provided or distributed via a network such as the Internet.

[0112] While several embodiments of the present invention have been described, these embodiments are presented as examples only and are not intended to limit the scope of the invention. These novel embodiments can be carried out in a variety of other forms, and various omissions, substitutions, modifications, and combinations are possible without departing from the spirit of the invention. These embodiments and their variations are included in the scope and spirit of the invention, as well as in the claims of the invention and its equivalents. [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 Department (an example of an acquisition department), 502... In-store Accounting Department, 503...Batch Reflection Section (Example of Registration Section), 504...Daily Settlement Section (Example of Registration Section), 51...CPU, 52...ROM, 53...RAM, 54...Communication section, 55...Display unit, 56...Operation unit, 561...Release key, 57...Scanner, 58...Audio output unit, 60...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] Japanese Patent Publication No. 2023-048187

Claims

1. In a sales data processing device used in conjunction with a management device for managing order information, which is information about orders received by a store, the device performs accounting based on the order information and registers the accounted-for order information as sales information in a predetermined storage unit, It includes a control unit that performs batch processing upon receiving a predetermined operation, The control unit that executes the batch update process, An acquisition unit that acquires from the management device the order information that was received outside the store, paid for by the customer, and not registered as sales information in the storage unit, A registration unit generates sales information based on the order information acquired by the acquisition unit and registers it in the storage unit, A sales data processing device equipped with the following features.

2. The control unit further comprises a daily settlement unit which performs a daily settlement process that is executed after closing time, which includes determining sales and issuing settlement receipts. The aforementioned daily settlement process includes the aforementioned batch reflection process. The sales data processing device according to claim 1.

3. A computer equipped with a sales data processing device, which is used together with a management device for managing order information, which is information about orders received by a store, performs accounting based on the said order information, and registers the settled order information as sales information in a predetermined storage unit, It functions as a control unit that executes a batch update process upon receiving a predetermined operation. The control unit that performs the batch update process is An acquisition unit that acquires from the management device the order information that was received outside the store, paid for by the customer, and not registered as sales information in the storage unit, A registration unit generates sales information based on the order information acquired by the acquisition unit and registers it in the storage unit, A program that makes it function as such.

Images