The challenge
Navision was the operational core of VARO, but a growing collection of websites, internal applications and management tools also needed access to its data and processes. Connecting every application directly to the ERP would spread Navision-specific knowledge across the organization and make changes harder to control. VARO needed a dependable integration layer that could coordinate those connections and keep business information consistent.
Role and responsibility
As lead developer, David designed and implemented the links between Navision and the systems around it. His responsibility included understanding what each application needed, translating that requirement into an integration contract and protecting the operational rules already present in the ERP. The work established a technical boundary that other developers and applications could use without reproducing the same connection logic.
A shared integration layer
VB.NET provided the foundation for services that exchanged information with Navision. Microsoft SQL Server supported the relational data handling required around those exchanges. Together they formed an intermediary between the ERP and the websites or management tools that depended on product, customer and operational information.
This structure separated the pace of web and internal-tool development from the implementation details of Navision. Applications could request or supply the information they needed through one controlled route.
Repeatable data exchange
The integration work focused on predictable transformations and flows rather than one-off data copies. Information moving out of Navision had to remain meaningful to the receiving application, while updates moving back had to respect the ERP’s expectations. Centralizing that translation reduced the chance that separate applications would interpret the same business data differently.
SQL also provided a practical place to stage or structure information when the shape used by an external system did not match the ERP directly.
Operational integrity
Because Navision remained central to day-to-day operations, integration failures could affect several downstream workflows. The layer therefore had to preserve clear ownership of data and avoid uncontrolled duplicate processing. Keeping connection logic together made issues easier to trace and allowed changes to be assessed against all participating systems instead of only one consumer.
The design supported automation while retaining Navision as the authoritative operational system.
Result
VARO gained a reusable route between its ERP and a growing digital landscape. Websites, internal tools and external systems could participate in coordinated workflows without each building a separate Navision connection. The VB.NET and SQL integration layer reduced duplicated handling, strengthened data consistency and created the foundation on which later customer-facing and internal platforms could be connected.