Skip to Content

Connect Kerridge and Diract

Connecting Kerridge and Diract for a company that uses both could allow for the transfer of relevant business data between the systems. This could support more accurate and timely information sharing, reduce manual data entry, and improve operational efficiency by aligning processes that depend on data from both platforms.

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

Contact us

Why connect Kerridge and Diract?

A company that operates both Kerridge and Diract could benefit from connecting these two systems to facilitate data exchange and improve operational efficiency. Without such a connection, staff may be required to enter the same data separately into each system, which increases the risk of errors and inconsistencies. Over time, this can lead to records in Kerridge and Diract diverging, so that information is not aligned between the two, making it harder for teams to trust the data they are using. Decision-making can then be based on outdated or incomplete figures, potentially impacting customer service, inventory management, and financial reporting. If a connection between Kerridge and Diract were established, it could enable the transfer of key business data between the two platforms. Examples of data that could be exchanged include product information, customer details, sales orders, purchase orders, stock levels, and invoices, provided that these data types are supported by both systems. Sharing such information could reduce manual effort, improve data accuracy, and make business processes more responsive and transparent. However, the specific data that can be exchanged in practice depends on what each system makes available through its API or other integration methods, and must be determined for each individual case.

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 Diract 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