Study guide
4.2 Default Order Settings and Site-Specific Order Settings
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
4.2 Default Order Settings and Site-Specific Order Settings
Key Takeaways Explain This Topic AI
Default order settings govern procurement, internal inventory movements, and sales distribution across three dedicated tabs: Purchase order, Inventory, and Sales order.
Default site and warehouse automatically populate transaction lines; marking Mandatory site or Mandatory warehouse strictly prevents users and master planning from overriding those dimensions.
Order quantity boundaries (Minimum, Maximum, Multiple, and Standard order quantities) enforce order lot sizes, carton increments, master planning order splits, and BOM cost calculation lot sizes.
Lead time parameters can be calculated using elapsed calendar days or constrained by an active Working days calendar assigned to the vendor, warehouse, or coverage group.
Site-specific order settings override the global fallback (blank site) order settings, allowing organizations to tailor order multiples, lead times, warehouses, and Stopped statuses per operational facility.
Last updated: September 2026
4.2 Default Order Settings and Site-Specific Order Settings
Quick Answer: Default Order Settings ( InventItemOrderSetup ) define operational and commercial guardrails for released products in D365 SCM. Structured across three functional contexts— Purchase order , Inventory , and Sales order —they control default and mandatory sites/warehouses, order quantity boundaries (Minimum, Maximum, Multiple, Standard), lead times, and transaction blocking via Stopped flags. D365 SCM evaluates order settings through a two-tiered resolution hierarchy: the system first searches for a Site-specific order setting matching the transaction site; if none exists, it falls back to the Global default order setting (where Site is blank).
Default Order Settings Architecture: The Three Functional Tabs
Every released product requires defined ordering parameters to control document creation and guide Master Planning (Planning Optimization). Navigate to Product information management > Products > Released products > Manage inventory tab > Order settings > Default order settings .
The form is organized into three distinct transaction tabs:
Purchase order tab ( InventItemPurchSetup ): Governs external procurement, purchase requisition line defaulting, purchase order generation, planned purchase orders generated by master planning, and vendor confirmation lead times.
Inventory tab ( InventItemInventSetup ): Governs internal warehouse movements, transfer orders, inventory adjustment/movement journals, BOM/formula component flushing, production order batch sizing, and planned transfer/production orders.
Sales order tab ( InventItemSalesSetup ): Governs commercial distribution, customer sales quotation and sales order line defaulting, customer return orders, Available-to-Promise (ATP) shipping lead times, and sales quantity restrictions.
Default Site and Warehouse vs. Mandatory Flags
Within each of the three tabs, consultants configure the physical fulfillment topology:
Default Site and Warehouse : When an order line (PO, SO, Transfer) is initialized, D365 SCM automatically populates the Site and Warehouse fields using these default values. If a user changes the customer delivery address or selects a different site, the default warehouse tied to that site is re-evaluated.
Mandatory Site : When checked, users cannot modify the Site dimension on the transaction line. It is strictly locked to the configured default site. If an automated import or EDI message attempts to pass a different site, the transaction fails validation.
Mandatory Warehouse : When checked, users cannot modify the Warehouse dimension. Master planning is strictly prohibited from generating planned orders for any other warehouse under that site.
Warning
Exam Trap — Master Planning Impact: If Mandatory warehouse is enabled on the Purchase order tab for Warehouse 11, Master Planning (Planning Optimization) will never create a planned purchase order for Warehouse 12, even if Warehouse 12 faces a catastrophic stockout and possesses an active item coverage record. Mandatory flags strictly override dynamic planning logic.
Order Quantity Parameters and Lot Sizing
Order quantity controls prevent erratic ordering patterns, enforce full-carton or pallet-layer purchasing, and protect against catastrophic entry mistakes:
Parameter Field Name Master Planning & Operational Impact
Multiple MultipleQty Forces transactions in discrete numerical increments (e.g., Multiple = 12 enforces full dozens). Master planning rounds net requirements up to the nearest multiple.
Minimum order quantity MinQty Smallest permissible order quantity. If master planning calculates net demand for 3 units, but the Minimum is 50, the planned order is generated for 50 units.
Maximum order quantity MaxQty Upper capacity ceiling for a single order line. When master planning encounters demand exceeding this limit (e.g., net demand of 300 where Maximum is 100), it splits the requirement into multiple planned orders (100 + 100 + 100).
Standard order quantity StandardQty Populates the initial default line quantity upon manual entry. On the Inventory tab, it dictates the Costing lot size for BOM cost roll-ups, amortizing fixed setup costs across this exact quantity.
Lead Time Management: Working Days vs. Calendar Days
Each tab provides dedicated lead time fields:
Purchase lead time : Days required from PO confirmation to dock receiving.
Inventory lead time : Production cycle duration or inter-warehouse transit window.
Sales lead time : Order dispatch window used for Available-to-Promise (ATP) delivery date calculations.
The Working Days Toggle
Beside each lead time field sits the Working days checkbox:
Working days unchecked : Lead time represents elapsed calendar days (24/7 continuous progression), including weekends, holidays, and facility shutdown periods.
Working days checked : D365 SCM iterates through the assigned Working time calendar (configured on the vendor, warehouse, coverage group, or legal entity). Saturdays, Sundays, and non-working holiday dates are skipped. If an order with a 5-day purchase lead time is confirmed on a Thursday, the engine skips Saturday and Sunday, establishing delivery for the following Thursday.
Site-Specific Order Settings: Resolution Hierarchy
In multi-facility enterprises, operational parameters vary by location. An item procured at Site 1 (near a local supplier) may have a 2-day lead time and purchase multiple of 10. That same item transacted at Site 2 (supplied via overseas freight) may require a 45-day lead time and a minimum order quantity of 1,000.
Modern D365 SCM manages this through Site-specific order settings within the unified Default order settings form:
Rank 0 / Fallback Record (Blank Site) : Every released product has a baseline default record where the Site field is empty. This serves as the universal fallback configuration.
Site-Specific Record : When a record is created with a specific Site selected (e.g., Site 1, Site 2), all settings on that row override the baseline fallback whenever a transaction is initiated for that specific site.
Granular Overrides : You can configure a site-specific record that overrides only the Sales order tab while inheriting purchasing rules from the fallback record.
The "Stopped" Flag Architecture
The Stopped checkbox is an administrative control available independently on the Purchase order, Inventory, and Sales order tabs:
Purchase order tab : Blocks purchase requisitions, purchase order lines, vendor confirmation, PO product receipts, and planned purchase orders.
Inventory tab : Blocks transfer orders, inventory journals (adjustments, movements, counting), BOM consumption, and production report-as-finished.
Sales order tab : Blocks sales quotation confirmations, sales order line creation, packing slips, and invoicing.
Global vs. Site-Specific Stopping
Global Discontinuation : Marking Stopped on the blank-site fallback record prevents transactions across the entire legal entity.
Site-Specific Stopping : Marking Stopped on the Site 2 record halts transactions exclusively at Site 2 (e.g., closing sales from a damaged regional warehouse while Site 1 continues normal order fulfillment).
Implementation Scenarios and Exam Traps
Important
Exam Tip — Stopped vs. Product Lifecycle State: The Stopped flag on default order settings blocks transactions immediately at the document entry level without altering the product master's lifecycle state. Conversely, Product lifecycle state ( Product information management > Setup > Product lifecycle state ) provides broader, policy-driven governance across all legal entities.
Warning
Exam Trap — Minimum vs. Standard Quantity: On the exam, do not confuse Minimum Order Quantity with Standard Order Quantity. Minimum order quantity strictly restricts the smallest transaction size permitted on orders. Standard order quantity simply populates the initial default line quantity and dictates the costing lot size for BOM roll-ups.