aureuserp / aureuserp/aureuserp

Feature Request: Add a "Products" tab on the Location view (open) page showing on-hand product quantities

Open
#1,240 0 comments 0 reactions 1 assignee Claimed by @harshqa-webkul View on GitHub
Feature Requested Fix Proposed
Dominant language
PHP
Stars
11.9k
Forks
559
Avg merge
1d 19h
Merged PRs (30d)
34

Description

### Summary
When opening a Location (Inventory → Configurations → Locations → open a record), add a **Products** tab that lists every product currently stored in that location, with a column showing the **On
Hand quantity** for each.

### Motivation / Problem
Today there is no way to see *what is stored in a location* directly from the location screen. To answer "what products and how many units are in `WH/Stock`?", a user has to leave the Location page
and dig through inventory/quant filtered by location. Warehouse and inventory users frequently need this per-location stock view right where they are inspecting the location.

### Proposed Solution
Add a **Products** tab to the Location **view** page (`ViewLocation`), implemented as a Filament relation manager (consistent with the existing tabs registered via `HasRecordNavigationTabs`).

The tab should render a table of the products present in the location with at least:

| Column | Source |
|---|---|
| Product | `inventories_product_quantities.product_id` → `product.name` |
| On Hand Qty | `inventories_product_quantities.quantity` |
| UoM (optional) | product UoM |
| Lot / Package (optional) | `lot_id` / `package_id` when product is tracked |

Notes:
- **On-hand quantity** is the `quantity` column on `inventories_product_quantities` (keyed by `product_id` + `location_id`, optionally `lot_id`/`package_id`).
- Optionally also expose **Reserved** (`reserved_quantity`) and **Available** (`quantity - reserved_quantity`) columns, since both are already stored on the same table.
- Rows where on-hand quantity is `0` should ideally be hidden (or filterable), so the tab shows only products actually present.
- If a product appears under multiple lots/packages, either show one row per lot/package or aggregate per product (aggregated-per-product with an expandable lot breakdown is the most useful
default).

### Screenshot:

Image

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.