Connect Edifact and Kerridge

Connecting Edifact and Kerridge for a company could enable the automated exchange of transactional data, such as orders and invoices, between the two systems. This integration could reduce manual data entry, improve accuracy, and support more efficient business processes by ensuring that information flows directly from one platform to the other.

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

Contact us

Why connect Edifact and Kerridge?

A company that operates both Edifact and Kerridge could consider connecting these systems to allow relevant business data to be exchanged between them. Such a connection could help reduce manual data entry by enabling information to flow automatically from one system to the other. Without this kind of link, staff may need to enter the same data into both systems, which can result in wasted time, higher risk of errors, and inconsistencies between records. Over time, these discrepancies could lead to business decisions being made on outdated or mismatched information, potentially impacting customer service, inventory accuracy, and financial reporting. The types of data that could be exchanged between Edifact and Kerridge depend on the roles these systems serve. Edifact is widely known as a standard for electronic data interchange, so it could be used to send and receive structured business documents such as purchase orders, invoices, or shipping notices. Kerridge is known for providing ERP solutions, often in the distribution and automotive sectors, and could hold data on products, inventory, sales orders, and customer accounts. If the two systems were connected, documents or records such as sales orders, inventory updates, and invoices could be transferred automatically, reducing the risk of discrepancies and improving information flow across departments. What can actually be exchanged depends on what each system exposes through its API, and is determined per 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 Edifact 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.