Stock transfers
If you have several warehouses, a product in surplus in one may be short in another. The Planlama → Stok Transferleri (Planning → Stock transfers) page spots this and suggests a transfer before you place a new order.
VidiStock does not make transfers: the transfer is made in the ERP (an inter-warehouse transfer or warehouse slip). VidiStock reads completed transfers from the ERP or from a transfers file and compares them with the suggestion. The same transaction is not entered separately in two systems; warehouse stock comes only from the ERP or the stock file.
Suggestions
Section titled “Suggestions”The suggestions tab lists, based on the latest forecast run, possible transfers from warehouses holding stock above their target level to warehouses below their reorder point. The source warehouse is never taken below its own target level. Suggestions are stored with the run; stock values are as of the run.
Each suggestion shows its match in the ERP:
| Status | Meaning |
|---|---|
| Pending | No transfer yet; awaited until the next forecast run. |
| Applied | At least 90% of the suggestion was transferred. |
| Partial | Part of the suggestion was transferred. |
| Not applied | No transfer was made before the next run. |
Matching is by product, source and destination warehouse. A transfer to the same destination from another warehouse also counts, because it covers the destination’s need. Details and past runs: Suggestion compliance.
Transfer or purchase
Section titled “Transfer or purchase”A transfer and a purchase cover the same need. For each suggestion the forecast run calculates three options with the same rules: purchase only, full transfer and partial transfer (the shortfall during the lead time + safety stock; the rest purchased). The option with the lowest total cost is selected:
- transfer cost (fixed + unit × quantity from Settings),
- cost of the purchase plan over the forecast horizon (ordering + holding),
- holding cost of the surplus left at the source warehouse,
- gross margin lost with lost sales (selling price − cost).
If no transfer cost is set, using the source surplus is the default. The selected transfer is deducted from the destination warehouse’s purchase suggestion; Order Suggestions shows Transfer bekleniyor (Transfer expected). A source’s total transfers never exceed its surplus above its own target stock; the surplus is shared among several warehouses.
The suggestion is shown but not deducted from the purchase (the full purchase is suggested) when:
- purchasing is cheaper;
- the suggestion was rejected (30 days);
- the same suggestion was also made in the previous day’s run and has since been neither approved nor carried out in the ERP. Repeat runs on the same day do not count.
Approving and rejecting
Section titled “Approving and rejecting”In the Planlama (Planning) column of the suggestions table you can approve or reject a suggestion (with edit rights). This decision does not change stock or the ERP; it only affects the plan in later forecast runs.
| Decision | Effect | Duration |
|---|---|---|
| Approve | The transfer counts as “in transit” (on order) at the destination and “reserved” at the source; the purchase is calculated accordingly and the same pair is not suggested again. Order Suggestions shows a Transfer onaylı (yolda) (Transfer approved, in transit) badge | Transfer time + 1 day. If at least 90% is transferred in the ERP within this time it becomes “carried out”; otherwise the approval lapses and the purchase is calculated without the transfer |
| Reject | The suggestion is not deducted from the purchase | 30 days |
Approvals and rejections can be removed with Undo. The daily run does not erase yesterday’s approval; an approval lapses by time. The Approved transfers (in transit) list above the table shows approvals not yet carried out in the ERP, the remaining quantity and the expiry.
Completed transfers
Section titled “Completed transfers”The completed transfers tab shows transfers read from the ERP or a file (date, document number, product, source, destination, quantity). The list is read-only; corrections are made in the ERP and appear after the next sync.
- With an ERP connection: transfers are read together with stock. Each sync re-reads the most recent days, so a document deleted or corrected in the ERP is reflected in VidiStock. Transfers are taken when both warehouses are mapped in the warehouse mapping.
- Without an ERP: upload transfers on the Import page with the inter-warehouse transfers file.
Stock transactions
Section titled “Stock transactions”When the stock file or an ERP sync changes a warehouse balance, the difference is recorded as a transaction. The stock transactions tab shows when, in which warehouse and by how much it changed. Transactions of transfers made inside VidiStock in earlier versions also remain here.