# Record a shipment event

> Record loading, arrival, delivery, delay and issue events on a shipment; the delivery event carries the recipient's name.

URL: https://erpdocs.corexlogic.com/en/lojistik/islemler/sefer-olayi-kaydetme

- **Type:** Task
- **Module:** Logistics
- **Menu path:** Lojistik Yönetimi › Taşıma › Taşıma Belgeleri › sefer detayı › Olay Kaydet (Logistics Management › Transportation › Transportation Documents › shipment details › Record Event)
- **Screen route:** `/erp/logistics/transports/{id}`
- **Required permission:** `erp-logistics-transport-events.create`
- **Prerequisites:**
  - The shipment is in **Planlandı** (Planned) (Yüklendi (Loaded) only) or **Yolda** (In Transit) status.

An event does not change the plan; information from the driver and the field is recorded with its own permission
(`erp-logistics-transport-events.create`). The departure and completion events are written by the shipment's own steps
(**Yola Çıkar** (Dispatch), **Tamamla** (Complete)).

## Steps

1. In the shipment details, click **Olay Kaydet** (Record Event) on the **Olaylar** (Events) card.
   <!-- action: click · target: "Olay Kaydet" · expect: "The Olay Kaydet (Record Event) window opens; on a shipment in transit, the event defaults to 'Teslim edildi' (Delivered) and the next undelivered delivery in stop sequence" -->
2. Select the **Olay** (Event): **Yüklendi** (Loaded), **Vardı** (Arrived), **Teslim edildi** (Delivered), **Gecikme bildirildi** (Delay reported) or **Sorun bildirildi** (Issue reported) (on a planned shipment, only Yüklendi (Loaded)).
   <!-- action: select · target: "Olay" · value: "Teslim edildi" -->
3. Select the **Durak** (Stop). It is required for arrival and delivery; for other events, **Seferin geneli** (Entire shipment) can be selected.
   <!-- action: select · target: "Durak" · value: "1. SV-2026-000003 — Başkent Mimarlık ve İç Mimari Ltd. Şti." -->
4. For a delivery event, enter the name of the **Teslim Alan** (Recipient).
   <!-- action: fill · target: "Teslim Alan" · value: "Depo Sorumlusu" -->
5. Enter the **Zaman** (Time) (the default is now) and, if necessary, the **Konum** (Location) and **Not** (Note), then click **Kaydet** (Save).
   <!-- action: click · target: "Kaydet" · value: "02.11.2026 13:40 · Çankaya / Ankara" · expect: "The event is added to the timeline; the stop's Teslim (Delivery) column on the delivery becomes 'Teslim edildi · zaman · teslim alan' (Delivered · time · recipient)" -->

   ![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

**Result:** The event is written to the shipment's timeline. The date and recipient of the delivery event appear in the delivery details and are suggested in the [proof of delivery](https://erpdocs.corexlogic.com/en/lojistik/islemler/alindi-teyidi-kaydetme) window.

## What you need to know

- An event cannot be changed; an incorrect record is corrected with a new event.
- A stop is delivered only once; a delivered stop does not appear in the delivery list (*"SV-… zaten teslim edildi."*
  (SV-… has already been delivered.)).
- An event cannot be before the departure; Konum (Location) can have up to 256 characters, and Not (Note) up to 512.
- Rejection messages of the window: *"Durağı (teslimatı) seçin."* (Select the stop (delivery).), *"Teslim alanın adını
  yazın."* (Enter the recipient's name.)
- **Gecikme bildirildi** (Delay reported) and **Sorun bildirildi** (Issue reported) do not change the shipment's
  status; the shipment remains **Yolda** (In Transit). The server calculates the **Gecikmede** (Delayed) badge in the
  header with its own clock.

## Related

- [Transportation documents screen](https://erpdocs.corexlogic.com/en/lojistik/ekranlar/tasima-belgeleri)
- [Complete a shipment](https://erpdocs.corexlogic.com/en/lojistik/islemler/seferi-tamamlama)