The Hummerce integration with Microsoft Dynamics NAV (Navision) connects the store to Microsoft's ERP: it syncs items, stock levels, B2B customers, orders, statuses and invoices, without manually re-entering data between systems. This is one of the ERP integrations available in the standard Hummerce platform, alongside Microsoft Dynamics 365 Business Central and Comarch ERP XL - with credit limits and customer payment terms as an extension implemented individually.
Last updated: 2026-09-29.
¶ Benefits and use cases
- Catalog and stock levels consistent with the ERP - items, units of measure and availability update automatically from Navision.
- B2B customer base shared with the ERP - business customer data, including payment terms and prepayment, comes from Navision.
- Individual customer price lists - B2B prices imported from the customer's price list in Navision.
- Orders and statuses reach the ERP and come back to the store - the sales department works in Navision, the customer sees the current status in the store.
- Invoices available in the store - the invoice and its PDF file from Navision, without logging into the ERP.
- Credit limits and payment terms visible to the customer (individual implementation) - the store keeps track of the business customer's obligations instead of relying solely on manual checks.
- Items - import of the product master data: description, base unit, minimum purchase quantity, manufacturer/supplier assignment.
- Stock levels - import of item availability, refreshed more frequently than the other data.
- B2B customers - import of customer and contact data, including payment terms, the warehouse assigned to the customer, and customer block information.
- Customer price lists - import of individual B2B prices assigned to the customer in Navision.
- Orders - export of the store order to Navision: customer data, delivery address, line items, delivery, payment.
- Order statuses - import and export of order, payment and delivery status (two-way).
- Invoices - import of invoices and credit notes from Navision, together with the PDF file.
Hummerce has two variants of the Navision integration in the code:
- Web service integration (Web Service/SOAP) - the current variant, described in this section; communication over the SOAP protocol.
- Older integration (XML/FTP) - an earlier file exchange variant, kept for existing deployments.
The variant is chosen during implementation, depending on which service the customer's Navision system exposes.
- The integration has its own section in the panel, with a preview of recent errors and the most recent messages sent and received.
- An order shows its Navision send status and the text of the last error, if sending failed, in the panel.
¶ Credit limits and payment terms (individual implementation)
Credit limits and payment terms are not part of the standard integration - they are implemented individually on top of the Navision integration (or Comarch ERP XL). How it works:
- the business customer sees their credit limit and payment term in their account,
- the store always accepts the order, regardless of the limit's state,
- once the limit is exceeded, the customer gets a message that the order will be fulfilled once their obligations to the store are settled.
The Navision integration has been available in Hummerce for many versions.
- Access to the Navision web service - the service address and an account with read/write permissions.
- VAT rates, units of measure and warehouses set up in Hummerce matching the data from Navision (code mapping).
- Credit limits and payment terms - additional implementation work beyond the standard integration scope.
- The integration requires implementation - it doesn't start on its own after an update. Scope of a typical setup:
- configuring access to the Navision web service (address, account, individual service paths),
- enabling and configuring the needed sync types (items, stock, customers, prices, orders, statuses, invoices),
- mapping codes (VAT, units of measure, warehouses, delivery and payment methods) between the store and Navision,
- full-cycle testing: importing an item and a customer, placing a test order, checking the status and the invoice.
- Minimum estimated time:
- basic exchange (items, stock, customers, orders, statuses) in an existing Navision environment - from 16 h,
- full scope (B2B price lists, invoices with PDF) - from 24 h,
- credit limits and payment terms (individual implementation, beyond the standard) - quoted separately, depending on scope and the ERP system,
- we always add: analysis - +1 h, testing - +2 h, production deployment - +1 h.
- The time for a specific implementation depends on its scope and on which Navision version/variant the customer supports - we quote it individually.
- What the time depends on:
- the integration variant (web service vs. the older XML/FTP integration),
- the number of enabled sync types and the data volume,
- how well codes (VAT, units of measure, statuses) match between the systems,
- whether the implementation covers credit limits and payment terms.
- Credit limits and payment terms are not part of the standard integration - they require individual implementation.
- The integration syncs data on the frequency set for scheduled tasks, not in real time, second by second.
- Mapping of order, payment and delivery statuses needs to be adjusted to the status dictionary used in the specific Navision deployment.
- The two integration variants (web service and the older XML/FTP) are not interchangeable without extra work - the choice depends on what Navision exposes for the customer.
- We do not verify the task for legal compliance (e.g. licenses of submitted materials, GDPR, store terms of service).
- Unifying the two integration variants (web service and the older XML/FTP) into a single module.
- Near-real-time price and stock import (instead of scheduled tasks).
Does the Navision integration work right after a Hummerce update?
No. This is an individually implemented integration - it requires configuring access to the Navision web service and mapping data (VAT, units of measure, warehouses, statuses) in the store.
Does the store enforce a business customer's credit limit?
Yes, but as an individually implemented extension, not part of the standard integration: the customer sees the limit and payment term, the order is always accepted, and once the limit is exceeded, the customer gets a message that the order will be fulfilled once their obligations are settled.
Are invoices from Navision visible in the store?
Yes - invoices imported from Navision are available in the panel, together with the PDF file.
Are there two different ways to integrate with Navision?
Yes - the current integration through web services (SOAP), and an older integration based on XML/FTP file exchange, kept for existing deployments.
How long does setting up the Navision integration take?
Basic exchange (items, stock, customers, orders, statuses) in an existing Navision environment - from 16 h; full scope with B2B price lists and invoices - from 24 h. Credit limits and payment terms are quoted separately, as an individual extension.
Want to see how the Navision integration could work in your store? Contact the Hummerce team (in Polish).
- Navision section in the admin panel - recent errors, most recent messages sent and received.
- Order send status and error text - visible next to the order in the panel.
- Navision invoice repository - invoice number, order number, customer contact, document type, net/gross amounts, PDF file.
¶ REST API and MCP
The integration works through scheduled tasks and the admin panel.
Properties set on store objects by the integration (mapped from Navision):
| Symbol |
Object |
Purpose |
navCustomerID |
Customer |
Customer identifier in Navision |
navContactID |
Customer |
Contact identifier in Navision |
paymentSymbol |
Customer |
Payment method symbol |
warehouseSymbol |
Customer |
Symbol of the warehouse assigned to the customer |
blocked |
Customer |
Whether the customer is blocked in Navision |
Payment terms (paymentTerms) |
Customer |
Customer's payment terms from Navision |
Prepayment in days (prepayment) |
Customer |
Number of days of prepayment required from the customer |
_navisionSendStatus |
Order |
Order send status to Navision |
_navisionError |
Order |
Text of the last sending error |
_orderNavNo |
Order |
Order number assigned in Navision |