Skip to main content

Subcontracting in BC 2026 Wave 1 — A Manufacturer's Guide to the New Native Framework

 Introduction

Subcontracting has been one of the most common pain points I encounter in Business Central manufacturing implementations. The question I've heard dozens of times is some version of this: "We send components to a vendor for painting / galvanizing / heat treatment — how do we handle that in BC without building a workaround?"

Until now, the honest answer was: with some creative configuration, a fair bit of discipline, and an acceptance that BC's native subcontracting capabilities only handled the cost side of the equation, not the physical movement of goods.

It is worth noting that subcontracting logistics functionality has existed in BC but only within specific localizations, namely India and Italy. Manufacturers running those localizations have had access to logistics flows for subcontractor transfers as a regional capability. With 2026 Wave 1, Microsoft is promoting this to a W1 — worldwide — solution, meaning any BC customer on any localization can now benefit from the same framework. A long-overdue move, and a significant one for the global manufacturing community.

That changes with 2026 Release Wave 1, with General Availability confirmed for June 2026. This post breaks down exactly what's new, what it means in practice, and what manufacturers should think about before enabling it.


What 2026 Wave 1 delivers — the three key capabilities

The new W1 subcontracting framework covers three core areas: logistic flows that manage subcontractor transfers for raw materials and components with warehouse handling and item tracking; flexible pricing that considers the work center, item, dates, and quantity; finished goods receipts with item tracking and warehouse handling from purchase orders; and logistic flow management for subcontractor transfers of finished goods.

Here is what each of these means for a manufacturing operation in practice:

1. Logistic flows for raw material and component transfers

This is the capability that fills the biggest gap. BC can now manage the physical shipment of components to a subcontractor as part of the production workflow — with proper inventory movement, warehouse handling, and item tracking (lot and serial numbers) maintained throughout.

If you send a batch of components to an external vendor for processing, the system now creates and tracks the outbound transfer within the production context. Your inventory reflects that the items are at the subcontractor's location. When they return, the receipt is handled with full traceability back to the original lot or serial number.

For manufacturers in industries like automotive, aerospace, medical devices, or food and beverage — where lot traceability through every production step including subcontracted operations is a regulatory requirement — this is significant.

Practical tip: When setting up the new framework, map your subcontractor locations carefully in the system before go-live. Each subcontractor site that holds your inventory at any point in the process should have its own location code. This keeps your inventory position accurate and makes the transfer logic work correctly.

2. Flexible subcontracting pricing

Previously, subcontracting pricing in BC was relatively blunt — essentially a standard cost per unit tied to the routing operation. The new framework supports pricing that varies by work centre, item, date range, and quantity.

This reflects how subcontracting pricing actually works in the real world. A vendor might charge differently depending on which of their machines processes your parts, offer volume discounts above a certain quantity threshold, or apply seasonal rate adjustments. BC can now accommodate these pricing structures natively without requiring custom fields or workaround tables.

Practical tip: Use the date-range pricing capability to manage annual subcontractor rate agreements. Set up the agreed rates at the start of each contract period and let the system apply them automatically rather than relying on manual updates when purchase orders are raised.

3. Finished goods receipts with full item tracking

When processed goods return from a subcontractor, they can now be received back into BC via a purchase order with complete item tracking and warehouse handling — meaning lot and serial numbers are preserved and warehouse bin management is respected on receipt.

Previously, this was another area requiring workarounds. The new framework makes the return receipt a first-class transaction in the system, properly linked to the originating production order.

Practical tip: For items that require quality inspection on return from a subcontractor — for example, heat-treated components that need a hardness test before going back into production — consider integrating this receipt point with a quality hold or quarantine workflow. Native quality management capabilities are also arriving in BC 2026 Wave 1, and combining the two features creates a clean end-to-end process.


Before enabling, my recommended checklist:

  • Test in a sandbox environment against your actual subcontracting scenarios — not just the demo dataset
  • Review your current subcontractor location setup and align it with the new framework's expectations
  • Confirm with your warehouse team how the new receipt and transfer flows will affect their daily picking and put-away processes
  • If you are in a regulated industry, document the new traceability flow for your quality management system before go-live

Who benefits most from this update

Not every BC manufacturing customer will need the full new subcontracting framework immediately. Here is a straightforward assessment:

High benefit — adopt promptly: Manufacturers who send components to external vendors for processing (heat treatment, surface finishing, machining, assembly) and need full lot or serial traceability through those external steps. Also manufacturers in regulated industries where the previous workaround approach created audit risk.

Moderate benefit — worth evaluating: Manufacturers who subcontract volume that is significant enough that the flexible pricing capabilities would reduce manual effort in managing rate agreements and purchase order pricing.

Lower immediate benefit — no rush: Manufacturers where subcontracting is a minor part of the production process, the existing workaround is working reliably, and the team's bandwidth is better spent on other priorities.


Final thought

This is one of the most practically impactful manufacturing updates Microsoft has planned for BC in upcoming waves, with General Availability confirmed for June 2026 as part of 2026 Release Wave 1. Subcontracting logistics has been a real gap that has forced experienced consultants to build workarounds for years. The W1 framework is a mature, well-designed solution that addresses the core problems correctly.

If you manage BC manufacturing implementations, I would recommend getting hands-on with this feature in a sandbox as soon as it reaches preview — before your clients start asking about it. The questions are coming.

Once the feature is available in preview mode, I will be sharing a step-by-step guide covering the full setup and how transactions will flow end to end — stay tuned!

Comments

Popular posts from this blog

Manufacturing Costing — What Changed in recent versions (BC26 & 27) and Why It Matters

  Introduction Manufacturing costing has always been one of the most technically demanding areas of a Business Central implementation. Get it right and you have a reliable, real-time view of what it actually costs to make your products. Get it wrong and your P&L tells a story that doesn't match your shop floor. In 2025, Microsoft has made meaningful improvements to manufacturing costing across both Wave 1 and Wave 2 — which targeted fixes to gaps that practitioners like me have been navigating in our implementations. This post walks through what changed, what it means in practice, and what you should do about it. Quick reference — what's available and when All four features covered in this post are already generally available. Here's the version map so you know exactly what you need to be running: Feature Wave GA Date BC Version Non-inventory items in production cost Wave 1 20...

BC vs Traditional ERP — A Manufacturer's Perspective

  BC vs Traditional ERP — A Manufacturer's Perspective Introduction After 11 years implementing ERP systems — first as a production planner on the shop floor, then as a functional consultant— I've sat on both sides of the table. I've felt the frustration of a clunky legacy ERP as a user, and I've guided manufacturers through the transition to Microsoft Dynamics 365 Business Central as a consultant. The question I get most often from manufacturers considering a move is simple: "Is BC really different, or is it just another ERP with a new logo?" The honest answer is: It depends on how you implement it; flexibility that actually fits the way a factory works. Here are the most practical differences I've observed, and the tips that make the difference in real-world manufacturing implementations. 1. Traditional ERP was built for Accounting, Extended to Manufacturing Most legacy ERP systems were designed from the financial ledger outward. Manufa...