System and method for cloud-based inventory management with multi-level approval

Abstract

System and method 100 for inventory management includes a mobile device (440, fig. 4) configured to capture 110 product information by scanning a barcode and / or capturing a product image(s). A cloud-b

Description

FIELD OF INVENTION [0001 ] The present disclosure relates to the field of inventory management systems, and more particularly, to cloud-based inventory management systems utilizing mobile devices for product data capture and implementing multi-level approval processes for inventory validation and updates. BACKGROUND

[0002] Inventory management is a critical aspect of modern business operations, particularly in retail and e-commerce sectors. It involves tracking and controlling the quantity, location, and status of goods and materials within an organization. Effective inventory management ensures that businesses can meet customer demand while minimizing costs associated with overstocking or stockouts.

[0003] Traditional inventory management methods often rely on manual processes, such as physical counts and paper-based record-keeping. These approaches are time-consuming, prone to human error, and provide limited real-time visibility into inventory levels. As businesses grow and product catalogs expand, the complexity of managing inventory increases exponentially, making it challenging to maintain accurate and up-to-date records.

[0004] In recent years, technological advancements have led to the development of various digital inventory management solutions. These systems typically incorporate barcode scanning, database management, and reporting tools to streamline inventory tracking processes. However, many existing solutions still face limitations in terms of data accuracy, real-time updates, and integration with other business systems. Additionally, the process of onboarding new products and maintaining accurate inventory information across multiple locations remains a significant challenge for many organizations.

[0005] Cloud computing and mobile technologies have opened up new possibilities for inventory management, offering the potential for real-time data synchronization, remote access, and improved collaboration among team members. However, there is still a need for comprehensive solutions that can effectively leverage these technologies to address the full spectrum of inventory management challenges faced by modern businesses. SUMMARY

[0006] This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.

[0007] The present disclosure provides a system for inventory management. The system includes a mobile device configured to capture product information by scanning a barcode and / or capturing at least one image of a product. The system also includes a cloud-based database configured to store the captured product information. The system further includes processing circuitry configured to validate the product information through a multi-level approval process, update real-time inventory status based on the validated product information, and synchronize the updated inventory data with the cloud-based database. The system also includes a user interface configured to display product details and facilitate user interaction for inventory management tasks.

[0008] The system may include various features to enhance its functionality and user experience. For example, the mobile device may comprise a camera configured to capture the at least one image of the product, and may further include a flash button to activate a flash for the camera. The user interface may include a barcode field to display a scanned barcode number and an image carousel to display multiple thumbnail images of the product. The processing circuitry may generate a status field indicating the current state of the product in the inventory management system. The user interface may also include input fields for entering product details such as product name, store price, quantity, category, and rack location, as well as an additional notes field for extra information. The system may also generate an inventory management interface displaying a summary of inventory checks, including total products checked, out-of-stock items, in-stock items, and new products added.

[0009] The present disclosure also provides a method for inventory management. The method includes capturing product information using a mobiIe device by scanning a barcode and capturing at least one image of a product, transmitting the captured product information to a cloud-based database, validating the product information through a multi-level approval process, updating real-time inventory status based on the validated product information, and synchronising the updated inventory data with existing store inventory systems. However, in its simplest form, the user is only required to scan / image the product and enter the price for their store. The method may also include displaying product details on a user interface and generating various fields and interfaces to facilitate inventory management tasks.

[0010] Additionally, the present disclosure provides a non-transitory computer-readable medium storing instructions that, when executed by a processor, cause the processor to perform an inventory management method. The method includes receiving product information captured by a mobile device, storing the received product information in a cloudbased database, initiating a multi-level approval process to validate the product information, updating real-time inventory status based on the validated product information, and synchronizing the updated inventory data with existing store inventory systems. The method may also include generating user interfaces and fields to display product details and facilitate inventory management tasks.

[0011] These systems, methods, and computer-readable media provide efficient and accurate inventory management solutions that can be adapted to various retail environments, improving stock tracking, reducing errors, and enhancing overall inventory control processes.

[0012] The foregoing general description of the illustrative embodiments and the following detailed description thereof are merely exemplary examples of the teachings of this disclosure and are not restrictive. BRIEF DESCRIPTION OF FIGURES

[0013] Non-limiting and non-exhaustive examples are described with reference to the following figures. The above and other objects and advantages of the disclosure will be apparent upon consideration of the following detailed description, taken in conjunction with the accompanying drawings, which: FIG. 1 illustrates a flowchart of a method for managing inventory information, in accordance with some examples of the present disclosure. FIG. 2 depicts a flowchart of a method for product onboarding in an inventory management system, in accordance with some examples of the present disclosure. FIG. 3 shows a flowchart of a method for inventory management using an Allish Audit Application, in accordance with some examples of the present disclosure. FIG. 4 presents a block diagram of a system for inventory management, in accordance with some examples of the present disclosure. FIG. 5 illustrates a user interface for adding a product in an inventory management system, in accordance with some examples of the present disclosure. FIG. 6 depicts a user interface of a mobile application for inventory management, showing a product details screen and a status popup, in accordance with some examples of the present disclosure. FIG. 7 shows a user interface for an inventory management system displaying product information and update options, in accordance with some examples of the present disclosure. FIG. 8 illustrates a user interface for an image capture system in an inventory management context, in accordance with some examples of the present disclosure. FIG. 9 depicts four side-by-side interfaces demonstrating various product statuses in an inventory management system, in accordance with some examples of the present disclosure. FIG. 10 presents an inventory management interface for a retail store inventory system, showing multiple screens of the scanning process, in accordance with some examples of the present disclosure. FIG. 11 illustrates a front view of a mobile device screen displaying a barcode scanning interface, in accordance with some examples of the present disclosure. DETAILED DESCRIPTION

[0014] The following description sets forth exemplary examples of the present disclosure. It should be recognised, however, that such a description is not intended as a limitation on the scope of the present disclosure. Rather, the description also encompasses combinations and modifications to those exemplary examples described herein.

[0015] The present disclosure provides a system and method for managing inventory in a retail environment. This system leverages cloud-based technologies and mobile devices to streamline the process of capturing and validating product information. Key components of the system include a mobile device configured to capture product information by scanning barcodes and capturing images, a cloud-based database for storing the captured product information, and processing circuitry for validating the product information through a multilevel approval process. The system also includes a user interface for displaying product details and facilitating user interaction for inventory management tasks. Furthermore, the system provides real-time inventory status updates and synchronizes the updated inventory data with existing store inventory systems. This approach to inventory management offers potential advantages in terms of efficiency, accuracy, and real-time visibility into inventory levels.

[0016] In its basic form, the invention may be described as an inventory management and audit system that streamlines the process of adding and updating products in a store's inventory. The system may operate in two main modes: Inventory Management and Inventory Audit.

[0017] In some aspects, the inventory management process may differ based on whether a product has a barcode or not. For products with barcodes: The user may scan the product's barcode using the mobile device. The system may check if the product exists in the Allish database. If the product is present in the Allish system, the user may only need to add the store-specific price and rack location. If the product is not present in the Allish system, the user may need to add images, store price, and rack location.

[0018] For products without barcodes: The user may cancel the scanner page and manually enter the product name. As the user types the name, the system may display suggestions from existing products in the database. If a matching product is found and selected from the suggestion list, it may be treated as if it were found in the system (similar to a barcode scan). The user may then only need to add the store price and rack location. If no matching product is found, indicating it's not present in the Allish system, the user may need to add the full product details including name, images, store price, and rack location.

[0019] The inventory audit process may be designed to efficiently update the status and details of existing products in the inventory. The system may automatically load a list of products without barcodes for the manual check process. During the manual check process, users may: Swipe right to mark a product as in-stock. Swipe left to mark a product as out-of-stock. Use an update price field to make any necessary changes to the product's price. This streamlined approach may allow for quick and efficient inventory management and auditing, reducing the time and effort required to maintain accurate product information across multiple stores.

[0020] In some examples, the method 100 for managing inventory information begins with the capturing of product information using a mobile device 440. This capturing process may involve scanning a barcode associated with a product and capturing at least one image of the product (step 110). The barcode scanning can be performed using a built-in camera of the mobile device 440 or an external barcode scanner connected to the mobile device 440 via a wired or wireless connection. The image capture can also be performed using the built-in camera of the mobile device 440. The captured image may provide visual details of the product, such as its packaging, branding, and physical characteristics.

[0021] Once the product information is captured, it is transmitted to a cloud-based database 212, 312 (step 120). The transmission may be facilitated by a network connection, such as a Wi-Fi or cellular data connection. The cloud-based database 212, 312 is configured to store the captured product information, which may include the scanned barcode, the captured image, and any additional product details entered by the user 101.

[0022] The processing circuitry 420 then initiates a multi-level approval process to validate the product information (step 130). This approval process may involve one or more approvers who review the captured product information for accuracy and completeness. The approvers may be human users, automated systems, or a combination of both. The multi-level approval process ensures that the product information is thoroughly reviewed and validated before it is used to update the inventory status.

[0023] Upon validation of the product information, the processing circuitry 420 updates the real-time inventory status based on the validated product information (step 140). The updated inventory status may reflect the current availability of the product in the store, including the quantity in stock and the location of the product within the store. This real-time inventory status update provides accurate and up-to-date inventory information, which can enhance the efficiency of store operations and improve the shopping experience for customers.

[0024] Finally, the processing circuitry 420 synchronizes the updated inventory data with the cloud-based database 212, 312 (step 150). This synchronization ensures that the inventory data stored in the cloud-based database 212, 312 is consistent with the real-time inventory status in the store. The synchronized inventory data can be accessed and utilized by various components of the system 400, including the user interface 500, 700, 800 for displaying product details and facilitating user interaction for inventory management tasks.

[0025] In some examples, the processing circuitry 420 is configured to update real-time inventory status based on the validated product information. This update may involve adjusting the quantity of the product in stock, marking the product as out of stock, or adding a new product to the inventory. The updated inventory status provides a real-time view of the product availability in the store, which can be crucial for managing store operations and fulfilling customer orders.

[0026] In some examples, the processing circuitry 420 is also configured to synchronize the updated inventory data with the cloud-based database 212, 312. This synchronization process may involve transmitting the updated inventory data to the cloud-based database 212, 312 over a network connection. The cloud-based database 212, 312 then updates its stored inventory data to reflect the latest inventory status from the store. This synchronization ensures that the inventory data stored in the cloud-based database 212, 312 is always up-to-date and consistent with the real-time inventory status in the store.

[0027] In some examples, the system 400 may be implemented using a non-transitory computer-readable medium that stores instructions. When these instructions are executed by a processor, such as the processing circuitry 420, they cause the processor to perform an inventory management method. This method may include the steps of capturing product information using a mobile device 440, transmitting the captured product information to a cloud-based database 212, 312, validating the product information through a multi-level approval process, updating real-time inventory status based on the validated product information, and synchronizing the updated inventory data with the cloud-based database 212, 312. This implementation allows the system 400 to be deployed on various hardware platforms and provides flexibility for future upgrades and enhancements.

[0028] Referring to FIG. 2, in some examples, a method 200 for product onboarding in an inventory management system is illustrated. The method 200 begins with a user 101, in this case, the catalog team, initiating the process. In step 210, the user 101 scans a barcode, which interacts with a database 212. The barcode scanning may be performed using a built-in camera of a mobile device or an external barcode scanner connected to the mobile device. The barcode scanning process may involve capturing a barcode image, decoding the barcode image to extract product information, and transmitting the product information to the database 212 for storage and further processing.

[0029] Following the barcode scanning in step 210, the method 200 proceeds to step 220, where it checks if the product is available in the Allish System. This step may involve querying the database 212 with the product information obtained from the barcode scanning to determine if the product is already present in the system. If the product is not available (No branch), the process moves to step 222, where the product is added to the Allish Database / Storage. This step may involve creating a new product entry in the database 212 with the product information obtained from the barcode scanning.

[0030] If the product is available or after it's added, the method 200 continues to step 224, where the product is added to the Store Inventory. This step may involve updating the store's inventory data in the database 212 to include the newly added product. The inventory data may include information about the product's availability, quantity, location within the store, and other relevant details.

[0031] Following step 224, the method 200 moves to step 230, which involves adding Rack Location and Quantity / Weight information. This step may involve capturing additional product information, such as the location of the product within the store and the quantity or weight of the product in stock. This information may be manually entered by the user 101 or automatically obtained through additional scanning or sensing processes.

[0032] Step 240 follows, where pricing information is added to the product. This step may involve capturing the product's price information, which may be manually entered by the user 101 or automatically obtained through additional scanning or sensing processes. The price information may include the product's retail price, wholesale price, discount price, or other relevant pricing details.

[0033] The method 200 then proceeds to step 250, where the product undergoes an approval process by the Allish Product Team. If approved (Yes branch), the method 200 moves to step 252, where the product becomes available on the Allish customer App / Portal for online ordering. If not approved (No branch), the method 200 proceeds to step 254, where the product is sent back to the user 101 for correction, creating a feedback loop in the process.

[0034] The flowchart depicts the sequence of steps in the method 200, with arrows indicating the flow from one step to the next. The method 200 incorporates decision points, data storage interactions, and a validation process for adding and approving products in the inventory management system.

[0035] In some examples, the inventory management method 300, as depicted in FIG. 3, begins with a user 101, such as an inventory controller, logging into the Allish Audit Application on a mobile device 440. This login process, as shown in step 310, may involve entering user credentials, such as a username and password, and may include additional security measures such as two-factor authentication or biometric verification.

[0036] Once logged in, the user 101 can initiate a product scanning process, as depicted in step 320. This process may involve using a built-in camera of the mobile device 440 or an external barcode scanner connected to the mobile device 440 via a wired or wireless connection to scan barcodes associated with products in the store. The scanned barcode data can provide unique identifiers for the products, facilitating accurate tracking and management of inventory.

[0037] Following the product scanning process, the method 300 proceeds to step 330, where it performs availability checks for the scanned products. This step may involve querying a database 312 with the scanned barcode data to determine the current inventory status of the products. The database 312 may be a cloud-based database that stores inventory data for the store, including information about product availability, quantity, location within the store, and other relevant details.

[0038] In some examples, the availability check process in step 330 and the product scanning process in step 320 may be carried out simultaneously. For example, the system may be configured to automatically perform an availability check for each product immediately after its barcode is scanned. This can provide real-time inventory updates, enhancing the efficiency of the inventory management process.

[0039] In some examples, the method 300 also includes steps for adding new products to the system or marking existing products as available for online shopping. As depicted in step 340, if a scanned product is not found in the database 312, the user 101 can add the product to the system. This may involve capturing additional product information, such as product name, description, price, and images, and transmitting this information to the database 312 for storage and further processing.

[0040] If a scanned product is found in the database 312 but is currently marked as unavailable for online shopping, the user 101 can update the product's status, as shown in step 350. This may involve changing the product's availability status in the database 312 to indicate that the product is now available for online shopping. This feature allows the store to quickly and easily update their online product offerings based on their current inventory.

[0041] In some examples, the method 300 may be implemented with a modified sequence of steps to optimize the inventory management process. In this alternative embodiment, the order of steps 330 and 340 may be reversed, with step 340 being carried out before step 330. Additionally, in some implementations, steps 330 and 340 may be carried out in parallel to further enhance the efficiency of the inventory management process.

[0042] In the configuration where steps 330 and 340 are reversed, after the user 101 logs into the Allish Audit Application in step 310 and begins rack-wise product scanning in step 320, the method 300 may proceed directly to step 340. At step 340, the system may check if the scanned product is available in the store inventory. This initial check of store inventory may allow for quicker identification of discrepancies between physical stock and recorded inventory.

[0043] If the product is available in the store inventory (Yes branch from step 340), the method 300 may proceed to step 346, where the product is marked as available in inventory. Following this, the method 300 may then move to step 330, where it checks if the scanned product is available in the Allish system. This sequence may allow for efficient updating of the Allish system based on confirmed in-store inventory.

[0044] If the product is not available in the store inventory (No branch from step 340), the method 300 may proceed to step 342, where the product is added to Store Data. This may be followed by step 344, where admin approval is sought for the newly added product. After these steps, the method 300 may then proceed to step 330 to check if the product is available in the Allish system.

[0045] At step 330, if the product is available in the Allish system (Yes branch), the method 300 may proceed to step 332, where the product is added to the Allish Product Pool. If the product is not available in the Allish system (No branch), the method 300 may skip step 332 and proceed directly to step 350.

[0046] The method 300 may conclude with step 350, where the product becomes available for online shopping. This modified sequence may provide a more streamlined approach to inventory management, potentially reducing discrepancies between physical store inventory and the Allish system database.

[0047] In the configuration where steps 330 and 340 are carried out in paralell, as soon as a product is scanned in step 320, the system may simultaneously initiate both the availability check in the Allish system (step 330) and the availability check in the store inventory (step 340). This parallel processing approach may allow for faster data retrieval and processing, potentially reducing the overall time required for inventory management tasks.

[0048] By performing these steps concurrently, the system may be able to quickly identify discrepancies between the Allish system and the store inventory, allowing for more rapid resolution of any inconsistencies. For example, if a product is found to be available in the store inventory but not in the Allish system, the system may flag this discrepancy for immediate attention, potentially streamlining the process of adding new products to the online catalog.

[0049] In some examples, the parallel processing of steps 330 and 340 may be implemented using multi-threading techniques, where separate threads or processes handle the Allish system check and the store inventory check simultaneously. This approach may take advantage of modern multi-core processors, potentially improving the overall performance of the inventory management system, especially when dealing with large volumes of product data.

[0050] The system may also incorporate intelligent prioritization algorithms that dynamically adjust the processing order based on factors such as the likelihood of discrepancies, the importance of certain product categories, or historical data on inventory accuracy. This adaptive approach may further optimize the inventory management process, focusing resources on areas that are most likely to require attention or updates.

[0051] Referring to FIG. 4, in some examples, a system 400 for inventory management is illustrated. The system 400 comprises a data storage 410, processing circuitry 420, and an input output path 430. The data storage 410 is represented by a cylindrical structure at the top of the system 400, designed to store inventory data. Below the data storage 410 is the processing circuitry 420, depicted as a rectangular box, which processes the stored data. At the bottom of the system 400 is the input output path 430, also represented by a rectangular box, facilitating data flow in and out of the system. The components are arranged vertically within the system 400, suggesting a logical flow of data from storage through processing to input / output interfaces. The system 400 is shown connected to a mobile device 440 via a zigzag line, indicating a wireless connection. The mobile device 440 is depicted as a smartphone-like device, suggesting that it can interact with the system 400 for inventory management tasks.

[0052] In some examples, the data storage 410 may be a cloud-based database configured to store the captured product information. The product information may include, but is not limited to, product identifiers such as name or SKU, product descriptions, product images, and other relevant product details. The data storage 410 may be designed to accommodate a large volume of product data, allowing for efficient storage and retrieval of inventory information.

[0053] The processing circuitry 420 may be configured to perform various operations on the stored product data. These operations may include validating the product information through a multi-level approval process, updating real-time inventory status based on the validated product information, and synchronizing the updated inventory data with existing store inventory systems. The processing circuitry 420 may be equipped with powerful processors and algorithms to handle these tasks efficiently and accurately.

[0054] The input output path 430 may facilitate the flow of data in and out of the system 400. This may involve receiving product information captured by the mobile device 440, transmitting the captured product information to the data storage 410 for storage, and sending updated inventory data from the processing circuitry 420 to the mobile device 440 or other connected devices. The input output path 430 may support various data transfer protocols to ensure the integrity and security of the data during transmission.

[0055] The mobile device 440 may be configured to capture product information by scanning a barcode and / or capturing at least one image of a product. The mobile device 440 may comprise a camera configured to capture the at least one image of the product. The camera may be a built-in component of the mobile device 440, or it may be an external device connected to the mobile device 440. The camera may be equipped with advanced imaging technologies to capture high-quality images of products. The mobile device 440 may also include a barcode scanner for scanning product barcodes. The barcode scanner may be a built-in feature of the mobile device 440, or it may be an external device connected to the mobile device 440. The barcode scanner may be capable of accurately scanning barcodes even in challenging lighting conditions or at various angles. The mobile device 440 may also include user interface elements, such as a touchscreen display and input buttons, to facilitate user interaction with the system 400.

[0056] Referring to FIG. 5, in some examples, a user interface 500 for adding a new product to an inventory management system is illustrated. The user interface 500 may be displayed on a mobile device 440, such as a smartphone or tablet, and may be designed to facilitate user interaction for inventory management tasks. The user interface 500 may include various components for inputting and reviewing product information, including a barcode field 510, an image carousel 810, and various input fields for product details.

[0057] In some examples, the barcode field 510 may be configured to display a scanned barcode number. The barcode field 510 may be located at the top of the user interface 500 for easy visibility. The barcode field 510 may also include a "Scan Again" option, allowing users to re-scan a barcode if necessary. This feature may be useful in examples where the initial barcode scan is unsuccessful or unclear.

[0058] In some examples, the user interface 500 may include an image carousel 810 configured to display multiple thumbnail images of the product. The image carousel 810 may be located below the barcode field 510 and may allow users to view and review the captured images of the product. The image carousel 810 may support various image manipulation functions, such as zooming in and out, rotating, and deleting images. This feature may be particularly useful for products that have complex or detailed features that need to be captured from multiple angles.

[0059] The user interface 500 may also include various input fields for entering product details. These may include a product name field 730, a store price field 740, a quantity field 520, a category field 530, and a rack location field 540. The product name field 730 may allow users to enter the name of the product, while the store price field 740 may allow users to enter the price of the product in the store. The quantity field 520 may allow users to enter the quantity of the product in stock, while the category field 530 may allow users to select the category to which the product belongs. The rack location field 540 may allow users to enter the location of the product within the store, which may be useful for locating the product during inventory checks or restocking.

[0060] In some examples, the user interface 500 may further include an additional notes field 550 for entering extra information about the product. This field may be useful for capturing additional details about the product that are not covered by the other input fields, such as special handling instructions, expiration dates, or other relevant information. [0061 ] At the bottom of the user interface 500, a review button 560 may be provided. The review button 560 may be configured to submit the entered product information for review and approval. Upon clicking the review button 560, the entered product information may be transmitted to a cloud-based database 212, 312 for storage and further processing. The review button 560 may also trigger a validation process, where the entered product information is checked for accuracy and completeness before being approved for inclusion in the inventory system.

[0062] In some examples, the user interface 500 may be configured to display product details and facilitate user interaction for inventory management tasks. The user interface 500 may be designed to be intuitive and user-friendly, enabling users to easily navigate through the inventory data, perform inventory checks, add or update product information, and perform other inventory management tasks. The user interface 500 may be accessible on various devices, including but not limited to, mobile devices, desktop computers, and tablets.

[0063] Referring to FIG. 5, in some examples, the user interface 500 for adding a new product to an inventory management system is further illustrated. The user interface 500 may include additional input fields for product details that enhance the inventory management system's functionality. These additional input fields may include a 'Sell By' field and an 'Order By' field.

[0064] In some examples, the 'Sell By' field may provide options for 'Quantity' and 'Weight'. This field may allow users to specify how the product is sold in the store. For example, if the product is sold by weight, the user may select the 'Weight' option in the 'Sell By' field. If the product is sold by quantity, such as individual units or packs, the user may select the 'Quantity' option in the 'Sell By' field. This information may be useful for accurately representing the product in the inventory system and for providing customers with accurate product information.

[0065] In some examples, the 'Order By' field may also provide options for 'Quantity' and 'Weight'. This field may allow users to specify how the product can be ordered by customers. For example, if customers can order the product by weight, the user may select the 'Weight' option in the 'Order By' field. If customers can order the product by quantity, the user may select the 'Quantity' option in the 'Order By' field. This information may be useful for accurately representing the product in the inventory system and for providing customers with accurate product ordering options.

[0066] In some examples, the user interface 500 may further include an additional notes field 550 for entering extra information about the product. This field may be useful for capturing additional details about the product that are not covered by the other input fields, such as special handling instructions, expiration dates, or other relevant information. The additional notes field 550 may be a text box that allows users to freely enter any additional information they deem necessary or useful.

[0067] In some examples, the user interface 500 may be designed to be intuitive and user-friendly, enabling users to easily navigate through the inventory data, perform inventory checks, add or update product information, and perform other inventory management tasks. The user interface 500 may be accessible on various devices, including but not limited to, mobile devices, desktop computers, and tablets.

[0068] Referring to FIG. 6, in some examples, a user interface for an inventory management system is illustrated. The user interface includes a product details screen 600 and a status popup 610. The product details screen 600 displays information about a specific product, such as the product name, images, and other relevant details. The product details screen 600 may also include interactive elements, such as buttons or fields, that allow a user 101 to update the product information or perform other inventory management tasks.

[0069] In some examples, the product details screen 600 may include a product image section 710 that displays one or more images of the product. The product image section 710 may allow the user 101 to view the product from various angles, providing a comprehensive visual representation of the product. The product image section 710 may also include interactive elements, such as buttons or sliders, that allow the user 101 to navigate through the images or adjust the view of the product.

[0070] The product details screen 600 may also include a product name field 730 that displays the name of the product. The product name field 730 may be editable, allowing the user 101 to update the product name if necessary. Similarly, a store price field 740 may display the current price of the product in the store, and may be editable to allow the user 101 to update the price.

[0071] The status popup 610 may be displayed over the product details screen 600 and may provide information about the approval status of the product. The status popup 610 may include a timeline that shows the stages of the approval process and the current status of the product. For example, the timeline may show that the product information has been sent for review to a first approver, that the product information has been approved by the first approver, and that the product information has been sent for review to a second approver. The status popup 610 may also display the decision of the second approver, such as whether the product has been approved or rejected. If the product has been rejected, the status popup 610 may provide a reason for the rejection.

[0072] In some examples, the status popup 610 may be interactive, allowing the user 101 to navigate through the stages of the approval process or to take action based on the decision of the second approver. For example, if the product has been rejected, the user 101 may be able to click on a button or link in the status popup 610 to view more details about the reason for the rejection or to resubmit the product information for review.

[0073] The user interface, including the product details screen 600 and the status popup 610, may be designed to be intuitive and user-friendly, enabling users to easily navigate through the inventory data, perform inventory checks, add or update product information, and perform other inventory management tasks. The user interface may be accessible on various devices, including but not limited to, mobile devices, desktop computers, and tablets.

[0074] Referring to FIG. 7, in some examples, a user interface 700 for an inventory management system is illustrated. The user interface 700 displays product information and allows for product updates. At the top of the interface, there is a header displaying the product name "Jay's Potato Crisps" with a back arrow for navigation.

[0075] The product image section 710 occupies a significant portion of the screen. It includes a large main image of the product packaging, showing a bag of Jay's Potato Crisps. Below the main image, there are smaller thumbnail images, likely representing different views of the product.

[0076] Below the product image section 710, the status field 720 is displayed. The status field 720 shows the current status of the product as "REJECTED" and provides a reason: "Images are not clear and prices are incorrect." In some examples, the processing circuitry 420 may be further configured to generate the status field 720 indicating the current state of the product in the inventory management system. This status field 720 may provide valuable feedback to the user 101, allowing them to understand why a product was rejected and what changes need to be made.

[0077] The product name field 730 repeats the product name "Jay's Potato Crisps" for clarity. The store price field 740 displays the current price of the product, which is shown as "£6.99". These fields may be editable, allowing the user 101 to update the product name or price if necessary.

[0078] At the bottom of the user interface 700, there is an update product button 750. This button allows users to make changes to the product information displayed on the screen. Upon clicking the update product button 750, the user 101 may be directed to another screen where they can edit the product details. This functionality allows for efficient and convenient updates to product information, enhancing the overall inventory management process.

[0079] In some examples, the user interface 700 may be designed to be intuitive and user-friendly, enabling users to easily navigate through the inventory data, perform inventory checks, add or update product information, and perform other inventory management tasks. The user interface 700 may be accessible on various devices, including but not limited to, mobile devices, desktop computers, and tablets.

[0080] Referring to FIG. 8, in some examples, a user interface 800 for an image capture system within an inventory management system is illustrated. The user interface 800 may be displayed on a mobile device 440, such as a smartphone or tablet, and may be designed to facilitate user interaction for inventory management tasks. The user interface 800 may include various components for capturing and reviewing product images, including a capture button 830, an image carousel 810, and various navigation elements. [0081 ] In some examples, the capture button 830 may be configured to initiate the image capture process. The capture button 830 may be located at a convenient position on the user interface 800, such as at the bottom of the screen, to allow for easy access by the user 101. Upon pressing the capture button 830, the mobile device 440 may activate its camera and capture an image of the product. The captured image may then be displayed on the user interface 800 for review by the user 101.

[0082] In some examples, the user interface 800 may include an image carousel 810 configured to display multiple thumbnail images of the product. The image carousel 810 may be located below the capture button 830 and may allow users to view and review the captured images of the product. The image carousel 810 may support various image manipulation functions, such as zooming in and out, rotating, and deleting images. This feature may be particularly useful for products that have complex or detailed features that need to be captured from multiple angles.

[0083] In some examples, the user interface 800 may include various navigation elements that facilitate efficient product image management within the inventory system. These navigation elements may include buttons, sliders, or other interactive components that allow the user 101 to navigate through the captured images, select specific images for review or deletion, and perform other image management tasks.

[0084] In some examples, the user interface 800 may be designed to support continuous image capture with low latency. This feature may allow the user 101 to quickly capture multiple images of a product without significant delays between each capture. This can be particularly useful when adding a large number of products to the inventory system in a short period of time.

[0085] In some examples, the user interface 800 may include an option to expand captured images. This feature may allow the user 101 to view a larger version of a captured image, providing a more detailed view of the product. This can be particularly useful for products with small or intricate details that may not be clearly visible in the thumbnail images displayed in the image carousel 810.

[0086] Referring to FIG. 9, in some examples, a user interface for an inventory management system is illustrated. The figure comprises four side-by-side interfaces for the same product, demonstrating the various statuses for a product possible: new product interface 910A, existing product interface 910B, new store product interface 910C, and reviewed product interface 910D. Each interface displays an "Add Product" screen with various components for inputting and reviewing product information.

[0087] In some examples, the new product interface 910A may be displayed when a product is being added to the system for the first time. The interface 910A may include a status field 720 indicating that the product is "New in system". The interface 910A may also include various input fields for entering product details, such as a product name field 730, a store price field 740, a quantity field 520, a category field 530, and a rack location field 540. An additional notes field 550 may also be provided for entering any extra information about the product.

[0088] In some examples, the existing product interface 910B may be displayed when a product is already present in the system and is being updated. The interface 910B may include a status field 720 indicating that the product is "Found in current store". The interface 910B may also include various input fields for updating product details, such as a product name field 730, a store price field 740, a quantity field 520, a category field 530, and a rack location field 540. An additional notes field 550 may also be provided for entering any extra information about the product.

[0089] In some examples, the new store product interface 910C may be displayed when a product is present in the system but is being added to a new store. The interface 910C may include a status field 720 indicating that the product is "Found in system, new in store". The interface 910C may also include various input fields for entering product details, such as a product name field 730, a store price field 740, a quantity field 520, a category field 530, and a rack location field 540. An additional notes field 550 may also be provided for entering any extra information about the product.

[0090] In some examples, the reviewed product interface 910D may be displayed when a user scans a product already sent for review. The interface 910D may include a status field 720 indicating that the product is "Already sent for review". The interface 910D may also include various input fields for reviewing product details, such as a product name field 730, a store price field 740, a quantity field 520, a category field 530, and a rack location field 540. An additional notes field 550 may also be provided for entering any extra information about the product.

[0091] In some examples, each of the interfaces 910A, 910B, 910C, and 910D may include a "Send for Review" button. This button may be configured to submit the entered product information for review and approval. Upon clicking this button, the entered product information may be transmitted to a cloud-based database for storage and further processing. The "Send for Review" button may also trigger a validation process, where the entered product information is checked for accuracy and completeness before being approved for inclusion in the inventory system.

[0092] Referring to FIG. 10, in some examples, an inventory management interface 1000 for a retail store inventory system is illustrated. The inventory management interface 1000 may be displayed on a mobile device 440, such as a smartphone or tablet, and may be designed to facilitate user interaction for inventory management tasks. The inventory management interface 1000 may include various components for viewing and managing inventory data, including summary displays, ongoing process information, and navigation elements.

[0093] In some examples, the inventory management interface 1000 may include a summary display that provides an overview of inventory checks conducted for a store. The summary display may include details such as the total number of products checked, the number of out-of-stock items, the number of in-stock items, and the number of new products added. This summary display may provide a quick and convenient way for users to review the results of inventory checks and identify any potential issues or trends.

[0094] In some examples, the inventory management interface 1000 may also include ongoing process information that provides real-time updates on the progress of inventory checks. This ongoing process information may include details such as the time remaining for the current inventory check, the number of products scanned so far, and the number of new products identified. This ongoing process information may help users to monitor the progress of inventory checks and make necessary adjustments or interventions as needed.

[0095] In some examples, the inventory management interface 1000 may also include navigation elements that facilitate efficient navigation through the inventory data. These navigation elements may include buttons, sliders, or other interactive components that allow users to navigate through the inventory data, select specific products for review or update, and perform other inventory management tasks.

[0096] In some examples, the processing circuitry 420 may be further configured to generate the inventory management interface 1000. The processing circuitry 420 may process the inventory data stored in the data storage 410 and generate the inventory management interface 1000 based on the processed data. The processing circuitry 420 may also update the inventory management interface 1000 in real-time as new inventory data is captured and processed.

[0097] In some examples, the method for inventory management may further include generating the inventory management interface 1000. This may involve processing the inventory data, generating the summary displays and ongoing process information, and configuring the navigation elements. The generated inventory management interface 1000 may then be displayed on a mobile device 440 or other suitable device for user interaction.

[0098] In some examples, a non-transitory computer-readable medium may store instructions that, when executed by a processor, cause the processor to perform an inventory management method that includes generating the inventory management interface 1000. The instructions may include steps for processing the inventory data, generating the summary displays and ongoing process information, configuring the navigation elements, and displaying the inventory management interface 1000 on a mobile device 440 or other suitable device.

[0099] Referring to FIG. 11, in some examples, a mobile device screen 1100 displaying a barcode scanning interface for an inventory management system is illustrated. The mobile device screen 1100 may be part of a mobile device 440, such as a smartphone or tablet, and may be designed to facilitate user interaction for inventory management tasks. The mobile device screen 1100 may include various components for capturing and reviewing product barcodes, including a flip camera button 1110, a flash button 1120, and a barcode scan area 1130.

[0100] In some examples, the inventory management system may be designed to handle situations where a barcode cannot be scanned. This may occur due to various reasons, such as damaged or missing barcodes, non-standard packaging, or products without barcodes like fresh produce. In such examples, the system may allow users to capture and process product information using images instead. [0101 ] For instance, when adding a product like an apple to the inventory, which typically does not have a barcode, the user may utilize the image capture functionality of the mobile device 440. The user interface 800 may provide an option to switch from barcode scanning to image capture mode. In this mode, the user may use the capture button 830 to take one or more clear images of the apple from different angles.

[0102] Once the images are captured, the system may use image recognition technology to identify the product. The processing circuitry 420 may analyze the captured images, comparing them to a database of known product images to determine that the product is an apple. The system may then populate relevant fields in the user interface, such as the product name field 730 with "Apple" and the category field 530 with "Fresh Produce".

[0103] The user may then manually input additional information specific to their inventory, such as the variety of apple in the product name field 730 (e.g., "Granny Smith Apple"), the quantity in the quantity field 520, and the price in the store price field 740. The rack location field 540 may be filled with the appropriate location in the produce section of the store.

[0104] This image-based product entry method may provide flexibility in managing inventory for a wide range of products, especially those that do not have standard barcodes. It may also facilitate faster and more accurate data entry for products like fresh produce, where manual entry of all details could be time-consuming and prone to errors.

[0105] In some examples, the flip camera button 1110 may be configured to switch between different cameras of the mobile device 440. The flip camera button 1110 may be located at a convenient position on the mobile device screen 1100, such as at the bottom of the screen, to allow for easy access by the user 101. Upon pressing the flip camera button 1110, the mobile device 440 may switch between its front and rear cameras, or between other available cameras, allowing the user 101 to choose the most suitable camera for barcode scanning.

[0106] In some examples, the mobile device screen 1100 may include a flash button 1120 configured to activate a flash for the camera of the mobile device 440. The flash button 1120 may be located near the flip camera button 1110 for easy access by the user 101. Upon pressing the flash button 1120, the mobile device 440 may activate its flash, providing additional lighting for barcode scanning. This feature may be particularly useful when scanning barcodes in low-light conditions or when the barcode is printed on a reflective surface that may cause glare. In some examples, capturing the at least one image of the product may comprise activating a flash using the flash button 1120 on the mobile device 440.

[0107] In some examples, the mobile device screen 1100 may include a barcode scan area 1130 configured to display a live preview of the barcode scanning process. The barcode scan area 1130 may be located in the central area of the mobile device screen 1100, providing a clear view of the barcode being scanned. The barcode scan area 1130 may display a standard UPC (Universal Product Code) barcode, consisting of vertical black lines of varying widths on a white background. Below the barcode, a numerical code may be displayed, corresponding to the information encoded in the barcode. This feature may allow the user 101 to visually confirm that the correct barcode is being scanned and that the barcode scanning process is functioning correctly.

[0108] In some examples, the inventory management system may include a feature for generating a route for an employee to move among a plurality of branch stores based on inventory levels and product expiration dates. This feature may be implemented by the processing circuitry 420, which may analyze the inventory data stored in the data storage 410 and generate an optimal route for the employee. The generated route may be displayed on the mobile device 440, guiding the employee through the various branch stores. This feature may help to improve the efficiency of inventory checks and restocking tasks, particularly in large retail environments with multiple branch stores.

[0109] In some examples, the user interface 500, 700, 800 may include a 'How to Use' option for providing guidance to users. This option may be located in a convenient position on the user interface, such as in a dropdown menu or a dedicated help section. Upon selecting the 'How to Use' option, the user may be presented with detailed instructions on how to use the inventory management system, including how to scan barcodes, capture product images, enter product details, and perform inventory checks. This feature may help to ensure that users can effectively use the inventory management system, even if they are not familiar with its functionalities.

[0110] In some examples, the system may include filters for date and status (Pending, Rejected 1, Rejected 2, Retracted, Approved) in the user interface 500, 700, 800. These filters may allow users to sort and filter the inventory data based on various criteria, such as the date of the last inventory check or the approval status of a product. The filters may be implemented as dropdown menus, checkboxes, or other interactive elements on the user interface. By using these filters, users may be able to quickly and easily find specific products or inventory data, enhancing the usability of the inventory management system.

[0111] In some examples, the system may include sorting options (A to Z, Z to A, Creation / Last Modified) in the user interface 500, 700, 800. These sorting options may allow users to sort the inventory data in various ways, such as alphabetically by product name, in reverse alphabetical order, or by the date of creation or last modification. The sorting options may be implemented as buttons, dropdown menus, or other interactive elements on the user interface. By using these sorting options, users may be able to organize the inventory data in a way that best suits their needs, improving the efficiency of inventory management tasks.

[0112] In some examples, the system may display a count of product rows furnished in the user interface 500, 700, 800. This count may provide a quick overview of the number of products currently displayed in the inventory data. The count may be updated in real-time as products are added, updated, or removed from the inventory. This feature may help users to keep track of the size of the inventory and monitor changes over time.

[0113] In some examples, the inventory management system may include a notification feature. This feature may be implemented by the processing circuitry 420, which may be configured to generate notifications based on certain triggers or conditions. For instance, when products belonging to a store go into either 'Retracted' or 'Rejected' state, the system may generate a notification for the user 101. The notification may be displayed on the user interface 500, 700, 800 of the mobile device 440, alerting the user 101 to check upon the Rejected and Retracted Products section of that store and update them accordingly. This feature may help to ensure that any issues with the inventory are promptly addressed, enhancing the accuracy and reliability of the inventory data.

[0114] In some examples, the inventory management system may include a feature to track the number of products scanned per minute by the user 101. This feature may be implemented by the processing circuitry 420, which may be configured to monitor the barcode scanning process and calculate the scanning rate. The scanning rate may be displayed on the user interface 500, 700, 800, providing real-time feedback to the user 101. This feature may help to monitor the efficiency of the inventory check process and identify any potential issues or bottlenecks.

[0115] In some examples, the inventory management system may include integration with a hand scanner as an alternative to the mobile device's camera for barcode scanning. The hand scanner may be connected to the mobile device 440 via a wired or wireless connection, such as Bluetooth. The hand scanner may be configured to scan barcodes and transmit the scanned data to the mobile device 440 for further processing. This feature may provide a more efficient and ergonomic option for barcode scanning, particularly in large retail environments with a high volume of products.

[0116] In some examples, the inventory management system may be designed to function on both iOS and Android devices. This cross-platform functionality may be achieved through the use of platform-agnostic technologies and frameworks, ensuring that the system can operate effectively on a wide range of mobile devices. This feature may enhance the accessibility and usability of the system, allowing it to be used by a diverse range of users with different types of mobile devices.

[0117] In some examples, the inventory management system may be designed to upload and retrieve images with low latency for use with low internet signals. This feature may be implemented by the processing circuitry 420, which may be configured to optimize the image data for efficient transmission over low-bandwidth connections. The system may use various techniques to achieve this, such as image compression, progressive loading, and adaptive bitrate streaming. This feature may ensure that the system can operate effectively even in environments with poor internet connectivity, enhancing its usability and reliability.

[0118] In some examples, the system may utilize a centralized database approach for product information management. This approach may provide significant advantages for new stores, particularly small local stores, joining the platform.

[0119] The cloud-based database may store comprehensive product information for a wide range of items. When a new store joins the system, they may benefit from this existing product database. As the store scans products during the onboarding process, the system may first check if the product already exists in the database. If the product is found, the store may only need to enter store-specific information, such as their price and inventory quantity.

[0120] This approach may significantly streamline the onboarding process for new stores. Unlike traditional e-commerce platforms where merchants may need to manually enter all product details, the present system may allow stores to leverage pre-existing product information. For example, product names, descriptions, images, and categorizations may already be available in the system.

[0121] In some examples, when a store scans a barcode of a product already in the database, the system may automatically populate most of the product fields. The store may then only need to enter or confirm their specific pricing information. This may greatly reduce the time and effort required for a store to establish their online presence.

[0122] This automatic population of product fields based on existing database entries represents a key efficiency feature of the inventory management system. When a store scans a product barcode, the system queries the centralized cloud-based database to check if that product already exists. If found, the system can instantly retrieve and display pre-existing product information such as the product name, description, images, category, and other standard details.

[0123] By automatically populating these fields, the system significantly streamlines the product onboarding process for new stores. Instead of manually entering all product details, store staff only need to review the pre-populated information for accuracy and enter storespecific data like their unique pricing and inventory quantity. This approach not only saves time but also reduces the potential for data entry errors.

[0124] The efficiency gains are particularly impactful for small to mid-sized stores with limited resources. These stores can leverage the collective product information already in the system, allowing them to quickly build out their online product catalog without the need for extensive manual data entry. This lowered barrier to entry enables smaller retailers to more easily establish an online presence and compete in the e-commerce marketplace.

[0125] Furthermore, this feature contributes to data consistency across the platform. When multiple stores carry the same product, they can all benefit from a standardized set of core product information, ensuring uniformity in how products are represented across different retailers. At the same time, the system maintains flexibility by allowing stores to customize certain fields as needed to reflect their unique offerings or local variations.

[0126] Moreover, this centralized database approach may ensure consistency in product information across different stores on the platform. It may also facilitate easier updates to product information, as changes made to the central database may be reflected across all stores carrying that product, if desired.

[0127] In some examples, the system may also allow for store-specific customization of product information. For instance, while leveraging the centralized product data, individual stores may have the option to modify certain fields to better reflect their unique offerings or local variations.

[0128] This efficient product onboarding process may be particularly beneficial for small local stores that may not have the resources to manually input extensive product catalogs. By reducing the barrier to entry for e-commerce, the system may enable a wider range of stores to establish an online presence and compete in the digital marketplace.

[0129] A number of implementations have been described. Nevertheless, it will be understood that various modifications may be made without departing from the spirit and scope of the disclosure. Accordingly, other implementations are within the scope of the following claims.

Claims

1. A system for inventory management, comprising:a mobile device (440) configured to capture product information by scanning a barcode and / or capturing at least one image of a product;a cloud-based database (212, 312) configured to store the captured product information;processing circuitry (420) configured to:validate the product information through a multi-level approval process (step 130);update real-time inventory status based on the validated product information (step 140); andsynchronize the updated inventory data with the cloud-based database (step 150); anda user interface (500, 700, 800) configured to display product details and facilitate user interaction for inventory management tasks.

2. The system of claim 1, wherein the mobile device (440) comprises a camera configured to capture the at least one image of the product.

3. The system of claim 2, wherein the mobile device (440) further comprises a flash button (1120) configured to activate a flash for the camera.

4. The system of any of claims 1 to 3, wherein the user interface (500, 700, 800) comprises a barcode field (510) configured to display a scanned barcode number.

5. The system of any of claims 1 to 4, wherein the user interface (500, 700, 800) comprises an image carousel (810) configured to display multiple thumbnail images of the product.

6. The system of any of claims 1 to 5, wherein the processing circuitry (420) is further configured to generate a status field (720) indicating the current state of the product in the inventory management system.

7. The system of any of claims 1 to 6, wherein the user interface (500, 700, 800) comprises input fields for entering product details including a product name field (730), a store price field (740), a quantity field (520), a category field (530), and a rack location field (540).

8. The system of claim 7, wherein the user interface (500, 700, 800) further comprises an additional notes field (550) for entering extra information about the product.

9. The system of any of claims 1 to 8, wherein the processing circuitry (420) is further configured to generate an inventory management interface (1000) displaying a summary of inventory checks including total products checked, out-of-stock items, in-stock items, and new products added.

10. A method for inventory management, comprising:capturing product information using a mobile device (440) by scanning a barcode and capturing at least one image of a product (step 110);transmitting the captured product information to a cloud-based database (212, 312) (step 120);validating the product information through a multi-level approval process (step 130);updating real-time inventory status based on the validated product information (step 140); andsynchronizing the updated inventory data with the cloud-based database (step 150).

11. The method of claim 10, further comprising displaying product details on a user interface (500, 700, 800) configured to facilitate user interaction for inventory management tasks.

12. The method of claim 11, wherein the user interface (500, 700, 800) comprises a barcode field (510) configured to display a scanned barcode number and an image carousel (810) configured to display multiple thumbnail images of the product.

13. The method of claim 11 or 12, wherein the user interface (500, 700, 800) comprises input fields for entering product details including a product name field (730), a store price field (740), a quantity field (520), a category field (530), and a rack location field (540).

14. The method of any of claims 10 to 13, further comprising generating a status field (720) indicating the current state of the product in the inventory management system.

15. The method of any of claims 10 to 14, wherein capturing the at least one image of the product comprises activating a flash using a flash button (1120) on the mobile device (440).

16. The method of any of claims 10 to 15, wherein validating the product information through the multi-level approval process (step 130) comprises:sending the product information for review to a first approver;upon approval by the first approver, sending the product information to a second approver; andupdating the product status based on the decision of the second approver.

17. The method of any of claims 10 to 16, further comprising generating an inventory management interface (1000) displaying a summary of inventory checks including total products checked, out-of-stock items, in-stock items, and new products added.

18. The method of any of claims 10 to 17, further comprising generating a route for an employee to move among a plurality of branch stores based on inventory levels and product expiration dates.

19. A non-transitory computer-readable medium storing instructions that, when executed by a processor, cause the processor to perform an inventory management method, the method comprising:receiving product information captured by a mobile device (440), the product information including a scanned barcode and at least one image of a product;storing the received product information in a cloud-based database (212, 312);initiating a multi-level approval process to validate the product information (step 130);updating real-time inventory status based on the validated product information (step 140); andsynchronizing the updated inventory data with the cloud-based database (step 150).

20. The non-transitory computer-readable medium of claim 19, wherein the method further comprises generating a user interface (500, 700, 800) configured to display product details and facilitate user interaction for inventory management tasks.

21. The non-transitory computer-readable medium of claim 20, wherein the user interface (500, 700, 800) comprises a barcode field (510) configured to display a scanned barcode number and an image carousel (810) configured to display multiple thumbnail images of the product.

22. The non-transitory computer-readable medium of claim 20 or 21, wherein the user interface (500, 700, 800) comprises input fields for entering product details including a product name field (730), a store price field (740), a quantity field (520), a category field (530), and a rack location field (540).

23. The non-transitory computer-readable medium of any of claims 20 to 22, wherein the method further comprises generating a status field (720) indicating the current state of the product in the inventory management system.

24. The non-transitory computer-readable medium of any of claims 19 to 23, wherein the multilevel approval process (step 130) comprises:sending the product information for review to a first approver;upon approval by the first approver, sending the product information to a second approver; andupdating the product status based on the decision of the second approver.

25. The non-transitory computer-readable medium of any of claims 19 to 24, wherein the method further comprises generating an inventory management interface (1000) displaying a summary of inventory checks including total products checked, out-of-stock items, in-stock items, and new products added.

Images