Inventory & Pipeline: Two Views of the Same Stock

"Inventory" is everything the platform knows about. "Pipeline" is what’s currently moving through the workflow stages. Same assets, two questions, two pages.

Inventory list

/core/inventory shows every asset under tenant scope, filterable by warehouse, category, grade, status, lifecycle stage, and a dozen other dimensions. The CSV export drops the filtered set straight into a spreadsheet — used for client reporting, audit prep, or feeding a downstream system that doesn’t talk to the platform yet.

Bulk actions on the row dropdown: retire (mark as scrapped/recycled with a reason), move to pallet (consolidate onto a different pallet), request erasure (queue for re-wipe). Saved-views bar at the top remembers your filter set — the inventory list as it was Tuesday afternoon is one click away.

Pipeline view

/core/pipeline is the kanban-style view of assets currently in motion: receiving → testing → grading → erasure → ready-for-sale → reserved → sold. Sortable per stage. The "retest" action on a row sends an asset back to testing without losing the original audit trail. Used by warehouse leads who need to know "what’s stuck and where."

Import queue

/core/inventory/import-queue is not a generic CSV asset-import today. It is the review place for audit reports and unmatched wipe certificates from Blancco bulk import or sync. Asset lists enter through inbound manifests and receiving; non-Core sellable inventory enters through the Market/Auction import wizards or the sellable-assets API.