Skip to Content

Connect Kerridge and InRiver

Connecting Kerridge and InRiver could enable a company to transfer product data between the two platforms, supporting more consistent information across sales and marketing channels. Such a connection could reduce manual data entry and help maintain up-to-date product details in both systems, potentially improving operational efficiency and data accuracy.

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

Contact us

Why connect Kerridge and InRiver?

A company operating both Kerridge and InRiver could benefit from connecting these systems to allow automatic data exchange between them. Without such a connection, staff may need to enter the same information in both systems, which could increase the risk of errors and consume valuable time. Over time, differences could develop between records held in each system, leading to situations where decisions are made using outdated or inconsistent data. This could affect areas such as inventory management, product information accuracy, and customer service. If a connection were established, it could support the transfer of data such as product details, pricing, stock levels, and order information, where each system handles these types of records. The specific data types exchanged would depend on what is relevant to the company’s operations and what each system is designed to manage. The actual data that can be shared depends on the capabilities of each system’s API and must be determined for each implementation.

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 Kerridge 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.

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