Shipping in the client app
This document covers shipping — how picked goods leave the warehouse — in the client app. Once orders have been picked, shipping is organised around the delivery plan: a document that gathers the orders going out together on one vehicle, sets the loading order, and tracks the load until it is dispatched.
As with picking, the client is the planning-and-monitoring cockpit: a dispatcher builds the plan and watches it progress from a workstation, while the hands-on loading is recorded on the handheld terminal. The dispatcher drives the plan only through its first two statuses; the system sets the rest once loading is confirmed on the floor.
Phase 1. Creating the delivery plan
You start a delivery plan from the Delivery Plan list, with the add (+) button. A delivery plan gathers the orders that will go out together on one vehicle, so the first step is to describe that load.
The plan opens as a short form on its General tab:
- Warehouse — required. The warehouse the goods ship from. The plan cannot be saved without it.
- Shipping Zone — the staging area the load is gathered in and leaves through. Only locations marked as shipping zones can be chosen. A shipping zone must be set before the plan can be marked ready to load (next phases).
- Car Number — the vehicle's registration. Free text.
- Planned Ship At — when the load is expected to leave.
- Notes — a free-text remark; you can add or change it at any time.
A new plan opens in Draft — the only status in which it can be edited. With the load described, you move on to choosing which orders it carries.
Phase 2. Adding orders and loading order
On the plan's Orders tab you choose which outbound orders this load carries. Add the orders that are ready to ship; each one keeps its own details and contributes its goods to the load.
The order in which orders sit on the tab is their loading order — the sequence they will be loaded onto the vehicle in. Reorder them to match how the vehicle is packed, so what goes in last comes off first.
Adding, removing, and reordering orders is possible only while the plan is in Draft. Once the plan is marked ready to load, the list is locked (next phase). For which orders are eligible to ship, see outbound order statuses.
Phase 3. Marking ready to load
When the plan is complete, you hand it to the floor by moving it from Draft to Ready to Load on the plan's status bar. The app asks you to confirm the change.
A shipping zone must be set before the plan can leave Draft — that is where the load is gathered for loading.
Marking the plan ready to load locks its order list: orders can no longer be added, removed, or reordered. If you still need to change the load, send the plan back to Draft from the same status bar, make the change, and mark it ready again.
From here the work moves to the floor; the client becomes a monitoring surface for the loading (next phase).
Phase 4. Loading and dispatch
With the plan Ready to Load, the goods are loaded onto the vehicle. The hands-on loading — scanning the containers and goods as they go on board — is done on the handheld terminal, not from the client. The desktop monitors it.
As loading is recorded, each order's plan-versus-fact is filled in: the plan's execution snapshot shows, row by row, how much was actually shipped against how much was planned. The desktop only shows this snapshot — shipped quantities are recorded on the handheld, not typed in here.
Once loading is confirmed on the floor, the system moves the plan to Dispatched. This status is not set by hand from the client. As the plan is dispatched, its orders move to Shipped when everything ordered went out, or Partially Shipped when only part did.
Phase 5. Closure
After the load has gone, the plan reaches Closed — its final status. A closed plan is read-only: it stays as the record of what was dispatched, but nothing on it can be changed. Like Dispatched, this status is set by the system rather than by hand from the client.
Shipping without a plan: self-pickup
Not every order leaves on a planned vehicle. An order marked Self Pickup is collected by the customer directly and ships without a delivery plan — there is no load to assemble and no vehicle to schedule.
Self-pickup is a property of the order, not of a delivery plan, and the two are mutually exclusive: an order is either part of a delivery plan or marked for self-pickup, never both. The goods are still picked the usual way; when they are handed over, the shipment is recorded against the order itself. You follow it the same way as any other shipment — through the order's status (Shipped / Partially Shipped) and the Shipment list (next section).
Monitoring shipments
Every issue of goods — whether through a delivery plan or a self-pickup order — is recorded as a shipment: the fact of stock actually leaving the warehouse. The shipments themselves are recorded on the handheld terminal during loading; on the client, the Shipment list is where you monitor them.
Each shipment shows its status:
- Draft — the shipment is being recorded and has not been confirmed yet; nothing is posted to stock.
- Confirmed — the goods have been issued and stock reduced. The normal state of a recorded shipment.
- Cancelled — the shipment was reversed; any stock it issued is restored.
The list is read-only on the client — it is for watching what has gone out, not for recording it. For the full meaning of each state, see shipment statuses.
Business value
One load, planned and watched from one screen. The dispatcher gathers orders onto a vehicle, sets the loading order, and follows the load to dispatch — without leaving the workstation.
A clear line between planned and shipped. The execution snapshot shows what actually went out against what was planned, so short or partial loads are visible at a glance.
The floor does the lifting. Hands-on loading and scanning happen on the handheld; the client stays a planning-and-monitoring surface, and the order list locks once a plan is handed over so a load can't change underneath the team.