What does this integration do?
With the Yurtiçi Kargo integration, Shopify orders are written as shipments into your contracted Yurtiçi account; labels are printed from the store admin and delivery status is updated on the order.
The data it synchronises
Automatic shipment records
Label and dispatch note output
Tracking number written back
Delivered / out-for-delivery tracking
Cash-on-delivery shipments
Multi-warehouse support
How the data flows
01
The order becomes a shipment
The order is written into your Yurtiçi account as a shipment on the trigger you define. We decide together which orders flow automatically and which need approval.
02
The dispatch warehouse is chosen
If you have more than one warehouse, the shipment's origin is selected from the stock location in Shopify. Choosing the wrong warehouse increases both time and cost.
03
Label and dispatch note are printed
Labels are printed individually or in bulk. On cash-on-delivery shipments the collection amount is printed on the label.
04
Tracking information is written back
The tracking number is written onto the order and the customer notification is triggered. Whether Shopify or a separate SMS flow sends that notification is decided here.
05
Delivery status is tracked
Distribution and delivery statuses are reflected on the order; undeliverable shipments are collected in a separate list for the operations team.
What we watch for in this integration
In a multi-warehouse setup, if stock locations are not defined correctly in Shopify, shipments leave from the wrong branch
Differences between the cash-on-delivery amount and the order total (the COD service fee) cause reconciliation problems; where that difference is booked is settled up front
If product weights are missing, shipments are opened on a default volumetric weight and an invoice discrepancy follows
If an order sometimes has to ship in parts (from different warehouses), that scenario is designed up front
If a notification SMS is also sent separately, a single source is chosen so the customer is not notified twice
The setup process
01
Data and permission analysis
We decide which data flows in which direction, which system is the master, and what API permissions are required.
02
Mapping table
Product, variant, category, warehouse and account fields are mapped between the two systems, one by one.
03
Development and testing
The integration is built on a development store; order, return and error scenarios are tested with real data.
04
Going live
It is released through a controlled switchover, watched closely for the first few days, with the error queue monitored.
05
Monitoring and maintenance
Logging, error alerting and API version updates continue under the maintenance retainer.
What we need from you before we start
Yurtiçi Kargo customer number and integration user credentials
Your negotiated price list
Number of warehouses/locations and how stock is distributed
Whether cash on delivery is used
Daily shipment count