Arthur Ria
26 KiB
title, type, sources, related, last_compiled
| title | type | sources | related | last_compiled | |||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Shipping | concept |
|
|
2026-04-17 |
Shipping
Overview
Shipping is the end-to-end process of fulfilling customer orders: from order receipt through stock assignment, preparation (picking or container shipping), consolidation, truck loading, and closure. EasyWMS represents outbound work through shipping orders — the central document linking customer demand to warehouse operations.
Shipping orders typically arrive from the ERP via SOR messages but can be created manually from the web interface. For the canonical shipping order lifecycle and all statuses (Waiting, Reserved, Released, In Preparation, Paused, Closed/Archived, etc.) see Outbound Order.
Shipping Order
A shipping order (SO) represents a customer's purchase order, a supplier return, or an inter-warehouse transfer. It contains:
- Header: customer, carrier, dock, stage, consolidation location, load, route, wave/group, priority, dates
- Lines: item, UoM, requested quantity, logistic attributes (batch, expiration, etc.), required/rejected statuses, required container type
Shipping Order Types
| Type | Description |
|---|---|
| Standard | Normal outbound order for a customer |
| Return to supplier | Stock returned outbound to a supplier |
| Transfer | Inter-warehouse stock transfer |
| Desk order | Stock requested from a retail desk inside the warehouse |
Shipping Order Lifecycle
| Status | Meaning |
|---|---|
| Created | Order received/created; no stock assigned yet |
| Released | Stock assigned; tasks generated for preparation |
| In preparation | Active picking/shipping tasks being executed |
| Prepared | All lines prepared; stock at dock/stage waiting for loading |
| Loaded | Stock loaded onto transport |
| Closed | ERP notified of shipped quantities; documentation issued |
| Archived | Historical record; no further modifications allowed |
Order Management Operations
| Operation | Description |
|---|---|
| Create (manual) | Manually create from web interface (rare; for ERP downtime or special requests) |
| Edit lines | Increase/decrease/cancel lines during preparation (ERP changes if received from ERP) |
| Assign stock | Manually trigger stock assignment before release |
| Reserve stock | Pre-reserve specific stock or maximum available for an order or account |
| Assign dock/stage | Manually assign shipping dock or staging area |
| Assign PK/MP (automatic WH) | Assign picking conveyor + preparation zone for automatic warehouse picking |
| Assign PS group | Assign outbound conveyor group for automatic warehouse shipping |
| Stop | Freeze order at a configurable point; prevents further modifications |
| Pause | Temporarily halt preparation; assigned stock retained |
| Restart | Resume paused order; tasks generated to continue with held stock |
| Cancel | Cancel order (if not fully prepared); stock released; ERP notified |
| Close | Finalize partially-prepared order; confirm shipped quantities to ERP |
| Archive | Move to historical records |
| Mix orders | Configure strategies to mix different orders in same client container |
Order Release
Releasing an order is the trigger that moves it from "Created" to "In Preparation":
- Assign stock: system selects specific stock for each line (see Picking for assignment strategy details)
- Assign PK/MP (automatic warehouses): if auto-assignment configured, picking conveyors and preparation zones are allocated
- Generate tasks:
- Picking tasks for all lines with stock in picking locations
- Shipping tasks (full container moves) for stock in locations that allow shipping
- If dock/stage assigned: loading tasks to move prepared stock to dock/stage
Tasks are created in parallel as stock is assigned, following line number order, except when:
- Some lines are marked critical or required for shipping (inter-line dependencies)
- Negative picking conditions are met (excess must be extracted before picking)
- Sequencing rules require specific task ordering
Release can be:
- Manual: warehouse manager selects orders in web UI
- Automatic: order has auto-release date/time set, or is triggered by a shipping template
ERP message sent: SOC (order status change)
Transaction recorded: OUT.CST
Parameter: MAX_AUTORELEASED_OUTBOUNDORDERS — maximum orders auto-released simultaneously
Release by Sub-warehouse
For warehouses with multiple sub-warehouses, orders can be released sub-warehouse by sub-warehouse. Each sub-warehouse release generates tasks only for its stock. ERP is notified of each sub-warehouse release.
Grouping Strategies (Waves, Groups, Fusions)
Grouping shipping orders reduces operator travel by combining multiple orders into a single picking round.
Groups
Multiple shipping orders are picked together (same picking path). After picking, stock is ungrouped at an ungrouping station (UAP) to separate each order's stock into its own containers.
- Manual or automatic creation (via shipping templates)
- Include/exclude orders after creation
- Close and archive when last order is ungrouped
- Cancel: prepared stock released; orders must be re-prepared separately
Fusions
Multiple shipping orders are shipped together without ungrouping — typically for orders going to the same customer. Picked stock can be placed in shared containers without redistribution.
Waves
Each wave fills operators' equipment to maximum capacity. Orders in a wave can be included fully or partially (by lines). Waves can be:
- Grouped (stock ungrouped at UAP after picking)
- Ungrouped (stock distributed directly on equipment during picking)
Special case: if all wave orders are "Single Units" with the same destination, ungrouping station is bypassed.
Operators select which wave to execute (from released waves). Wave closes automatically when all included orders are archived.
Shipping Templates
Automation mechanism that selects orders matching configured criteria and:
- Creates groups, fusions, or waves automatically
- Assigns ungrouping station
- Releases the grouping
Templates are defined from Configuration → Modèle d'expédition and follow a sequence-number priority (lower = higher priority, identical to putaway strategies).
Common base fields (every template type) :
| Field | Description |
|---|---|
| Code | Template code |
| Prefix | Group/wave name prefix |
| Priorité | Priority of the created wave/group |
| Mode d'assignement | Auto release / manual release |
| Nb max de groupes créés | Cap on active groups/waves |
| Nb max de groupes libérés | Cap on groups/waves in preparation |
| Trié par | Order in which orders are consumed (recommended : creation date ASC) |
A stock-assignment strategy and/or a prepackaging strategy can be attached to the template.
Per-type tabs :
- Picking d'ordres groupés : grouping criteria (carrier, mono-ligne, mono-unité, critère personnalisé), group size (max orders / lines / volume), filters (stock rangé, crossdocking, UdM, critère perso), ungrouping (UAP + packing buffer), minimum conditions (min qty, min orders).
- Vague de picking : carrier + critère perso ; max orders, volume, UdM, min orders. Checkbox "Generate tasks on release" — if set, tasks are created when the wave is released ; otherwise at operator pickup time.
- Picking d'ordre : for single-order templates. Filters on UdM + critère perso only.
Scheduler. Templates can run between two hours on selected weekdays, with a configurable interval in minutes. Two daily windows (e.g. 9–10h and 15–16h) require duplicating the template.
Criteria are mandatory (at least one per template). Each criterion rejects orders that don't match — two tabs are available :
- Ordre d'expédition : Code, Description, Type (
Customer,Transfer,DirectTransfer,Fabrication,Manuel,Retour…), Class, Owner, Mono-ligne, Mono-unité, Follow sequence, Auto-release, Carrier, Transport type, N hours before release/loading, N hours late, Country/City/Postal code. - Ligne d'ordre d'expédition : item type, item family, danger, stackability, voluminous, single parcel.
Critère personnalisé — LINQ syntax :
// Criterion on the outbound order itself (ex: orders imported with source = "WEB")
o.Source == "WEB"
// Criterion on an outbound order line
l.Item.ItemType.Code == "FROID"
Prepackaging
Prepackaging calculates the number and type of client containers (cartons, pallets) needed to ship an order before picking begins, maximizing container utilization.
| Prepackaging source | Description |
|---|---|
| Calculated by EasyWMS | System uses item dimensions + available container formats to compute optimal packing |
| Calculated by ERP | ERP sends container count/type via messaging before release |
| Calculated by operator | Operator manually enters container count (for small warehouses) |
When prepackaging is applied:
- During picking: system guides operator on which container to use for each item as picking progresses
- During consolidation: at a packaging stage/consolidation station, system guides stock redistribution into computed containers
Consolidation
Consolidation redistributes prepared stock from multiple source containers (or loose stock) into final shipping packages, optimizing the number of outbound containers.
Typical need: order prepared from multiple origins (manual + automatic aisles, different work areas), resulting in many partial containers. Consolidation combines them.
Setup: consolidation station (buffer-type location) must be assigned to the shipping order before release. After release, any picked/shipped containers are sent to the consolidation station automatically.
Detailed prepackaging mechanics, tested behaviors, and the SOR02
<PrepackagingConfiguration>structure are covered in Prepackaging.
Process (at conveyor):
- Operator at consolidation station scans source container SSCC
- System guides transfer of stock into destination container(s)
- Empty source containers are deleted if configured; task cancellation follows
Transactions:
CON.CREATE— new consolidation container createdSTK.MOVE— stock moved from source to destinationCON.DELETE— empty source container deletedTSK.CANCEL— tasks for deleted container canceled
HPKS (laser pick-term tray) illuminates the destination division for easy identification.
Routes
Routes group shipping orders when containers must be loaded in stop sequence so they can be unloaded at each delivery stop without rearranging.
Route structure: Route → Stops → Shipping orders per stop
Route management operations:
| Operation | Description |
|---|---|
| Create | Manual or from ERP messaging |
| Assign dock/stage | Set staging area and loading dock |
| Release | Begin preparation of all included orders; ERP notified |
| Monitor | Track progress; pause/stop/change priority |
| Include/exclude orders | Add or remove orders during preparation |
| Modify stops | Change stop numbers / order sequence |
| Pause/Resume | Pause route; ERP notified of paused orders |
| Stop/Restart | Stop route; ERP notified; restart resumes with held stock |
| Close/Archive | Close after last stop loaded; print transport documents |
| Cancel | Cancel route; decide if included orders continue as separate SOs |
Important: route loading must respect stop order. RFT warns operator if container is loaded in wrong sequence.
RUT File (TMS-driven Routes)
When route sequencing is planned by a TMS, the ERP sends a RUT file instead of individual SOR messages. The RUT carries a route header plus all the constituent orders, each tagged with its stop number. The loading discipline is inverse to stop number : the container destined for the last customer is loaded first, so unloading proceeds naturally stop after stop.
Operational flow :
- Integrate the RUT file. Orders appear in the orders view but must be handled from the routes view — releasing them individually is not the nominal path.
- Launch the route → each order is auto-released with its stock assignment.
- Prepare the orders in any convenient internal order.
- Create a truck load and attach it to the route. A template can create the load automatically at route release.
- ⚠️ The load must have a dock before truck loading can start.
- RFT truck loading. Scan containers in the expected sequence (
n_max→n_max-1→ … →1). Scanning a container with the wrong stop number prompts a warning asking whether to proceed anyway.
💡 Custom idea repeatedly requested by customers : display the next expected container on the RFT so the operator can target it directly on the staging area.
Loads
Loads represent a physical transport vehicle (truck, van) that will carry one or more shipping orders or one route.
| Load type | Description |
|---|---|
| Planned | Created in advance; specific orders assigned; only assigned containers/stock can be loaded |
| Unplanned | Created "on the fly" at loading time from RFT; orders must allow unplanned loading |
| Route loads | One route per load; containers must be loaded in stop sequence |
Load Lifecycle
- Create load (manual or auto on order release)
- Assign dock
- Assign orders/routes
- Load containers/stock/packages (via RFT)
- Close load → ERP notified, transport documents printed
Load operations:
- Monitor (detect incidents, check progress)
- Pause / Resume loading
- Unload container/stock (if loading error)
- Undo preparation (release stock back to warehouse)
- Remove excesses (if order quantities changed after preparation)
- Partial close (close without all containers loaded, if configured)
- Auto-close (triggered automatically when last container/package is loaded)
Multi-zone Loading (Virtual Dock)
Warehouses with multiple storage/preparation areas can use a virtual dock — a common dock reference for all zones. Carriers collect stock from different physical zones, but all are referenced to the same virtual dock for tracking purposes.
Truck Loading — SmartUI configuration reference (Mecalux France)
Standard EasyWMS exposes two truck-loading modes at dock level :
- No buffer — order auto-ships as soon as it lands on the dock
- Buffer + dock — an intermediate control step validates pallets against the load before shipment
Load creation modes (per order type: unitary, route, group, merged, wave, by carrier):
| Mode | Description |
|---|---|
| Automatic (planned) | Load created at order release; strict container control (scanning a container from another order raises an error) |
| Non planifié | Load created at release; no container control |
| Manuel (planned) | Load created manually; strict container control |
| RFT — manual, no control | Created from RFT; no container control (indicative only) |
| RFT — from a route | Load tied to an existing route |
EasyS minimum: one buffer + one dock per dock used. The buffer can be carried in <PrpPackingLocation> on SOR02, or assigned manually via SmartUI Ordres de sortie → "Assigner quai/poumon".
SmartUI — Configuration → Chargements:
| Option | Effect |
|---|---|
| Truck plate number | Mandatory / Not required / Optional |
| Seal number | Mandatory / Not required / Optional |
| Auto-close | Close on last container loaded → stock exit + order close |
| Partial close | Allow closing with uncharged containers; a remainder load is auto-created (codes suffixed _2, _3, …) |
| Quantity validation | Same semantics as picking |
| Allow load of all stock | Adds a RFT button to load all free stock in one action |
RFT — create a load from the floor: Ordres de sortie → Chargement camion → Charger les conteneurs → Nouveau. To disable this path, set every order-type mode to something other than "Non planifiée". As soon as one type is "Non planifiée", operators can create loads from RFT.
RFT — execute a load (EasyWMS.TruckLoad_GetLoads_UI):
Ordres de sortie → Chargement camion → Charger les conteneurs- Filter by dock/buffer or by load
- Select the load (status
Ready to loadif the whole order is prepared) - Scan pallets — button "Conteneur" lists remaining containers ; "Effectuer" closes the load even if pallets are missing
ℹ️ During loading the load status reads "Loading" (red on RFT).
Delivery-note printing at load close: when the BL is configured to print on order close, closing the truck load triggers the print — including for a partial close. On a two-step load (remainder), the BL is printed at each close and always covers all shipped lines of the order.
Truck unloading (RFT): menu Décharger les conteneurs → scan the container → scan the drop-off location (default: the end-of-preparation buffer).
Order Merge vs Load
Truck loading handles loads — merging happens before load creation on the shipping orders themselves. A merged order behaves as a single order when assigning a load, but ERP traceability remains per-original-order (see Outbound Order → Merge).
Truck Loading (RFT Process)
Operators at the dock register each item loaded using the RFT:
Containers
- Planned: load only containers from assigned orders
- Unplanned: create load on the fly; scan any container
- Route: enforce stop-order loading; system alerts if wrong sequence
- Stacked containers: load stacked units to maximize truck height utilization
- Direct to dock: containers automatically considered loaded when they arrive at dock (no explicit RFT scan)
Stock (loose stock)
- Similar to containers but for non-containerized stock
- Cannot be used for routes (routes require container-level tracking)
- Direct to dock variant supported
Packages (Multi-Carrier)
- Packages (parcels with carrier labels) are scanned for loading
- Carrier must match load's carrier assignment
- Packages can be in containers; containers with packages are loadable as a unit
- If carrier allows: undo preparation, reject package
Common loading events:
- Excess detection: if order was reduced after preparation, operator is guided to remove surplus before/during loading
- Auto-close: last item loaded triggers close process (seal registration, report collection)
- Partial close: configured to allow closing without all units loaded
PS Groups (Automatic Warehouse — Outbound Conveyors)
PS (Pallet Shuttle or outbound conveyor) groups are logical groupings of outbound conveyors in automatic warehouses. Each group configures which PS stations belong to it and how they are filled (criteria for which PS station gets the next container).
- One PS group can be assigned per shipping order/route
- Manual or auto assignment
- Containers arriving at PS conveyors are shipped (manually or automatically)
- PS group shipping flow: containers arrive at configured PS stations → shipped in configured order
Inventory After Picking
At the end of picking (last task from a location/container), EasyWMS can ask operators to verify if the location/container is now empty, enabling continuous inventory. Configurable behavior:
- If operator says empty: stock adjustment (reduces inventory to zero)
- If operator says not empty: location/container marked for review (count triggered)
Shipping Order Mixing
Multiple shipping orders can be merged into the same client container if they meet configured mixing strategy conditions (e.g., same customer, same carrier, same delivery date range). Mixing strategies define the compatibility criteria.
ERP Integration
| Message | Direction | Trigger |
|---|---|---|
SOR (inbound) |
ERP → WMS | Shipping order creation/update from ERP |
SOC (outbound) |
WMS → ERP | Order release; status change (stock assignment) |
SOF / SOF02 (outbound) |
WMS → ERP | Order fulfilled / partial fulfillment with differences |
LOF (outbound) |
WMS → ERP | Load closed; transport details sent to ERP |
See ERP Interface for full field tables and variants (SOR01/SOR02, SOF01/SOF02).
Transactions
| Transaction | Trigger |
|---|---|
OUT.CST |
Shipping order release |
STK.PICKING |
Picking task executed |
STK.SHIP |
Shipping task (full container extracted) |
CON.LOAD |
Container loaded onto transport |
STK.LOAD |
Loose stock loaded onto transport |
CON.CREATE |
New client/consolidation container created |
CON.COC |
Client container closed |
STK.MOVE |
Stock moved (consolidation) |
CON.DELETE |
Empty container deleted |
Parameters
| Parameter | Description |
|---|---|
MAX_AUTORELEASED_OUTBOUNDORDERS |
Maximum shipping orders auto-released at the same time |
ALLOW_CONFIRMATION_ON_PLACEMENT |
Operator confirms destination container at picking deposit |
EMPTY_PICKING_LOCATION_QUESTION |
Ask if location/container is empty after last pick |
EMPTY_PICKING_LOCATION_STOCK_ADJUST |
If empty confirmed: adjust stock (true) or mark for review (false) |
Common Errors
Order stays in "Created" after release attempt: Stock assignment failed for all lines (no eligible stock). Check: stock statuses allow picking, locations not locked, no active count tasks, picking dedicated locations configured if needed.
Tasks generated but no operator picks up: Tasks assigned to specific equipment that isn't active, or operator logged into wrong zone/sub-warehouse. Check equipment assignment on the order; clear if not needed.
Route containers loaded in wrong order: Operator ignored system warnings or system route stop not correctly configured. Route stop numbers must be in reverse delivery sequence (last stop loaded first) for efficient unloading.
Consolidation station not receiving containers: Consolidation station assigned after order release. Must be assigned before release for existing prepared containers to be re-routed. Only new container movements will go to the station post-assignment.
Load closed without all containers: Partial close was triggered or configured. ERP receives load-close notification; missing containers must be tracked manually or re-assigned to a new load.
Order mixing containers rejected: Two orders cannot mix due to mixing strategy conditions (different customer, incompatible logistic attributes). Check mixing strategy criteria and adjust or create a different strategy for these order types.
PS group not releasing containers to outbound: PS group not assigned to the order, or all PS stations in the group are locked. Assign PS group or unlock stations.
Interface Paths
| Interface | Path |
|---|---|
| Web — shipping orders | Menu "Shippings" → "Shipping orders" |
| Web — routes | Menu "Shippings" → "Routes" |
| Web — loads | Menu "Shippings" → "Loads" |
| Web — waves | Menu "Shippings" → "Waves" |
| Web — groups/fusions | Menu "Shippings" → "Groups" |
| Web — shipping templates | Menu "Configuration" → "Shipping templates" |
| Web — PS groups | Menu "Control" → "PS groups" |
| RFT — truck loading | Menu "Shipping" → "Load truck" |
| RFT — consolidation | Menu "Shipping orders" → "Packaging" |
Related
- Picking — picking is the core preparation activity within the shipping process
- Replenishment — picking dedicated locations are replenished when stock runs out during order preparation
- Container (LPN) — containers are the main unit tracked through shipping, loading, and delivery
- Crossdocking — some shipping orders can bypass storage through crossdocking
- Reception — inbound stock feeds the inventory that shipping orders consume
- Outbound Order — shipping orders (SOR/SOF/SOC) drive the entire shipping process; order type determines destination and process
- Task — shipping generates Shipping and Loading tasks; task priority inherits from order priority
- cutting-stock — cutting stock has special shipping profile requirements (excess %, enter quantity mode = Manually)
- stations — Dock (type 34), Stage (type 33), PS (type 4), Consolidation (type 17) stations are central to shipping
- Prepackaging — dedicated page for prepackaging strategy configuration, ERP (SOR02) payload, and tested behaviors