1. A merchant can connect with Pongo from your interface
One of the most important aspect of our experience is to enable our respective clients (a.k.a. the merchant) to connect your software with Pongo autonomously.
For that reason, we developed an Oauth2 authentication System that we host on our server and that you can implement to let the merchant configure by themselves the connexion with Pongo.
You only have to implement the authentication system in your backend and provide a button that redirect to our OAuth form from your admin panel.
Giving the merchant autonomy to connect with Pongo is required to ensure the best security and operational efficiency.
2. How to ensure your system locations and Pongo's location are properly synced
The merchant's locations (or stores in Pongo) are used for many features in Pongo. It is mainly used to understand in which location a customer have been and help them to better engage with them.
All orders sent to Pongo requires a loyalty_store_slug. Once the merchant has linked its Pongo account with your system through Oauth, you can retrieve the list of the merchant's location with the GET stores endpoint.
You will need to make sure the right loyalty_store_slug is passed with the POST create order call.
3. Provide guidance to associate Pongo rewards with POS SKUs
In order to know which product should be added in an order when a customer use a reward, each reward has an external_idattribute. This attribue contains all the SKUs separated by a comma , from external systems.
Those SKUs are added directly in the Pongo backoffice by the merchant on each reward. It is therefore important to tell the merchant and Pongo how to retrieve them.
How to manage external ids / SKUs
- Each reward has an SKU field where the merchant can add one or multiple external ids.
- Each SKU/External ID is separated by commas.
- If the merchant add one SKU, it means it is a single product or menu.
If the merchant add multiple SKUs, it is a list of product or menu.
Cautions
- Ensure the customer choosing a reward corresponding to a product with paid option can choose any options. The options should not be offered to the customer and must be paid.
- The external_id field can returns multiple SKUs from multiple partner. So you need to filter the SKUs to retains only the one matching in your system.