SAP Integration for Your Online Shop
We connect SAP Business One and S/4HANA bidirectionally with your shop — products, prices, stock and orders flow in real time instead of by hand. The fixed price is set after an upfront system analysis.
24/7
monitoring
50+
SAP integration projects
< 5 s
synchronization latency
99.5 %
interface availability
Fixed price · net plus VAT
- Fixed price after a system analysis instead of an open estimate
- SAP Business One and S/4HANA via Service Layer, OData and RFC/BAPI
- Bidirectional sync of products, prices, stock and orders
- Monitoring and SLA operation of your interface well beyond go-live
Standard scope bidirectional: products, prices, stock and orders. Custom business logic on a time basis — project day 990 € net (hourly rate 119 € per hour). A third-party connector license from 99 € per month applies separately. All prices net plus VAT. 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.
SAP is the heart of inventory management in many mid-market companies. Product master data, customer conditions, stock levels and order processes are managed in SAP and must communicate seamlessly with the online shop. As a specialized integration agency, we know both worlds: the specifics of SAP interface technologies (RFC, BAPI, OData, Service Layer) and the requirements of modern shop platforms. The result: robust, performant integrations that work reliably in daily operations.
SAP Data Quality: Manual Maintenance vs. Integration
SAP Business One: Integration for the mid-market
SAP Business One (B1) is the most widely deployed ERP solution in mid-market trading and manufacturing companies. Integration with an online shop uses the Service Layer, a REST-based API that provides access to all business objects: items, business partners, orders, deliveries and invoices. We use the Service Layer as the primary interface, supplementing it with DI-API calls for complex business logic that cannot be mapped through the REST API.
A typical SAP Business One integration project includes synchronization of product master data with all relevant attributes (name, description, weight, units of measure, serial number requirements), price lists with customer-specific special prices and volume discounts, stock levels across multiple warehouses, customer address data with delivery addresses and contacts, and bidirectional order processing from web shop cart to SAP delivery note.
SAP S/4HANA: Enterprise integration for complex scenarios
SAP S/4HANA offers a powerful foundation for shop connectivity with its OData-based APIs and Integration Suite. The in-memory architecture of S/4HANA enables real-time queries even with large data volumes, which is particularly relevant for availability checks (ATP) and pricing. We use CDS Views and OData V4 Services for read access to master data and BAPI/RFC interfaces for transactional order processing.
S/4HANA integrations are typically more complex than B1 projects: client structures are more nested, pricing uses condition techniques with numerous access sequences, and organizational structures (company code, sales area, plant) must be correctly mapped in the integration layer. Our experience with both SAP worlds enables us to choose the right integration strategy for your specific system landscape.
The six core data flows of a SAP shop integration
Regardless of whether you use SAP Business One or S/4HANA, the fundamental data flows repeat. The following overview shows the six most important synchronization areas that we implement in virtually every SAP integration project.
Product Master Data
Item numbers, names, descriptions, weights, units of measure and classifications are synchronized from the SAP system to the shop. Changes in SAP are available in the shop without manual intervention.
Prices and Conditions
List prices, volume prices, customer-specific special conditions and time-limited promotions are transferred from SAP price lists to the shop. Currency conversion and tax assignment included.
Stock Levels
Available quantities per warehouse, reserved stock and expected goods receipts are synchronized at defined intervals or in real time. Multi-warehouse queries and ATP calculations are implementable.
Orders and Deliveries
Shop orders are created as sales orders in SAP. Order status, partial deliveries and shipping information flow back to the shop. The complete order history is viewable in the customer portal.
Business Partners
Debtors, delivery addresses, contacts and payment terms are bidirectionally synchronized. New customer registrations in the shop automatically create business partners in SAP.
Invoices and Documents
SAP invoices and credit notes are made available as PDF downloads in the shop. Payment receipts from the shop update the document status in SAP. Optional: forwarding to DATEV.
Technical integration patterns for SAP connectivity
The choice of integration pattern depends on latency, data volume and transaction safety requirements. In practice, we use the following patterns, often in combination within a single project.
REST via Service Layer
The SAP B1 Service Layer and S/4HANA OData Services provide REST-based endpoints for all common business objects. Ideal for CRUD operations with moderate data volume and acceptable latency in the seconds range.
RFC/BAPI for Transactions
For complex business processes like SAP pricing with condition techniques or ATP availability checks, we use RFC calls that directly execute SAP business logic and deliver consistent results.
Message Queue Integration
For high data volumes and maximum decoupling, we use message queues. SAP change documents trigger events that are distributed via RabbitMQ to the shop and other target systems.
Common challenges in SAP shop integrations
SAP integrations are technically demanding because SAP systems represent their own world with unique data types, naming conventions and processing logic. The following four topics appear in virtually every project, and we have a proven approach for each.
Data types and encoding
Format conversions and correct character encoding of special characters and umlauts are handled centrally in the integration layer, not in every endpoint.
Pricing with condition technique
Instead of rebuilding SAP access sequences in the shop, we synchronize calculated net prices or call SAP pricing via RFC in real time as needed.
Displaying stock types correctly
Freely available, quality inspection, blocked and consignment stock: together we define the business rules for which stock counts as available in the shop.
Organizational structures
Company code, sales area and plant are cleanly mapped in the integration layer so quantities and prices stay tied to the right context.
Pricing: SAP logic without duplicating it
SAP processes customer-specific prices, material group discounts, time periods and minimum quantities in a condition chain with access sequences. Replicating this logic one-to-one in the shop is rarely practical. We choose between precomputed net prices and a real-time RFC call depending on data volume and freshness requirements.
- Precomputed net prices for high volumes and infrequent changes
- Real-time RFC pricing for highly dynamic B2B conditions
- Combination of both approaches per assortment area possible
Our project approach for SAP integrations
SAP System Analysis
We analyze your SAP installation: which modules are active? Which customizations affect the interfaces? Which document types, number ranges and organizational structures need to be considered? The result is a detailed interface concept.
Mapping and Proof of Concept
For each data flow, we create a mapping matrix with source fields, target fields and transformation rules. Critical scenarios like pricing or ATP checks are implemented as proof of concept and validated with real test data.
Iterative Implementation
Development proceeds in prioritized sprints: product master data first, then prices and stock, finally order processing. After each sprint, we test the interfaces on the staging environment with your department representatives.
Integration and Load Testing
Before go-live, we test all data flows end-to-end with realistic data volumes. Load tests simulate peak scenarios: initial import of 100,000 products, 5,000 simultaneous price changes, order processing during SAP daily closing.
Go-Live and Hypercare
Go-live proceeds with close monitoring. During the two-week hypercare phase, we accompany production operations with heightened attention, analyzing edge cases and optimizing synchronization intervals based on real data volumes.
Ongoing Operations
After the hypercare phase, we take over regular operations with agreed SLAs. Proactive monitoring, automated error handling and quarterly reviews ensure long-term stability.
What a SAP Integration Costs
In SAP projects, an open-ended effort estimate is a particularly impractical basis for budgeting. That is why we state clear starting prices for the most common SAP scenarios. The binding fixed price is set after the free SAP system analysis — with no hidden items. Ongoing connector licenses and operations are shown transparently and separately from the project fixed price.
Fixed Prices for Your SAP Connection
All prices net plus VAT. Every project starts with a free SAP system analysis and a binding fixed price. Scope and system landscape determine the right path.
SAP Standard Connection
Connector-based integration in standard scope.
- SAP Business One or S/4HANA via Service Layer and OData
- Products, prices, stock and orders bidirectional
- Delta synchronization and standard field mapping
- Queue with automatic retry
- Setup, testing and monitoring included
SAP Custom Integration
Custom business logic beyond the standard scope.
- Condition-technique pricing via RFC in real time
- ATP availability checks and multi-warehouse logic
- Multi-client and complex S/4HANA org structures
- Message-queue decoupling for high data volumes
- Load test and accompanied go-live included
Operation and Support
Ongoing operation of your SAP interface after go-live.
- SLA operation with proactive monitoring
- Compatibility check before every SAP update
- Extension with additional data flows
- Quarterly data quality reviews
- Third-party connector license from 99 € per month separate
All prices net plus VAT. The binding fixed price is set after the free SAP system analysis. Ongoing connector licenses (third party, from 99 € per month) are shown transparently and separately from the project fixed price.
Unsure Which SAP Scope Fits You?
In the free SAP system analysis, we review your system landscape, prioritize the critical data flows and give you a concrete fixed price — before development starts.
SAP integration for various shop platforms
Our SAP integration expertise is not limited to a single shop platform. We have experience connecting SAP to Shopware 5 and 6 as well as all common open-source and proprietary shop platforms. The integration architecture remains consistent: a middleware layer abstracts SAP specifics and provides normalized data via a REST API consumed by the shop. This approach enables changing the shop platform without rebuilding the SAP integration.
The middleware handles the heavy lifting: data type conversions, character encoding, error handling and retry logic. The shop connector on the other side is lean and focuses on the specifics of the respective platform: product import APIs, order export formats and pricing structures. This separation of responsibilities makes the overall architecture maintainable and extensible.
Investment security and long-term partnership
A SAP integration is a long-term investment. SAP updates, shop updates and changing business requirements demand continuous evolution of the interfaces. Our operations contracts ensure your integration is professionally maintained after go-live. Regular compatibility checks before SAP updates, proactive adaptation to new API versions and extension with additional data flows are part of our long-term support.
Manual order entry is eliminated, stock display in the shop matches reality, and price changes in SAP take effect in the shop within seconds.
Talk to us about your SAP landscape and we will show you what an integration could look like. Also learn about DATEV integration as a complement to your SAP connectivity.
SAP data quality as a success factor
The quality of data in the SAP system directly impacts integration quality. When product master data has been maintained over years with inconsistent formatting, missing mandatory fields or outdated category assignments, interface development ruthlessly reveals these deficiencies. That is why every SAP integration project begins with a data quality analysis: we check the completeness of mandatory fields, the consistency of formatting and the currency of category assignments. The result is a remediation plan implemented before or in parallel with interface development.
- Product names in different formats (capitalized vs. mixed)
- Missing or outdated long texts and descriptions
- Inconsistent units of measure and unmaintained weight data
- Category assignments not updated since initial setup
Data cleanup belongs in the project, not after it
Security architecture of SAP connectivity
The SAP-shop interface transmits sensitive business data: customer-specific prices, order volumes, stock levels and sometimes personal data. We secure each of these data flows on multiple levels and consistently follow the principle of least privilege.
TLS encryption
All data transfers between SAP, interface and shop are encrypted via TLS.
Token authentication
Access to the SAP Service Layer and OData services uses token-based mechanisms, complemented by IP whitelisting to defined servers.
Minimal permissions
The integration user receives only the rights for the defined data flows: read on master data, write for order creation, no admin rights.
Audit logging
All transactions are logged so it remains traceable at any time which data was transferred when.
Long-Term Partnership and SAP System Support
SAP integrations are long-term investments that must grow with both system landscapes. SAP regularly releases updates and feature packs, Shopware CE evolves continuously. Our maintenance packages keep your integration in step: monitoring of synchronization processes, adaptation to API changes, performance optimization and quarterly data quality reviews. Every integration decision is documented in architecture diagrams, mapping matrices and operations handbooks, so it remains comprehensible even after years and personnel changes on both sides. This long-term support is why 97 percent (project experience) of our clients renew their contracts.
If you are planning an SAP-Shopware integration or want to evolve your existing integration, contact us for a free initial consultation. We analyze your current system landscape and provide a well-founded assessment of architecture, timeline and budget.
Performance optimization for SAP interfaces
With large product catalogs and high order volumes, the performance of the SAP interface is business-critical. We rely on proven optimization strategies: delta synchronization transfers only changed records instead of the entire dataset. Batch processing combines individual requests into efficient bulk operations. Caching layers reduce the number of accesses to the SAP system for frequently queried data like price lists and product master data.
For order processing, we use asynchronous patterns: orders are passed to SAP via a message queue so the shop ordering process does not depend on SAP processing speed. Order confirmations and status changes flow back asynchronously. This approach ensures the shop remains performant even during SAP peak loads (daily closing, inventory counts, mass price changes). Monitoring dashboards visualize throughput, latency and queue depth of all SAP data flows in real time, enabling early detection and resolution of bottlenecks.
Frequently asked questions about SAP integration
Further reading: SAP and Shopware: Real-Time Synchronization of Master Data describes the data flows in detail, SAP Integration Suite: Clean-Core Shop Link puts the clean-core strategy in context, and Customer-Specific Prices from ERP explains price determination and caching for B2B assortments.
Connecting SAP to the shop: three routes compared
SAP offers several integration routes. Which one fits depends on release, operating model and change frequency.
Direct access to SAP
- Fastest variant when only a few fields are required
- No additional component to operate
- Load from the shop hits the production system directly
- Changes in the SAP release affect the shop immediately
- Error handling is spread across shop and SAP
Extension inside the SAP core
- Even complex business logic can be represented
- Reuses existing authorisation and posting logic
- Makes later upgrades and clean-core policies harder
- Adjustments require SAP development cycles
- Higher dependence on the SAP team in daily business
Decoupled integration layer
- Access via Service Layer, OData or RFC/BAPI depending on the release
- Caching and peak-load buffering outside the production system
- The SAP core stays untouched, upgrades remain plannable
- Setup fixed price from 9,900 € net after a free system analysis
- One additional component that has to be operated and monitored
Typical starting situations in SAP landscapes
Illustrative scenarios from typical project sequences (project experience), anonymised and without customer details.