Have an integration built: directly from system A to system B

We program direct integrations between two systems, such as shop and accounting or CRM and invoicing software. After a free 30-minute check you receive a fixed-price quote. The code is yours, and operation runs on our servers in Germany or, if you prefer, on yours. If a ready-made connector is enough, we tell you beforehand.

How you know an integration is missing

Most inquiries begin with a process that costs time every day. Orders from the shop are typed by hand into the ERP. At the end of the month someone exports a CSV file, cleans it up in Excel and sends it to the tax advisor. From a won deal in the CRM, the office writes the invoice all over again.

Such processes work as long as few transactions occur and the same person always remembers them. They become expensive as volume grows. Then typical errors appear: transposed digits in amounts, forgotten credit notes, customers created twice, stock levels in the shop that are no longer correct. Each of these errors usually surfaces late, often at the tax advisor or with the customer.

An integration transfers this data automatically and by fixed rules. It works the same way every day, logs what it did and reports when something does not fit.

What we build and what we do not

We build a direct connection from system A to system B. The integration reads data from the source system, converts it to the format of the target system and writes it there. If needed, information also flows back, for example the payment status from accounting to the shop. This is called a bidirectional integration.

We do not build a platform through which you would have to manage all your systems in future, and we do not build a clone of an automation service. There is no extra tool to learn and no billing per transaction. You get a small, clearly defined program that does one job.

The source code is yours. You receive it with documentation and can run it yourself at any time or have others develop it further. This way you avoid vendor lock-in.

How an integration works technically

Which approach fits depends on what the two systems offer. We check this in the integration check and choose the most robust approach.

• API

  Most current programs have an API. It lets you read and write data selectively, with login and fixed rules.

• Webhook

  A webhook reports an event immediately, such as a new order. The integration then does not have to keep asking.

• File and SFTP

  If a system has no API, we exchange files, for example CSV or XML, via a secured folder or SFTP.

• Database

  For local programs, by agreement we read directly from the database, read-only if writing is not permitted.

The core is the data mapping: the rule on which field goes where. An order with tax rate, shipping costs and discount becomes, for example, a posting record with account, offsetting account and tax code. We define these rules with you and, for accounting, with your tax advisor.

1. Order becomes invoice or posting record on receipt
2. Credit note becomes reversal entry on receipt
3. Payment status is reconciled daily
4. Customer is created or matched as a debtor account (Debitor) as needed

Every integration includes three things that you do not see but that decide its quality:

• Error handling

  If a system is unreachable, the integration tries again later. Unique identifiers prevent a record from arriving twice in the process.

• Log

  Every transaction is recorded: what was transferred, when and with what result. This makes every posting traceable.

• Monitoring

  If something fails, you and we get a message before anyone notices in day-to-day business.

Ready-made connector, iPaaS or custom integration?

For many common combinations there are ready-made apps and plugins. There are also automation services, also called iPaaS, with which you can click together workflows without programming. Both are often the right choice. A custom integration is worthwhile mainly when the standard option does not fit your process.

Zapier, for instance, bills by tasks per month. With few transactions that is inexpensive; with many orders per day the math can look different. A detailed comparison is in the guide connector or custom integration and under Zapier alternative.

Our services at a glance

• DATEV integration

  Posting batches (Buchungsstapel) and documents from shop, ERP or industry software for your tax advisor.

• Shop-ERP connection

  Products, stock levels, prices and orders between shop and ERP.

• CRM connection

  From the won deal to the invoice, without a second entry.

• Connection without an API

  Connect legacy systems, CSV exports and local databases automatically.

• E-invoicing

  Generate XRechnung and ZUGFeRD from your existing ERP.

• Operation and monitoring

  Monitoring, alerts and notice when an API changes.

Specific combinations such as Shopware and DATEV, Shopware and JTL-Wawi or HubSpot and Lexware Office are in the overview of integrations.

Who we build integrations for

We work for small and medium-sized businesses in Germany, Austria and Switzerland. Typical are online retailers with shop, ERP and tax advisor, wholesalers with customer-specific prices, trade businesses with industry software and service providers who manage orders in a CRM and write invoices in another program. What they all share: two systems that work well individually but do not talk to each other. Examples by industry are under e-commerce, wholesale, skilled trades and logistics. We describe the programs involved individually in the overview of systems.

Process and pricing

A project runs in four steps. In the free integration check (30 minutes) we clarify which data should flow in which direction and what access the systems offer. Within 3 working days you receive a fixed-price quote with a precisely described scope. Implementation usually takes 2 to 4 weeks, including a test with real data in a test environment. Afterwards, if you want, we take over operation.

A simple connection between two systems starts at €1,900 net, projects with several systems at €4,900 net. Operation costs from €149 a month and can be cancelled monthly. What pushes the price up is explained on the page process and pricing and in the guide What does an integration cost?.

Data protection and hosting

By default your integration runs on our servers in Germany, or on your own server if you prefer. For operation on our servers we conclude a data processing agreement (AVV) under the GDPR with you. Credentials for your systems are stored encrypted and set up only with the permissions the integration really needs. Personal data is kept only as long as needed for the transfer and for traceability.

Updated: 10/21/2026