• US: +1 (716) 989 6531

Demand, Sales and Workload Forecasting Software

Getting started with Lokad Desktop Sales Forecasting

Products » Desktop Sales Forecasting » Here

Getting started with Desktop Sales Forecasting


Image

Install

  1. Install Lokad Desktop Sales Forecasting through the regular Windows installer.
  2. Get a Lokad account (unless you already have one).
  3. Update the settings of Lokad Desktop (a).

(a) More details provided in the following section.

As you can see the install does not require to actually change anything to your current application. Furthermore, Lokad Desktop will not make any change to your database neither during the install, nor afterwards while executing the application.

Updating the settings

There are 3 sections for the Lokad Desktop settings (see the screenshots)
  1. the Lokad connection that indicates which Lokad account should be used (user name / password).
  2. the Forecasting task that defines the type of forecast that is requested (ex: weekly or monthly forecasts).
  3. the Business application that indicates how to connect to your accounting/commerce application to retrieve your sales data.

In order to update those settings, launch the Lokad Desktop Sales Forecasting application and select the select the Settings tab.

1. Lokad connection

  • User name: The Lokad user name is the e-mail address that you have provided when creating your Lokad account.
  • Password: It's the same password that the one used to access your Lokad account.
  • WS URL: Do not change unless you know what you are doing (see the developer guide and the sandbox).

2. Forecasting task

  • Period: The period defines the type of forecast to be delivered (ex: daily, weekly or monthly forecasts).
  • Past periods: Indicates how many periods should be displayed as sales history in the Report panel.
  • Future periods: Indicates how many periods should be displayed as forecasted sales in the Report panel.
  • Max tasks: Maximal number of forecasting tasks. Lokad is priced by the forecasting task. Basically, each product in your catalog has its own sales history, and potentially its own forecasting task. Yet, some products may not be worth to be forecasted due to their low sales activities. The max tasks indicates that only the top N most active products will be forecasted; thus, avoiding the merchant to get charged for less than useful forecasts.
  • Period start: The date used as a reference to define the period boundaries. The default value is Monday, Jan 1st, 2001. Thus, if you choose weekly forecasts (resp. monthly forecasts), all the periods will start on Mondays (resp. the 1st day of the month). The period start could be changed if you want to adjust the definition of the periods to your business needs.

3. Business application

  • Application: Indicates the commerce application where the sales data will be retrieved from. See section below for more details.
  • Connection string: The connection string used to connect to your commerce application database. connectionstrings.com is a directory listing the connection string syntaxes for all major database systems.
  • Application option: Some commerce applications need additional settings. This field can be left empty.

Supported commerce applications

The setting named application indicates the commerce application where the sales data will be retrieved. The supported commerce applications are listed below.

Applications (1)Sample connection string
AdempiereProvider=msdaora;Data Source=MyOracleDB;User Id=myId;Password=myPwd; (Oracle)
AspDotNetStoreFrontDriver={SQL Native Client};Server=myServer;Database=myDB;Uid=myId;Pwd=myPwd; (SQL Server 2005)
dashCommerce (previously named Commerce Starter Kit)Driver={SQL Native Client};Server=myServer;Database=myDB;Uid=myId;Pwd=myPwd; (SQL Server 2005)
Dynacom under Accesscheck the Dynacom instructions
Dynacom under SQL Servercheck the Dynacom instructions
CRE Loaded (use osCommerce)see osCommerce
CubeCartServer=myServer;Database=myDB;Uid=myId;Pwd=myPwd;
.netCARTDriver={SQL Native Client};Server=myServer;Database=myDB;Uid=myId;Pwd=myPwd; (SQL Server 2005)
MediaChase eCommerce FrameworkDriver={SQL Native Client};Server=myServer;Database=myDB;Uid=myId;Pwd=myPwd; (SQL Server 2005)
Microsoft Dynamics POS (use MS RMS)Driver={SQL Native Client};Server=myServer;Database=myDB;Uid=myId;Pwd=myPwd; (SQL Server 2005)
Microsoft Dynamics RMSDriver={SQL Native Client};Server=myServer;Database=myDB;Uid=myId;Pwd=myPwd; (SQL Server 2005)
Microsoft ExcelC:\MyDocs\Sample.xls?Sheet1$A1
See also sample spreadsheet, and tutorial.
Microsoft Office AccountingData Source=HOME\MSSMLBIZ;Initial Catalog=myCompany;Integrated Security=true (SQL Server 2005)
Neogia under MySQL (use OfBiz)see OfBiz
Negia under PostgreSql (use OfBiz)see OfBiz
Apache OfBiz under MySQLServer=myServer;Database=myDB;Uid=myId;Pwd=myPwd;
Apache OfBiz under PostgreSqlServer=127.0.0.1;Port=5432;User Id=ofbiz;Password=ofbiz;Database=ofbiz;
OpenTaps under MySQL (use OfBiz)see OfBiz
Openbravo under OracleData Source=erp;User Id=bravo;Password=bravo;
Openbravo under PostgreSQLServer=127.0.0.1;Port=5432;User Id=bravo;Password=bravo;Database=bravo;
OpenTaps under PostgreSql (use OfBiz)see OfBiz
osCommerce check the osCommerce instructions
Paypalcheck the Paypal instructions
QuickBookscheck the QuickBooks instructions
SmileHouse WorkspaceServer=myServer;Database=myDB;Uid=myId;Pwd=myPwd; (MySQL)
TinyERPServer=127.0.0.1;Port=5432;User Id=tinyerp;Password=tinyerp;Database=tinyerp;
VirtueMartServer=myServer;Database=myDB;Uid=myId;Pwd=myPwd;
XSE.NETDriver={SQL Native Client};Server=myServer;Database=myDB;Uid=myId;Pwd=myPwd; (SQL Server 2005)
Zen Cart (use osCommerce)see osCommerce

(1) Some providers are used to support several applications.

Not seeing your favorite application listed here? Just tell us. Your feedback is important for us to prioritize our developments.

Uninstall

  1. Revert back you subscription plan to Free on your Lokad account.
  2. Click on the Uninstall link that has been installed in your Windows Start menu.