Moving a container on the PDT
Moving a container on the terminal takes three actions: scan the container, scan the cell you are sending it to, confirm. The container goes with everything inside it, and the move takes effect at once — there is no document and nothing to close.
The terminal moves a container to a cell. To hand one to a carrier, use the client app. To move goods rather than the container itself, see Relocation.
Step 1. Opening the screen
Open Container Movements from the menu.
The screen shows the movement list for your warehouse — what has happened to containers here, newest first — and carries a scanner button.
Scan the code on the container you want to move. The terminal finds it and opens its transfer screen.
If the code matches no container, the terminal says the code was not found and stays on the list. Check you scanned the container label and not a cell or a product barcode.
Step 2. Scanning the target cell
The transfer screen shows four fields. Only the last one accepts input — the other three are there so you can check you have the right container before you send it anywhere.
| Field | Editable? | What it shows |
|---|---|---|
| Container | no | the container you scanned |
| Source Location | no | where it is now |
| Plan Location | no | where the process that created it wants it to go, if it has one |
| Target Location | yes | where you are sending it |
Read Plan Location before you decide. If it is filled in, someone else's process is expecting this container somewhere specific — a packing station, a shipping lane — and sending it elsewhere works against that.
Filling in the target
Scan the label on the cell you are sending the container to. You can also pick the cell from the list, but scanning is the normal way.
Two things can go wrong, and both appear under the field:
The code matches no cell. The terminal reports that the code was not found. Check you scanned a cell label.
The cell does not suit this container. The terminal reports Location type is not allowed and names the type it rejected. Each container purpose has its own set of permitted cell types — see Transfer rules for what is checked and Container purposes for the table.
The container's own Plan Location is the exception: it is accepted even when its type would otherwise be refused. That is how a cart reaches a packing station.
Step 3. What the system checks
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.
Step 4. Confirming the move
Confirm, and the move is done.
It takes effect at once — the container's location becomes the cell you scanned, and the move is added to its log against your name. There is no document to close and nothing to come back to.
If the container has just arrived at its plan cell and that cell is a packing or sorting area, the terminal has also reopened it, so the station can start work. Confirming the move covers exactly when that happens.
If something was wrong — wrong cell, wrong container — move it again. The correction is a new entry in the log, and both stay visible.