Which Logo products are supported?

Logo Tiger and Logo Go. Both use the same database structure, so the connector is the same.

We have several periods. Which one is read?

Transactions are read from all of the firm's periods and stock balances from the latest period, so a long history can be used for forecasting. If the reading objects are installed as procedures, a new period is found automatically; if installed as views, the script is run again when a new period is opened.

How are foreign-currency orders read?

The transaction currency and rate of the order line are read; the local price is divided by the rate to get the foreign price. Logo's currency numbers may differ from VidiStock's (for example euro is 20); you enter the currency sequence numbers in Settings according to Logo.

How mature is the connection?

It is in beta. It was tested against a Logo test database; validation in real customer installations is ongoing.

Inventory planning for Logo Tiger and Logo Go

VidiStock reads item cards, transactions, warehouse balances and purchase orders from the Logo Tiger / Go database read-only and produces demand forecasts and order suggestions.

Logo Tiger and Logo Go keep your item, warehouse and order records. VidiStock forecasts demand from these records and calculates the safety stock, reorder point and order suggestion for every item and warehouse.

Which data is read from Logo?

Data is read from views or procedures installed in a vidistock schema in the Logo database; the connector has no permission on the Logo tables. The sample scripts read the tables below and are adapted during setup to how the company uses Logo. In the table names xxx is the firm number and yy the period number; the firm number is set at the top of the sample script.

Data	Logo table
Item cards, unit	`LG_xxx_ITEMS`, `LG_xxx_UNITSETL`
Sales and return transactions (day, warehouse, account)	`LG_xxx_yy_STLINE` (all periods)
Accounts	`LG_xxx_CLCARD`
Purchase orders and goods receipts (with warehouse, transaction currency and rate)	`LG_xxx_yy_ORFLINE`, `LG_xxx_yy_ORFICHE`, `LG_xxx_yy_STLINE`
Warehouse transfers (warehouse slips; beta)	`LG_xxx_yy_STLINE`, `LG_xxx_yy_STFICHE`
Warehouse balances	`LG_xxx_yy_STINVTOT` (latest period)
Warehouses	`L_CAPIWHOUSE`

Product attributes are extra columns of the products object; the sample script includes SPECODE from the item card.

Setup

In VidiStock, on Administration → Integrations, choose Logo and generate a connector key.
Install the VidiStock Connector on a Windows computer that can reach the Logo database.
Download the sample scripts from the Integrations page and run them in the Logo database: they create the vidistock schema, a SQL user with permission only on that schema, and the reading objects. Set the firm number and the sales source (invoice or delivery note) at the top of the script.
Enter the SQL Server address, the database name and this user; choose a view or a procedure for each data type, then test the connection.
Set the history start and the warehouse mapping. Do not map scrap and loss warehouses.
Choose the schedule and enable it.

What is calculated from Logo data?

Demand forecast per item and warehouse and the forecast’s past error.
Safety stock, reorder point and order suggestion for your service level; every suggestion’s calculation is shown step by step.
Transfer suggestions between warehouses: balancing an item that is in surplus in one warehouse and short in another without a new order.
FX risk: the effect of exchange-rate changes on your margin for items bought in foreign currency.

Good to know

The connection is in beta; after the first synchronisation, compare the sales and warehouse balance of a few items with your Logo report.
Item card prices are read in local currency in this version. Set the currency of items bought in foreign currency on the VidiStock product card or by CSV.
VidiStock does not transfer orders to Logo; you export the suggestion to Excel and create the order in Logo.

Detailed setup: ERP integration.