Business Central 2026 Wave 1 Subcontracting: Warehouse Flows, Pricing Rules and Italian Migration

With the launch of Roadmap ID 576872—which reached general availability on July 8, 2026, as part of the Dynamics 365 Business Central 2026 release wave 1 —Microsoft has significantly expanded its standard worldwide (W1) subcontracting capabilities. Enabled by administrators, makers, or analysts for end users across standard multi-tenant cloud instances, this update brings advanced logistics flows, warehouse handling, item tracking, and granular subcontractor pricing directly into the core Business Central ecosystem.

For manufacturing leads and IT administrators, this is not just a minor quality-of-life patch. It represents a structural shift in how Dynamics 365 Business Central handles outsourced production—and for organizations running the Italian localization, it marks the beginning of a mandatory architectural transition toward the global W1 standard.

What Changed in the 2026 Release Wave 1 Update​

To appreciate what Microsoft has delivered, it helps to distinguish between Business Central's baseline capabilities and the extended features provided through Microsoft's official Subcontracting extension. Out of the box, without the extension installed, Business Central has long offered basic subcontracting tools: administrators could link a work center to a vendor via the Subcontractor No. field and calculate operation costs based on either production time or a flat charge per unit.

However, real-world supply chains demand far more than basic time-and-unit math. When you ship raw materials across state or national borders to a third-party fabricator, you need strict chain-of-custody tracking, serial and lot visibility, and multi-tiered vendor pricing. According to Microsoft Learn's release plan documentation, the July 2026 update expands the standard solution with five core pillars:

• Component and Raw Material Logistics: Dedicated logistics flows that manage transfers of raw materials and components to subcontractors, complete with warehouse handling and item tracking.
• Flexible Subcontractor Pricing: A multi-dimensional pricing engine that evaluates the work center, item, validity dates, and order quantity—along with variants, standard tasks, and minimum order floors.
• Finished Goods Receipts: The ability to process finished goods receipts directly from purchase orders with full item tracking (serial and lot numbers) and warehouse handling.
• Finished Goods Transfer Flows: End-to-end logistics flows designed to manage subcontractor transfers of finished goods.
• Usability and Transparency: Enhanced role center visibility, factboxes, and document connections that keep production orders, transfer orders, and purchase orders tightly synchronized.

Section Summary: While Business Central previously handled basic vendor-linked work centers, the July 2026 launch introduces comprehensive warehouse handling, serial/lot item tracking, component transfer flows, and multi-variable pricing to the global W1 subcontracting framework.

Under the Hood: Configuring Subcontracting and Warehouse Flows​

How does an ERP administrator actually wire this up without stalling the production line? According to Microsoft Learn's subcontracting setup documentation, everything starts by installing the Microsoft-published Subcontracting extension from the Extension Management page or Microsoft Marketplace. Once installed, admins can launch the Set up Subcontracting assisted setup guide, or configure defaults manually on the Subcontracting FastTab within the Manufacturing Setup page.

Critical Setup Parameters and Guardrails​

Before generating your first subcontracted order, several architectural rules in Business Central require close attention:

1. Work Centers Only (No Machine Centers): When building routings for subcontracted operations, the routing line's Type field must be set to Work Center. Microsoft explicitly warns that Machine Center operations do not support subcontractor assignments. If you accidentally assign a subcontractor step to a Machine Center, automatic location changes, subcontractor pricing, and purchase order creation will simply fail to trigger.
2. Transfer Routes and In-Transit Codes: To move components or Work in Process (WIP) items between your main warehouse and a vendor's facility (defined via the Subc. Location Code on the vendor card), Microsoft recommends configuring Transfer Routes with an explicit In-Transit Code. If you skip setting up a transfer route, Business Central defaults to creating direct transfer orders—which carry severe limitations if either your source warehouse or the destination location relies on advanced warehouse handling. Administrators should also verify the Direct Transfer Posting setting on the Inventory Setup page.
3. Component Transfer Lead Times: On the Manufacturing Setup page, the Subcontracting Component Transfer Lead Time field ensures materials arrive before the vendor is scheduled to start work. Business Central calculates the transfer order receipt date using a straightforward formula:
   Receipt Date = Due Date of Production Order Component - Subcontracting Component Transfer Lead Time
4. Component Costing Strategy: Administrators must set the Component Direct Unit Cost option to either Standard (which pulls from normal purchase prices and discounts) or Prod. Order Component (which pulls the calculated direct unit cost from the production order component line).

Section Summary: Proper deployment requires installing the Subcontracting extension, restricting outsourced routing steps to Work Centers rather than Machine Centers, and establishing In-Transit transfer routes to prevent conflicts with advanced warehouse handling.

The Pricing Engine: Why "Highest Minimum Quantity" Beats "Lowest Price"​

If there is one technical detail in this release that every purchasing manager, cost accountant, and ERP consultant needs to tape to their monitor, it is how Business Central calculates subcontractor prices.

In standard Business Central purchasing, when an item qualifies for multiple price tiers, the ERP compares all valid lines and generously selects the lowest price for the buyer. Subcontractor pricing does not work that way.

According to Microsoft Learn's subcontractor pricing documentation, when Business Central evaluates the Subcontractor Prices table—which requires a Work Center No., Vendor No., and Item No., and can optionally filter by Standard Task Code, Variant Code, Starting Date, Ending Date, Unit of Measure Code, and Currency Code—it selects the quantity-break tier with the highest Minimum Quantity that is less than or equal to the order quantity.

Why does that distinction matter? Suppose a vendor price list contains two qualifying entries for the same work center and item:

• Tier 1: Minimum Quantity = 1 | Direct Unit Cost = $15.00
• Tier 2: Minimum Quantity = 50 | Direct Unit Cost = $18.00

If you place an order for 80 units, both tiers technically qualify. Instead of picking the cheaper $15.00 rate, Business Central selects Tier 2 ($18.00) because 50 is the highest qualifying minimum quantity threshold. It assumes that the higher quantity bracket represents the most specific tier for that volume.

Silent Minimum Amount Floors and Overhead Math​

In addition to quantity tiers, price lines support a Minimum Amount field, which acts as a batch fee or minimum charge per production order. If a vendor charges $10.00 per unit with a $50.00 minimum amount, and you release a production order for just 3 units, the raw total ($30.00) falls below the floor. Business Central will silently recalculate the Direct Unit Cost upward without displaying a warning dialog:

Direct Unit Cost = Minimum Amount ÷ Quantity ($50.00 ÷ 3 = $16.67 per unit).

Furthermore, the Direct Unit Cost entered on the Subcontractor Prices page reflects only what you pay the external vendor. To capture internal administration, quality inspection, or logistics costs, Business Central layers the work center's Indirect Cost % and Overhead Rate on top using this formula:

Unit Cost per = Direct Unit Cost × (1 + Indirect Cost % / 100) + Overhead Rate

If a planner manually edits the Unit Cost per field directly on a production order routing line, Business Central automatically back-calculates the vendor's Direct Unit Cost by stripping out the overhead:

Direct Unit Cost = (Unit Cost per - Overhead Rate) / (1 + Indirect Cost % / 100)

Section Summary: Unlike standard purchase pricing, Business Central's subcontractor pricing engine selects the highest qualifying minimum quantity tier rather than the lowest unit cost, silently adjusts unit prices upward to meet minimum order amounts, and automatically separates vendor direct costs from internal work center overhead.

Day-to-Day Execution: Orders, Warehouse Receipts, and Gotchas​

Once your routings and prices are live, planners have two pathways to generate subcontracting purchase orders from Released Production Orders:

1. Direct Creation from the Routing: Open a released production order, navigate to Routing, highlight one or more subcontracted operations, and click Create Subcontracting Order. Crucial caveat: If you select multiple routing lines here, Business Central generates a separate purchase order for every single line—it will not consolidate them, even if they share the exact same subcontractor.
2. Batch Creation via the Subcontracting Worksheet: Open Subcontracting Worksheets, run Calculate Subcontracts, review the lines, and select Carry Out Action Message. Unlike direct creation, if multiple subcontracted operations are destined for the same vendor location, the worksheet consolidates them into a single purchase order.

In both workflows, any comments attached to the routing operation flow onto the purchase order as zero-quantity text lines, and routing file attachments with Document Flow Production and Document Flow Purchase toggled on will automatically carry over to the purchase line.

Warehouse Handling, Item Tracking, and the "Last Operation" Trap​

When the subcontractor finishes the job and ships the goods back, how Business Central handles the receipt depends entirely on your warehouse setup and whether the operation is an intermediate step or the final operation on the routing:

• Warehouse Receipts and Inventory Put-aways: For locations requiring receipt or put-away processing, users can trigger Create Whse. Receipt or Create Inventory Put-away/Pick... directly from the released subcontracting purchase order.
• Serial and Lot Tracking Boundary: If an item requires serial or lot tracking, warehouse staff can assign or verify tracking numbers on the final routing operation before posting. Microsoft notes that intermediate routing operations do not support item tracking during receipt or put-away; intermediate steps record capacity ledger entries only, generating zero item ledger, value, or warehouse entries.
• The Automatic Output Trap: When a subcontracting purchase order is posted as received, Business Central posts a capacity ledger entry. However, if that subcontracted step happens to be the last operation on the production order routing, posting the purchase receipt automatically posts an output journal entry for the entire production order. As Microsoft cautions in its documentation, automatic output posting can skew expected quantities and posting dates. To prevent premature output posting, manufacturing engineers should ensure the subcontracted step is not the final operation—for instance, by adding an internal final inspection or put-away operation at the end of the routing.
• Invoicing and Undo Restrictions: Subcontracting purchase orders must be invoiced directly from the purchase order itself; you cannot pull them into a separate purchase invoice using Get Receipt Lines or Get Order Lines. If a receipt is posted in error prior to invoicing, you can use Undo Receipt on the Posted Purchase Receipt—but be warned that if component consumption was triggered automatically via flushing methods, undoing the receipt will not reverse the component consumption. You will need to reverse those via an output journal or the Reverse Production Order Transaction action.
• Document Locking: To prevent inventory mismatches while materials are physically sitting at a vendor's shop, Business Central locks the Quantity, No., Bin Code, and Unit of Measure Code fields (and prevents line or order deletion) whenever transfer orders exist or stock remains at the subcontractor location. The Variant Code is permanently locked on linked subcontracting purchase lines.

Section Summary: Creating orders via the Subcontracting Worksheet consolidates vendor POs whereas direct routing creation does not. Furthermore, admins must guard against automatic output posting on final routing operations and remember that serial/lot item tracking applies only to final-operation receipts.

Special Advisory for Italian Localization (IT) Environments​

While this roadmap update is a welcome capability expansion for global users, it carries a specific deprecation mandate for organizations running the Italian localization of Dynamics 365 Business Central.

Historically, the Italian version of Business Central maintained its own bespoke localization for managing subcontractor raw material transfers and finished goods logistics. With the 2026 release wave 1, Microsoft is officially deprecating the legacy Italian subcontracting functionality and replacing it with the unified global (W1) solution.

According to Microsoft's documentation, administrators control the timing of this cutover by activating a feature key on the Feature Management page, though several operational realities apply:

• Starting with Business Central version 28.3, the legacy Italian subcontracting features are hidden by default in newly provisioned environments (though they can be temporarily re-enabled via Manufacturing Setup).
• To transition existing environments, Microsoft provides an IT Subcontracting Migration app alongside the core Subcontracting extension.
• Strict Migration Prerequisites: You must test the migration in a sandbox environment first. Before running the migration in production, all open WIP transfer orders and related purchase orders must be completed. The migration process locks affected tables while running, is irreversible, and migrates only master data and open documents—it does not convert historical or posted transactions.

Final Thoughts for ERP Administrators​

By bringing raw material transfers, warehouse receipts, serial/lot tracking, and multi-tiered vendor pricing into the standard W1 subcontracting architecture, Microsoft has closed a longstanding gap between lightweight SMB manufacturing and enterprise supply chain management. Whether you are rolling out the Subcontracting extension for the first time or preparing an Italian tenant for migration, take the time to audit your Work Center routings, configure your In-Transit transfer routes, and test the quantity-tier pricing behavior in a sandbox before turning your buyers loose in production.