Short answer
A Sendeo Shopify integration automatically sends Shopify orders to the Sendeo (today Kolay Gelsin) system, creates barcodes, writes the tracking number to the Shopify fulfillment and carries delivery statuses back to Shopify. But there is an important development to know about: Sendeo, the carrier of Koç Group, merged with Ekol’s Kolay Gelsin, and according to industry press, following the Turkish Competition Board’s approval on 29 May 2024, the combined company operates under the Kolay Gelsin name.
So for a Shopify brand searching for a “Sendeo integration” today, the right question is how to keep an existing Sendeo connection working or how to move it to Kolay Gelsin. Reviewing and updating an existing integration takes 1–2 weeks; a new setup takes 2–5 business days with a ready-made app and 3–5 weeks with a custom build.
This guide was prepared from the field experience of the Byte Digital team, a Shopify Plus Partner that has served Shopify brands since 2020.
What happened to Sendeo? A short history
Sendeo is a Koç Group distribution and delivery company, founded in 2021 under Aygaz’s lead as Aykargo and rebranded as Sendeo the same year. It stood out by working with distribution centres and delivery points instead of a classic branch model.
Date | Development | What it means for Shopify brands |
|---|---|---|
January 2021 | Aykargo founded as an Aygaz and McKinsey partnership | Initially served Istanbul only |
September 2021 | Aykargo continued under the Sendeo brand | Integrations were built under the Sendeo name |
February 2022 | Reached all 81 provinces, according to industry press | Nationwide shipping became possible |
January 2024 | Letter of intent signed to merge with Kolay Gelsin | The future of existing integrations came into question |
May 2024 | Competition Board approved the merger; the company continues as Kolay Gelsin | New agreements and API credentials run through Kolay Gelsin |
While preparing this article we could not access and verify Sendeo’s official website or current API documentation. We therefore recommend confirming in writing with your account representative how accounts and API credentials opened under the Sendeo name work today. For Kolay Gelsin’s own features and a setup from scratch, see our Kolay Gelsin Shopify integration guide.
What does a Sendeo Shopify integration do today?
A working Sendeo or Kolay Gelsin integration does the same four jobs as other shipping integrations: it opens a shipment record, generates barcodes and labels, writes the tracking number to Shopify and syncs delivery statuses. For the general structure, see our Shopify shipping integration guide. After the merger, three areas on the Shopify side become especially important:
Tracking company name: Neither Sendeo nor Kolay Gelsin is among the carriers for which Shopify generates tracking links automatically. So the company name and tracking URL are sent explicitly in trackingInfo. For new shipments after the merger, decide which brand name the customer sees and use the same name across all channels.
Tracking URL template: If your integration builds the tracking link from a fixed Sendeo address, check that this address still leads to the right page. To fix the link on open shipments, Shopify’s fulfillmentTrackingInfoUpdate mutation can be used (Shopify fulfillmentTrackingInfoUpdate); if the notifyCustomer field is left blank, the customer is not notified again.
Status mapping: Status codes from the new system may not match the old ones one to one. Re-test the mapping to IN_TRANSIT, OUT_FOR_DELIVERY, READY_FOR_PICKUP and DELIVERED; an unmatched code can mean Shopify’s “Delivered” email is never sent.
Integration methods for Sendeo or Kolay Gelsin
If you use an existing app or integrator, first check its post-merger support; if you are building a multi-carrier setup, an aggregator platform is the right choice, and with an ERP connection, a custom middleware layer.
Method | When to choose it | Time | Flexibility | Ongoing cost |
|---|---|---|---|---|
Keep the existing Sendeo app | App is still supported and this is confirmed | 1–3 days of checks | Low | Existing subscription |
Move to a Kolay Gelsin app | New agreement signed under the Kolay Gelsin name | 2–5 business days | Low–medium | Monthly subscription |
Multi-carrier platform | Using Sendeo / Kolay Gelsin alongside other carriers | 1–2 weeks | Medium | Per shipment or monthly |
Custom middleware | ERP, warehouse software, custom status mapping | 3–5 weeks | Highest | Hosting + maintenance |
Some multi-carrier apps on the App Store still list Sendeo among supported carriers; others use the Kolay Gelsin name. Whatever name it is listed under, ask the app developer whether it works with the current API. In Byte Digital’s analysis of 100 Turkish Shopify stores, 95 stores were integrated with carriers directly or through an aggregator; shipping integration is now standard, and the difference shows up in maintenance.
Updating a Sendeo integration step by step: time and cost
Reviewing and updating an existing integration takes 1–2 weeks, moving to a new setup takes 2–5 weeks; most of the time goes to confirmation and parallel testing.
Inventory (1–2 days): List which app or code connects to Sendeo, which API credentials it uses and how tracking URLs are built.
Contract confirmation (3–7 days): Get the post-merger status of the existing agreement, cash on delivery and return scope, and new API credentials in writing from the account representative.
Update or migration (1 day – 3 weeks): App settings or middleware are updated with the new API credentials; the company name, tracking URL template and status mapping are corrected.
Parallel testing (3–5 days): For a few days, part of the shipments are opened with the new setup; barcodes, tracking links, delivery status and returns are checked.
Full cutover and cleanup (2–3 days): The old app is removed, unused API credentials are revoked, and the customer support team is briefed on the new tracking flow.
The main cost drivers: the type of existing integration (app or custom code), shipment volume, ERP connection, cash on delivery and return flows, and whether several carriers are used. Shipping rates depend on your agreement.
Delivery points and shipping promise: how are they shown at checkout?
Sendeo’s model relied on recipients collecting their parcel from the nearest delivery point when it could not be delivered to the address; delivery points remain an important option in the combined company. To make this option truly usable on the Shopify side, the delivery point or delivery preference should be shown at checkout. This is done with Checkout Extensibility, which replaced checkout.liquid, through a checkout UI extension or an app that manages delivery options.
The shipping promise is also part of conversion. Setting the free shipping threshold slightly above your average order value and suggesting a complementary product to customers approaching the threshold is one of the most effective ways to turn shipping cost into sales; details are in our cross-sell, upsell and bundle guide.
The 6 most common Sendeo Shopify integration mistakes
Most post-merger mistakes are not technical; they come from old settings being kept without question.
Not checking because “it works”: Even if barcodes are created, the tracking link or status updates may have quietly broken.
Keeping the old tracking URL: The customer lands on an empty or wrong page, and support gets flooded with questions.
Writing the carrier name differently across channels: Seeing “Sendeo” in Shopify and “Kolay Gelsin” in an email confuses the customer.
Not re-testing status code mapping: If new codes do not match, the “Delivered” email is not sent and the order stays open.
Leaving old API credentials active: If unused integrations are not revoked, there is a risk of unauthorised access.
Not confirming cash on delivery and return scope: Terms may have changed after the merger; collection and return flows should not stay live without written confirmation.
Sendeo Shopify integration with Byte Digital
Byte Digital is an Istanbul-based Shopify Plus Partner that has provided Shopify builds, integrations and Shopify technical support to leading Turkish brands since 2020. We audit existing integrations built with Sendeo, adapt them to the post-merger setup, or move them, together with Kolay Gelsin and other carriers, into a single Shopify-centred shipping layer.
Share the app or integration you use, your shipment volume and your other carriers; we will prepare a free preliminary assessment covering the state of your current setup, the updates needed and an estimated budget.
Request a free Sendeo Shopify assessment →
Frequently asked questions
Is Sendeo still operating?
According to industry press, Sendeo merged with Kolay Gelsin, and following the Competition Board approval in May 2024 the combined company operates under the Kolay Gelsin name. Confirm the status of your existing account with your account representative.
Will my existing Sendeo Shopify integration keep working?
That depends on whether the app or code you use is compatible with the current API. Test barcodes, tracking links and delivery status with a few real shipments; if there is a problem, update it with new API credentials.
How do I fix tracking links for Sendeo shipments in Shopify?
For open shipments, the tracking URL can be updated with the fulfillmentTrackingInfoUpdate mutation. Leave the notifyCustomer field blank so the customer is not notified again.
Should I choose Sendeo or Kolay Gelsin for a new store?
Since new agreements after the merger run through Kolay Gelsin, starting new setups with Kolay Gelsin’s current API is the healthier choice. When choosing an app, ask about current API support.
Can Sendeo delivery points be shown at Shopify checkout?
Delivery point selection can be shown with a checkout extension built on Checkout Extensibility or an app that offers this feature. Clarify with the carrier which service the list of points will come from.
How long does it take to move from Sendeo to another carrier?
It takes 2–5 business days with a ready-made app and 3–5 weeks with a custom setup that includes ERP and return flows. A few days of parallel running during the move catches tracking and notification errors before go-live.
