The Pipeline View: Where the Work Is Stuck, Not Where Each Asset Lives

The pipeline view (/core/pipeline) is the operational read of the workflow engine: one section per enabled workflow, a summary per stage, and the numbers a warehouse lead needs to decide where the team should be working this afternoon. It is explicitly not a place to edit individual assets. Bottlenecks are visible here; the fix happens in Inventory, Testing or Outbound.

Receiving gets its own block

Assets only enter a workflow stage once receiving has created them, so a pipeline that showed stages alone would look empty on the busiest intake morning of the month. Above the workflow sections the pipeline therefore shows the upstream receiving work as a worklist, not a tile: open and paused receiving sessions as rows with a direct scan or resume action, and active inbound orders without a session below them as work that can be started. A partially received order — two of three items in — gets “Continue receiving”. Which orders count is the same rule the Receiving overview uses: not fully received yet, or still carrying an open or paused session. A draft, a cancelled order or a fully received order without a session does not appear on either screen.

Filters and sorts

The stage view filters by inbound order, by customer and by warehouse, and has a switch to show only items over SLA — the SLA being the stage’s template hours or the contract’s SLA where a contract defines one. Sorting is by asset volume (the fullest stage first), by urgency, or by the oldest item in the stage. Three sorts, three questions: where is most of the work, where is it most overdue, and what has been sitting there longest.

Retest lives in the testing queue

An asset that has already been graded and hits a problem — a buyer’s pre-shipment check fails, a warehouse audit catches a regraded device — goes back to testing through the retest action on the asset, which re-queues it. The earlier graded queue row stays in the table as history, so the asset has a chain of graded, retested, graded again that an auditor can follow. A retest is refused while the asset still has an open queue item: wait for it to be graded before testing it again. The pipeline reports the consequence — one more item in Diagnostics — but the action itself is not on the pipeline page.

Bulk actions live in Inventory

Selecting a stage and advancing forty assets at once is not what the pipeline does. Bulk work happens in Inventory, where a selection can be sent to erasure, labeled, added to an outbound, given an evidence package, moved, logged as refurbished or listed for sale, each with a per-asset result. The pipeline is the map. Inventory is the truck.

Open the assets that need attention

The attention list identifies assets without a workflow and assets past an existing stage or contract deadline. Each row shows its serial number, current step, inbound order and original deadline. Several reasons stay on one asset row. Sold, shipped, recycled and scrapped assets are excluded. If no person is assigned in the source, the list says “Not recorded”. Search covers the complete filtered selection before pagination; the filters above also apply. Open a row to inspect its inventory record, use the existing work process to make changes, then refresh Pipeline. A failed read produces an error with a retry action rather than an empty work overview.

Follow pending evidence and calculations

A separate searchable, paginated list shows pending evidence reviews and current Carbontrace issues for your organization. Review actions open the specific import. Administrators and managers can inspect current calculation problems and follow links to source data, connection settings or manual results import. Replaced runs and successfully calculated devices are excluded; scheduled attempts are shown only when recorded. Refresh after resolving the source. Receiving work also supports search and pagination, with the assigned person, session opener and recorded note. A paused session retains its neutral status and resume action. Calculations do not prevent the tenant’s physical processing.