Skip to content
SAP, DATEV and Dynamics experts

Integration services that unify your system landscape

From SAP connectivity through DATEV accounting exports to custom API development: our service portfolio covers the entire integration needs of your online shop.

Integration from 1,490 € net SAP, JTL-Wawi, DATEV & Dynamics 365 Fixed price after system analysis

What Our Clients Rely On

since 2013
integration experience
50+
completed integration projects
(project experience)
97%
contract renewal rate
(project experience)
8-12 wks
typical ERP-shop connection
(project experience)

Setup fixed prices · net plus VAT

from 1,490 € setup fixed price net
  • Fixed setup price per integration instead of an open estimate
  • SAP, JTL-Wawi, Dynamics 365, DATEV and Lexware connected
  • Products, stock, prices and orders synchronized bidirectionally
  • SLA operations and monitoring well beyond go-live

DATEV and payment connection from 1,490 €, JTL-Wawi and Lexware from 4,900 €, Microsoft Dynamics 365 from 6,900 €, SAP Business One from 9,900 € and marketplace connection from 2,480 € per channel. API and middleware development 990 € per project day (119 € per hour net). Ongoing connector and tool licenses are shown separately. The project day is a package price for a reserved working day and therefore deliberately not a multiple of the hourly rate — the rationale is on the pricing overview.

In an online shop that needs to be connected with ERP, accounting, PIM and warehouse management, the quality of the interfaces determines the efficiency of the entire business operation. We help companies transform their existing system landscape into seamless data flows. We combine deep technical know-how with an understanding of the business requirements for data consistency, availability and scalability.

Our service portfolio at a glance

Every integration project brings unique requirements: different ERP systems, different data volumes, different synchronization frequencies, different compliance requirements. We therefore group our work into six core disciplines that interlock along the data flow, from connecting the source system to the target format in the shop. From the initial system analysis through technical implementation to long-term operations, we accompany your project through all phases.

Layered integration architecture
Six core disciplines as one continuous layer
From system analysis to SLA operations, every layer feeds the next — documented, monitored and at a fixed price. Illustrative representation — values are examples.
S4Online shopCatalog, orders, customer accounts, checkoutShopware
S3API layerREST and GraphQL · OAuth 2.0 · rate limiting · versioningREST
S2Middleware & data mappingMessage queue · transformation · dead-letter · routing0 losses
S1ERP, PIM & accountingSAP · JTL-Wawi · Dynamics 365 · DATEV · Lexwarefrom 1,490 €
MMonitoring & SLA operationsReal-time metrics · alerts · escalation · quarterly reviews97%
Entry DATEV connectionfrom 1,490 €setup fixed price net
ERP connectorfrom 4,900 €JTL-Wawi, Dynamics 365, SAP
Sync directionbidirectionalShop ⇄ ERP, PIM, DATEV
Dead-letter & retryno data loss on outage
Fixed priceIntegration from 1,490 € net
The six core disciplines as one continuous architecture layer: from shop through API and middleware down to ERP, DATEV and monitoring — documented and SLA-backed. Setup fixed prices from 1,490 € net.

ERP Integration

Bidirectional connectivity with SAP Business One, S/4HANA, Microsoft Dynamics 365 Business Central and industry-specific ERP systems via REST APIs, OData and RFC. Learn more

DATEV Integration

Automated transfer of invoices, credit notes and payment data to DATEV Unternehmen Online. GoBD-compliant archiving and configurable account assignment rules. Learn more

API Development

Design and implementation of REST and GraphQL APIs with authentication, versioning, rate limiting and comprehensive documentation for all stakeholders. Learn more

Middleware Architecture

Central integration layers with message queues, event-driven architecture and dead-letter handling for reliable data flows even during system outages. Learn more

Data Mapping and Transformation

Systematic translation of data models between ERP, PIM, shop and accounting. Documented mapping matrices, automated validation and conflict resolution strategies.

Operations and Monitoring

SLA-based operations packages with real-time monitoring, automated alerts, error analysis and quarterly optimization reviews for all running interfaces.

Each service in detail

Our six core services interlock: ERP integration defines the data flows, API development ensures technical communication, middleware orchestrates the processes, data mapping bridges the different data models, the DATEV connector closes the financial cycle, and ongoing operations keep everything running.

ERP Integration: The backbone of your shop connectivity

ERP integration is the most business-critical interface in most projects. Product master data, prices, stock and orders flow bidirectionally between inventory management and shop. Before we implement, we clarify data ownership per entity: which system is authoritative for products, where do customer prices originate, where are orders approved?

ERP · SAP, JTL-Wawi
Middleware
Shopware shop
Products, prices and stock: source is the ERP
Orders and customer accounts: source is the shop
Data ownership per entity clarified before the build

API Development: Interfaces tailored to your needs

Not every system provides the API your project needs. Our API development closes this gap with REST APIs for standardized operations and GraphQL for flexible queries. Versioning allows parallel operation during migration, webhooks replace polling and reduce latency.

  • OAuth 2.0 or API key authentication
  • Rate limiting and OpenAPI documentation
  • Cursor pagination for large datasets
GET /v2/products
OAuth 2.0 · bearer tokenRate limiting · 1,000 per minuteVersioning · v1 and v2 parallelCursor paginationWebhooks instead of pollingOpenAPI documentation

Middleware and data mapping: the interplay

In landscapes with three or more systems, a dedicated middleware layer orchestrates the data flows over message queues (such as RabbitMQ). When the ERP updates a product, it publishes a message; the middleware transforms the data and distributes it to shop, PIM and warehouse. If a target system goes down, messages stay in the queue and are delivered after recovery. Dead-letter queues catch undeliverable messages for manual analysis. Data mapping translates each data model systematically: an ERP gross-net logic with line discounts becomes a final price per product in the shop, documented per mapping matrix and secured with regression tests.

How our services interlock

An integration project is not a linear process. In practice, our teams work in parallel: while the ERP specialists analyze the data structures in the source system, the API team is already defining the endpoints. The mapping team documents the transformation rules, and the middleware team configures the message queues. Because API contracts, data models and queue topology take shape together from the outset, we avoid later architectural breaks and gain valuable time compared to a purely sequential approach.

In joint interface reviews with your system owners and subject matter experts, we clarify data ownership, open mapping questions and technical dependencies before they turn into blockers. The result is an integration architecture where APIs, middleware, data mapping and monitoring work seamlessly together. And after go-live, our operations team ensures everything continues running stably with defined SLAs.

Six disciplines that interlock as one architecture

Our services form a continuous layer between your systems: API development establishes communication, middleware orchestrates the processes, data mapping bridges different data models and monitoring keeps everything in view. The result is an integration that carries every single interface.

  • API layer for shop, ERP, PIM and accounting
  • Middleware with message queues and dead-letter handling
  • Documented data mapping per entity and monitoring per interface
API layer
REST and GraphQL for shop, ERP, PIM and accounting
Auth and versioning
Middleware core
Message queue, transformation and dead-letter handling
no data loss on outage
Monitoring & SLA
Real-time metrics, alerts and quarterly reviews
monitored per interface

Typical deliverables of an integration project

To help you estimate what an integration project concretely includes, we have compiled typical deliverables. The exact composition varies depending on system landscape and requirements.

  • System analysis with data flow diagram and interface specification
  • Mapping matrix for all entities (products, prices, stock, customers, orders)
  • REST/GraphQL APIs with OpenAPI documentation and Postman collections
  • Middleware configuration with message queues, routing and dead-letter handling
  • ERP connector for bidirectional data synchronization
  • DATEV export with automatic account assignment and GoBD archiving
  • Monitoring dashboard with real-time metrics and configurable alerts
  • Integration and load tests with documented test results
  • Operations handbook with runbooks for typical error scenarios
  • SLA-based operations contract with defined response times

Supported systems and technologies

Our integration experience spans a broad range of ERP systems, shop platforms and third-party systems. The following overview shows the systems we work with regularly. If your system is not listed, contact us: virtually any system can be connected via standardized APIs.

ERP Systems

SAP Business One, SAP S/4HANA, Microsoft Dynamics 365 Business Central, Sage, SelectLine, orgaMAX and industry-specific ERP systems. Connectivity via native APIs, OData, RFC or custom connectors.

Shop Platforms

Shopware 5 and 6 as well as all common open-source and proprietary shop platforms. Any shop system with a REST or GraphQL API can be integrated into our architecture as a source or target system.

PIM Systems

Common Product Information Management systems with REST or SOAP interfaces. Product descriptions, technical data, media and category trees are reliably synchronized to your shop.

Accounting and Finance

DATEV Unternehmen Online, DATEV Rechnungswesen, Lexware and other accounting software. Automated document transfer with configurable account assignment and GoBD-compliant archiving.

CRM Systems

Microsoft Dynamics CRM and other industry-specific CRM systems. Customer master data, contact history and sales territories are bidirectionally synchronized with the shop.

Logistics and Shipping

Warehouse management systems, shipping carrier APIs, track-and-trace platforms. Stock synchronization, shipping label generation and shipment tracking directly from the shop.

Why specialized integration expertise makes the difference

Many shop agencies offer integration work as an add-on service. We have made it our core business. The difference shows in the depth of analysis, the robustness of architecture and the quality of ongoing operations. We know the quirks of common ERP systems firsthand: the specifics of the SAP RFC interface, the limitations of Dynamics OData endpoints, the format requirements of the DATEV interface specification. This detailed knowledge makes the difference between an interface that works in testing and one that works reliably under production load with real data volumes and edge cases.

Our experience from 50+ integration projects means we know typical pitfalls and avoid them from project start. We know which data types can cause problems when transforming between SAP and Shopware. We know the performance bottlenecks when synchronizing large price lists. And we have proven monitoring strategies that detect problems before they become business-relevant. Contact us for a non-binding initial assessment of your integration project.

Security and compliance in every data flow

Integration data frequently contains sensitive business information: customer-specific prices, order volumes, payment information and personal data. Protecting this data is our highest priority. All data transfers are encrypted via TLS. API access is authenticated via OAuth 2.0 and protected by rate limiting. IP whitelisting restricts access to defined servers. And all transactions are logged for audit purposes, so you can trace which data was transferred between which systems at any time.

For DATEV integration, we fully meet GoBD requirements: immutability of transferred documents, complete traceability of all processing steps and completeness of the document chain from order to payment. The procedural documentation describing how data travels from shop to accounting is a standard component of every DATEV integration project and mandatory for tax audits.

Long-term operations: Your integration in experienced hands

An integration project does not end with go-live. ERP updates, new shop versions and changing business requirements demand continuous maintenance of interfaces. Our operations packages include real-time monitoring of all data flows with configurable alerts and escalation chains, regular health checks of interfaces and their performance, compatibility checks before system updates with proactive adaptation, quarterly optimization reviews to identify improvement potential, and extension with additional data flows or systems.

With a contract renewal rate of 97 percent (project experience), it is clear that our clients value this long-term support. We see ourselves not as a service provider that sets up an interface and moves on, but as a long-term technology partner that maintains and evolves your integration architecture over the years. Learn more about our project approach on the References page. Contact us for a non-binding initial assessment of your integration project.

Integration as a side activity or as a core business

AspectIntegration as a side activityOur specialized approach
System knowledgeSuperficial standard connectorsSAP RFC, Dynamics OData and DATEV format in depth
Error handlingWorks in testing, breaks under loadDead-letter handling, retry logic, edge-case tests
ArchitecturePoint-to-point, hard to maintainDecoupled middleware, documented mapping
After go-liveProject ends with handoverSLA operations, monitoring and quarterly reviews
UpdatesReactive on outageCompatibility check before every system update

The project workflow: From analysis to ongoing operations

  1. 1

    System analysis and blueprint

    We capture the system landscape, data flows and pain points in detail. The result: an integration blueprint with all interfaces, data formats and priorities.

  2. 2

    Mapping and API contracts

    For each entity we create a mapping matrix, in parallel we define API endpoints and queue topology so no architectural breaks occur.

  3. 3

    Iterative sprints

    Implementation proceeds in two-week sprints. After each sprint you test working integrations on the staging environment.

  4. 4

    Integration and load testing

    Before go-live we test edge cases: what happens with 10,000 simultaneous product updates or a 30-minute ERP outage?

  5. 5

    Go-live and SLA operations

    Only after all test cases pass do we go live and take over operations with defined SLAs, proactive monitoring and quarterly reviews.

Integration projects require particularly careful methodology because they work at the intersection of multiple systems, teams and responsibilities. The five phases above keep technical complexity manageable, identify risks early and ensure the result meets business requirements.

What your integration costs

A budget can hardly be planned properly with an open effort range. For the most common connections we therefore state clear setup fixed prices. The final price depends on your system landscape and the critical data flows and becomes binding after a free system analysis — with no hidden items. Ongoing licenses for connectors, middleware and accounting tools are shown transparently and separately from the service fixed price.

Setup fixed prices per integration type

All prices net plus VAT. Every connection starts with a free system analysis and a binding setup fixed price. Scope and system landscape determine the right path.

Accounting & Payment

Accounting and payments posted cleanly.

from 1,490 € setup fixed price net
  • DATEV connection from 1,490 € net (Fibu export, GoBD)
  • Payment connection from 1,490 € net (payment reconciliation)
  • Lexware and ERP connection from 4,900 € net
  • Revenue account mapping and audit-proof document archive
  • Handover to your tax advisor without rework
Request analysis
Most common

ERP Integration

Your authoritative system bidirectionally at the shop.

from 4,900 € setup fixed price net
  • JTL-Wawi connection from 4,900 € net
  • Microsoft Dynamics 365 Business Central from 6,900 € net
  • SAP Business One integration from 9,900 € net
  • Products, stock, prices and orders in sync
  • Connector license separate from approx. 99 € per month
Request analysis

Channels & Development

Marketplaces and custom interfaces.

from 2,480 € per channel net
  • Marketplace connection per channel from 2,480 € net
  • Amazon, eBay, OTTO Market and Kaufland as channels
  • API and middleware development 990 € net per project day
  • Hourly rate for extensions 119 € per hour net
  • Custom REST and GraphQL APIs on a time basis
Request analysis

Setup fixed prices after a free system analysis; ongoing third-party licenses (connector rental, DATEV tools, marketplace plugins from approx. 30 € net per month) are shown transparently and separately. All prices net, plus VAT. You receive a binding offer after the free system analysis.

Which service delivers the greatest leverage for your business?

Tell us which systems you run. We recommend the disciplines that unlock the greatest business value first.

Frequently asked questions about our services

Our technical approach is documented in detail on the blog: REST API or Middleware explains the architecture decision at project start, Error Handling in Interfaces covers retry, dead-letter queue and monitoring, and Building Test Environments for ERP Interfaces shows why a clean sandbox lowers project risk.

Three ways to introduce an integration project

The sequence determines risk and how much budget is committed. A factual comparison of the common approaches.

One date

Switch everything at once

  • Only one switchover date, after which the target state is reached
  • All data flows are tested together
  • The first visible benefit only arrives after months
  • Root causes are hard to isolate because much is new at the same time
  • The entire budget is committed before anything runs in production
Fast start

Single connections without a target picture

  • First results within a few weeks
  • Low entry investment per connection
  • Without a target architecture, direct links emerge that get in the way later
  • The same master data ends up mapped differently several times
  • The second and third connection tend to get more expensive, not cheaper
Our approach

Expansion stages after a system analysis

  • The target architecture is set, delivery happens in delimited stages
  • Every stage has its own fixed price and a visible benefit
  • Master data mapping is created once and reused
  • Setup fixed price from 1,490 € net per connection after a free analysis
  • The analysis takes time before the first connection starts

How integration projects typically unfold

First connection
Starting point
Articles are maintained separately in shop and ERP; changes reach the shop late or not at all.
Measure
Inventory system integration with clearly defined data ownership per field.
Result
Article maintenance happens only in the leading system, and the shop picks up the state automatically.
Expansion stage
Starting point
The first connection runs, but special prices and customer approvals are still maintained in lists.
Measure
Extension with price and customer group logic from the ERP, billed by effort at the project-day price.
Result
B2B customers see their agreed conditions in the shop without sales having to maintain them.
Operation
Starting point
After go-live, a missing transfer is only noticed when a customer gets in touch.
Measure
Monitoring of data flows with alerting on aborts and retry runs.
Result
Faults are detected before they show up in daily business, and open cases are documented traceably.

Illustrative scenarios from typical project histories (project experience), anonymized and without client details.

If the B2B shop itself is being built alongside the interface, you will find the scope at b2b-commerce-agentur.de. For ongoing operation after go-live, shop-wartung.de is the right address.

By submitting you consent to the processing of your details to handle this request. Details in our privacy policy.