JP7597754B2 - Order management device, order management method, and order management program - Google Patents

Description

The present invention relates to an order management device, an order management method, and an order management program.

Today, for example, in industries that process and sell food in stores, it is important to manage orders by understanding the lead time from ordering products and ingredients to delivering them to the store.

Patent Document 1 (Patent Publication No. 6880343) discloses a scheduler system. This scheduler system includes a production scheduler, a manufacturing execution system, and a scheduler management device equipped with a plan information acquisition unit and a replanning execution unit.

The plan information acquisition unit of the scheduler management device acquires monitored data, which is data for monitoring the occurrence of an event that requires the re-creation of the first production plan information after the creation of the first production plan information, from another device connected to the scheduler management device. The re-planning execution unit of the scheduler management device detects whether an event has occurred using the monitored data, and, if an event has occurred, instructs the production scheduler to acquire additional information, which is information other than the plan creation information that is information used to create the first production plan information, and the plan creation information.

The planning information acquisition unit instructs the production scheduler to acquire additional information and planning information, and then instructs the production scheduler to recreate second production planning information for orders that span multiple processes, using the acquired additional information and planning information.

Patent No. 6880343

However, sometimes an order is placed with a supplier after the supplier has closed its order intake. In such cases, the order contents are not properly processed by the supplier because the supplier has closed its order intake, which causes inconvenience in that the delivery is not made at the required timing for the ordering party.

The present invention has been made in consideration of the above-mentioned problems, and aims to provide an order management device, an order management method, and an order management program that enable proper ordering.

In order to solve the above-mentioned problems and achieve the object, an order management device according to the present invention is an order management device including a control unit, the control unit including an acquisition unit that acquires a product delivery date or an order request date, a calculation unit that performs at least one of calculation of a product order request deadline by reading order lead time information indicating the time required for product shipment from a storage unit and subtracting the calculated product delivery date from the product delivery date, and calculation of a product scheduled delivery date by reading delivery lead time information indicating the time required for product delivery from the storage unit and adding the calculated product delivery date to the order request date, and a display unit that displays the calculated order request deadline or scheduled delivery date. and a display control unit that displays on the display unit information indicating the product to be ordered, a plurality of dates, and information indicating a date selected and input as the product delivery date from the plurality of dates when a date on which the product will not be shipped is selected and input as the product delivery date from the plurality of dates displayed on the display unit, and when a date on which the product will not be shipped is selected and input as the product delivery date from the plurality of dates displayed on the display unit, the display control unit does not display the information indicating the selected and input date on the display unit.

In order to solve the above-mentioned problems and achieve the object, an order management method according to the present invention is an order management method for an order management device including a control unit, comprising: an acquisition step in which an acquisition unit of the control unit acquires a product delivery date or an order request date; a calculation step in which a calculation unit of the control unit performs at least one of calculation of a product order request deadline by reading order lead time information indicating the time required for product shipment from a storage unit and subtracting the product delivery date from the product delivery date, and calculation of a product scheduled delivery date by reading delivery lead time information indicating the time required for product delivery from the storage unit and adding the delivery lead time information to the order request date; and a display control unit of the control unit displays the calculated order request date. The method includes a display control step of displaying a deadline date or a scheduled delivery date on the display unit, and in the calculation step, if the calculated order request deadline date for the product falls on a day on which the product will not be shipped, a new order request deadline date is calculated by subtracting the time equivalent to the day on which the product will not be shipped from the calculated order request deadline date, and in the display control step, information indicating the product to be ordered, a plurality of dates, and information indicating a date selected and input from the plurality of dates as the delivery date for the product are displayed on the display unit, and if a day on which the product will not be shipped is selected and input as the delivery date of the product from the plurality of dates displayed on the display unit, the information indicating the selected and input date is not displayed on the display unit.

In order to solve the above-mentioned problems and achieve the object, an order management program according to the present invention is an order management program that causes a computer of an order management device to function, and includes an acquisition unit that acquires a product delivery date or an order request date, and a calculation unit that performs at least one of calculation of a product order request deadline by reading order lead time information indicating the time required for product shipment from a storage unit and subtracting the calculated product delivery date from the product delivery date, and calculation of a product scheduled delivery date by reading delivery lead time information indicating the time required for product delivery from the storage unit and adding the calculated product delivery date to the order request date, and Or it functions as a display control unit that displays the scheduled delivery date on the display unit, and when the calculated order request deadline for the product falls on a day on which the product will not be shipped, the calculation unit calculates a new order request deadline by subtracting the time equivalent to the day on which the product will not be shipped from the calculated order request deadline, and the display control unit displays on the display unit information indicating the product to be ordered, a plurality of dates, and information indicating a date selected and input from the plurality of dates as the delivery date for the product, and when a day on which the product will not be shipped is selected and input as the delivery date for the product from the plurality of dates displayed on the display unit, the display control unit does not display the information indicating the selected and input date on the display unit.

The present invention can make it possible to place proper orders.

FIG. 1 is a block diagram showing a hardware configuration of an order management device according to an embodiment. FIG. 2 is a diagram illustrating an example of the product order master. FIG. 3 is a diagram showing an example of the supplier calendar master. FIG. 4 is a diagram illustrating an example of the store master. FIG. 5 is a diagram illustrating an example of the supplier master. FIG. 6 is a diagram illustrating an example of the order classification master. FIG. 7 is a diagram illustrating an example of the deadline master. FIG. 8 is a diagram showing an example of the product number master. FIG. 9 is a diagram illustrating an example of the delivery company master data. FIG. 10 is a flowchart showing the flow of order management processing in the order management device according to the embodiment. FIG. 11 is a diagram for explaining the subtraction process of the shipping lead time and the shipping added lead time. FIG. 12 is a diagram for explaining the subtraction process of the acceptance lead time and the acceptance added lead time. FIG. 13 is a diagram for explaining the process of adding an order deadline to order request deadline information. FIG. 14 is a flowchart for explaining an order input operation using the order input screen in the order management device according to the embodiment. FIG. 15 is a diagram showing an example of an order input screen. FIG. 16 is a diagram for explaining an ordering operation in which a scheduled delivery date is specified in the order management device according to the embodiment.

Below, an order management device according to an embodiment of the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited to the following embodiment.

(Hardware configuration)
Fig. 1 is a block diagram showing a hardware configuration of an order management device 1 according to an embodiment. The order management device 1 shown in Fig. 1 includes a storage unit 2, a control unit 3, a communication interface unit 4, and an input/output interface unit 5. An input device 6 and an output device 7 are connected to the input/output interface unit 5. The output device 7 may be a display unit such as a monitor device (including a home television). The input device 6 may be a keyboard device, a mouse device, a microphone device, or a monitor device that cooperates with a mouse device to realize a pointing device function.

The memory unit 2 may be, for example, a storage device such as a ROM (Read Only Memory), a RAM (Random Access Memory), a HDD (Hard Disk Drive), or a SSD (Solid State Drive). The memory unit 2 includes storage areas such as a product order master 11, a supplier calendar master 12, a store master 13, a supplier master 14, an order classification master 15, a deadline master 16, a product number master 17, and a delivery company master 18. The memory unit 2 also stores an order management program that enables error-free ordering and delivery on the desired date.

Figure 2 is a diagram showing an example of the product order master 11. As shown in Figure 2, the product order master 11 stores (registers) various information such as the store, product, flight, supplier, order classification, acceptance lead time, shipping lead time, and deadline code. The acceptance lead time is the period from when the supplier accepts an order to when the order is prepared for shipping. The shipping lead time is the period from when the supplier ships the order to when the order arrives at the store.

This example in Figure 2 shows that when store A purchases product A in the first shipment, it will require a receipt lead time of "2 days" and a shipping lead time of "1 day". It also shows that the deadline for placing an order in the first shipment is "11:00". Similarly, the example in Figure 2 shows that when store A purchases product B in the second shipment, it will require a receipt lead time of "2 days" and a shipping lead time of "1 day". It also shows that the deadline for placing an order in the second shipment is "14:00".

Figure 3 shows an example of the supplier calendar master 12. In this supplier calendar master 12, the receipt additional lead time and shipping additional lead time for each supplier and each date are stored (registered). The example in Figure 3 shows that the supplier, XX Bussan, is divided into an order receipt department and a shipping department, and the shipping department is closed on May 7th (Saturday) and May 8th (Sunday), so orders cannot be processed on those days. In this case, an order received on May 7th (Saturday) requires a shipping additional lead time of "1 day," and an order received on May 8th (Sunday) requires a shipping additional lead time of "2 days."

It also indicates that the reception department will be unavailable from Tuesday, May 3, 2022 to Friday, May 6, 2022 due to holidays (continuous weekend). It also indicates that the reception department will require an additional reception lead time of "1 day" for receptions on Tuesday, May 3, and an additional reception lead time of "2 days" for receptions on Wednesday, May 4. It also indicates that the reception department will require an additional reception lead time of "3 days" for receptions on Thursday, May 5, and an additional reception lead time of "4 days" for receptions on Friday, May 6.

Figure 4 is a diagram showing an example of the store master 13. As shown in this Figure 4, the store master 13 stores the store code, store name, etc.

Figure 5 is a diagram showing an example of the supplier master 14. As shown in Figure 5, the supplier master 14 stores supplier codes, supplier names, etc.

Figure 6 is a diagram showing an example of the order classification master 15. As shown in this Figure 6, the order classification master 15 stores code values and code names in association with each other.

Figure 7 is a diagram showing an example of the deadline master 16. As shown in this figure, the deadline master 16 stores deadline codes and deadline times in association with each other.

Figure 8 is a diagram showing an example of the product number master 17. As shown in the example in Figure 8, the product number master 17 stores product codes, product names, specifications, and units (pieces or grams, etc.) in association with each other.

Figure 9 is a diagram showing an example of the delivery company master data 18. As shown in the example in Figure 9, the delivery company master data 18 stores flight codes and flight names in association with each other.

(Functional configuration of the order management device)
Next, the control unit 3 executes the order management program stored in the storage unit 2, thereby functioning as an acquisition unit 21, a calculation unit 22, a data generation unit 23, and a display control unit 24. The acquisition unit 21 acquires the delivery date or order request date of the product input by a business operator or the like.

The calculation unit 22 reads out the shipping lead time, shipping added lead time, receipt lead time, and receipt added lead time, which are examples of order lead time information indicating the time required until the product is shipped, from the product order master 11 or the supplier calendar master 12, which are examples of a storage unit, and calculates the product order request deadline by subtracting them from the product delivery date.

The calculation unit 22 also reads out the acceptance lead time and the shipping lead time, which are examples of delivery lead time information indicating the time required for delivery of the product, from the product order master 11, and calculates the earliest delivery date (scheduled delivery date) of the product by adding them to the order request date.

The display control unit 24 displays the calculated order request deadline date or expected delivery date via the output device 7, which is an example of a display unit. The display control unit 24 also displays an order input screen via the output device 7 for inputting the delivery date or order request date of the desired product.

(Order Management Operation)
Next, an order management operation for managing the date on which an order can be placed for a product in the order management device 1 of the embodiment will be described. Fig. 10 is a flowchart showing the flow of an operation for managing an order request deadline, which is an example of the order management operation. The control unit 3 executes each process of the flowchart in Fig. 10 based on the order management program stored in the storage unit 2.

First, in step S1, the acquisition unit 21 acquires the desired delivery date input by the business operator. In step S2, the calculation unit 22 subtracts the shipping lead time detected by referring to the product order master 11 from the delivery date as shown in FIG. 11(a). In the example of FIG. 11(a), the delivery date, which is the date on which the product is desired to be delivered, is Monday, May 9, 2022, and the shipping lead time is "1 day". Therefore, the calculation unit 22 subtracts "1 day" from Monday, May 9, 2022, and calculates the supplier shipping date of Sunday, May 8, 2022.

Next, in step S3, the calculation unit 22 refers to the supplier calendar master 12 as shown in FIG. 11(b) to determine whether or not there is a shipping addition lead time corresponding to the supplier shipping date of Sunday, May 8, 2022. If there is no shipping addition lead time corresponding to the supplier shipping date in the supplier calendar master 12 (step S3: No), the process proceeds to step S5.

If the supplier calendar master 12 contains a shipping additional lead time corresponding to the supplier shipping date (step S3: Yes), the calculation unit 22 subtracts the shipping additional lead time from the supplier shipping date in step S4. In the example of FIG. 11(b), since May 8, 2022 is a Sunday, a shipping additional lead time of "2 days" is stored in the supplier calendar master 12. Therefore, the calculation unit 22 subtracts the shipping additional lead time of "2 days" from the supplier shipping date of Sunday, May 8, 2022, and calculates the supplier shipping date of Friday, May 6, 2022.

Next, in step S5, the calculation unit 22 refers to the product order master 11 and subtracts the acceptance lead time from the supplier shipping date, as shown in FIG. 12(a). In this example, the calculation unit 22 calculates the supplier shipping date of Friday, May 6, 2022 by subtracting the shipping added lead time as shown in FIG. 11(b), so the calculation unit 22 calculates the supplier shipping date of Wednesday, May 4, 2022 by subtracting a lead time of "2 days" from the supplier shipping date of Friday, May 6, 2022, as shown in FIG. 12(a).

Next, in step S6, the calculation unit 22 refers to the supplier calendar master 12 as shown in FIG. 12(b) to determine whether there is a receipt addition lead time corresponding to the supplier shipping date of Wednesday, May 4, 2022. If there is no shipping addition lead time corresponding to the supplier shipping date in the supplier calendar master 12 (step S6: No), the process proceeds to step S8.

If the supplier calendar master 12 contains a shipping additional lead time corresponding to the supplier shipping date (step S6: Yes), the calculation unit 22 subtracts the reception additional lead time from the supplier shipping date in step S7. In the example of FIG. 12(b), a reception additional lead time of "2 days" is stored in the supplier calendar master 12. Therefore, the calculation unit 22 subtracts the reception additional lead time of "2 days" from the supplier shipping date of Wednesday, May 4, 2022, to calculate the supplier shipping date of Monday, May 2, 2022.

Next, in step S8, the data generation unit 23 generates order request deadline information in which the deadline for "flight 1" is added to the supplier shipping date as shown in Fig. 13. In this example, since the finally calculated supplier shipping date is Monday, May 2, 2022, the data generation unit 23 generates order request deadline information in which the deadline for flight 1, "11:00", is added to the supplier shipping date of Monday, May 2, 2022. In step S9, the display control unit 24 displays this order request deadline information on the output device 7. This ends all the processing in the flowchart of Fig. 10.

The business operator recognizes from the order request deadline information displayed on the output device 7 that, for example, if delivery is desired on Monday, May 9, 2022, the order request must be placed by 11:00 on Monday, May 2, 2022. The business operator then places the order request by 11:00 on Monday, May 2, 2022. This allows the order to be placed so that delivery can be obtained on Monday, May 9, 2022.

(Order management using the order entry screen)
Such order management can be performed more clearly and accurately by using the order input screen described below. Fig. 14 is a flowchart showing the flow of order management operations using this order input screen. The control unit 3 executes each process of the flowchart in Fig. 14 based on the order management program stored in the memory unit 2.

In step S11, the display control unit 24 detects a display specification operation of the order input screen performed by the business operator via the input device 6, and displays the order input screen illustrated in FIG. 15 on the output device 7.

This order input screen has an input field for the store from which the order is to be delivered, and an input field for the period for selecting the delivery date (= the period for which the calendar display below will be displayed). The business operator refers to the store master 13 illustrated in FIG. 4, and inputs the store code of the store from which the order is to be delivered, such as "T01". The business operator also inputs the range (period) of delivery dates that the operator wishes to select, such as "May 4, 2022 - May 12, 2022", and operates the confirm button 50.

When the operation of the Confirm button 50 is detected, the calculation unit 22 and the display control unit 24 determine that a range of delivery dates has been specified (step S12: Yes), and in step S13, determine whether each delivery date in the specified range can be specified. Then, based on the result of determining whether each delivery date can be specified in step S13, the display control unit 24 displays dates that cannot be specified in a different display form.

In other words, when the delivery date range (period) is entered and the Confirm button 50 is operated, the display control unit 24 displays a calendar-like order input field for each product from the middle to the bottom of the order input screen shown in FIG. 15. This order input field includes display fields for the product name, delivery name, unit name, and specifications, as well as a field for the business operator to input the number of products desired to be delivered.

In step S13, the calculation unit 22 repeatedly executes the processes of steps S1 to S9 of the flowchart in FIG. 10 for each delivery date in the specified range, thereby calculating the supplier shipping date corresponding to each delivery date (see FIG. 12(b) and FIG. 13). If the calculated supplier shipping date for each delivery date is a date within the range of delivery dates, the display control unit 24 displays an input field for the number of items corresponding to that date in a display format different from the other input fields.

To explain more specifically, the example in FIG. 15 is an example in which the range of May 4 (Wed) to May 12 (Thu) is specified as the range of delivery dates to be selected on May 3, 2022. In this case, the display control unit 24 displays an input field for the number of items to be delivered for each delivery date in the specified range on the order input screen. The calculation unit 22 calculates the supplier shipping date (see FIG. 12(b) and FIG. 13) for each delivery date corresponding to each input field based on the processing of steps S1 to S9 of the flowchart in FIG. 10. If the calculated supplier shipping date for each delivery date is a date included in the range of delivery dates, the display control unit 24 displays the input field for the number of items corresponding to that date as, for example, an input field with a white background, and displays the other input fields as input fields with a gray background (gray display).

In the example of Figure 15, the input fields for the second shipment of product B with delivery dates from Friday, May 6th to Thursday, May 12th, and the input fields for the first shipment of product A with delivery dates from Tuesday, May 10th to Thursday, May 12th are displayed as input fields with a white background, while the other input fields are displayed in gray.

This allows the business operator to recognize that the delivery date corresponding to the input field with a white background can be specified on May 3, 2022, which is the current day in this example. The operator then inputs the number of items to be ordered for the desired product into this input field with a white background. The display control unit 24 displays this input number of items to be ordered in the corresponding input field. The example in FIG. 15 shows that five items of product B have been ordered with Friday, May 6 specified as the delivery date. Similarly, the example in FIG. 15 shows that ten items of product A have been ordered with Tuesday, May 10 specified as the delivery date. Note that the information indicating the number of items to be ordered, such as five or ten, displayed in this way in the input field corresponds to "information indicating the date selected and input as the delivery date for the product."

Next, in step S15 of the flowchart in FIG. 14, whether or not the desired number of items has been input for any of the delivery dates displayed on the calendar is monitored. When an input operation for the desired number of items is detected (step S15: Yes), in step S16, the display control unit 24 determines whether or not the input date is a date that can be specified as a delivery date. That is, as shown in FIG. 15, if an input operation for the number of items has been performed in an input field that is displayed in gray (step S16: No), the display control unit 24 proceeds to step S20 and rejects the input because it is a date for which ordering is difficult.

To reject input, for example, the input operation in that input field may be invalidated and the entered numerical value may be hidden, and in addition to or instead of not displaying the numerical value, a specified error message may be displayed.

On the other hand, if the input operation is performed in an input field with a white background (step S16: Yes), the display control unit 24 determines that a date that can be specified as a delivery date has been specified, and proceeds to step S17. Then, in step S17, the display control unit 24 displays a number indicating the order quantity, such as 5 or 10, as described above, in the input field for the delivery date that was input (selection input process).

For example, the following is an example of the input permission judgment when an order is entered at 13:00 on Tuesday, May 3, 2022.

Specify Monday, May 9, 2022 as the delivery date → Refer to the product order master 11 and subtract the shipping lead time of "1 day" to calculate the supplier shipping date of Sunday, May 8, 2022 → Refer to the supplier calendar master 12 and subtract the shipping additional lead time of "2 days" to calculate the supplier shipping date of Friday, May 6, 2022 → Refer to the product order master 11 and subtract the acceptance lead time of "2 days" to calculate the supplier shipping date of Wednesday, May 4, 2022 → Refer to the supplier calendar master 12 and subtract the acceptance additional lead time of "2 days" to generate order request deadline information for 11:00 on Monday, May 2, 2022 → If the date is outside the range displayed on the calendar on the order input screen, it is determined to be "unacceptable for input."

Specify May 10, 2022 (Tuesday) as the delivery date → Refer to the product order master 11 and subtract the shipping lead time of "1 day" to calculate the supplier shipping date of May 9, 2022 (Monday) → Refer to the supplier calendar master 12 and detect that the shipping additional lead time is "none (0 days)" → Refer to the product order master 11 and subtract the reception lead time of "2 days" to calculate the supplier shipping date of May 7, 2022 (Saturday) → Refer to the supplier calendar master 12 and detect that the reception additional lead time is "none" → Generate order request deadline information for 11:00 on May 7, 2022 (Saturday) → If the date is within the range displayed on the calendar on the order input screen, it is determined that "input is possible."

Specify Friday, May 6, 2022 as the delivery date → Refer to the product order master 11 and subtract the shipping lead time of "1 day" to calculate the supplier shipping date of Thursday, May 5, 2022 → Refer to the supplier calendar master 12 and detect that the shipping additional lead time is "none (0 days)" → Refer to the product order master 11 and subtract the acceptance lead time of "2 days" to calculate the supplier shipping date of Wednesday, May 3, 2022 → Refer to the supplier calendar master 12 and detect that the acceptance additional lead time is "none" → Generate order request deadline information for 14:00 on Wednesday, May 3, 2022 → If the date is within the range displayed on the calendar on the order input screen, it is determined that "input is possible."

Next, after the business operator has input the desired order quantity for the desired delivery date in this manner, he/she operates the registration button 51 shown in FIG. 15. In step S18, the data generation unit 23 monitors whether or not this registration button 51 has been operated. If the operation of the registration button 51 is detected (step S18: Yes), in step S19, the data generation unit 23 generates order registration data including the product name, delivery name, unit name, specifications, delivery date, and order quantity based on the various information entered on the order input screen in FIG. 15, and stores this in the memory unit 2. This completes all the processing in the flowchart in FIG. 14. Note that orders for products are placed with suppliers based on this order registration data.

(Calculation and management of the shortest delivery date)
The above example is an example of managing the order date to obtain the delivery of the product on the desired delivery date, but the shortest delivery date (scheduled delivery date) can also be calculated based on the order date. For example, assume that the order date for product A is 13:00 on Tuesday, May 3, 2022. In this case, the calculation unit 22 first determines whether the order time exceeds the cut-off time of the product order master 11, as shown in FIG. 16(a). In this example, the cut-off time of the product order master 11 is 11:00, while the order is placed at 13:00, so the order processing will actually be performed on the next day or later. Therefore, the calculation unit 22 calculates the supplier acceptance date of May 4, 2022 (Wednesday) by adding "1 day" to Tuesday, May 3, 2022.

Next, the calculation unit 22 calculates the supplier acceptance date of Friday, May 6, 2022 by adding the acceptance lead time of "2 days" detected by referring to the product order master 11 to the supplier acceptance date of Wednesday, May 4, 2022.

Next, the calculation unit 22 calculates the supplier acceptance date of Saturday, May 7, 2022 by adding the shipping lead time of "1 day" detected by referring to the product order master 11 to the supplier acceptance date of Friday, May 6, 2022. This allows the business operator, etc. to recognize that if an order for product A is placed at 13:00 on Tuesday, May 3, 2022, the earliest delivery date will be Saturday, May 7, 2022.

(Effects of the embodiment)
As is clear from the above explanation, the order management device 1 of the embodiment makes it possible to set the supplier's reception holidays, shipping holidays, reception lead times, shipping lead times, etc., and controls whether orders can be entered for the delivery date for each store and each product when entering store orders. This makes it possible to accurately grasp the order deadline and control entry on the order entry screen for each store, product, and supplier. This makes it possible to prevent fraudulent (invalid) orders from stores.

In addition to calculating the order deadline by considering each lead time value with the delivery date as the starting point, the system can also calculate the shortest possible delivery date in the future with the order date as the starting point by using the reception lead time and shipping lead time settings in the product order master 11. By displaying a list on a screen or as a report function, the shortest delivery date (scheduled delivery date) for each store, supplier, and product can be identified and managed.

[Contribution to the United Nations-led Sustainable Development Goals (SDGs)]
This embodiment can contribute to improving business efficiency and promoting appropriate management decisions by companies, thereby making it possible to contribute to Goals 8 and 9 of the SDGs.

In addition, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, which can contribute to the achievement of SDGs Goals 12, 13, and 15.

In addition, this embodiment can contribute to strengthening control and governance, making it possible to contribute to Goal 16 of the SDGs.

[Other embodiments]
The present invention may be embodied in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using a known method.

In addition, the processing procedures, control procedures, specific names, registered data for each process, information including parameters such as search conditions, screen examples, and database configurations shown in this specification and drawings may be changed as desired unless otherwise specified.

Furthermore, with regard to the order management device 1, each component shown in the figure is a functional concept, and does not necessarily have to be physically configured as shown in the figure.

For example, the processing functions of the order management device 1, particularly the control unit 3 and each processing function performed by the control unit 3, may be realized in whole or in part by a CPU (Central Processing Unit) and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded on a non-transient computer-readable recording medium that contains programmed instructions for causing the information processing device to execute the processing described in this embodiment, and is mechanically read by the order management device 1 as necessary. That is, a computer program is recorded in a storage unit such as a ROM or HDD for working with the OS to give instructions to the CPU and perform various processes. This computer program is executed by being loaded into RAM, and works with the CPU to configure the control unit 3.

The order management program of the order management device 1 may also be stored in another server device connected to the order management device 1 via any network, and all or part of it may be downloaded as necessary.

The order management program for executing the process described in this embodiment may be stored in a non-transitory computer-readable recording medium, or may be configured as a program product. Here, the term "recording medium" includes any "portable physical medium" such as a memory card, a Universal Serial Bus (USB) memory, a Secure Digital (SD) card, a flexible disk, a magneto-optical disk, a ROM, an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable and Programmable Read Only Memory (EEPROM (registered trademark)), a Compact Disk Read Only Memory (CD-ROM), a Magneto-Optical Disk (MO), a Digital Versatile Disk (DVD), and a Blu-ray (registered trademark) Disc.

A "program" is a data processing method written in any language or description method, and may be in any format, such as source code or binary code. Note that a "program" is not necessarily limited to a single structure, but also includes a structure that is distributed as multiple modules or libraries, or a structure that works in cooperation with a separate program, such as an OS, to achieve its function. Note that the specific structure and reading procedure for reading a recording medium in the order management device 1 shown in the embodiment, as well as the installation procedure after reading, can use well-known structures and procedures.

The memory unit 2 is a storage means such as a memory device such as RAM or ROM, a fixed disk device such as a hard disk, a flexible disk, or an optical disk, and stores various programs, tables, databases, and web page files used for various processes and providing websites.

The order management device 1 may be configured as an information processing device such as a known personal computer device or a workstation, or may be configured as an information processing device to which any peripheral device is connected. The information processing device may be realized by implementing software (including programs or data, etc.) that realizes the processing described in this embodiment.

Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the figures, and all or part of them can be functionally or physically distributed and integrated in any unit depending on various additions or function additions. In other words, the above-mentioned embodiments can be implemented in any combination, or the embodiments can be implemented selectively.

The present invention is suitable for use in businesses that operate multiple stores and order from the stores to factories and external parties (especially companies that handle food, etc.).

REFERENCE SIGNS LIST 1 Order management device 2 Storage unit 3 Control unit 4 Communication interface unit 5 Input/output interface unit 6 Input device 7 Output device 11 Product order master 12 Supplier calendar master 13 Store master 14 Supplier master 15 Order classification master 16 Deadline time master 17 Product number master 18 Delivery company master 21 Acquisition unit 22 Calculation unit 23 Data generation unit 24 Display control unit

Claims (4)

An order management device including a control unit,
The control unit is
An acquisition unit for acquiring a delivery date or an order request date of a product;
a calculation unit that performs at least one of the following: calculation of an order request deadline for the product by reading out from a storage unit order lead time information indicating the time required until shipment of the product and subtracting the calculated date from the delivery date of the product; and calculation of a scheduled delivery date for the product by reading out from the storage unit delivery lead time information indicating the time required until delivery of the product and adding the calculated date to the order request date;
a display control unit that displays the calculated order request deadline or the scheduled delivery date on a display unit,
When the calculated order request deadline for the product corresponds to a day on which the product will not be shipped, the calculation unit calculates a new order request deadline by subtracting the time corresponding to the day on which the product will not be shipped from the calculated order request deadline;
the display control unit displays, on the display unit, information indicating the product to be ordered, a plurality of dates, and information indicating a date selected and input as the delivery date of the product from among the plurality of dates, and when a date on which the product is not shipped is selected and input as the delivery date of the product from among the plurality of dates displayed on the display unit, hides the information indicating the selected and input date from the display unit;
An order management device comprising : the calculation unit, when the acquisition time of the order request date acquired by the acquisition unit is beyond the order request deadline time stored in the storage unit, calculates the scheduled delivery date as the next day as the order request date;
2. The order management device according to claim 1, An order management method for an order management device including a control unit,
An acquisition step in which an acquisition unit of the control unit acquires a delivery date or an order request date of a product;
a calculation step in which a calculation unit of the control unit performs at least one of the following: calculation of an order request deadline for the product by reading, from a storage unit, order lead time information indicating the time required until shipment of the product, and subtracting the calculated date from the delivery date of the product; and calculation of a scheduled delivery date for the product by reading, from the storage unit, delivery lead time information indicating the time required until delivery of the product, and adding the calculated date to the order request date;
A display control step in which a display control unit of the control unit displays the calculated order request deadline or the scheduled delivery date on a display unit,
In the calculation step, if the calculated order request deadline for the product corresponds to a day on which the product will not be shipped, a new order request deadline is calculated by subtracting the time corresponding to the day on which the product will not be shipped from the calculated order request deadline;
In the display control step, information indicating the product to be ordered, a plurality of dates, and information indicating a date selected and input as the delivery date of the product from among the plurality of dates are displayed on the display unit, and when a date on which the product is not shipped is selected and input as the delivery date of the product from among the plurality of dates displayed on the display unit, the information indicating the selected and input date is hidden from the display unit;
An order management method comprising the steps of : An order management program that causes a computer of an order management device to function,
The computer,
An acquisition unit for acquiring a delivery date or an order request date of a product;
a calculation unit that performs at least one of the following: calculation of an order request deadline for the product by reading out from a storage unit order lead time information indicating the time required until shipment of the product and subtracting the calculated date from the delivery date of the product; and calculation of a scheduled delivery date for the product by reading out from the storage unit delivery lead time information indicating the time required until delivery of the product and adding the calculated date to the order request date;
functioning as a display control unit that displays the calculated order request deadline or scheduled delivery date on a display unit;
When the calculated order request deadline for the product corresponds to a day on which the product will not be shipped, the calculation unit calculates a new order request deadline by subtracting the time corresponding to the day on which the product will not be shipped from the calculated order request deadline;
the display control unit displays, on the display unit, information indicating the product to be ordered, a plurality of dates, and information indicating a date selected and input as the delivery date of the product from among the plurality of dates, and when a date on which the product is not shipped is selected and input as the delivery date of the product from among the plurality of dates displayed on the display unit, hides the information indicating the selected and input date from the display unit;
An order management program that features:

Images