Outbound Orders: From Pick List to Bill of Lading

An outbound order is the mirror of an inbound: assets leave, paperwork follows, settlement closes the deal. The platform handles each piece so the operator doesn’t reconstruct it from scratch.

Five outbound types

Sale (market or auction win), recycling (downstream-only), internal-transfer (between warehouses), return-to-client (for lease-return scenarios where some assets go back), donation (with the appropriate documentation). The type controls which documents are required and which workflow stages run.

The document set

For each outbound, the platform generates the relevant documents on demand — pick list, packing slip, bill of lading (BOL), loading report, recycling certificate. Each is a route under /core/outbound/[id]/{type}, rendered server-side and printable. Document templates are tenant-configurable per outbound type via /settings/core/templates, so a BOL for a sale uses different boilerplate than one for an internal transfer.

Pick list

The pick list is the warehouse-floor doc: which pallet, which rack, which position, which asset, in the order that minimizes walking. The scanner’s outbound mode is built to walk the pick list — scan an asset, the platform confirms it’s on the right line, errors if not.

Sellable-quality gate

Before an asset can land on a sale-type outbound, it has to pass the sellable-quality threshold (D0 erasure, no critical-severity defects, grade above the tenant floor). The gate is enforced server-side; the operator can’t accidentally ship a D-grade asset to a buyer who paid for B-grade.

Deep revert

If an outbound has shipped and needs to come back — a buyer rejects, a courier returns the load — the deep-revert flow walks back the state. Risk-tier-aware (a high-value lot needs a manager approval), with a side-effect preview that shows exactly what status flips, what audit rows get written, and which escrow accounts get locked. Not destructive. Not silent. Reversible by design.