Shopify Kolay Gelsin Integration

Kolay Gelsin is the shipping network previously known as Sendeo. Older contracts and some integration panels still say Sendeo; the firm you connect to today is Kolay Gelsin. The firm has no Shopify app of its own, so the path runs through a corporate agreement and access details taken from a branch. City and district are expected as codes from the firm's list, the barcode can be yours or the firm's, and the tracking number does not arrive at the same time as the barcode.

Talk to us about setup See the integration

200+ active brands
growing on Shopify with Nodus Works

Shopify Kolay Gelsin integration what is it?

The Shopify Kolay Gelsin integration is the connection that declares store orders as shipments to the carrier, prints the label, writes the tracking number on the order and reads delivery status back. Kolay Gelsin does not publish its own Shopify app; an integration tool builds the bridge using your corporate account credentials.

Setup starts with an agreement, not with writing code. Access details are requested from the branch and arrive in a few business days. If the row in your panel still says Sendeo, it is the same network; a second contract is not opened, your existing customer code is used.

Once the connection is live, daily work runs from one screen: the order is declared, the label is printed, the customer notification goes out from Shopify's own email when the tracking number is written on the order, and the order closes on its own when delivery status is read back.

WHAT IT DOES

What a shipping integration actually does

Once the connection is live, shipment declaration, label, tracking, delivery status, collection and returns become parts of the same flow. The six headings below cover the questions asked most often about the Shopify Kolay Gelsin integration.

Creating and declaring a shipment

The order address is declared with the data on the order instead of being typed into the carrier by hand. On the Kolay Gelsin side, city and district are expected as codes from the firm's own list; an unrecognized district stops the shipment.

Printing the label and barcode

The label is printed from the order screen. The barcode can be one of two paths: a unique reference you give, or a carriage barcode the firm produces. Which one sits on the label is chosen during setup.

Writing the tracking number on the order

The tracking number does not arrive at the same time as the barcode. It is assigned after the package reaches the branch and is scanned; when it is written on the order, the customer notification goes out from Shopify's own email.

Reading delivery status back

When the carrier status is written on the order, the order closes on its own. A tracking link also comes back in the shipment response; the customer follows the package on that link.

Reconciling cash-on-delivery shipments

On a cash-on-delivery order the amount to collect is read from the order total and written on the shipment, and the order is marked paid when the money reaches the account. Cash on delivery is tied to a separate contract.

Cancellation and return flow

Cancelling the order does not turn into cancelling the shipment until the declaration is withdrawn. Whether the return code is fixed or one-time, and whether a separate return agreement is required, could not be confirmed on the firm's published material; you ask your branch.

SHOPIFY LIMIT

How far does Shopify's own shipping go in Turkey?

The whole need for a shipping integration starts here. Shopify's shipping side was built for specific countries and Turkey is not on that list.

You cannot buy a label from the admin

Shopify's own shipping is tied to shipping origins in eight countries and Turkey is not on that list. The buy-a-label flow never appears on the order screen; the label is printed from the carrier panel or from an integration.

Checkout cannot show a live carrier rate

Pulling a live rate from the carrier's own account is available only on higher plans, and the supported list has no Turkish shipping firm. So the shipping charge at checkout in a Turkish store is a fixed or conditional rate you set by hand.

A return label does not come out of Shopify

Creating a return label through Shopify requires both the shipping origin and the buyer address to be in the United States. In Turkey the return label is produced outside and uploaded to the order.

The product card has no length, width or height

The Shopify product card has weight and no dimensions; dimensions live only on the package definition in shipping settings. A multi-line order uses the default package, the desi declaration stays short, and the branch measures the difference.

You cannot add a district field at checkout

On plans other than Plus you cannot add city and district pickers at checkout. Kolay Gelsin, meanwhile, expects district as a code from its own list. The fix in the field is making address line 2 required and renaming it to district.

The notification chain is ready, the trigger is yours

Shopify already carries shipping confirmation, shipping update, out for delivery and delivered notifications. The last two depend on an event from the carrier; the data that feeds them comes from the integration.

The shared result of these six points is this: in Turkey a shipping integration does not add convenience on top of Shopify, it puts a missing piece in place. Label production, tracking number and delivery status do not enter Shopify any other way.

SETUP

How do you set up Shopify Kolay Gelsin integration?

The six steps below cover the whole setup, from the agreement to printing the first label. The second step is specific to this firm: if the row in your panel still says Sendeo, a new contract is not opened.

Sign your corporate agreement and take your customer code

The path goes through the branch. Through kolaygelsin.com tell your nearest branch that you want to become a corporate customer and that you want integration access. Your customer code is assigned after the contract.

Request access details from the branch

Integration details do not come out of a personal account; the branch gives them and it can take a few business days. If your older contract is in the Sendeo name, the same code is valid; do not open a second customer record. If you will use cash on delivery, ask in the same meeting whether that side is tied to a separate contract.

Add the account to the tool you use

The customer code and access details go into the integration tool. If the carrier name in the panel still says Sendeo, it is the same network, and you pick that row. The firm has no app of its own in the Shopify app store; the listing that appears belongs to an independent developer.

Choose the barcode path and the recipient types

Will your reference sit on the label, or the firm's carriage barcode? The two are not one number at the same time. Recipient type (individual or corporate) and address type (home or workplace) are separate fields on the declaration; Shopify does not carry them natively, so a default value is written during setup.

Define the address, desi and payment setup

Make address line 2 required at checkout and rename it to district. The district has to be a value the firm's list recognizes. Also set your label printer, your default package dimensions and, if you will use cash on delivery, the manual payment method on the Shopify side in this step.

Confirm the label and tracking with a single order

Place an order with a single product and see that the shipment is created, the label is printed, the barcode can be scanned and the tracking number is written on the order later. If the district is not recognized, the shipment stops in this step; the fix is on the address line, not in the carrier panel.

The table below shows which Shopify records map to which counterparts on the Kolay Gelsin side.

What Shopify has	What it maps to at Kolay Gelsin
Order	Shipment declaration
Shipping address	Recipient address; city and district as codes
Address line 2	District (no separate field outside Plus)
Package definition	Desi declaration, dimensions are not on the product card
Order number	Your reference; the barcode can be separate
Tracking	Assigned after the branch scan
Cash on delivery	Amount to collect, a separate contract
Return	Tied to the agreement; the model is not clear in this review
No Shopify counterpart	Recipient type, address type, city and district code list

The last row of the table is three items Shopify does not carry natively. Recipient type and address type are chosen separately on the declaration; if they are left empty the shipment stops or the wrong rate is applied. City and district are resolved from the firm's list, free text is not enough.

Where are you in the setup?

Tell us about your catalog and current setup, and we will work out how the Shopify Kolay Gelsin integration should be built for your product structure. You do not need to fill in a form, reach us directly by phone, email or WhatsApp.

Get in touch 0850 888 2815 hub@nodusworks.com WhatsApp

SENDEO NAME

If it says Sendeo, is it the same network?

Kolay Gelsin previously operated under the Sendeo name. Developer documentation still sits under the old organization name and Sendeo appears in the text. That does not mean two separate shipping firms.

If a Sendeo row still sits in your older contract, on your invoices or in the carrier list of the integration panel you use, you most likely use the same customer code. Opening a new corporate application produces a second invoice and a second access; packages split across two accounts.

A new contract is signed in the Kolay Gelsin name. The branch tells you whether the old code is valid under the new name; do not assume it, ask. The row name in the panel may not have changed, and the shipment still lands on the same network.

The same split sits on the barcode side. If you use your own unique reference, tracking runs from that reference; if you use the firm's carriage barcode, the number on the label is theirs. Mixing the two produces a label the branch cannot scan.

ADDRESS AND DESI

Why do city, district and desi stop a shipment?

A Kolay Gelsin declaration expects a coded address and a measured package. Shopify carries neither natively.

City and district are resolved from a list

The city name does not go as free text, it matches a code on the firm's city and district list. 'Ist.' or 'Kadikoy' is not recognized. The district on the address line has to match the spelling on the list.

There is no district field outside Plus

Adding a district picker at checkout is tied to a higher plan. On other plans address line 2 is made required and its label becomes District. If the customer writes a neighborhood there, the shipment is not created.

Desi is volume turned into a charge

The invoice is issued on whichever is larger, weight or desi. Domestically volume is divided by three, internationally by five; rounding is up from one half.

Dimensions do not live on the product card

The Shopify product card has no length, width or height. Dimensions live on the package definition, and a multi-line order uses the default package. The declaration stays short, the branch measures the real desi, and the difference hits the invoice.

Piece dimensions can go separately

If a shipment has more than one piece, each piece's own length, width, height and weight can be declared. A single default package does not carry that split; a store that uses multi-piece boxes sets the package definition to match.

An undeclared label cannot be scanned at the branch

Printing the barcode first and declaring later is not a problem; the reverse is. If the label is in hand and the shipment is not in the system, the branch does not take the package.

PAYMENT AND RETURNS

How are cash on delivery and returns set up?

Both items are tied to an agreement. An app does not turn them on by itself.

Cash on delivery is a manual method in Shopify

The order opens as payment pending and is marked paid by hand after collection. The integration sets up the match. Region limits, amount caps and a cash-on-delivery fee are not built into Shopify.

The agreement belongs to the seller

Apps do not provide a shipping agreement. The alternative is shipping on an intermediary's bulk rate, and in that case the invoice comes from the intermediary. The two models are not mixed.

A barcode and a tracking number are not the same thing

The barcode is an intermediate number produced so the firm can recognize the package. The tracking number is assigned after the package reaches the branch and the barcode is scanned. That is the answer to why the tracking number does not arrive at once.

The tracking link comes from the response

When the shipment is created, the firm's tracking link also comes back. The customer follows the package on that link; if the link is not written on the order, the notification stays empty.

The return code depends on the model

A fixed code and a one-time code are two separate models, and firms do not support the two together. Which one applies on the Kolay Gelsin side could not be confirmed on the firm's published material; you ask the branch.

Marketplace shipping is not your agreement

A Trendyol or Hepsiburada label is that channel's shipping. Invoice and return flow are separate; shipping cost does not appear on a single screen. Your Kolay Gelsin agreement only covers shipments that leave from your own site.

WHICH PATH

Which path do you connect through?

There are three paths and they split by scale. Because the firm has no Shopify app of its own, the choice stays on your side.

A multi-carrier panel

If you use more than one shipping firm, you pick the Kolay Gelsin or Sendeo row from the panel's carrier list. The same customer code is entered. Whether it writes the tracking number on the Shopify order automatically is confirmed from the panel.

An independent app

There is a listing under the Kolay Gelsin name in the app store; the developer is not the firm. If you want a screen focused on one firm and you will not use another carrier, this path can be short. Ownership sits in that developer's contract.

A project-specific bridge

If recipient type, piece dimensions, your own barcode and a custom return rule are all required at once, a ready panel is not enough. The bridge turns your order fields into the declaration form the firm expects.

No shipment without an agreement

Access is tied to a corporate customer code. A personal branch shipment is not opened to the integration. Without an agreement, no label is produced.

An older Sendeo code

If you have an older code, the branch opens it on the Kolay Gelsin side. A new application produces a second invoice; ask first whether the existing code is still valid.

Looking from a single panel

Because marketplace shipping stays separate, seeing Kolay Gelsin shipments that leave from your own site next to channel shipping makes the work easier. That is why Station comes in.

SCENARIO

Three common problems and how we solve them

The three setup scenarios below show how we handle Shopify Kolay Gelsin integration problems we have solved in stores we connected.

The shipment not being created because of district

ProblemThe label would not print, and the panel said the district was not recognized. The customer address looked correct on the screen.

CauseDistrict was not a separate field at checkout. The customer had written a neighborhood or a site name into address line 2. Kolay Gelsin was expecting district as a code from its own list.

SolutionAddress line 2 was made required and its label became District, and a sample spelling was added at checkout. Districts on open orders were corrected from the list and the shipments were declared again.

Treating the Sendeo row as a second firm

ProblemThe store had opened a new Kolay Gelsin agreement, and the older Sendeo code was still sitting in the panel. Packages were splitting across two accounts, and the invoice was split in two.

CauseThe two names pointed at the same network. The panel had not updated its carrier list, and the older row had stayed as Sendeo. The new application had produced a second customer code.

SolutionThe branch confirmed that the older code was valid. The new code was closed, a single row was left in the panel. Shipments were written back to one account.

The tracking number never landing on the order

ProblemThe label was printing, the courier was taking the package, and the customer was writing to ask where the shipment was. The Shopify order still looked like it was waiting.

CauseThe bridge was writing the barcode and not writing the tracking number. Because the tracking number arrives after the branch scan, the first response was empty and a second read had not been set up.

SolutionStatus was read a second time after the shipment was created, and the tracking number and the tracking link were written on the order. Shopify's shipping notification started going out from that moment.

STATION

Shopify Kolay Gelsin integration

Station is the tool we built to run order, label, tracking and collection flow from one panel. If you also sell on marketplaces, their shipping flow stays separate, so seeing the two side by side makes the work easier.

See the integration Talk to us about setup

FAQ

Frequently Asked Questions

How do you set up Shopify Kolay Gelsin integration?

Setup starts with a corporate agreement. The customer code and access details are taken from the branch, the account is added to the tool you use, the barcode path and recipient type are chosen, and the district field is set up at checkout. The last step is printing the label of a test order with a single product and writing the tracking number on the order.

Are Kolay Gelsin and Sendeo the same firm?

Kolay Gelsin was previously known as Sendeo. The row name in an older contract and in some integration panels can still say Sendeo. The network you connect to today is Kolay Gelsin; treating the two names as two firms and opening a second contract splits shipments across two accounts.

Does Kolay Gelsin have an official Shopify app?

The firm has no app that it publishes itself in the Shopify app store. The listing that appears belongs to an independent developer. The official path is a corporate agreement and access details taken from a branch.

Where are access details taken from?

They do not come out of a personal account. You tell the branch that you want to be a corporate customer and that you want integration access, and the details arrive in a few business days. If you have an older Sendeo code, ask first whether it is still valid.

Can a shipment be sent without an agreement?

The integration is tied to a corporate customer code. A personal branch shipment is not opened to this bridge. Without an agreement, no label is produced.

Why are city and district required?

Kolay Gelsin expects city and district as codes from its own list. Free text is not recognized. Because a district field cannot be added at checkout outside Shopify Plus, address line 2 is set up as district.

Are a barcode and a tracking number the same thing?

They are not. The barcode is an intermediate number produced so the firm can recognize the package. The tracking number is assigned after the package reaches the branch and the barcode is scanned. That is the answer to why the tracking number does not arrive at once.

Can I use my own reference number as the barcode?

Yes, the firm's documentation describes working with a unique reference you give and with a carriage barcode the firm produces. Which one sits on the label is chosen during setup; mixing the two produces a label the branch cannot scan.

What are recipient type and address type?

On the declaration the recipient is chosen separately as individual or corporate, and the address as home or workplace. Shopify does not carry these natively. A default value is written during setup; if they are left empty the shipment stops or the wrong rate is applied.

How is desi calculated?

Desi is volume turned into a charge, and the invoice is issued on whichever is larger, weight or desi. Domestically volume is divided by three, internationally by five; rounding is up from one half. Because the Shopify product card has no dimensions, the declaration goes from the package definition.

How does cash on delivery work?

On the Shopify side it is a manual payment method; the order opens as pending and is marked paid after collection. On the Kolay Gelsin side cash on delivery is tied to a separate contract. Region limits and amount caps are not built into Shopify.

How is a return code taken?

A return code is tied to an agreement. A fixed code and a one-time code are two separate models. Which one Kolay Gelsin gives could not be confirmed on the firm's published material; you ask the branch.

Can I also send marketplace orders with Kolay Gelsin?

Marketplace shipping is that channel's agreement, not your Kolay Gelsin contract. Shipments that leave from your own site are declared to Kolay Gelsin; the marketplace label comes out of the channel's shipping.

Where does the tracking link come from?

When the shipment is created, the firm's tracking link comes back in the response. If that link is written on the order, the customer follows the package from there. If only the barcode is written, the customer asks where the shipment is.

Should I pick the Sendeo row or the Kolay Gelsin row in the panel?

If the tool you use has not updated its list, the row name may still say Sendeo. If the branch says the same customer code is valid on that row, you pick that row. Filling both rows at once splits shipments in two.

How long does the integration take?

Because the agreement and the access details come from the branch, the branch sets the calendar; an official day count is not published. After the details arrive, the address setup, the barcode path and the test order sit on your side.

Do orders outside Turkey go as well?

Kolay Gelsin is a domestic-focused network. Dropping an order with a foreign address onto this bridge stops the shipment; those orders are split to a separate carrier.

What happens if a label is printed without a declaration?

If the label is in hand and the shipment is not in the system, the branch does not take the package. Printing the barcode first and declaring later is not a problem; the reverse is.