CSV import

Data is loaded as CSV files on Yönetim → İçe Aktarma (Administration → Import). A template for each data type can be downloaded from that page.

File format

• The delimiter can be a semicolon, comma or tab; it is detected automatically.
• Encoding can be UTF-8 or Windows-1254 (Excel’s Turkish save format).
• Turkish headers (for example Stok Kodu, Tarih, Miktar) and decimal commas (1.250,75) are supported.
• Excel files (.xlsx) cannot be uploaded directly; use Save As → CSV in Excel.

File types

Load products first; the sales, stock and order files find products by their stock code. Suppliers must be defined before purchase orders: with the Suppliers file or by supplierCode in the products file.

Type	Required columns	Optional columns
Products	sku, name	unit, category, supplierCode, supplierName, leadTimeDays, minOrderQty, lotMultiple, shelfLifeDays, unmetDemand, unitCost, unitPrice, costCurrency, priceCurrency
Sales	sku, date, salesQty	warehouse, returnQty, customer, customerName, campaign
Stock	sku, onHand	warehouse, onOrder, date
Suppliers	supplierCode	supplierName, leadTimeDays, contactName, email, phone, address, city, country
Purchase orders	supplierCode, sku, orderDate, promisedDate, orderedQty	orderNo, warehouse, receivedDate, receivedQty, rejectedQty, unitCost, currency, closed
Goods receipts	orderNo, sku, receivedDate, receivedQty	supplierCode, rejectedQty, documentNo
Inter-warehouse transfers	date, sku, fromWarehouse, toWarehouse, qty	documentNo
Campaigns	campaignCode, campaignName, startDate, endDate, sku	warehouse, upliftPct

Good to know

• Warehouse: warehouse is the warehouse code or name. Rows that leave it empty go to the default warehouse.
• Re-uploading: If the same product, warehouse and day are uploaded again, the quantity is replaced, not added. Uploading the same file twice does no harm.
• Campaign sales: a row with K in the campaign column (Turkish header kampanya) is a campaign sale; it is removed from the baseline demand forecast and campaign effects are learned from it (Campaigns). A file without this column leaves earlier marks unchanged.
• Customer: customer is the customer code and is optional. The customer concentration analysis is calculated from this column.
• Stock: The file sets the warehouse balance to the value in the file; the difference is recorded as a stock transaction.
• Suppliers: Existing codes are updated; an empty field (the name too) keeps its current value. leadTimeDays is the supplier’s default lead time. A row with an invalid email is rejected.
• Purchase orders: If receivedDate is empty the order is treated as open; if receivedDate is empty and receivedQty is less than ordered, the line is partly received and the rest shows as pending on the Purchase Orders page. In the closed column enter E (or yes, 1, S as in Netsis) for an order closed in the ERP: a partly received line is closed short, a line closed without any receipt is not imported (and deleted if uploaded before); H or empty means open. A file without the column does not change whether lines are closed. Rows with an orderNo are updated when uploaded again. warehouse is the warehouse that receives the order; it is used to match order suggestions by warehouse, and if empty the order is matched at product level (it is not assigned to the default warehouse). Deliveries are not entered manually in VidiStock; a company without an ERP uploads its orders with this file.
• Transfers: These are completed inter-warehouse transfers; they do not change stock balances and are compared with transfer suggestions. Transfers previously uploaded by file between the earliest and latest date in the file are deleted and rewritten; to correct them, upload that period’s file again. Rows with the same document, product and warehouse pair are added together.
• Campaigns: Rows with the same code form one campaign; the name, dates and rate come from the first row, and a row with a different rate gets its own rate for that product. If warehouse is empty the product is in the campaign in all warehouses. If the same code is uploaded again the campaign is replaced with the file. Details: Campaigns.
• Empty fields: In the products file, an empty field keeps the existing value.
• Unmet demand: In the unmetDemand column write lost sales, backorder, or company to remove the product override and return to the company setting (Turkish values kayıp satış, sonradan karşılanır and firma also work). An unrecognised value marks the row as an error.
• Currency: the costCurrency, priceCurrency and currency columns take a code (USD) or the number on the Settings page (1). If empty, the base currency is used for products and the product’s purchase currency for deliveries. An undefined currency makes the row invalid.
• Product attributes: In the products file, a column whose header matches an attribute’s name or key (e.g. marka, Uyumlu Araç Markası) is read as that attribute’s value; spelling style does not matter. In a multi-value attribute, values are separated by commas (the file delimiter must then be a semicolon). An attribute present in the file is rewritten and an empty cell clears the value; an attribute with no column in the file is left untouched. Undefined columns are ignored.

Rows with errors

Rows with errors are skipped and the rest are loaded. The result screen shows the row number and reason for every skipped row (for example an unknown stock code or an unreadable date).