Contents

1. What is the warehouse module for?2. The seven concepts you need 2.1 Warehouse jargon ↔ plain language 3. Getting to know the screen 4. Example: 40 chairs to Ankara 5. Step by step: your first transfer order Pick the source warehouse Open [+ New order] and enter target and items Save — the order exists, the goods have not moved When the truck is loaded, press [Ship now]Ankara counts the goods and presses [Receive]If something is missing: partial receipt and shrinkage 6. Counting: confronting the book with reality 7. Replenishment: let the program spot what ran low 8. Special cases: lots, pallets, quarantine, consignment, disposal 9. When the system stops you 10. Daily routine by role 11. Frequently asked questions 12. Glossary 13. Permission gates: who can do what?14. Lot traceability: from document to lot, from lot to customer 14.1 Entering lot and expiry at goods receipt 14.2 The FEFO suggestion on sales and document-traced lot deduction 14.3 The expiry warning strip and the Cockpit tile 14.4 The Lot Reconciliation tab: confronting the ledger with stock 14.5 How a count difference is applied to lots 14.6 Recall: from lot number to customer 15. The scrap warehouse and leaving quarantine 15.1 The Scrap / Reject warehouse type 15.2 Leaving quarantine: the right route and the "no quality decision" warning 17. "Preview target stock" on a new instruction: seeing both warehouses before sending 18. The in-transit badge on the transfer list: how many days, due, late 19. Quarantine is now a warehouse TYPE, not a warehouse name 20. Two approval gates at shipment: negative stock and transfer to scrap 21. The four-eyes rule: automatic replenishment, single manager, single-signature setting 22. Three conveniences: undoing a count slip, slip uniqueness check, lot-tracking flag 16. Warehouse receipt and lot evidence Protecting the owner of consigned goods A warehouse that forbids going negative (chemical store)Plant mapping, goods in transit and e-Kanban

Help › Warehouse Management

Warehouse Module — A Guide from Scratch for Warehouse Staff

This guide is written for someone who has never used warehouse software. You already know how to move goods by hand; what you will learn here is how that movement leaves a trace in the program. Do not memorise — understand why it works this way and the screen explains itself. Read in order.

⏱ How long does it take?

Sections 1–4 (logic + concepts): 15 minutes of reading. Section 5 (your first transfer order): 15 minutes at the screen. After that, raising an order takes one minute.

1. What is the warehouse module for?

Before you open the program, think about this: is the sentence "we have 200 chairs" useful on its own? It is not. A salesperson asks "can I promise these to a customer?" — and of those 200, sixty may sit in the Ankara branch, forty may be on a truck, thirty may be quarantined by quality control and twenty may belong to a customer who left them with us. The number you can actually sell is fifty. That is the whole job of the warehouse module: to break one big number into meaningful parts.

Figure 1 — The warehouse module does not count stock; it separates it. Its job is to keep that separation live.

💡 The module in one sentence

It records where goods are, in what state, and whose they are. A stock figure that cannot answer these three questions is a guess.

2. The seven concepts you need

Everything in this module is built on these seven words. Do not memorise them — see the logic:

🏭

Warehouse

The physical place goods sit in: the main store, the Ankara branch, a subcontractor's shop, even a truck. Each has a Warehouse code, and stock always belongs to one of them.

📍

Location

The address inside a warehouse: aisle A, rack 3, bin 2. The warehouse says which building, the location says where in that building. It exists so you can find things.

🏷️

Lot / batch

A group of the same stock code that came from one batch, with a lot number and an expiry date. When a customer complains, only the lot can answer "which batch did this come from?".

📦

Pallet

A package of items that move together. Shipping a pallet pours all its items into the order without typing them one by one — faster, and you cannot mistype.

🚚

Transfer order

The instruction "this much of this item goes from warehouse A to warehouse B". Note: the order does not move anything; it records the intention. The real movement happens at dispatch and receipt.

🛣️

Transit (on the road)

Goods that have left the source but not yet arrived at the target. Visible in the program, but sellable in neither warehouse. If the truck crashes, the loss shows up here.

⛔

Quarantine

Goods with no quality verdict yet. They sit in the warehouse and appear in counts, but cannot be sold or consumed. They leave quarantine only by a written quality decision with a reason.

2.1 Warehouse jargon ↔ plain language

You will hear these terms from consultants and other systems. Here are the equivalents:

Term you will hear	Equivalent in HNR	What it means
SKU	Stock code	A product's identity number
Bin / slot	Location	Shelf-bin address
Batch / lot	Lot	Group from one batch
FEFO	Earliest expiry first	Ship the soonest-expiring lot first
In-transit	In transit	Left but not arrived
Cycle count	Stock count	Comparing book with reality
Replenishment	Replenishment	Topping up what ran low
Consignment	Consignment	Someone else's goods held by us
Shrinkage	Shrinkage / loss	Lost or damaged goods

3. Getting to know the screen

When you open the Warehouses window you see the warehouse list on the left and ten tabs on the right. Ten looks intimidating, but you will not use them all every day. This three-way split helps:

📷 Actual screen Depository window — tab bar

🗺 What each field does

Figure 2 — In your first week use only Transfers and Stock. The rest will come.

⚠ Why does the warehouse type matter?

The Warehouse type field on the Details tab is not a cosmetic label; it changes behaviour. Types other than normal (Subcontract, Quarantine, Consignment) do not appear in the sales document picker or as a replenishment source. So if you mark a warehouse "Quarantine" by mistake, sales will never see that stock and will tell you "the stock is missing". The answer is in this field, not in the warehouse.

4. Example: 40 chairs to Ankara

Throughout this guide we follow one concrete job. The Ankara branch calls: "send us 40 units of chair SNDLY-01." The main store holds 120. The truck leaves tomorrow. You will see step by step what happens in the program.

Figure 3 — Four states, four buttons. The coloured badge on screen always tells you where on this line you are.

5. Step by step: your first transfer order

We are sending Ankara the 40 chairs they asked for. Sit at the screen and follow along.

Pick the source warehouse

Click the MERKEZ (main) warehouse in the left list, then open the Transfers tab. This tab lists every order leaving from and arriving at this warehouse. Narrow it with the Sent / In transit / Received filters at the top.

💡 Why must I pick a warehouse first?

Because stock belongs to a warehouse. Without one, "40 chairs" means nothing — which 40 chairs?

Open [+ New order] and enter target and items

Press [+ New order] (top right). In the form that opens:

Field	What you enter	Why
Source warehouse	MERKEZ	Where goods leave from — comes from the selected warehouse
Target warehouse	ANKARA	Cannot equal the source — the program blocks it. The source list is limited to the warehouses you are assigned to (all active ones for an administrator); the target list is company-wide — so someone assigned to a single warehouse can still raise an order.
Line: Stock code	SNDLY-01	Type to search; the list shows only items in stock at the source
Line: Quantity	40	At most what is on hand — you cannot exceed it
Vehicle (plate), Driver	34 ABC 123	Optional, but if goods go missing this is your only clue

To send several items, add rows with [Add line]. If you have a pallet, use Load lines from pallet — the pallet contents pour into the lines automatically.

Save — the order exists, the goods have not moved

On [Save] you get the "Transfer order created" message and a new row with the Order badge. At this point the main store still shows 120. This is where beginners are most often surprised: saving is not moving.
When the truck is loaded, press [Ship now]

After the goods are physically loaded, open the order and press [Ship now]. Now the main store drops 120 → 80, 40 units show as In transit and the badge turns amber. Sales may now promise 80 from the main store; Ankara may promise nothing yet.

⚠ Do not press dispatch early

If you press [Ship now] before the goods are on the truck, the program believes stock you are still holding is on the road. It becomes unsellable and shows up as a discrepancy at month-end. The button follows the physical work — it never leads it.
Ankara counts the goods and presses [Receive]

When the truck arrives, the person on duty in Ankara opens the order, counts what came and presses [Receive]. The Received by name is recorded — never leave it blank, because if something is missing this is the answer to "who counted it?". Ankara's stock goes +40, transit clears and the badge turns green: Completed.
If something is missing: partial receipt and shrinkage

You sent 40, 38 arrived; two broke. Do this: enter 38 when receiving — the order stays open as Partial. Then use [Shrinkage] for the remaining two; the program requires a reason ("broken in transport"). The line closes with the gap and the order completes.

💡 Why is a shrinkage reason mandatory?

Because lost goods are an expense and accounting needs it. And if the same route keeps producing losses, reading the reasons lets you say "this driver / this packaging is the problem". Without a reason, that knowledge disappears.

📷 Actual screen Transfer tab — instructions list and status rozenaries

🗺 What each field does

Figure 4 — Once you can read a row, you see the situation without filtering the list.

6. Counting: confronting the book with reality

However carefully you work, the number in the book and the number on the shelf drift apart: things break, get put on the wrong rack, get scanned twice. The Count tab confronts the two. The logic is simple — three columns.

📷 Actual screen Number tab — book, counted, difference

🗺 What each field does

Figure 5 — With no difference the program says "No difference — book matches the count" and cuts no slip.

After the count you can review the slips under Stock slips issued and Past counts. These records are never deleted: when an auditor asks "why did three units vanish last year", this is where the answer lives.

7. Replenishment: let the program spot what ran low

A branch should not have to phone every morning saying "we ran out of this". On the Stock tab you set a minimum and a maximum level per item; the Replenishment tab then lists every item whose available stock fell below the minimum, and [Convert all to orders] turns the whole list into transfer orders at once.

📷 Actual screen Double tab — Pencils below the minimum level

🗺 What each field does

Figure 6 — Replenishment tops up to the maximum, not the minimum; otherwise you would reorder every week.

💡 How do I choose the minimum level?

A simple rule: average daily usage × lead time (days) × 1.5. If goods reach Ankara in 2 days and you sell 6 chairs a day, minimum ≈ 6 × 2 × 1.5 = 18. The formula is not perfect but it beats nothing; after three months check the turnover figures on the Reports tab and adjust.

8. Special cases: lots, pallets, quarantine, consignment, disposal

Case	Where	What you do / what the program demands
Lot tracking	Lots tab	Add lot number and expiry with [Add lot]. When shipping, take the earliest-expiring lot first (FEFO) — do not sit on goods about to spoil.
Pallet shipping	Pallets tab	Tick Load lines from pallet on the order and the pallet contents fill the lines. With no pallet you see (no pallet — enter the lines by hand).
Releasing from quarantine	Stock tab	Release from quarantine by quality decision (minuted) — the program requires a reason. No reason, no release; the block is deliberate.
Consignment goods	Details tab	Set the type to Consignment (customer's goods) and fill the owner account code. Such stock cannot be sold and is separated in value reports — it is not your capital.
Disposal	Stock tab	Minuted disposal — both a reason and a witness name are required. No single person can destroy stock alone; the rule protects you.

9. When the system stops you

When you see a red warning, do not panic: these are deliberate blocks, not faults. The five you will meet most often, with their fixes:

Message	What it really means	Fix
Source and target must differ.	You picked the same warehouse twice	Change the target. Moving within one warehouse is a location change, not a transfer.
not in stock at source — pick from the list.	You typed a code by hand; that warehouse has none	Choose from the dropdown — it already shows only what that warehouse holds.
at most … can be shipped	You asked for more than is on hand	Lower the quantity or replenish that warehouse first. A warehouse never goes negative.
Shrinkage reason (required)	You cannot close a loss without a reason	Write what happened ("broken in transport"). That text later becomes a report.
Enter at least one line (code + positive qty).	An empty or zero-quantity order	Add a line. An empty order cannot answer "what was supposed to go?" later.

10. Daily routine by role

📥

Warehouse operator

Morning: Transfers → In transit filter; see today's arrivals. During the day: count what arrives, [Receive]; load what leaves, [Ship now]. Evening: check Replenishment; convert any red rows into orders.

🧭

Warehouse supervisor

Weekly: any order stuck In transit? (Goods on the road for a week are usually lost goods.) Monthly: run a count, read the adjustment slips. Quarterly: Reports → dead stock and turnover; update min/max levels.

📊

Manager

Watch three numbers: dead stock (money that has not moved in 12 months), turnover (how often stock refreshes) and total shrinkage (the cash value of losses). Those three describe warehouse performance on a single page.

11. Frequently asked questions

I saved the order but stock did not change — is it broken?

No, it is working correctly. An order is an intention. Stock only changes at [Ship now] (leaves the source) and [Receive] (enters the target). That way "typed but not sent" never corrupts stock.

I shipped to the wrong warehouse — can I undo it?

Before dispatch, [Cancel] is enough. After dispatch there is no undo — the goods physically left. The correct path: receive them, then raise a new order in the opposite direction. The record shows two movements, because two movements really happened.

Sales says "no stock" but I can see it with my own eyes.

Four possibilities, check in order: (1) it is quarantined, (2) it is consignment (someone else's), (3) the warehouse type is not normal (subcontract/quarantine warehouses are hidden from the sales picker), (4) it still shows as In transit because nobody received it. All four mean "visible but not sellable".

What if I skip an item during the count?

Nothing — a skipped row never reaches the slip and keeps its book value. The program only processes rows where you entered a quantity. That is why "did not count" differs from "counted zero": if it really is zero, type 0.

Is stock I sent to a subcontractor still mine?

Yes. A subcontractor warehouse is of type Subcontract (outside processing): the goods stay in your capital and appear in value reports, but not in the sales picker — they are not finished yet. When processing ends they come back with a transfer order.

12. Glossary

Türkçe	English	Bahasa Indonesia
Depo	Warehouse	Gudang
Depo kodu	Warehouse code	Kode gudang
Lokasyon	Location / bin	Lokasi
Lot	Lot / batch	Lot
Palet	Pallet	Palet
Transfer talimatı	Transfer order	Perintah transfer
Kaynak depo	Source warehouse	Gudang asal
Hedef depo	Target warehouse	Gudang tujuan
Yolda / Transit	In transit	Transit
Kısmi sevk	Partial dispatch	Pengiriman sebagian
Teslim al	Receive	Terima barang
Fire	Shrinkage / loss	Susut
İmha (tutanaklı)	Disposal (minuted)	Pemusnahan (berita acara)
Sayım	Stock count	Stok opname
Ambar fişi	Stock slip	Slip gudang
İkmal	Replenishment	Pengisian ulang
Karantina	Quarantine	Karantina
Emanet	Consignment	Titipan
Fason	Subcontract	Maklon
Ölü stok	Dead stock	Stok mati
Devir hızı	Turnover rate	Perputaran stok
ABC analizi	ABC analysis	Analisis ABC

13. Permission gates: who can do what?

The program deliberately stops some actions; that is not a fault but a security gate. There are three: Assignment — to raise a transfer order and to dispatch/receive you must be an assigned user of the source or target warehouse (an administrator assigns you on the Staff tab; this is what the "must be assigned" error means). Four-eyes approval — a new order starts in the Order state; only after an administrator clicks Approve can an assigned user dispatch. If you see "waiting for administrator approval", use the Request approval button. Administrator gates — creating/deleting warehouse cards, cancelling orders, writing in-transit loss, undoing counts and disposal belong to the system administrator only. Quarantine decisions (release / REJECT) are written by an administrator or an assigned user of the QUARANTINE warehouse. When a gate stops you, simply ask the right person for approval or assignment.

14. Lot traceability: from document to lot, from lot to customer

A lot (batch) is a group of goods made under the same conditions or arriving in the same shipment. The warehouse module already separated stock by where, in what state and whose; the lot ledger adds one more question: which batch? A food, pharmaceutical, chemical or aerospace store that cannot answer it will fail an audit — because when something goes wrong, "which batch do we recall" has no answer.

💡 The lot ledger does not BLOCK stock, it only TRACES it

This is the most important sentence in this guide. Goods with no lot record are still sold, still transferred, still consumed in production. The lot ledger breaks no document and stops no dispatch. All it does is leave a trail — and the trail is only as complete as the lot numbers you typed.

14.1 Entering lot and expiry at goods receipt

The first row of the lot ledger is written at goods receipt. While entering a purchase invoice, a block titled "Lot / SKT (mal kabul)" opens under the item grid, with this note beneath it: "optional — written to the lot ledger after the document is saved (document no goes in the note); an item left blank enters without a lot". Each filled item gets two fields: Lot no and SKT (expiry date). Once the document has an HNR number the fields lock — lot data is not patched onto an issued document afterwards; that is done by hand on the Warehouses → Lots tab.

⚠ If the lot cannot be written, the document is NOT harmed

Lots are written after the document is saved. On success you see: "3 lots written to the ledger" with the code → lot pairs beneath. If something prevents it, the warning reads: "the lot could not be written — the document record was NOT affected … lots can be entered by hand on Warehouses → Lots." Your invoice is valid either way; you only need to complete the lot trail manually.

ℹ Three details to know

(1) Quantities are converted to the main unit. Even if you entered the item in boxes, the lot ledger stores the stock card's main unit — otherwise lot totals could never match warehouse stock. (2) With no warehouse selected the lot is written as "general", which requires administrator rights; a small (no warehouse) hint appears. Make selecting a warehouse on the document a habit. (3) Lot totals may not exceed warehouse stock. If they do, the program says: "lot total X, warehouse stock Y — check the lot quantity". Usually the cause is the same lot entered twice.

14.2 The FEFO suggestion on sales and document-traced lot deduction

FEFO = First Expired, First Out: the lot with the nearest expiry leaves first. It differs from FIFO (first in, first out) because goods do not arrive in expiry order — yesterday's batch may expire sooner than one received two months ago. For perishables, FEFO is the correct rule.

On screen: while entering a sales invoice, a block titled "Lot (FEFO önerisi)" (FEFO suggestion) opens under the item grid for items that have lot records. Its note: "on save, the lots with the nearest expiry are deducted automatically (the document number is traced) — expired lots do not enter the automatic pass". For each code the first five lots appear as small pills in three colours:

Pill	Meaning
Red, prefixed ⚠	Expired. Automatic FEFO skips it; to consume it deliberately, reduce it by hand on Warehouses → Lots.
Green, ending `→ −qty`	This lot will be drawn from — a suggestion. On save it really is deducted.
Grey	The next lot in line — untouched because the quantity was already covered.
Amber text: "lots do not cover: …"	Lot totals do not cover the line quantity. The remainder leaves without a lot trail and shows up in the Lot Reconciliation report.

On save the deduction really happens on the server and a notification titled "Lot izleme (FEFO)" appears. It may contain: lots deducted: CODE/LOT×12.00 …, lots did not cover: CODE (3.00) …, expired lots did not enter FEFO: CODE/LOT …. It always ends with the same reminder: "— trail: Quality → Tracing (by lot no)". The ordering rule is: nearest expiry first, lots with no expiry last, ties broken by the oldest record.

💡 A lot expiring today is still valid

The rule is: a lot is valid while expiry ≥ today; the red warning appears only when expiry < today. So a lot dated today is neither shown red nor skipped by FEFO. The date is computed against your machine's local day — there is no time-zone drift.

14.3 The expiry warning strip and the Cockpit tile

At the very top of the Warehouses window, above the warehouse list, sits a strip: "SKT Uyarıları" (expiry warnings). It carries two pills: "N lots EXPIRED" (red) and "N lots ≤30 days" (amber). The counts cover all warehouses. The strip is hidden entirely when both counts are zero — it does not clutter the screen for nothing. Clicking a pill switches to the Lotlar tab with the matching filter applied.

The same figure also sits as a small tile in the Production panel of the Cockpit: titled "SKT (lotlar)" with the value "X expired · Y ≤30 days". The tile is red if anything has expired, neutral if only approaching, green when both are zero. Clicking it opens the Warehouses window. A manager can thus see "what is about to spoil" without entering the warehouse at all.

ℹ The filter on the Lots tab

The Lots tab filters by the selected warehouse (while the strip counts all warehouses — the two numbers may differ, and that is normal). The filter offers four choices: all lots, expired, expiring within 30 days, within 90 days. In the list the expiry cell turns bold red only for already expired lots. From this tab you may add a lot by hand (code · lot no · expiry · quantity · notes) or delete a row with the ×.

14.4 The Lot Reconciliation tab: confronting the ledger with stock

Because the lot ledger never blocks stock, the two can drift apart: documents issued without lots, hand-entered lots, quantities FEFO could not cover… The Lot Mutabakat (lot reconciliation) tab finds that gap. Its job is simple: for every code+warehouse that has lot records, it compares the lot total against the warehouse stock and lists only the mismatches. Matching rows never appear.

Column	What it shows
Kod · Açıklama · Depo	The item and warehouse where the gap is.
Lot toplamı	The sum of the lot ledger quantities for that code+warehouse.
Depo mevcudu	The actual on-hand figure in the stock ledger.
Fark	Lot total − warehouse stock. Amber when positive, red when negative.
Yön	"lot ledger over — a count is advised" or "lot ledger short — a count is advised".

When nothing differs, a green line appears instead of the list: "the lot ledger agrees with stock — no difference." Double-clicking a row opens that item's stock card. ↻ Tazele (refresh) rebuilds the report. Closing a gap takes two steps: first a physical count (the Sayım tab) to establish the truth, then bringing the lot ledger into line with that truth by hand.

14.5 How a count difference is applied to lots

When you cut a count slip the program also considers the lot ledger — but in one direction only.

Difference	What happens to the lot ledger?
Negative (count below book)	The difference is drained from the lots in FEFO order — nearest expiry first. Here expired lots are consumed (unlike on sales), because this is loss, not a sale. The trail is written with source `sayim` and the count slip number.
Positive (count above book)	Nothing is written to the lot ledger — because which lot the surplus belongs to cannot be known. The server produces this warning: "no lot assignment was made for a positive count difference (the lot cannot be known): … — correct the lot records by hand". After the count, check the Lot Reconciliation tab and add the missing lot manually.

⚠ Undoing a count does not restore lots

Undoing a count slip (an administrator action) reverts the stock ledger but does not touch the lot ledger. That shows up in Lot Reconciliation as a "lot ledger short" row. After an undo, check reconciliation and top the lot up by hand.

14.6 Recall: from lot number to customer

All this bookkeeping exists for one moment: a batch turns out to be faulty and someone asks "who received it?" The answer comes from Quality window → Tracing: type the lot number and press [İzle]. Every movement of that lot number is listed — receipt, issue, transfer, quarantine release, disposal, count difference, production consumption, subcontract — and rows that left on a sales document are matched to the invoice and the customer. A summary strip sits above the list: "documents/customers this lot went to: Document #128 → ABC Foods Ltd · …"

🚫 Goods that leave without a document have no trail

Only rows that left on a sales document resolve to a customer. If goods left the warehouse by hand (a manual lot reduction, an undocumented delivery) the row appears in the trail but the "who received it" column stays empty. That is why the real precondition of traceability is selling through documents. The second condition is entering the lot number: with no number there is nothing to search for.

15. The scrap warehouse and leaving quarantine

Goods waiting in quarantine have two exits: accept (usable, to a normal warehouse) and REJECT (nonconforming, to be set aside). The right destination of a REJECT is a warehouse of type scrap/reject.

15.1 The Scrap / Reject warehouse type

The warehouse type field on the warehouse card offers five choices: Normal, Subcontract, Quarantine (quality), Transit and Scrap / Reject. Only an administrator may change it. The scrap type has a single but very important effect: it never appears in the sales document's warehouse picker. Rejected goods therefore cannot be sold even by accident. (The same protection applies to transit and consignment warehouses.)

⚠ "Target warehouse warning"

If you decide REJECT and send the goods to a warehouse of type normal, the program raises: "rejected goods are going to the SELLABLE (normal) warehouse '…' — a scrap/reject type warehouse is advised (Warehouses → Info → Warehouse type: Hurda)." It does not block — a small business may not have a separate scrap store. But on the day you first see this warning, spend five minutes creating a HURDA warehouse; from then on the chance of accidentally selling rejected goods drops to zero.

15.2 Leaving quarantine: the right route and the "no quality decision" warning

The only proper way out of quarantine is Warehouses → QUARANTINE → Release. That flow asks four things in turn — quantity, decision (accept/reject), target warehouse and a reason — all four mandatory. Two warehouse slips are cut, a release report is written, and the lot information is carried to the target warehouse (lot no + expiry preserved, the trail unbroken).

⚠ "Missing quality decision"

If you take a short cut and dispatch with a transfer order whose source is QUARANTINE, the program completes the dispatch but raises: "dispatch from QUARANTINE: no quality decision (release report) was written for these codes: … — the correct route is Warehouses → QUARANTINE → Release; the dispatch remains valid with administrator approval." Your dispatch is not cancelled; but for those goods there is no recorded answer to "who released them, on what grounds". That is precisely what an auditor asks.

17. "Preview target stock" on a new instruction: seeing both warehouses before sending

In the "[+ New instruction]" form of section 5, next to "Open instruction" there is Preview target stock. Pressing it writes nothing; a table per line appears: source on hand → after, target on hand → after, the target's min and max levels and warnings. A row is red if the source would go negative, yellow if the target would exceed its max or stay below its min. When you open the instruction the response also carries the same "target stock" table (a snapshot after writing).

Permission: a manager or the keeper of the source/target warehouse (same as the transfer scope; outside it 403). If the source is empty the preview says "source goes negative" — information, not a block; the negative-stock gate is still asked at shipment (section 20).

18. The in-transit badge on the transfer list: how many days, due, late

A shipped-but-not-received instruction row shows the badge 🚚 N days in transit · due YYYY-MM-DD; once the due date has passed the badge turns red "LATE". Calculation: shipment day = the day of the first shipment record, days in transit = today − shipment day (calendar days), due = shipment day + N. N defaults to 3 and is set company-wide (TRANSFER_TERMIN_GUN; you can also request the list temporarily with another value via ?terminGun=). Rows still at instruction stage or already completed have no badge. The due date is not stored in the database — it is derived from the shipment day; a per-instruction due date would need a separate field.

19. Quarantine is now a warehouse TYPE, not a warehouse name

The quarantine flow of section 15.2 used to depend on a single warehouse named exactly "KARANTINA"; a plant that opened a second quarantine warehouse such as "CN-KRNT" never saw the quality gate. The rule is now type = quarantine: every warehouse of that type is a quarantine (the old "KARANTINA" name is still recognised for compatibility). Consequences:

Quality permission = system administrator or keeper of a quarantine-type warehouse. Quality decisions, release, disposal, NCR decisions and clean-room decisions pass through this gate. The "my quality warehouses" list appears in the Quality window's context.
The Release button exists on the Stock tab of every quarantine-type warehouse; the form sends the source warehouse itself. If no source is given via the API, the program picks the single quarantine warehouse of the user's that holds this code; with none or several it lists them with 422 ("specify the source: A, B") — no silent choice. The target cannot be quarantine-type.
The "shipping from a quarantine warehouse: no quality decision written" warning at shipment and RMA now works for every quarantine-type warehouse and names the warehouse. The quality decisions list shows the real source warehouse.

If you get 403: the message names the warehouse type and the assignment — either the warehouse is not quarantine-type (Warehouses › warehouse card › type) or you are not its keeper (Warehouses › Keepers). A manager fixes both.

20. Two approval gates at shipment: negative stock and transfer to scrap

Message	Reason and escape
"insufficient stock … resend with eksiStokOnay" (422)	The source warehouse holds less than the shipped quantity. The program shows the approval question; if you say yes the shipment is written as "partial", the note gets the trace "[eksiStokOnay: code (on hand X, shipped Y)]" and the source goes negative. This flag once failed to reach the server, so 422 persisted even after approval — fixed.
"target is a scrap warehouse — no way back … hurdaOnay" (422)	The target warehouse is of type scrap and the source is not. Because scrap-to-normal is closed (section 15.1) this transfer cannot be undone; the program asks "NO WAY BACK", and if you say yes the notes get "[TRANSFER TO SCRAP approved: name]" and the response carries a warning.

21. The four-eyes rule: automatic replenishment, single manager, single-signature setting

Whoever opens an instruction cannot approve it (DORT_GOZ_ZORUNLU); the approver is a system administrator. This rule permanently locked the "Replenish › all" instructions of section 7 in a single-manager company. Three exceptions were defined:

Automation: instructions opened by "Replenish › all" are flagged automatic; the opener counts as "the program", so the manager who ran the replenishment may approve. Trace: "[approval: automatic replenishment, name]". The rule still applies to instructions you open by hand.
Single-manager company: if no other system administrator exists and that administrator opened the instruction, the registered keeper of the source or target warehouse may give the second signature. Trace: "[four-eyes: single manager, keeper second signature name]". With several managers a keeper gets 403.
Single-signature setting (depo.dort_goz_tek_imza, off by default): if a manager switches it on, the lone manager may also approve his own instruction; trace "[TEK_IMZA …]" plus a separate Audit-trail row. With another manager present the setting is not applied. See the Security guide.

The list now carries an approvable flag and its reason on every row (your-own-instruction, automatic-replenishment, not-a-manager, status-…); the Approve button is disabled on your own instruction and shows the explanation. The "Replenish › all" response states the single/multiple-manager situation immediately.

22. Three conveniences: undoing a count slip, slip uniqueness check, lot-tracking flag

Whoever opened a count slip may delete it. The count slip of section 6 could only be deleted by a manager. Now a non-manager keeper may "Undo" if they opened the slip themselves, it is today's slip and they are the warehouse's keeper; otherwise 403, and the message says who opened it and on which day. Backup and lot return are done as before.

Slip uniqueness check (manager; GET /api/depolar/fis-denetim): scans whether the same warehouse slip number was used on two documents, lists conflicting slips with their lines and records, and shows counter ceilings and the next slip number. Because simultaneous release/disposal/scrap slips now take their number inside the lock, the normal result is "conflicts 0"; if you see anything else, tell your administrator.

Lot-tracking flag and automatic lot on purchase: "lot tracking yes/no" can be written explicitly for a stock card (PUT /api/depolar/lot-takip/<code>; a manager or any warehouse keeper). When a tracked card is received on a purchase invoice the lot opens by itself (manual entry from section 14.1 still applies; a given lot/expiry takes precedence) and is rolled back when the invoice is deleted. Pattern and rules: Corporate guide. Stock reconciliation (section 14.4) was reduced to a single query and is cached for 60 seconds — Refresh forces a fresh calculation. Keeper assignment: if the user you assign to a warehouse has the warehouse permissions off, the assignment is still written but the response warns and suggests a template (see the Settings guide).

🔗 Related guides

If the goods feed production see the Production guide; if they go to a customer see the CRM guide. For the quarantine decisions and the lot trail themselves see the Quality window guide.

16. Warehouse receipt and lot evidence

Attach certificates, CoC/CoA, inspection report, and delivery note to a lot; warehouse receipt, proof of delivery, delivery note, and where needed photos to pallets/transfers; and count/receipt documents, inspection reports, or photos to stock counts. Document number, sender/recipient, date, vehicle/plate, and lot/serial must describe the same shipment.

Do not delete an attachment from a received transfer. Cancel the wrong file with a reason and upload the correct delivery proof as a new attachment. Field guide: Practical User Handbook.

Protecting the owner of consigned goods

In Warehouses → warehouse card, choosing Customer-owned requires a registered Owner account code. Blank or unknown accounts are rejected. You may correct the owner of an unused empty warehouse. Once stock, lots or movement history exists, ownership is locked: this field cannot turn the goods into another customer's or company property. A zero current balance does not erase history. Create a separate warehouse for another owner. Address, description and contact details remain editable. This basic protection adds no industry certificate requirement to Level 1.

Consignment transfer

In Transfers → New instruction, a customer-owned source offers only destinations with the same owner. You can ship 10 M from customer warehouse A to B, then receive 4 M and 6 M. Company or other-customer destinations are rejected even for administrators; a warehouse transfer is not a title transfer. An open instruction locks ownership changes on an empty destination too. Cancelling an unused instruction releases that lock only if no other stock, history or open instruction exists. Shipment and receipt recheck ownership. Lot/serial columns appear only when used. Historical lot separation in the shared YOLDA warehouse is outside this check.

Consignment — our goods left with a customer on a "pay if you sell it" basis, or supplier goods held by us on an "invoice as you use it" basis — has its own window: for agreements, the consignment warehouse (KNS-…), shipment/receipt, invoicing from a consumption report, returns, counts and period reconciliation see Consignment / Custody.

Transfer lots and safe receipt

Open a transfer and expand “Transfer lot movements” when available. Check stock, warehouse, lot, expiry, direction and quantity. If two customers have the same product in transit, each transfer receives only its own shipped lot, not the other customer's earlier-expiring lot. A failed lot/serial step rolls back the stock document, counters and trace records. Refresh and check lot quantity and quality status; do not create a compensating stock document assuming the failed movement posted. Old transfers with missing trace records require stock/lot reconciliation, not automatic guessing. Split a pallet before moving only part of it. These checks do not introduce mandatory lot tracking or certificates at Level 1.

A warehouse that forbids going negative (chemical store)

While Forbid going negative is ticked on the warehouse card, stock in that warehouse cannot go below zero: neither a production confirmation nor a sale can pass with negative-stock approval; the error starts with EKSI_YASAK_DEPO and states the remedy (record the receipt first). This gate deliberately has no visible escape — in a chemical or dye store there is no physical state called "minus 40 kg"; a negative balance there means an unweighed receipt, and a bath recipe computed from it is ruined from the start. A gate that can be approved away would make the operator approve exactly the mistake the system exists to catch; the decision belongs to the administrator on the warehouse card. It is off by default; existing warehouses are unaffected. Details: Textile guide.

Plant mapping, goods in transit and e-Kanban

In a business with several factories every warehouse is mapped to a plant (Corporate › Plant / Warehouse). The mapping is used not only for the security wall but for planning: plant-scoped MRP and plant kanban see only warehouses mapped to a plant. The band at the top of the screen states how many warehouses are still unmapped and lets you attach them to one plant with a multi-select. Details: Automotive guide, section 13.

Goods in transit. The replenishment screen counts goods on open transfer orders (order/approved/partial) that have not yet been received as “in transit”, and therefore does not raise a second order for the same shortage. MRP did not count them; the two screens reported different shortages for the same item and the gap was enough to open duplicate purchase orders. With the depo.mrp_transit_arz gate on, MRP uses the same figure. The gate is off by default: while off the MRP answer is exactly what it is today, and switching it on is a deliberate decision because planning numbers change.

e-Kanban. For a frequently consumed item you define the source and target warehouse, the bin quantity, the daily demand and the transit days; the server computes the card count. The board lists cards whose available stock has fallen below the reorder point, with a Create transfer order button on each row. Triggering goes through the normal transfer order path: four-eyes approval, the plant wall, ownership and scrap gates all still apply. Automatic triggering (depo.kanban_otomatik) and automatic inter-plant approval (depo.kanban_tesis_disi) are separate and both off by default; while the second is off an inter-plant kanban stops with TESIS_TRANSFER_ONAY.

The steps after the delivery note — cartons, vehicle loading, route, carrier and proof of delivery — are in a separate window: Shipping and Logistics.

The daily work inside the warehouse — pick lists for orders and production kits, QR picking on the phone, cycle counting on an ABC schedule with four-eyes variance approval, rack/bin slotting, stock in transit — is in a separate window as well: Warehouse Operations. A count variance there is written with the warehouse count document on this page (section 6).