<aside> <img src="notion://custom_emoji/bbb1a532-a743-4075-a97f-7c30bff00064/3525769c-771a-8059-b51a-007acb7a5f95" alt="notion://custom_emoji/bbb1a532-a743-4075-a97f-7c30bff00064/3525769c-771a-8059-b51a-007acb7a5f95" width="40px" />

The Manage Warehouse screen is a centralized administrative interface that allows Warehouse Administrators to view, create, and manage warehouse configurations, ensuring that facility settings and locations are accurately maintained for Critical Parts Warehouse (CPW) operations.

</aside>

Page Overview

• Access this page from: Main Menu > Manage Warehouse Data > Warehouses
• The page consists of a central management table where administrators can:
  • Search and Filter: Locate specific warehouses by Name, Code, or Description and filter results by Active or Inactive status.
  • Navigate to Structure: Use the Structure action to jump directly to the zones, slots, and handling units configuration for a specific site.
  • Audit History: Access the View History action to review a complete audit trail of configuration changes.
  • Lifecycle Management: Perform a Soft Delete to mark a facility as inactive or Restore a previously deleted warehouse record.

Warehouse Configuration

General Information

When creating or editing a warehouse via the Detail Drawer, the following fields are required:

• Warehouse Name: A unique plain-text name (max 250 characters).
• Warehouse Code: A unique alphanumeric code (max 30 characters) that acts as a site-scoped prefix for labeling.
• Location: A searchable dropdown used to link the warehouse to a valid location entity, which displays as a formatted physical address.
• Description: A required plain-text description of the warehouse.

Queue Auto-Assignment

Administrators can configure Batch Sizes to control how the system automatically distributes work to associates:

• Queue Types: Settings are available for Replenishment, Cycle Count, and Picking.
• Logic Toggle: Entering a positive integer enables auto-assignment for that queue, while setting the value to 0 or null disables the logic, allowing users to manually claim tasks.
• Queue Enforcement: When enabled, individual "Claim" buttons are hidden, and a prominent "Assign" button claims a batch of tasks based on the defined size.

:lightbulb: User Insights