Dynamics 365 Supply Chain UAT: What Operations Teams Need to Test Before Go-Live

A Dynamics 365 Supply Chain Management go-live that works in testing and fails in production almost always fails for the same reason: the UAT was run module by module, not end-to-end. Purchase order approvals were tested without inventory. Warehouse pick logic was tested without the sales order volume that triggers replenishment. Production orders were tested against a simplified BOM that didn't reflect the actual item configurations in use.

The result is a go-live where everything worked in UAT and the first real operational week produces a cascade of issues: stock allocated to orders that can't be fulfilled, purchase invoices posting to the wrong account, warehouse staff unable to complete pick tasks because location directives haven't been configured for the actual warehouse layout. These failures are configuration failures — and they are almost entirely preventable with a UAT cycle designed around real operational scenarios rather than module-by-module functionality checks.

Why SCM UAT is harder than it looks

Dynamics 365 Supply Chain Management is not a standalone module. It sits at the intersection of Finance (every goods receipt generates an accrual; every purchase invoice posts to a GL account), Warehouse Management (every sales order line triggers pick work; every purchase order line triggers put-away), Production (every manufactured item draws from a BOM and follows a production route), and external systems (3PL partners, supplier portals, demand planning tools, EDI feeds).

The configuration decisions made in each of these areas interact with each other. A change to an item's storage dimension group affects how it can be reserved, picked, and tracked. A change to a vendor's payment terms affects the cash flow forecast that Finance relies on. A production route change affects the work centre scheduling that Operations uses to plan capacity. Testing any one of these in isolation confirms that the configuration is self-consistent — not that it is correct when the full system runs.

“The failure mode that causes the most operational disruption isn't a single broken feature. It's the interaction between two correctly configured features that produces incorrect behaviour when they run together. That interaction is exactly what isolated module testing misses.”

1. Inventory reservation and allocation logic

Inventory reservation is the single most common source of post-go-live operational failures in Dynamics 365 SCM deployments. The reservation model — which determines how and when stock is committed against sales orders, production orders, and transfer orders — must be configured and tested against real demand patterns, not synthetic test data with convenient round numbers.

• —Single-warehouse reservation — confirm that a sales order reservation correctly reduces available inventory and prevents double-allocation against a concurrent order
• —Multi-warehouse reservation — test scenarios where stock exists across multiple warehouses and sites; verify that reservation logic selects the correct source based on the configured priority rules
• —Batch and serial number reservation — for items tracked at batch or serial level, test reservation at the batch/serial level including FEFO (first-expiry, first-out) and FIFO logic
• —Partial fulfilment — test what happens when a sales order quantity cannot be fully reserved; verify backorder creation, partial shipment confirmation, and reservation behaviour on the remainder
• —Reservation against transfer orders — validate that stock in transit is correctly excluded from available-to-promise calculations during the in-transit period
• —Over-delivery and under-delivery tolerances — confirm that goods receipt over-delivery and under-delivery tolerance percentages are configured and behave correctly at purchase order level

2. Purchase order and procurement workflows

Purchase order approval workflows in Dynamics 365 are configured using the workflow engine — a powerful but unforgiving system where a misconfigured condition or an incorrectly assigned approver role can result in purchase orders that route to the wrong person, get stuck in an approval limbo, or — most dangerously — bypass approval entirely because no matching rule was found.

• —Standard purchase order creation and approval — full cycle from requisition through purchase order creation, approval routing, and vendor acknowledgement
• —Value threshold routing — purchase orders above defined thresholds must route to the correct approver tier; test at threshold boundaries, not just at comfortable values well below the limit
• —Cross-legal-entity purchasing — for multi-entity deployments, test intercompany purchase orders where the buying entity and the selling entity are different legal entities in the same D365 instance
• —Goods receipt against PO — post a goods receipt for a subset of a purchase order line and verify correct partial receipt accounting, remaining quantity on order, and accrual posting
• —Purchase invoice matching — configure and test the three-way match (PO, goods receipt, invoice) and confirm that mismatches trigger the correct exception workflow
• —Vendor returns — return to vendor process tested from the return purchase order through vendor credit note receipt and credit posting

3. Warehouse Management System (WMS) configuration

If your Dynamics 365 SCM deployment uses the built-in Warehouse Management module (WMS), the UAT scope expands significantly. WMS in D365 uses a system of location directives, work templates, and wave templates that together determine how inbound and outbound work is generated, directed, and completed. These configurations are highly dependent on the physical layout of the warehouse, the product mix being handled, and the operational processes the warehouse team uses daily.

WMS UAT must be performed with warehouse team members who work in the actual warehouse — using handheld devices in the UAT environment, not desktop browsers — against a warehouse layout that mirrors production. Tests to include:

• —Inbound receiving and put-away — receive a purchase order against a realistic inbound load; confirm location directives route goods to the correct zone and bin based on item storage dimensions and zone rules
• —Sales order pick and pack — generate pick work for a representative sales order mix; confirm work sequence, zone routing, and label printing all behave correctly
• —Cluster picking — if cluster picking is configured, test multi-order cluster generation and validate correct product and quantity assignment per tote
• —Replenishment work — trigger replenishment by running the sales order to below the minimum threshold in a pick location; confirm replenishment work is generated and routes to the correct reserve location
• —Cycle counting — initiate a cycle count for a representative location set and validate that count results update on-hand inventory correctly without creating phantom movements
• —WMS and Finance integration — confirm that goods receipt in WMS generates the correct product receipt in inventory and the correct accrual posting in Finance

4. Sales order fulfilment and shipment confirmation

The sales order fulfilment cycle in Dynamics 365 SCM is the process that customers ultimately experience. A failure here — a shipment that goes to the wrong address, a partial delivery that isn't communicated, a packing slip that doesn't match what's in the box — is immediately visible and immediately reputational. UAT must test the full cycle, including edge cases that don't appear in the standard process flow.

• —Standard order-to-shipment cycle — sales order creation, reservation, pick list generation, pick and pack, shipment confirmation, and customer invoice posting
• —Partial shipment — confirm partial shipment processes correctly, generates a partial invoice, and leaves the remainder on backorder with the correct delivery date
• —Direct delivery (drop shipment) — if direct delivery from vendor to customer is configured, test the full cycle including purchase order generation and vendor invoice matching
• —Customer returns (RMA) — return merchandise authorisation creation, goods return from customer, quality inspection workflow, and credit note posting
• —Freight charges — if freight charges are applied at order or shipment level, confirm correct calculation, invoice inclusion, and GL posting
• —Customer-specific pricing — confirm that customer-specific price agreements and trade allowances apply correctly at order line level

5. Production order flows (for manufacturers)

For organisations using Dynamics 365 SCM for manufacturing, production order UAT is a critical track. Bill of materials (BOM) explosions, production route scheduling, and the cost accounting for work-in-progress (WIP) are all areas where configuration gaps can have significant financial and operational consequences — and none of them surface in sales or procurement testing.

• —BOM explosion — create a production order for a finished good and validate that the BOM explosion produces the correct component requirements at every level for multi-level BOMs
• —Route scheduling — schedule a production order and confirm that work centre capacity, routing operations, and lead times produce a realistic and achievable production schedule
• —Material picking for production — generate picking work for production order components; test from the production floor perspective using handheld devices if WMS is in scope
• —Production reporting — report as finished for a production order and validate correct inventory posting, WIP clearance, and co-product/by-product handling
• —Standard cost variance posting — for organisations using standard costing, validate that production variances (material, labour, overhead) post correctly to the configured variance accounts
• —Subcontracting — if production operations are subcontracted, test the subcontracting purchase order cycle and confirm correct cost accumulation on the production order

“Production order failures in D365 are disproportionately expensive because they compound. A BOM error produces incorrect component consumption. Incorrect consumption produces incorrect inventory. Incorrect inventory produces incorrect demand planning. By the time the root cause is found, the variance has propagated through multiple systems and multiple periods.”

6. Demand forecasting and master planning

Master planning in Dynamics 365 SCM generates planned purchase orders, planned production orders, and planned transfer orders based on demand signals — sales orders, forecasts, minimum stock levels — and supply parameters — vendor lead times, production lead times, safety stock. A master planning run that produces incorrect planned orders is difficult to diagnose because the error may be in the item coverage settings, the forecast model, the BOM structure, or the inventory parameters — any one of which can silently drive an incorrect result.

• —Master planning run — execute a planning run with representative demand data (real sales orders or a realistic forecast) and review planned orders for completeness and correctness
• —Item coverage settings — validate minimum and maximum stock levels, reorder points, and coverage group assignments for representative items from each category
• —Vendor lead time accuracy — confirm that vendor lead times are correctly configured and that planned purchase order dates reflect the correct lead time calculation
• —Transfer order planning — for multi-site deployments, validate that inter-site replenishment plans generate correctly and route to the correct receiving site
• —Forecast consumption — if demand forecasting is in scope, validate that actual sales orders correctly consume the forecast and that net requirements reflect the unconsumed forecast balance

The case for independent SCM UAT

Dynamics 365 SCM implementations are delivered by partner teams who have spent months in configuration. They know the system — the workarounds adopted to fit the customer's processes, the configuration decisions made under time pressure, the integration assumptions that haven't been fully validated. That knowledge is also what makes their UAT unreliable: they test what they configured, not what the business actually needs to run.

Independent UAT specialists approach the SCM deployment the way your operations team will on day one: following a real operational process, with no knowledge of implementation decisions, and no incentive to call a scenario good enough when it isn't. The scenarios they find are the scenarios that matter — because they're the ones the business will actually run, in the sequence the business actually runs them, with the data volumes the business actually generates.

For a manufacturing or distribution business where the first week of production operations will stress every inventory, procurement, and warehouse process simultaneously, the UAT cycle is the last line of defence between configuration and consequence. Independent UAT by specialists who understand both the Dynamics 365 SCM configuration model and the operational processes it supports is how organisations go live without going wrong.