15.1 Inbound Receiving Processes, Planned Cross-Docking, and Putaway

15.1 Inbound Receiving Processes, Planned Cross-Docking, and Putaway

Quick Answer: In Dynamics 365 Supply Chain Management (D365 SCM), inbound warehouse execution leverages the Warehouse Management mobile app to register physical receipts and generate warehouse work. Inbound flows fall into two architectural patterns: single-step receiving (receiving and immediate putaway executed in one mobile flow) and two-step receiving (dock registration generating open putaway work executed asynchronously by material handlers). For pre-advised shipments, License plate receiving reads an Advance Shipping Notice (ASN) to register an entire pallet in a single scan. Arriving goods with immediate outbound demand bypass bulk storage via Planned cross-docking, which matches purchase order supply to sales or transfer demand within a designated cross-docking time window and generates direct putaway work to outbound staging docks.

---

1. Inbound Receiving Architecture and Flow Variations

In warehouse management (WMS-enabled warehouses), physical receiving does not post an immediate financial ledger journal directly from the desktop client. Instead, receiving is an operational warehouse execution process performed on mobile radio frequency (RF) barcode scanners via the Warehouse Management mobile app.

Receiving creates Warehouse Work of work order type Purchase orders. Work consists of paired Pick and Put inventory transactions that transition goods from an inbound dock location (typically a default location of type RECV) to final storage locations.

[Inbound Vendor Truck arrives at Dock Door]
                  │
                  ▼
    ┌───────────────────────────┐
    │ Mobile App Receiving Scan │
    └─────────────┬─────────────┘
                  │
         ─────────┴─────────
        │                   │
        ▼                   ▼
┌─────────────────┐ ┌──────────────────────────────────────┐
│   Single-Step   │ │               Two-Step               │
│ (Item Receiving │ │  Step 1: Item Receiving / LP Receive │
│   & Putaway)    │ │          (Inventory registered at    │
│                 │ │           dock; Work created)        │
│ Worker receives │ │                  │                   │
│ and immediately │ │                  ▼                   │
│ drives pallet   │ │  Step 2: Purchase Order Putaway      │
│ to final shelf. │ │          (Forklift driver scans LP,  │
│                 │ │           picks from dock, puts to   │
│                 │ │           rack location)             │
└─────────────────┘ └──────────────────────────────────────┘

Single-Step Receiving Flows

In single-step receiving, a single worker receives the goods at the dock door and is immediately guided by the mobile device to transport and deposit the goods into their final warehouse location.

• Mobile Menu Item: Mode = Work, Work creation process = Purchase order item receiving and putaway.
• Operational Fit: Ideal for smaller warehouses, cross-dock docks without dedicated staging, or operations where receiving staff also operate forklifts.
• Limitation: The dock door worker remains locked into the putaway task until completed, creating a bottleneck if high-throughput truck unloading is required.

Two-Step Receiving Flows (Decoupled Receiving and Putaway)

In high-volume distribution centers, dock unloading and high-bay racking putaway are handled by separate warehouse crews. Two-step receiving decouples dock check-in from high-bay transport.

• Step 1 (Dock Registration): The receiving clerk uses a mobile menu item with Work creation process = Purchase order item receiving. The clerk scans the Purchase Order number, Item number, and quantity. The system registers the inventory as physically received at the inbound dock location (RECV), generates a unique Target License Plate, and creates an open warehouse work header with a status of Open.
• Step 2 (Putaway Execution): A forklift material handler logs into a mobile device menu item configured with Mode = Work, Use existing work = Yes. The worker scans the License Plate (LP) affixed to the pallet at the receiving dock. The mobile app directs the driver to pick the pallet from RECV and deposit it into the system-directed bulk or pick-face rack location determined by inbound location directives.

License Plate Receiving via Advance Shipping Notice (ASN)

When vendors transmit an electronic Advance Shipping Notice (ASN) via EDI (typically ANSI X12 856 or EDIFACT DESADV), D365 SCM creates an inbound Load structure containing packing structures and pre-assigned License Plate identifiers.

• Mobile Menu Item: Work creation process = License plate receiving (or License plate receiving and putaway).
• Operational Advantage: The receiving clerk does not scan individual purchase order numbers or individual item lines. Instead, the clerk scans only the vendor's pallet License Plate barcode. D365 SCM matches the scanned LP against the inbound load, instantly registering all lines, batches, serial numbers, and catch-weight quantities nested beneath that license plate in a single operational step.

---

2. License Plate Generation and GS1-128 Bar Code Integration

License Plate Generation

A License Plate (LP) in D365 SCM is a unique alphanumeric identifier assigned to a physical storage medium (pallet, tote, crate, or roll) that tracks inventory location, quantity, batch, and status as a single movable unit.

• Configuration: Navigate to Warehouse management > Setup > Mobile device > Mobile device menu items.
• Generate License Plate Parameter: On inbound menu items, selecting the Generate license plate checkbox instructs D365 SCM to automatically issue a new LP number from the warehouse number sequence upon receipt confirmation if the vendor did not provide an acceptable pre-printed barcode.
• Print Label: Enabling Print label triggers automated document routing (Warehouse management > Setup > Document routing > Document routing) to print a Zebra Programming Language (ZPL) pallet barcode label directly to a network printer at the dock door.

GS1-128 Barcode Parsing

In modern supply chains, goods arrive labeled with complex GS1-128 (formerly UCC/EAN-128) barcodes. A single GS1-128 barcode string encodes multiple data elements separated by standardized two- to four-digit Application Identifiers (AIs) enclosed in parentheses.

(01)00614141999996(10)LOT-2026A(17)261231(30)50
 │                 │            │         │
 │                 │            │         └─ AI (30): Quantity = 50
 │                 │            └─────────── AI (17): Expiration Date = Dec 31, 2026
 │                 └──────────────────────── AI (10): Batch Number = LOT-2026A
 └────────────────────────────────────────── AI (01): GTIN / Item Identification

To configure GS1-128 parsing in D365 SCM:

1. Navigate to Warehouse management > Setup > Mobile device > Bar code setup > GS1 application identifiers.
2. Configure standard GS1 Application Identifiers:
   • AI (01): Global Trade Item Number (GTIN) — maps to Released Product Item ID or Barcode.
   • AI (10): Batch / Lot number — maps to the Batch number tracking dimension.
   • AI (17): Expiration date — maps to Inventory shelf-life expiration date (YYMMDD format).
   • AI (21): Serial number — maps to the Serial number tracking dimension.
   • AI (30): Variable count / Quantity — maps to the physical transaction quantity.
3. Navigate to Warehouse management > Setup > Mobile device > Bar code setup > Bar code generic and link the GS1 parsing policy to the mobile device scanning profiles.

When a warehouse worker scans a GS1 barcode at the receiving dock, D365 SCM parses the string instantaneously, populating the item number, batch lot, expiration date, and received quantity in one operation without requiring manual data entry.

---

3. Inbound Work Templates and Location Directives

Once goods are registered at the dock, D365 SCM determines how and where to put them away using Work Templates and Location Directives.

Work Templates (Warehouse management > Setup > Work > Work templates)

Work templates define the structural blueprint of the work. For Work order type Purchase orders, the simplest work template contains two mandatory lines:

1. Pick: Pick inventory from the receiving staging location (RECV).
2. Put: Put inventory into the designated warehouse storage location.

Work templates support multiple pick/put pairs for multi-stage movements (e.g., Pick from Dock -> Put to Quality Inspection -> Pick from Quality -> Put to Bulk Rack).

Location Directives (Warehouse management > Setup > Location directives)

Location directives are the intelligent routing engine that decides the exact destination bin for the Put step.

• Work order type: Purchase orders
• Directive Lines: Evaluate quantity ranges, units of measure (e.g., Pallet vs. Each), and disposition codes.
• Location Directive Actions: Contain queries and search strategies:
  • Consolidate: Directs the worker to put the pallet into a location that already holds on-hand inventory of the exact same item and batch, maximizing storage density.
  • Empty location with no incoming work: Finds a completely unoccupied location that has no on-hand inventory and no open putaway work directed to it, preventing bin overcrowding.
  • Locate strategy (None): Relies strictly on the query filter criteria (e.g., Zone ID = BULK, Aisle = A01).

---

4. Planned Cross-Docking Architecture

Cross-docking is a lean warehousing strategy where inbound inventory from purchase orders or transfer orders is transferred directly to an outbound staging or shipping dock door without ever entering intermediate warehouse storage racks.

[Inbound Receiving Dock: RECV]
              │
              ├─── (Standard Putaway) ───► [Bulk Storage Racks: BULK-01]
              │                                   │
              │                            (Future Picking Work)
              │                                   ▼
              └─── (Cross-Docking)   ───► [Outbound Staging: STAGE-BAY04]
                   (Bypasses Bulk)                │
                                                  ▼
                                     [Outbound Customer Trailer]

Planned Cross-Docking Configuration

Planned cross-docking is pre-calculated before or during the inbound receiving transaction based on configured cross-docking rules:

• Navigation: Warehouse management > Setup > Work > Cross-docking templates
• Demand Sources: Sales orders, Transfer order issue lines.
• Supply Sources: Purchase orders.

The Cross-Docking Time Window

A critical configuration parameter in the cross-docking template is the Cross-docking time window:

• Demand release window: Specifies how far into the future the system looks for outbound demand. For example, if the demand release window is set to 24 Hours, a purchase order receipt arriving today at 8:00 AM will only match sales orders scheduled to ship before 8:00 AM tomorrow.
• Strategy: Defines demand priority resolution:
  • Date to date: Matches supply to demand based on requested ship dates (earliest scheduled demand receives cross-docked stock first).
  • Locate demand priority: Matches demand based on customer priority codes or order urgency flags.

Work Creation for Cross-Docking

When planned cross-docking criteria are met, D365 SCM overrides the standard bulk storage location directive. The generated Purchase Order work directs the worker to deposit the goods directly at an outbound staging location (e.g., STAGE or BAYDOOR-02).

The system links the inbound purchase order work directly to the outbound sales shipment. The cross-docked inventory is automatically reserved against the outbound sales line, ensuring another order cannot claim it.

---

5. Executing Cross-Docking via the Mobile App

When a receiving worker processes a purchase order via the Warehouse Management mobile app:

1. The worker scans the Purchase Order number and Item number (or GS1 barcode).
2. D365 SCM evaluates active cross-docking templates against existing unfulfilled sales order demand within the time window.
3. Full Cross-Dock: If the received quantity matches or is less than the outbound demand, the mobile device displays a Put instruction directing the worker directly to the outbound staging location: Put to Location: STAGE-01.
4. Partial Cross-Dock (Split Work): If the worker receives 100 units, but outbound demand within the time window is only 40 units, D365 SCM automatically splits the generated work lines:
   • Work Line 1: Put 40 units to STAGE-01 (Cross-docked for Outbound Sales Order).
   • Work Line 2: Put 60 units to BULK-A-12-02 (Standard Putaway to Warehouse Racking).

By splitting the work line dynamically, D365 SCM fulfills urgent customer shipments immediately while sending the surplus inventory to bulk storage in a single receiving session.

---

6. Implementation Scenarios and Exam Traps

[!IMPORTANT] Exam Tip — ASN Requirement for License Plate Receiving: A frequent MB-330 exam question tests whether an operator can use the License plate receiving mobile menu item for standard purchase orders delivered without an ASN. License plate receiving requires an Advance Shipping Notice (ASN) or pre-created Inbound Load structure where the license plate is already known to D365 SCM. If an unregistered supplier delivers pallets with unknown license plates, workers must use Purchase order item receiving and enable Generate license plate.

[!WARNING] Exam Trap — Planned vs. Opportunistic Cross-Docking: Do not confuse Planned Cross-Docking with Opportunistic (Auto) Cross-Docking. Planned cross-docking uses cross-docking templates and evaluates demand at the moment of inbound receipt. Opportunistic cross-docking is evaluated during outbound wave processing when the wave attempts to allocate inventory and detects inbound supply arriving at the dock.

[!TIP] Best Practice — Direct Staging Putaway: When configuring location directives for cross-docking, ensure that the Put location directive has a dedicated line for cross-docking work. This prevents cross-docked pallets from accidentally routing to standard high-bay bulk racks where extra labor would be wasted putting them away and picking them back down minutes later.