Connect cXML and Kerridge

Connecting cXML and Kerridge for a company using both could make it possible to automate the exchange of procurement documents and transactional data between the two systems. This could reduce manual data entry, help ensure consistency of information, and support more efficient business processes involving purchasing and inventory management.

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

Contact us

Why connect cXML and Kerridge?

A company operating both cXML and Kerridge systems could benefit from enabling them to exchange data directly. Without such a connection, staff may need to enter the same information in both systems, which increases the risk of errors and consumes valuable time. This manual effort can also lead to records becoming inconsistent between the two platforms, and decisions may be made based on outdated or incomplete information if updates are not synchronized. If a connection were established, it could allow for the transfer of transaction data, such as purchase orders, invoices, and shipment notices, between cXML and Kerridge. This could reduce duplicate data entry and help ensure that both systems reflect the same business reality. The types of data exchanged would depend on the features supported by each system, but could include supplier details, order status updates, and inventory information. The actual data that can be exchanged depends on what each system exposes through its API and is determined for each specific 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 cXML 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.