Microsoft Dynamics Business Central¶
Microsoft Dynamics 365 Business Central (formerly Navision) is the ERP system used by Zwerfkei. It acts as the source of truth for pricing, stock availability, and customer data. See ADR-0004 for the architectural decision.
Consumer focus
Zwerfkei focuses almost exclusively on consumers (B2C). B2B functionality in Business Central (customer-specific pricing, account management) is largely out of scope for the Zwerfkei platform.
LS Central is deployed on top of Business Central as a retail extension. See the LS Central page for details.
Role within Zwerfkei¶
| Data | Direction | Description |
|---|---|---|
| Prices & discounts | ERP → Zwerfkei | Synchronised to the Zwerfkei Backend on a scheduled basis |
| Stock availability | ERP → Zwerfkei | Synchronised; final check at checkout to prevent overselling |
| Customer data | ERP → Zwerfkei | Consumer (B2C) data; B2B account features are largely out of scope |
| Confirmed orders | Zwerfkei → ERP | Pushed to Business Central for stock deduction and financial registration |
API¶
Business Central exposes a REST API (v2.0) as the preferred integration method. The API is built on OData and requires no custom AL code for standard entities.
API endpoints confirmed
TCOG has confirmed which API endpoints are available for integration. Specific LS Central modules will be determined once the blueprint is finalised.
Key concepts¶
- Built-in APIs — extensive set of standard endpoints (items, customers, sales orders, inventory, etc.) available out of the box.
- Custom APIs — can be developed using AL
API pagesandAPI queriesfor Zwerfkei-specific data. - Authentication — OAuth 2.0 (Azure AD) for cloud environments; Basic auth supported for on-premises.
- Versioning — always use the highest available version (
v2.0). v1.0 is deprecated. - Performance — use
$filter,$selectand$expandto limit response size; avoid unbounded queries.
Endpoint structure¶
https://api.businesscentral.dynamics.com/v2.0/{tenantId}/{environment}/api/v2.0/{entity}
Relevant API categories¶
| Category | Purpose |
|---|---|
| Items & inventory | Product data, variants, stock levels |
| Sales orders | Order submission from Zwerfkei to ERP |
| Customers | Customer account data |
| Price lists | Base prices and customer-specific discounts |
Legacy integration (current system)¶
Zwerfkei Old uses a different integration
The current live platform (Zwerfkei Old) integrates with Navision 2018 via SOAP web services (K3 Retail / LS Retail extension), not the Business Central REST API. The pages below document how that legacy integration works — essential context during the migration.
-
Local Werkplek (RDP)
Connect to the remote desktop environment that hosts the Navision Zwerfkei client — required before you can log in.
-
Login Procedure
Step-by-step instructions for logging in to the Navision Zwerfkei client application.
-
Product, Order & Contact Navigation
How to find product (Retail-artikelen), order (Transactiejournaal) and contact (Contacten) data within Navision Zwerfkei.
-
Legacy Integration
How Zwerfkei Old syncs with Navision 2018 via SOAP: inbound buffer polling, outbound queue, two-way data flows.
-
Sync Triggers & Cron
All cron methods, what they do, when they run, and the recommended schedule.
-
K3 Data Models
All K3_ database tables — fields, relationships, and how they map to Navision entities.
Links¶
Business Central API overview Business Central API v2.0 reference LS Central documentation ERP Sync Diagrams NAV endpoint inventory (Olaf — Google Sheets)