# Shipment planning

> From approved sales order to delivery — open delivery, picking, packing, shipment and carrier, goods issue, transit, proof of delivery and freight settlement.

URL: https://erpdocs.corexlogic.com/en/surecler/sevkiyat-planlama

How do the goods of approved sales orders leave the warehouse, get loaded onto a vehicle and reach the customer?
This guide walks end to end through a shipment that sends two sales orders to Ankara on the same carrier trip.
The sales order itself and the single-step delivery are covered in the [Quotation to invoice](https://erpdocs.corexlogic.com/en/surecler/tekliften-faturaya)
guide; the screens are detailed in the [Logistics](https://erpdocs.corexlogic.com/en/lojistik/) section.

> **Scenario**
On 02.11.2026 **CoreX Demo Endüstri** (Istanbul, Ümraniye) sends the approved sales orders of two of its
customers in Ankara with the same vehicle:

- **SS-2026-000007** — Başkent Mimarlık ve İç Mimari Ltd. Şti. (M-0015): 2 units of MAM-0005 DOSYA DOLABI
  80X40X200 BEYAZ, 1 unit of MAM-0004 TOPLANTI MASASI 240X120 CEVİZ.
- **SS-2026-000008** — Güneş Enerji Sistemleri Mühendislik A.Ş. (M-0006): 2 units of MAM-0002 AYDINLATMA
  DAĞITIM PANOSU 12 GRUP.

The goods are in bin RAF-M1 of **MAMUL — Mamul Deposu** (Finished Goods Warehouse). Transport is carried out by
the carrier **Hızlı Hat Nakliyat ve Lojistik Ltd. Şti.** (T-0018); its rate is **HIZLIHAT-2026**: 1.500 TRY per
trip + 12 TRY per km (10 TRY above 500 km). The distance is 450 km. The second customer refuses one of the
panels because it is damaged.

```
SS-2026-000007 ┐                       ┌─ DLG-2026-000001 (wave) ─ DG-…001..003 (picking, Approved)
SS-2026-000008 ┴─► SV-2026-000003 ─────┤
   (Approved)      SV-2026-000004      ├─ TB-2026-000001 · TB-2026-000002 (pallet)
                   (Open → Picked      │
                    → Packed)          └─► TSM-2026-000001 (Planned)
                                              │  Select Carrier → Assign  (freight 6.900,00 TRY)
                         Goods issue ◄────────┤
                  (Goods Issue Posted)         │  Loaded → Dispatch (In Transit)
                                              │  Delivered × 2 → Complete (Completed)
                  Proof of delivery ◄─────────┘
                  (Confirmed; SV-4: 1/2 accepted)
                                              └─► NHS-2026-000001 (Saved, 8.280,00 TRY incl. VAT)
```

## Step-by-step tasks

- [Create an open delivery](https://erpdocs.corexlogic.com/en/satis/islemler/acik-teslimat-olusturma) — Collective delivery from due lines.
  - [Pick a delivery](https://erpdocs.corexlogic.com/en/lojistik/islemler/teslimat-toplama) — Waves and picking tasks.
  - [Pack a delivery](https://erpdocs.corexlogic.com/en/lojistik/islemler/tasima-birimi-olusturma) — Handling unit and label.
  - [Create a shipment document](https://erpdocs.corexlogic.com/en/lojistik/islemler/tasima-belgesi-olusturma) — Trip plan and deliveries.
  - [Select the carrier for a trip](https://erpdocs.corexlogic.com/en/lojistik/islemler/tasiyici-secme) — Ranking, assignment, freight.
  - [Post the goods issue](https://erpdocs.corexlogic.com/en/satis/islemler/mal-cikisi-kaydetme) — Stock is reduced at this step.
  - [Dispatch a trip](https://erpdocs.corexlogic.com/en/lojistik/islemler/seferi-yola-cikarma) — The plan is frozen.
  - [Record a trip event](https://erpdocs.corexlogic.com/en/lojistik/islemler/sefer-olayi-kaydetme) — Loading, delivery, delay.
  - [Complete a trip](https://erpdocs.corexlogic.com/en/lojistik/islemler/seferi-tamamlama) — Arrival and closing.
  - [Record proof of delivery](https://erpdocs.corexlogic.com/en/lojistik/islemler/alindi-teyidi-kaydetme) — Accepted quantity.
  - [Create a freight settlement](https://erpdocs.corexlogic.com/en/lojistik/islemler/navlun-hesaplasmasi-olusturma) — The carrier's freight.

## Preparation: master data

Done once: the carrier profile ([Define a carrier](https://erpdocs.corexlogic.com/en/lojistik/islemler/tasiyici-tanimlama)), the carrier's vehicle
**34DMO002** and driver ([Vehicle](https://erpdocs.corexlogic.com/en/lojistik/islemler/arac-tanimlama),
[Driver](https://erpdocs.corexlogic.com/en/lojistik/islemler/surucu-tanimlama)) and the carrier's rate
([Create a freight agreement](https://erpdocs.corexlogic.com/en/lojistik/islemler/navlun-anlasmasi-olusturma)). Without a carrier rate the trip
can be planned, but the freight cannot be calculated.

## 1. Create open deliveries from due lines

The **Lojistik Yönetimi › Giden Teslimat › Giden Teslimat Oluştur** (Logistics › Outbound Delivery › Create
Outbound Delivery) screen lists the approved sales order lines to be delivered by the **Vadesi gelen (en geç)**
(Due by (latest)) date. Select the three lines (SS-2026-000007/10, /20 and SS-2026-000008/10), select **MAMUL —
Mamul Deposu** as the **Depo** (Warehouse) and click **Teslimat Oluştur** (Create Delivery).

![Create Outbound Delivery — due items](https://erpdocs.corexlogic.com/en/en/img/screens/satis/giden-teslimat-olustur.png)
1. Due by — items to deliver up to this date
2. Select the item to deliver
3. Warehouse
4. Create Delivery — opens an open delivery

The **Sonuç** (Result) field shows two deliveries: **SV-2026-000003 · SS-2026-000007 · 2 kalem** (2 lines) and
**SV-2026-000004 · SS-2026-000008 · 1 kalem** (1 line) — the lines are split into two deliveries because the
recipient and address differ. The deliveries are created as **Açık** (Open): the lines are allocated on the sales
order, but **stock is not reduced yet**. Details: [Create an open delivery](https://erpdocs.corexlogic.com/en/satis/islemler/acik-teslimat-olusturma).

## 2. Pick the goods

In **Stok Yönetimi › Depo Yürütme › Dalgalar › Dalga Oluştur** (Inventory › Warehouse Execution › Waves ›
Create Wave), select **Depo** (Warehouse) MAMUL and **Kaynak** (Source) **Açık teslimatlar** (Open deliveries);
select the three lines and click **Dalgayı Oluştur** (Create Wave).

![Create Wave — picking from open deliveries](https://erpdocs.corexlogic.com/en/en/img/screens/lojistik/dalga-olustur.png)
1. Warehouse — the delivery warehouse
2. Source: Open deliveries
3. Delivery item to pick
4. Create Wave — picking tasks are created

Wave **DLG-2026-000001** is created, with one picking task per line in the RAF-M1 → SEVK direction
(**DG-2026-000001…000003**). The warehouse worker opens each task and saves it with **Onayla** (Confirm); when
all three tasks are confirmed, the wave becomes **Tamamlandı** (Completed).

![Wave detail — picking tasks](https://erpdocs.corexlogic.com/en/en/img/screens/lojistik/dalga-detay.png)
1. The wave completes when all tasks are confirmed
2. The wave line carries the delivery number
3. Picking task — from source bin to SEVK

The picked goods are allocated to the sales order line in the SEVK (shipping) area. The picking status in the
header of both deliveries becomes **Toplandı** (Picked). Details: [Pick a delivery](https://erpdocs.corexlogic.com/en/lojistik/islemler/teslimat-toplama).

## 3. Pack

On each delivery's details, open a pallet with **Taşıma Birimi Oluştur** (Create Handling Unit) on the
**Paketleme** (Packing) card: **Kap Cinsi** (Packaging Type) **Palet (PX)** (Pallet), **Dara (kg)** (Tare
(kg)) 25, **Kalanın Tamamı** (All of the remaining), **Oluştur** (Create). **TB-2026-000001** (total gross
295 kg) is created for SV-2026-000003 and **TB-2026-000002** (97 kg) for SV-2026-000004, and the packing status
becomes **Paketlendi** (Packed). Labels are printed as PDF with **Etiketleri Yazdır** (Print Labels).

![Open delivery — picked and packed](https://erpdocs.corexlogic.com/en/en/img/screens/lojistik/acik-teslimat-paketlendi.png)
1. Picking status
2. Packing status
3. Picked quantity per item
4. New handling unit (carton, pallet…)
5. Handling unit labels (PDF)

Packing is not a precondition for the goods issue; but the pallet tare and the number of pallets go into the
trip's load calculation. Details: [Pack a delivery](https://erpdocs.corexlogic.com/en/lojistik/islemler/tasima-birimi-olusturma).

## 4. Plan the trip

In **Lojistik Yönetimi › Taşıma › Taşıma Belgesi Oluştur** (Logistics › Transportation › Create Shipment
Document), enter **Yürütücü** (Executed By) **Taşıyıcı** (Carrier), **Planlanan Çıkış** (Planned Departure)
02.11.2026 08:00, **Planlanan Varış** (Planned Arrival) 18:00, **Planlanan Mesafe (km)** (Planned Distance (km))
450; add SV-2026-000003 and SV-2026-000004 with **Teslimat Ekle** (Add Delivery) (order: first Başkent Mimarlık,
then Güneş Enerji) and click **Oluştur** (Create).

![Create Transport Document — completed form](https://erpdocs.corexlogic.com/en/en/img/screens/lojistik/tasima-olustur.png)
1. Executor — own fleet or carrier
2. Carrier
3. Planned departure — required
4. Distance — basis for per-km freight
5. Deliveries — order is stop order
6. Create

The trip opens with number **TSM-2026-000001** in **Planlandı** (Planned) status. The **Yük ve Kapasite** (Load
and Capacity) card shows the gross weight (392 kg) and the number of pallets (2); the capacity is shown once a
vehicle is selected. Details: [Create a shipment document](https://erpdocs.corexlogic.com/en/lojistik/islemler/tasima-belgesi-olusturma).

For deliveries without a trip that will be transported with our own vehicles, [Load Planning](https://erpdocs.corexlogic.com/en/lojistik/ekranlar/yuk-planlama)
suggests loads for vehicles.

## 5. Select the carrier and see the freight

On the trip details, the **Taşıyıcı Seç** (Select Carrier) dialog ranks the active carriers by the agreement valid
on the trip's departure day. The Hızlı Hat line shows **HIZLIHAT-2026** and **6.900,00 TRY**; click **Ata**
(Assign).

![Select Carrier dialog — ranking by tariff](https://erpdocs.corexlogic.com/en/en/img/screens/lojistik/tasiyici-sec.png)
1. Ranking: cost or priority
2. Freight from the agreement
3. Assign — carrier is written to the trip
4. Tender with the selected carriers

The header shows the carrier's name, and the **Navlun** (Freight) card shows *Sefer başı 1 sefer × 1.500 =
1.500,00 TRY* (Per trip: 1 trip × 1.500) and *Km başı 450 km × 12 = 5.400,00 TRY* (Per km: 450 km × 12),
**Toplam 6.900,00 TRY** (Total). Then select the carrier's vehicle **34DMO002** and driver with **Düzenle** (Edit);
the load is compared with the capacity (*392 kg / 18.000 kg*, *2 / 18* pallets). If quotations are to be requested
from several carriers, open a tender from the same dialog: [Open a carrier tender](https://erpdocs.corexlogic.com/en/lojistik/islemler/ihale-acma).

If the plan changes later (departure day, distance, deliveries), use **Yeniden Hesapla** (Recalculate) on the
Navlun (Freight) card.

## 6. Post the goods issue

On each delivery's details, open **Mal Çıkışını Kaydet** (Post Goods Issue). Because the delivery has been picked,
the form says *"Teslimat toplandı — toplanan mal dağılımlara yazıldı; gerekirse değiştirebilirsiniz."* (The
delivery has been picked — the picked goods were written to the allocations; you can change them if needed.): the
allocations are filled with the SEVK bin and the SIFIR status. Click **Mal Çıkışını Kaydet**.

![Post Goods Issue — physical allocation](https://erpdocs.corexlogic.com/en/en/img/screens/satis/mal-cikisi.png)
1. Goods issue date — stock is reduced on this date
2. Allocation — location, status, lot or serial
3. Post Goods Issue

Stock is reduced, the deliveries become **Mal Çıkışı Kaydedildi** (Goods Issue Posted) and can no longer change;
packing becomes read-only. The delivery note is printed from the delivery's **Çıktı** (Output) menu (if e-Delivery
Note is enabled in the installation, **e-İrsaliye Oluştur** — Create e-Delivery Note — appears). Details: [Post the
goods issue](https://erpdocs.corexlogic.com/en/satis/islemler/mal-cikisi-kaydetme).

> **Order matters**
A trip cannot be dispatched before the goods issue of its deliveries is posted. In the scenario, when **Yola
Çıkar** (Dispatch) was attempted before the goods issue, the server returned: *"Mal çıkışı kaydedilmemiş ya da
iptal edilmiş teslimatla sefer yola çıkamaz: SV-2026-000003, SV-2026-000004."* (A trip cannot be dispatched with a
delivery whose goods issue has not been posted or that has been cancelled: SV-2026-000003, SV-2026-000004.)

## 7. Load and dispatch

On the trip details, record the **Yüklendi** (Loaded) event with **Olay Kaydet** (Record Event) (**Durak** (Stop)
*Seferin geneli* (Whole trip), **Zaman** (Time) 07:30, **Konum** (Location) "Dudullu OSB — sevk rampası" (Dudullu
OIZ — shipping ramp), **Not** (Note) "2 palet yüklendi" (2 pallets loaded)). Then, in the **Yola Çıkar**
(Dispatch) dialog, enter **Yola çıkış** (Departure) 08:15 and click **Yola Çıkar**.

![Dispatch dialog](https://erpdocs.corexlogic.com/en/en/img/screens/lojistik/yola-cikar.png)
1. Departure time — now if empty
2. Dispatch

The trip becomes **Yolda** (In Transit): the plan and the deliveries are frozen, and the **Olaylar** (Events) card
shows *Yüklendi* (Loaded) and *Yola çıktı* (Dispatched). In Delivery Tracking the deliveries move to the **Yolda**
(In Transit) stage.

![Trip in transit — events](https://erpdocs.corexlogic.com/en/en/img/screens/lojistik/tasima-yolda.png)
1. Status: In transit
2. Complete — arrival is written, trip closes
3. Record Event — arrival, delivery, delay, problem
4. Event timeline

A delay or problem on the road is recorded with the **Gecikme bildirildi** (Delay reported) / **Sorun bildirildi**
(Problem reported) event (the screenshot above is from the Izmir trip TSM-2026-000002). Details: [Dispatch a
trip](https://erpdocs.corexlogic.com/en/lojistik/islemler/seferi-yola-cikarma).

## 8. Record the deliveries and complete the trip

At each stop, record **Teslim edildi** (Delivered) with **Olay Kaydet** (Record Event): stop 1 SV-2026-000003,
**Teslim Alan** (Received By) "Depo Sorumlusu" (Warehouse Supervisor), 13:40; stop 2 SV-2026-000004, "Mal Kabul
Sorumlusu" (Goods Receipt Supervisor), 15:10, **Not** (Note) "1 panonun kapağı ezik" (the cover of 1 panel is
dented).

![Record Event dialog — delivered](https://erpdocs.corexlogic.com/en/en/img/screens/lojistik/olay-kaydet.png)
1. Event
2. Stop (delivery)
3. Received by — required on delivery
4. Time — now if empty

After the last stop, enter **Varış** (Arrival) 17:30 in the **Tamamla** (Complete) dialog. The trip becomes
**Tamamlandı** (Completed); the **Teslim** (Delivery) column shows the delivery time and recipient for each stop.

![Completed trip — deliveries and freight](https://erpdocs.corexlogic.com/en/en/img/screens/lojistik/tasima-tamamlandi.png)
1. Status: Completed
2. Load compared with capacity
3. Delivery and receiver per stop
4. Settled freight is not recalculated

Details: [Record a trip event](https://erpdocs.corexlogic.com/en/lojistik/islemler/sefer-olayi-kaydetme),
[Complete a trip](https://erpdocs.corexlogic.com/en/lojistik/islemler/seferi-tamamlama).

## 9. Record the proof of delivery

When the signed delivery notes come back, open **Alındı Teyidi Kaydet** (Record Proof of Delivery) on each
delivery's details. The dialog suggests the delivery day and the recipient from the trip's delivery event.

- **SV-2026-000003:** the accepted quantities are the same as the delivered quantities; **Kaydet** (Save).
- **SV-2026-000004:** for MAM-0002, **Kabul edilen** (Accepted) 1, **Sebep** (Reason) **Taşımada hasar**
  (Damaged in transit), **Not** (Note) "1 pano kapağı ezik geldi; müşteri teslim almadı" (1 panel cover arrived
  dented; the customer did not accept it); **Kaydet**.

![Proof of Delivery dialog](https://erpdocs.corexlogic.com/en/en/img/screens/lojistik/alindi-teyidi-kaydet.png)
1. Delivery date — cannot be in the future
2. Received by — required
3. Accepted quantity — prefilled with delivered
4. Reason for short acceptance

The card becomes **Teyit edildi** (Confirmed); SV-2026-000004 shows *Teslim edilen 2 · Kabul edilen 1 · Fark 1 ·
Taşımada hasar* (Delivered 2 · Accepted 1 · Difference 1 · Damaged in transit).

![Delivery with recorded proof of delivery — short acceptance](https://erpdocs.corexlogic.com/en/en/img/screens/lojistik/alindi-teyidi.png)
1. Confirmation status
2. Undo — only for unbilled deliveries
3. Delivered vs accepted difference
4. Difference reason

With a partial acceptance, the invoice is issued for the accepted quantity. In the **Zamanında-Tam Teslim**
(On-Time In-Full) report, Güneş Enerji's line shows *Zamanında %100 · Tam %0* (On time 100% · In full 0%). Taking
the returned panel back into stock is a separate document ([delivery correction](https://erpdocs.corexlogic.com/en/lojistik/islemler/teslimat-duzeltmesi-olusturma)
or İade Al — Receive Return). If **Alındı teyidinden sonra faturala** (Invoice after proof of delivery) had been
selected on the customer record, the deliveries would have been **Teyit bekleniyor** (Awaiting confirmation)
before the confirmation and would not have been invoiced. Details: [Record proof of delivery](https://erpdocs.corexlogic.com/en/lojistik/islemler/alindi-teyidi-kaydetme).

## 10. Settle the freight

In **Lojistik Yönetimi › Taşıma › Navlun Hesaplaşması Oluştur** (Logistics › Transportation › Create Freight
Settlement), select the **Taşıyıcı** (Carrier) Hızlı Hat; select TSM-2026-000001 (6.900,00 TRY), enter the **Not**
(Note) "Kasım 1. hafta — Ankara seferi" (November week 1 — Ankara trip) and click **Hesaplaşmayı Kaydet** (Save
Settlement).

![Create Freight Settlement](https://erpdocs.corexlogic.com/en/en/img/screens/lojistik/navlun-hesaplasmasi-olustur.png)
1. Carrier
2. Currency — one per document
3. Settlement date
4. Completed trip with calculated freight
5. Save Settlement

**NHS-2026-000001** opens in **Kaydedildi** (Saved) status: Amount (excl. VAT) 6.900,00 TRY, VAT 1.380,00 TRY
(KDV20 · 20%), **Genel Toplam 8.280,00 TRY** (Grand Total). The trip's Navlun (Freight) card now says
*"Hesaplaşıldı: NHS-2026-000001 — navlun yeniden hesaplanmaz."* (Settled: NHS-2026-000001 — the freight is not
recalculated.) The carrier's invoice is linked to this document in Finance.

![Freight settlement detail](https://erpdocs.corexlogic.com/en/en/img/screens/lojistik/navlun-hesaplasmasi-detay.png)
1. Status
2. Total incl. VAT
3. Cancel — if not linked to an invoice

Details: [Create a freight settlement](https://erpdocs.corexlogic.com/en/lojistik/islemler/navlun-hesaplasmasi-olusturma).

## Monitoring the process

**Lojistik Yönetimi › Giden Teslimat › Teslimat İzleme** (Logistics › Outbound Delivery › Delivery Tracking)
counts the deliveries stage by stage: awaiting goods issue, not assigned to a trip, planned trip, in transit,
awaiting proof of delivery. Overdue deliveries appear with the **Gecikmiş** (Overdue) badge.

![Delivery Monitor — stages](https://erpdocs.corexlogic.com/en/en/img/screens/lojistik/teslimat-izleme.png)
1. Warehouse filter
2. Look-back window
3. Stage card — count and overdue
4. Overdue delivery
5. Reference check — shows, does not fix

For freight and delivery performance, see [Logistics analytics](https://erpdocs.corexlogic.com/en/lojistik/ekranlar/analitik) (Freight Cost,
On-Time In-Full).

## FAQ / Troubleshooting

| Message or situation | Cause and solution |
|---|---|
| *"Mal çıkışı kaydedilmemiş ya da iptal edilmiş teslimatla sefer yola çıkamaz: …"* (A trip cannot be dispatched with a delivery whose goods issue has not been posted or that has been cancelled: …) | Post the goods issue of the deliveries on the trip; remove the cancelled delivery from the trip. |
| *"Taşıyıcıya verilen sefer taşıyıcı seçilmeden yola çıkamaz."* (A trip given to a carrier cannot be dispatched before a carrier is selected.) | Select the carrier with **Taşıyıcı Seç › Ata** (Select Carrier › Assign) or **Düzenle** (Edit). |
| *"Kendi filomuzla yapılan sefer araç ve sürücü olmadan yola çıkamaz."* (A trip with our own fleet cannot be dispatched without a vehicle and driver.) | Select the vehicle and driver with **Düzenle** (Edit). |
| *"Belgesiz sefer yola çıkamaz — en az bir teslimat atayın."* (A trip without documents cannot be dispatched — assign at least one delivery.) | Add a delivery to the trip. |
| *"Şu belgeler başka bir seferde: …"* (These documents are on another trip: …) | A delivery can be on only one trip at a time; remove it from the other trip. |
| The Navlun (Freight) card shows *"Seferde taşıyıcı yok."* (The trip has no carrier.) | Select the carrier; freight is calculated only for a carrier trip. |
| *"Taşıyıcının seferin çıkış gününde geçerli navlun anlaşması yok."* (The carrier has no freight agreement valid on the trip's departure day.) | Check the agreement's validity period or the trip's departure day. |
| *"Ölçüsü bilinmeyen dayanak hesaba girmez: …"* (A basis with an unknown measure is not included in the calculation: …) | Enter the distance on the trip and the weight and volume on the item record; **Yeniden Hesapla** (Recalculate). |
| *"Sefer ya da anlaşma hesaptan sonra değişti — navlunu yeniden hesaplayın."* (The trip or the agreement changed after the calculation — recalculate the freight.) | **Yeniden Hesapla** (Recalculate) on the Navlun (Freight) card. |
| *"Varış ve teslim bir durağın (belgenin) olayıdır — durağı seçin."* (Arrival and delivery are events of a stop (document) — select the stop.) | Select the **Durak** (Stop) in the event dialog. |
| *"Teslim tarihi bugünden sonra olamaz."* (The delivery date cannot be later than today.) | The delivery date of the proof of delivery must be today or earlier. |
| *"TSM-… tamamlanmadı — yalnız tamamlanmış sefer hesaplaşır."* (TSM-… has not been completed — only a completed trip can be settled.) | **Tamamla** (Complete) the trip first. |
| *"Seferin navlunu NHS-… hesaplaşmasında — önce hesaplaşmayı iptal edin."* (The trip's freight is in settlement NHS-… — cancel the settlement first.) | Settled freight is not recalculated; cancel the settlement if necessary. |
| *"Yalnız planlanan sefer iptal edilir — yola çıkmış sefer tamamlanır."* (Only a planned trip can be cancelled — a dispatched trip is completed.) | A trip in transit cannot be cancelled. |
| In Load Planning a delivery shows *"Ağırlığı ya da hacmi bilinmiyor (ölçüsü tanımsız ürün) — kapasitesi tanımlı araca konamaz."* (Weight or volume unknown (item without defined measures) — it cannot be put on a vehicle with a defined capacity.) | Enter weight/volume on the item record, or create the trip manually. |