question

shoaib-bagwan avatar image
shoaib-bagwan asked geopme answered

Is it possible for a business with multiple locations (POSs) using the same MID, and utilising the central storage?

If a business has multiple locations (POSs) using the same Clover account and merchant ID, and the Clover eCommerce API is being used, is it possible to:

  1. Store the API authentication token centrally and access it from all locations?
  2. Store customer data with Clover and access it from all locations?

In this scenario, when customers place an order at a location, their information is stored on file. However, if they place an order at a different location, they currently have to provide their information again. From the customer's perspective, they are ordering from the same business and shouldn't have to repeatedly enter their information for each location.

clover developer community
10 |2000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

2 Answers

·
bryanvargas avatar image
bryanvargas answered

So if all of the Clover devices are on ONE merchant ID all information will be synced across the devices and you can access the data from an API call.

Ie, using /v3/merchants/{mId}/customers doesn't matter how many devices they have, all information will be pulled from that mId.

We recommend storing the authentication token in backend servers, which are the safest, to prevent the token from being obtained by others.

10 |2000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

geopme avatar image
geopme answered

Hello Shoaib Bhagwan!


In the scenario you described, where a company operates multiple locations with the same Clover account and merchant ID, it is indeed possible to provide centralized storage and access to critical data such as API authentication tokens and customer information.


Centralized API Authentication Token: Yes, the API Authentication Token can be stored centrally and accessed from all locations. By implementing a centralized token management system, you can simplify token access across all POS points, ensuring secure and efficient authentication for all API transactions.


Centralized storage of customer data. Similarly, you can centralize the storage of customer data using Clover and ensure access from all locations. By leveraging Clover's robust data management capabilities and seamlessly integrating them into your POS systems, you can provide customers with a unified experience, eliminating the need for them to repeatedly enter their information in different places.


By addressing these key aspects of centralization, you can increase operational efficiency, improve the customer experience, and streamline business processes across multiple locations.


For more information on optimizing your business operations and implementing effective management strategies, I recommend checking out this in-depth guide to implementing OKRs in JIRA: jira okr. He offers practical tips and practical advice for beginners who want to achieve success through structured goal setting methodologies.


Feel free to explore the guide to gain valuable information tailored to your business needs!

10 |2000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Welcome to the
Clover Developer Community