Warehouses provides searchable, paginated list and detail for distribution nodes used with inventory flows. Matches admin table patterns (debounced search, 10/page).
| Goals | Non-goals |
|---|
| Maintain warehouse reference data | Optimize pick paths or WMS integration |
| Link to inventory semantics | Document 3PL contracts |
- 400ms debounced search; pagination 10; detail at
/dashboard/warehouses/:id.
- Open Warehouses → search → open detail.
- Create/edit per UI if routes exist (see body).
- Physical address and access contacts may be sensitive—role-gate exports.
| ID | Scenario | Expected |
|---|
| W1 | List | Search + pagination |
| W2 | Detail | Loads warehouse context |
| W3 | Zone scope | Data limited per admin zone rules |
| Path | Purpose |
|---|
/dashboard/warehouses | Paginated, searchable list |
/dashboard/warehouses/:id | Warehouse detail |
- Search — debounced (400ms), resets to page 1.
- Pagination — 10 rows per page.
- Stats — total row count (from list meta) and a count of active warehouses on the current page (rows with
status === 1).
- Rows are mapped from API data via
adminWarehouseToRow for display; opening a row navigates to /dashboard/warehouses/:id.
Warehouses are the inventory location layer; stores are the commercial / vendor-facing unit. Stock and lots in the admin UI connect warehouses to products and suppliers on detail and related flows (see Catalog and products and supplier detail).