Daily operations

Site transfers

Two-legged moves between sites: sending, stock in transit, receiving with variances, and cancelling.

Why transfers exist

Between sites, a plain move would make stock vanish from one place and appear at another instantly — hiding the hours or days it spends in a van or with a carrier. A transfer is the honest version: a send leg, an in transit state, and a receive leg. Stock in transit stays visible, owned, and counted the whole way. (Transfers ride the multi-site plan capability.)

The transfer list — Draft, in transit, received, cancelled — with an in-transit total. The site filter defaults to transfers involving your active site.

Send

New transfer picks the source and destination, then lines: each line is a stock record and a quantity. Carrier, tracking number, and a note travel on the transfer.

Creating a transfer — Lines come straight from the source's stock records.

Sending debits the source and creates in-transit stock — the ledger writes one transfer-send movement per line.

In transit and receive

The transfer page shows both legs and the current state.

An in-transit transfer — The parcel exists in the system while it exists in the van.

At the destination, Receive confirms per-line received quantities. Short receipts don't get papered over: the difference is written as a variance adjustment with its own ledger entry, so shrinkage in transit is measurable. Overdue transfers can raise an alert.

Cancel

A transfer that never leaves gets Cancelled with a reason — stock returns to the source and the record remains, keeping even non-events accountable.