By reading this documentation, and with the help of the first assessment of the Wapping Onboarding team, the integrator will have a complete understanding of the relevant APIs that apply to the scenario of the business, the priorities and the path forward to follow.

This article shows and lists the different parts involving an onboarding integration, and explain each one so the user has a clear understanding if this is something required, or applied to their case.

Base integration

The most important piece is the Checkout API, here the mayority of the focus has to be directed, as it's the corner stone of the platform. To put into perspective around 75% of the effort and resources should be directed here.

The complete information about this integration is in the Checkout API Guide.

The next in priority would be the Product API, as it infuses a lot of relevant information that allows the marketing and business teams to make full use of the platform.
This API is not 100% required, as all the products that enter the platform via Checkout will be created the first time, but it is highly recommended.

To integrate it you can refer to the Product API Guide for all the information.

Ecommerce

The ecommerce channel is particular because, although it integrates via the Checkout API same as the POS, a couple more configurations/integrations have to be done in order to provide full functionality to the customer.

This will vary depending on the Ecommerce, if it's one of the supported ones (Salesforce, Shopify, Prestashop, VTEX, Magento) the checkout integration is already provided by Wapping via App, plugin, cartridge, etc, and only a couple configurations have to be made.

In other cases where the ecommerce is not one of them, a full integration has to be made by the team.
This integration will include both the checkout (again, same as POS) and the customer part.

There are three main parts, control of user flows (same as in case 1), integration with Identity API, and embedding the wallet via Iframe.

For the in-deep steps in this case refer to the Custom Ecommerce Guide.

Historic customers or loyalty programs

Wapping supports the transfer of current or old loyalty programs and customers. This is best assessed with the Onboarding Team, and it is part of the first meetings.

Whith this process, the Onboarding Team first understand the current picture, and then offers support on how best to migrate it to the Platform, which services are the best suited.

This process can be divided in two parts, the historic purchases of the customer, and the current benefits that they hold.
Both can be tackled in a direct and extended way:

• Direct: a list of customers with the relevant data will be provided on launch (phone, mail, current benefits and relation with new ones to link, current membership level, historical amount spent, etc)
  This method will allow all the data to transfer, but the customer won't see the historic operations in the feed.
• Extended: the data part would be the same, but two integrations have to be made with the Webhook API and Order API to allow the upload of the historic transactions.
  The extended documentation can be consulted here

Wapping recommends the first option as it's the most straight forward and doesn't require any integration whatsoever. It also prevents any missasignment of orders to customers, remember that in Wapping all customers are validated and the unique identification is guaranteed by default, that is not the case in the majority of historical data around.

It's important to understand that this process does not create customers in the platform, neither joins information silos. One of Wapping cornerstones is the Unique Identity of the customer, this is done via the organic validation of the customers since day one, meanin that the current information will only be used to inject information to an already validated customer.

External customer syncronization

Wapping offers a way to integrate all the relevant customer information via Webhook, to either keep it syncronized with some existing services, or to use externally.

You can use the Integration Guide Webhook API to deep dive into the ins and outs of the API, understand how to set it up and how the information flows from Wapping via the API to the backend.