SKU-Based Inventory Services

The Defense Commissary Agency (DeCA) is seeking SKU-Based Inventory Services for its CONUS and Pacific locations through a Request for Information (RFI). The procurement will involve comprehensive inventory counting services for grocery items using automated handheld scanners, with contractors required to have a minimum of 3 years of grocery/retail inventory experience and team leaders possessing at least 2 years of inventory management experience. The contract will be structured as an Indefinite Delivery/Indefinite Quantity (IDIQ) with one base year and four optional one-year extensions. Potential contractors must submit their questions specifically related to the attached Technical Requirements and Performance Work Statement documents by 3:00 PM EST on January 24, 2025, with interested companies encouraged to email Christina Ellison at christina.ellison@deca.mil to express their interest. The inventory services will require real-time tracking, detailed SKU-level reporting, and automated validation processes for high-risk and randomly selected inventory sections.

The pre-solicitation notice indicates no specific set-aside designations for this contract opportunity. The inventory services will cover multiple locations within the contiguous United States and Pacific regions, with quarterly inventory requirements solicited approximately 60 days before each service quarter. Contractors must provide their own equipment and personnel while working collaboratively with DeCA staff, and must adhere to strict protocols for electronic device usage during inventories. The technical requirements are comprehensive, covering both fixed weight and random weight items across front-of-store and back-room inventory management, with detailed specifications for data reporting and file formats. Contractors will be expected to handle complex inventory calculations, including pricing for random weight items and providing extensive inventory valuation data by SKU, section, and overall store. The contract will require precise data exchange, with potential penalties for multiple instances of requiring third-count validations.