Pepper · FreshO · Microsoft Dynamics
FreshO ordering. Built around your NAV operation.
Connect FreshO with Microsoft Dynamics NAV / Navision while keeping pricing, tax, fulfilment and invoicing rules in your ERP.
LeXurey has delivered a production FreshO–NAV integration for an Australian food distributor, including customer-specific pricing, order import and invoice/status return.
The connection, at a glance
FreshO
Customer ordering channel
LeXurey integration
Mapping, validation & transfer monitoring
Dynamics NAV / Navision
Pricing, tax, fulfilment & invoicing
Business Central API options are assessed separately. Sync frequency and supported fields are agreed during scoping.
How the connection is scoped
Our published FreshO delivery used NAV OData V4 and SOAP services, with CSV/XML files exchanged through SFTP on the FreshO side. A new implementation is scoped against your current NAV and FreshO requirements.
Read the production case study for the delivered architecture, controls and operational outcomes. Its results describe that engagement, rather than a guaranteed outcome for every environment.
The data that keeps ordering working
Each flow is confirmed during scoping. The ERP remains the agreed source for commercial and fulfilment rules.
01
Products & availability
Map item codes, units of measure and availability rules, including stock reserved for other orders.
02
Customer-specific prices
Agree customer and delivery-account mappings, price lists, effective dates, discounts and tax treatment.
03
Sales orders into NAV
Validate order references, order and delivery dates, quantities and units before creating or releasing sales orders.
04
Invoices & order status
Scope invoice and status return with duplicate checks, transfer logs, error alerts and a clear retry process.
OData, APIs or files?
Choose the connection around your ERP version and the ordering platform’s supported interfaces.
NAV OData / web services
Where supported and published in your NAV environment, OData services expose ERP data. JSON is a data format an OData service can return; OData is not a file type.
Business Central APIs
For new Business Central integrations, assess Microsoft’s standard APIs or a custom API extension. Authentication, permissions and available fields are part of the design.
JSON / CSV / XML files
Use an agreed schema and transfer method when file exchange fits the platform. Our FreshO case study uses CSV/XML over SFTP. JSON files are an option only where the receiving interface accepts them.
Technical references: Microsoft OData / JSON · Business Central APIs
Implementation pricing
Request a scoped quote
LeXurey confirms your ERP version, data flows and business rules before quoting. The written proposal sets out the implementation fee, inclusions, exclusions and GST treatment.
- Scope covers agreed mappings, integration development, testing, go-live and handover.
- Monitoring, ongoing support, hosting and later changes are itemised separately where required.
- Pepper/FreshO subscriptions, Microsoft licences and third-party charges are separate from LeXurey services.
Pepper publishes custom-quote pricing. Request current FreshO subscription pricing directly from FreshO. Pepper pricing
Discuss FreshO integrationSee an example JSON mapping
A fictional example brings together item availability, customer-specific prices and an order with order and delivery dates. Use it to discuss the fields your integration needs.
{
"sampleOnly": true,
"orderDate": "2026-09-22",
"requestedDeliveryDate": "2026-09-24",
"currency": "AUD",
"unitPriceExTax": 25.00
}Illustrative LeXurey mapping only. The sample price is a fictional product price, not an implementation fee. This is not an official Pepper, FreshO or Microsoft payload, and it does not connect to a live system.
Download sample JSONExtend the flow into your warehouse
Explore Tasklet Mobile WMS for barcode-guided receiving, picking, movements and counts around NAV / Business Central.
See the FreshO–NAV production delivery
Architecture, pricing controls, order import and invoice return in practice.