Pack station
Overview
At the pack station it is verified that everything really is in the box — line by line, by scan. That is a work step with its own intermediate state: half scanned, one parcel closed, the second one open. A delivery note has no intermediate state; it comes into being at the end, once it is settled what actually leaves the building.
One packing session per order. Even when the goods arrived via a multi-order pick list: packing is done order-clean, because the box goes to exactly one customer.
The pack station is operable without a mouse — both scan fields accept Enter and keep the focus afterwards.
Core tasks
Identify. Scan what is on the paper: order number or pick list number. The step is idempotent — scanning the same shipment twice does not open a second session, it returns the same one.
Scan the lines. Accepted are product number, EAN and packaging-unit EAN; a packaging-unit scan books its contents in one go. Goods that do not belong to the order — or whose line is already complete — are rejected. Catching exactly that wrong item is the point of the pack station.
Close the parcel. Per parcel, weight, packaging and dimensions are recorded. The weight follows the three-step weighing policy (setting wms.weighing.mode):
required— it must be weighed, otherwise no completion.prefill— a stable reading from the workplace scale is proposed; if there is none, the system
computes it from the product weights plus a surcharge.
none— it is only computed.
A value you type in always wins. Either way the result is a positive number — no carrier accepts a label request without a weight.
Complete. The delivery note is built from the quantities actually scanned, reported as picked and shipped — which is what buys the label. See Shipping and Printing & workplaces.
Fields in detail
The What it does column answers what changes in the system — not what the field is called. The grey name behind the label is the API field: the same thing runs under that name through automation, import and AI tools.
Pack station
| Field | Required | Values / format | What it does |
|---|---|---|---|
Scan scan | yes | barcode | The way in: order, pick list or article. Every scanned article is checked against the order — what does not belong is rejected instead of quietly travelling along. |
Carrier carrierPluginKey | yes for a label | a configured carrier | Who ships. The choice follows the configured connections, not preference. |
Service service | no | the carrier's service | Standard, express, bulky goods … It determines price and transit time of the label. |
Only when every item is confirmed can the shipping label be drawn. That is the real safeguard of the pack station: no incomplete shipment gets a label.
Settings & permissions
- Module
module.wms. wms.pack.execute— scan, pack, ship. The right is granted to no role by default.wms.weighing.mode(none·prefill·required) plus a weight surcharge in grams and in
percent — system settings, not brand-specific.
- The scale belongs to the workplace, not to the account: the scale reading is queried per
workplace key (for example packtisch-1).
- Without a connected scale the weighing policy stays fully usable — the computed weight then
carries the pre-fill.
FAQ & troubleshooting
Scanning the pick list number fails with a conflict. The list contains several orders. Which one is meant cannot be guessed — scan the order number.
A product is rejected. It does not belong to this order, or its line is already fully scanned. Both are a wrong item, not an operating error.
Completion is refused. Not everything has been scanned. A partial shipment is possible but must be allowed explicitly — the half-filled box is precisely what the pack station exists to prevent.
A weight is missing. With the policy on required the field is mandatory. On prefill and none the system computes it from the product weights plus surcharge.
Packed on a handheld — a different path? No. The scanner uses the same backend path; only the scale stays at the pack station.