This article gives you a quick overview and introduction to the different sales integration types currently available in SameSystems. The article also helps you to identify what integration clients are using. Last, the article enables you to choose the correct integration 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 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 standard 3-party integration between a POS provider and SameSystem. This allows for easy data sharing only by enabling a few settings in SameSystem and collecting a few access information (password and API Token) from the client.

Opting for a POS integration is always the best choice as it is the easiest and least time-consuming integration to set up. Before recommending to a client that we should import sales data from their POS system, remember to check if we already have an integration with their system (list above).

A CSV integration 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 (this is not manual but something the client will do automatically).

Recommending a CSV integration is a good choice for the client if we do not integrate with the POS system. Also, if the client does not have development resources internally to build an integration with the SameSystem API. Before recommending to a client that they should import data, check if the client can share the needed data in the correct format.

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

Building an API integration is 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 API documentation and best practices.

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

Before recommending to a client that they should import data using the API, make sure they understand that it requires development resources 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 understand what an API integration requires regarding competencies, resources, and technical capabilities on the client-side. Agreeing on this approach without client-side tech know-how will often set the project up to fail.