Study guide
7.1 Transfer Orders, In-Transit Warehouses, and Delivery Schedules
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
7.1 Transfer Orders, In-Transit Warehouses, and Delivery Schedules
Key Takeaways Explain This Topic AI
Transfer orders manage multi-step stock movements between warehouses via dedicated In-transit warehouses, supporting shipping documentation, freight carrier rating, and separate shipment and receipt tracking.
An In-transit warehouse is a virtual, non-nettable warehouse assigned to an origin physical warehouse; Master Planning treats goods in transit as inbound supply arriving at the destination on the scheduled delivery date.
Transfer order shipping transitions inventory from Picked to Deducted at the origin warehouse and creates a Received transaction in the transit warehouse; receiving transitions transit stock to Deducted and logs Received at the destination.
Delivery schedules split a single transfer order line across staggered delivery dates while retaining a central parent commercial line for aggregated tracking.
Scrapping goods lost or damaged during transit is executed directly on the transfer order receipt dialog, deducting quantity from the transit warehouse and debiting the Transfer order scrap account.
Last updated: September 2026
7.1 Transfer Orders, In-Transit Warehouses, and Delivery Schedules
Quick Answer: A Transfer order manages multi-step physical inventory movements between warehouses using a dedicated In-transit warehouse . Unlike a one-step Transfer journal (which moves stock instantaneously with zero transit time and no transport documentation), a Transfer order separates outbound shipping from inbound receiving, supports freight charges, integrates with Transportation Management (TMS) and Warehouse Management (WMS), and tracks inventory ownership while goods are en route. Master Planning treats the In-transit warehouse as a non-nettable conduit, projecting the in-transit inventory as available supply arriving at the destination warehouse on the transfer order's confirmed delivery date.
1. Architectural Distinction: Transfer Orders vs. Transfer Journals
In Dynamics 365 Supply Chain Management (D365 SCM), moving inventory between physical locations can be accomplished via an Inventory transfer journal or a Transfer order . Functional consultants must evaluate operational complexity, geographical distance, transit lead time, and legal documentation requirements when choosing the appropriate mechanism. Inventory movement options:
- ├── Transfer Journal (1-Step): Source Loc ──[Instant Sync Post]──> Destination Loc
- └── Transfer Order (Multi-Step): Origin WH ──[Shipment]──> Transit WH ──[Receipt]──> Destination WH
Operational Dimension Transfer Journal Transfer Order
Execution Lifecycle One-step instantaneous posting. Inventory is deducted from the source and received at the destination in a single atomic transaction. Multi-step asynchronous workflow. Outbound shipment from origin and inbound receipt at destination occur as independent events separated by time and geography.
In-Transit Tracking No in-transit warehouse. Inventory is never tracked as being "on the road" or in transit. Mandatory In-transit warehouse. Goods reside in a designated transit warehouse while moving between facilities.
Documentation & Paperwork Generates a standard inventory journal voucher. No shipping documents, packing slips, or bills of lading. Full commercial and shipping documentation: Transfer order picking lists, shipment packing slips, bills of lading, and transfer order receipt slips.
Transportation Management (TMS) No TMS integration. Cannot be planned into loads, rated with shipping carriers, or tracked via freight routes. Full TMS integration. Transfer order lines can be planned into inbound/outbound loads, assigned shipping carriers, and rated for freight costs.
Warehouse Management (WMS) Limited WMS support. Used primarily for manual location or dimension status adjustments. Full advanced WMS support. Supports outbound wave templates, work creation, mobile device picking, staging, loading, license plate tracking, and mobile receiving.
Transit Lead Time & Order Promising Assumes zero lead time. Cannot evaluate transport calendars or delivery date control. Integrates with Delivery date control , Transport days matrices, shipping/receiving calendars, and Master Planning lead times.
Discrepancy & Scrap Handling Cannot record in-transit damages or scrap. Variances require manual adjustment journals after posting. Supports Overdelivery , Underdelivery tolerances, and direct Scrap quantity recording during receipt.
2. In-Transit Warehouse Topology and Master Planning
A Transit warehouse is a specialized virtual warehouse type configured at Inventory management > Setup > Inventory breakdown > Warehouses . Inventory management
- └── Setup
- └── Inventory breakdown
- └── Warehouses
- ├── Warehouse: 27 (Type: Transit)
- └── Warehouse: 21 (Type: Standard > General FastTab > Default transit warehouse: 27)
- Transit Warehouse Architecture Rules
Warehouse Type Parameter : On the warehouse record, the Type field must be set to Transit .
Association with Standard Warehouses : A transit warehouse is linked to physical origin warehouses via the Default transit warehouse field located on the General FastTab of the shipping warehouse. When a transfer order is created with Warehouse 21 as the From warehouse , D365 SCM automatically assigns the linked transit warehouse (e.g., Warehouse 27 ) to the order header and lines.
Manual vs. Automated Assignment : While the transit warehouse defaults from the From warehouse setup, users can override it on the transfer order header if a specific shipment requires a different transit node (such as an ocean transit warehouse versus an air transit warehouse).
No Direct Inventory Operations : Users cannot post manual adjustment journals, movement journals, counting journals, or purchase orders directly into a transit warehouse. Stock can only enter or leave a transit warehouse through the execution of transfer orders.
Master Planning (MRP / Planning Optimization) Behavior
Non-Nettable Status : An in-transit warehouse is inherently non-nettable. Master Planning never generates planned purchase orders, planned production orders, or planned transfer orders to replenish a transit warehouse directly. Safety stock minimums cannot be established for transit warehouses.
Supply Projection : When a transfer order is shipped, Master Planning recognizes the inventory sitting in the transit warehouse as committed supply destined for the To warehouse . It schedules the availability of that inventory at the destination warehouse based on the Receipt date calculated by delivery date control and transit time engines.
Note
Architecture Detail: While inventory sits in the transit warehouse, it remains an asset of the legal entity. If the From and To warehouses belong to different financial inventory sites, the system posts inter-site transit accruals to maintain balance sheet integrity across physical business units.
3. Transfer Order Lifecycle and Inventory Transaction Statuses
The execution of a transfer order ( Inventory management > Inbound and outbound orders > Transfer order ) drives inventory through distinct transaction states in the InventTrans table across three distinct warehouse entities: the From warehouse , the Transit warehouse , and the To warehouse .
Step-by-Step Lifecycle Stages
Order Creation ( Created ) :
From Warehouse : An InventTrans issue record is created with status On order (or Reserved physical if automatic reservation is active).
To Warehouse : An InventTrans receipt record is created with status Ordered .
Transit Warehouse : No transaction records exist yet.
Warehouse Release and Picking ( Picked ) :
In advanced WMS, releasing the transfer order to the warehouse creates wave work. Workers pick the stock from storage locations to the outbound staging/baydoor location.
From Warehouse : The inventory transaction transitions from Reserved physical to Picked .
Shipment Posting ( Shipped ) :
The warehouse clerk posts the Shipment ( Transfer order > Ship > Ship transfer order ).
From Warehouse : The inventory transaction transitions from Picked to Deducted . The physical stock is removed from the origin warehouse on-hand balance.
Transit Warehouse : A new receipt transaction is created with status Received . The inventory is now physically and financially tracked inside the transit warehouse.
To Warehouse : The transaction status remains Ordered (representing future expected supply).
Receipt Posting ( Received ) :
The carrier arrives at the destination facility. The receiving clerk registers the goods (or uses the mobile app) and posts the Receive action ( Transfer order > Receive > Receive ).
Transit Warehouse : The receipt transaction is closed, and an issue transaction transitions to Deducted , removing the stock from the transit warehouse.
To Warehouse : The inbound transaction transitions from Ordered (or Registered ) to Received . The stock is now fully available at the destination warehouse.
Financial Settlement ( Sold and Purchased ) :
When the periodic Inventory close or Recalculation job runs, the issue at the origin warehouse transitions from Deducted to Sold , and the receipt at the destination transitions from Received to Purchased , locking the financial cost settlement.
4. Auto-Reservation Rules on Transfer Orders
When creating transfer orders, enterprises must control how aggressively inventory at the origin warehouse is allocated. This behavior is governed by the Reservation parameter configured at Inventory management > Setup > Inventory and warehouse management parameters > General tab or overridden on the transfer order header.
Manual : The system creates transfer order lines with status On order . Inventory is not reserved. Other sales orders, transfer orders, or production orders can claim available on-hand inventory until a warehouse worker manually reserves the stock or releases the order to the warehouse.
Automatic : The moment a transfer order line is entered and saved, D365 SCM automatically attempts to reserve physical on-hand inventory at the origin warehouse. If sufficient physical on-hand exists, the transaction status immediately becomes Reserved physical . If partial stock exists, the available portion is reserved physically, and the remainder remains On order .
Explosion : Used when transfer order lines involve kit or BOM components that require reservation down through lower assembly levels.
Warning
Exam Trap: In an advanced WMS warehouse, setting reservation to Manual means the order cannot be released to the warehouse via automated wave processing until reservation occurs. WMS wave templates require inventory to be in status Reserved physical (above location in the reservation hierarchy) before allocation work can be generated.
5. Over-Delivery and Under-Delivery Tolerances
Physical bulk materials, liquids, agricultural commodities, and freight shipments frequently experience quantity variations between dispatch and arrival. D365 SCM enforces shipment and receipt compliance via Over-delivery and Under-delivery percentage tolerances.
Configuration Hierarchy
Default Settings : Configured on the Released product record ( Product information management > Released products > Manage inventory FastTab > Transfer order ).
Line Overrides : Tolerances default from the item master onto the transfer order line, where authorized users can adjust them.
Operational Handling
Under-Delivery Tolerance ( Underdelivery ) :
Defines the allowable percentage by which the received quantity can fall short of the ordered quantity.
Example : An order line specifies 1,000 units with a 10% under-delivery tolerance. The transit carrier delivers 920 units, and the remaining 80 units cannot be fulfilled.
Closing the Order : When posting the receipt, the user marks the Close checkbox on the receipt dialog. Because the 920 units fall within the 10% tolerance (minimum acceptable = 900 units), the system accepts the 920 units, advances the transfer order status to Received , and cancels the remaining 80 units without error.
If the received quantity falls below the tolerance (e.g., 850 units received when minimum is 900), D365 SCM blocks the closure with an Infolog warning unless the under-delivery tolerance on the line is increased.
Over-Delivery Tolerance ( Overdelivery ) :
Defines the allowable percentage by which the shipped or received quantity can exceed the original ordered quantity.
Example : An order line specifies 500 units with a 5% over-delivery tolerance. The origin warehouse can pick and ship up to 525 units without modifying the original line quantity.
6. Delivery Schedules on Transfer Orders
When a large inventory transfer must be distributed across multiple shipments over time (e.g., replenishing a regional retail store with 10,000 units split into weekly increments of 2,500 units), creating separate transfer orders causes administrative clutter. Instead, D365 SCM provides Delivery schedules . Transfer Order Line: Item A0001 (10,000 ea) [Commercial Header Line - Locked]
- ├── Schedule Line 1: 2,500 ea | Ship Date: Oct 01 | Delivery Date: Oct 05
- ├── Schedule Line 2: 2,500 ea | Ship Date: Oct 08 | Delivery Date: Oct 12
- ├── Schedule Line 3: 2,500 ea | Ship Date: Oct 15 | Delivery Date: Oct 19
- └── Schedule Line 4: 2,500 ea | Ship Date: Oct 22 | Delivery Date: Oct 26
- How Delivery Schedules Function
Creation : On the Transfer order line, select Transfer order line > Delivery schedule .
Parent / Commercial Line : The original order line becomes the Total line (commercial parent). Its quantity field displays the aggregate total (10,000 units) and becomes read-only . Inventory transactions are stripped from this line.
Child / Delivery Lines : The user defines individual schedule lines with specific quantities, ship dates, delivery dates, and modes of delivery.
Operational Execution : WMS waves, picking lists, shipments, and receipts are executed strictly against the individual delivery schedule child lines. Master Planning generates planned supply based on the distinct delivery dates of the child lines.
7. Scrapping Transfer Order Lines During Transit
When goods are destroyed, spoiled, or lost while in the custody of a freight carrier, the lost quantity must be removed from the transit warehouse without receiving it into the destination warehouse's sellable stock. Transit Warehouse (100 units on-hand)
- │
- ├── 90 units received ──> Destination Warehouse (Received)
- │
- └── 10 units scrapped ──> Deducted from Transit WH
- └── GL Debit: Transfer order scrap account
- Step-by-Step Transit Scrap Procedure
Navigate to the transfer order and open the Receive posting dialog ( Transfer order > Receive > Receive ).
On the Lines tab of the posting form, locate the line experiencing transit damage.
Enter the sound physical quantity received into the Receive quantity field (e.g., 90 ).
Enter the damaged or lost quantity into the Scrap quantity field (e.g., 10 ).
Post the receipt.
Inventory and Financial Accounting Results
Destination Warehouse : 90 units transition to status Received at the destination warehouse location.
Transit Warehouse : All 100 units are removed from the transit warehouse. 90 units transfer to the destination, and 10 units are issued as Deducted directly from the transit warehouse.
General Ledger Posting : The financial value of the 10 scrapped units is credited from inventory and debited to the Transfer order scrap account configured in the Inventory Posting Profile ( Inventory management > Setup > Posting > Posting > Inventory tab > Transfer order scrap ).
Order Completion : Because the sum of the received quantity (90) and the scrap quantity (10) equals the shipped quantity (100), the transfer order line is fully closed with status Received .