Lokad can be seen as an add-on for TradeGecko. We deliver advance inventory forecasting, commerce analytics and pricing optimization. Lokad is an app, like TradeGecko, with a monthly subscription. TradeGecko-powered merchants typically get started with Lokad 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, optimizing inventory tends to be inherently complex.

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

TradeGecko credentials    TradeGecko concepts vs Lokad concepts    Setup of the inventory settings    Data retrieved from TradeGecko       Lokad_Items.tsv       Lokad_Orders.tsv       Lokad_PurchaseOrders.tsv       Lokad_Prices.tsv

TradeGecko credentials

In order to import your TradeGecko 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, TradeGecko being one of them. In particular, this wizard page will redirect you to a webpage within your TradeGecko account that displays an API token. You will be expected to copy-paste this token into the Lokad setup page. Once this token is entered within your Lokad account, Lokad gains the capability to import all your TradeGecko data.

Two remarks:

• our data retrieval logic is read-only. Your TradeGecko data will not be modified in any way by Lokad. In the future, if Lokad were to add write capabilities for TradeGecko, we will make it very explicit whenever your are about to change anything within TradeGecko.
• 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 drop us a message.
  

TradeGecko concepts vs Lokad concepts

TradeGecko offers the notion of variant which represents the multiple declinations of a product. Each variant can be stored in one or more locations. Lokad has the concept of inventory items where items can be used to reflect SKUs, barcodes or products depending on the situation. In the case of TradeGecko, Lokad performs its analysis for each variant.

Note: it is possible that we change this behavior in the future to retrieve have one Lokad item associated to each pair of Location + Variant , instead of ignoring the locations.

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 TradeGecko does not support yet the possibility to create custom properties for variants, thus, Lokad cannot retrieve this information from TradeGecko. 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 variant level.

Data retrieved from TradeGecko

Lokad retrieves extensive data from TradeGecko which include:

• All variants with the stock on hand, the stock on order, the retail price, the cost price.
• The sales order history with the quantity, the unit price, the tax rate, the client.
• The purchase order history with the quantity, the unit price, the delivery date, the supplier, the status.
• The variant composition details with the parent variant and the children variants part of the composite.
• The price lists with the variant, the price and the name of the price list.
  

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

The documentation below adopts the TradeGecko terminology. Ex: variant refer to the variant object within TradeGecko.

Lokad_Items.tsv

The file Lokad_Items.tsv contains the columns:

• Id: the variant ID
• Name: the product name
• Variant: the variant options
• Sku: the variant SKU
• Category: the product type
• Brand: the product brand
• StockOnHand: the variant stock on hand
• StockOnOrder: the variant stock on order
• StockAvailable the stock available
• CurrrentReorderPoint: the reorder point for the variant
• Supplier: the supplier
• SellPrice: the default selling price
• BuyPrice: the default buying price
• SupplierLeadTime: extrapolated from the purchase orders.
• OrderingLeadTime: extrapolated from the purchase orders.
• LeadTime: extrapolated from the purchase orders.
• IsForecasted: true if the variant is flagged as managed.
  

Lokad_Orders.tsv

The file Lokad_Orders.tsv contains the columns:

• Id: the variant ID of the order line
• Date: the creation date of the order
• Quantity: the quantity of the order line
• NetAmount: the amount without tax for the line
• TaxAmount: the amount of tax for the line
• Currency: the currency code
• OrderStatus: the status associated to the order
• Client: the client email associated to the order
• OrderId: the ID of the order
  

Lokad retrieves orders with the following statuses: draft,active,finalized,fulfilled,void.

Lokad_PurchaseOrders.tsv

The file Lokad_PurchaseOrders.tsv contains the columns:

• Id: the variant ID of the purchase order line
• Date: the creation date of the purchase order
• DeliveryDate: the reception date of the procurement matching the purchase order
• Quantity: the quantity of the purchase order line
• NetAmount: the amount without tax for the line
• TaxAmount: the amount of tax for the line
• Currency: the currency of the purchase order
• OrderNumber: the number of the purchase order
• OrderStatus: the status of the purchase order
• ProcurementStatus: the procurement status of the purchase order
• Supplier: the name of the supplier
• OrderId: the order number for the line
  

Lokad_Prices.tsv

The file Lokad_Prices.tsv contains the columns:

• Id: the variant ID of the purchase order line
• ListName: the name of the price list
• UnitPrice: the per-unit price
• Currency: the currency code
• IsBuy: boolean flag true or false