Connect as2 and Kerridge

Connecting as2 and Kerridge could allow a company to transfer data between the two systems, such as exchanging documents or synchronizing business information. This could reduce manual entry and help maintain accurate records across both platforms, supporting more efficient operations for organizations that use both as2 and Kerridge.

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

Contact us

Why connect as2 and Kerridge?

A company operating both as2 and Kerridge could benefit from connecting the two systems to ensure that critical business data is consistent and up to date across their operations. Without such a connection, staff may need to enter the same information into both systems, increasing the risk of errors, wasted time, and duplicated effort. Over time, records in as2 and Kerridge could become inconsistent, leading to confusion, discrepancies in reporting, and decisions based on outdated or incomplete information. If data exchange were enabled between these systems, it could allow for the transfer of information such as customer records, product details, inventory levels, sales orders, invoices, and financial transactions, depending on what each system is designed to handle and what is supported by their interfaces. The specific data that could be exchanged would depend on the capabilities and openness of each system’s API, and would need to be defined for each company’s requirements and technical environment.

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