mcp-wms-wiki/wiki_old_13-05-2026/concepts/order-inbound.md

title, type, sources, related, last_compiled

title	type	sources	related	last_compiled
Inbound Order (Receipt Order)	concept	areas/receptions/reception_admin/receipt_orders.md areas/receptions/reception_admin/receipt_order_type.md areas/receptions/reception_admin/receipt_order_class.md areas/receptions/reception_admin/receipt_order_supervise.md areas/receptions/reception_admin/receipt_order_supervise.md areas/receptions/reception_admin/views/view_receipt_order.md areas/receptions/reception_admin/views/view_receipt_order_lines.md areas/receptions/reception_admin/unload_receipt.md areas/ERP/receipts/ror.md areas/ERP/receipts/roc.md areas/ERP/receipts/rof.md areas/ERP/receipts/asn.md areas/ERP/receipts/aso.md areas/ERP/receipts/ref.md areas/ERP/requests/str.md areas/inbounds/index.md	concepts/reception.md concepts/container.md concepts/product-item.md concepts/stock.md concepts/putaway.md concepts/order-outbound.md concepts/crossdocking.md concepts/erp-interface.md	2026-04-10

Inbound Order (Receipt Order)

Overview

A receipt order (also called inbound order) is the WMS document that tracks expected incoming stock. It represents a list of items or containers expected to arrive at the warehouse, serving as the basis for the reception process. Receipt orders allow the warehouse to plan dock resources, validate quantities, and close the loop with the ERP upon receipt.

Most receipt orders originate in the ERP (purchase orders to suppliers, customer return orders, transfer orders from other warehouses) and arrive via messaging. Easy WMS also allows manual creation of receipt orders directly in the UI. Receipt orders are optional — stock can be received without one (blind reception) — but they enable quantity control, automatic label printing, and ERP reconciliation.

The receipt order is distinct from the receipt (the actual WMS event of receiving stock physically). One receipt order can be fulfilled by one or more receipts; one receipt can be associated with one or more receipt orders.

Types

Receipt orders (and their associated receipts) are categorized by type, which conditions how they are processed:

Type	Description	Typical origin
Supplier	Stock arriving from a vendor. Lines specify items, expected quantities, and UoM. Stock may arrive in any presentation (pack, box, etc.) regardless of the line's UoM. Logistic attributes and quality status can optionally be pre-set by the ERP.	ERP purchase order (PO)
Return	Customer returns — damaged or surplus stock. Similar line structure to Supplier type.	ERP return authorization
Transfer	Stock transferred from another warehouse in the same organization. Stock always arrives in containers, which are pre-notified as ASN containers at the destination. Lines specify containers, items, and quantities.	ERP transfer order; automatic when source shipping order closes (Transfer type)

Receipt orders also have a class for additional personalization of the reception process (custom flow variants, label types, etc.). Classes do not change the type logic but allow further differentiation.

Structure

Order header

Field	Description
Code	Unique inbound order code
Status	Current lifecycle status (see Lifecycle section)
Type	Supplier / Return / Transfer
Class	Optional sub-classification of the order
Owner	Owner of the stock (mandatory when Owner Extension / Billing / 3PL Portal module installed)
Document	Delivery note or reference document from supplier/carrier
Supplier	Supplier code (Supplier type only)
Account	Customer account code (Return type only)
Source	Source warehouse code (Transfer type only)
Allow lines auto-creation	If enabled, unexpected items received against this order are accepted and added as new lines
Enable container label printing	All receipts from this order will automatically print GS1-128 container labels during receipt
Enable stock label printing	All receipts from this order will automatically print GS1-128 item labels during receipt
Single receipt	Only one receipt is auto-created for this order (use when all stock arrives in one delivery). Requires AutoCreateReceptionFromRecOrder parameter active.

Order lines

Each line identifies the expected item/container and quantity:

Field	Description
Line number	Unique line identifier within the order
Status	Line status (mirrors order status progression)
Container	Expected or received container code (Transfer type or ASN)
Item	Item code expected; alternatively, a presentation alias (GTIN/EAN) can be used — in this case, only stock of that EAN presentation is received against this line
Owner	Owner of the expected stock
Quantity	Expected quantity
UoM	Unit of measure (usually base UoM; can be a presentation if packaging is known)
Logistic attributes	Pre-set lot, expiration date, etc. (unusual; typically captured at physical reception)
Stock status	Quality status that will be automatically applied to received stock (receiving status)
Number of ERP parcels	Informational parcel code from ERP; used to reconcile which packages were received
Excess percentage (LneTrmExceedPerc)	Maximum percentage above expected quantity that can be received on this line

Lifecycle

[ERP sends ROR or manual creation]
            ↓
        WAITING
    (order created; no receipt started)
            ↓
[First receipt created] → RECEPTION PENDING
            ↓
[First stock physically received] → RECEIVING
            ↓
[Some lines complete, others not] → PARTIALLY RECEIVED
            ↓
[All lines fully received] → COMPLETE
            ↓
[Manually or automatically closed] → CLOSED
            ↓
[No activity within validity period] → EXPIRED
[Canceled before any receipt] → CANCELED

ERP is notified of every status transition via ROC message.

Closing can happen:

• Automatically when all lines are fully received and the AutoCloseInboundOrder parameter is active
• Manually from the Receipt orders view
• Forced close even with partial receipt

Cancellation is only allowed when no stock has been received (status: Waiting or Reception Pending).

Modifications allowed while in Waiting or Reception Pending:

• Add new lines
• Edit expected quantity (up or down; down to received qty completes the line)
• Edit UoM (only if no stock received on that line)

ERP integration

Messages: ERP → WMS

ROR — Receipt Order Request

Creates, modifies, or cancels receipt orders.

Operation	Description
C / S	Create new receipt order (header + lines)
U	Update existing order (add/modify lines, edit quantities)
D (standard)	Cancel receipt order (only if nothing received)
D + CloseReceiptOrder=True	Close completed/partially received order

Key ROR fields:

• RorCode: unique order code
• RorType: Supplier / Return / Transfer
• SupplierCode / AccountCode: for Supplier or Return types
• Document: delivery note reference
• RecDatDate, RecDatDockR, RecDatContainers: estimated arrival date, dock, and container count (informational)
• EnableLabelPrinting: auto-print container labels during receipt
• EnablePrintingItemLabel: auto-print item labels during receipt
• AllowAutoCreateLines: accept unexpected stock
• SingleReceipt: one receipt per order
• Line LneTrmExceedPerc: over-receive tolerance percentage
• Line LneStockStatus: forced receiving status for stock on this line
• Line reserves (LneStkRsvSORCode / LneStkRsvAccCode): pre-allocate received stock to a specific outbound order or account

ASN — Advanced Shipping Notice

Pre-notifies containers expected at the warehouse. Containers are created in the virtual ASN location.

Variant	Description
With receipt order	Pre-notified container linked to a ROR
Without receipt order	Pre-notified container only (blind ASN)
Stacked (lifted) containers	Hierarchy of stacked containers pre-notified together
Matched containers on dummy	Matched group based on virtual slave container (dummy, no weight)
Matched on labeled slave	Slave container is labeled (has code)
Matched on non-labeled slave	Slave container has no code; stock linked to inner containers
With divisions	Container with division type and per-division stock lines
With exclusive reserve for outbound order	Pre-notified container's stock reserved for specific SOR on receipt
With exclusive reserve for route	Pre-notified container's stock reserved for a route stop
With reserve and expiry deadline	Reserve creation deadline if order/route doesn't exist at receipt time

ASN key fields: ContainerCode, ContainerType, ReceiptOrderCode, NumExpectedContainers, ExpectedOutboundOrderCode / ExpectedRouteCode

Messages: WMS → ERP

ROC — Receipt Order status Change

Sent by WMS when an order changes status. Fields: RorCode, Status (Waiting / ReceptionPending / Receiving / PartiallyReceived / Complete / Expired / Canceled), UpdateDate (UTC timestamp).

ROF — Receipt Order Finalization

Sent when an order is closed or canceled. Two versions:

• ROF01: includes receipt data + order data + stock received. Sent on order close/cancel AND on receipt close (even if receipt has no order).
• ROF02: order data and stock only. Receipt closings sent separately via REF message. Use ROF02 in installations with frequent grouped receipts (one receipt associated with multiple orders).

ROF01/ROF02 key fields per line: LneItemCode, LneOwnerCode, LneQtyExpected, LneQtyReceived, LneQtyFree, LneQtyUoMCode.

ASO — ASN receipt confirmation (WMS → ERP)

Sent when an ASN pre-notified container is physically received. Confirms item, owner, quantity, and optionally the receiving status (LneStaStatus). Variants mirror ASN variants (stacked, matched on dummy, with divisions).

STR — Stock lock/unlock request (ERP → WMS)

Although STR is a request (not a receipt order message), it is closely related to inbound quality control. The ERP requests Easy WMS to apply or remove a user status on stock (e.g., lock a lot for quality reasons):

• Operation S: add user status (lock) with optional quarantine end date
• Operation D: remove user status (unlock by lot or by receiving status)

WMS responds with one or more STC messages confirming the modified stock.

Parameters

Parameter	Effect
AutoCreateReceptionFromRecOrder	If active, a receipt is automatically created when a ROR is received. Combined with SingleReceipt, creates exactly one receipt per order.
AutoCloseInboundOrder	If active, the order automatically closes when all lines are fully received

Interface

Function	Hardware	Menu path
Receipt orders view	PC	Receiving → Receipt orders
Receipt order lines view	PC	Receiving → Receipt order lines
Manual creation	PC	Receiving → Receipt orders → New
Supervision	PC	Receiving → Receipt orders → Supervise

Available operations

Operation	Conditions
Create manual receipt order	Any time; complete creation before receipts can start
Add lines to existing order	Order must not be Completed, Closed, or Archived
Edit expected quantity	Order in Waiting or Reception Pending; if stock received, quantity ≥ received qty
Edit UoM on line	Order in Waiting or Reception Pending; no stock received on line
Close receipt order	Stock already received; status Complete/Partially received/Reception pending with no active receipt
Cancel receipt order	No stock received; status Waiting or Reception Pending

Common errors

Symptom	Cause	Solution
Receipt order cannot be canceled	Stock already received against it	Close the order instead; cancel remaining unreceived quantities
Unexpected stock received but not accepted	Allow lines auto-creation not enabled on order	Enable the flag on the order header, or create the missing line manually before reception
Over-receive blocked	LneTrmExceedPerc = 0 or not set	Request ERP to update the line with a tolerance percentage; or adjust quantity manually
ROC not sent	WMS-ERP integration configuration issue	Check ERP communication settings and ROC message configuration
Transfer receipt order has no ASN	Source warehouse did not close shipping order (Transfer type)	Verify source warehouse has closed the transfer shipping order; ASN is created automatically
ASN reserve not created at receipt	Expected outbound order did not exist and deadline passed	Check ExpectedReserveValidDate; re-create reserve manually on the outbound order
Order stuck in Receiving	Receipts associated to the order are still open	Close or finalize all associated receipts first

Related

• reception — the physical reception process that fulfills receipt orders; dock/PIE/ASN reception modes all reference receipt orders
• container — ASN pre-notifies containers; Transfer-type receipt orders always involve containers
• product-item — receipt order lines reference items by code or alias; reception profile governs behavior
• stock — receipt creates stock; receiving status from ROR line is applied to created stock
• putaway — after reception, putaway tasks move stock from dock to storage; receipt order type affects putaway strategy eligibility
• order-outbound — receipt orders can include reserves for outbound orders (cross-dock scenario); transfer orders create an outbound order at source
• crossdocking — ASN containers with exclusive reserves enable direct crossdocking on receipt
• erp-interface — ROR (in), ASN (in), ROC (out), ROF (out), ASO (out), STR (in), STC (out) messages