Study guide
15.1 Inbound Receiving Processes, Planned Cross-Docking, and Putaway
Microsoft Dynamics 365 Supply Chain Management Functional Consultant MB-330
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Product Master and Released Products
1.1 Product Masters, Variants, and Configuration Technologies 1.2 Product Templates, Category Hierarchies, and Product Lifecycle States 1.3 Product Attributes, Attribute Types, and Attribute Groups
2 Chapter 2: Bills of Materials (BOM) and Formulas
2.1 BOM Lines, Line Types, and Component Configurations 2.2 BOM Versions, Activation, Approvals, and Circularity Checks 2.3 BOM Calculations, Cost Group Types, Flushing Principles, and Scrap Handling
3 Chapter 3: Product Prerequisites and Dimension Groups
3.1 Product, Storage, and Tracking Dimension Groups 3.2 Item Model Groups, Inventory Models, and Physical/Financial Posting 3.3 Reservation Hierarchies and Unit Sequence Groups
4 Chapter 4: Additional Product Details and Warehouse Fit
4.1 Bar Codes, GTINs, and Product Unit Conversions 4.2 Default Order Settings and Site-Specific Order Settings 4.3 Product Filter Codes and Physical Warehouse Dimensions
5 Chapter 5: Inventory Costing and Pricing
5.1 Costing Versions, Costing Sheets, and Standard Costing 5.2 Base Item Prices, Price Groups, and Price Tolerances 5.3 Trade Agreements, Price/Discount Journals, and Smart Rounding
6 Chapter 6: Inventory Journals and Core Transactions
6.1 Movement, Adjustment, and Transfer Journals 6.2 Counting Journals, Tag Counting, and Cycle Count Adjustments 6.3 Item Arrival Journals, Output Orders, and BOM Journals
7 Chapter 7: Inventory Operations, Blocking, and Closing
7.1 Transfer Orders, In-Transit Warehouses, and Delivery Schedules 7.2 Inventory Blocking Mechanisms, Batch Disposition Codes, and Inventory Status 7.3 Inventory Closing, Recalculation, Settlement, and ABC Classification
8 Chapter 8: Quality Management and Nonconformance
8.1 Quality Control Setup: Tests, Test Groups, and Item Sampling 8.2 Quality Associations, Automatic Generation, and Quality Orders Processing 8.3 Nonconformances, Corrections, Corrective Operations, and Quarantine Orders
9 Chapter 9: Asset Management: Setup and Maintenance
9.1 Assets, Asset Types, and Functional Locations Setup 9.2 Asset Lifecycle Models, Lifecycle States, and Asset Loans 9.3 Work Orders Configuration, Work Order Settings, and Maintenance Capacity Management 9.4 Maintenance Plans, Maintenance Requests, Work Order Scheduling, and Journal Consumption
10 Chapter 10: Procurement and Sourcing Configuration
10.1 Vendors, Vendor Groups, and Procurement Category Hierarchies 10.2 Purchasing Policies, Spending Limits, Procurement Workflows, and Charge Codes 10.3 Purchase Agreements, Vendor Rebates, and Vendor Collaboration Portal
11 Chapter 11: Purchase Order Lifecycle and Consignment
11.1 Purchase Requisitions, Requests for Quotation (RFQs), and Bidding Processes 11.2 Purchase Orders Creation, Over/Under-Delivery Tolerances, Delivery Schedules, and Product Receipt 11.3 Consignment Inventory Replenishment/Ownership Change and Vendor Return Orders
12 Chapter 12: Landed Cost and Inbound Logistics
12.1 Landed Cost Architecture: Voyages, Shipping Containers, Folios, and Journey Templates 12.2 Cost Type Codes, Auto-Costs, and Allocation Methods 12.3 Tracking Control Center, Goods in Transit Orders, and Over/Under Tolerances
13 Chapter 13: Sales Management and Order Processing
13.1 Customers, Customer Groups, Sales Agreements, and Sales Quotations 13.2 Sales Order Processing, Manual and Automatic Reservation, and Sales Returns 13.3 Order Promising: ATP, CTP, Delivery Schedules, and Product Bundles 13.4 Intercompany Trading Chains, Sales Commissions, and Customer Rebates
14 Chapter 14: Warehouse Setup and Core Infrastructure
14.1 Warehouse Topology: Sites, Warehouses, Locations, Profiles, Formats, and Zones 14.2 Work Policies, Work Breaks, and Packing Dimensions 14.3 Wave Templates, Work Templates, and Location Directives Configuration 14.4 Label Layouts, Document Routing, Wave Label Printing, and GS1 Number Sequences
15 Chapter 15: Warehouse Execution Processes
15.1 Inbound Receiving Processes, Planned Cross-Docking, and Putaway 15.2 Outbound Waves, Wave Processing, Picking (Order, Cluster, Batch), and Manual Packing 15.3 Replenishment Strategies (Wave vs. Min/Max) and Inventory Movements via Warehouse Work 15.4 Cycle Counting Plans, Thresholds, Blind Counting, and Automated Containerization
16 Chapter 16: Transportation Management and Logistics
16.1 Shipping Carriers, Carrier Groups, Carrier Services, and Rate/Route Engines 16.2 Route Plans, Route Guides, Inbound/Outbound Loads, and Dock Appointment Scheduling 16.3 Freight Bills, Freight Invoicing, and Manual/Automatic Freight Reconciliation
17 Chapter 17: Warehouse Management Mobile App
17.1 Mobile App Installation, Display Settings, Connection Profiles, and Warehouse Worker Setup 17.2 Mobile Device Menus, Work-Based and Indirect Menu Items, and Inventory Inquiries 17.3 Step Detours Configuration and GS1 Barcode Scanning Implementation
18 Chapter 18: Master Planning and Planning Optimization
18.1 Master Planning Parameters, Coverage Groups, and Planning Optimization Cloud Service Architecture 18.2 Item Coverage Settings, Positive/Negative Days, Time Fences, and Action Messages 18.3 Running Master Planning, Analyzing Results, Planned Orders Firming, and Supply Schedule 18.4 Safety Stock Journals, Safety Margins, and Copilot in Dynamics 365 Supply Chain Management
15.1 Inbound Receiving Processes, Planned Cross-Docking, and Putaway
Key Takeaways Explain This Topic AI
Dynamics 365 Supply Chain Management supports both single-step receiving (immediate putaway) and two-step receiving (separate dock registration and deferred putaway via distinct mobile device menu items).
License plate (LP) receiving leverages pre-registered Advance Shipping Notices (ASNs) or inbound loads to register entire multi-item, mixed-SKU pallets in a single mobile device barcode scan.
GS1-128 barcode parsing uses Application Identifiers (AIs) such as AI (01) GTIN, AI (10) Batch, AI (17) Expiry, and AI (30) Quantity to capture multiple inventory dimensions in a single physical scan.
Planned cross-docking evaluates inbound purchase order supply lines against outbound sales or transfer demand within a configured cross-docking time window.
Cross-docking execution generates direct putaway work to outbound staging or baydoors, completely bypassing bulk storage racking and eliminating redundant putaway and picking travel.
Last updated: September 2026
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.
Receiving Menu Item Process Work Created At User Flow on Mobile App ASN / Load Required?
Purchase order item receiving and putaway Mobile scan Step 1: Scan PO & Item; Step 2: Immediate Putaway to shelf No
Purchase order item receiving Mobile scan Step 1: Scan PO & Item; Putaway work remains open for later execution No
License plate receiving Mobile scan Step 1: Scan Pallet LP; Pallet registered at dock; Putaway work remains open Yes (Inbound ASN/Load)
License plate receiving and putaway Mobile scan Step 1: Scan Pallet LP; Step 2: Immediate Putaway to shelf Yes (Inbound ASN/Load)
- 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:
Navigate to Warehouse management > Setup > Mobile device > Bar code setup > GS1 application identifiers .
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.
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:
Pick : Pick inventory from the receiving staging location ( RECV ).
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:
The worker scans the Purchase Order number and Item number (or GS1 barcode).
D365 SCM evaluates active cross-docking templates against existing unfulfilled sales order demand within the time window.
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 .
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.