Analytics and Inventory Forecasting for Clover

Analytics and Inventory Forecasting for Clover

Home » Integrations » Here

Lokad can be seen as an add-on for Clover. We deliver advance inventory forecasting, commerce analytics and pricing optimization. Lokad is an app, like Clover, with a monthly subscription. Clover-powered merchants typically get started with Lokad either to consolidate analytics from multiple Clover accounts (franchise) or to optimize their inventory, that is, increase service levels while reducing inventory levels in the same time. Don't hesitate to request a free demo; while we strive to make Lokad as simple as possible, franchise analytics and inventory optimization tend to be inherently complex.

The data from Clover can be imported in just a few clicks into Lokad thanks to a native integration that leverages the Clover API. In this page, we details how to make the most of this native Clover integration.

Clover authorization

In order to import your Clover data into Lokad, you need a Lokad account. If it's not already done, you can get one at no cost in 60s. Then, when you log into your Lokad account for the first time, you will be proposed to establish a connection with multiple data sources, Clover being one of them. In particular, this wizard page will redirect you to a webpage within your Clover account. There, you will need to confirm that you grant a data access to Lokad. Once you've granted the access to Lokad within Clover, you are redirected to Lokad, and now a new option should appear within the connector list. Click this option, and you are done setting-up the link between Clover and Lokad.

Two remarks:
  • our data retrieval logic is read-only. Your Clover data will not be modified in any way by Lokad. In the future, if Lokad were to add write capabilities for Clover, we will make it very explicit whenever your are about to change anything within Clover.
  • your company remains the sole owner of your data. By default, we treat this data as if an NDA was in place between your company and Lokad. If you want an actual NDA to be signed, just .

Franchises (multiple Clover accounts)

Lokad allows a franchise to plug multiple Clover accounts into a single Lokad account. This setup allows to create analytics for the network as a whole, and per outlet too; but this setup also allows the franchises to keep an operational control over their individual Clover accounts. It is also possible to share the Lokad dashboards with franchisees without giving them access to the primary Lokad account.

Once an authorization to access a Clover account is given to Lokad, Lokad remains capable of pulling the data from this account until the authorization is revoked. In practice, this means that the authorization operation has only to be performed once, and not every time the Lokad needs to refresh the data. Also because Lokad is using the app store of Clover to authenticate, the authentication is not lost when Clover user passwords are changed.

As far pricing is concerned, Lokad is charging based on the revenue. We typically use the Clover data itself to figure out in which price range your companies lie. However, many companies (ex: a gym) also sell services through Clover, such as membership subscriptions. When calculating the applicable Lokad fee, we typically exclude the portion of the turnover which not related to commerce activities. However, when multiple Clover accounts are plugged into Lokad, we would look at the total commerce activity summed over all franchisees.

The setup for a Clover franchise can be done swiftly with Lokad, but because every franchise tends to have its own specificities, the setup can be a bit technical. We suggest to to let our staff performs the onboarding on your behalf.

Setup of the inventory settings

The inventory forecasting logic of Lokad requires two settings to be provided, namely the lead times (in days) and the service levels (in percent). At this point of time Clover does not support yet the possibility to create custom properties for products, thus, Lokad cannot retrieve this information from Clover. The inventory forecasting engine offers the possibility to define default values, but this is crude and provides no differentiation among variants.

Thus, Lokad offers an alternative path to manage those settings within your Lokad account. The process consists of creating a settings Excel sheet. This sheet becomes the repository of the inventory settings that should drive your inventory forecasting report. Through this sheet is becomes possible to adjust the inventory settings down to the product level.

Data retrieved from Clover

Lokad retrieves extensive data from Clover which include:
  • All products with the category, the stock on hand, the selling price.
  • The sales order history with the quantity, the net amount, the order status.

Those data are pushed into 3 flat files named Lokad_Items.tsv, Lokad_Orders.tsv and Lokad_Prices.tsv within your Lokad account.


The file Lokad_Items.tsv contains the columns:
  • Id: synthetic identifier that combines Ref and Loc
  • Ref: the SKU code
  • Loc: the merchant name
  • Name: the name of the product
  • Sku: same as Ref
  • Category: the product type
  • StockOnHand: the stock count
  • StockAvailable: same as StockOnHand
  • Supplier: the name of the supplier
  • IsForecasted: boolean at true if the product is not hidden, false otherwise.


The file Lokad_Orders.tsv contains the columns:
  • Id: synthetic identifier that combines Ref and Loc
  • Ref: the SKU code
  • Loc: the merchant name
  • Date: the creation date of the order
  • Quantity: the quantity of the order line
  • NetAmount: the total charged for this order line, tax excluded
  • Currency: the currency associated to the order
  • OrderStatus: the status of the order
  • Channel: constant at default (for now)
  • OrderId: the identifier of the order


The file Lokad_Prices.tsv contains the columns:
  • Id: synthetic identifier that combines Ref and Loc
  • Ref: the SKU code
  • Loc: the merchant name
  • ListName: sellprice or buyprice
  • UnitPrice: the per-unit price
  • Currency: the default merchant currency
  • IsBuy: indicates if buy price or not