The Hummerce integration with Microsoft Dynamics 365 Business Central connects the store to Microsoft's ERP: it syncs items, customers, prices, stock levels and orders, so store staff and the sales department work on the same, up-to-date data without manual re-entry. This is one of the ERP integrations available in the standard Hummerce platform, alongside Microsoft Dynamics NAV (Navision) and Comarch ERP XL.
As of Hummerce 2.33.292 (developed further in 2.34), updated 2026-09-29.
¶ Benefits and use cases
- One source of truth for items and prices - the catalog, B2B and B2C prices, and stock levels update automatically from Business Central, without entering data manually in two systems.
- Orders go straight to the ERP - the sales department and accounting see the store order without re-entering line items, addresses and payments.
- Order statuses stay consistent in both systems - a change of payment, delivery or fulfillment status in Business Central comes back to the store, and vice versa.
- Invoices available right away in the store - the customer and store staff have access to the invoice (including credit notes) and its PDF file from Business Central, without logging into the ERP.
- Configurable products go to the ERP as component line items - with the option to also send a line item for the set itself (Configuration in the cart and order).
- Items - import of the product master data from Business Central: number, description, VAT rate, manufacturer/supplier, sales units, attributes.
- Customers - import of customer and contact data, including the address and delivery address.
- Prices - import of B2C price lists (the store's general price list) and B2B price lists (the customer's individual prices from Business Central).
- Stock levels - import of stock per warehouse, updated on a cycle.
- Orders - export of the store order to Business Central: customer data, line items, delivery, payment, comment.
- Order statuses - two-way sync of order, payment and delivery status.
- Invoices - import of VAT invoices and credit notes from Business Central, together with the PDF file.
- Manufacturers/suppliers and item attributes - import of supplementary product master data.
¶ Direction and frequency of the exchange
- Import of items, customers, prices, stock, invoices, and export of orders run as independent scheduled tasks - each type of data has its own refresh frequency, set during implementation.
- Each type of sync (items, customers, B2B/B2C prices, stock, invoices, order export, statuses) is enabled separately - the integration can be limited to only the scope you need.
- An order marked for sending reaches Business Central automatically; a sending error is visible in the panel next to the order.
- The integration has its own section in the panel, with a preview of recent errors and the most recent messages sent and received.
- Invoices from Business Central are available as a repository in the panel, with the option to download the invoice or credit note PDF file.
- Integration available since Hummerce 2.33.292, developed further in version 2.34 (including the invoice repository in the panel).
- Sending line items of a configurable product (set) to Business Central, with the option to skip the line item for the set itself - since version 2.33 (Configuration in the cart and order).
- An Azure AD application account with access to the Business Central API (OAuth 2.0 authentication).
- An environment and company set up on the Business Central side for the e-commerce exchange.
- VAT rates, units of measure and warehouses set up in Hummerce matching the data from Business Central (code mapping).
- Configuration in the cart and order - for stores with configurable products.
- The integration requires implementation - it doesn't start on its own after an update. Scope of a typical setup:
- registering an application in Azure AD and configuring API access on the Business Central side,
- enabling and configuring the needed sync types (items, customers, prices, stock, orders, statuses, invoices),
- mapping codes (VAT, units of measure, warehouses, delivery and payment methods) between the store and Business Central,
- 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, customers, orders, statuses) in an existing Business Central environment - from 16 h,
- full scope (B2B/B2C prices, invoices with PDF, attributes, multiple warehouses) - from 24 h,
- 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 how much needs adjusting on the Business Central side - we quote it individually.
- What the time depends on:
- the number of enabled sync types and the data volume (number of items, customers, orders),
- the number of warehouses and B2B price lists,
- how well codes (VAT, units of measure, statuses) match between the systems - the more non-standard mappings, the more work,
- support for configurable products and sets - quoted together with Configuration in the cart and order.
- Credit limits and customer payment terms are not part of this integration - available in the integrations with Microsoft Dynamics NAV (Navision) and Comarch ERP XL, implemented individually.
- The integration syncs data on the frequency set for scheduled tasks - this is not a real-time, second-by-second exchange.
- Mapping of order, payment and delivery statuses needs to be adjusted to the status dictionary used in the specific Business Central deployment.
- We do not verify the task for legal compliance (e.g. licenses of submitted materials, GDPR, store terms of service).
- Near-real-time price and stock import (instead of scheduled tasks).
- Extending status mapping with additional states specific to the deployment.
Does the Business Central integration work right after a Hummerce update?
No. This is an individually implemented integration - it requires API access configuration on the Business Central side and data mapping (VAT, units of measure, warehouses, statuses) in the store.
Does the store enforce the customer's credit limit in this integration?
Not in this integration. Credit limits and payment terms are available in the integrations with Microsoft Dynamics NAV (Navision) and Comarch ERP XL, implemented individually.
Are invoices from Business Central visible in the store?
Yes - VAT invoices and credit notes imported from Business Central are available in the panel, together with the PDF file.
Does the integration support configurable products (sets)?
Yes - the product and its components go to Business Central as order line items, with the option to skip the line item for the set itself.
How long does setting up the Business Central integration take?
Basic exchange (items, customers, orders, statuses) in an existing Business Central environment - from 16 h; full scope with B2B/B2C prices and invoices - from 24 h. The time for a specific implementation depends on its scope.
Want to see how the Business Central integration could work in your store? Contact the Hummerce team (in Polish).
- Business Central section in the admin panel - recent errors, most recent messages sent and received.
- Business Central invoice repository - invoice number, order number, document type (VAT invoice / credit note), 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 Business Central):
| Symbol |
Object |
Purpose |
_bcCustomerID |
Customer |
Customer identifier in Business Central |
_bcContactID |
Customer |
Contact identifier in Business Central |
_bcDelivery |
Delivery method |
Shipping agent code in Business Central |
_bcPayment |
Payment method |
Payment method code in Business Central |
_bcWarehouse |
Warehouse |
Location code in Business Central |
_bcUnitOfMeasureCode |
Unit of measure |
Unit code in Business Central |
_bcVatRate |
VAT group |
VAT posting group code in Business Central |
_bcSendStatus |
Order |
Order send status to Business Central |
_bcError |
Order |
Text of the last sending error |