Skip to content
GDPR-compliant B2B shops

Interfaces and Integrations for Your B2B Shop

We connect Shopware bidirectionally with ERP, CRM, PIM and accounting — SAP Business One, S/4HANA, Dynamics 365 or DATEV. Products, prices, stock and orders flow automatically and in near real time, without manual double entry.

Request a Free Integration Analysis Call: +49 5123 9579000
ERP connection from 4,900 € net SAP, DATEV and Dynamics 365 Real-Time Synchronization

2013

e-commerce experience since

bidirectional

data synchronization

< 60 s

change visible in shop

50+

B2B integration projects

Fixed prices · net plus VAT

from 4,900 € per standard connection
  • Fixed price per standard connector instead of an open estimate
  • SAP Business One, S/4HANA, Dynamics 365 and DATEV connected
  • Bidirectional sync of products, prices, stock and orders
  • Monitoring of your interfaces well beyond go-live
Request a Free Integration Analysis See maintenance & monitoring

Custom ERP integration with its own transformation layer from 12,900 €, OCI punchout from 4,900 € and cXML from 6,900 € per connection. Support on a time basis 119 € per hour (day rate 940 €), ongoing interface monitoring from 249 € per month. All prices net plus VAT.

In many B2B organizations, data on products, customers, pricing and inventory lives in multiple systems simultaneously: in the ERP for resource planning, in the PIM for product information, in the CRM for customer relationships and in the online shop for digital sales. Without clean interfaces, inconsistencies emerge that lead to incorrect shop pricing, faulty stock level displays and manual rework. As a specialized B2B e-commerce agency, we build integration solutions that reliably connect these systems and spare your teams the burden of maintaining data in multiple places.

Data Flow from Source System into the Shopware Shop

Data flow through the integration layer
From raw record to usable shop information
Products, prices and stock from ERP, PIM and CRM run through a central layer — mapped, validated and idempotent in the Shopware shop. Illustrative representation — values are examples.
Raw data from ERP, PIM & CRM — products, prices, stock, orders6 sources
Field mapping, unit and currency conversion in the transformation layer1 layer
Validated, idempotent and in sync in the Shopware shop< 60 s
Standard connectorfrom 4,900 €SAP, DATEV, Dynamics 365
Sync directionbidirectionalShop ⇄ ERP, PIM, CRM
Data losses0via retry queue
Queue & retryno data loss on outage
Fixed priceERP connection from 4,900 € net
The journey of a record through the integration layer: from the source systems through mapping and validation bidirectionally into the Shopware shop. Fixed price per standard connection from 4,900 € net.

Why Seamless Integration Is Essential in B2B Commerce

Data Quality Determines Every Order Completion

In B2B commerce, data quality and process speed have a direct impact on revenue. If a key account does not see their negotiated volume pricing in the shop, they will not order. If stock levels in the shop do not match the warehouse system, delivery delays and support inquiries follow. If orders must be transferred manually from the shop into the ERP, the entire fulfillment cycle slows down. Professional interface development solves these problems at the root: data flows automatically, bidirectionally and in near real time across all connected systems. The result is faster order cycles, fewer errors and significantly reduced workload for your internal teams.

Without integration
Manual double entry
Incorrect prices in the shop, stock levels diverge, orders typed in by hand — high error rate
Data quality low
VS
With integration
Automated data flow
Correct customer pricing, consistent stock, orders straight into the ERP — near real time
Data quality high, error rate minimal

Six Integration Scenarios for Your B2B Shop

Every system landscape is different. Across more than 50 B2B projects, we have encountered the most common integration requirements and developed proven approaches for each type. The following overview shows the six most important integration scenarios that we implement in virtually every B2B project.

ERP Connectivity

Bidirectional synchronization with SAP Business One, SAP S/4HANA and Microsoft Dynamics 365 Business Central. Product master data, customer-specific pricing, stock levels and orders flow automatically between ERP and Shopware via REST APIs, OData endpoints or RFC/BAPI interfaces. Changes in the ERP are visible in the shop within seconds.

DATEV Integration

Automated transfer of invoices, credit notes and payment information to DATEV Unternehmen Online or DATEV Rechnungswesen. Account assignment rules are mapped in the integration layer so your accountant can accept the postings without manual rework. GoBD-compliant archiving included.

PIM Systems

Connection of Product Information Management systems as the single source of truth for product data. Product descriptions, technical data sheets, images, documents and category trees are synchronized reliably into your Shopware shop. Support for ETIM, BMEcat and ECLASS classifications for standardized product data.

CRM Integration

Linking your Customer Relationship Management with the online shop. Customer master data, contacts, sales territories and interaction history are synchronized. Your sales team sees online orders in the CRM, and the shop uses CRM segmentation for personalized catalogs and customer-specific pricing.

Logistics and Shipping

Integration with warehouse management systems, shipping carriers and track-and-trace platforms. Tracking numbers, delivery status and return information are exchanged automatically between logistics partner and Shopware, displayed in real time in the B2B customer portal.

Marketplaces and EDI

Integration with B2B marketplaces and traditional EDI communication via EDIFACT, cXML or OCI punchout. Orders from your customers' procurement platforms flow directly into your Shopware shop and onward into your ERP without manual intermediate steps.

Integration Patterns in Detail: REST, SOAP, EDI and SFTP

Choosing the right integration protocol depends on the capabilities of the systems involved, the requirements for latency and data volume, and the industry-specific standards in play. In practice, we employ the following integration patterns, often combining several within a single project.

REST APIs

The standard for modern system integration. JSON-based data exchange over HTTP with a clear resource structure. Ideal for real-time scenarios such as price queries, inventory checks and order submission. Versioning via URL paths or headers ensures backward compatibility.

SOAP and OData

Proven protocols for connecting to enterprise systems. SOAP with WSDL contracts for type-safe communication, OData for standardized access to SAP data. We generate client code from service definitions for maximum reliability and minimal maintenance effort.

EDI and SFTP

For electronic data interchange with large enterprises, we implement EDIFACT, cXML and VDA standards. Transmission occurs via AS2 or encrypted SFTP. For legacy systems without APIs, we deliver file-based integrations via CSV or XML export with automated file reconciliation.

Data Mapping and Transformation

The Transformation Layer as Translator

The greatest challenge in integration projects is rarely the technical connection itself but the correct mapping and transformation of data between disparate systems. A product in the ERP has different fields, units and categories than in the Shopware shop. Customer prices may be stored in the ERP as a discount percentage on the list price, while the shop requires absolute prices. Units of measure, currencies and tax rates must be converted correctly.

ERP: discount 12%
Mapping
Shop: 87.12 €
Field mapping, unit and currency conversion defined centrally
Business rules: volume pricing, conditions and rounding in one place
Every mapping rule versioned and logged for audits

We address these challenges through a dedicated transformation layer that mediates between source and target system. In this layer, field mappings, value conversions, unit transformations and business rules are defined and documented centrally. Changes to the data structure of one system require adjustments only in the transformation layer, not across the entire integration. This pattern has proven particularly maintainable in our projects, as new fields or changed logic can be added without reimplementing the interface.

  • Field mapping: detailed mapping of all relevant data fields between source and target system
  • Value conversion: automatic conversion of units, currencies and tax rates
  • Business rules: condition determination, discount calculation and price list assignment in the transformation layer
  • Data validation: checks for completeness, plausibility and format compliance before handoff
  • Error logging: detailed logs for every transformed record with source and target values
  • Versioning: traceable change history of mapping rules for audit purposes

Our Technical Approach to Integration Projects

Interfaces are the most critical component of a B2B e-commerce architecture. When an integration fails, orders stall and data drifts apart. That is why we rely on proven design patterns that prioritize reliability, traceability and maintainability. Our integrations use message queues (RabbitMQ, Apache Kafka) for asynchronous processing, ensuring that a temporary outage of a target system does not cause data loss. Idempotent API calls prevent repeated transmissions from creating duplicates. Comprehensive logging and monitoring allow us to detect errors early and pinpoint their cause precisely. As part of our performance and monitoring services, we continue to monitor your interfaces well beyond go-live.

Real-Time vs. Batch: Synchronization Modes Compared

Not every data flow requires real-time synchronization. Choosing the right synchronization mode is one of the most important architectural decisions in integration projects. Real-time synchronization (event-based or webhook-driven) is essential for stock levels, prices and order status, since your customers expect current information in the B2B portal. Batch synchronization at defined intervals is better suited for master data reconciliation, product catalog updates and statistical evaluations where a delay of minutes or hours is acceptable.

In practice, we combine both modes within a single integration. For example, price changes in the ERP trigger an event that updates the affected prices in the shop immediately, while a full catalog reconciliation runs as a nightly batch job. This hybrid architecture significantly reduces system load compared to pure real-time synchronization while still ensuring that business-critical data such as inventory and prices remain current. The intervals and triggers are aligned with your team to match the specific requirements of your business processes.

Data FlowRecommended ModeRationale
Stock LevelsReal-time (event-based)Customers expect current availability
Customer PricesReal-time with cacheIncorrect prices erode trust
Order StatusReal-time (webhook)Self-service in the portal requires current data
Product Master DataBatch (hourly or daily)Infrequent changes, high data volume
Product Images and DocumentsBatch (nightly)Large files, low change frequency
Invoices and DocumentsNear-realtime (minutes)Timely availability in the document archive

Error Handling and Monitoring Concepts

In production integration environments, errors are inevitable: an ERP system may be briefly unreachable during an update, a data record may contain invalid values, an API rate limit may be exceeded. What matters is not whether errors occur but how the system handles them. Our integrations implement a multi-tier error handling concept that distinguishes between transient and permanent errors.

Transient errors such as network timeouts or temporary system outages are automatically retried via an exponential backoff mechanism. The failed message remains in the message queue and is reprocessed after increasing wait intervals. Permanent errors such as invalid data are moved to a dead-letter queue and reported to your team via a monitoring dashboard. Every error is logged with full context: timestamp, affected record, error type, HTTP status code and the number of retry attempts so far.

Automatic Retry Logic

Exponential backoff with configurable intervals and maximum retry counts. Idempotent processing prevents duplicates on redelivery.

Dead-Letter Queue

Permanently failed messages are stored in isolation and can be reprocessed manually or automatically after the underlying issue is resolved.

Real-Time Alerting

Critical errors trigger immediate notifications via email or webhook. Configurable thresholds prevent alert fatigue for non-critical warnings.

Integration Project in Five Phases

We document your existing system landscape, capture all relevant data flows and determine which system serves as the authoritative source for each data domain. The output is an integration matrix showing which data needs to be synchronized in which direction and at what frequency.

Integration Options Compared

Choosing the right integration approach depends on the complexity of your system landscape, requirements for latency and reliability, and your budget. The following overview helps with orientation.

CriterionDirect API ConnectionMiddleware / Integration LayerFile-Based Import
Real-Time CapabilityNear real time (seconds)Near real time with bufferingBatch-based (minutes to hours)
Error HandlingIn application codeCentralized in middleware layerManual reprocessing
ScalabilityDependent on target API limitsHigh through message queuesLimited by file sizes
Maintenance EffortIndividual per interfaceCentralized and standardizedLow but error-prone
Best Suited ForFew systems, simple flowsComplex landscapes, many systemsLegacy systems without APIs
Typical TechnologiesREST, GraphQL, OData, SOAPRabbitMQ, Redis Streams, Apache KafkaCSV, XML, SFTP, EDIFACT

What Connecting an Interface Costs

Open-ended effort estimates offer little help when planning a budget. That is why we name clear fixed prices for the most common connections. The final price depends on your system landscape and critical data flows and is fixed after a free integration analysis — with no hidden items. Where useful, we bundle the ongoing operation of your interfaces with our maintenance and monitoring services.

Fixed Prices for Your Interfaces

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

Standard Connector

Proven connection for common ERP and accounting systems.

from 4,900 € fixed price net
  • SAP Business One, S/4HANA, Dynamics 365 or DATEV
  • Products, prices, stock and orders in sync
  • Standardized field mapping
  • Queue with automatic retry
  • Setup and testing included
Request Analysis
Recommended

Custom Integration

Bidirectional connection with its own transformation layer.

from 12,900 € fixed price net
  • Customer-specific prices, tiers and conditions
  • Dedicated transformation and mapping layer
  • Middleware with message queue (RabbitMQ, Kafka)
  • Real-time and batch synchronization combined
  • Load testing and go-live support
Request Analysis

Punchout & EDI

Connect your customers' procurement systems.

from 4,900 € per connection net
  • OCI punchout from 4,900 € per connection
  • cXML punchout from 6,900 € per connection
  • EDIFACT and VDA via AS2 or SFTP
  • Cart transfer back (PunchOutOrderMessage)
  • Testing with the procurement system included
Request Analysis

Support on a time basis 119 € per hour, day rate 940 € net. Ongoing interface monitoring from 249 € per month (Business 490 €, Premium 990 €). License costs for Shopware B2B Components are shown transparently and separately. You receive a binding quote after the free integration analysis.

Unsure Which Connection You Need?

In the free integration analysis, we review your system landscape and give you a concrete fixed price per interface — before development begins.

Request Integration Analysis Call: +49 5123 9579000

Security and Authentication in Integrations

B2B data flows carry business-critical information: customer pricing, order data, accounts receivable master records and invoice details. The security of this data is our highest priority. All interfaces use encrypted connections (TLS 1.3), and API access is secured via OAuth2 tokens or dedicated API keys that are rotated on a regular schedule. IP whitelisting and VPN tunnels provide additional protection for sensitive connections, and access logs document every data operation for complete traceability.

For system-to-system authentication, we employ different methods depending on security requirements and system capabilities. OAuth2 with the client credentials flow is the preferred standard for modern API-to-API communication. For SAP systems, we use certificate-based authentication or SAP-specific token mechanisms. For SFTP-based integrations, SSH key pairs are employed. Every authentication method is configured so that credentials never appear in plain text in configuration files or logs.

For GDPR-relevant data flows, we implement pseudonymization mechanisms and access logging. Retention periods for transaction logs are coordinated with your legal department. For the DATEV connection, we ensure GoBD compliance so that document data is archived in an audit-proof manner and the automated document export meets the requirements of the German tax authorities.

Additionally, we define a detailed error escalation concept for every interface. Critical errors such as failed order write-backs are reported immediately via email and optionally via webhook to your team. Less critical warnings such as temporary timeout errors are logged and displayed in aggregate on the monitoring dashboard. This way, you maintain a constant overview of the health of your entire integration landscape.

Early Interface Planning Saves Costs

The biggest cost traps in integration projects arise from missing or imprecise interface specifications. When field mappings, data formats and synchronization directions have to be clarified during development, it leads to rework and delays. Our structured analysis process ensures that all integration requirements are fully documented and agreed upon with all system owners before development begins. This upfront work typically reduces the overall effort by 20 to 30 percent (based on our project experience) compared to an unstructured approach. Start with a strategic consultation to clarify your integration requirements early.

Real-World Integration Scenarios

In our projects, we consistently encounter similar integration challenges that are relevant across industries. A typical scenario is bidirectional inventory synchronization between shop and warehouse management. When a customer places a B2B order, the inventory in the ERP must be reserved immediately to prevent overselling. At the same time, inventory changes from the ERP, such as goods receipts or manual corrections, must be reflected in the shop promptly. We implement such scenarios via event-based synchronization with configurable thresholds and automatic conflict resolution.

Another common scenario involves customer-specific pricing. B2B prices are rarely static: framework contract conditions, volume pricing, special agreements and time-limited promotions must be queried from the ERP in real time and displayed in the shop. The challenge lies not only in the technical connection but also in performance: when a catalog of 50,000 items needs to calculate individual prices on every page view, intelligent caching strategies and asynchronous price queries are critical for the user experience.

The third core scenario is document and record synchronization. Order confirmations, delivery notes, invoices and credit notes are generated in the ERP and should be available for download as PDFs in the B2B customer portal. The integration encompasses automatic assignment to the correct customer account, archiving according to compliant retention periods and optional customer notification when new documents are available. This document synchronization significantly reduces manual effort for the sales support team and increases customer satisfaction through instant document availability. Three articles go into the details: ERP Integration in B2B E-Commerce: SAP, DATEV, Dynamics, API Architecture in B2B: REST, GraphQL and Message Queues and SAP ECC 2027: Shop Integration for the S/4HANA Switch.

Integrations at a glance

  • Two-way synchronization of items, prices, stock and orders instead of nightly CSV exports.
  • Connected systems include SAP Business One and S/4HANA, Microsoft Dynamics, DATEV, Lexware and industry-specific inventory systems.
  • A dedicated transformation layer encapsulates field mappings so a change in one system does not break the entire chain.
  • Standard connector from 4,900 € net, custom integrations from 12,900 € net.
  • In addition, PIM integration covers product data maintenance and punch-out and OCI cover your key accounts' procurement systems.

Frequently Asked Questions About Integrations and Interfaces

How your electrical wholesale business could look online

The draft shows how the product areas, the stock list and the tier calculator work together, and how the customer account gates prices. The business shown here is invented.

Draft
Electrical wholesaler

Wholesale with customer account and volume tiers

A draft for an electrical wholesaler: six product areas, a filterable and sortable stock list with the states in stock, remaining stock and made to order, plus a calculator that shows which volume tier applies to an entered quantity. Prices deliberately stay inside the customer account, which is only unlocked after the trade credentials have been checked. Trade counter, delivery runs and payment terms follow as separate sections.

Customer accountVolume tiersStock listCounter pickup

Illustrative layout drafts. The businesses shown are fictitious; these are not client projects.

What can we help you with?

One click is enough — everything after that is optional.

Tell us briefly about the project

Everything on this step is optional.

When would you like to start? (optional)
Rough budget range (optional)

Optional — you are not committing to anything.

How can we reach you?

We usually get back to you within one business day.

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