Inventory management device, inventory management method and inventory management program

Abstract

To perform system management on guarantee periods of commercial transaction objects in a plurality of marketing routes.SOLUTION: When a movement of a commercial transaction object is input, a data generation unit refers to a storage unit which is stored with guarantee period management information for a storage place representing whether the movement destination is a storage place where the guarantee period of the commercial transaction object is managed and a common identification number and a common guarantee period attached in common when the storage space as the movement destination is a storage place where the guarantee period is not managed, and then generates movement data including the identification number and guarantee period of the commercial transaction object when the guarantee period management information for a storage place shows that the storage place as the movement destination shown by the movement input is the storage place where the guarantee period is managed and also generates movement data including the common identification number and common guarantee period stored in the storage unit when the guarantee period management information for a storage place shows that the storage place as the movement destination shown by the movement input is a storage place where the guarantee period is not managed. An output control unit outputs the generated movement data to external equipment.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to an inventory management device, an inventory management method, and an inventory management program. [Background technology]

[0002] Patent document 1 (JP 2022-182329 A) discloses an order and warehouse management system that performs order inventory management that occurs when products are ordered by customers, and also performs shipping inventory management by storing products in advance and delivering ordered products ordered by customers.

[0003] In this order receipt and warehouse management system, a computer creates an order receipt for the ordered products ordered by a customer and a shipping slip by determining an allocation source warehouse to ship the stored products.The computer also performs allocation processing to allocate the stored products stored at the allocation source warehouse to the ordered products.The stored products allocated in the allocation processing are then shipped.

[0004] This allows for the integrated management of order inventory at each store and shipment inventory at each warehouse to be managed in a single system. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2022-182329 A Summary of the Invention [Problem to be solved by the invention]

[0006] Here, if there are multiple sales channels for commercial transaction items, such as a sales channel through a wholesaler and a sales channel through stores, it becomes difficult for the system to manage the warranty periods for all commercial transaction items through all sales channels.

[0007] That is, for example, in the case of a commercial transaction object sold in a store, since it is difficult to detect the warranty period of the commercial transaction object purchased by a purchaser, it is difficult to perform system management of the warranty period of the commercial transaction object sold in the store. Therefore, it is difficult to perform system management of the warranty period of the commercial transaction object in all sales channels including the sales channel of such a store.

[0008] The present invention has been made in consideration of the above-mentioned problems, and aims to provide an inventory management device, an inventory management method, and an inventory management program that enable system management of warranty periods for commercial transaction items across multiple sales channels. [Means for solving the problem]

[0009] In order to solve the above-mentioned problems and achieve the object, the inventory management device of the present invention has a data generation unit that, when a transfer input for a commercial transaction object is made, references a memory unit that stores storage location warranty period management information indicating whether the destination storage location is a storage location that manages the warranty period, which is the period for guaranteeing the quality or operation of the commercial transaction object, and a common identification number and common warranty period that are commonly assigned when the destination storage location is a storage location that does not manage the warranty period, and generates transfer data including the identification number and warranty period of the commercial transaction object when the destination storage location indicated in the transfer input is indicated as a storage location that manages the warranty period in the storage location warranty period management information, and generates transfer data including the common identification number and common warranty period stored in the memory unit when the destination storage location indicated in the transfer input is indicated as a storage location that does not manage the warranty period in the storage location warranty period management information, and an output control unit that outputs the generated transfer data to an external device.

[0010] In addition, in order to solve the above-mentioned problems and achieve the object, the inventory management method of the present invention includes a data generation step in which, when a transfer input for a commercial transaction object is made, a data generation unit references a memory unit in which storage location warranty period management information indicating whether the storage location to be the transfer destination is a storage location that manages a warranty period, which is a period for guaranteeing the quality or operation of the commercial transaction object, and a common identification number and common warranty period that are commonly assigned when the storage location to be the transfer destination is a storage location that does not manage the warranty period, and generates transfer data including the identification number and warranty period of the commercial transaction object when the storage location to be the transfer destination indicated by the transfer input is indicated as a storage location that manages the warranty period in the storage location warranty period management information, and generates transfer data including the common identification number and common warranty period stored in the memory unit when the storage location to be the transfer destination indicated by the transfer input is indicated as a storage location that does not manage the warranty period in the storage location warranty period management information; and an output control step in which an output control unit outputs the generated transfer data to an external device.

[0011] In addition, in order to solve the above-mentioned problems and achieve the object, the inventory management program of the present invention causes a computer to function as a data generation unit that, when a transfer input for a commercial transaction object is made, refers to a memory unit in which storage location warranty period management information indicating whether the storage location to be the transfer destination is a storage location that manages the warranty period, which is the period for guaranteeing the quality or operation of the commercial transaction object, and a common identification number and common warranty period that are commonly assigned when the storage location to be the transfer destination is a storage location that does not manage the warranty period, generates transfer data including the identification number and warranty period of the commercial transaction object when the storage location to be the transfer destination indicated in the transfer input is indicated as a storage location that manages the warranty period in the storage location warranty period management information, and generates transfer data including the common identification number and common warranty period stored in the memory unit when the storage location to be the transfer destination indicated in the transfer input is indicated as a storage location that does not manage the warranty period in the storage location warranty period management information, and an output control unit that outputs the generated transfer data to an external device. Effect of the Invention

[0012] The present invention is capable of system-based management of warranty periods for commercial objects across multiple sales channels. [Brief description of the drawings]

[0013] [Figure 1] FIG. 1 is a block diagram showing a hardware configuration of an inventory management device according to an embodiment. [Diagram 2] FIG. 2 is a diagram illustrating an example of the warehouse master. [Diagram 3] FIG. 3 is a diagram illustrating an example of the product master. [Figure 4] FIG. 4 is a diagram illustrating an example of the basic information master. [Diagram 5] FIG. 5 is a diagram showing an example of various data generated during the process from purchase input to sales input in the wholesale sale of food products. [Figure 6] FIG. 6 is a diagram showing an example of various data generated during the period from purchase input to sales input in the case of in-store sales of food products. [Figure 7] FIG. 7 is a diagram illustrating an example of purchase data. [Figure 8] FIG. 8 is a diagram showing an example of inventory data immediately after a purchase input. [Figure 9] FIG. 9 is a diagram showing an example of the movement instruction input screen. [Figure 10] FIG. 10 is a diagram showing an example of a details screen of the transfer instruction input screen. [Figure 11] FIG. 11 is a diagram illustrating an example of the movement instruction data. [Figure 12] FIG. 12 is a diagram showing an example of the shipment input screen. [Figure 13] FIG. 13 is a diagram showing the flow of the automatic setting operation of the expiration date on the details screen of the shipment input screen. [Figure 14] FIG. 14 is a diagram showing an example of a details screen of the shipping input screen in which the expiration date is automatically set. [Figure 15] FIG. 15 is a diagram showing an example of shipping data generated by a shipping input. [Figure 16]FIG. 16 is a diagram showing an example of arrival schedule data generated together with shipping data by inputting shipping. [Figure 17] FIG. 17 is a diagram showing an example of the transfer / receive data generated by the transfer / receive input. [Figure 18] FIG. 18 is a diagram showing an example of inventory data showing warehouse and store inventory corresponding to the movement of food products. [Figure 19] FIG. 19 is a diagram showing an example of a sales input screen for food sold from a warehouse. [Figure 20] FIG. 20 is a diagram showing the flow of the operation of automatically setting the expiration date on the details screen of the sales input screen. [Figure 21] FIG. 21 is a diagram showing an example of a details screen of the sales input screen for food sold from the warehouse. [Figure 22] FIG. 22 is a diagram showing an example of a lot inventory search screen. [Diagram 23] FIG. 23 is a diagram showing an example of a details screen of the sales input screen in a state in which the lot number and expiration date of the details selected from the lot inventory search screen are automatically input. [Figure 24] FIG. 24 is a diagram showing an example of a sales input screen for food products sold by a store. [Diagram 25] FIG. 25 is a diagram showing an example of a details screen of the sales input screen in which a dummy lot number and a dummy expiration date are automatically input when an input indicating sales is made from a store. [Figure 26] FIG. 26 is a diagram showing an example of a details screen of the sales input screen in which the sales quantity (transfer amount) of food items sold from the store has been input. [Figure 27] FIG. 27 is a diagram showing an example of sales data corresponding to food products sold from the warehouse and food products sold from the store. [Figure 28] FIG. 28 is a diagram showing an example of inventory data reflecting sales data. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] Next, an inventory management device according to an embodiment of the present invention will be described in detail with reference to the drawings. The inventory management device according to the embodiment will be described below as managing the expiration dates of food products (products) stored in warehouses and stores. "Warehouses and stores" are examples of storage locations. "Food products" are an example of a commercial transaction object. "Expiration dates" are an example of a warranty period.

[0015] The present invention may also be applied to an inventory management device that manages the operation guarantee period of machines stored in warehouses and stores, and is not limited to the following embodiments.

[0016] (overview) As an example, in the food industry, it is common to use a system to manage the expiration dates of food products, or to manage the expiration dates of food products outside of a system. Also, the food industry is often a business model of selling a large amount of products at a low profit margin, making it difficult to ensure profits. For this reason, sales channels are often expanded to include not only one sales channel, but also other different sales channels.

[0017] For example, if you sell food through a so-called wholesaler, in which the sold food is transported from your own warehouse to a client's warehouse, the expiration date of the sold food can be managed on a system using so-called ERP (Enterprise Resources Planning).

[0018] However, when food is sold through a store, it is difficult to manage which of the foods displayed in the storefront has an expiration date that a customer has purchased. In other words, since foods with various expiration dates are displayed in the storefront, it is difficult to manage the expiration date of the food purchased by a customer. When managing the expiration dates of foods sold in such a store, it is difficult to manage them on an ERP system, so the store must manage them in a ledger or in a separate system.

[0019] Also, when there are multiple sales channels, it is possible to obtain multiple management codes for the same food according to the management system, and manage the expiration date of the same food using these multiple management codes. Or, for example, when using JAN codes (Japanese Article Numbers), it is possible to associate multiple foods with one JAN code and manage the expiration date of each food. However, in either case, managing the expiration date becomes cumbersome. For this reason, expiration dates are managed using a separate system.

[0020] For this reason, the inventory management device of the embodiment manages wholesale inventory based on the actual expiration date when receiving and paying inventory, and eliminates the need for actual management of in-store inventory by using a system-wide expiration date. This makes it possible to manage the expiration dates of foods from multiple sales channels, and also enables the system to manage foods that should be managed by expiration date.

[0021] (Hardware configuration) As shown in FIG. 1, the inventory management device 1 of the embodiment 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 corresponds to a display unit such as a monitor device (including a home television), a printing device, or a speaker device. 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 communication interface unit 4 is connected to a network such as a wide area network such as the Internet or a private network such as a LAN (Local Area Network).

[0022] The storage unit 2 may be, for example, a read only memory (ROM), a random access memory (RAM), a hard disk drive (HDD), or a solid state drive (SSD). The storage unit 2 stores an inventory management program that enables system management of expiration dates of foods sold through multiple sales channels, such as a sales channel from a warehouse and a sales channel from a store. The storage unit 2 also stores a warehouse master 11, a product master 12, and a basic information master 13. The storage unit 2 also stores purchase data, inventory data, movement instruction data, shipping data, arrival schedule data, movement and arrival data, and sales data that are generated by executing the inventory management program in the control unit 3.

[0023] The warehouse master 11 includes a warehouse code, a warehouse name, and information on whether or not expiration date management is performed for a storage location (an example of warranty period management information for a storage location) as shown in Fig. 2. The example in Fig. 2 shows that foods stored in Warehouse A, the wholesale warehouse, and the mail order warehouse (mail order warehouse) are subject to expiration date management (1: subject), and foods stored in Warehouse C are not subject to expiration date management (0: not subject).

[0024] The product master 12 includes a product code, a product name, and information on whether or not a product is subject to expiration date management (an example of warranty period management information for commercial transaction objects) as shown in Fig. 3. The example in Fig. 3 indicates that a canned mackerel (canned mackerel) is subject to expiration date management (1: subject), and red wine is not subject to expiration date management (0: not subject).

[0025] The basic information master 13 includes a common lot number (dummy lot number) and a common expiration date (dummy expiration date) as shown in Fig. 4. The common lot number and common expiration date are used for movement instruction data, movement receipt data, and inventory data corresponding to the movement of food to stores where it is difficult to manage expiration dates, or are data that are used consistently (commonly) for sales data and inventory data generated by sales from stores.

[0026] In this example, which is just one example, the common lot number (dummy lot number) is set to "DUMMY", and the common expiration date (dummy expiration date) is set to "January 1, 2100 (2100 / 01 / 01)".

[0027] (Functional configuration of inventory management device) Next, the control unit 3 executes the inventory management program stored in the storage unit 2, thereby functioning as a display control unit 21 and a data generation unit 22, as shown in FIG. 1. The display control unit 21 is an example of an output control unit. In this example, the description will proceed assuming that the output control unit is the display control unit 21, but the output control unit may be a print control unit or an audio output control unit. When the output control unit is a print control unit, various data described later are printed out via a printer, which is the output device 9. When the output control unit is an audio output control unit, various data described later are output as audio via a speaker device, which is the output device 9.

[0028] When a transfer input for a commercial transaction object (food) is made, the data generating unit 22 refers to a memory unit (warehouse master 11) in which storage location warranty period management information indicating whether the storage location to which the food is to be moved is a storage location that manages the warranty period (best before date), which is the period during which the quality or operation of the commercial transaction object is guaranteed, is stored. In addition, when a transfer input for a commercial transaction object (food) is made, the data generating unit 22 refers to a memory unit (basic information master 13) in which a common identification number and a common warranty period that are commonly assigned when the storage location to which the food is to be moved is a storage location that does not manage the warranty period (best before date), is stored.

[0029] Then, when the storage location to be moved, indicated by the movement input, is indicated as a storage location that manages the warranty period in the storage location warranty period management information (=1 in Figure 2: Warehouse A, wholesale warehouse, mail order warehouse in question), the data generation unit 22 generates movement data (shipment data, movement arrival data, and inventory data, described below) including the identification number and warranty period of the commercial transaction object (food).

[0030] In addition, when the storage location to be moved, indicated by the transfer input, is indicated as a storage location that does not manage the warranty period in the storage location warranty period management information (0 in Figure 2: Store C, which is not included), the data generation unit 22 generates transfer data (transfer arrival data and inventory data, described later) including the common identification number (dummy identification number of DUMMY in Figure 4) and common warranty period (dummy expiration date in Figure 4) stored in the memory unit (basic information master 13).

[0031] When the output control unit is the display control unit 21, the display control unit 21 outputs (displays) the generated movement data to an external device (output device 7).

[0032] In addition, when the storage location of the sold commercial transaction object (food) entered by sales input is indicated as a storage location that manages the warranty period (best before date) in the storage location warranty period management information (storage location expiration date management availability information stored in the warehouse master 11), the data generation unit 22 generates sales data including the identification number (product code) and warranty period (best before date) of the commercial transaction object (food).

[0033] In addition, when the storage location of the sold commercial transaction object (food) entered by sales input is indicated as a storage location that does not manage the warranty period (best before date) in the storage location warranty period management information (storage location expiration date management availability information stored in the warehouse master 11), the data generation unit 22 generates sales data including a common identification number (dummy lot number in Figure 4) and a common warranty period (dummy expiration date in Figure 4).

[0034] The output control unit outputs the generated sales data to an external device.

[0035] The memory unit 2 also stores warranty period management information for the commercial transaction object (food product) indicating whether or not the commercial transaction object (food product) is a commercial transaction object (food product) for which warranty period (best before date) management is performed (best before date management status information for the product stored in the product master 12 in Figure 3).

[0036] The data generation unit 22 generates movement data or sales data that does not include the warranty period or common warranty period when the commercial transaction object for which movement input or sales input has been made is a commercial transaction object for which warranty period management information for the commercial transaction object indicates that warranty period management is not performed.

[0037] In addition, when the commercial transaction object for which movement input or sales input has been made is a commercial transaction object for which warranty period management information for the commercial transaction object (information on whether or not the expiration date for the product is managed) indicates that the warranty period is to be managed, the data generation unit 22 generates movement data or sales data including the identification number and warranty period of the commercial transaction object, or movement data or sales data including a common identification number and a common warranty period, depending on the storage location.

[0038] In addition, when the storage location warranty period management information (information on whether or not expiration date management is performed for the storage location stored in the warehouse master 11 in Figure 2) indicates a warehouse, which is a storage location that manages the warranty period, the data generation unit 22 generates movement data or sales data including the identification number and warranty period of the commercial transaction object.

[0039] In addition, when the storage location warranty period management information (storage location expiration date management information stored in the warehouse master 11 in Figure 2) indicates a store that is a storage location that does not manage the warranty period, the data generation unit 22 generates movement data or sales data including a common identification number and a common warranty period.

[0040] (Inventory Management Overview) Next, Fig. 5 and Fig. 6 are diagrams showing an outline of the inventory management operation in the inventory management device 1 of the embodiment. Of these, Fig. 5 shows an outline of the inventory management operation in wholesale sales. In Fig. 5, the control unit 3 functions as the data generation unit 22 based on the inventory management program stored in the storage unit 2, and generates inventory data, movement instruction data, shipment data, movement arrival data, and sales data in response to the purchase input, movement instruction input, shipment input, movement arrival input, and sales input by the operator in steps S1 to S5, and stores them in the storage unit 2. In this wholesale sales, inventory management is performed based on the lot number and expiration date attached to foods such as canned mackerel.

[0041] In contrast, Fig. 6 shows an overview of the inventory management operation in store sales. In the case of this store sales inventory management, the control unit 3 also functions as the data generation unit 22 based on the inventory management program, and generates inventory data, movement instruction data, shipment data, movement arrival data, and sales data in response to the operator's purchase input, movement instruction input, shipment input, movement arrival input, and sales input in steps S1 to S5, and stores them in the storage unit 2. However, in the case of this store sales, for the movement arrival data, inventory data, and sales data after the shipment input, the lot number and expiration date attached to foods such as canned mackerel are converted into a common lot number (dummy lot number) and a common expiration date (dummy expiration date), and are used consistently. This makes it possible to manage the expiration dates of foods from multiple sales channels through the system.

[0042] (Details on inventory management) Next, such inventory control operations will be described in detail.

[0043] (Step S1: Purchase input) First, in the purchase input in step S1 described above, the operator inputs the purchase category, business code, purchase date, warehouse in which the purchased food is stored, product code, product name, quantity, unit price, purchase amount, lot number, and expiration date via a purchase input screen (not shown). The data generation unit 22 automatically assigns a purchase number and a row number based on such purchase input, generates purchase data as shown in FIG. 7, and stores it in the storage unit 2.

[0044] The example in Figure 7 is an example in which 10 cans of canned mackerel and 2 bottles of red wine were received at Warehouse A as regular purchases on July 7, 2023. The unit price of the canned mackerel is 200 yen, so the cost price is 2,000 yen. The lot number of the canned mackerel is "20230707" and the expiration date is "November 30, 2024."

[0045] The example in Figure 7 shows that 8 cans of canned mackerel were received in Warehouse A as a regular purchase on July 8, 2023. The unit price of canned mackerel is 200 yen, so the cost price is 1,600 yen. The lot number of the canned mackerel is "20230708" and the expiration date is "December 31, 2024."

[0046] Based on such purchase data, the data generation unit 22 generates inventory data including a warehouse name, product code, product name, quantity, lot number, and expiration date, as exemplified in Fig. 8. Since the inventory data shown in Fig. 8 is generated based on the purchase data shown in Fig. 7, the storage location of 10 cans of mackerel with a product code of "S001", a lot number of "20230707", and an expiration date of "November 30, 2024" is generated to indicate "Warehouse A" and stored in the memory unit 2.

[0047] 8 is generated to indicate that the storage location of eight cans of canned mackerel, which have a product code of "S001", a lot number of "20230708", and a best-before date of "December 31, 2024", is "Warehouse A", and is stored in the memory unit 2. Similarly, the inventory data shown in FIG. 8 is generated to indicate that the storage location of two bottles of red wine, which have a product code of "S120" and a lot number of "20230707", is "Warehouse A", and is stored in the memory unit 2.

[0048] (Step S2: Movement instruction input) Next, the input of an instruction to move the food in step S2 is performed via a transfer instruction input screen, as exemplified in Fig. 9, which is displayed by the display control unit 21 via the output device 7. On this transfer instruction input screen, the operator inputs the establishment code of the establishment from which the food will be moved, the transfer date, the name of the warehouse from which the food will be shipped, the transfer category, and the name of the warehouse to which the food will be stored.

[0049] In the example of Figure 9, "T100" is entered as the establishment code for the establishment transferring the food, and "July 8, 2023" is entered as the transfer date. In addition, the above-mentioned "Warehouse A" is entered as the name of the warehouse from which the food will be shipped, "Inter-warehouse transfer" is entered as the transfer category, and "Wholesale Warehouse" is entered as the name of the warehouse into which the food will be stored.

[0050] In addition, the operator designates the display of a transfer instruction details screen in order to input details of the transfer instruction in addition to the outline of the transfer instruction. When this display designation is performed, the display control unit 21 displays a details screen of the transfer instruction input screen illustrated in FIG. 10 via the output device 7.

[0051] The operator inputs the product code, number to be moved, lot number, and expiration date of the food to be moved on the details screen of this transfer instruction input screen. The example in Fig. 10 shows that "4 cans of canned mackerel" with a product code of "S001", lot number of "20230707", and expiration date of "November 30, 2024" will be moved to the above-mentioned "wholesale warehouse".

[0052] In this way, when details are entered on the details screen of the transfer instruction input screen and the operator operates the confirm button shown in Fig. 10, the input contents on the details screen are displayed in the details display field (blank square area in Fig. 9) of the transfer input screen shown in Fig. 9. To create transfer instruction data with this input contents, the operator operates the register button shown in Fig. 9.

[0053] When the registration button on the transfer instruction input screen shown in Fig. 9 is operated, the data generation unit 22 generates transfer instruction data as exemplified in Fig. 11 based on the input contents on the transfer instruction input screen (and the details screen of the transfer instruction input screen). The example of the transfer instruction data in Fig. 11 is an example in which the above-mentioned transfer instruction input is performed four times, generating four columns of records.

[0054] Specifically, the record in the first column of Figure 11 is a record of movement instruction data that instructs the movement of "4 cans" of canned mackerel with a product code of "S001", a lot number (shipping lot number) of "20230707", and an expiration date of "November 30, 2024" from "Warehouse A" to the "Wholesale Warehouse" with a scheduled shipping date of July 7, 2023 and a scheduled arrival date of July 8, 2023.

[0055] In addition, the record in the second column of Figure 11 is a record of movement instruction data that instructs the movement of "3 cans" of canned mackerel with product code "S001", lot number (shipping lot number) "20230707", and expiration date "November 30, 2024" from "Warehouse A" to "Store C" with a scheduled shipping date of July 7, 2023 and a scheduled arrival date of July 8, 2023.

[0056] In addition, the record in the third column of Figure 11 is a record of movement instruction data that instructs the movement of "3 cans" of canned mackerel with product code "S001", lot number (shipping lot number) "20230708", and expiration date "December 31, 2024" from "Warehouse A" to the "Wholesale Warehouse" with a scheduled shipping date of July 8, 2023 and a scheduled arrival date of July 9, 2023.

[0057] In addition, the fourth record in Figure 11 is a record of movement instruction data that instructs the movement of "4 cans" of canned mackerel with product code "S001", lot number (shipping lot number) "20230708", and expiration date "December 31, 2024" from "Warehouse A" to "Warehouse C" with a scheduled shipping date of July 8, 2023 and a scheduled arrival date of July 9, 2023.

[0058] (Step S3: Shipping input) Next, when the food is moved by inputting such a movement instruction, the operator performs a shipment input in step S3. When the operator performs an operation to specify a shipment input, the display control unit 21 displays a shipment input screen, as exemplified in FIG. 12, via the output device 7. The operator inputs the establishment code of the establishment from which the food is shipped, the shipping date, and the shipping warehouse to this shipment input screen. In addition, the operator inputs the scheduled shipping date, scheduled arrival date, and receiving warehouse as "extraction conditions". The example in FIG. 12 is an example in which a scheduled shipping date of "July 8, 2023" and a scheduled arrival date of "July 9, 2023" are specified as "extraction conditions".

[0059] When such an "extraction condition" is specified, the display control unit 21 detects the movement instruction data stored in the storage unit 2 and shown in Fig. 11, in which the shipping warehouse is "Warehouse A", the planned shipping date is "July 8, 2023", and the planned arrival date is "July 9, 2023". In the example of Fig. 11, the movement instruction data in the third and fourth columns are detected.

[0060] Display control unit 21 displays details corresponding to the detected movement instruction data as an "extraction result" for the "extraction condition" in a detail display field below the input field for extraction conditions shown in Fig. 12. The example in Fig. 12 is an example in which detail data indicating that three cans of canned mackerel have been stocked at a wholesale warehouse, which corresponds to the movement instruction data in the third column of Fig. 11, and detail data indicating that four cans of canned mackerel have been stocked at store C, which corresponds to the movement instruction data in the fourth column of Fig. 11, are displayed in the detail display field.

[0061] Here, in order to manage the expiration date of shipped food products, the operator selects the detailed data of the desired food product from the detailed data displayed in the detailed display field of the shipment input screen, and operates the line call button shown in Fig. 12. When this line call button is operated, the display control unit 21 displays, via the output device 7, the detailed screen of the shipment input screen corresponding to the detailed data selected by the operator, as shown in Fig. 14.

[0062] At this time, the data generation unit 22 generates automatic input data for automatically inputting the shipping lot number and the expiration date into the details screen of the shipment input screen shown in Figure 14, depending on whether or not the expiration date of the shipped product (food) is managed.

[0063] Specifically, as shown in Fig. 13, the data generation unit 23 first refers to the product master 12 shown in Fig. 3 based on a product code such as "S001" and determines whether or not the food with that product code is subject to expiration date management. If the food with that product code is not subject to expiration date management (0: not subject), the data generation unit 22 generates automatic input data in which only the shipping lot number of the movement instruction data is input. The display control unit 21 displays, via the output device 7, a details screen of the shipment input screen with the shipping lot number automatically input based on this automatic input data.

[0064] In contrast, in the case of canned mackerel with a product code of "S001", referring to the product master 12, it is found to be subject to expiration date management (1: subject). In this case, as shown in Fig. 13, the data generating unit 22 continues to refer to the warehouse master 11 shown in Fig. 2 and determines whether the storage location to which the food with that product code is to be moved is a storage location subject to expiration date management.

[0065] If the storage location to which the food of that product code is to be moved is a storage location subject to expiration date management (1: target), the data generation unit 22 generates automatic input data that inputs the shipping lot number and expiration date of the movement instruction data. The display control unit 21 displays, via the output device 7, a detail screen of the shipment input screen in which the shipping lot number and expiration date have been automatically input based on this automatic input data. The example of FIG. 14 is an example in which the shipping lot number of "20230708" and the expiration date of "December 31, 2023" of a can of mackerel shipped in three cans on July 8, 2023 are automatically input into the detail screen of the shipment input screen.

[0066] On the other hand, if the storage location to which the food of the product code is to be moved is not a storage location subject to expiration date management (0: not applicable), the data generation unit 22 refers to the basic information master 13 shown in FIG. 4 and detects the common lot number (dummy lot number) and the common expiration date (dummy expiration date). Then, the data generation unit 22 generates automatic input data into which the common lot number (dummy lot number) and the common expiration date (dummy expiration date) are input. The display control unit 21 automatically inputs the common lot number (dummy lot number) into the shipping lot number based on this automatic input data, and displays, via the output device 7, a detailed screen of the shipping input screen in which the common lot number (dummy lot number) is automatically input into the expiration date, and the common expiration date (dummy expiration date) is automatically input into the expiration date. As a result, a detailed screen of the shipping input screen is displayed in which "DUMMY" is automatically input as the shipping lot number and "January 1, 2100" is automatically input as the expiration date.

[0067] Next, the data generating unit 22 generates the shipping data illustrated in FIG. 15 based on the input contents of such a shipping input screen (and the details screen of the shipping input screen). The example of FIG. 15 shows that four cans of mackerel with an outgoing lot number of "20230707" and an outgoing best-before date of "November 30, 2024" were shipped from Warehouse A to the wholesale warehouse on July 7, 2023. Similarly, the example of FIG. 15 shows that three cans of mackerel with an outgoing lot number of "20230707" and an outgoing best-before date of "November 30, 2024" were shipped from Warehouse A to Store C on July 7, 2023.

[0068] Similarly, the example of FIG. 15 shows that three cans of mackerel with the shipping lot number "20230708" and the shipping expiration date "December 31, 2024" were shipped from Warehouse A to the wholesale warehouse on July 8, 2023. Similarly, the example of FIG. 15 shows that four cans of mackerel with the shipping lot number "20230708" and the shipping expiration date "December 31, 2024" were shipped from Warehouse A to Store C on July 8, 2023.

[0069] In addition to such shipping data, data generating unit 22 generates scheduled arrival data as shown in Fig. 16. This scheduled arrival data is data indicating foods that are scheduled to be received at a storage location (receiving warehouse) that is the shipping destination. Specifically, the scheduled arrival data includes a scheduled arrival number, row number, shipping number, row number, scheduled arrival date, shipping warehouse name, receiving warehouse name, product code, product name, quantity, shipping lot number, shipping best before date, receiving lot number, and best before date.

[0070] This expected arrival data is basically the same as the shipping data, but the difference from the shipping data is that the shipping date becomes the expected arrival date, and the arrival lot number and the expiration date are added. As for the arrival lot number, as explained using Figure 13, if the shipped food is a food that is subject to expiration date management and the storage location to which it is shipped is a storage location that manages the expiration date of the stored food, the expiration date such as "November 30, 2024" or "December 31, 2024" is added to the expected arrival data together with the arrival lot number such as "20230707" or "20230708" as shown in the records in the first and third columns of Figure 16.

[0071] In contrast, as explained using Figure 13, if the shipped food is one that is subject to expiration date management, but the storage location to which it is shipped is a storage location that does not manage the expiration dates of the stored food, a dummy expiration date of "January 1, 2024" (dummy expiration date) will be added to the scheduled arrival data along with the receiving lot number (= dummy lot number) of "DUMMY", as shown in the records in the second and fourth columns of Figure 16.

[0072] (Step S4: Input of moving stock) Next, when the shipped food is moved to the storage location, the operator inputs the moving and receiving number, row number, expected receiving number, row number, warehouse entry date, shipping warehouse, receiving warehouse, product code, product name, quantity, shipping lot number, shipping expiration date, receiving lot number, and expiration date of the moved and received food, via a moving and receiving input screen (not shown). The data generation unit 22 generates moving and receiving data as shown in FIG. 17 based on the input contents and stores it in the memory unit 2.

[0073] This transfer arrival data is basically the same as the scheduled arrival data, but it differs from the scheduled arrival data in that the scheduled arrival number becomes the transfer arrival number, the shipping number becomes the scheduled arrival number, and the scheduled arrival date becomes the arrival date. Note that the "DUMMY" receiving lot number (= dummy lot number) and the dummy expiration date of "January 1, 2024" (dummy expiration date) are used consistently in the transfer arrival data as well.

[0074] In addition, the data generating unit 22 generates such transfer data in the transfer input, and reflects the change in inventory due to the transfer of food in the inventory data as shown in FIG. 18. Specifically, in this example, the mackerel cans stored in the A warehouse with the lot number "20230707" and the expiration date "November 30, 2024" were initially "10 cans", but "4 cans" were shipped to the wholesale warehouse and "3 cans" were shipped to the C store. Therefore, the data generating unit 22 updates the inventory data so that the mackerel cans stored in the A warehouse with the lot number "20230707" and the expiration date "November 30, 2024" become "10 cans - 4 cans - 3 cans = 3 cans remaining".

[0075] Similarly, the canned mackerel with the lot number "20230708" stored in Warehouse A and the expiration date of "December 31, 2024" was initially "8 cans", but "3 cans" were shipped to the wholesale warehouse and "4 cans" were shipped to Store C. Therefore, the data generation unit 22 updates the inventory data so that the canned mackerel with the lot number "20230708" stored in Warehouse A and the expiration date of "December 31, 2024" becomes "8 cans - 3 cans - 4 cans = 1 can remaining".

[0076] In addition, the data generation unit 22 generates additional inventory data corresponding to the transfer of "4 cans" of canned mackerel with a lot number of "20230707" and a best-before date of "November 30, 2024" from warehouse A to the wholesale warehouse.

[0077] Similarly, the data generation unit 22 generates additional inventory data corresponding to "3 cans" of canned mackerel with a lot number of "20230708" and a best-before date of "December 31, 2024", which were moved from warehouse A to the wholesale warehouse.

[0078] In addition, as shown in FIG. 17, the mackerel cans with the "DUMMY" receiving lot number (=dummy lot number) and the dummy expiration date (dummy expiration date) of "January 1, 2024" that were moved to store C are "3 cans" of mackerel cans with the original shipping lot number "20230707" and the shipping expiration date "November 30, 2024", and "4 cans" of mackerel cans with the original shipping lot number "20230708" and the shipping expiration date "December 31, 2024", totaling "7 cans". Therefore, as shown in FIG. 18, the data generation unit 22 additionally generates inventory data for store C with the "DUMMY" receiving lot number (=dummy lot number) and the mackerel cans with the dummy expiration date (dummy expiration date) of "January 1, 2024" as "7 cans".

[0079] In this way, the inventory management device 1 of the embodiment manages the storage location (= warehouse) that manages the expiration date using the original lot number and expiration date. Also, for storage locations (= stores) that are difficult to manage from an operational standpoint, the management form is such that the lot number and expiration date are consistently managed using the same dummy lot number and dummy expiration date.

[0080] (Step S5: Enter sales) Next, the operator inputs the sales generated when the food moved to the wholesale warehouse or store is purchased by a purchaser or customer. In this case, the operator operates the input device 6 to specify the display of a sales input screen. This causes the display control unit 21 to display the sales input screen shown in FIG. 19 via the output device 7. The operator inputs the establishment code, sales date, customer code, warehouse code, sales category, and billing code into this sales input screen.

[0081] The example in Fig. 19 is an input example of sales from a wholesale warehouse with warehouse code "200" to customer A with customer code "T001". After the operator inputs data into such a sales input screen, the operator then specifies the display of a details screen of the sales input screen. This causes the display control unit 21 to display on the output device 7 the details screen of the sales input screen shown in Fig. 21.

[0082] The operator inputs the product code corresponding to the sold food and the quantity sold (number moved) into the details screen of the sales input screen, and operates the search button shown in Fig. 21. The example in Fig. 21 is an input example when "2 cans" of canned mackerel with product code "S001" have been sold. When the search button is operated, the display control unit 21 searches the inventory data shown in Fig. 18 for the inventory of "canned mackerel" entered into the details screen of the sales input screen shown in Fig. 21, which is the inventory of the "wholesale warehouse" entered into the sales input screen shown in Fig. 19, and displays it on a lot inventory search screen exemplified in Fig. 22.

[0083] In the example of FIG. 18, the mackerel cans stored in the "wholesale warehouse" are "4 cans" of mackerel cans with the lot number "20230707" and the expiration date "November 30, 2024", and "3 cans" of mackerel cans with the lot number "20230708" and the expiration date "December 31, 2024". For this reason, the display control unit 21 displays, on the lot inventory search screen shown in FIG. 22, as inventory search results, a record with the lot number "20230707", the expiration date "November 30, 2024", and the quantity "4 cans", and a record with the lot number "20230708", the expiration date "December 31, 2024", and the quantity "3 cans".

[0084] The operator selects, via the input device 6, a record corresponding to the lot number and expiration date corresponding to the current sale from among the records displayed on the lot inventory search screen as the inventory search result. When this selection is made, the display control unit 21 subtracts "2 cans", which is the number of transfers of canned mackerel corresponding to the current sale, entered into the details screen of the sales input screen shown in FIG. 21, from "4 cans", which is the quantity of canned mackerel with the lot number "20230707" and the expiration date "November 30, 2024", which is the record selected by the operator (4 cans - 2 cans = 2 cans). Then, the display control unit 21 displays the subtraction result of "2 cans" as the quantity of the record of canned mackerel with the lot number "20230707" and the expiration date "November 30, 2024", as shown in FIG. 22.

[0085] As a result, on the lot inventory search screen shown in Figure 22, the quantity of canned mackerel in the inventory search results, which was displayed as "4 cans" before the record was selected, is updated to "2 cans" after the record is selected.

[0086] Next, the operator selects a desired record on the lot inventory search screen shown in FIG. 22 and operates the Confirm button. When the Confirm button is operated, the data generation unit 22 generates automatic input data for automatically inputting the lot number and expiration date of the selected record shown in FIG. 22 into the lot number and expiration date of the details screen of the sales input screen described above, as shown in FIG. 23. Based on this automatic input data, the display control unit 21 automatically inputs the lot number, for example, "20230707" and the expiration date, for example, "November 30, 2024", corresponding to the record selected on the lot inventory search screen into the lot number and expiration date of the details screen of the sales input screen, as shown in FIG. 23.

[0087] Fig. 20 shows the flow of the automatic input operation of lot number and expiration date on the details screen of the sales input screen. When the Confirm button shown in Fig. 22 is operated, the data generation unit 22 refers to the product master 12 shown in Fig. 3 based on the product code such as "S001" on the lot inventory search screen. Then, for example, in the case of red wine, when the product expiration date management information is "0: Not applicable", indicating that expiration date management is not performed, the data generation unit 22 does not generate automatic input data. In this case, the display control unit 21 hides at least the expiration date on the details screen of the sales input screen (leaving it blank).

[0088] In contrast, by referring to the product master 12 shown in FIG. 3, when the product expiration date management information is "1: target" indicating that the expiration date is managed, such as for canned mackerel, the data generation unit 22 refers to the warehouse master 11 shown in FIG. 2 based on the warehouse code such as "200" on the lot inventory search screen. Then, when the storage location expiration date management information is "1: target" indicating that the expiration date is managed, such as for example, A warehouse, wholesale warehouse, mail order warehouse, etc., the data generation unit 22 generates automatic input data for automatically inputting the lot number, for example, "20230707", and the expiration date, for example, "November 30, 2024", corresponding to the record selected on the lot inventory search screen, as described above. As a result, as shown in FIG. 23, the display control unit 21 automatically inputs and displays the lot number and expiration date of the record selected on the lot inventory search screen for the lot number and expiration date on the details screen of the sales input screen.

[0089] On the other hand, by referring to the warehouse master 11 shown in Fig. 2, when the storage location expiration date management information is "0: Not applicable" indicating that expiration date management is not performed, such as in store C, the data generation unit 22 generates automatic input data for automatically inputting the above-mentioned dummy lot number and dummy expiration date into the lot number and expiration date on the details screen of the sales input screen. The display control unit 21 automatically inputs the dummy lot number and dummy expiration date into the lot number and expiration date on the details screen of the sales input screen based on this automatic input data.

[0090] In other words, this dummy lot number and dummy expiration date are automatically entered when the storage location (warehouse) where the food was sold is, for example, Store C, and the expiration date management information for the storage location is "0: Not applicable," indicating that expiration date management is not performed, as illustrated in Figure 24.

[0091] To explain step by step, when the food moved to store C is sold, the operator enters the warehouse code "300", which is the warehouse code for "store C", into the sales input screen shown in Figure 24 as the "warehouse" where the sale occurred.

[0092] Next, the operator displays the details screen of the sales input screen shown in Fig. 25 and inputs the number of foods sold (number of transfers) corresponding to the sales. When the display of the details screen of the sales input screen is specified, the data generation unit 22 refers to the warehouse master 11 shown in Fig. 2 based on the warehouse code of the sales input screen shown in Fig. 24. In this case, since the warehouse code is "300" indicating "Store C", the storage location expiration date management information becomes "0: Not applicable" indicating that expiration date management is not performed.

[0093] When the storage location expiration date management information is "0: not applicable" indicating that expiration date management is not performed, the data generation unit 22 refers to the basic information master 13 shown in Fig. 4 and detects the common lot number (DUMMY) and common expiration date (January 1, 2100). The data generation unit 22 then generates automatic input data for automatically inputting the detected dummy lot number and dummy expiration date into the lot number and expiration date on the details screen of the sales input screen. Based on this automatic input data, the display control unit 21 automatically inputs and displays the dummy lot number and dummy expiration date into the lot number and expiration date on the details screen of the sales input screen, as shown in Fig. 25.

[0094] The operator inputs the number of transfers, which is the number of canned mackerel sold this time, into the details screen of the sales input screen into which the dummy lot number and dummy expiration date have been automatically input, as shown in Fig. 26, and presses the Confirm button. When the Confirm button on the details screen of the sales input screen is pressed, the data generation unit 22 generates the sales data shown in Fig. 27 and updates the inventory data shown in Fig. 28.

[0095] Of the sales data shown in FIG. 27, the sales data in the first column of the record is sales data resulting from the sale of two cans of canned mackerel that were moved from Warehouse A to the wholesale warehouse. Canned mackerel is a product (food) subject to expiration date management as shown in FIG. 3, and the "wholesale warehouse" is a storage location subject to expiration date management as shown in FIG. 2. For this reason, as shown in the first column of the record in FIG. 27, the sales data is managed by the lot number "20230707" originally attached to the canned mackerel and the expiration date "November 30, 2024".

[0096] Furthermore, among the sales data shown in FIG. 27, the sales data in the record in the second column is sales data resulting from the sale of three cans of canned mackerel that were moved from Warehouse A to Store C. Canned mackerel is a product (food) subject to expiration date management as shown in FIG. 3, and "Store C" is a storage location that is not subject to expiration date management as shown in FIG. 2. For this reason, as shown in the record in the second column of FIG. 27, the sales data is managed with a dummy lot number of "DUMMY" and a dummy expiration date of "January 1, 2024."

[0097] In this example, two cans of canned mackerel with a lot number of "20230707" and a best-before date of "November 30, 2024" were sold from the wholesale warehouse. Therefore, the data generation unit 22 subtracts two cans, which is the number of cans sold, from four cans, which is the original number of canned mackerel stored in the wholesale warehouse, and updates the inventory data shown in FIG. 28 so that the remaining number of canned mackerel in the wholesale warehouse is two cans.

[0098] In this example, three cans were sold out of a total of seven cans of canned mackerel managed at "Store C" with a dummy lot number of "DUMMY" and a dummy expiration date of "January 1, 2024". Therefore, the data generating unit 22 subtracts three cans, which is the number of cans sold, from the original number of canned mackerel stored at Store C, which is seven cans, and updates the inventory data shown in FIG. 28 so that the remaining number of canned mackerel managed at Store C with a dummy lot number of "DUMMY" and a dummy expiration date of "January 1, 2024" is four cans.

[0099] (Effects of the embodiment) As is clear from the above explanation, when inventory is received or paid, the inventory management device 1 of the embodiment manages inventory based on the actual expiration date if it is "wholesale inventory." Also, when it is "storefront inventory," inventory management is performed based on the expiration date (dummy lot number and dummy expiration date) common to the system of the inventory management device 1 of the embodiment, making substantial management unnecessary.

[0100] This allows the system to manage the expiration dates of food products sold through multiple sales routes (sales routes from warehouses and sales routes from stores). It also allows the system to manage food products that should have their expiration dates managed.

[0101] [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, and can therefore contribute to Goals 8 and 9 of the SDGs.

[0102] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to Goals 12, 13, and 15 of the SDGs.

[0103] Furthermore, this embodiment can contribute to strengthening control and governance, making it possible to contribute to Goal 16 of the SDGs.

[0104] [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.

[0105] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically may be performed manually, and all or part of the processes described as being performed manually may be performed automatically.

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

[0107] Furthermore, with regard to the inventory management device 1, the components shown in the figures are merely conceptual functional components, and the device does not necessarily have to be physically configured as shown in the figures.

[0108] For example, the processing functions of the inventory 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 in a non-transient computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processing described in this embodiment, and is mechanically read by the inventory management device 1 as necessary. That is, a computer program for giving instructions to the CPU in cooperation with the OS and performing various processing is recorded in a storage unit such as a ROM or HDD. This computer program is executed by being loaded into a RAM, and constitutes the control unit 3 in cooperation with the CPU.

[0109] In addition, the inventory management program of this inventory management device 1 may be stored in another server device connected to the inventory management device 1 via any network, and it is also possible to download all or part of it as needed.

[0110] In addition, the inventory management program for executing the process described in this embodiment may be stored in a non-transient 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.

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

[0112] 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.

[0113] The inventory 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 connected to any peripheral device. The information processing device may be realized by implementing software (including programs or data, etc.) that realizes the processing described in this embodiment.

[0114] Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be functionally or physically distributed and integrated in any unit according to various additions or functional loads. In other words, the above-mentioned embodiments can be implemented in any combination, or the embodiments can be implemented selectively. [Industrial Applicability]

[0115] The present invention is suitable for application to industries involved in the wholesale and retail of commercial items such as food, machinery, and parts. [Explanation of symbols]

[0116] 1. Inventory management device 2 Storage section 3. Control Unit 4. Communication Interface Section 5 Input / Output Interface Section 6 Input Devices 7 Output Devices 11 Warehouse Master 12 Product Master 13 Basic Information Master 21 Display control unit 22 Data Generation Section

Claims

1. a data generating unit which, when a transfer input for a commercial transaction object is made, refers to a memory unit which stores storage location warranty period management information indicating whether the storage location to be the transfer destination is a storage location that manages a warranty period, which is a period for guaranteeing the quality or operation of the commercial transaction object, and a common identification number and common warranty period which are commonly assigned when the storage location to be the transfer destination is a storage location that does not manage the warranty period, and generates transfer data including the identification number and the warranty period of the commercial transaction object when the storage location to be the transfer destination indicated by the transfer input is indicated in the storage location warranty period management information as a storage location that manages the warranty period, and generates transfer data including the common identification number and the common warranty period stored in the memory unit when the storage location to be the transfer destination indicated by the transfer input is indicated in the storage location warranty period management information as a storage location that does not manage the warranty period; an output control unit that outputs the generated movement data to an external device; An inventory management device having the following:

2. the data generation unit generates sales data including an identification number and the warranty period of the commercial transaction object when the storage location of the sold commercial transaction object input by sales input is indicated in the storage location warranty period management information as a storage location that manages the warranty period, and generates sales data including the common identification number and the common warranty period when the storage location of the sold commercial transaction object input by sales input is indicated in the storage location warranty period management information as a storage location that does not manage the warranty period; The output control unit outputs the generated sales data to the external device; 2. The inventory management device according to claim 1,

3. the storage unit stores warranty period management information for the commercial transaction object, the warranty period management information indicating whether the commercial transaction object is a commercial transaction object for which the warranty period is to be managed; said data generation unit generates the movement data or the sales data not including the warranty period or the common warranty period when the commercial transaction object for which the movement input or the sales input has been made is a commercial transaction object for which warranty period management information for the commercial transaction object indicates that the warranty period is not managed, and generates the movement data or the sales data including the identification number and the warranty period of the commercial transaction object, or the movement data or the sales data including the common identification number and the common warranty period, according to the storage location when the commercial transaction object for which the movement input or the sales input has been made is a commercial transaction object for which warranty period management information for the commercial transaction object indicates that the warranty period is managed; 3. The inventory management device according to claim 2, wherein:

4. the data generation unit generates the movement data or the sales data including the identification number and the warranty period of the commercial transaction object when the storage location warranty period management information indicates a warehouse that is a storage location that manages the warranty period, and generates the movement data or the sales data including the common identification number and the common warranty period when the storage location warranty period management information indicates a store that is a storage location that does not manage the warranty period; 4. The inventory management device according to claim 2 or 3,

5. a data generating step of: a data generating unit, when a transfer input of a commercial transaction object is made, referring to a memory unit in which storage location warranty period management information indicating whether the storage location to be the transfer destination is a storage location that manages a warranty period, which is a period for guaranteeing the quality or operation of the commercial transaction object, and a common identification number and common warranty period that are commonly assigned when the storage location to be the transfer destination is a storage location that does not manage the warranty period, generating transfer data including the identification number and the warranty period of the commercial transaction object when the storage location to be the transfer destination indicated by the transfer input is indicated as a storage location that manages the warranty period in the storage location warranty period management information, and generating transfer data including the common identification number and the common warranty period stored in the memory unit when the storage location to be the transfer destination indicated by the transfer input is indicated as a storage location that does not manage the warranty period in the storage location warranty period management information; an output control step in which an output control unit outputs the generated movement data to an external device; An inventory control method having the following features.

6. Computer, a data generating unit which, when a transfer input for a commercial transaction object is made, refers to a memory unit which stores storage location warranty period management information indicating whether the storage location to be the transfer destination is a storage location that manages a warranty period, which is a period for guaranteeing the quality or operation of the commercial transaction object, and a common identification number and common warranty period which are commonly assigned when the storage location to be the transfer destination is a storage location that does not manage the warranty period, and generates transfer data including the identification number and the warranty period of the commercial transaction object when the storage location to be the transfer destination indicated by the transfer input is indicated in the storage location warranty period management information as a storage location that manages the warranty period, and generates transfer data including the common identification number and the common warranty period stored in the memory unit when the storage location to be the transfer destination indicated by the transfer input is indicated in the storage location warranty period management information as a storage location that does not manage the warranty period; functioning as an output control unit that outputs the generated movement data to an external device; Inventory management program.

Images