Connect Sitecore and Izettle

Connecting Sitecore and Izettle for a company that uses both could enable the exchange of relevant data between digital marketing activities and point-of-sale transactions. This connection could support more informed decision-making by making it possible to align customer engagement insights from Sitecore with sales and payment information managed in Izettle.

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

Contact us

Why connect Sitecore and Izettle?

A company operating both Sitecore and Izettle could benefit from connecting these systems to ensure that information flows efficiently between their digital experience platform and payment processing environment. Without such a connection, staff may need to manually enter transaction data or customer information in both systems, which increases the risk of errors and consumes valuable time. This manual duplication can also result in records diverging over time, as updates made in one system may not be reflected in the other. As a result, business decisions could be made using outdated or inconsistent data, impacting reporting accuracy and customer service. If these systems were connected, it could be possible to exchange data such as customer profiles, sales transactions, product information, and analytics. For example, sales data from Izettle could be used to personalize content or offers in Sitecore, while customer engagement data from Sitecore could inform sales strategies or loyalty programs managed through Izettle. The specific data that can be exchanged depends on what each system exposes through its API and must be determined based on the technical capabilities and business needs of each 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 Sitecore and Izettle 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.