Integrations: Connect Your Systems Directly
A direct integration moves data from one system into exactly one other system, with no platform in between. This page lists the connections we offer as direct integrations. Each page shows which data flows, what ready-made plugins and apps already do and where a custom integration starts to make sense.
What does a “direct connection from A to B” mean?
System A is the source, for example your shop or your CRM. System B is the target, such as your ERP or your accounting software. The integration reads from A, translates fields and rules and writes to B. Where needed, information flows back, such as a payment status or a tracking number. There is no hub that collects all your data, and no subscription per transaction.
The code belongs to you. You get a fixed price for the implementation. On request, we take over operation with monitoring and updates as a subscription you can cancel monthly, hosted in Germany and covered by a data processing agreement under the GDPR.
How the connection pages are structured
Data flow
Which objects are transferred, in which direction and at what interval, such as invoices, payments or stock levels.
What already exists
Ready-made apps, plugins, exports and automation services, with source and review date. If one of them is enough, we say so.
Where the standard stops
Typical limits of the combination, backed by vendor documentation and forums.
How we build it
The technology on both sides, error handling, logging and monitoring in operation.
The glossary explains what we mean by an integration. When a ready-made connector is the better choice is covered in the guide Connector or custom integration.
Business Central → DATEV
Postings, customers, vendors and documents from Business Central for your tax advisor in DATEV: what partner apps do, where mapping breaks, how we solve it.
HubSpot → Lexware Office
Won HubSpot deals become invoices in Lexware Office (formerly lexoffice): what apps can do, where the return path is missing and what custom code looks like.
JTL-Wawi → DATEV
JTL-Wawi and DATEV after the end of Rechnungsdatenservice 2.0: what the Buchungsdatenservice covers, where customer accounts fail and when custom code helps.
Pipedrive → Lexware Office
Quote, order confirmation and invoice from Pipedrive deals in Lexware Office (formerly lexoffice): what the partner app does and when custom code helps.
Shopify → DATEV
Orders, Shopify Payments payouts, fees and POS cash to DATEV. Which apps exist, where they stop and how we build the integration.
Shopify → Lexware Office
Shopify orders as invoices in Lexware Office (formerly lexoffice): what the app does, where payments and e-invoicing fall short, what custom code looks like.
Shopware → Business Central
Connect Shopware 6 to Microsoft Dynamics 365 Business Central: which connectors exist, where API and webhooks set limits and how we build it.
Shopware → DATEV
Invoices, credit notes and payments from Shopware 6 to DATEV automatically. What plugins can do, where they stop and what a custom integration looks like.
Shopware → JTL-Wawi
Shopware 6 and JTL-Wawi: what the JTL-Connector syncs, why the sync gets stuck and when custom code makes sense for parts of it.
Shopware → Lexware Office
Shopware invoices as vouchers in Lexware Office (formerly lexoffice): which plugins exist, where backfills and sales channels fall short, how we build it.
Related
Systems
Shop, ERP, accounting, CRM, POS, shipping and legacy systems: the programs we connect directly.
Services
Direct integrations between your systems, from the check to a fixed price to operation.
Connector or custom?
Criteria and a checklist for choosing between a ready-made connector and a custom integration.
