VidiStock is not an ERP; it works alongside your ERP. It reads product cards, sales and return transactions, warehouse balances and open purchase orders from your ERP, forecasts demand from them and tells you when and how much to order for every product and warehouse, together with the calculation.

Which ERPs?

ERP How it is read Status
Netsis VidiStock views and procedures in the SQL Server database Beta
Logo Tiger / Go VidiStock views and procedures in the SQL Server database Beta
Mikro VidiStock views and procedures in the SQL Server database Beta
DİA DİA web service (no database access needed) Beta
Others CSV file Always

What beta means: the connections were tested against a test database of each ERP; validation in real customer installations is ongoing. That is why in the first installation we compare last month’s sales and warehouse balances of a few products with your ERP report.

How does it connect?

  1. The VidiStock Connector, a small Windows service, is installed on a computer or server in your network.
  2. For Netsis, Logo and Mikro, a separate vidistock schema with reading objects (views or procedures) is installed in the ERP database; sample scripts are ready and are adapted to the company. The connector gets a SQL user with permission only on this schema; ERP tables are not accessed directly. For DİA, a web service user and API key are entered instead.
  3. On the schedule you choose (for example every night) the connector reads the data and sends it to VidiStock over HTTPS. The connector always starts the connection; no inbound port is opened in the firewall.
  4. Each synchronisation re-reads the transactions of the last days, so documents corrected later in the ERP are also reflected in VidiStock.

If you install VidiStock on your own server, data never leaves your network; the connector sends it to VidiStock on the same network.

Which data is read?

Data Used for
Product card: code, name, unit, group, preferred supplier, cost Plan, stock value, ABC class
Sales and return transactions (day, warehouse, customer) Demand forecast, customer concentration
Warehouse balances Stock position, days of cover
Open purchase orders (with currency) Stock position, FX risk
Stock card fields you select Product attributes (filters such as brand or sales channel)

The currency of an order in VidiStock is the one in the ERP. The ERP’s currency type number is matched with the currency sequence number in VidiStock; Turkish lira is always 0.

What do you see after connecting?

  • Demand forecast for every product and warehouse and the forecast’s past error (WAPE).
  • Safety stock, reorder point and order suggestion; a step-by-step calculation for every suggestion.
  • Alerts for stock-out risk, overstock, lead time drift and FX risk.
  • Capital tied up in stock, turnover, ABC/XYZ classes.

How the calculations work is described on the Methods and accuracy page.