Inventory & Pipeline: Two Views of the Same Stock

“Inventory” is everything the platform knows about. “Pipeline” is where that stock currently sits in the workflow. Same assets, two questions, two pages.

Inventory list

/core/inventory is the live asset register. Search on asset tag, serial, manufacturer and model or IMEI runs across the whole stock on the server before the page is cut — you never search only the rows your browser happened to load. Filters cover category, status, grade, disposition, data security, refurbishment, grade freshness, accessories, company, inbound order, receiving session, pallet, warehouse, testing queue status, received date and erasure state. The saved-views bar at the top remembers a filter set — the inventory list as it was Tuesday afternoon is one click away. The CSV export drops the current view or the selected rows straight into a spreadsheet, for client reporting, audit prep, or the downstream system that doesn’t talk to the platform yet.

Bulk actions

Select rows and the bulk bar offers Bulk erasure, Print labels, Add to outbound, Generate evidence, Move, Log refurbishment and List for sale. Log refurbishment writes one level, date and technician to every selected asset; List for sale runs the same market-ready check and publication path as the button on a single asset, reports what fails per asset with the reason, and lets the rest through. Selection is always the visible page — never rows on a server page you cannot see.

Assets that are already committed — reserved, on a channel, on an existing outbound order, or in a final lifecycle state — stay visible but not selectable. Hiding them would make the physical laptop on the shelf feel like free stock; greying them out tells the operator it exists and why it cannot be sold twice.

Scrap lives on the asset, not in the bulk bar

Scrap / recycle is an action on the asset detail page, and only there. It closes the asset for good as recycled or scrapped, with a reason, a processing method, a note and an explicit confirmation that this cannot be undone. Warehouse, manager and admin may do it; sold or shipped assets, and assets sitting in a published batch, listing or lot or on a sales order, cannot be scrapped from under the deal. The asset leaves the sales layer and the action is in Activity. The dedicated bulk-actions article goes deeper on both halves of that rule.

Pipeline view

/core/pipeline shows your workflows as sections — one per contract workflow, with a summary per stage — because the stages a lease return runs through are not the stages a recycling contract runs through. Eight preset workflows ship with the platform and your organization shapes them under Settings > Core > Workflows. Above the workflow sections sits the upstream receiving block: inbound orders not yet fully received and sessions still open or paused, with the actions to continue or start receiving. Filter on inbound order, customer or warehouse, show only items over SLA, and sort by asset volume, urgency or the oldest item in the stage. Requesting a retest of an individual asset happens on the asset detail, not here. Pipeline is not a place to edit every asset. It is a place to see where the work is stuck and decide where the team goes next.

Import queue

/core/inventory/import-queue is not a generic CSV asset import. 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 and Auction import wizards or the sellable-assets API.