Wiki/Core Operations/Bulk Actions and the Scrap Button: Fifty Laptops, One Decision, Zero Accidents
08Core Operations4 min read

Bulk Actions and the Scrap Button: Fifty Laptops, One Decision, Zero Accidents

What the Inventory selection bar can do to a batch at once, why the result is reported per asset, and the one button on the asset page that cannot be undone.

Fifty identical Latitudes came off one pallet, went through the same bench, got the same refurbishment and are ready for the same buyer. Doing fifty times the same click is not diligence; it is how the fifty-first mistake happens. The Inventory bulk bar exists so that one decision applies to the whole selection — while the platform still checks, records and reports every asset on its own.

The bulk bar

Select assets in Inventory and the bar offers bulk erasure, print labels, add to outbound, generate evidence, move, Log refurbishment and List for sale. Log refurbishment records one level, one date and one technician on every selected asset; notes, when given, replace the notes on those assets. Assets that are already sold, shipped, recycled or scrapped are skipped, because their refurbishment history is closed. List for sale runs the same market-readiness check as the button on a single asset page — grading, a value, a resale disposition and erasure evidence where required — and pushes what passes to the sales layer through the same publish path.

Partial success is reported, not hidden

Both actions treat the selection as fifty individual decisions. What fails the check is skipped and listed in the dialog with its reason — already listed, the contract workflow does not allow listing, not found in your inventory — and the rest goes through. On full success the toast says how many were done; otherwise it says how many were done and how many were skipped, and points to the dialog for the reasons. Every asset gets its own Activity line, and all the lines of one run share a correlation, so “who listed these forty-seven and why not the other three” is one query later.

As received is a level

The market-ready check does not require a logged refurbishment. Refurbishment level “none” means As received, and it is a valid way to sell a device — the sales layer shows that level to the buyer as-is. A device is not held back from sale because nobody wrote down that nothing was done to it.

Disposition drives the sales layer

Only assets with the disposition resale are projected into the sales layer that Market and Auction draw from. If the bench changes an already projected asset to recycle, scrap, return to client, donate or internal use, the projection goes on hold — unavailable, reason disposition — as long as the asset is not on a channel; set it back to resale and the hold releases by itself. A tenant hold placed separately stays. An asset that is already listed or reserved cannot have its disposition moved away from resale without first leaving the sale. The batch and auction wizards only show units that are free on the channel and available in the stock layer, so a hold keeps a unit out of the wizards too. Nothing bound for the recycler is quietly sold.

The scrap button

On the asset detail, Scrap / recycle opens a dialog that asks for the end-of-life action — recycle, or scrap for no recoverable value — a reason such as beyond repair, hazardous material, client request, compliance requirement or parts harvesting, a processing method such as shredding, demanufacturing, certified recycler or parts harvest, optional notes, and a tick on “I understand this cannot be undone”. It is available to the warehouse, manager and admin roles. It is refused for an asset that is already sold, shipped, recycled or scrapped, for an asset still in a published batch, listing or auction lot, and for an asset on an open outbound order — remove it from the sale layer or the order first, and the dialog tells you which. Saving sets the asset to recycled or scrapped, drops it from the sales layer and from any draft batch, and writes the decision to Activity fail-closed: if the log cannot be written, the asset does not change. The asset row stays, because chain of custody does not end at the shredder. The button does.

Committed stays visible

An asset that is already committed — on a direct sale, on Market, on Auction, reserved, unavailable or attached to an order number — stays in the Inventory list. It is not hidden, and it cannot be bulk-selected for new outbound work. An operator can see that the laptop exists and why it cannot be chosen again; the physical device standing in the rack is not an invitation to sell it twice.