This article gives you a quick overview and introduction to the different sales integration types that are currently available in SameSystems. The article also helps you to identify what integration clients are using. Last, the article helps you choose the right integration together with a client.

There are currently 3 types of integrations in SameSystem and some of these types have the option to integrate with several different providers.

Whatever integration option a client will use they should only import sales data that is useful for their Workforce Management needs. These data options are available through most integration options and are what should be recommended to clients:

A POS integration is a permanent integration between a POS provider and SameSystem. This allows for easy sharing of data only by enabling a few settings in SameSystem and collecting a few access information (password and API keys) from the client.

Opting for a POS integration is always the best choice as it is the easiest and least time-consuming integration to setup. Before recommending to a client that we should import sales data via their POS system remember to check if we have an integration with their system.

NB: Wishes for new POS integration should be directed to the Head of Sales or head of Customer Success as they decide the priority of new POS systems.

FTP or Email import of CSV files (CAMPR) is simply importing sales data via CSV files by continuously having the client share files with us either through emails or by uploading the CSV to an FTP/SFTP server every day.

Recommending an FTP or email import integration is a good choice for the client if we do not offer an integration with the POS system they use and if the client does not have development resources internally to build their own integration with SameSystem using our API. Before recommending to a client that they should import data this way make sure to check if the client systems can share the needed data and in the right format.

An API is an interface to build applications into one another that allows applications to share information by pushing and pulling it from each other.

Building an API integration is a task handled by the customer's development team. We do not help with the actual integration besides giving them access to the API, configuring the settings in SameSystem, and sharing documentation and best practices.

Recommending an integration is a good choice for the client if we do not offer an integration with their POS system or if the client has some complex needs that our POS integrations and FTP or email import integration can not accommodate.

Before recommending to a client that they should import data this way make sure they understand that it requires development resources on their side and have them include a technical resource in meetings leading up to the decision that can confirm that building an API integration is an option for them. Non-technical stakeholders will not have an understanding of what an API integration requires in terms of competencies, resources, and technical capabilities on the client side. Agreeing on this approach without client-side technical know-how will often set the project up to fail.