Connect Intershop and InRiver

Connecting Intershop and InRiver for a company using both could enable automated transfer of product information from InRiver’s PIM platform into Intershop’s e-commerce environment. This could reduce manual data entry and help maintain consistency of product data across sales channels, supporting efficient catalog updates and product launches.

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

Contact us

Why connect Intershop and InRiver?

A company operating both Intershop and InRiver could benefit from connecting these two systems to enable more efficient and accurate data exchange. Such a connection could reduce the need for manual data entry into both platforms, helping to prevent errors and inconsistencies that occur when product or catalog information is updated in one system but not the other. Without a connection, teams could face challenges such as duplicate effort, mismatched product details, and delays in updating online storefronts or product catalogs, which could in turn lead to decisions based on outdated or incomplete information. If a connection were established, it could enable the exchange of key data such as product descriptions, attributes, images, pricing, and inventory levels between Intershop, an e-commerce platform, and InRiver, a product information management (PIM) system. This could help ensure that both systems reflect the most current and accurate product information, supporting more reliable online sales and marketing activities. The specific data that can be exchanged would depend on what each system makes available through its API and would need to be determined for each particular 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 InRiver 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.