Skip to Content

Connect Kerridge and Perfion

Connecting Kerridge and Perfion could enable the transfer of product data and inventory information between the two platforms. This would support consistent product details across business functions and reduce manual data entry. The integration could also help synchronize updates, ensuring that changes in one system are reflected in the other.

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

Contact us

Why connect Kerridge and Perfion?

A company that operates both Kerridge and Perfion could benefit from connecting these systems to facilitate the exchange of business-critical data. Without a connection, staff might have to manually enter the same information into both platforms, which can increase the risk of errors and consume significant time. Over time, records in each system could diverge, leading to inconsistencies in product information, inventory levels, or pricing. This can result in decisions being made based on outdated or mismatched data, potentially impacting customer service, procurement, or sales operations. If a connection were established, the kinds of data exchanged could include product master data, inventory details, pricing, and supplier information. For example, changes made to product specifications in Perfion could be reflected in Kerridge to ensure that sales and procurement teams are always working with the most current information. Similarly, stock levels or transactional data from Kerridge could be shared back to Perfion to provide a unified view of product performance and availability. The specific data that can be exchanged depends on the interfaces and data models that Kerridge and Perfion make available through their APIs, and would need to be determined for each individual 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 Kerridge and Perfion 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