Integrations on websites and webstores.


Integration means the connection between two systems through which information flows from one system to another. Sometimes only in the other direction, sometimes in both directions. So, the data is exported and imported. The larger the web service, the more often there is a need for integrations. We are highly experienced designers and implementers of various integrations.

The need for integrations arises when you want to make services more effective and make your business more efficient, for example in terms of time management. Manual data transfer is slow, error prone, and labour intensive. An impact perspective on web services can be found in the seamless functionality of services, such as the functionality of purchasing processes when it is directly connected to the business processes of our customer company.

The mere transfer of data from one system to another does not usually meet the needs, but the receiving system must be able to interpret the content of the data and process it according to the needs.

When it comes to websites, integrations are most often related to CRM systems or marketing automation systems, such as:

  • The newsletter subscription information is exported from the website’s subscription form to, for example, MailChimp
  • Information from the contact form or request for quotation form is exported from the website to, for example, Salesforce
  • A contact form or an expert calendar booking view is imported from, for example, HubSpot to the website
  • The login of the extranet on the website is verified, i.e., the login’s personal information is verified, for example, from Azure AD. In this case, the login information is first exported to Azure and information about whether the user’s login ID is valid is imported from Azure.

For e-commerce, the needs for integration are changing and the workload associated with integration is typically increasing. Fortunately, payment integrations today are reasonably easy to implement if you can take advantage of payment service providers like Paytrail or Netaxept.

  • Payment is present in every online store. Paytrail, for example, offers high-quality and convenient integration opportunities. In this case, the information about the user’s purchase is exported from the online store to Paytrail and information about the successful or unsuccessful payment is imported from Paytrail.
  • CRM integrations are also present in the world of e-commerce. For example, from the web service we implemented, donor information is exported to the donor register in Salesforce.
  • The master data for product information is often located elsewhere than in the online store itself. In most cases, product information is maintained in an ERP or PIM system, from which product information is most often imported to an online store.

You need an integration, what to do?

Companies are utilising more and more various systems. When talking about websites and webstores, it is important to identify integrations that are necessary and appropriate from a business perspective. Like many other things in web service renewals, integrations must be planned before implementation:

  • What is the aim of integration?
  • “Mapping” of data moving through integration – what data is exported and where?
  • Interface descriptions of integrated systems
  • Exploring test interface options
  • Access rights


The following is terminology related to integrations. You don’t necessarily need to know or understand them. We know and understand them.

The most common communication protocols

  • Web service is a programming interface. Some servers provide software over the Internet or other Internet-based protocol to software running on other computers.
  • FTP (File Transfer Protocol), on the other hand, is a protocol that allows files to be transferred between two machines regardless of the operating system.
  • SOAP (Simple Object Access Protocol) is a language and protocol that allows a service user to send a command to a service provider and the service provider to send a response.

Web service architecture models for implementing interfaces

  • REST (Representational State Transfer) is an architecture model based on the HTTP protocol for implementing programming interfaces.
  • GRAPHQL is an architecture model based on the HTTP protocol for implementing programming interfaces.

Format of transferable materials

  • JSON (JavaScript Object Notation): An open standard file format for transferring information.
  • XML (Extensible Markup Language): XML is used both as a format for transferring data between systems and as a format for storing documents.

Other important concepts

  • An API is an application programming interface and an abbreviation for an application programming interface. It is a programming interface that allows multiple applications to communicate with each other.
  • JWT (JSON Web Token) is an open standard method for managing access tokens between different software.

We have experience with all of these.

Our integration customers

More about software development

Development process

When we code, in what order do things happen, who is involved in the implementation and what are our sprint guidelines?

Read more

WordPress and WooCommerce

What makes WordPress the most popular publishing system in the world? Why and how do we utilise its potential in almost all of our projects?

Read more

Shall we get to work?

"*" indicates required fields


All information is processed according to privacy policy statement.