Service · Custom software development

System integration

On paper it sounds simple: data has to travel from one system to another. The catch is that customers, item numbers and units are rarely recorded the same way, and software cannot decide which system is right. That call has to be made by the business.

Send an enquiry See the scope

Leading system

for each data type

Errors

visible straight away

Monitoring

of every run

Double entry

disappears

What the service covers

The technical side can almost always be solved. The real work is reaching internal agreement on which system leads for each kind of data.

Talk it through with us

Mapping the landscape

Which systems are involved, such as the webshop, e-conomic, Business Central, CRM and warehouse, and what is keyed in more than once today.

Data flow

What goes where, how often, and which system owns customers, products, prices and orders.

Field mapping

We link item numbers, customer records, VAT codes and units across the systems.

Development

Through the official APIs, or through a middleware layer we build where no API exists.

Error handling

What happens when a system is down: retries, queues and an alert to a person when a decision is required.

Monitoring

We keep an eye on the runs and notify the owner if an integration stalls.

How we deliver it

A simple integration between two systems takes about two weeks. Linking several systems with shared master data takes six weeks or more.

Data

We review master data at both ends. Duplicates and inconsistencies usually surface and must be cleaned up before we start.

Design

Data flow, rules on which system wins and how conflicts are resolved.

Development

Built and tested in a staging environment with real but pseudonymised data rather than invented samples.

Go-live

A period running alongside the manual process, after which manual entry stops.

Data edited in two systems at once is the biggest source of conflict. A salesperson updates a customer's phone number in the CRM, the bookkeeper does the same in the finance system, and the integration overwrites one with the other. That is why a leading system is appointed for each data type in advance, and the field is locked in the other.

Common questions

Clean it up before integrating, and that is a job for whoever owns the data, not for the developer. Connect two databases full of duplicates and discrepancies and the mess simply spreads to both.

Rarely. Most tasks are well served by hourly runs or a few runs a day, which is also more robust. Real time is needed where decisions are made on the spot, such as checking stock at the moment a customer places an order.

There are workarounds: file exchange, direct table access or automating the user's clicks. Each is inferior to an official API and needs care when the software is upgraded, but the goal is usually reached.

Yes, for example e-invoicing via NemHandel in OIOUBL format and CVR lookups. Integrations handling personal data are documented so you can account for them to Datatilsynet.

Related services

View the whole area

Service End-to-end development Discovery, design, code, testing and ongoing care from one team Service Mobile app development iOS and Android apps published under your own accounts Service Open source development No per-user licence fees and no single-vendor lock-in Service Dedicated development teams Developers and testers in your team without hiring

Let us connect your systems

Tell us which systems your staff currently copy data between by hand. We will estimate the work and tell you what needs tidying first.

Email
office@apply.dk

Coverage
All of Denmark, delivered remotely

I agree that Apply may handle my details as set out in the privacy policy