mcp-wms-wiki/wiki/concepts/reception.md

---
title: "Reception"
type: concept
sources:
  - areas/receptions/index.md
  - areas/receptions/reception_dock/index.md
  - areas/receptions/reception_dock/supplier_container.md
  - areas/receptions/reception_dock/blind_container.md
  - areas/receptions/reception_dock/return.md
  - areas/receptions/reception_asn/asn.md
  - areas/receptions/reception_pie/pie_recep_point.md
  - areas/receptions/reception_pk/pk_recep_point.md
  - areas/receptions/reception_admin/receipt_orders.md
  - areas/receptions/reception_admin/receipt_close.md
  - sources/archives/18_ASN_DirectTransfer.md
  - sources/archives/19_ASN_Transfer.md
  - sources/archives/29_Split_marchandise_reception.md
related:
  - concepts/container.md
  - concepts/order-inbound.md
  - concepts/putaway.md
  - concepts/stock.md
  - concepts/product-item.md
  - concepts/quality-control.md
  - concepts/erp-interface.md
  - concepts/transactions.md
  - concepts/labels.md
last_compiled: "2026-04-17"
---

# Reception

## Overview

Reception is the process by which stock physically arrives at the warehouse and is formally registered in EasyWMS. Until a receipt is completed and closed, the arrived stock does not exist for any other WMS process (picking, replenishment, shipping). Reception is therefore the entry gate between the physical world and the logical warehouse state.

EasyWMS supports five distinct reception entry points - each suited to a different physical configuration and information context: **Dock** (manual, RFT-driven), **ASN** (pre-notified containers), **PIE** (automated sensor gate), **PK** (picking conveyor), and **Returns** (customer returns). All share the same fundamental structure: a **Receipt** groups received stock lines, and optionally links to a **Receipt Order** (planned) or generates one ad hoc (blind).

The reception output is always a REF message to the ERP confirming what was received, and an ASO message (for pre-notified containers) or similar notification per entry point.

---

## Receipt Document Structure

### Receipt

A receipt is a document that groups all the stock received in a physical delivery. It can be linked to one or more receipt orders, or created standalone (blind/return).

| Property | Description |
|---|---|
| Code | Auto-generated or user-defined |
| Status | Created → In progress → Closing → Closed |
| Receipt order(s) | One or more inbound orders this receipt covers |
| Lines | One line per unique (item, UoM, logistic attributes, status) combination received |

A receipt is created:
- Automatically when the first container of a receipt order is received (if `AutoCreateReceptionFromRecOrder` active)
- Manually by the user from the web interface or RFT (if `ALLOW_CREATE_RECEPTION` active)
- Automatically and transparently by PIE for blind entries

### Receipt Order

A receipt order represents planned incoming stock from the ERP. Received via `ROR` message.

**Header attributes:**

| Property | Description |
|---|---|
| Code | Inbound order code |
| Status | Created → Partially received → Completed → Closed |
| Type | Supplier / Return / Transfer |
| Class | Functional classification (affects logistics treatment) |
| Owner | Mandatory if Owner Extension module installed |
| Supplier | For supplier-type orders |
| Account | For return-type orders |
| Source | Source warehouse for transfer-type |
| Allow lines auto-creation | Whether unexpected items can be received against this order |
| Enable container label printing | Print GS1-128 container labels during receipt |
| Enable stock label printing | Print GS1-128 item labels during receipt |
| Single receipt | Only one receipt auto-created for this order |

**Line attributes:** Item code, UoM, quantity, logistic attributes, stock status, container (optional), number of ERP parcels.

At close of receipt: `REF` sent to ERP. At close of receipt order: `ROF` sent to ERP.

---

## Reception Modes

### 1. Dock Reception (Manual / RFT)

Used for stock arriving physically at a warehouse dock. Operators use an RFT to receive stock.

#### Supply Reception (Supplier)

Stock arriving from a supplier against a receipt or receipt order.

| Sub-mode | Description |
|---|---|
| Multi-SKU LPN (multi-reference) | LPN contains multiple different items. Putaway on equipment or in a stage. |
| Single-SKU LPN (non-identical) | LPN with one item, labeled or not. Supports logistic attribute capture and status. |
| Single-SKU LPN (identical) | All LPNs contain same item and logistic attributes; can receive variable qty. |
| Loose stock | Stock received without a container, placed directly in a stage. |
| Cutting stock | Special flow for indivisible/measured stock (rope, cable, etc.). |

Two putaway modes for all sub-modes:
- **Receipt and putaway**: Stock received on equipment → immediate location search.
- **Receipt on stage**: Stock registered in a stage → putaway done later.

Supports **exclusive reserve** at receipt time: stock received can be pre-reserved for a specific shipping order or route (via `ROR` with reserve). The `CONFIRM_EXCLUSIVE_RESERVE_ASSIGNMENT` parameter controls whether the user must manually select the order when multiple compatible orders exist.

**ERP messages:**
- Receives: `ROR` (receipt order), optional `ASN`
- Sends: `REF` at close

**Transactions:** `CON.RECEP` per container, `STK.RECEP` per stock line.

**RFT path:** `Receipts > Supplier > Loose stock/multi-reference`

#### Blind Reception

Unplanned stock with no prior notification or entry order.

- A receipt is automatically created (and closed at end) - transparent to the user.
- The receipt cannot be created or edited from the WMS UI.
- Supports: multi-reference LPN, single-SKU LPN (labeled/unlabeled/identical), loose stock, cutting stock.
- Communicates to ERP via `REF` after blind receipt close.

**RFT path:** `Receipts > Blind`

#### Returns Reception

Customer-returned stock coming back to the warehouse.

- Can be linked to a receipt order (if created from the web) or not (if created from RFT).
- If created from RFT: no lines initially - lines are added as stock is received.
- Date logistic attributes (expiry, shelf life) are captured but **not validated** - expired stock may be returned and must be managed after receipt.
- Supports: containers, loose stock, cutting stock, exclusive reserves.
- Custom code prefix configurable: `RETURN_RECEPTION_PREFIX`

**ERP messages:** `REF` at close.
**RFT path:** `Receipts > Return`

---

### 2. ASN Reception (Pre-notified Containers)

Used when the ERP has pre-notified containers via `ASN` message before they physically arrive. The containers exist in the virtual **ASN location** with status _Pending receipt_ until physically received.

**Variants:**
| Variant | Description |
|---|---|
| With receipt order | Container explicitly linked to an existing receipt order |
| Without receipt order | Pre-notified but no receipt order; received without receipt association |
| Stacked containers | Hierarchy of stacked/matched containers; `RECEPTION_ASN_CONFIRM_ALL_STACK_CONTAINERS` controls whether all must be confirmed |
| Direct warehouse transfer (same org, near) | Containers transferred without truck; receipt order not created |
| Indirect warehouse transfer (same org, distant) | Transfer needs truck; receipt order created at destination |
| Two simultaneous receipts (same order) | Stock arrives in two trucks; operator creates separate receipts |
| Multiple identical lines | Order lines with same stock merged; quantities split at receipt close |
| Sequential channel storage | Containers for same shipping order/route stored together via channel-fill strategy |
| Dummy containers | ERP notifies quantity without SSCC; dummies created, updated at PIE |
| Exclusive reserve (ASN) | Entire container reserved for one shipping order |
| Exclusive reserve (ROR) | Partial stock reserved for one or more orders |
| Without stock information | Container pre-notified without stock content; exclusive reserve mandatory |

**Stock review at receipt (ASN):**
- `RECEPTION_ASN_SHOW_CONFIRMATION_DIALOG`: if active, user can review/adjust/reject container stock before confirming receipt.
- On rejection: `RECEPTION_FORBID_MOVE_FROM_ASN` controls whether container stays in ASN (true) or moves to Lost&Found and sends `ASK` (false).

**Strict mode for exclusive reserves:**
- `USE_EXCLUSIVE_RESERVE_STRICT_MODE`: if active, receipt blocked when shipping order/route referenced in reserve doesn't exist.

**ERP messages:**
- Receives: `ASN` (pre-notification)
- Sends: `ASO` on receipt, `ASK` on rejection, `REF` on receipt close, `ROF` on order close

**Transactions:** `CON.CREATE` + `STK.CREATE` when ASN received, `CON.ASN.001` + `STK.ASN` at receipt, `CON.MOVE` + `STK.MOVE` for location change, `CON.DELETE` + `CON.CNL.ASN` on rejection.

**UI paths:**
- Web: `Warehouse > ASN LPN`, `Receiving > Receipt orders`
- RFT: `Receipts > Notices`

#### DirectTransfer - inter-warehouse ASN flow

When the source order is a `<DirectTransfer>` shipment (cf. [concepts/order-outbound.md](../concepts/order-outbound.md#asn---directtransfer-flow)), closing the expedition at origin triggers an automatic `ASO01` message on the destination warehouse, pre-creating the incoming ASN container(s). The operator then receives them via RFT menu **Réception → Préavis** just like any other ASN container.

- Container deletion from SmartUI (`Entrepôt → Conteneurs ASN → Supprimer`) triggers an `ASK01` back to the ERP.
- ⚠️ The ASO/ASK messages carry **no reference to the originating shipping order or DirectTransfer header** - only the container and its stock.

#### Transfer - two-warehouse ASN flow (with receipt)

Unlike `<DirectTransfer>` (which bypasses reception at destination), a `<Transfer>`-type shipping order (`SorType = Transfer` in SOR02) **automatically creates an inbound order at destination** when expedition is confirmed at source. The destination ASN containers live on an `Asn` location in the destination warehouse.

| Setting (destination warehouse) | Effect |
|---|---|
| `AutoCreateReceptionFromRecorder = true` | A reception is created automatically when the first container is read. Otherwise the operator creates it manually. |
| `AutoCloseInboundOrder = true` | Closing the reception auto-closes the inbound order and generates `ROF02`. |

Operator flow: RFT menu **Réception → Préavis** (of the destination warehouse) → scan each container → close.

**ERP messages generated:**
- `ASO01` at each container reception
- `ROF02` at inbound order closure (contains **all** received containers - the authoritative record for Transfer receptions)
- `ASK01` when closing a partially-received inbound order (to drop non-arrived containers)

> ⚠️ Neither `ASO01` nor `ASK01` carries the transfer header info. For `<Transfer>` flows the ERP **must** consume `ROF02`.

Used in production at RAUD: transfers from hub LRM to spoke sites (MOR, LAM, …).

---

### 3. PIE Reception (Automated Entry Station)

The **PIE** (Pallet Identification Entry) is an automated gate station for automatic warehouses. It reads LPN labels automatically via scanner, validates dimensions/weight/condition, and routes containers into the warehouse or to a rejection/reconditioning station.

**Modes:**
- **Automatic PIE**: reads labels automatically; on error, diverts to rejection.
- **Semi-automatic PIE**: operator scans label manually when auto-read fails; container waits at station.

**PIE reception variants:**
| Variant | Description |
|---|---|
| Blind (unknown) container | Container not pre-notified; PIE auto-creates blind receipt transparently; closed at end. |
| Pre-notified, without receipt order | `ASN`-notified container, no linked receipt order; `ASO` sent at receipt. |
| Pre-notified, with receipt order | Container linked to receipt/order; ALLOW_CREATE_RECEPTION controls auto-creation; `REF`+`ROF` sent at close. |
| Exclusive reserve | Container with reserved stock; `USE_EXCLUSIVE_RESERVE_STRICT_MODE` controls behavior when order doesn't exist. |
| Without stock info | No stock in `ASN`; exclusive reserve required; routed via inbound conveyors. |
| Half pallets | Two half-pallets on a base pallet; slave/dummy container created; `Use slave container` setting in PIE config. |

**Rejection/Reconditioning routing:**
- If container has issues (dimensional, labeling): diverted to rejection or reconditioning station.
- At reconditioning, operator resolves issue and retries.
- Container considered **received** (ASO sent) if issue is dimensional/physical.
- Container **rejected** (receipt not possible) if receipt order data is missing or incompatible.

**Configuration:**
- PIE working mode: Automatic / Semi-automatic
- Auto container creation: enabled in EasyS or via `Stations` view action "Allow create container"
- Number of labels: max barcodes per GS1 label
- Avoid moving from ASN: per-station toggle

**ERP messages:** `REF` (blind close), `ASO` (pre-notified receipt), `ASK` (rejection)

**Transactions:** `CON.CREATE` + `STK.CREATE` (blind), `CON.ASN.001` + `STK.ASN` (pre-notified receipt), `CON.MOVE` + `STK.MOVE` (location change)

**UI path:** `Control > Stations` (web)

---

### 4. PK Reception (Picking Conveyor)

Pre-notified containers received via a **Picking Conveyor (PK)** workstation in automated warehouses.

- Container code scanned from workstation → container introduced into warehouse via inbound conveyors.
- Variants: with or without receipt order, stacked/matched, with/without divisions.
- If receipt order linked but doesn't exist: operator offered choice to continue (as no-order receipt) or leave container in ASN.
- `ALLOW_CREATE_RECEPTION`: controls auto-receipt creation from PK.
- `AutoCloseReception` / `AutoCloseInboundOrder`: control auto-closing.

**ERP messages:** `ASO` at receipt, `ASK` on rejection, `REF`+`ROF` at close.

**UI path:** `Picking` workstation → `Enter containers`

---

## Receipt Closing

Receipts can be closed **manually** or **automatically**.

### Manual Closing

- Done from web interface or RFT at any time - full quantity not required.
- If linked to receipt orders and all ordered stock received → receipt order = _Completed_; else = _Partially received_.
- Stock allocation across identical order lines follows: least expected qty first → oldest creation date → excess to first line allowing it.
- Process: `Reception_Close_PR_V2`

### Automatic Closing

- Triggered when all expected stock has been received and no excess allowed.
- Parameter: `AutoCloseReception`
- Same allocation logic as manual.

**Communications at close:** `REF` to ERP.
**Transactions:** `REC.CLS` (receipt close), `INO.CST` (receipt order close, if linked).

---

## Parameters

| Parameter | Effect |
|---|---|
| `ALLOW_CREATE_RECEPTION` | Allows creating a receipt from RFT/PIE/PK if none found |
| `AutoCreateReceptionFromRecOrder` | Auto-creates receipt when receipt order stock still pending |
| `AutoCloseReception` | Auto-closes receipt when all expected stock received |
| `AutoCloseInboundOrder` | Auto-closes receipt order when receipt closed (valid status required) |
| `RECEPTION_ASN_SHOW_CONFIRMATION_DIALOG` | Show stock review/adjust/reject dialog after reading ASN container |
| `RECEPTION_FORBID_MOVE_FROM_ASN` | If true, rejected ASN container stays in ASN; if false, moves to L&F |
| `RECEPTION_ASN_CONFIRM_ALL_STACK_CONTAINERS` | All containers in a stacked hierarchy must be confirmed |
| `USE_EXCLUSIVE_RESERVE_STRICT_MODE` | Blocks receipt if reserve's shipping order doesn't exist |
| `CONFIRM_EXCLUSIVE_RESERVE_ASSIGNMENT` | User must manually select shipping order for exclusive reserve when multiple compatible |
| `CREATE_ALIAS_ON_RECEPTION` | Allows declaring a scanned code as an item alias at receipt |
| `RECEPTION_DEFAULT_CONTAINER_TYPE` | Default LPN type suggested at receipt |
| `RECEPTION_DEFAULT_HEIGHT_TYPE` | Default height type suggested at receipt |
| `RECEPTION_NUM_DAYS_PRODUCTION_DATE_MARGIN` | Future production date margin allowed at receipt |
| `RETURN_RECEPTION_PREFIX` | Custom prefix for return receipt codes |
| `SKIP_RF_CONFIRMATION_MESSAGES` | Hides receipt/order close confirmation messages on RF |
| `MAX_RECEPTIONS_TO_CLOSE_JOB` | Max receipts in _closing_ status selected per job run |
| `NUM_EVENTS_PER_PARTIAL_COMMIT` | Events confirmed per block in closing process |

---

## ERP Integration

| Message | Direction | Trigger |
|---|---|---|
| `ROR` | ERP → WMS | Creates/updates receipt orders (Receipt Order Request) |
| `ASN` | ERP → WMS | Pre-notifies containers and their stock |
| `ASO` | WMS → ERP | Confirms receipt of a pre-notified container |
| `ASK` | WMS → ERP | Confirms rejection of a pre-notified container |
| `REF` | WMS → ERP | Receipt close confirmation - lists all received stock |
| `ROF` | WMS → ERP | Receipt order close confirmation |
| `STV` | WMS → ERP | Stock adjustment in pre-notified container during review |

For full message definitions see [concepts/erp-interface.md](../concepts/erp-interface.md).

---

## Labels at Reception

- **LPN labels**: GS1-128 labels can be printed for containers at receipt; label format controlled by `CONTAINER_LABEL_DEFAULT_FORMAT`.
- **Item labels**: Printed for items not labeled at origin; enabled via receipt order `Enable stock label printing`.
- **Multi-label reading**: When containers always arrive labeled in GS1-128, multi-reading mode allows scanning labels in any order.
- **Label reprint**: Available from RFT if a label is damaged or content changes.

See [concepts/labels.md](../concepts/labels.md) for complete label reference.

---

## Common Errors

**Receipt order not found from RFT:**
- Cause: Order code unknown or not yet created.
- Solution: Enable `ALLOW_CREATE_RECEPTION` to create a new receipt; or have the ERP send the `ROR` message first.

**ASN container rejected at PIE - order doesn't exist:**
- Cause: Receipt order referenced in ASN message not yet in WMS.
- Solution: If `USE_EXCLUSIVE_RESERVE_STRICT_MODE` is inactive, container can still be received; reserve is formalized later. If active, resolve order absence first.

**Receipt auto-close does not trigger:**
- Cause: Receipt still has uncommitted lines or allows excess reception.
- Solution: Close manually, or verify `AutoCloseReception` is active and no line allows over-receipt.

**Quantity discrepancy at PIE - container sent to reconditioning:**
- Cause: ASN pre-notified stock quantity doesn't match received stock and receipt order doesn't allow excess.
- Solution: Correct the discrepancy at the reconditioning station and retry.

**Multiple lines created for same item at receipt close:**
- Cause: Exclusive reserve splits stock lines into reserved and unreserved portions.
- Expected behavior; each line has distinct reserve linkage.

**Return receipt rejected for expired stock:**
- Cause: `RECEPTION_NUM_DAYS_PRODUCTION_DATE_MARGIN` check triggered.
- Note: Date logistic attributes are captured but expiry is **not blocked** during returns - check parameter configuration.

---

## Reception Split Strategy (Mecalux France pattern)

Deployed at **ROUJE** and **NEUT** - documented from NEUT (blind reception, supplier + customer return, loose stock on equipment). When the item has a picking dedicated location (PDL), incoming stock is split at reception between two buffers so PDLs are filled to capacity directly and the overflow lands in reserve.

**Flow:**

1. Stock received on equipment in loose mode
2. WMS computes the quantity needed to reach PDL capacity
3. That quantity is dropped onto the **PICKING buffer**
4. The remainder is dropped onto the **RESERVE buffer**
5. Downstream, a second operator puts away: PICKING buffer → PDLs ; RESERVE buffer → rack locations

**Buffer configuration:**

| Buffer | Storage mode | Storage zone | Work zone | Sub-warehouse |
|---|---|---|---|---|
| PICKING | Loose stock | RECEPTION | RECEPTION | PICKING |
| RESERVE | **Container + stock** (⚠️ *not* "Container only", else never proposed) | RECEPTION | RECEPTION | RESERVE |

> ⚠️ For projects with group-preparation flows, ungrouping stations and wall locations must **not** belong to the PICKING sub-warehouse.
> Equipment of type RECEPTION must only have access to the RECEPTION work zone, and vice versa.
> Routes must be explicitly created for both buffers (equipment group + station).

**Putaway strategies required (4):**

| # | From | To | Key criteria/rules |
|---|---|---|---|
| 1 | Reception equipment (code `REC_*`) | PICKING buffer | Destination zone = PICKING, location with assigned item (not full), partial putaway allowed |
| 2 | Reception equipment (type RECEPTION) | RESERVE buffer | Destination zone = RESERVE |
| 3 | PICKING buffer | Dedicated picking locations | Item assigned, destination zone = PICKING |
| 4 | RESERVE buffer | Pallet rack locations | Destination zone = PALETTE |

**Split logic (custom workflow) - rules applied after stock reception:**

| Situation | Action |
|---|---|
| No PDL for the item | Drop on RESERVE |
| PDL exists and is not full | Drop on PICKING the exact quantity to reach capacity; drop the rest on RESERVE |
| PDL exists and is full | Drop on RESERVE |
| Replenishment task already in progress toward that PDL | Drop on RESERVE |

> ⚠️ Stock dropped on the RESERVE buffer **must** be on a container (existing LPN or a newly generated code).

**Customs required:**
- `Equipment_Unload_ProductUnloadOnContainer_UI` - hide the free-drop button when `location.code == "RESERVE"`
- `Equipment_Unload_ProductUnloadAllStockOnContainer_UI` - idem
- Custom workflow after reception that computes the split and generates two drop tasks

Reference implementation: [NEUT-58](https://easywmsfrance.atlassian.net/browse/NEUT-58).

---

## Interface Paths

| Path | Equipment | Description |
|---|---|---|
| `Receiving > Receipt orders` | PC | Manage receipt orders |
| `Receiving > Receipt order lines` | PC | Manage receipt order lines |
| `Receiving > Receipts` | PC | View and close receipts |
| `Warehouse > ASN LPN` | PC | View pre-notified (pending) containers |
| `Control > Stations` | PC | PIE station management |
| `Receipts > Supplier` | RFT | Supplier reception (dock) |
| `Receipts > Blind` | RFT | Blind reception (dock) |
| `Receipts > Return` | RFT | Return reception |
| `Receipts > Notices` | RFT | ASN pre-notified containers |
| `Picking workstation > Enter containers` | Workstation | PK reception |

---

## Related

- [concepts/container.md](../concepts/container.md) - LPN structure, statuses, ASN pre-notification
- [concepts/order-inbound.md](../concepts/order-inbound.md) - Receipt orders (ROR message), inbound lifecycle
- [concepts/putaway.md](../concepts/putaway.md) - What happens after stock is received
- [concepts/stock.md](../concepts/stock.md) - Stock records created during reception
- [concepts/product-item.md](../concepts/product-item.md) - Item reception profiles, logistic attributes captured at receipt
- [concepts/quality-control.md](../concepts/quality-control.md) - Incoming stock quality locks
- [concepts/labels.md](../concepts/labels.md) - LPN and item labels at reception
- [concepts/erp-interface.md](../concepts/erp-interface.md) - ROR, ASN, ASO, ASK, REF, ROF message definitions
- [concepts/transactions.md](../concepts/transactions.md) - CON.RECEP, STK.RECEP, CON.ASN.001, REC.CLS