Transfer rules

Before a move goes through, the system checks a small number of things. They are the same wherever you record the move.

The container must be in service

A container that has been taken out of service cannot be moved at all. The refusal names its code, so you can tell which one it means when several are involved.

Nothing else about the container's state matters here — its status does not block a move.

The cell must suit the container's purpose

Every purpose has a set of cell types it is allowed in. A pick cart moves freely around the working areas — picking, storage, receiving, shipping, cross-dock. A finished unit bound for a customer is the strictest case: it belongs in a shipping area and nowhere else.

Send a container to a cell type its purpose does not allow and the move is refused, naming the type that was rejected. The full table is in Container purposes.

The plan cell is always allowed

There is one exception, and it is the one that makes the rest work. If the container carries a plan cell, that cell is accepted even when its type is not on the purpose's list.

Without it, a pick cart could never reach a packing station: packing is not a cell type any purpose allows. The plan cell is how a process routes its container to where it is actually needed.

For a carrier, one rule

Handing a container to a carrier checks one thing: the carrier must be active. An inactive carrier is refused, and the message names it.