Production integration · Food distribution
Modernising digital ordering without replacing Microsoft Dynamics NAV
LeXurey delivered a bidirectional production integration for an established Australian food distributor, connecting FreshO to a heavily customised on-premises Microsoft Dynamics NAV environment.
The new FreshO channel was introduced alongside the distributor’s established ordering system, preserving proven warehouse and accounting processes while extending how customers could place orders.
End-to-end production path
FreshO ordering channel
Orders, product data, customer data and negotiated pricing
Secure scheduled integration
Windows Integrated authentication, SFTP, validation and logging
Microsoft Dynamics NAV
Pricing, GST, sales order release, fulfilment and posting
Invoice and status return
Automated outbound delivery with operational diagnostics
Engagement context
A specialist delivery across food distribution, ERP and digital ordering
Compusoft Australia requested the engagement. LeXurey led the integration engineering and production delivery in coordination with Compusoft, FreshO and the customer’s operational teams.
The customer
An established Victorian foodservice distributor
Operating from a purpose-built distribution centre in Melbourne’s south-east, the business serves metropolitan and regional Victoria with coolroom infrastructure designed to handle 20 million litres and a 20-vehicle refrigerated fleet.
The ordering platform
FreshO
FreshO is a Melbourne-founded global order-management platform built for wholesale fresh food. FreshO publicly reports working with 45,000 venues and processing 750,000 orders and almost $400 million in platform volume each month, with customers in Australia, the United Kingdom, the United States, Ireland and New Zealand.
Explore FreshO AustraliaThe requesting partner
Compusoft Australia
Compusoft Australia brought its long-standing NAV and food-industry ERP relationship to the engagement, while LeXurey designed, built, deployed and hardened the production integration.
Delivery timeline
From implementation to controlled production operation
The rollout deliberately separated engineering, technical validation, production proof and live operational validation. The established ordering channel remained available throughout the transition.
- 1
25 May 2026
Implementation underway
The integration foundation, ERP connectors and full customer and product synchronisation workflows were in active development by this date.
- 2
24 June – 15 July
Technical testing and preflight
Customer, product, pricing, order-import and invoice-return paths were tested progressively, followed by live-environment connectivity checks and a formal go-live preflight.
- 3
18 July
Production readiness completed
The production deployment package, operating controls and rollback-conscious runbook were completed and checked before activation.
- 4
19 July
Go-live and end-to-end validation
Scheduled processing entered production. A FreshO order travelled through NAV creation, release, posting and invoice generation, then returned through the live outbound path while the existing ordering channel continued to operate.
- 5
20 July
FreshO-side confirmation
FreshO confirmed the returned invoice imported successfully and that recent product, customer and pricing data were running through the platform.
- 6
22–25 July
Live operational validation (UAT)
Business users tested live orders. Release status, NAV pricing precedence, negotiated pricing, GST treatment and litre/kilogram calculations were refined and all five findings passed regression validation.
This was a controlled go-live followed by live operational validation and hardening—not a high-risk single cutover. Parallel operation kept the established channel available while real production behaviour was validated. No separate formal UAT sign-off is claimed.
Production context
The challenge
NAV already contained the operational rules that mattered: customer-specific pricing, discounts, product tax treatment, order processing and fulfilment. The integration needed to introduce a modern digital channel without duplicating that logic or disrupting the existing route to market.
It also had to operate reliably around a customised legacy ERP, with secure connectivity, scheduled processing, clear diagnostics and a controlled production rollout.
What LeXurey delivered
A controlled order-to-invoice production flow
Automated FreshO-to-NAV processing
Orders are collected from FreshO, validated and created in NAV through scheduled processing. Valid imported orders are automatically released for fulfilment, while invalid orders are logged and directed for operational review.
NAV-controlled pricing and tax
NAV remains the source of truth for system pricing and discounts. Customer-specific negotiated pricing is exported to FreshO, and GST applicability is derived from NAV product posting groups rather than recreated in a separate system.
Warehouse-ready order data
Total litres and kilograms are calculated automatically as orders arrive, making the information available to established warehouse and delivery workflows.
Automated invoice and status return
Once an order progresses through NAV, invoice and status information is returned to FreshO through an automated outbound flow.
Secure production connectivity
The production design combines Windows Integrated authentication for the NAV environment with SFTP-based data exchange with FreshO.
Operational controls
Scheduled product, customer, pricing, order and invoice jobs are supported by logging, invalid-order handling and diagnostic tooling. Deployment was staged with rollback awareness and validation at each production boundary.
Technical foundation
A lightweight integration layer around a customised ERP
The implementation keeps transport, scheduling, file conversion and observability in a dedicated .NET service, while NAV remains responsible for customer, pricing, tax and order-validation rules.
.NET 10 self-contained integration service
Microsoft Dynamics NAV on-premises
NAV OData V4 and SOAP services
FreshO SFTP exchange using CSV and XML
Windows Integrated authentication
Windows Task Scheduler and PowerShell deployment
Structured logging, watermarks and cross-process locks
Idempotent processing, quarantine and failure notifications
Verified in this production delivery
Delivered and validated
- The existing ordering system and the new FreshO channel operate together during transition.
- FreshO orders are created correctly in NAV and automatically released for fulfilment.
- NAV remains authoritative for pricing, discounts and GST applicability.
- Customer-specific negotiated pricing is exported from NAV to FreshO.
- Total litres and kilograms are calculated as orders enter NAV.
- Invoice and status information is returned automatically to FreshO.
- The full path was validated in production: FreshO order, NAV sales order, release, posting, invoice generation and return delivery.
- Monitoring and troubleshooting were hardened around the realities of a customised legacy ERP.
General benefits
What this approach can support
- Reduce repeated manual order entry.
- Preserve established warehouse and accounting processes.
- Maintain consistent pricing and tax logic across channels.
- Introduce digital ordering without an immediate ERP replacement.
- Prepare interfaces and operating practices for future NAV or Business Central modernisation.
The verified outcomes apply to this specific delivery. The broader benefits describe what this integration approach can help organisations achieve; they are not measured savings from this engagement.
Integration strategy
Preserve proven operations while introducing a new channel.
What the production rollout taught us
The most important architectural decision was to keep transport and format conversion in a lightweight integration layer while leaving customer, pricing and order validation inside NAV. That protected years of operational logic and made retries, monitoring and controlled deployment practical.
Live UAT also demonstrated why production integration is more than moving files. Real orders exposed differences in release behaviour, pricing precedence, tax treatment and unit calculations that could only be resolved by working across the ordering platform, ERP customisations and warehouse process.
Preserve the system of record
NAV continued to own the commercial and operational rules instead of duplicating them in a second platform.
Run channels in parallel
Keeping the established ordering route active reduced transition risk and created room for measured live validation.
Design for operations
Schedules, state, logging, quarantine paths and notifications were treated as product features—not deployment afterthoughts.
Future direction
A staged path from NAV to Business Central
The future modernisation direction is to retain the proven FreshO transport, scheduling and monitoring layer while replacing NAV-specific endpoints and customisations with Business Central APIs and AL extensions.
This is the proposed technical direction rather than a published migration date. It protects the value of the current integration while avoiding a second big-bang change.
- 1
Inventory and rationalise the NAV customisations that still carry business value.
- 2
Move integration boundaries to supported Business Central APIs and AL extensions.
- 3
Reconcile orders, pricing, tax and invoice outcomes through parallel validation.
- 4
Cut over in controlled stages once operational equivalence is proven.
NAV and Business Central integration
Connect a new ordering channel to NAV or Business Central
Whether you are keeping NAV in place or preparing for Business Central, LeXurey can assess your interfaces, customisations and operational controls—and design a practical path from external order to fulfilment and invoice return.
This case study covers a production ordering integration with NAV, not a completed ERP migration. For a full platform transition, explore LeXurey’s Dynamics NAV to Business Central migration service in Australia.