Information processing apparatus

Abstract

To provide a technique capable of easily managing commodities stored in a container.SOLUTION: An information processing apparatus includes at least one memory and at least one processor, and the at least one processor is configured to acquire first identification information for identifying a container containing a product, acquire second identification information for identifying the product contained in the container, and register the first identification information and the second identification information in association with each other.SELECTED DRAWING: Figure 14

Description

[Technical Field]

[0001] The present disclosure relates to an information processing device. [Background technology]

[0002] There are known techniques for managing goods using various codes. For example, there is a technique for identifying the destination of a package by reading a barcode attached to the package with a barcode reader. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2009-263041 Summary of the Invention [Problem to be solved by the invention]

[0004] According to the present disclosure, a technology can be provided that allows for easy management of products housed in containers. [Means for solving the problem]

[0005] An information processing device according to one embodiment of the present disclosure includes at least one memory and at least one processor, and the at least one processor acquires first identification information that identifies a container that contains a product, acquires second identification information that identifies the product contained in the container, and links and registers the first identification information and the second identification information. [Brief explanation of the drawings]

[0006] [Figure 1] FIG. 1 is a diagram for explaining delivery of merchandise from a delivery center to a retail store. [Figure 2] FIG. 10 is a diagram for explaining each cart placed in each area. [Figure 3] FIG. 10 is a diagram illustrating an example of a shelf tag. [Figure 4] FIG. 10 is a diagram illustrating an example of a carriage. [Figure 5] FIG. 2 is a diagram illustrating an example of an area board. [Figure 6] FIG. 10 is a diagram illustrating an example of a case. [Figure 7] 1 is a block diagram showing an example of the overall configuration of a merchandise management system; [Figure 8] FIG. 2 is a block diagram illustrating an example of a functional configuration of a management device. [Figure 9] FIG. 10 is a diagram showing an example of an inspection list. [Figure 10] FIG. 10 is a diagram showing an example of sales information. [Figure 11] FIG. 2 is a diagram illustrating an example of a product database. [Figure 12] FIG. 10 is a diagram illustrating an example of inventory information. [Figure 13] FIG. 10 is a diagram showing an example of a stocking list. [Figure 14] FIG. 2 is a block diagram illustrating an example of a functional configuration of a terminal. [Figure 15] FIG. 10 is a sequence diagram illustrating an example of a manual product registration process. [Figure 16] FIG. 10 is a sequence diagram illustrating an example of a list creation process. [Figure 17] FIG. 10 is a sequence diagram illustrating an example of a list checking process. [Figure 18] FIG. 10 is a sequence diagram illustrating an example of a pickup process. [Figure 19] FIG. 10 is a diagram illustrating an example of an operation screen that notifies that a product cannot be identified. [Figure 20] FIG. 10 is a diagram showing an example of an operation screen for requesting reading of a single item JAN code. [Figure 21] FIG. 10 is a diagram illustrating an example of an operation screen that displays product information. [Figure 22] FIG. 10 is a diagram showing an example of an operation screen that displays a single item JAN and a case JAN. [Figure 23] FIG. 10 is a diagram illustrating an example of an operation screen for notifying a result of association. [Figure 24] FIG. 10 is a diagram illustrating an example of an operation screen for notifying a confirmation result. [Figure 25] FIG. 10 is a diagram showing an example of an operation screen for notifying a deletion result. [Figure 26] FIG. 10 is a sequence diagram illustrating an example of a code registration process. [Figure 27] FIG. 10 is a sequence diagram illustrating an example of a product identification process. [Figure 28] FIG. 2 is a block diagram illustrating an example of a hardware configuration of a computer. DETAILED DESCRIPTION OF THE INVENTION

[0007] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. In this specification and drawings, components having substantially the same functional configurations are designated by the same reference numerals, and redundant description will be omitted.

[0008] <Terminology> In this specification, a "retail store" refers to a store that sells products to consumers. Examples of retail stores include, but are not limited to, supermarkets, drug stores, convenience stores, department stores, and home improvement stores. In this specification, a "distribution center" refers to a business that receives products from product manufacturers and ships them to retail stores. A distribution center is also called, for example, a logistics center. As used herein, a "product" is a product sold to consumers at a retail store. A product may be any product belonging to any category. In this specification, a "sales floor" is a place where products are sold to consumers. In this specification, a "backroom" is a place where inventory of products sold on the sales floor (in other words, inventory products to be supplied to the sales floor) is stored. A backroom is also called, for example, a backyard or a warehouse. Note that even when a backroom is attached to a retail store that has a sales floor, the retail store is said to have both a sales floor and a backroom. In this specification, "area" refers to the area in the backroom where the carts are placed. In this specification, a "cart" refers to a transport tool that can be moved while loaded with goods. A cart is also called, for example, a cart or a wagon. A cart moves within a backroom while loaded with goods, and the goods may be stored on the cart at the destination of the cart. For example, goods may be delivered from a distribution center to a retail store's backroom while loaded on the cart. In this specification, a "case" is a unit in which a single product is stored in a backroom, and is a container that contains multiple units of the single product. The multiple units of the single product may be the same product. In other words, for a certain product, one case for that product may contain multiple units of the same product. A case is also called collective packaging, etc. As an example, a case may be a cardboard box or other such box. A case may be any container that can contain products, and may be made of, for example, paper, resin, wood, etc. In the following explanation, "case" and "container" can be used interchangeably depending on the context. In this specification, a "display shelf" refers to a location on the sales floor of a retail store where products are displayed. Note that a display shelf is not limited to a shelf, and may be any fixture on which products are displayed. A display shelf may be a fixture with multiple shelves. A display shelf may have shelf tags attached to it that correspond to the products displayed on the display shelf. "Shelf tags attached to a display shelf" includes shelf tags that are fixedly attached to the display shelf, shelf tags that are detachably attached, and shelf tags that are built into the display shelf. The shelf tags may be attached to the side of the shelf of the display shelf that faces the sales aisle. In this specification, a "shelf label" refers to an information medium on which information for identifying a product displayed near the shelf label is displayed in correspondence with the shelf label. The information for identifying the product may be, for example, any image showing a code such as a barcode. The shelf label may also be a price tag on which information for identifying the product is displayed in addition to the product name and price of the product displayed near the shelf label. In this specification, "information for identifying a product" refers to information that can uniquely identify a product (product information such as product name), and may be any image such as a code. Information for identifying a product may be displayed on a shelf tag or on the product itself.

[0009] In this specification, a "code" refers to any code in any format that encodes identification information that identifies at least one of a product or a case that contains the product. The code may be, for example, a barcode, a two-dimensional code, or a color code. Examples of the code format include an EAN (European Article Number) code such as a JAN (Japanese Article Number) code, an ITF (Interleaved Two of Five) code, a UPC (Universal Product Code), or a GTIN (Global Trade Item Number). The code may include multiple types of codes with different formats. For example, multiple types of codes with different formats may include at least JAN code and ITF code. Note that "different formats" may include "different standards," "different coding systems," and "different rules for encoding into codes." Depending on the context, a code may be interpreted as a symbol. For example, the code may include a code that identifies a product when the product is taken out of a case and sold individually (for example, a JAN code for single item sales). For example, the code may include a code that identifies a product when the product is sold in the case that contains it (for example, a JAN code for case sales). A JAN code for single item sales is also called a "single item JAN." A JAN code for case sales is also called a "case JAN." For example, the code may include a code that identifies a case in logistics (for example, an ITF code). An ITF code is also simply called "ITF." In this specification, "linking" includes both the concepts of direct linking and indirect linking. "Directly linking and registering A and B" means "making it possible to directly reference A from B and / or B from A (for example, registering A and B in items a and b, respectively, of a single record in a database)." "Indirectly linking and registering A and B" means "making it possible to indirectly reference A from B and / or B from A by referencing other items (for example, registering A and C in items a and c, respectively, of a single record in a database, and registering C and B in items c and b, respectively, of a single record in a different database)."

[0010] <Summary> Figure 1 is a diagram for explaining the delivery of goods from a distribution center to a retail store. Note that the number of retail stores, distribution centers, areas, carts, terminals, and employees shown in Figure 1 are examples and are not limited to these.

[0011] Each retail store (retail store a and retail store b in the example of Figure 1) receives goods delivered from one or more distribution centers. For example, retail store a receives goods delivered from multiple distribution centers (distribution center a and distribution center b in the example of Figure 1), and retail store b receives goods delivered from a single distribution center (distribution center b in the example of Figure 1).

[0012] A retail store includes a sales floor and a back room. The retail store has one or more employees 21. The employees 21 operate terminals 20 to perform various tasks related to the operation of the retail store. The employees 21 may be referred to as "users" in the sense that they use at least a portion of the product management system 1000, which will be described later, such as the terminals 20. The term "user" is not limited to the employees 21, but may also include people who operate at least a portion of the product management system 1000, which will be described later, such as the terminals 20. Below, an example of use of the product management system 1000 by an employee 21 will be described as an example of use of the product management system 1000 by a user.

[0013] A backroom has one or more areas. In the example of FIG. 1, retail store A has area A, area B, and so on. For example, an area is a predetermined section in the backroom (for example, a section separated by a line drawn on the floor of the backroom). Note that instead of determining sections in advance, an area may be defined as a location where a predetermined number of carts are placed.

[0014] Each area has one or more trolleys. In the example of Figure 1, area A has trolley 1, trolley 2, etc., and area B has trolley 3, trolley 4, etc.

[0015] Each cart is loaded with one or more products. For example, one or more identical products are contained in one case (e.g., a cardboard box), and one or more cases are loaded on the cart.

[0016] Note that a certain product may be in multiple areas. For example, product a may be in area A and area B. Also, a certain product may be in multiple carts. For example, product a may be in cart 1, cart 2, cart 3, and cart 4.

[0017] Products delivered from the distribution center on trucks or the like are delivered from the trucks or the like to the back room through a product entrance. After that, as needed, employees 21 supply the products from the back room to the sales floor through the entrance connecting the back room and the sales floor.

[0018] FIG. 2 is a diagram for explaining each cart placed in each area. One or more carts are placed in each area. FIG. 2 shows two carts placed in each of three areas. Note that the shapes and types of the carts are merely examples, and any shape and type may be used.

[0019] 3 is a diagram showing an example of a shelf tag. In a sales floor of a retail store, shelf tags are attached to shelves on which products are displayed. The shelf tags may be electronic or paper.

[0020] The shelf tag displays the product name and price of the product placed near the shelf tag. Furthermore, the shelf tag displays an arbitrary code (e.g., a barcode) that encodes information (e.g., a JAN code, which is identification information specific to the product) that can uniquely identify the product (product information such as the product name). In addition to this code, the shelf tag may also display a code (e.g., CODE128) to identify the shelf tag.

[0021] 4 is a diagram showing an example of a cart, which is placed in the back room of a retail store and on which one or more cases containing one or more products are loaded.

[0022] Each trolley is equipped with an information medium containing a trolley ID. The information medium may be, for example, a paper medium or an electronic medium such as an IC tag. For example, the information medium containing the trolley ID is a medium that displays a character string of the trolley ID and a code encoding the trolley ID. The information medium may be, for example, a plate, a sticker, a badge, or the like. The position where the information medium is attached to the trolley is not limited to a specific position. The trolley may be delivered with the information medium containing the trolley ID attached. Furthermore, at a distribution center, products loaded on multiple trolleys may be transferred onto a single trolley for delivery. In this case, the single trolley after transfer may be delivered with information media containing the trolley IDs of the multiple trolleys before transfer attached. That is, the delivered trolley may be equipped with information media containing one or more trolley IDs.

[0023] 4 shows an example in which an area board, which is an example of an information medium, is attached to a dolly. As an example, the area board may be attached to the top of the dolly.

[0024] 5 is a diagram showing an example of an area board. When a cart loaded with products is delivered to the back room, employee 21 attaches the area board to the cart.

[0025] The area board is a medium that displays identification information (area ID) that identifies an area, identification information (board ID) that identifies an area board, and a code that encodes information that can uniquely identify the area board within the backroom. The area board may be, for example, a plate, a sticker, a badge, or the like. In the example of FIG. 5, the area ID is "A" and the board ID is "2". The area board displays the area ID and board ID so that the employee 21 can read them. The code displayed on the area board may be, for example, information that indicates both the area ID and the board ID, or information that encodes information that indicates a board ID that is linked to the area ID in advance and does not overlap between areas.

[0026] The area ID and board ID of the area board attached to each cart are linked to that cart. An employee 21 searching for a desired product can use the area ID and board ID of the area board attached to each cart to find the cart carrying the desired product in the back room.

[0027] It is preferable that the board ID can be uniquely identified within the backroom (i.e., the board ID does not overlap between areas) from the viewpoint of searching for the area board by the employee 21. However, as long as the area board can be uniquely identified within the backroom from both the area ID and the board ID, the board ID may overlap between areas.

[0028] The area board may be colored in a color corresponding to the area so that the employee 21 can easily identify the area. In the example of Fig. 5, the frame of the area board is colored in a color corresponding to the area.

[0029] 6 is a diagram showing an example of a case. One or more types of codes are displayed on the case containing the product. For example, the codes may be displayed by printing the code on the surface of the case or by attaching a sticker with the code printed on it. For example, the multiple types of codes may include at least one of the case JAN and ITF.

[0030] Fig. 6(A) is a diagram showing an example of a case where multiple types of codes are displayed on the same side. Fig. 6(B) is a diagram showing an example of a case where multiple types of codes are displayed on different sides. Fig. 6(C) is a diagram showing an example of a case where some of the multiple types of codes (for example, only one type) are displayed. When multiple types of codes are displayed on a case as shown in Fig. 6, the display position of each code and the type of code to be displayed may be determined arbitrarily.

[0031] [Embodiment] One embodiment of the present disclosure is a product management system that manages products. In this embodiment, the products to be managed may be products sold to consumers in a store such as a retail store. The products may be stored in a case and delivered to the store. The products may be removed from the case and sold individually in the sales area of ​​the store, or may be sold in a case that stores multiple products.

[0032] <Overall structure of product management system> The overall configuration of the product management system according to this embodiment will be described with reference to Fig. 7. Fig. 7 is a block diagram showing an example of the overall configuration of the product management system.

[0033] 7, the product management system 1000 includes a management device 10 and a terminal 20. The product management system 1000 may also include a delivery management system 30 and a sales management system 40. The management device 10, the terminal 20, the delivery management system 30, and the sales management system 40 may be connected to each other via a communication network such as a local area network (LAN) or the Internet so that data can be communicated with each other.

[0034] The management device 10 is an example of an information processing device such as a personal computer, workstation, or server that manages products sold in a store. The management device 10 may manage products sold in a retail chain that includes multiple stores. The management device 10 may manage products on a store-by-store basis, or on a retail chain-by-retail chain basis. For example, the management device 10 may be installed in a backroom of a store, at a headquarters that oversees the retail chain, or at a remote location such as a data center that can communicate with a store or the headquarters via a network.

[0035] The terminal 20 is an example of an information processing device operated by a store employee 21. For example, the terminal 20 may be a portable information processing terminal such as a smartphone, a tablet terminal, or a laptop personal computer. For example, the terminal 20 may be a mobile terminal such as a handy terminal specialized for operating a retail store. The terminal 20 may include an input device such as a touch screen or buttons for receiving information input, and a display device for displaying information. The terminal 20 may include a reading device such as a barcode reader that can read codes. The terminal 20 may include an imaging device such as a camera.

[0036] The delivery management system 30 is an example of an information processing device or information processing system that manages the delivery of products. The delivery management system 30 may manage deliveries from one or more delivery centers to one or more stores. As an example, the delivery management system 30 may be installed in one of the delivery centers, the headquarters of a retail chain, or a remote location such as a data center that can communicate with the delivery center or the headquarters via a network.

[0037] The delivery management system 30 transmits an inspection list to the management device 10. The inspection list is electronic data that records a list of products delivered from a delivery center to a store. As an example, the inspection list may be data that includes product information about the products delivered to the store, the number of the products, and information about the carts that carry the products.

[0038] The delivery management system 30 may transmit the inspection list to the management device 10 before the products are actually delivered. The delivery management system 30 may transmit the inspection list to the management device 10 after the products are actually delivered.

[0039] The inspection list may be input into the delivery management system 30 by a user of the delivery management system 30. The user of the delivery management system 30 may be, for example, an employee of a delivery center or a system administrator of the delivery management system 30.

[0040] The sales management system 40 is an example of an information processing device or information processing system that manages the sale of products in a store. As an example, the sales management system 40 may be a point of sale (POS) system. As an example, the sales management system 40 may be installed in a back room of a store, at the headquarters of a retail chain, or at a data center that can communicate with the store or the headquarters via a network.

[0041] The sales management system 40 stores sales information about products sold in the store. The sales information is electronic data that records information about products sold in the store. The sales information may include information about products that are not currently sold in the store. The sales information may include information about products that have been sold in the past or products that are scheduled to be sold in the future. The sales information may be data that includes product information about products sold in the store and price information for those products.

[0042] The sales information may be input in advance into the sales management system 40 by a user of the sales management system 40. The user of the sales management system 40 may be, for example, a store employee, a supervisor at headquarters, or a system administrator of the sales management system 40. At least a part of the sales information may be generated based on the inspection list.

[0043] The overall configuration of the product management system 1000 shown in Figure 7 is just one example, and various system configuration examples are possible depending on the application and purpose. The product management system 1000 may be configured from one or more devices. The devices included in the product management system 1000 may be a system configured from multiple devices. Each function included in the product management system 1000 may be realized by any device that makes up the system. Each component included in the product management system 1000 may be included in any device that makes up the system.

[0044] The product management system 1000 may include multiple units of one or more of the management device 10, terminal 20, delivery management system 30, and sales management system 40. The management device 10, delivery management system 30, or sales management system 40 may be realized as a system including multiple computers, or may be realized as a cloud computing service. Two or more of the management device 10, terminal 20, delivery management system 30, and sales management system 40 may be realized as standalone computers. The division of devices such as the management device 10, terminal 20, delivery management system 30, and sales management system 40 shown in Figure 7 is one example.

[0045] <Stocking work> The employee 21 performs various tasks performed on the sales floor or in the back room of the store using the terminal 20. As an example, the employee 21 may use the terminal 20 to perform stocking tasks.

[0046] Stocking work is the work of displaying inventory items stored in the backroom on the sales floor. Stocking work may include, for example, manual product registration, list creation, picking up, and displaying products. The work performed in stocking work is not limited to these, and other work may be included, or some work may not be included.

[0047] Employee 21 uses terminal 20 to perform various tasks related to stocking operations. Terminal 20 can communicate with merchandise management system 1000 via a communication network, such as wireless communication. Employee 21 uses terminal 20 after logging in to it. That is, terminal 20 becomes available for use after user authentication. This allows merchandise management system 1000 to store historical information related to each task performed by employee 21 using terminal 20, in association with information identifying employee 21 (e.g., employee ID, etc.). Logging in to terminal 20 may be performed by reading the employee ID code printed on employee 21's employee ID card with a reading device on terminal 20, or by inputting the employee ID into terminal 20 via an input device on terminal 20, or the like.

[0048] <Manual product registration> Manual product registration is the task of linking and registering the carts placed in each area with the products loaded on those carts. When products are delivered to the backroom, employee 21 loads the cases containing those products onto one of the carts. After loading the cases onto the cart, employee 21 uses the reading device of terminal 20 to read the codes displayed on the area board and the codes displayed on the cases. Employee 21 may input the number of loaded products into terminal 20.

[0049] The terminal 20 sends a linking request including the two read codes and the number of products to the product management system 1000. The product management system 1000 identifies the product information and storage location (area and cart) based on the codes included in the linking request. The product management system 1000 also links the product information, storage location, and number of products together and stores this as inventory information in the storage device of the management device 10. The number of products may be obtained from the inspection list. Furthermore, the product management system 1000 links history information indicating that the products were loaded onto the cart with information indicating the employee 21 who performed the manual product registration (e.g., employee ID, etc.) and stores this in the storage device of the management device 10. In this way, manual product registration can be said to be the process of registering products by linking them with their storage locations.

[0050] <<Create a list>> List creation is the task of creating a list of products that need to be stocked (hereinafter also referred to as a "stocking list"). Employee 21 patrols the sales floor and identifies products that need to be stocked. Products that need to be stocked may include, for example, products that are out of stock or products that are likely to be out of stock. Products that are out of stock are products that have been sold out and are no longer on the shelves. Products that are likely to be out of stock are products that have been put on the shelves and are in a state where there are only a few products left, and there is a high possibility that the shelves will run out of products in the near future.

[0051] When employee 21 identifies an item that needs to be put out, he or she uses a reading device on terminal 20 to read a code that uniquely identifies the item (for example, a code displayed on a shelf tag or a code displayed on the item itself). Employee 21 also inputs the number of items to be put out into terminal 20. The number of items to be put out may be the number of cases that contain the items.

[0052] The terminal 20 transmits a registration request including the read code and the input quantity to the product management system 1000. The product management system 1000 identifies the product information based on the code included in the registration request. Hereinafter, identifying the product information may be referred to as identifying the product. The product management system 1000 also identifies a storage location linked to the identified product information. The product management system 1000 then links the product information, the storage location, and the number of items to be put out, and registers them in a stocking list. The product management system 1000 also stores history information indicating that the item has been registered in the stocking list in the storage device of the management device 10, linking it with information indicating the employee 21 who created the list (e.g., an employee ID, etc.).

[0053] <<Pickup>> Pickup is the task of loading out items registered on the stocking list from the back room. In response to operations by employee 21, terminal 20 obtains the stocking list from product management system 1000 and displays it on a display device. Employee 21 moves to the storage location of the items indicated on the stocking list. Employee 21 removes the number of items to be put out from the storage location indicated on the stocking list. Note that product management system 1000 may be configured so that the stocking list can be shared between different terminals 20 used by multiple employees 21. As an example, the stocking list created on a first terminal 20 may be configured so that it can be used (referenced) on a second terminal 20 to pick up items.

[0054] When employee 21 has unloaded the number of products to be put out from the storage location, either individually or in cases, employee 21 inputs into terminal 20 that the unloading is complete. For example, employee 21 may input into terminal 20 that the unloading of the products is complete by reading a code displayed on the product or a code displayed on the product case using a reading device on terminal 20. For example, the product putting list displayed on the display device of terminal 20 may include a "Unloading Completed" button for each product, and employee 21 may input into terminal 20 that the unloading of the product is complete by pressing the "Unloading Completed" button for the product that has been unloaded.

[0055] The terminal 20 transmits a cancellation request to the product management system 1000 for the product that has been picked up. The product management system 1000 removes the product information indicated in the cancellation request from the stocking list. The product management system 1000 also subtracts the number of items picked up from the number of items stored in the inventory information. Furthermore, the product management system 1000 stores history information indicating that the product has been picked up from the storage location in the storage device of the management device 10, linking it with information indicating the employee 21 who picked up the product (e.g., an employee ID, etc.).

[0056] On the other hand, if there are not enough items left in the backroom to be put out (i.e., the item to be put out is out of stock), employee 21 inputs into terminal 20 that the item is out of stock. For example, the stocking list displayed on the display device of terminal 20 may include an "out of stock" button for each item, and employee 21 may input into terminal 20 that the item is out of stock by pressing the "out of stock" button for the out-of-stock item. Terminal 20 notifies product management system 1000 of the item that could not be put out. Product management system 1000 registers in inventory information that the notified item is out of stock. Furthermore, product management system 1000 stores history information indicating that the item is out of stock in the storage device of management device 10, linking it to information indicating employee 21 who picked up the item (e.g., employee ID, etc.).

[0057] ≪Product display≫ Product display is the work of displaying products that have been unloaded from the backroom on the sales floor. In the pickup work, employee 21 transports the products that have been unloaded from the backroom to the sales floor. Once the products have been transported to the sales floor, employee 21 displays the transported products on the display shelves that have been allocated space for displaying those products.

[0058] <Product Database> In stocking operations, employee 21 identifies product information based on various codes read by the reading device of terminal 20. Codes read by the reading device include, for example, codes displayed on shelf tags, codes displayed on the products themselves, or codes displayed on cases. To enable product information to be identified from these codes, product management system 1000 uses a product database.

[0059] The product database is a database that links product information about products sold in a store with multiple types of codes used to identify the product information. In this embodiment, the codes used to identify the product information may include a code that encodes identification information (product ID) that identifies the product and a code that encodes identification information (case ID) that identifies a case that contains multiple products. In other words, the product database may be a database that links product information, product IDs, and case IDs. Specifically, the product database may be a database that stores records that include product names, individual item JANs, case JANs, and ITFs. The product database may also be a database that links unique product codes as product IDs to case IDs in addition to individual item JANs. The product database may also link codes other than case IDs to product information.

[0060] In conventional stocking operations, it has been difficult to obtain information linking product IDs with case IDs. This has required the system administrator of the product management system 1000 to manually maintain the product database. Manual work by the system administrator can result in data that is not linked to product IDs and case IDs due to missing registrations, etc. If product IDs and case IDs are not linked, product information cannot be identified based on the case ID, and operations that use that function cannot be performed.

[0061] The present embodiment aims to enable easy management of products housed in cases. In this embodiment, a code displayed on the case and a code displayed on the product are read, and a product ID and a case ID are linked and registered based on these codes. In one aspect, according to this embodiment, employee 21 simply uses a reading device on terminal 20 in the backroom to read the code displayed on the case and the code displayed on the product, and the product ID and case ID can be linked and registered in the product database, making it easy to manage products housed in cases.

[0062] <Functional configuration> The functional configuration of the product management system 1000 will be described with reference to FIGS.

[0063] ≪Management device≫ Fig. 8 is a block diagram showing an example of the functional configuration of the management device. As shown in Fig. 8, management device 10 includes product information storage unit 101, inventory information storage unit 102, stocking list storage unit 103, inspection list acquisition unit 110, sales information acquisition unit 120, request reception unit 130, product information identification unit 140, product information acquisition unit 150, product information management unit 160, inventory information management unit 170, and stocking list management unit 180. By executing a management program installed in advance, management device 10 functions as product information storage unit 101, inventory information storage unit 102, stocking list storage unit 103, inspection list acquisition unit 110, sales information acquisition unit 120, request reception unit 130, product information identification unit 140, product information acquisition unit 150, product information management unit 160, inventory information management unit 170, and stocking list management unit 180.

[0064] The product information storage unit 101 stores a product database that stores product information. The product database is a database that manages information about products sold in stores. The product information may include, for example, the name of the product and identification information (product ID) that identifies the product. The product database may store a code (product ID) displayed on the product and a code (case ID) displayed on the case that contains the product, linked to each other. For example, the product ID may be a single item JAN. For example, the case ID may be at least one of the case JAN and ITF. The case ID may include multiple codes. For example, the case ID may include both the case JAN and ITF.

[0065] The inventory information storage unit 102 stores inventory information. The inventory information is information about inventory items stored in the backroom of the store. The inventory information may include product information about the inventory items, storage location information for the inventory items, and quantity information for the inventory items. As an example, the storage location information may include at least one of an area ID or a board ID. The quantity information may include at least one of the number of cases or the quantity of a single item.

[0066] A stocking list is stored in the stocking list storage unit 103. The stocking list is information about products to be stocked in the sales floor. The stocking list may include product information about the products to be stocked, storage location information for the products, and the number of products to be stocked.

[0067] A stocking list may be created for each product category. A stocking list may be created for each terminal 20. A stocking list may be created for each employee 21. As an example, a category may be a type of product. A type of product may be arbitrarily determined depending on the products sold in the store. As an example, a type of product may include beverages, confectioneries, seasonings, etc. As an example, a category may be a section based on the layout of the sales floor.

[0068] The inspection list acquisition unit 110 acquires the inspection list. The inspection list acquisition unit 110 may acquire the inspection list from the delivery management system 30. The inspection list acquisition unit 110 may receive the inspection list sent by the delivery management system 30. The inspection list acquisition unit 110 may request the inspection list from the delivery management system 30. The inspection list acquisition unit 110 may read out the inspection list stored in the delivery management system 30. The inspection list acquisition unit 110 may acquire the inspection list from another information processing device or information processing system different from the delivery management system 30. The inspection list acquisition unit 110 may accept the inspection list input by the user of the management device 10.

[0069] The sales information acquisition unit 120 acquires sales information. The sales information acquisition unit 120 may acquire sales information from the sales management system 40. The sales information acquisition unit 120 may receive sales information transmitted by the sales management system 40. The sales information acquisition unit 120 may request sales information from the sales management system 40. The sales information acquisition unit 120 may read out sales information stored in the sales management system 40. The sales information acquisition unit 120 may acquire sales information from an information processing device or information processing system other than the sales management system 40. The sales information acquisition unit 120 may accept sales information input by a user of the management device 10.

[0070] The request receiving unit 130 receives various requests from the terminal 20. The request receiving unit 130 may receive a request to identify product information. The request receiving unit 130 may receive a request to obtain product information. The request receiving unit 130 may receive a request to link a product with a case. The request receiving unit 130 may receive a request to link a product with a storage location. The request receiving unit 130 may receive a request to register a stocking list. The request receiving unit 130 may receive a request to confirm a stocking list. The request receiving unit 130 may receive a request to send a stocking list. The request receiving unit 130 may receive a request to cancel a stocking list.

[0071] The product information identification unit 140 identifies product information. The product information identification unit 140 may identify product information in response to a product information identification request received by the request receiving unit 130. The product information identification unit 140 may identify product information based on a product database stored in the product information storage unit 101. The product information identification unit 140 may extract product information linked to a case ID included in the acquisition request from the product database based on the case ID included in the acquisition request. The product information identification unit 140 may extract product information to which the product ID is set from the product database based on the product ID included in the acquisition request.

[0072] The product information acquisition unit 150 acquires product information. The product information acquisition unit 150 may acquire product information in response to a product information acquisition request received by the request reception unit 130. The product information acquisition unit 150 may acquire product information based on sales information acquired by the sales information acquisition unit 120. Based on a product ID included in the acquisition request, the product information acquisition unit 150 may extract product information to which the product ID is set from the sales information.

[0073] The product information management unit 160 manages product information. The product information management unit 160 may manage product information using a product database stored in the product information storage unit 101. The product information management unit 160 may register product information in the product database. The product information management unit 160 may update product information registered in the product database. The product information management unit 160 may delete product information registered in the product database.

[0074] The product information management unit 160 may update the product information in response to the linking request received by the request receiving unit 130. The product information management unit 160 may link the product ID and the case ID in the product database in response to the request to link the product and the case. The product information management unit 160 may link the case ID to the product information in which the product ID included in the request to link the product and the case is set, and register the case ID in the product database.

[0075] The inventory information management unit 170 manages inventory information. The inventory information management unit 170 may manage inventory information stored in the inventory information storage unit 102. The inventory information management unit 170 may register inventory information regarding products delivered to the backroom based on the inspection list acquired by the inspection list acquisition unit 110. The inventory information management unit 170 may update the quantity of items in the inventory information in response to a request to cancel the stockout list. The inventory information management unit 170 may delete inventory information regarding products that are out of stock.

[0076] The stocking list management unit 180 manages the stocking list. The stocking list management unit 180 may manage the stocking list stored in the stocking list storage unit 103. The stocking list management unit 180 may register an item to be put out on the stocking list in response to a request to register the stocking list. The stocking list management unit 180 may transmit a confirmation result of the stocking list in which a specific item is registered in response to a request to confirm the stocking list. The stocking list management unit 180 may transmit the stocking list to the terminal 20 in response to a request to send the stocking list. The stocking list management unit 180 may remove an item to be put out from the stocking list in response to a request to remove the stocking list.

[0077] FIG. 9 is a diagram showing an example of an inspection list. As shown in FIG. 9, the inspection list may include, for example, a truck ID, a delivery date, a delivery batch ID, a product name, a product ID, and the number of loaded boxes. The truck ID is an example of information about the truck. The product name and product ID are examples of product information. The number of loaded boxes is an example of the number of products.

[0078] The dolly ID is identification information that identifies a dolly delivered from a distribution center to a store. Note that one dolly may be loaded with one type of product, or may be loaded with multiple types of products. Also, a dolly may be loaded with a case containing multiple products.

[0079] The delivery date is the date on which the product is delivered from the distribution center to the store. The delivery batch ID is identification information that identifies the delivery schedule. The product name is the name of the product loaded on the cart. The product ID is identification information that identifies the product loaded on the cart. As an example, the product ID may be the JAN of a single item. The number of boxes loaded is the number of cases loaded on the cart.

[0080] Fig. 10 is a diagram showing an example of sales information. As shown in Fig. 10, the sales information may include a category, a product name, a product ID, a price, etc. The product name and product ID are examples of product information. The price is an example of price information for the product.

[0081] The category is information indicating the category of the product sold at the store. The product name is the name of the product sold at the store. The product ID is identification information that identifies the product sold at the store. As an example, the product ID may be the JAN of a single item. The price may be the selling price of the product at the store.

[0082] FIG. 11 is a diagram showing an example of a product database. As shown in FIG. 11, the product database may include product names, product IDs, case IDs, etc. The product names and product IDs are examples of product information. The product ID may be, for example, a single item JAN. The case ID may include, for example, a case JAN and ITF.

[0083] The product database may contain records in which a product ID and a case ID are not linked. For example, the product database may contain records in which a product ID is set but a case ID is not set. If the case ID contains multiple types of codes, a record in which one or more of the multiple types of codes are not set may be treated as a record in which a case ID is not set.

[0084] The records shown in Figure 11 with the product names "Product C," "Product E," and "Product F" are examples of records for which a case ID is not set. For the record with the product name "Product C," neither the case JAN nor the ITF is set. For the record with the product name "Product E," the case JAN is set, but the ITF is not. For the record with the product name "Product F," the ITF is set, but the case JAN is not set.

[0085] FIG. 12 is a diagram showing an example of inventory information. As shown in FIG. 12, the inventory information may include a product name, a product ID, a cart ID, a board ID, an area ID, the number of cases, and the number of individual items. The product name and product ID are examples of product information. The cart ID, board ID, and area ID are examples of storage location information. The number of cases and the number of individual items are examples of the number of products.

[0086] FIG. 13 is a diagram showing an example of a stocking list. As shown in FIG. 13, the stocking list may include a product name, a product ID, a board ID, an area ID, and the number of items to be stocked. The product name and product ID are examples of product information. The board ID and area ID are examples of storage location information. The number of items to be stocked is an example of the number of items to be stocked.

[0087] Terminal Fig. 14 is a block diagram showing an example of the functional configuration of a terminal. As shown in Fig. 14, the terminal 20 includes a case code reading unit 210, an individual item code reading unit 220, a storage location acquisition unit 230, an identification request unit 240, an acquisition request unit 250, a linking request unit 260, a list registration unit 270, a list display unit 280, and a list release unit 290. By executing a terminal program installed in advance, the terminal 20 functions as the case code reading unit 210, the individual item code reading unit 220, the storage location acquisition unit 230, the identification request unit 240, the acquisition request unit 250, the linking request unit 260, the list registration unit 270, the list display unit 280, and the list release unit 290.

[0088] The case code reading unit 210 uses a reading device to read a code displayed on the case. For example, the case code reading unit 210 may read at least one of the case JAN or ITF. The case code reading unit 210 may sequentially read the case JAN and ITF in a predetermined order or in any order. The case code reading unit 210 may simultaneously read the case JAN and ITF. The case code reading unit 210 may also read other codes displayed on the case. The case code reading unit 210 may acquire a case ID by recognizing the read code.

[0089] The single item code reading unit 220 uses a reading device to read a code displayed on a single item. As an example, the single item code reading unit 220 may read a single item JAN number. The single item code reading unit 220 may also read other codes displayed on the item. The single item code reading unit 220 may acquire a product ID by recognizing the read code.

[0090] The storage location acquisition unit 230 acquires product storage location information. The storage location acquisition unit 230 may read a code displayed on an area board using a reading device. The storage location acquisition unit 230 may read at least one of an area ID or a board ID. The storage location acquisition unit 230 may sequentially read the area ID and the board ID in a predetermined order or an arbitrary order. The storage location acquisition unit 230 may simultaneously read the area ID and the board ID. The storage location acquisition unit 230 may acquire at least one of an area ID or a board ID by recognizing the read code. The storage location acquisition unit 230 may accept at least one of an area ID or a board ID input by the employee 21 via an input device.

[0091] The storage location acquisition unit 230 may use a reading device to read the cart ID from an information medium attached to the cart. The storage location acquisition unit 230 may also accept the cart ID input by the employee 21 via an input device.

[0092] The identification request unit 240 requests the management device 10 to identify product information. The identification request unit 240 may transmit the product information identification request to the management device 10. The product information identification request may include the code read by the case code reading unit 210 (i.e., the case ID). The product information identification request may include the code read by the single item code reading unit 220 (i.e., the product ID).

[0093] The identification request unit 240 receives the identification result from the management device 10. The identification request unit 240 may present the identification result to the employee 21. As an example, the identification request unit 240 may display the identification result received from the management device 10 on a display. The identification result may include information indicating whether the identification of the product information was successful or unsuccessful. If the management device 10 is able to identify the product information, the identification result may include the identified product information. If the management device 10 is unable to identify the product information, the identification result may not include the product information.

[0094] The identification request unit 240 may notify the employee 21 whether the identification of the product information was successful or unsuccessful. For example, the identification request unit 240 may display a notification regarding the identification result on a display. If the identification of the product information is unsuccessful, the notification may include, for example, a notification that the product information is not registered. In this case, the notification may also include, for example, a statement requesting that the code displayed on the product be read.

[0095] The identification request unit 240 may have the employee 21 confirm the product information included in the identification result. As an example, the identification request unit 240 may display the product information included in the identification result on a display. The identification request unit 240 may confirm the identified product information in response to a confirmation operation by the employee 21.

[0096] The acquisition request unit 250 requests the management device 10 to acquire product information. The acquisition request unit 250 may transmit the request to acquire product information to the management device 10. The request to acquire product information may include the code read by the single item code reading unit 220 (i.e., the product ID).

[0097] The acquisition request unit 250 receives the acquisition results from the management device 10. The acquisition request unit 250 may present the acquisition results to the employee 21. As an example, the acquisition request unit 250 may display the acquisition results received from the management device 10 on a display. The acquisition results may include the acquired product information.

[0098] The acquisition request unit 250 may have the employee 21 confirm the product information included in the acquisition result. As an example, the acquisition request unit 250 may display the product information included in the acquisition result on a display. The acquisition request unit 250 may confirm the acquired product information in response to a confirmation operation by the employee 21.

[0099] The linking request unit 260 transmits a linking request to the management device 10. The linking request unit 260 may transmit a request for linking a product with a case to the management device 10. The request for linking a product with a case may include the code read by the single item code reading unit 220 (i.e., the product ID) and the code read by the case code reading unit 210 (i.e., the case ID).

[0100] The request to link a product with a case is information or a signal that requests the management device 10 to link the product ID with the case ID and register them in the product database. In other words, the linking request unit 260 may link the product ID with the case ID and register them in the product database.

[0101] The linking request unit 260 may transmit a request to link a product with a storage location to the management device 10. The request to link a product with a storage location is information or a signal that requests the management device 10 to link the product ID with storage location information (i.e., area ID and board ID) and register them in the inventory information. In other words, the linking request unit 260 may link the product ID with the area ID and board ID and register them in the inventory information.

[0102] If the identification request unit 240 is able to identify product information, the request for linking the product with the storage location may include the product ID included in the identification result and the code (i.e., area ID and board ID) read by the storage location acquisition unit 230. If the acquisition request unit 250 is able to acquire product information, the request for linking the product with the storage location may include the code (i.e., product ID) read by the single item code reading unit 220 and the code (i.e., area ID and board ID) read by the storage location acquisition unit 230.

[0103] The list registration unit 270 transmits a request to register a stock list to the management device 10. The request to register a stock list includes identification information for identifying the stock list, the product IDs of the products to be stocked, and the number of products to be stocked.

[0104] The list registration unit 270 may allow the employee 21 to select a stocking list. The list registration unit 270 may display a list of stocking lists on a display so that the list can be selected. The list registration unit 270 may select a stocking list in response to a selection operation by the employee 21, and include identification information that identifies the selected stocking list in the registration request.

[0105] The list registration unit 270 may use a reading device to read a code indicating a product to be put out. The code indicating a product to be put out may be, for example, a code displayed on a shelf tag or a code displayed on the product. The list registration unit 270 may obtain the product ID of the product to be put out by recognizing the code read using the reading device.

[0106] The list registration unit 270 may have the employee 21 input the number of items to be put out. The list registration unit 270 may accept the number of times a code indicating a product to be put out has been read as the number of items to be put out. The list registration unit 270 may include the number of items to be put out input into the terminal 20 by the employee 21 in the registration request.

[0107] The list registration unit 270 may enable a function of registering a product whose JAN code has been read by a reading device as a product to be put out. Based on the enablement of this function, the terminal 20 may set the reading device to not read any other types of codes other than JAN codes.

[0108] The list display unit 280 transmits a request to the management device 10 to send a stocking list. The list display unit 280 may present the stocking list received from the management device 10 to the employee 21. The list display unit 280 may display the stocking list on a display. The list display unit 280 may display the storage locations of the products shown in the stocking list, and when the employee 21 arrives at the storage location, may display product information about the products to be stocked and the number of products to be stocked.

[0109] As an example, the list display unit 280 may display the stocking list in stages in the order of area, cart, and product. That is, the list display unit 280 may first display the area ID, and when the employee 21 arrives at the area, display the cart ID of the cart placed in the area, and when the employee 21 arrives on the cart, display the stocking list for the products loaded on the cart. The arrival at the storage location may be input into the terminal 20 by the employee 21 pressing an "Arrival" button displayed on the display. The arrival at the storage location may also be detected automatically based on the location information of the terminal 20.

[0110] The list canceling unit 290 transmits a request to cancel the stocking list to the management device 10. The list canceling unit 290 may transmit the request to cancel the stocking list to the management device 10 in response to a completion operation by the employee 21. The completion operation may be, for example, an operation of pressing a "Pickup Complete" button displayed on the display of the terminal 20. The request to cancel the stocking list may include the product ID of the product to be stocked for which the completion operation has been performed.

[0111] <Product management method flow> 15 to 18, a product management method executed by the product management system 1000 will be described. In this embodiment, the product management method may include, for example, a manual product registration process (see FIG. 15), a list creation process (see FIG. 16), a list confirmation process (see FIG. 17), and a pickup process (see FIG. 18).

[0112] <Manual product registration process> 15 is a sequence diagram showing an example of manual product registration processing. The manual product registration processing is processing executed by the product management system 1000 when the employee 21 performs manual product registration work. That is, the product management system 1000 provides a function for linking and registering products stored in a case with their storage locations.

[0113] In step S101, the inspection list acquisition unit 110 of the management device 10 acquires the inspection list from the delivery management system 30. The inspection list acquisition unit 110 sends the acquired inspection list to the inventory information management unit 170.

[0114] In step S102, the storage location acquisition unit 230 of the terminal 20 requests the employee 21 to read the code displayed on the area board. In response to an operation by the employee 21, the storage location acquisition unit 230 uses a reading device to read the code displayed on the area board. The storage location acquisition unit 230 recognizes the read code and acquires storage location information. The storage location acquisition unit 230 sends the acquired storage location information to the linking request unit 260.

[0115] In step S103, the case code reading unit 210 of the terminal 20 requests the employee 21 to read the code displayed on the case. The case whose code is read in step S103 may be a case loaded on a cart equipped with an area board whose storage location information was acquired in step S102. The case code reading unit 210 uses a reading device to read the code displayed on the case in response to an operation by the employee 21. The case code reading unit 210 recognizes the read code and acquires a case ID. In other words, the case code reading unit 210 acquires the case ID of the case in which the product is stored in order to link and register the product stored in the case whose code was read in step S103 with the storage location information acquired in step S102. The case code reading unit 210 reads the code displayed on a case in which multiple products are stored in response to an operation by the employee 21 and acquires the case ID. The case code reading unit 210 sends the acquired case ID to the identification request unit 240 and the linking request unit 260.

[0116] In step S104, the identification request unit 240 of the terminal 20 receives the case ID from the case code reading unit 210. The identification request unit 240 generates an identification request for the product information. The identification request includes the case ID acquired by the case code reading unit 210. The identification request unit 240 transmits the identification request for the product information to the management device 10.

[0117] In step S105, the product information identification unit 140 of the management device 10 receives a product information identification request from the terminal 20. The product information identification unit 140 identifies the product information based on the case ID included in the received identification request. Specifically, the product information identification unit 140 extracts the product information linked to the case ID from the product database stored in the product information storage unit 101.

[0118] In step S106, the product information identification unit 140 of the management device 10 generates an identification result in response to the identification request. If one or more pieces of product information are identified in step S105, the product information identification unit 140 generates an identification result that includes the identified product information and indicates that the product information has been successfully identified. On the other hand, if no product information is identified in step S105, the product information identification unit 140 generates an identification result that does not include the product information and indicates that the product information has not been successfully identified. The product information identification unit 140 transmits the generated identification result to the terminal 20.

[0119] In step S107, the identification request unit 240 of the terminal 20 receives the identification result from the management device 10. The identification request unit 240 determines whether or not the product information has been identified based on the identification result.

[0120] For example, the identification request unit 240 may determine that the identification of the product information has been successful when the identification result indicates that the identification of the product information has been successful. On the other hand, the identification request unit 240 may determine that the identification of the product information has been unsuccessful when the identification result indicates that the identification of the product information has been unsuccessful.

[0121] As another example, the identification request unit 240 may determine that the identification of the product information has been successful if the identification result includes the product information. On the other hand, the identification request unit 240 may determine that the identification of the product information has failed if the identification result does not include the product information.

[0122] If the identification result includes product information, the identification request unit 240 may have the employee 21 confirm the product information included in the identification result. The identification request unit 240 may display the product information included in the identification result on a display, and determine that the product information has been successfully identified if the employee 21 performs a confirmation operation. On the other hand, the identification request unit 240 may determine that the product information has not been successfully identified if the employee 21 does not perform a confirmation operation (for example, if an operation indicating that the product information is different is performed).

[0123] If the product information can be identified, the identification request unit 240 sends the product ID included in the identification result to the linking request unit 260, and proceeds to step S116. On the other hand, if the product information cannot be identified, the identification request unit 240 proceeds to step S108. If the product information cannot be identified and the employee 21 performs a specific operation (for example, tapping the register button 602) on the operation screen (for example, operation screen 600 in FIG. 19 ) that is displayed on the display, the identification request unit 240 may proceed to step S108.

[0124] In step S108, the individual item code reading unit 220 of the terminal 20 requests the employee 21 to read the code displayed on the product. In response to an operation by the employee 21, the individual item code reading unit 220 uses a reading device to read the code displayed on the product. The product whose code is read in step S108 may be the product contained in the case whose code was read in step S103. For example, the product whose code is read in step S108 may be the product that the employee 21 unpacks and takes out of the case whose code was read in step S103. For example, the product whose code is read in step S108 may be the same product that the employee 21 brings from the sales floor or the like and that is contained in the case whose code was read in step S103. The individual item code reading unit 220 recognizes the read code to obtain a product ID. In other words, if the single item code reading unit 220 is unable to identify a product ID based on the case ID acquired in step S103, it acquires the product ID of the product contained in the case in order to link and register the product contained in the case whose code was read in step S103 with the storage location information acquired in step S102. In this way, if the single item code reading unit 220 is unable to identify a product based on the case ID acquired by reading the code displayed on the case, it reads the code displayed on the product contained in the case in response to an operation by employee 21 and acquires the product ID. The single item code reading unit 220 sends the acquired product ID to the acquisition request unit 250.

[0125] In other words, if the single item code reading unit 220 is unable to identify the product information based on the case ID obtained in step S103, it prompts the employee 21 to obtain the product ID of the product contained in the case. For example, the single item code reading unit 220 may prompt the employee 21 to obtain the product ID by displaying on the display an operation screen that prompts the employee 21 to read the code displayed on the product. For example, the single item code reading unit 220 may prompt the employee 21 to obtain the product ID by outputting from a speaker a sound that prompts the employee 21 to read the code displayed on the product. The single item code reading unit 220 may prompt the employee 21 to obtain the product ID by vibrating the terminal 20. The method of prompting the employee 21 to obtain the product ID may be any method that notifies the employee 21 that a product ID will be obtained and enables the employee 21 to obtain the product ID in response to the notification. Here, prompting the employee 21 to obtain the product ID is a concept that includes the management device 10 transmitting to the terminal 20 an identification result indicating that identification of the product information failed in step S106.

[0126] In step S109, the acquisition request unit 250 of the terminal 20 receives the product ID from the single item code reading unit 220. The acquisition request unit 250 generates an acquisition request for product information. The acquisition request includes the product ID acquired by the single item code reading unit 220. The acquisition request unit 250 transmits the acquisition request for product information to the management device 10.

[0127] In step S110, the product information acquisition unit 150 of the management device 10 receives a request to acquire product information from the terminal 20. The product information acquisition unit 150 requests sales information from the sales information acquisition unit 120. In response to the request from the product information acquisition unit 150, the sales information acquisition unit 120 acquires the sales information from the sales management system 40. The sales information acquisition unit 120 sends the acquired sales information to the product information acquisition unit 150.

[0128] In step S111, the product information acquisition unit 150 of the management device 10 receives sales information from the sales information acquisition unit 120. The product information acquisition unit 150 acquires product information from the sales information based on the product ID included in the acquisition request received in step S110. Specifically, the product information acquisition unit 150 extracts sales information in which the product ID included in the acquisition request is set from the sales information, and acquires the product information included in the sales information.

[0129] In step S112, the product information acquisition unit 150 of the management device 10 generates an acquisition result in response to the acquisition request. The product information acquisition unit 150 generates the acquisition result including the product information acquired in step S111. The product information acquisition unit 150 transmits the generated acquisition result to the terminal 20.

[0130] In step S113, the acquisition request unit 250 of the terminal 20 receives the acquisition result from the management device 10. The acquisition request unit 250 determines whether or not the correct product information has been acquired based on the acquisition result.

[0131] As an example, the acquisition request unit 250 may have the employee 21 confirm the product information included in the acquisition result. The acquisition request unit 250 may display the product information included in the acquisition result on a display, and may determine that the acquisition of the product information has been successful if the employee 21 performs a confirmation operation. On the other hand, the acquisition request unit 250 may determine that the acquisition of the product information has failed if the employee 21 does not perform a confirmation operation (for example, if an operation indicating that the product information is different is performed).

[0132] If the correct product information is acquired, the acquisition request unit 250 sends the product ID included in the acquisition result to the linking request unit 260 and proceeds to step S114. On the other hand, if the correct product information is not acquired, the acquisition request unit 250 returns the process to step S108.

[0133] Returning to step S108, the single item code reading unit 220 requests the employee 21 to read the code displayed on another product. In response to an operation by the employee 21, the single item code reading unit 220 uses a reading device to read the code displayed on the other product. Thereafter, the product management system 1000 executes the processes from steps S109 to S113 again for the code read from the other product. In this way, the product management system 1000 repeatedly executes the processes from steps S108 to S113 until the correct product information for the product contained in the case whose code was read in step S103 is obtained.

[0134] In step S114, the linking request unit 260 of the terminal 20 receives the product ID from the acquisition request unit 250. The linking request unit 260 also receives the case ID from the case code reading unit 210. The linking request unit 260 generates a request to link the product with the case. The linking request includes the product ID acquired by the acquisition request unit 250 and the case ID acquired by the case code reading unit 210. The linking request unit 260 transmits the request to link the product with the case to the management device 10.

[0135] In step S115, the product information management unit 160 of the management device 10 receives a request to link a product with a case from the terminal 20. The product information management unit 160 links the product ID with the case ID based on the linking request. Specifically, the product information management unit 160 links the case ID included in the linking request with the product information stored in the product database stored in the product information storage unit 101, and registers the product information. This links the product with the case in the product database.

[0136] In step S116, the linking request unit 260 of the terminal 20 receives the storage location information from the storage location acquisition unit 230. If it is determined in step S107 that the product information has been successfully identified, the linking request unit 260 receives the product ID from the identification request unit 240. If it is determined in step S107 that the product information has not been successfully identified, the linking request unit 260 uses the product ID received from the acquisition request unit 250 in step S114.

[0137] The linking request unit 260 generates a request for linking the product with the storage location. The linking request includes the product ID acquired by the identification request unit 240 or the acquisition request unit 250 and the storage location information acquired by the storage location acquisition unit 230. The linking request unit 260 transmits the request for linking the product with the storage location to the management device 10. In other words, if the linking request unit 260 can identify the product ID based on the case ID acquired in step S103, the linking request unit 260 links the product ID identified based on the case ID acquired in step S103 with the storage location information acquired in step S102 and registers them in the product database.

[0138] In step S117, the inventory information management unit 170 of the management device 10 receives a request to link products with storage locations from the terminal 20. The inventory information management unit 170 receives the inspection list from the inspection list acquisition unit 110. The inventory information management unit 170 generates inventory information based on the linking request and the inspection list. Specifically, the inventory information management unit 170 links the inspection list with storage location information based on the trolley ID. The number of cases in the inventory information may be set to the number of loaded boxes in the inspection list, or may be set to the number of cases input by the employee 21. The number of individual items in the inventory information may be set to zero, or may be set to the number of individual items input by the employee 21. The inventory information management unit 170 stores the generated inventory information in the inventory information storage unit 102.

[0139] The product management system 1000 executes a manual product registration process to link and register the products contained in the cases with their storage locations. Here, linking and registering the products with their storage locations is a concept that includes the terminal 20 sending a request to the management device 10 in step S116 to link the products with the storage locations, in order to cause the management device 10 to execute the process of step S117.

[0140] Furthermore, if the product management system 1000 is unable to identify product information based on the case ID acquired in step S103, it links the product ID acquired in step S108 with the case ID acquired in step S103 and registers them. Here, linking and registering the product ID and case ID is a concept that includes the terminal 20 sending a request to link the product with the case to the management device 10 in step S114 in order to cause the management device 10 to execute the process of step S115.

[0141] <List creation process> 16 is a sequence diagram showing an example of the list creation process, which is executed by the merchandise management system 1000 when the employee 21 performs a list creation task.

[0142] In step S201, the single item code reading unit 220 of the terminal 20 requests the employee 21 to read the code displayed on the product that needs to be put out, in response to an operation by the employee 21. The operation by the employee 21 may include an operation of selecting a stocking list to register from multiple stocking lists. In response to an operation by the employee 21, the single item code reading unit 220 uses a reading device to read the code displayed on the product that needs to be put out. The single item code reading unit 220 recognizes the read code and obtains the product ID. The single item code reading unit 220 sends the obtained product ID to the identification request unit 240.

[0143] In step S202, the identification request unit 240 of the terminal 20 receives the product ID from the single item code reading unit 220. The identification request unit 240 generates an identification request for the product information. The identification request includes the product ID received from the single item code reading unit 220. The identification request unit 240 transmits the identification request for the product information to the management device 10.

[0144] In step S203, the product information identification unit 140 of the management device 10 receives a product information identification request from the terminal 20. The product information identification unit 140 identifies the product information based on the product ID included in the received identification request. Specifically, the product information identification unit 140 extracts the product information to which the product ID is set from the product database stored in the product information storage unit 101.

[0145] The product information identification unit 140 may acquire inventory information of the product to be put out based on the product ID included in the identification request. Specifically, the product information identification unit 140 may extract inventory information to which the product ID is set from the inventory information stored in the inventory information storage unit 102.

[0146] In step S204, the product information identification unit 140 of the management device 10 generates an identification result in response to the identification request. The product information identification unit 140 generates the identification result including the product information identified in step S203. The product information identification unit 140 transmits the generated identification result to the terminal 20.

[0147] The product information identification unit 140 may include information about the inventory of the product to be put out in the identification result based on the inventory information acquired in step S203. The information about the inventory may be, for example, information indicating whether or not there is inventory, or the number of products stored in the back room.

[0148] In step S205, the list registration unit 270 of the terminal 20 receives the identification result from the management device 10. The list registration unit 270 displays the product information included in the identification result on the display and requests the employee 21 to input the number of items to be put out. The list registration unit 270 accepts the input of the number of items to be put out by the employee 21.

[0149] As one example, the list registration unit 270 may accept an input of the number of items to be put out by the employee 21 via an input device of the terminal 20. As another example, the list registration unit 270 may accept, as the number of items to be put out, the number of times that a code displayed on a product is read using a reading device of the terminal 20. In other words, if the employee 21 reads the same code N times using the reading device of the terminal 20, the list registration unit 270 may determine that the number of items to be put out is N.

[0150] If the identification result includes information indicating whether or not an item is in stock, the list registration unit 270 may display the availability of stock in association with the product information. If the identification result includes information indicating that an item is out of stock (for example, if the number of items is zero), the list registration unit 270 may display a message indicating that an item is out of stock (for example, "out of stock") near the product information. The vicinity of the product information may be, for example, an area adjacent to the top, bottom, left, or right of the area where the product information is displayed.

[0151] If the item to be put out is out of stock, the list registration unit 270 may not accept the input of the number of items to be put out. If the input number of items to be put out is greater than the number of items included in the inventory information, the list registration unit 270 may discard the input number of items to be put out. If the input number of items to be put out is greater than the number of items included in the inventory information, the list registration unit 270 may accept the number of items included in the inventory information as the number of items to be put out.

[0152] If the list registration unit 270 does not accept input of the number of items to be put out, it may request the employee 21 to read a code displayed on another product. If the list registration unit 270 does not accept input of the number of items to be put out, it may return the process to step S201 and request the employee 21 to read a code displayed on another product.

[0153] In step S206, the list registration unit 270 of the terminal 20 generates a registration request for a stocking list. The registration request includes the product information included in the identification result and the number of items to be stocked input in step S205. The list registration unit 270 transmits the registration request for the stocking list to the management device 10.

[0154] In step S207, the stocking list management unit 180 of the management device 10 receives a stocking list registration request from the terminal 20. The stocking list management unit 180 acquires storage location information for the products to be stocked based on the stocking list registration request. Specifically, the stocking list management unit 180 extracts, from the stock information stored in the stock information storage unit 102, the stocking information for which the product ID included in the registration request is set, and acquires the storage location information set in the stock information.

[0155] The stocking list management unit 180 links the product ID and the number of items to be put out included in the registration request with the acquired storage location information and registers them in the stocking list. If there is no stock of the product to be put out (for example, if the number of products included in the inventory information is zero), the stocking list management unit 180 does not need to register it in the stocking list. If the stock of the product to be put out is less than the number to be put out, the stocking list management unit 180 does not need to register it in the stocking list, or it may register the number of products included in the inventory information as the number to be put out in the stocking list.

[0156] <List confirmation process> FIG. 17 is a sequence diagram showing an example of list confirmation processing. The list confirmation processing is processing executed by product management system 1000 when employee 21 performs list confirmation work. The list confirmation work is a work to confirm whether a specific product is registered on the stocking list. The list confirmation work may be performed in a back room or on the sales floor. The list confirmation work may be performed during the list registration work, or may be performed at any timing unrelated to the list registration work.

[0157] In step S301, terminal 20 requests employee 21 to read a code in response to an operation by employee 21. The code read in step S301 is the code related to the product for which it is desired to check whether it is registered on the stocking list. The code related to the product may be the code displayed on the product (for example, the individual product JAN) or the code displayed on the case in which the product is stored (for example, at least one of the case JAN and ITF).

[0158] When reading the code displayed on the case, the case code reading unit 210 of the terminal 20 uses a reading device to read the code displayed on the case in response to an operation by the employee 21. The case code reading unit 210 recognizes the read code and obtains the case ID. The case code reading unit 210 sends the obtained case ID to the identification request unit 240.

[0159] When reading the code displayed on a product, the item code reading unit 220 of the terminal 20 uses a reading device to read the code displayed on the product in response to an operation by the employee 21. The item code reading unit 220 recognizes the read code and obtains the product ID. The item code reading unit 220 sends the obtained product ID to the identification request unit 240.

[0160] In step S302, the identification request unit 240 of the terminal 20 receives a case ID or a product ID from the case code reading unit 210 or the single item code reading unit 220. The identification request unit 240 generates a confirmation request for the stocking list. The confirmation request includes the case ID received from the case code reading unit 210 or the product ID received from the single item code reading unit 220. The identification request unit 240 transmits the confirmation request for the stocking list to the management device 10.

[0161] In step S303, the stocking list management unit 180 of the management device 10 receives a request to confirm the stocking list from the terminal 20. The stocking list management unit 180 sends the case ID or product ID included in the received confirmation request to the product information identification unit 140. The product information identification unit 140 receives the case ID or product ID from the stocking list management unit 180.

[0162] When the product information identification unit 140 receives a case ID from the stocking list management unit 180, it identifies product information based on the received case ID. Specifically, the product information identification unit 140 extracts product information linked to the case ID from the product database stored in the product information storage unit 101. The product information identification unit 140 sends the product ID included in the identified product information to the stocking list management unit 180.

[0163] If the product information identification unit 140 cannot identify product information based on the case ID, the product management system 1000 may execute a process of linking the product and the case and registering them in the product database. For example, the product management system 1000 may execute the processes from step S106 to step S115 of the manual product registration process to link the product and the case and register them in the product database (see FIG. 15 ).

[0164] When the product information identification unit 140 receives a product ID from the stocking list management unit 180, it identifies product information based on the received product ID. Specifically, the product information identification unit 140 extracts product information to which the product ID is set from the product database stored in the product information storage unit 101. The product information identification unit 140 sends the product ID included in the identified product information to the stocking list management unit 180.

[0165] In step S304, the stocking list management unit 180 of the management device 10 acquires a stocking list in which the product ID is registered, based on the product ID received from the product information identification unit 140. Specifically, the stocking list management unit 180 extracts, from the stocking lists stored in the stocking list storage unit 103, a stocking list in which the product ID is registered.

[0166] In step S305, the stocking list management unit 180 of the management device 10 generates a confirmation result in response to the confirmation request. The stocking list management unit 180 generates a confirmation result that includes the product information identified in step S303 and information related to the stocking list extracted in step S304. The information related to the stocking list may include, for example, identification information that identifies the stocking list (e.g., the name of the stocking list), the quantity to be stocked, or the date and time when the stocking list was registered (e.g., information about when the stocking list was created). The stocking list management unit 180 transmits the generated confirmation result to the terminal 20.

[0167] In step S306, the list release unit 290 of the terminal 20 receives the confirmation result from the management device 10. The list release unit 290 displays on the display the product information and information related to the stock list included in the confirmation result. If the confirmation result includes one or more stock lists, the list release unit 290 displays on the display an operation screen that allows a deletion operation to delete a product from the stock list.

[0168] The list release unit 290 accepts a deletion operation by the employee 21. The deletion operation is performed by specifying the stock list from which the product is to be deleted. In response to the deletion operation, the list release unit 290 generates a request to release the stock list. The request to release the stock list may include the product ID of the product to be deleted from the stock list and identification information that identifies the stock list specified in the deletion operation.

[0169] In step S307, the list cancellation unit 290 of the terminal 20 transmits to the management device 10 a request to cancel the stocking list generated in step S306.

[0170] In step S308, the stocking list management unit 180 of the management device 10 receives a request to remove the stocking list from the terminal 20. Based on the request to remove the stocking list, the stocking list management unit 180 removes the product identified in step S303 from the stocking list for which the deletion operation was performed. Specifically, based on the identification information included in the removal request, the stocking list management unit 180 identifies a stocking list stored in the stocking list storage unit 103, and removes the product ID included in the removal request from the identified stocking list.

[0171] <Pickup process> 18 is a sequence diagram showing an example of the pickup process, which is executed by the merchandise management system 1000 when the employee 21 performs the pickup operation.

[0172] In step S401, the list display unit 280 of the terminal 20 generates a request to send a stock list in response to an operation by the employee 21. The request includes information indicating the stock list to be displayed. The operation by the employee 21 may include an operation to select a stock list to be displayed from multiple stock lists. The list display unit 280 sends the request to send the stock list to the management device 10.

[0173] In step S402, the stocking list management unit 180 of the management device 10 receives a request to send a stocking list from the terminal 20. The stocking list management unit 180 reads out from the stocking list storage unit 103 the stocking list indicated in the request to send the stocking list.

[0174] In step S403, the stocking list management unit 180 of the management device 10 transmits the stocking list read out in step S402 to the terminal 20. The stocking list management unit 180 may transmit at least a part of the stocking list. As one example, the stocking list management unit 180 may extract a list of products to be stocked from the stocking list, and transmit the storage locations of the selected products in response to a product selection operation by the employee 21. As another example, the list display unit 280 may extract the storage location from the stocking list, and when the employee 21 arrives at the storage location, transmit a stocking list of the products to be stocked that are stored at the storage location where the employee 21 has arrived.

[0175] In step S404, the list display unit 280 of the terminal 20 receives the stocking list from the management device 10. The list display unit 280 displays the stocking list on a display. The list display unit 280 may display at least a portion of the stocking list. As one example, the list display unit 280 may display a list of product names registered in the stocking list. The list display unit 280 may display the product names registered in the stocking list together with information about the inventory of each product. The list display unit 280 may display the product names registered in the stocking list together with the number of each product to be stocked. As another example, the list display unit 280 may display a list of products to be stocked, and, in response to a product selection operation by the employee 21, may display the storage location of the selected product. As another example, the list display unit 280 may display the storage location of the product to be stocked, and, when the employee 21 arrives at the storage location, display the stocking list for the products to be stocked. As another example, the list display unit 280 may display the names of storage locations of the products to be put out using tabs or the like, and when employee 21 selects a tab corresponding to a storage location, a list of the products to be put out that are stored in that storage location may be displayed.As another example, the list display unit 280 may display a list of storage locations of the products to be put out, and when employee 21 selects a storage location from the list, a list of the products to be put out that are stored in that storage location may be displayed.

[0176] In step S405, the case code reading unit 210 of the terminal 20 requests the employee 21 to read the code displayed on the case. The case whose code is read in step S405 is the case containing the product to be put out, which was displayed in step S404. In response to an operation by the employee 21, the case code reading unit 210 uses a reading device to read the code displayed on the case. The case code reading unit 210 recognizes the read code and obtains a case ID. The case code reading unit 210 sends the obtained case ID to the identification request unit 240 and the linking request unit 260.

[0177] The processing from step S406 to step S417 is the same as the processing from step S104 to step S115 of the manual product registration processing (see FIG. 15). That is, the product management system 1000 identifies product information based on the case ID acquired in step S405, and if the product information cannot be identified, associates the product with the case and registers them in the product database.

[0178] In step S418, the list release unit 290 of the terminal 20 accepts a completion operation by the employee 21. The completion operation is performed by specifying one or more items for which pickup has been completed. In response to the completion operation, the list release unit 290 generates a release request for the stocking list. The release request may include the product IDs of the one or more products specified in the completion operation.

[0179] In step S419, the list cancellation unit 290 of the terminal 20 transmits to the management device 10 a request to cancel the stocking list generated in step S418.

[0180] In step S420, the stocking list management unit 180 of the management device 10 receives a request to cancel the stocking list from the terminal 20. Based on the request to cancel the stocking list, the stocking list management unit 180 cancels the items to be put out that have been picked up from the stocking list.

[0181] <User Interface> The user interface of the terminal 20 will be described with reference to Fig. 19 to Fig. 25. The user interface of the terminal 20 may include, for example, an operation screen. For example, the operation screen may be displayed on the display of the terminal 20.

[0182] Fig. 19 is a diagram showing an example of an operation screen for notifying that a product cannot be identified. The operation screen 600 shown in Fig. 19 is an example of an operation screen displayed when it is determined in step S107 of the manual registration process that product information cannot be identified.

[0183] As shown in FIG. 19, the operation screen 600 may have a notification display section 601, a registration button 602, and a back button 603. The notification display section 601 is an area that displays a notification that the product cannot be identified based on the code displayed on the case. The registration button 602 is a button for starting to associate the product with the case. The back button 603 is a button for closing the operation screen 600 without associating the product with the case. For example, when the registration button 602 is tapped, the operation screen may transition from the operation screen shown in FIG. 19 to the operation screen shown in FIG. 20.

[0184] Fig. 20 is a diagram showing an example of an operation screen for requesting reading of a single item JAN code. Operation screen 610 shown in Fig. 20 is an example of an operation screen displayed when reading the code displayed on a single item in step S108 of the manual registration process.

[0185] As shown in FIG. 20, the operation screen 610 may have a code display section 611, a request display section 612, and a cancel button 613. The code display section 611 is an area that displays a code displayed on a case that cannot identify a product (e.g., a case JAN). The request display section 612 is an area that displays a request to read the individual item JAN. The cancel button 613 is a button for closing the operation screen 610 without reading the individual item JAN. For example, when the individual item JAN is read and corresponding product information is obtained, the operation screen may transition from the operation screen shown in FIG. 20 to the operation screen shown in FIG. 21.

[0186] Fig. 21 is a diagram showing an example of an operation screen for displaying product information. Operation screen 620 shown in Fig. 21 is an example of an operation screen for allowing employee 21 to check the product information included in the acquisition result in step S113 of the manual registration process.

[0187] 21, operation screen 620 may have a product name display section 621, a confirmation button 622, and a retry button 623. Product name display section 621 is an area for displaying a product name acquired based on a code read on operation screen 610. Confirm button 622 is a button for confirming the product name displayed in product name display section 621. Retry button 623 is a button for discarding the product name displayed in product name display section 621 and reading another code. For example, when confirmation button 622 is tapped, the operation screen may transition from the operation screen shown in FIG. 21 to the operation screen shown in FIG. 22. For example, when retry button 623 is tapped, the operation screen may transition from the operation screen shown in FIG. 21 to the operation screen shown in FIG. 20.

[0188] Fig. 22 is a diagram showing an example of an operation screen that displays the code displayed on a single product (e.g., single product JAN) and the code displayed on the case (e.g., case JAN). The operation screen 630 shown in Fig. 22 is an example of an operation screen that is displayed before sending a linking request in step S114 of the manual registration process.

[0189] As shown in FIG. 22, operation screen 630 may have code display section 631, code display section 632, and registration button 633. Code display section 631 is an area that displays a case JAN that cannot identify a product. Code display section 632 is an area that displays a code (i.e., a single item JAN) read on operation screen 610. Registration button 633 is a button for transmitting a linking request between the case JAN displayed in code display section 631 and the single item JAN displayed in code display section 632. For example, when registration button 633 is tapped, the operation screen may transition from the operation screen shown in FIG. 22 to the operation screen shown in FIG. 23.

[0190] Fig. 23 is a diagram showing an example of an operation screen for notifying the result of the linking. The operation screen 640 shown in Fig. 23 is an example of an operation screen for notifying the employee 21 of the result of linking the product and the case in step S115 of the manual registration process.

[0191] 23, the operation screen 640 may have a result display section 641 and a close button 642. The result display section 641 is an area that displays the result of the association request sent on the operation screen 630. The close button 642 is a button for closing the operation screen 640.

[0192] Fig. 24 is a diagram showing an example of an operation screen for notifying the confirmation result. Operation screen 650 shown in Fig. 24 is an example of an operation screen for notifying employee 21 of the result of checking whether or not the product is registered on the stocking list in step S306 of the list confirmation process.

[0193] As shown in FIG. 24, the operation screen 650 may have a notification display section 651, a product information display section 652, a list display section 653, and a code display section 654. The notification display section 651 is an area that displays a notification that the product identified by the read code is registered in one or more stock lists. The product information display section 652 is an area that displays information about the product identified by the read code. The list display section 653 is an area that displays a list of stock lists in which the product identified by the read code is registered. The code display section 654 is an area that displays the read code.

[0194] 24 is an example of an operation screen that is displayed when the product whose code has been read is registered in one or more stock lists. If the product whose code has been read is not registered in one or more stock lists, the notification display unit 651 may display a notification that the product identified by the read code is not registered in the stock lists. Furthermore, the list display unit 653 may display a message that the product identified by the read code is not registered in the stock lists, or the list display unit 653 itself may not be displayed.

[0195] The list display unit 653 accepts a delete operation for each stock list in which the identified product is registered. The list display unit 653 may have a delete button 655 near each of one or more stock lists. The delete button 655 is a button for performing a delete operation to delete the identified product from the stock list displayed in the list display unit 653. For example, when the delete button 655 is pressed, the screen may transition from the operation screen 650 shown in FIG. 24 to the operation screen 660 shown in FIG. 25. Here, the explanation will continue assuming that the delete button 655 corresponding to the stock list named "List for Early Morning People" has been pressed.

[0196] Fig. 25 is a diagram showing an example of an operation screen for notifying the result of the deletion. Operation screen 660 shown in Fig. 25 is an example of an operation screen for notifying employee 21 of the result of removing an item from the stocking list in step S308 of the list confirmation process.

[0197] As shown in FIG. 25, the operation screen 660 may have a result display section 661 and a list display section 662. The result display section 661 is an area that displays the result of the request to cancel the stocking list sent on the operation screen 650. The list display section 662 is an area that displays a list of stocking lists in which the product identified by the read code is registered. The list display section 662 of the operation screen 660 shows that the stocking list named "List for Early Mornings" has been deleted when the delete button 655 was pressed on the operation screen 650.

[0198] [Variation 1] In the example of the manual product registration process shown in Figure 15, a configuration was described in which product information is acquired based on sales information when product information cannot be identified based on the case ID. Here, the management device 10 may be configured to acquire product information based on an image that includes at least a portion of the product information. Note that the management device 10 may acquire product information from the product database when product information is registered in the product database, or may acquire product information based on an image when product information is not registered in the product database.

[0199] <Product information registration process> FIG. 26 is a sequence diagram illustrating an example of the product information registration process.

[0200] The product information registration process may be executed in the manual product registration process shown in Fig. 15. For example, the product management system 1000 may execute steps S501 to S510 of the product information registration process instead of steps S108 to S112 of the manual product registration process (see Fig. 15).

[0201] The product information registration process may be executed in the list creation process shown in Fig. 16. For example, the product management system 1000 may execute steps S501 to S510 of the product information registration process instead of steps S201 to S204 of the list creation process (see Fig. 16).

[0202] The product information registration process may be executed in the list confirmation process shown in Fig. 17. For example, the product management system 1000 may execute steps S501 to S509 of the product information registration process instead of steps S301 to S303 of the list confirmation process (see Fig. 17).

[0203] The product information registration process may be executed in the pickup process shown in Fig. 18. For example, the product management system 1000 may execute steps S501 to S510 of the product information registration process instead of steps S410 to S414 of the pickup process (see Fig. 18).

[0204] The product information registration process may be a process executed when employee 21 performs product information registration work. The product information registration work is a process of registering product information that is not registered in the product database. In other words, the product information registration process may be a process executed at any timing independent of other processes.

[0205] Step S501 is the same as step S108 of the manual product registration process, step S201 of the list creation process, step S301 of the list confirmation process, or step S410 of the pickup process. That is, in step S501, the single item code reading unit 220 of the terminal 20 requests the employee 21 to read the code displayed on the product. In response to an operation by the employee 21, the single item code reading unit 220 uses a reading device to read the code displayed on the product. The single item code reading unit 220 recognizes the read code and obtains the product ID. The single item code reading unit 220 sends the obtained product ID to the acquisition request unit 250.

[0206] Step S502 is the same as step S109 of the manual product registration process, step S202 of the list creation process, step S302 of the list confirmation process, or step S411 of the pickup process. That is, in step S502, the acquisition request unit 250 of the terminal 20 receives the product ID from the single item code reading unit 220. The acquisition request unit 250 generates an acquisition request for product information. The acquisition request includes the product ID acquired by the single item code reading unit 220. The acquisition request unit 250 transmits the acquisition request for product information to the management device 10.

[0207] In step S503, the product information identification unit 140 of the management device 10 receives a product information acquisition request from the terminal 20. The product information identification unit 140 identifies the product information based on the product ID included in the received acquisition request. Specifically, the product information identification unit 140 extracts the product information to which the product ID is set from the product database stored in the product information storage unit 101.

[0208] In step S504, the product information identification unit 140 of the management device 10 determines whether the product ID included in the acquisition request is registered in the product database. If one or more pieces of product information are extracted from the product database in step S503, the product information identification unit 140 determines that the product ID is registered in the product database. On the other hand, if no product information is extracted from the product database in step S503, the product information identification unit 140 determines that the product ID is not registered in the product database.

[0209] If the product information identification unit 140 determines that the product ID is registered in the product database (YES), the management device 10 proceeds to step S510. On the other hand, if the product information identification unit 140 determines that the product ID is not registered in the product database (NO), the management device 10 proceeds to step S505.

[0210] In step S505, the product information acquisition unit 150 of the management device 10 transmits a request to capture a reference image to the terminal 20. The reference image is an image for acquiring product information, and is an example of an image in which at least a portion of the product information (e.g., product name) is captured. As an example, the reference image may include an image of at least one of the product itself, the product packaging, the shelf label corresponding to the product, or the container containing the product.

[0211] In step S506, the acquisition request unit 250 of the terminal 20 receives a request to capture a reference image from the management device 10. The acquisition request unit 250 requests the employee 21 to capture a reference image. In response to an operation by the employee 21, the acquisition request unit 250 uses an imaging device to capture the reference image.

[0212] In step S507, the acquisition request unit 250 of the terminal 20 generates a request to acquire product information. The request includes the reference image captured by the imaging device in step S506. The acquisition request unit 250 transmits the request to acquire product information to the management device 10.

[0213] In step S508, the product information acquisition unit 150 of the management device 10 receives a product information acquisition request from the terminal 20. The product information acquisition unit 150 acquires product information based on the reference image included in the received acquisition request. Specifically, the product information acquisition unit 150 recognizes the product information captured in the reference image and acquires the product information from the recognition result.

[0214] For example, the product information acquisition unit 150 may recognize product information from a reference image based on a machine learning model. The product information acquisition unit 150 may input input information (e.g., a prompt) including a reference image and instruction information instructing the machine learning model to estimate product information from the reference image. The instruction information may include, for example, at least one of an instruction to read product information from the reference image and estimate product information, an instruction to estimate product information by filling in missing information when the product information read from the reference image is partially missing, and an instruction to estimate product information by using not only product information included in the reference image but also image features such as color and shape. For example, the machine learning model may include a visual language model (VLM), a large language model (LLM), a generative model, a base model, etc. The machine learning model may be included in the management device 10 or in an information processing device other than the management device 10. The product information acquisition unit 150 may acquire product information based on output information output from the machine learning model.

[0215] As another example, the product information acquisition unit 150 may recognize product information from the reference image based on optical character recognition (OCR). The product information acquisition unit 150 may recognize character strings included in the reference image by performing optical character recognition on the reference image. The product information acquisition unit 150 may acquire product information based on one or more character strings included in the recognition result.

[0216] The product information acquisition unit 150 may acquire product information from a reference image by combining a machine learning model and optical character recognition. As an example, the product information acquisition unit 150 may perform optical character recognition on the reference image, and input information including one or more character strings included in the recognition result into the machine learning model instead of or together with the reference image, thereby causing the machine learning model to estimate product information.

[0217] By using a machine learning model such as a visual language model, for example, even if only a portion of the product information is captured in a reference image, it is possible to accurately estimate product information using learned knowledge. For example, in the case of beverages such as cans, bottles, and plastic bottles, product information may be displayed on a curved surface such as the side of the product. In this case, when the product information is captured with a camera, it is possible that some of the product information is not included in the field of view, or some characters are blurred in the image. For example, if the machine learning model has learned images of the product or products similar to the product, it is possible to recognize the product information with high accuracy even if only a portion of the product information is captured in the reference image.

[0218] In step S509, the product information acquisition unit 150 of the management device 10 sends the product information acquired in step S508 to the product information management unit 160. The product information management unit 160 stores the product information received from the product information acquisition unit 150 in the product information storage unit 101. Specifically, the product information management unit 160 associates the product ID received in step S503 with the product information acquired in step S508, and registers them in the product database stored in the product information storage unit 101. At this time, the product information management unit 160 does not need to set a case ID in the record to be registered.

[0219] Step S510 is the same as step S112 of the manual product registration process, step S204 of the list creation process, or step S414 of the pickup process. That is, in step S510, the product information acquisition unit 150 of the management device 10 generates an acquisition result in response to the acquisition request received in step S502. If the product information identification unit 140 determines in step S504 that the product ID included in the acquisition request is registered in the product database (YES), the acquisition result includes the product information extracted from the product database in step S503. On the other hand, if the product information identification unit 140 determines in step S504 that the product ID included in the acquisition request is not registered in the product database (NO), the acquisition result includes the product information acquired based on the reference image in step S508. The product information acquisition unit 150 transmits the generated acquisition result to the terminal 20.

[0220] In this modification, the configuration has been described in which product information is acquired based on an image in which at least a portion of the product information is captured. In other words, in this modification, sales information is not used to acquire the product information. In order to use sales information to acquire the product information, it is necessary to cooperate with the sales management system 40 that manages sales information linking product IDs with product information. However, according to this modification, the management device 10 does not need to cooperate with the sales management system 40.

[0221] For example, in order for the management device 10 to link with the sales management system 40, it is necessary to make settings necessary for system linkage in either or both of the management device 10 and the sales management system 40, but according to this modified example, the settings necessary for system linkage can be made unnecessary. Also, for example, a configuration is conceivable in which sales information acquired from the sales management system 40 is stored in a storage device of the management device 10, but according to this modified example, the computational resources (for example, storage capacity, amount of calculation, amount of communication, etc.) for storing the sales information can be reduced or made unnecessary.

[0222] [Variation 2] In the example of the manual product registration process shown in Figure 15, a configuration was described in which a case ID was obtained by reading a code displayed on a case, and product information was identified based on the case ID. Also, in the example of the list creation process shown in Figure 16, a configuration was described in which a product ID was obtained by reading a code displayed on a product, and product information was identified based on the product ID. Here, the management device 10 may be configured to identify product information based on an image of the case or product that includes at least a portion of the product information.

[0223] <Product Information Identification Processing> Fig. 27 is a sequence diagram showing an example of a product information identification process. The product information identification process may be executed in the manual product registration process shown in Fig. 15. The product information identification process may be executed in the list creation process shown in Fig. 16. The product information identification process may be executed in the list confirmation process shown in Fig. 17. The product information identification process may be executed in the pick-up process shown in Fig. 18.

[0224] The product information identification process may be executed within the manual product registration process shown in Fig. 15. For example, the product management system 1000 may execute steps S601 to S605 of the product information identification process instead of or in parallel with steps S103 to S106 of the manual product registration process (see Fig. 15). The product management system 1000 may execute steps S103 to S106 of the manual product registration process (see Fig. 15) or steps S601 to S605 of the product information identification process in response to a selection operation by the employee 21 received via the terminal 20. Furthermore, for example, the product management system 1000 may execute steps S601 to S605 of the product information identification process instead of or in parallel with steps S108 to S112 of the manual product registration process (see Fig. 15). The product management system 1000 may execute steps S108 to S112 (see FIG. 15) of the manual product registration process or steps S601 to S605 of the product information identification process in response to a selection operation by the employee 21 received via the terminal 20.

[0225] The product information identification process may be executed within the list creation process shown in Fig. 16. For example, the product management system 1000 may execute steps S601 to S605 of the product information identification process instead of or in parallel with steps S201 to S204 of the list creation process (see Fig. 16). The product management system 1000 may execute steps S201 to S204 of the list creation process (see Fig. 16) or steps S601 to S605 of the product information identification process in response to a selection operation by the employee 21 received via the terminal 20.

[0226] The product information identification process may be executed as part of the list confirmation process shown in Fig. 17. For example, the product management system 1000 may execute steps S601 to S604 of the product information identification process instead of or in parallel with steps S301 to S303 of the list confirmation process (see Fig. 17). The product management system 1000 may execute steps S301 to S303 of the list confirmation process (see Fig. 17) or steps S601 to S604 of the product information identification process in response to a selection operation by the employee 21 received via the terminal 20.

[0227] The product information identification process may be executed as part of the pickup process shown in Fig. 18. For example, the product management system 1000 may execute steps S601 to S605 of the product information identification process instead of or in parallel with steps S405 to S408 of the pickup process (see Fig. 18). The product management system 1000 may execute steps S405 to S408 of the pickup process (see Fig. 18) or steps S601 to S605 of the product information identification process in response to a selection operation by the employee 21 received via the terminal 20. Furthermore, for example, the product management system 1000 may execute steps S601 to S605 of the product information identification process instead of or in parallel with steps S410 to S414 of the pickup process (see Fig. 18). In response to a selection operation by the employee 21 received via the terminal 20, the merchandise management system 1000 may execute steps S410 to S414 (see FIG. 18) of the pickup process or steps S601 to S605 of the merchandise information identification process.

[0228] The product information identification process may be a process executed when employee 21 performs a product information identification task. The product information identification task is a task of identifying product information associated with a case or a product. In other words, the product information identification process may be a process executed at any timing independent of other processes.

[0229] In step S601, the identification request unit 240 of the terminal 20 requests the employee 21 to capture a reference image. The reference image may be configured in the same manner as in variant example 1. That is, the reference image is an example of an image in which at least a portion of product information (e.g., product name) is captured. The identification request unit 240 captures the reference image using an imaging device in response to an operation by the employee 21. The identification request unit 240 may capture multiple reference images. The multiple reference images may include images of multiple different cases or products.

[0230] When step S601 is executed instead of step S103 (see FIG. 15) of the manual product registration process, the identification request unit 240 may request capturing of a reference image including at least a part of the product information displayed on the case loaded on the cart. When step S601 is executed instead of step S108 (see FIG. 15) of the manual product registration process, the identification request unit 240 may request capturing of a reference image including at least a part of the product information displayed on the product contained in the case.

[0231] When step S601 is executed instead of step S201 (see FIG. 16) of the list creation process, the specific request unit 240 may request capturing of a reference image including at least a portion of the product information displayed on the product that needs to be put out.

[0232] When executing step S601 instead of step S301 (see Figure 17) of the list confirmation process, the specific request unit 240 may request capturing of a reference image including at least part of the product information displayed on the product or case for which it is desired to confirm whether or not it is registered on the stocking list.

[0233] When step S601 is executed instead of step S405 (see FIG. 18) of the pickup process, the identification request unit 240 may request capturing of a reference image including at least a portion of the product information displayed on the case containing the product to be put out. When step S601 is executed instead of step S410 (see FIG. 18) of the pickup process, the identification request unit 240 may request capturing of a reference image including at least a portion of the product information displayed on the product contained in the case.

[0234] In step S602, the identification request unit 240 of the terminal 20 generates an identification request for the product information. The identification request includes the reference image captured by the imaging device in step S601. The identification request unit 240 transmits the identification request for the product information to the management device 10.

[0235] In step S603, the product information identification unit 140 of the management device 10 receives a product information identification request from the terminal 20. The product information identification unit 140 acquires product information based on the reference image included in the received identification request. Specifically, the product information identification unit 140 recognizes the product information captured in the reference image and acquires the product information from the recognition result. In step S601, if multiple reference images are captured, the product information identification unit 140 may recognize product information for each of the multiple reference images.

[0236] The method for recognizing the product information may be the same as that of step S508 of the product information acquisition process (see FIG. 26). For example, the product information identification unit 140 may recognize the product information from the reference image based on a machine learning model such as a visual language model. For example, the product information identification unit 140 may recognize the product information from the reference image based on optical character recognition.

[0237] In step S604, the product information identification unit 140 of the management device 10 identifies product information registered in the product database based on the product information recognized in step S603. Specifically, the product information identification unit 140 extracts product information similar to the recognized product information from the product database stored in the product information storage unit 101.

[0238] The product information identification unit 140 may calculate the similarity between each piece of product information registered in the product database and the product information recognized in step S603. The product information identification unit 140 may extract, from the product information registered in the product database, the product information that has the highest similarity to the recognized product information. The product information identification unit 140 may extract, from the product information registered in the product database, the product information that has the highest similarity to the recognized product information and that is equal to or greater than a threshold.

[0239] The product information identification unit 140 may determine that the identification of product information is successful when product information having a similarity to the recognized product information equal to or greater than a threshold is extracted from the product database. On the other hand, the product information identification unit 140 may determine that the identification of product information is unsuccessful when product information having a similarity to the recognized product information equal to or greater than a threshold is not extracted from the product database.

[0240] If one item of product information is extracted, the management device 10 may execute the subsequent process without executing step S605. For example, when step S604 is executed instead of step S105 (see FIG. 15 ) of the manual product registration process, the inventory information management unit 170 of the management device 10 may generate inventory information based on the storage location information acquired in step S102 and the product information identified in step S604, and store the inventory information in the inventory information storage unit 102.

[0241] The similarity may be a distance measure indicating the similarity between character strings. The similarity may be, for example, an edit distance. The edit distance may include, for example, a Hamming distance or a Levenshtein distance. As another example, the similarity may be the distance between data obtained by transforming character strings using a predetermined function (e.g., vector embedding). The distance between data (e.g., the distance between two vectors obtained by vector embedding for each of two character strings) may include, for example, Euclidean distance, Mahalanobis distance, or cosine similarity. The vector may be calculated using a trained embedding model. Note that when the similarity is the distance between vectors, the product database may include pre-calculated vectors of product information.

[0242] In step S605, the product information identification unit 140 of the management device 10 generates an identification result in response to the identification request. If one or more pieces of product information are extracted in step S604, the product information identification unit 140 generates an identification result that includes the extracted product information and indicates that the product information has been successfully identified. In this case, the product information identification unit 140 may include in the identification result the product information that is most similar to the product information recognized in step S603. On the other hand, if no product information is extracted in step S604, the product information identification unit 140 generates an identification result that does not include any product information and indicates that the product information has not been successfully identified. The product information identification unit 140 transmits the generated identification result to the terminal 20.

[0243] In this modified example, a configuration has been described in which product information is identified based on an image in which at least a portion of the product information is captured. For example, in manual product registration work, depending on the orientation of a case loaded on a cart, it may be difficult to read the code displayed on the case. On the other hand, product information is often displayed on multiple sides of a case, and even if the code is difficult to read, the product information may be easily imaged. Therefore, if the product information can be identified based on an image in which at least a portion of the product information is captured (a reference image), employees can efficiently perform the task of identifying product information.

[0244] [Other embodiments] In this embodiment, a configuration has been described in which the code displayed on the case is linked to the code displayed on the product when the code displayed on the case is read during manual product registration work, list confirmation work, and pick-up work in stocking work. The timing for linking the code displayed on the case to the code displayed on the product may be any work in any business, as long as the code displayed on the case (i.e., case JAN or ITF) is read.

[0245] <Summary> As is clear from the above description, terminal 20 according to one embodiment of the present disclosure acquires first identification information that identifies a container that contains a product, acquires second identification information that identifies the product contained in the container, and links and registers the first identification information and the second identification information.

[0246] The containers containing the products may be stored in a storage location in a backroom. The terminal 20 may acquire first identification information to link and register the products contained in the containers with the storage location. If the product cannot be identified based on the first identification information, the terminal 20 may acquire second identification information and perform registration.

[0247] When a product is identified based on first identification information acquired to link and register the product contained in the container with the storage location, the terminal 20 may link and register the identified product with the storage location.

[0248] The terminal 20 may acquire the first identification information by reading a first code in which the first identification information is encoded. The terminal 20 may acquire the second identification information by reading a second code in which the second identification information is encoded. The first code may be displayed on a container. The second code may be displayed on a product.

[0249] The terminal 20 may be operated by an employee of a store that sells the product.

[0250] If the product cannot be identified based on the first identification information, the terminal 20 may prompt the user to acquire the second identification information. If the product cannot be identified based on the first identification information, the terminal 20 may acquire the second identification information.

[0251] The terminal 20 may determine that the product cannot be identified if the second identification information is not linked to the first identification information. The terminal 20 may determine that the product cannot be identified if the product identified by the second identification information linked to the first identification information is different from the product contained in the container.

[0252] When the terminal 20 cannot identify the product based on the first identification information, the terminal 20 may notify the user that the product cannot be identified. The terminal 20 may acquire second identification information in response to an operation in response to the notification.

[0253] The terminal 20 may display product information of the product identified by the second identification information. The product information may be obtained from sales information of the product. The sales information may be obtained from a second information processing device that manages sales of the product.

[0254] The terminal 20 may acquire third identification information that identifies a storage location of the product. If the terminal 20 can identify the product based on the first identification information, the terminal 20 may register the identification information that identifies the identified product in association with the third identification information. The third identification information may be identification information that identifies at least one of the cart on which the container is loaded or the area where the cart is placed.

[0255] The terminal 20 may display a stocking list including product information of the product to be stocked and the number of products to be stocked. If the terminal 20 can identify the product based on the first identification information, the terminal 20 may remove the identification information identifying the identified product from the stocking list.

[0256] According to one embodiment of the present disclosure, a device that can easily manage products stored in containers can be provided. In one aspect, according to one embodiment, a store employee can associate and register a container and a product simply by reading the code displayed on the container and the code displayed on the product in the back room.

[0257] Conventionally, linking of containers that hold products to the products contained in the containers has been performed manually by a system administrator, etc. According to this embodiment, linking of containers to products is performed by store employees while they are performing their work, thereby reducing delays in work caused by a lack of linking between containers and products, and enabling work to be performed smoothly.

[0258] [Hardware configuration of information processing device] Some or all of the devices (management device 10, terminal 20, delivery management system 30, and sales management system 40) in the above-described embodiments may be configured as hardware, or may be configured as software (program) information processing executed by a CPU (Central Processing Unit), GPU (Graphics Processing Unit), or the like. When configured as software information processing, software that realizes at least some of the functions of each device in the above-described embodiments may be stored on a non-transitory storage medium (non-transitory computer-readable medium) such as a CD-ROM (Compact Disc-Read Only Memory) or a USB (Universal Serial Bus) memory, and the software information processing may be executed by loading the software into a computer. Alternatively, the software may be downloaded via a communication network. Furthermore, all or part of the software processing may be implemented in a circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array), thereby allowing the software information processing to be executed by hardware.

[0259] The storage medium that stores the software may be a removable medium such as an optical disk, or a fixed medium such as a hard disk, memory, etc. The storage medium may be provided inside the computer (main storage device, auxiliary storage device, etc.) or outside the computer.

[0260] 28 is a block diagram showing an example of the hardware configuration of each device (management device 10, terminal 20, delivery management system 30, and sales management system 40) in the above-described embodiment. Each device may be realized as a computer 7 including, for example, a processor 71, a main storage device 72 (memory), an auxiliary storage device 73 (memory), a network interface 74, and a device interface 75, which are connected via a bus 76.

[0261] Although the computer 7 in FIG. 28 includes one of each component, it may also include multiple of the same component. Also, while FIG. 28 shows one computer 7, the software may be installed on multiple computers, and each of the multiple computers may execute the same or different parts of the software. In this case, a distributed computing configuration may be used in which each computer communicates with the other computers via a network interface 74 or the like to execute the processing. That is, each device in the above-described embodiment (the management device 10, the terminal 20, the delivery management system 30, and the sales management system 40) may be configured as a system in which one or more computers execute commands stored in one or more storage devices to realize its functions. Furthermore, the system may be configured such that information sent from a terminal is processed by one or more computers on a cloud, and the processing results are sent to the terminal.

[0262] The various calculations of each device (management device 10, terminal 20, delivery management system 30, and sales management system 40) in the above-described embodiments may be executed in parallel using one or more processors, or using multiple computers via a network. Furthermore, the various calculations may be distributed to multiple processing cores within a processor and executed in parallel. Furthermore, some or all of the processes, means, etc. disclosed herein may be realized by at least one of a processor and a storage device provided on a cloud that can communicate with computer 7 via a network. Thus, each device in the above-described embodiments may be implemented in the form of parallel computing using one or more computers.

[0263] The processor 71 may be an electronic circuit (processing circuit, processing circuitry, CPU, GPU, FPGA, ASIC, etc.) that at least controls a computer or performs calculations. The processor 71 may be a general-purpose processor, a dedicated processing circuit designed to perform a specific calculation, or a semiconductor device that includes both a general-purpose processor and a dedicated processing circuit. The processor 71 may also include an optical circuit or a calculation function based on quantum computing.

[0264] The processor 71 may perform arithmetic processing based on data or software input from each device or the like configured inside the computer 7, and may output the calculation results or control signals to each device or the like. The processor 71 may control each component constituting the computer 7 by executing the OS (Operating System) of the computer 7, applications, etc.

[0265] Each device in the above-described embodiment (the management device 10, the terminal 20, the delivery management system 30, and the sales management system 40) may be realized by one or more processors 71. Here, the processor 71 may refer to one or more electronic circuits arranged on one chip, or may refer to one or more electronic circuits arranged on two or more chips or two or more devices. When multiple electronic circuits are used, the electronic circuits may communicate with each other via wire or wirelessly.

[0266] The main memory device 72 may store instructions executed by the processor 71, various data, etc., and information stored in the main memory device 72 may be read by the processor 71. The auxiliary memory device 73 is a memory device other than the main memory device 72. Note that these memory devices refer to any electronic component capable of storing electronic information, and may be semiconductor memory. The semiconductor memory may be either volatile memory or non-volatile memory. The memory devices for saving various data, etc. in each device (management device 10, terminal 20, delivery management system 30, and sales management system 40) in the above-described embodiments may be realized by the main memory device 72 or the auxiliary memory device 73, or may be realized by an internal memory built into the processor 71. For example, each memory unit in the above-described embodiments may be realized by the main memory device 72 or the auxiliary memory device 73.

[0267] When each device (management device 10, terminal 20, delivery management system 30, and sales management system 40) in the above-described embodiment is configured with at least one storage device (memory) and at least one processor connected (coupled) to this at least one storage device, at least one processor may be connected to one storage device. Also, at least one storage device may be connected to one processor. Also, a configuration may be included in which at least one processor out of multiple processors is connected to at least one storage device out of multiple storage devices. Also, this configuration may be realized by storage devices and processors included in multiple computers. Furthermore, a configuration in which a storage device is integrated with a processor (for example, a cache memory including an L1 cache and an L2 cache) may be included.

[0268] The network interface 74 is an interface for connecting to the communication network 8 wirelessly or via a wire. The network interface 74 may be an appropriate interface, such as one that conforms to an existing communication standard. Information may be exchanged with an external device 9A connected via the communication network 8 via the network interface 74. The communication network 8 may be any one of a WAN (Wide Area Network), a LAN (Local Area Network), a PAN (Personal Area Network), etc., or a combination thereof, as long as information is exchanged between the computer 7 and the external device 9A. An example of a WAN is the Internet, an example of a LAN is IEEE802.11 or Ethernet (registered trademark), and an example of a PAN is Bluetooth (registered trademark) or NFC (Near Field Communication), etc.

[0269] The device interface 75 is an interface such as a USB that directly connects to the external device 9B.

[0270] The external device 9A is a device connected to the computer 7 via a network. The external device 9B is a device connected directly to the computer 7.

[0271] For example, the external device 9A or the external device 9B may be an input device. The input device may be a device such as a camera, a microphone, a motion capture device, various sensors, a keyboard, a mouse, or a touch panel, and provides acquired information to the computer 7. Alternatively, the external device 9A or the external device 9B may be a device equipped with an input unit, a memory, and a processor, such as a personal computer, a tablet terminal, or a smartphone.

[0272] Furthermore, the external device 9A or the external device 9B may be, for example, an output device. The output device may be, for example, a display device such as an LCD (Liquid Crystal Display) or an organic EL (Electro Luminescence) panel, or a speaker that outputs sound or the like. Alternatively, the output device may be a device including an output unit, a memory, and a processor, such as a personal computer, a tablet terminal, or a smartphone.

[0273] Furthermore, the external device 9A or the external device 9B may be a storage device (memory). For example, the external device 9A may be a network storage or the like, and the external device 9B may be a storage such as an HDD.

[0274] Furthermore, the external device 9A or the external device 9B may be a device having some of the functions of the components of each device (the management device 10, the terminal 20, the delivery management system 30, and the sales management system 40) in the above-described embodiment. In other words, the computer 7 may transmit some or all of the processing results to the external device 9A or the external device 9B, or may receive some or all of the processing results from the external device 9A or the external device 9B.

[0275] In this specification (including the claims), when the expression "at least one of a, b, and c" or "at least one of a, b, or c" (including similar expressions) is used, it includes any of a, b, c, ab, ac, bc, or abc. It may also include multiple instances of any element, such as aa, abb, aabbcc, etc. Furthermore, it also includes the addition of elements other than the enumerated elements (a, b, and c), such as having d, as in abcd.

[0276] In this specification (including claims), when expressions such as "using data as input / based on / according to / in response to data" (including similar expressions) are used, unless otherwise specified, this includes cases where the data itself is used, or where data that has been processed in some way (e.g., data with noise added, normalized data, features extracted from data, intermediate representations of data, etc.) is used. Furthermore, when a statement is made that a result is obtained "using data as input / based on / according to / in response to data" (including similar expressions), this includes cases where the result is obtained based solely on the data, or where the result is influenced by other data, factors, conditions, and / or states other than the data itself, unless otherwise specified. Furthermore, when a statement is made that "data is output" (including similar expressions), this includes cases where the data itself is used as output, or where data that has been processed in some way (e.g., data with noise added, normalized data, features extracted from data, intermediate representations of various data, etc.) is used as output, unless otherwise specified.

[0277] When the terms "connected" and "coupled" are used in this specification (including the claims), they are intended as open-ended terms that encompass any of direct connection / coupling, indirect connection / coupling, electrically connection / coupling, communicatively connection / coupling, functionally connection / coupling, and physically connection / coupling. These terms should be interpreted appropriately according to the context in which they are used, but any form of connection / coupling that is not intentionally or naturally excluded should be interpreted as being included in these terms without limitation.

[0278] In this specification (including the claims), the expression "A configured to B" may include the physical structure of element A having a configuration capable of performing operation B, and the permanent or temporary setting / configuration of element A being configured / set to actually perform operation B. For example, if element A is a general-purpose processor, it is sufficient that the processor has a hardware configuration capable of performing operation B, and is configured to actually perform operation B by setting a permanent or temporary program (instruction). Also, if element A is a dedicated processor, dedicated arithmetic circuit, etc., it is sufficient that the circuit structure, etc. of the processor is implemented to actually perform operation B, regardless of whether control instructions and data are actually attached.

[0279] Whenever words implying containing or possessing (e.g., "comprising / including," "having," etc.) are used in this specification (including the claims), they are intended to be open-ended terms that include the inclusion or possession of things other than the object designated by the object of the term. When the object of such words implying containing or possessing does not specify a quantity or suggests a singular number (e.g., expressions using the articles "a" or "an"), the expression should be construed as not being limited to a specific number.

[0280] In this specification (including the claims), even if expressions such as "one or more" and "at least one" are used in some places and expressions that do not specify a quantity or that imply a singular number (expressions using the articles "a" or "an") are used in other places, the latter expressions are not intended to mean "one." In general, expressions that do not specify a quantity or that imply a singular number (expressions using the articles "a" or "an") should be interpreted as not necessarily being limited to a specific number.

[0281] In this specification, when a particular advantage / result is described as being obtained with respect to a particular configuration of an embodiment, it should be understood that the same advantage / result can also be obtained with one or more other embodiments having the same configuration, unless otherwise stated. However, it should be understood that the presence or absence of the effect generally depends on various factors, conditions, and / or circumstances, and that the effect is not necessarily obtained with the configuration. The effect is merely obtained by the configuration described in the embodiment when various factors, conditions, and / or circumstances are satisfied, and the effect does not necessarily occur in a claimed invention that defines the same or a similar configuration.

[0282] In this specification (including claims), when multiple pieces of hardware perform a predetermined process, the pieces of hardware may cooperate to perform the predetermined process, or some of the hardware may perform all of the predetermined process. Furthermore, some of the hardware may perform part of the predetermined process, and other hardware may perform the rest of the predetermined process. In this specification (including claims), when an expression such as "one or more pieces of hardware perform a first process, and the one or more pieces of hardware perform a second process" (including similar expressions) is used, the hardware performing the first process and the hardware performing the second process may be the same or different. In other words, it is sufficient that the hardware performing the first process and the hardware performing the second process are included in the one or more pieces of hardware. Note that hardware may include electronic circuits, devices including electronic circuits, etc.

[0283] In this specification (including the claims), when multiple storage devices (memories) store data, each of the multiple storage devices may store only a portion of the data, or may store the entire data. Also, a configuration in which only some of the multiple storage devices store data may be included.

[0284] In this specification (including the claims), terms such as "first," "second," etc. are used merely as a way of distinguishing between two or more elements, and are not necessarily intended to impose technical meanings such as temporal aspect, spatial aspect, sequence, quantity, etc. Thus, for example, a reference to a first element and a second element does not necessarily mean that only two elements can be employed therein, that the first element must precede the second element, that the first element must be present in order for the second element to be present, etc.

[0285] Although the embodiments of the present disclosure have been described in detail above, the present disclosure is not limited to the individual embodiments described above. Various additions, modifications, substitutions, partial deletions, etc. are possible within the scope of the conceptual idea and spirit of the present invention, which is derived from the content defined in the claims and their equivalents. For example, when numerical values ​​or formulas are used in the above-described embodiments, they are shown for illustrative purposes and do not limit the scope of the present disclosure. Furthermore, the order of each operation shown in the embodiments is also illustrative and does not limit the scope of the present disclosure.

[0286] The disclosed technology may take the following forms as described below.

[0287] (Appendix 1) At least one memory; at least one processor; The at least one processor: obtaining first identification information that identifies a container containing the product; acquiring second identification information that identifies the product contained in the container; registering the first identification information and the second identification information in association with each other; Information processing device.

[0288] (Appendix 2) The container containing the product is stored in a storage location in a back room, The at least one processor: acquiring the first identification information to link and register the product contained in the container with the storage location; If the product is not identified based on the first identification information, the second identification information is acquired and the product is registered. 10. The information processing device according to claim 1.

[0289] (Appendix 3) The at least one processor: When the product is identified based on the first identification information acquired for registering the product contained in the container in association with the storage location, the identified product is registered in association with the storage location. 3. The information processing device according to claim 2.

[0290] (Appendix 4) The at least one processor: acquiring the first identification information by reading a first code in which the first identification information is encoded; acquiring the second identification information by reading a second code in which the second identification information is encoded; 4. An information processing device according to any one of appendices 1 to 3.

[0291] (Appendix 5) the first code is displayed on the container; The second code is displayed on the product. 5. The information processing device according to claim 4.

[0292] (Appendix 6) The information processing device is operated by an employee of a store that sells the product. 6. An information processing device according to any one of appendices 1 to 5.

[0293] (Appendix 7) The at least one processor: If the product is not identified based on the first identification information, prompt the user to obtain the second identification information. 7. An information processing device according to any one of appendices 1 to 6.

[0294] (Appendix 8) The at least one processor: If the product cannot be identified based on the first identification information, the second identification information is acquired. 8. An information processing device according to any one of appendices 1 to 7.

[0295] (Appendix 9) The at least one processor: If the second identification information is not linked to the first identification information, it is determined that the product cannot be identified. 9. The information processing device according to claim 8.

[0296] (Appendix 10) The at least one processor: If the product identified by the second identification information linked to the first identification information is different from the product contained in the container, it is determined that the product cannot be identified. 9. The information processing device according to claim 8.

[0297] (Appendix 11) The at least one processor: If the product cannot be identified based on the first identification information, notify the user that the product cannot be identified. 11. An information processing device according to any one of appendices 1 to 10.

[0298] (Appendix 12) The at least one processor: acquiring the second identification information in response to an operation on the notification; 12. The information processing device according to claim 11.

[0299] (Appendix 13) The at least one processor: displaying product information of the product identified by the second identification information; 13. An information processing device according to any one of appendices 1 to 12.

[0300] (Appendix 14) The product information is obtained from sales information of the product. 14. The information processing device according to claim 13.

[0301] (Appendix 15) The sales information is acquired from a second information processing device that manages sales of the product. 15. The information processing device according to claim 14.

[0302] (Appendix 16) At least a part of the product information is acquired based on a captured image. 14. The information processing device according to claim 13.

[0303] (Appendix 17) The image includes an image of at least one of the product itself, the product packaging, the shelf label corresponding to the product, or the container containing the product. 17. The information processing device according to claim 16.

[0304] (Appendix 18) The product information is recognized from the image based on a machine learning model. 18. The information processing device according to claim 16 or 17.

[0305] (Appendix 19) The product information is recognized from the image based on optical character recognition. 19. The information processing device according to claim 16.

[0306] (Appendix 20) The at least one processor: obtain third identification information that identifies a storage location of the product; If the product can be identified based on the first identification information, the identification information for identifying the identified product is associated with the third identification information and registered. 20. An information processing device according to any one of appendices 1 to 19.

[0307] (Appendix 21) The third identification information is identification information that identifies at least one of a cart on which the container is loaded or an area in which the cart is placed. 21. The information processing device according to claim 20.

[0308] (Appendix 22) The at least one processor: Display a stocking list including product information of the products to be stocked and the number of items to be stocked; If the product can be identified based on the first identification information, the identification information that identifies the identified product is removed from the stock list. 22. An information processing device according to any one of appendices 1 to 21.

[0309] (Appendix 23) At least one memory that stores a database in which product information for each of a plurality of products is registered in association with identification information that identifies the product; at least one processor; The at least one processor: extracting product information linked to the identification information from the database based on the identification information that identifies the product contained in the container, thereby identifying the product; If the product cannot be identified from the database based on the identification information, an image capturing at least a part of the product information is acquired. The product information recognized by inputting the image into a visual language model is linked to the identification information and registered in the database. Information processing device.

[0310] (Appendix 24) At least one memory that stores a database in which product information for each of a plurality of products is registered; at least one processor; The at least one processor: acquiring an image of at least a portion of the product information; Identifying the product by extracting product information corresponding to the recognized product information from the database based on the product information recognized from the image. Information processing device. [Explanation of symbols]

[0311] 10: Management device 20: Terminal 30: Delivery management system 40: Sales management system 101:Product information storage section 102: Inventory information storage unit 103: Stocking list storage unit 110: Inspection List Acquisition Department 120: Sales Information Acquisition Department 130: Request reception unit 140:Product information identification department 150:Product information acquisition department 160:Product Information Management Department 170: Inventory Information Management Department 180: Stock List Management Department 210: Case code reader 220: Single code reader 230: Storage location acquisition department 240:Specific request section 250: Acquisition request section 260: Linking request section 270: List registration section 280: List display section 290: List Cancellation Section 1000: Product management system

Claims

1. at least one memory; at least one processor; The at least one processor acquiring first identification information that identifies a container containing the product; acquiring second identification information that identifies the product contained in the container; registering the first identification information and the second identification information in association with each other; Information processing device.

2. The container containing the product is stored in a storage location in a back room, The at least one processor acquiring the first identification information to link and register the product contained in the container with the storage location; If the product is not identified based on the first identification information, the second identification information is acquired and the product is registered. The information processing device according to claim 1 .

3. The at least one processor When the product is identified based on the first identification information acquired for registering the product contained in the container in association with the storage location, the identified product is registered in association with the storage location. The information processing device according to claim 2 .

4. The at least one processor acquiring the first identification information by reading a first code obtained by encoding the first identification information; acquiring the second identification information by reading a second code obtained by encoding the second identification information; The information processing device according to claim 1 .

5. the first code is displayed on the container; The second code is displayed on the product. The information processing device according to claim 4 .

6. The information processing device is operated by an employee of a store that sells the product. The information processing device according to claim 1 .

7. The at least one processor If the product is not identified based on the first identification information, the user is prompted to obtain the second identification information. The information processing device according to claim 1 .

8. The at least one processor If the product cannot be identified based on the first identification information, the second identification information is acquired.

8. The information processing device according to claim 1.

9. The at least one processor If the second identification information is not linked to the first identification information, it is determined that the product cannot be identified. The information processing device according to claim 8 .

10. The at least one processor If the product identified by the second identification information linked to the first identification information is different from the product contained in the container, it is determined that the product cannot be identified. The information processing device according to claim 8 .

11. The at least one processor If the product cannot be identified based on the first identification information, a notification is given to the effect that the product cannot be identified.

8. The information processing device according to claim 1.

12. The at least one processor acquiring the second identification information in response to an operation on the notification; The information processing device according to claim 11.

13. The at least one processor displaying product information of the product identified by the second identification information; 8. The information processing device according to claim 1.

14. The product information is obtained from sales information of the product. The information processing device according to claim 13.

15. the sales information is acquired from a second information processing device that manages sales of the product; The information processing device according to claim 14.

16. At least a part of the product information is acquired based on a captured image. The information processing device according to claim 13.

17. the image includes an image of at least one of the product itself, the product packaging, a shelf label corresponding to the product, or the container containing the product; The information processing device according to claim 16.

18. The product information is recognized from the image based on a machine learning model. The information processing device according to claim 16.

19. The product information is recognized from the image based on optical character recognition. The information processing device according to claim 16.

20. The at least one processor acquiring third identification information that identifies a storage location of the product; If the product can be identified based on the first identification information, the identification information for identifying the identified product is associated with the third identification information and registered.

8. The information processing device according to claim 1.

21. The third identification information is identification information that identifies at least one of a cart on which the container is loaded or an area in which the cart is placed. The information processing device according to claim 20.

22. The at least one processor Display a stocking list including product information of the products to be stocked and the number of items to be stocked; If the product can be identified based on the first identification information, the identification information that identifies the identified product is removed from the stock list.

8. The information processing device according to claim 1.

23. At least one memory that stores a database in which product information for each of a plurality of products is registered in association with identification information that identifies the product; at least one processor; The at least one processor extracting product information linked to the identification information from the database based on the identification information that identifies the product contained in the container, thereby identifying the product; If the product cannot be identified from the database based on the identification information, an image capturing at least a part of the product information is acquired. The product information recognized by inputting the image into a visual language model is linked to the identification information and registered in the database. Information processing device.

24. At least one memory that stores a database in which product information for each of a plurality of products is registered; at least one processor; The at least one processor acquiring an image of at least a portion of the product information; Identifying the product by extracting product information corresponding to the recognized product information from the database based on the product information recognized from the image. Information processing device.

Images