Study guide
12.3 Locations, Transfer Routes & Stockkeeping Units (SKUs)
Microsoft Dynamics 365 Business Central Functional Consultant MB-800
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Company Creation & Data Migration
1.1 Creating Companies & Assisted Setup Wizards 1.2 Configuration Packages & RapidStart Worksheets 1.3 Opening Balances & Data Migration Strategies
2 Chapter 2: Security, Profiles & Auditing
2.1 Users, User Setup & Role Center Profiles 2.2 Permission Sets & Security Group Management 2.3 Security Filters, Change Log & Security Auditing
3 Chapter 3: Core System Configuration, Number Series & Copilot
3.1 Company Information, Number Series & Job Queues 3.2 Report Layout Management & Copilot AI Capabilities
4 Chapter 4: Dimensions Architecture & Governance
4.1 Dimension Concepts & Dimension Values 4.2 Global Dimensions vs Shortcut Dimensions 4.3 Default Dimensions, Combinations & Priorities
5 Chapter 5: Workflows & Approvals
5.1 Native Workflow Templates & Approval Hierarchy 5.2 Workflow User Groups & Notification Configuration
6 Chapter 6: Financial Setup, Periods & Currencies
6.1 General Ledger Setup & Accounting Periods 6.2 Payment Terms, Payment Methods & Deferrals 6.3 Multi-Currency Setup & Exchange Rates
7 Chapter 7: Chart of Accounts, Categories & Allocations
7.1 Chart of Accounts Structure & G/L Account Cards 7.2 Account Categories, Subcategories & Financial Reporting 7.3 General Ledger Allocation Accounts & Sharing
8 Chapter 8: Posting Groups & Posting Setup
8.1 Specific Posting Groups: Customer, Vendor, Bank & Inventory 8.2 General Posting Groups & General Posting Setup Matrix 8.3 Inventory Posting Setup & Alternative Posting Groups
9 Chapter 9: General Journals & Recurring Methods
9.1 Bank Account Cards & Posting Setup 9.2 General Journal Templates, Batches & Number Series 9.3 Recurring General Journals & Allocation Methods
10 Chapter 10: Accounts Payable & Accounts Receivable Setup
10.1 Purchases & Payables Setup & Vendor Master 10.2 Sales & Receivables Setup & Customer Master 10.3 Payment Journals, Cash Receipts & Payment Registration Setup
11 Chapter 11: Fixed Assets Setup & Depreciation Books
11.1 Fixed Asset Setup, Classes & Depreciation Books 11.2 Fixed Asset Cards, Main/Component Assets & Depreciation Methods
12 Chapter 12: Inventory Setup, Costing & Locations
12.1 Inventory Setup, Item Types, Categories & Variants 12.2 Costing Methods (FIFO, LIFO, Average, Standard) & Ledger Architecture 12.3 Locations, Transfer Routes & Stockkeeping Units (SKUs)
13 Chapter 13: Logistics Master Data, Pricing & Discounts
13.1 Shipping Agents, Locations & Vendor Lead Times 13.2 Sales Prices, Purchase Prices & Price Lists 13.3 Line Discounts, Invoice Discounts & Thresholds
14 Chapter 14: User Interface, Views, Inspection & Excel
14.1 Personalization, Profile Customization & Designer 14.2 Searching, Advanced Filters, Saved Views & Page Inspection 14.3 Edit in Excel, OneDrive & Data Analysis Mode
15 Chapter 15: Purchase & Sales Order Execution
15.1 Purchase Orders, Receiving, Over-Receipt & Undo 15.2 Purchase Invoicing, Recurring Lines & Blanket Orders 15.3 Sales Quotes, Availability Checks & Order Conversion 15.4 Sales Shipping, Invoicing, Undo & Blanket Orders
16 Chapter 16: Invoices, Credit Memos & Document Corrections
16.1 Direct Invoices, Credit Memos & Document Reopening 16.2 Correct, Cancel & Corrective Credit Memo Procedures 16.3 Combined Shipments/Receipts & Prepayment Workflows
17 Chapter 17: Cash Management, Bank Reconciliation & Ledger Applications
17.1 Processing Payment Journals & Cash Receipt Registrations 17.2 Applying, Unapplying & Reversing Customer/Vendor Entries 17.3 Bank Account Reconciliation & Statement Matching Rules
18 Chapter 18: Operational Adjustments, Inventory & Asset Accounting
18.1 Exchange Rate Adjustments & Dimension Corrections 18.2 Inventory Adjustments, Transfers & Physical Counting 18.3 Fixed Asset Acquisitions, Depreciation Runs & Disposals
12.3 Locations, Transfer Routes & Stockkeeping Units (SKUs)
Key Takeaways Explain This Topic AI
Locations define physical or logical operating facilities, with configurable warehouse complexity tiers ranging from basic document posting up to directed put-away and pick with bin mandatory enforcement.
In-Transit locations are specialized non-physical locations that track inventory ownership during transit between facilities, barring permanent stock storage, direct vendor receipts, and bin assignments.
Transfer Routes establish formal logistics channels between source and destination locations, specifying mandatory in-transit locations, shipping agents, and shipping time calculations.
Stockkeeping Units (SKUs) allow organizations to localize item planning, replenishment, and costing rules across specific locations and variants, completely superseding Item Card parameters for that context.
SKUs enable decentralized supply chain strategies by allowing a single item master to be replenished via Purchase at a central hub and replenished via Transfer at regional branch warehouses.
Last updated: September 2026
12.3 Locations, Transfer Routes & Stockkeeping Units (SKUs)
Quick Summary: In Dynamics 365 Business Central, a Location (Table 14) represents a distinct physical or logical site where inventory is stored. Locations can range in warehouse complexity from simple direct order posting to advanced Directed Put-away and Pick . Goods moving between facilities are tracked using Transfer Orders routed through specialized In-Transit Locations via defined Transfer Routes . To handle regional differences in replenishment, costing, and lead times, organizations implement Stockkeeping Units (SKUs) (Table 5700), which localize item planning and replenishment rules by Location and Variant, overriding global Item Card settings.
Multi-Location Infrastructure & The Location Card
The Location Card ( Alt+Q -> type Locations , Page 5703 / Table 14) defines facilities such as warehouses, retail stores, manufacturing plants, or third-party logistics (3PL) distribution centers. UI Navigation Path:
- Tell Me (Alt+Q) -> Locations -> Action Bar: New -> Location Card
- The "Use As In-Transit" Location
A vital operational toggle on the General FastTab of the Location Card is Use As In-Transit :
Purpose: Represents an intermediary virtual location used to maintain financial balance sheet custody of goods while they are physically in transit between two company facilities.
Legal & Financial Ownership: Inventory residing in an in-transit location is fully capitalized on the general ledger balance sheet as corporate inventory, but it cannot be reserved, picked, or sold to customers.
Strict Restrictions: In-Transit locations cannot utilize bins, cannot have warehouse handling flags enabled (such as Require Receive or Require Shipment), cannot be used as a standard line location on sales or purchase orders, and cannot store permanent static inventory.
Warehouse Complexity Tiers on the Location Card
Business Central allows organizations to scale warehouse operations across five progressive complexity levels by configuring checkboxes on the Warehouse FastTab of the Location Card: Warehouse Complexity Spectrum:
- [Level 1: Basic] ──► Direct Sales/Purchase Document Posting (Zero warehouse docs)
- [Level 2: Receipts] ──► Require Receive / Require Shipment (Separate warehouse documents)
- [Level 3: Put/Pick] ──► Require Put-away / Require Pick (Inventory Put-aways / Picks)
- [Level 4: Bins] ──► Bin Mandatory (Tracks shelf/rack/bin coordinates)
- [Level 5: Advanced] ──► Directed Put-away and Pick (Zones, Bin Types, Bin Ranking, WMS)
- Progressive Warehouse Handling Configurations
Warehouse Level Active Toggles on Location Card Generated Documents & Workflow
Level 1: Minimal / Direct All warehouse toggles set to No . Users post receipts and shipments directly from Sales Orders and Purchase Orders. Ideal for small offices or retail stores.
Level 2: Warehouse Documents Require Receive and/or Require Shipment = Yes . Generates Warehouse Receipts and Warehouse Shipments . Decouples physical dock loading from accounting order entry.
Level 3: Internal Handling Level 2 + Require Put-away and/or Require Pick = Yes . Generates dedicated Warehouse Put-away and Warehouse Pick documents to guide warehouse floor personnel.
Level 4: Bin Enforcement Level 3 + Bin Mandatory = Yes . Enforces that every inventory receipt, shipment, and adjustment must specify a valid Bin Code (Aisle-Rack-Shelf).
Level 5: Advanced WMS Directed Put-away and Pick = Yes (Requires Bin Mandatory) . Full enterprise WMS. Requires Zones, Bin Types, Bin Ranking, dedicated inbound/outbound bins, cross-docking, and item class tracking.
Bin Architecture & Bin Types
When Bin Mandatory is enabled, facilities are subdivided into bins representing physical storage slots:
Bin Types: Categorize operational permissions ( RECEIVE , SHIP , PUTAWAY , PICK , PUTPICK ).
Default Bins: Defined per item or location to automate document line suggestions.
Dedicated Bins: Locked to specific items to prevent cross-contamination or mixed stock.
Transfer Routes & In-Transit Logistics Execution
Moving inventory between physical facilities requires a formal audit trail. Organizations configure the Transfer Routes matrix ( Alt+Q -> type Transfer Routes , Page 5740 / Table 5742) to automate logistics parameters. Transfer Order Logistics Flow:
- [Origin: MAIN Warehouse]
- │
- ▼ (Action: Post Shipment)
- [In-Transit Location: INTRANSIT] ──► Owned by company; Goods in transit on carrier truck
- │
- ▼ (Action: Post Receipt)
- [Destination: STORE-1]
- Transfer Route Components
For every unique combination of Transfer-from Code (Origin) and Transfer-to Code (Destination), consultants define:
In-Transit Code: Specifies the dedicated in-transit location (e.g., INTRANSIT ).
Shipping Agent Code: Identifies the logistics carrier (e.g., FEDEX , UPS , DHL ).
Shipping Agent Service: Specifies the transit speed (e.g., NEXTDAY , GROUND ).
Shipping Time: A date formula (e.g., 1D , 2D , 1W ) used by the system's lead-time calculation engine to predict expected receipt dates at the destination.
The Two-Step Transfer Order Process
When executing a Transfer Order ( Alt+Q -> type Transfer Orders , Page 5740):
Step 1: Post Shipment: Relieves stock from the origin location (e.g., MAIN ) and increases inventory in the INTRANSIT location. The system creates negative Item Ledger Entries at MAIN and corresponding positive Item Ledger Entries at INTRANSIT .
Step 2: Post Receipt: Relieves stock from the INTRANSIT location and increases inventory at the destination location (e.g., STORE-1 ). Inventory valuation remains unbroken throughout the lifecycle.
Stockkeeping Units (SKUs): Localizing Master Data & Supply Chain Rules
In a distributed enterprise, managing an item purely through global settings on the Item Card is inadequate. A product might be manufactured at a central plant, purchased from a local vendor at a regional hub, and replenished via transfer at retail branches. Stockkeeping Units (SKUs) ( Alt+Q -> type Stockkeeping Units , Page 5701 / Table 5700) resolve this by establishing localized item definitions. Item Card vs Stockkeeping Unit Architecture:
- ┌────────────────────────────┐
- │ ITEM CARD: CHAIR-100 │
- │ Global Costing: FIFO │
- │ Global Replenish: Purchase │
- └─────────────┬──────────────┘
- │
- Local Overrides per Location & Variant
- ▼
- ┌───────────────────────────┐ ┌───────────────────────────┐ ┌───────────────────────────┐
- │ SKU: MAIN Location │ │ SKU: WEST Location │ │ SKU: STORE-1 Location │
- │ Replenish: Purchase │ │ Replenish: Prod. Order │ │ Replenish: Transfer │
- │ Vendor: VEND-100 │ │ Routing: ROUT-200 │ │ Transfer-from: MAIN │
- │ Reorder Policy: Maximum │ │ Reorder Policy: Order │ │ Reorder Policy: Fixed │
- └───────────────────────────┘ └───────────────────────────┘ └───────────────────────────┘
- Automated Creation of SKUs
Rather than creating SKUs manually, consultants run the Create Stockkeeping Unit batch job ( Alt+Q -> type Create Stockkeeping Unit , Report 5706):
Create Per: Location , Variant , or Location & Variant .
Item Filters: Selects specific product groups or active items.
Automatically copies baseline parameters from the Item Card to the new SKU records.
Parameter Overrides at the SKU Level
Functional Tab Overridable Fields Operational Impact & Planning Behavior
Costing Unit Cost, Standard Cost, Last Direct Cost Permits localized valuation to reflect regional freight, tariffs, or local vendor pricing differences.
Replenishment Replenishment System ( Purchase , Prod. Order , Transfer , Assembly ) Critical for multi-echelon supply chains. Central hubs are set to Purchase or Prod. Order , while branch locations are set to Transfer .
Transfer Fields Transfer-from Code , Shipping Agent Code, Shipping Agent Service Directs the Planning Worksheet to generate Transfer Orders from a specific supplying warehouse rather than purchase orders.
Planning Policies Reordering Policy ( Fixed Reorder Qty. , Maximum Qty. , Order , Lot-for-Lot ) Tailors replenishment calculations to local demand volume. High-volume hubs use Maximum Qty. , while remote stores use Fixed Reorder Qty.
Planning Modifiers Safety Stock Qty., Reorder Point, Reorder Qty., Min/Max Order Qty., Order Multiple Governs exact lot-sizing rules, lead times, and buffer stocks per facility.
Important
Planning Precedence Rule: When calculating the Planning Worksheet or Requisition Worksheet , Business Central checks for the existence of an SKU record for the specific Item + Location + Variant . If an SKU exists, the planning engine exclusively honors the SKU parameters , completely ignoring the Item Card's replenishment and planning fields.
- Step-by-Step UI Configuration Workflows
- Workflow A: Setting Up a New Warehouse Location with Bins
Press Alt+Q , type Locations , and select New .
In the Code field, enter DIST-1 ; enter a descriptive Name and physical address.
On the Warehouse FastTab:
Set Require Receive to Yes .
Set Require Shipment to Yes .
Set Require Put-away to Yes .
Set Require Pick to Yes .
Set Bin Mandatory to Yes .
In the action bar, select Location -> Bins .
Create bin records (e.g., RECEIVE , SHIP , A-01-01 , A-01-02 ) with assigned Bin Types.
Return to the Location Card and assign default bins under the Bin Setup FastTab.
Workflow B: Configuring a Transfer Route
Press Alt+Q , type Transfer Routes , and select the related link.
In the grid, locate the intersection of Transfer-from Code MAIN and Transfer-to Code STORE-1 .
In the line details:
In In-Transit Code , select INTRANSIT .
In Shipping Agent Code , select FEDEX .
In Shipping Agent Service , select GROUND .
Enter 2D in Shipping Time .
Workflow C: Creating and Configuring a Branch SKU
Press Alt+Q , type Stockkeeping Units , and select New .
On the SKU Card, enter Item No. 1000 and Location Code STORE-1 .
On the Replenishment FastTab:
Change Replenishment System from Purchase to Transfer .
In Transfer-from Code , enter MAIN .
On the Planning FastTab:
Set Reordering Policy to Fixed Reorder Qty.
Set Reorder Point to 10 .
Set Reorder Quantity to 25 .
Set Safety Stock Quantity to 5 .
Common Implementation Pitfalls & Exam Traps
Pitfall 1: Missing Transfer Route Definition. If a user attempts to release or post a Transfer Order between two locations where no Transfer Route has been configured, Business Central throws a validation error stating that an In-Transit location must be specified. Transfer routes must be established before executing transfers.
Pitfall 2: Attempting to Enable Bins on an In-Transit Location. Enabling the Use As In-Transit toggle locks all warehouse tabs. Attempting to assign bin codes to an in-transit location is blocked by platform validation.
Pitfall 3: Assuming Item Card Changes Update Existing SKUs. Modifying replenishment or planning parameters on the Item Card does not update pre-existing SKU records. Consultants must update the SKU cards directly or re-run the Create Stockkeeping Unit batch job with update options.
Pitfall 4: Leaving Transfer-from Code Blank on Transfer SKUs. When an SKU has its Replenishment System set to Transfer , omitting the Transfer-from Code causes the Planning Worksheet to fail during calculation, as it cannot determine the supplying source location.