Question 1

What does shop integration mean exactly?

Accepted Answer

Shop integration refers to the technical connection of an online shop with other business systems, particularly ERP (inventory management), accounting (DATEV), PIM (product data management) and CRM (customer management). The goal is automatic, bidirectional data exchange: product data, prices and stock levels flow from the ERP to the shop, orders flow back, invoices are transferred to accounting. Without integration, this data must be transferred manually, which is time-consuming, error-prone and not scalable.

Question 2

Which systems can be connected to the online shop?

Accepted Answer

We integrate a wide range of systems: ERP systems like SAP Business One, S/4HANA, Microsoft Dynamics 365, Sage and SelectLine. Accounting software like DATEV Unternehmen Online and Lexware. Common PIM systems for product data management. CRM systems like Microsoft Dynamics CRM and industry-specific solutions. Warehouse management systems and shipping carriers. The basic principle: any system with an API or export interface can be connected.

Question 3

Which shop platforms are supported?

Accepted Answer

Our integration architecture is platform-independent. We have experience with Shopware 5 and 6 as well as all common open-source and proprietary shop platforms. The middleware layer abstracts shop-specific APIs so the ERP connector and business logic work independently of the shop platform. This means: if you switch shop platforms in the future, only the shop adapter needs adaptation, not the entire integration.

Question 4

Can existing manual processes be automated step by step?

Accepted Answer

Yes, we actually recommend a phased approach. Rather than automating all data flows simultaneously, we start with the most business-critical interfaces: typically product master data and order transfer to the ERP. In subsequent phases, price synchronization, stock reconciliation and DATEV integration are added. This approach reduces project risk, enables early user feedback and distributes the investment over a longer period.

Question 5

How does a professional integration differ from a CSV-based solution?

Accepted Answer

CSV imports and exports are fundamentally manual processes: someone must create the file, check it and import it. Errors are only detected during import, often too late. A professional integration works automatically and bidirectionally in real time or at defined intervals. Errors are detected and handled immediately. Data quality is consistently higher because automatic validation rules apply. And scalability is given: whether 100 or 100,000 products are synchronized, the effort remains the same.

Question 6

Is integration worthwhile for smaller shops too?

Accepted Answer

Yes, as soon as the manual effort for data maintenance between systems becomes noticeable, automation pays off. With over 100 orders per month or regular price changes across more than 500 products, a professional integration typically pays for itself within six to twelve months (project experience). We offer scalable solutions that grow with your business: start with the most important data flows and expand step by step.

Question 7

How is data consistency between systems ensured?

Accepted Answer

We achieve data consistency through multiple mechanisms: unique identifiers (master keys) link records across system boundaries. Timestamp-based delta synchronization ensures only changed data is transferred. Validation rules in the middleware check data for completeness and consistency before forwarding. And monitoring dashboards show the synchronization status of all data flows in real time.

Question 8

What happens when a system is temporarily unreachable?

Accepted Answer

Our middleware architecture is designed for exactly this scenario. Messages are persistently stored in message queues. When a target system is unreachable, automatic retries with exponentially growing wait times are executed. A circuit breaker prevents overloading the failing system. After recovery, all pending messages are automatically delivered. Dead-letter queues catch messages that could not be delivered after defined attempts.

Question 9

How performant is synchronization with large data volumes?

Accepted Answer

Performance depends on the chosen integration pattern and data volume. With REST APIs, typically 500 to 2,000 records per minute are realistic. Via message queues, we can process 10,000 to 50,000 messages per minute. For initial imports of large catalogs (100,000+ products), we use bulk import strategies with parallel processing. Delta synchronization during ongoing operations is significantly faster since only changes are transferred.

Question 10

What security measures protect data transfer?

Accepted Answer

All data transfers are encrypted via TLS. API access is authenticated via OAuth 2.0 or API keys and protected by rate limiting. IP whitelisting restricts access to defined servers. All transactions are logged for audit purposes. Integration services run on servers in German data centers and are subject to GDPR. Personal data is stored only as long as required for the processing purpose.

Question 11

Can the integration be extended incrementally?

Accepted Answer

Yes, our architecture is modularly designed. New data flows, additional systems and extended business logic can be added at any time without affecting existing integrations. The middleware serves as a central hub to which new systems can simply be connected. Typical extensions after the initial go-live include: DATEV integration, PIM connectivity, marketplace connection or extended inventory logic.

Question 12

Do you support real-time synchronization?

Accepted Answer

Yes, for time-critical data flows we implement real-time synchronization via webhooks and event-based architecture. Typical real-time scenarios include stock changes (goods receipt, picking), order status changes and price changes. For less time-critical data flows like product master data synchronization, we often recommend interval-based synchronization (e.g., every 5 minutes), which uses system resources more efficiently.

Question 13

Which SAP interfaces do you use for shop integration?

Accepted Answer

For SAP Business One, we primarily use the Service Layer (REST API) for master data and transactions, supplemented with DI API calls for complex business logic. For SAP S/4HANA, we use OData V4 Services and CDS Views for read access, plus RFC/BAPI interfaces for transactional processes like order creation and pricing. The optimal integration path depends on your specific SAP configuration.

Question 14

How is SAP pricing mapped in the shop?

Accepted Answer

SAP uses a condition technique with access sequences that is too complex for direct replication in the shop. We offer two approaches: for stable price lists, we synchronize calculated net prices from SAP to the shop. For highly dynamic scenarios with frequent condition changes, we call SAP pricing via RFC in real time. Which approach is optimal depends on the change frequency of your prices and order volume.

Question 15

Can Dynamics 365 Business Central be connected both cloud and on-premises?

Accepted Answer

Yes, we support both variants. The cloud version is connected via standardized REST/OData APIs with Azure AD authentication. The on-premises version additionally offers SOAP web services. Our middleware abstracts Dynamics-specific details so the shop adapter remains identical for both deployment variants.

Question 16

Are industry-specific ERP systems supported?

Accepted Answer

Yes, beyond SAP and Dynamics, we also integrate industry-specific ERP systems like Sage, SelectLine and orgaMAX. The prerequisite is a usable interface: REST API, SOAP web service, ODBC database access or a defined file exchange format. Through our API development, we can create custom connectors even for systems with limited interface capabilities.

Question 17

What happens during SAP or Dynamics updates?

Accepted Answer

System updates can bring interface changes. Our operations contracts include compatibility checks before every major update: we test existing integrations on a test environment with the new version and adapt connectors as needed. For cloud versions like Dynamics 365 BC that update automatically, we monitor release notes and proactively respond to announced API changes.

Question 18

Can multiple ERP systems be connected simultaneously?

Accepted Answer

Yes, this is a typical scenario for corporate groups or post-merger situations. Our middleware architecture is designed to orchestrate multiple source systems in parallel. Each ERP system receives its own connector, the middleware consolidates the data and provides the shop with a unified view. Conflicts with different item numbers or prices are resolved via defined business rules in the middleware.

Question 19

How long does a typical integration project take?

Accepted Answer

Duration depends on scope and complexity. A single ERP-shop connection with core data flows (products, prices, stock, orders) typically takes eight to twelve weeks. A comprehensive multi-system integration with middleware, DATEV connectivity and custom APIs spans twelve to twenty weeks. Add two weeks of hypercare after go-live. We create a detailed timeline after the initial system analysis.

Question 20

What internal resources do we need to provide?

Accepted Answer

You need a project lead who serves as central contact and can drive decisions. For system analysis and mapping, we need access to your ERP data and subject matter experts (typically 2 to 4 hours per week during the analysis phase). For testing and acceptance, people from the affected departments (purchasing, sales, accounting) should be available.

Question 21

How is the project billed?

Accepted Answer

We work with fixed-price packages for defined integration scopes. After the system analysis, you receive a binding offer with detailed scope, milestones and payment plan. Scope changes are managed through a transparent change request process. For ongoing operations after go-live, we offer SLA-based monthly packages.

Question 22

Do you offer maintenance and operations after go-live?

Accepted Answer

Yes, we offer SLA-based operations packages that include monitoring, alerting, error analysis and quarterly optimization reviews. Operations contracts include defined response times and proactive measures like compatibility checks before system updates. Our contract renewal rate of 97 percent shows that our clients value this long-term support.

Question 23

Can we operate the integration internally?

Accepted Answer

Yes, after go-live we hand over complete documentation: architecture diagrams, API specifications, mapping matrices, monitoring setup and operations handbooks. If your IT team has the necessary capacity and expertise, you can take over operations entirely. Many clients still choose our managed service because integration topics require specialized knowledge and internal IT is usually occupied with other tasks.

Question 24

Do you only work with clients in Northern Germany?

Accepted Answer

No, we work nationwide and internationally. Collaboration is primarily remote: workshops via video conference, shared project boards and staging environments enable close collaboration regardless of location. For kick-off workshops and important milestones, in-person meetings are possible. Get in touch and we will discuss the optimal collaboration model for you.

Frequently asked questions about shop integration

General questions about system integration

Technical questions

ERP-specific questions

Questions about project and collaboration