D365 2024 Wave 1 - What's Actually Useful for Food Distribution

Microsoft's 2024 Wave 1 release for Dynamics 365 Finance & Operations has been in production for several months now. We're running it in our sandbox environment as we prepare for our migration from S2K. Here's my assessment filtered through the lens of food distribution.

The Copilot Features - Cautious Optimism

Microsoft has been pushing Copilot across all products. Wave 1 added Copilot capabilities to several F&O areas. My honest take: some promise, much hype.

Copilot for workspace summaries: You can ask questions about your workspaces in natural language. "Show me overdue invoices over $10,000" type queries. It works for simple questions. Complex queries or questions requiring joins across multiple data entities often fail or return confusing results.

Verdict: Interesting for occasional ad-hoc queries. Not replacing proper reports anytime soon.

Copilot for demand forecasting: AI-assisted demand planning sounds great for food distribution where forecasting spoilable inventory is critical. In practice, the Wave 1 implementation is basic - it's largely a natural language interface to existing forecasting features, not new AI-driven forecasting capabilities.

Verdict: Wait for Wave 2. The underlying forecasting hasn't fundamentally improved.

Warehouse Management Improvements

We use BFC Dakota for WMS, so D365's native warehouse management is less relevant for us. But I tested these features anyway:

Mobile app improvements: The warehouse mobile app got UI refreshes and improved scanning performance. For companies using native WMS, this is a quality-of-life improvement. The app is noticeably snappier than previous versions.

Wave template enhancements: More flexibility in how work is created and grouped. You can now create wave templates that consider more factors - useful for complex distribution scenarios.

Load building improvements: Better tools for optimizing how items are loaded onto trucks. For food distribution with mixed-temperature shipments, this could help prevent cross-contamination scenarios.

For us, these don't change our BFC Dakota strategy, but they show Microsoft is investing in warehouse capabilities.

Finance Module Updates

Bank reconciliation enhancements: This is genuinely useful. The improved matching algorithms catch more automatic matches, and the exception handling UI is cleaner. Our finance team tested it and appreciated the improvements.

Accounts receivable workflow: Better collection workflows with more automation options. You can now create more sophisticated collection strategies based on customer segments, payment history, and aging buckets.

Financial dimension defaults: Easier configuration of default financial dimensions across the system. Small improvement, but it reduces setup time and configuration errors.

Supply Chain Features

Inventory visibility improvements: Better real-time inventory visibility across locations. The ATP (available to promise) calculations are faster and more accurate. For food distribution where inventory accuracy directly affects spoilage and customer satisfaction, this matters.

Planning optimization updates: Master planning runs faster with the planning optimization service. For companies with complex planning scenarios, the performance improvements are significant. We've seen planning runs complete 40% faster in testing.

Quality management updates: More flexible quality testing workflows. For food safety compliance, you can now configure quality checks that enforce specific testing protocols based on product type, vendor, or lot.

What's Missing for Food Distribution

Every release, I look for certain features that would make D365 truly great for food distribution. Still waiting:

Native catch weight improvements: Catch weight handling in D365 works but remains clunky. The dual-unit-of-measure challenges persist. Wave 2 promises improvements; we'll see if they materialize.

Better lot tracking for compliance: FSMA (Food Safety Modernization Act) requires detailed traceability. D365's lot tracking is adequate but not purpose-built for FDA compliance. We'll need third-party solutions or customization.

Temperature tracking integration: Cold chain management is critical for food distribution. Native integration with IoT temperature monitoring would be valuable. Currently requires custom development or third-party add-ons.

Delivery scheduling flexibility: Food customers often have specific delivery windows, dock assignments, and receiving requirements. D365's delivery scheduling is basic compared to specialized route planning software.

Platform and Integration Improvements

Dual-write improvements: The synchronization between F&O and Dataverse (which enables Power Platform integration) is more reliable. Fewer sync failures, better error messages, improved conflict resolution.

Data entity performance: Several standard data entities got performance optimizations. Our data integration tests show 20-30% improvement in data export speeds.

API versioning: Better support for API versioning means we can upgrade D365 without necessarily breaking our Adobe Commerce integration. This reduces the risk of service updates causing integration failures.

Our Upgrade Strategy

We're not live on D365 yet (migration planned for Q1 2025), but we're running current updates in our sandbox. Our strategy:

Stay current during implementation. We're implementing on the latest version rather than an older "stable" version. Yes, this means dealing with newer features that have less community documentation. But it also means we won't face a major version jump immediately after go-live.

Test thoroughly before each update. We've built a regression test suite that we run against each service update. The Regression Suite Automation Tool (RSAT) has been invaluable for this.

Defer non-critical features. Just because a feature exists doesn't mean we use it. We're implementing core functionality first and will evaluate Copilot and other advanced features after go-live stabilization.

Comparison with Competition

I keep tabs on what SAP, Oracle, and others are doing:

SAP S/4HANA: SAP's AI investments are significant, but their food & beverage solutions remain expensive and complex. For mid-market companies, the total cost of ownership still favors D365.

Oracle NetSuite: NetSuite's Wave 1 2024 focused on AI-driven insights and improved supply chain planning. They're catching up in some areas, but their manufacturing/distribution capabilities still lag D365 for complex scenarios.

Infor CloudSuite: Strong in food & beverage manufacturing but less compelling for distribution. If we were a processor/manufacturer, Infor would deserve more consideration.

Bottom Line

D365 2024 Wave 1 is an incremental improvement. No single feature is transformational, but the cumulative effect of better performance, improved UI, and enhanced integration capabilities makes the platform more mature.

For food distribution specifically, we're still waiting for Microsoft to make catch weight and compliance features truly first-class. Until then, we'll continue supplementing with customization and third-party solutions.

Our migration timeline remains on track. Wave 1 gives us confidence that D365 is moving in the right direction, even if it's not yet perfect for our industry.