Skip to Content

Connect Intershop and Kerridge

Connecting Intershop and Kerridge for a company could enable the transfer of product, inventory, and order data between the two systems. This connection could support more efficient order processing, reduce manual data entry, and help maintain consistent information across sales and back-office operations.

You can build this integration on the System2System platform. We design the connection between Intershop and Kerridge around the way you work — not as an off-the-shelf connector, but to fit your systems.

Contact us

Why connect Intershop and Kerridge?

A company operating both Intershop and Kerridge could benefit from connecting the two systems to allow data to be exchanged between them. Without such a connection, teams might have to enter the same information twice, which can lead to errors and wasted time. When the same data is maintained in separate systems, there is also a risk that records could drift apart as updates made in one system are not reflected in the other. This can result in business decisions being made based on outdated or inconsistent information, affecting everything from stock levels to customer service. If these systems were connected, the types of data that could be exchanged would depend on the roles each system plays. For example, data such as product information, inventory levels, pricing, sales orders, and customer records are often important for companies using platforms for commerce and enterprise resource planning. By exchanging such data, a company could reduce manual work, improve accuracy, and ensure that both systems reflect the latest business activity. However, what can actually be exchanged depends on what each system exposes through its API, and is determined per situation.

How System2System builds an integration

Connectors

We connect to each system through the interface it offers — an API, a database, a file exchange or a webhook — and handle authentication, rate limits and retries.

Mapping

Fields rarely line up one to one. We map and transform the data so both systems receive it in the shape they expect.

Workflow

We define what triggers an exchange, in which direction data flows and which system takes precedence when the two disagree.

Monitoring

Every exchange is logged. Failures are flagged and can be replayed, so nothing disappears without anyone noticing.

What can actually be exchanged?

That depends on what Intershop and Kerridge make available through their APIs, on the licences and modules in use, and on the version each system runs. Which records are synchronised, in which direction and how often, is something we determine together before any work starts.

We are happy to look at your specific situation and tell you what is feasible — including when the answer is that it is not.

About these systems

Read more about each system and what it can be connected to

Looking to connect these systems?

Talk to us about what your setup needs. No obligation.

Contact us