Shopify Kargoist Integration

Kargoist is not a shipping aggregator or a multi-carrier panel; it is a shipping firm that works with its own branches and couriers. On integration panels it sits as one row in the same list as other shipping firms. A second point that often gets mixed up is on the Shopify side: this firm has neither its own app nor an app built only for it in the app store, so the connection is built from a multi-carrier panel. The access credentials come from the panel you use, a few fields are required on the declaration, and a few topics still have to be confirmed before setup.

Talk to us about setup See the integration

200+ active brands
growing on Shopify with Nodus Works

Shopify Kargoist integration what is it?

The Shopify Kargoist integration is the connection that declares store orders as shipments to the carrier, produces the label, writes the tracking number on the order and reads delivery status back. The firm 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. After you become a corporate sender the access credentials are sent on a request made to the branch; this firm has no portal where you can produce the credentials yourself. The identity pair is also different from other firms: an access key and a form identity are used instead of a customer code and a password. On setups like this, where there is no self-service credential portal, Nodus Works' Shopify integration and custom app development service runs the process for you.

Once the connection is live, daily work runs from one screen: the order is declared as a shipment, the barcode is produced, the label is printed, the customer notification goes out 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 Kargoist integration actually does

Once the connection is live, shipment declaration, barcode, label, tracking, delivery status and collection become parts of the same flow. The six headings below cover the questions asked most often about the Shopify Kargoist 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. At this firm the required fields of the declaration also include a branch code, so which origin the shipment leaves from is stated on the declaration.

Barcode and label

During the declaration a unique barcode number is given to the shipment and the label is printed with that number. What format the label arrives in is not a published fact; you need to confirm it from the tool you use in setup.

Writing the tracking number on the order

When the tracking number is written on the order, the customer notification goes out from Shopify's own email. At this firm tool choice matters here: one aggregator does not list Shopify among the platforms it writes the tracking number on automatically.

Reading delivery status back

When the package enters the branch and when it is delivered, the status is written on the order and the order closes on its own. If this reading is not set up, the only way to learn which package was delivered is to look at the tracking screen one by one.

Cash-on-delivery shipment

At this firm the collection type is chosen at declaration time: a shipment the receiver pays for, prepaid and cash-on-delivery by card sit as separate values. So the form of cash on delivery is set at shipment level.

Return shipment

No published code model was found for this firm on the return side; there is no source on the split between a fixed code and a one-time code. That is why you need to settle the return flow from your contract before setup.

THE CORE DISTINCTION

Is Kargoist a shipping firm or a shipping platform?

The answer to this question decides the whole setup. Kargoist is a shipping firm; the platform is the panel you connect it to.

A shipping firm that works with its own branches and couriers

Kargoist carries packages on its own network. On the supported-firms table of integration panels it sits as one row in the same list as other shipping firms; it is not the panel itself, it is the carrier you connect to the panel.

Coverage is not all of Turkey

The firm is based in Istanbul and has branches in certain cities. Two third-party sources give different city and branch counts, and both are old; that is why we do not give a number here. You need to confirm coverage before the contract.

It has no Shopify app of its own

The app store has neither the firm's own app nor a third-party app built only for it. The only verified path is going through the supported-firms list of a multi-carrier app. A simple setup focused on one firm is not possible here.

No path without an agreement is visible

On one aggregator's supported-firms table the no-agreement shipping column is unmarked for this firm. So instead of shipping on the tool's bulk rate you need to make your own corporate contract.

The firm's official sources cannot be read right now

The corporate site shows a maintenance notice; the service page, frequently asked questions and contact page are not live, and the consumer tracking screen is also closed. No closure or transfer news was found either, so the status is unclear. The information below is compiled from integration-panel documents and the press.

You need to build a backup-carrier plan

Because coverage is limited, a second shipping firm is needed for some of your shipments. That is why the panel you use being multi-carrier is a requirement; you also need to define in setup the rule for which firm an order is sent to.

For the backup-carrier decision you can find the setup details of the other firms on the Shopify Yurtiçi Kargo integration and Shopify Aras Kargo integration pages.

SETUP

How do you set up Shopify Kargoist integration?

The six steps below cover the whole setup, from the agreement to printing the first label. The second and third steps are specific to this firm: the credentials come from the branch and a fixed address definition is asked for in setup.

Make your corporate agreement and confirm coverage

The integration cannot be set up without becoming a corporate sender; no path of shipping on the tool's bulk rate is visible at this firm. In the meeting, next to the rate, payment terms and invoice layout, also ask in writing which cities and districts they distribute to. Coverage is part of the buying decision.

Request your access credentials from the branch

This firm has no public developer portal; integration credentials are sent on a request made to the branch and the process can take a few days. Sending your request together with the agreement meeting is the most practical path; also saying the name of the tool you will use makes the other side's work easier.

Record the access key and the form identity

At this firm the identity pair is different from the others: an access key and a form identity are given instead of a customer code and a password. The two work together; taking one and waiting for the other leaves setup half done. Also ask in the same meeting for the branch code you will use on the declaration.

Set up your panel and have the address definition made

The credentials go into your multi-carrier panel. Among this firm's settings there is an address field that must be defined for access; so the connection working depends on a fixed address being defined on the other side. You need to handle this in setup together with your tool provider.

Define the address, desi and payment setup

On the declaration, city and district are expected as separate fields and written correctly by name. Make address line 2 required at checkout and rename it to district. If you will use cash on delivery, set the manual payment method on the Shopify side and decide which declaration value the collection type will be tied to.

Confirm the flow with a test shipment

Create a shipment from a single order and see that the barcode is produced and the label is printed. Then check that the tracking number is written on the order, the customer notification goes out and delivery status is read back. At this firm writing the tracking number on the Shopify order depends on the tool, so the test is especially important here.

The table below shows which Shopify data maps to which counterpart on the carrier side.

What Shopify has	What the carrier uses
Order	Shipment declaration
Order number	Source of the barcode number
Customer name	Receiver name
Shipping address	Open address
City	A separate field, written correctly by name
Address line 2	District, a separate field
Phone	The number the notification message goes to
Weight	One side of the chargeable weight
Package definition	Source of the desi calculation, on single-line orders
Payment status	Amount on a cash-on-delivery shipment
No Shopify field	Branch code; charge type; access key and form identity; the defined access address

The last row of the table is the backbone of setup. Branch code and charge type are values set at shipment level; access key, form identity and the defined address are the fixed settings of the connection. Without all five complete, the declaration does not work.

Where are you in the setup?

Tell us about your catalog and current setup, and we will work out how the Shopify Kargoist 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

ACCESS

Where do you get Kargoist access credentials?

At this firm the path goes through the branch. One aggregator's setup note writes this clearly: to take your service-user credentials you apply to the branch, state that you want integration credentials, and the information is sent within a few days. No customer panel or developer portal where you can produce the credentials yourself was found. The reflection of this on your setup plan is this: the most uncertain line is the wait, and sending the request together with the agreement meeting is the way to close that wait in one pass.

The second detail is the form of the identity pair. At other shipping firms you take a customer code and a password; here an access key and a form identity are given. The two work together, so when one arrives and the other is missing the connection is not built. You also need to ask in the same meeting for the branch code you will use on the declaration; branch code is among the required fields, and a store with more than one origin is expected to state on the declaration where the shipment leaves from.

The third is that among this firm's settings there is an address field that must be defined for access. So the connection working depends on a fixed address having been defined on the other side. If you will connect from your own server this address needs to be fixed; if you will use a ready panel you need to take the address to be defined from your tool provider and send it to the branch. This is the place setup gets stuck most often on the technical side, because both sides need to enter the same information correctly.

The fourth is that panel choice is more decisive at this firm than at the others. Because there is no app built only for this firm in the app store, the connection is built from a multi-carrier panel. One aggregator does not list Shopify among the platforms it writes the tracking number on automatically; another offers this firm as a paid and optional extra module. Before choosing the tool you need to ask two questions: is the tracking number written on the Shopify order, and is this firm in the standard scope.

There is also the question of who the agreement belongs to. Apps do not provide a shipping agreement; you make the agreement in your own company's name and the invoice comes from the carrier. At other shipping firms, stores without their own agreement can ship on an intermediary's bulk rate; at this firm that path is not visible, because the no-agreement shipping column on the supported-firms table is unmarked.

DECLARATION FIELDS

Which fields are required on the shipment declaration?

The fields asked for on the declaration are the real test of setup: if your data can fill these fields the integration works, if it cannot an error comes back. The six headings below are the ones specific to this firm.

A unique barcode number

Every shipment is given a number that is not repeated and the label is printed with that number. A layout produced from your order number is the most practical; opening a second shipment with the same number produces a clash, so the recreate-after-cancel rule needs to be defined from the start.

City and district as separate fields

City and district are expected in separate fields, written correctly by name. Because Shopify's checkout has no separate district field, if this field cannot be filled the declaration fails. Correcting your address data is part of setup.

Branch code

Which origin the shipment leaves from is stated on the declaration. If you have a single warehouse it is defined as a fixed value; if you ship from two warehouses, the rule for which order leaves with which branch code is written in setup.

Charge type, meaning collection type

At this firm the collection type is chosen at declaration time: bulk shipment, a shipment the receiver pays for, prepaid and cash-on-delivery by card sit as separate values. So the form of cash on delivery is set at shipment level.

The option to declare with a fixed desi

One of the integration panels has an option to send every shipment with a fixed desi value. It is used a lot in practice, but the difference between real desi and the declaration hits the invoice; that is why you need to choose the fixed value to your own package standard.

Shared-barcode support

The layout where a single barcode can be shared for the same shipment is marked as supported at this firm; split shipment also sits as supported on the same table. Cumulative shipment and marketplace shipping, on the other hand, appear as not supported.

If the order is cancelled, the declaration must be cancelled as well; if the address changes, the declaration is cancelled and created again. Because the barcode number must be unique, a declaration cannot be given again with the same number after a cancel; a new number is produced.

CHECKLIST

What you need to confirm at this firm

This firm has no public seller document and the corporate site cannot be read right now. That is why the nine headings below cannot be confirmed from the sources; they are what you should ask in the agreement meeting.

What is the firm's current status

The corporate site shows a maintenance notice and the consumer tracking screen is closed. No closure or transfer news was found either, so the status is unclear. Before the contract you need to speak with the firm directly and confirm that operations and customer support are continuing.

Which cities and districts they distribute to

Coverage is not all of Turkey and two third-party sources give different numbers, both old. Ask for the current city and district list in writing; you will need a second shipping firm for orders that fall outside coverage.

Which documents are asked for the agreement

No published information was found on the documents asked for, the contract flow or the approval time. In the sector a tax plate, a signature circular and a volume statement are generally asked for, but we do not claim that in this firm's name; ask for the list at the start of the meeting.

How long the access credentials take to arrive

One aggregator's note mentions a few days, but no official time has been published. If you will give a go-live date you need to learn this time from the start; sending the request together with the agreement reduces the wait risk.

What format the label arrives in

No source was found on the label format. If you will buy a thermal printer you need to ask this both to the firm and to your tool provider; printing a label that arrives as a document on large paper shrinks the barcode until it will not scan.

How the return flow will be set up

There is no source on whether the return code is fixed or one-time, or whether an easy-return agreement exists. If you have return volume you need to settle this in the contract, otherwise every return is run by hand.

When the money arrives on a cash-on-delivery shipment

No published information was found on the transfer time or the service fee. If you will tie your cash flow to cash on delivery you need to take these two lines in writing.

Is the tracking number written on the Shopify order

One aggregator does not list Shopify among the platforms it writes the tracking number on automatically. Ask this behavior before choosing the tool; if it is not written you will have to trigger customer notifications by hand.

Is this firm an extra-fee module in the panel you chose

One aggregator offers this firm as an optional and paid extra module; other carriers on the same panel can be in the standard scope. When choosing a tool you need to ask both the scope and the extra cost.

CASH ON DELIVERY

How is cash on delivery set up in Shopify?

Cash on delivery is set up separately on both sides: as a payment method on the Shopify side, and as a shipment layout on the carrier side. At this firm the second side is the charge-type field at declaration time.

The Shopify counterpart is a manual payment method

In Settings, under payments, cash on delivery sits as a ready manual payment method. On such an order, payment opens as pending and is marked paid after collection happens.

Collection type is chosen on the declaration

At this firm charge type is one of the declaration fields and cash-on-delivery by card sits as a separate value. So cash and card collection are split at shipment level; which order leaves with which value is tied to a rule in the integration.

Reconciliation is the integration's job

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. If this match is not set up, every order is marked by hand and at month end which collection belongs to which order is lost.

Region and amount limits are not built in

Restricting cash on delivery by region, setting an amount limit or adding a cash-on-delivery fee do not come as ready settings in Shopify. Those are solved with rate setup or an extra app.

Transfer time and service fee are confirmed

No published information was found for this firm on how long collected money takes to reach the account or on the collection service fee. Instead of trusting unsourced rate and time claims you need to take both lines from your contract.

Cash on delivery changes the return rate

Collecting payment at delivery raises the rate of packages that are not accepted, and every package that comes back means a two-way carriage fee. If you will turn cash on delivery on, you need to watch unaccepted shipments separately.

ADDRESS AND DESI

Why do address and desi data decide your invoice?

In shipping integrations the two fields that produce the most errors are address and desi. At this firm the address side is among the required fields of the declaration, and the desi side sits as an option on the panel.

District must be a separate, recognizable value

On the declaration, city and district are expected in separate fields and written correctly by name. Orders with an empty district or a district buried in free text fail at the declaration step.

How a district field is added at checkout

On plans other than Plus you cannot add city and district pickers at checkout. The path used in the field is one: address line 2 is made required and renamed to district by editing the checkout language. The second path is taking an address confirmation after the order.

Desi is volume turned into a charge

The invoice is issued on whichever is larger, weight or desi. Package volume is found in cubic decimeters, divided by three on a domestic shipment and the result is compared with kilograms.

The data to calculate desi is not on the order

The Shopify product card has no length, width or height field; dimensions live only on the package definition, and a multi-line order uses the store default package. That is why the declaration in most setups does not carry the real volume.

A fixed-desi option is a decision, not a solution

The panel has an option to send every shipment with a fixed desi value. This simplifies the calculation, but if you choose the fixed value above your real packages you overpay, if you choose it below the difference hits the invoice.

The firm measures the real desi, the difference hits the invoice

If the declared value and the measured value differ, the invoice is issued on the measured value. The shipping charge you took from the customer stays fixed while your invoice changes, so the difference comes straight out of margin.

Defining your package standards and declaring shipments on their real dimensions also lets you set the shipping rate at checkout to that real cost. If you will send orders that fall outside coverage to a second shipping firm, look at Station to see both firms' costs on one screen.

COMMON MISTAKES

The most common mistakes in a Shopify Kargoist integration

The nine headings below are the mistakes met most often in setup. At this firm half of them come from treating information that has no source as if it had one.

Thinking Kargoist is a shipping aggregator

Kargoist is a shipping firm that works with its own branches and couriers; on integration panels it sits as one row in the same list as other carriers. Looking for a panel because you think it is a platform builds setup wrong from the start.

Looking for an app focused on one firm

There is no app built only for this firm in the app store. The only verified path goes through a multi-carrier panel; stores that look for an app built only for it lose days.

Signing without asking about coverage

The firm does not distribute to all of Turkey and the sources disagree on the city count. A store that ties itself to a single carrier without taking coverage in writing is left with no outbound on out-of-coverage orders.

Expecting to ship on the tool's bulk rate

On the supported-firms table the no-agreement shipping column is unmarked for this firm. So no path of opening a shipment without your own contract is visible; a store that plans setup before the agreement hits a wall.

Trying to produce the access credentials yourself

This firm has no public developer portal; credentials are sent on a request made to the branch. Time spent looking for a portal is a direct loss; the request needs to be sent together with the agreement meeting.

Skipping the access-address definition

Among this firm's settings there is an address field that must be defined for access. When the definition is not made the connection is not built and the error is thought to be in the identity credentials; the problem is the undefined address.

Starting setup without asking for the branch code

Branch code is among the required fields of the declaration. A setup that starts without the code stops on the first shipment and correspondence with the branch starts again.

Going live without fixing the district field

On the declaration, city and district are expected as separate and written correctly. Orders with an empty district or a district buried in free text fail; turning address line 2 into district should be part of setup.

Trusting unsourced rate and time promises

Unsourced claims such as delivery rate and cash-on-delivery success circulate about this firm on the internet. You need to take times, rates and fees from your contract; promising your customer based on promotional copy produces returns directly.

SCENARIO

Three common problems and how we solve them

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

Days were lost looking for an app

ProblemThe store decided to work with Kargoist and looked for an app that belongs to it in the app store. Because they could not find one they first thought the search term was wrong, then thought the firm did not support Shopify, and setup stayed on hold for more than a week.

CauseWhat they were looking for did not exist. This firm has neither its own app nor a third-party app built only for it; the only verified path is going through the supported-firms list of a multi-carrier app. The firm is a carrier, not a panel.

SolutionA multi-carrier panel was set up and the firm was defined as a supported carrier. Because the same panel also carried a second shipping firm for out-of-coverage orders, the store had two carriers from a single setup; which city goes to which firm was written as a rule.

The credentials are correct but the connection is not built

ProblemAccess credentials had arrived from the branch and been entered into the panel. Still, every attempt was rejected. The team thought the credentials had arrived wrong, corresponded with the branch for two days, the same credentials were sent again and the result did not change.

CauseThe problem was not in the credentials. Among this firm's settings there is an address field that must be defined for access, and that definition had not been made. That is why the connection was rejected; because the identity credentials were correct the error was looked for in the wrong place.

SolutionThe address the panel connects from was taken from the tool provider and sent to the branch to be defined on the other side. In the same meeting the branch code to be used on the declaration was also taken, so a second block that would appear on the first shipment was closed in advance.

The shipping invoice came in far above the estimate

ProblemThe store had planned its monthly shipping cost to the rate on the checkout. On the first invoice the cost per shipment came in clearly above what was expected, and because the shipping charge taken from the customer stayed fixed the difference came straight out of margin.

CauseIn setup the option to declare every shipment with a fixed desi value was on, and the chosen value was below the real packages. Because the carrier measures the real desi the invoice was issued on the measured value; the difference between declaration and measurement repeated on every shipment.

SolutionProducts were split into three standards by package size and the declaration was set to be produced from those standards. The shipping rate at checkout was also rewritten to the same standards; so the charge taken from the customer and the incoming invoice sat on the same calculation.

STATION

Shopify Kargoist integration

Station is the tool we built to run order, label, tracking and collection flow from one panel. If you will use a second shipping firm for orders that fall outside the coverage area, seeing the two flows 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 Kargoist integration?

Setup starts with a corporate agreement; at this firm no path of shipping on the tool's bulk rate is visible. After the agreement the access credentials are sent on a request made to the branch. The credentials go into a multi-carrier panel, the address definition needed for access is made, address fields are corrected and a test shipment is made from a single order.

Is Kargoist a shipping firm or a shipping platform?

A shipping firm. It carries packages with its own branches and couriers; on the supported-firms table of integration panels it sits as one row in the same list as other shipping firms. The platform is the panel you connect it to. Setups that do not make this split look in the wrong place from the start.

Does Kargoist have a Shopify app?

It does not. The app store has neither the firm's own app nor a third-party app built only for it. The only verified path is going through the supported-firms list of a multi-carrier app. So a simple setup focused on one firm is not possible at this firm.

Where do I get my Kargoist API credentials?

You apply to the branch and state that you want integration credentials; one aggregator's setup note writes that the information is sent within a few days. No portal where you can produce the credentials yourself was found at this firm. Sending the request together with the agreement meeting is the way to close the wait in one pass.

What do access key and form identity mean?

This firm's identity pair is different from other shipping firms: an access key and a form identity are given instead of a customer code and a password. The two work together, so when one arrives and the other is missing the connection is not built. When you ask the branch for credentials you need to ask for both together.

Do I need to have an address defined for access?

Among this firm's integration settings there is an address field that must be defined for access, so the connection working depends on a fixed address having been defined on the other side. If you use a ready panel you need to take the address to be defined from your tool provider and send it to the branch. This is the place setup gets stuck most often, and the error is usually thought to be in the identity credentials.

Where do I find the branch code during the declaration?

Branch code is among the required fields of the declaration and is taken from the branch you made the agreement with. When you ask for access credentials you also need to ask for the branch code in the same meeting. If you have a single warehouse it is defined as a fixed value; if you ship from two warehouses, the rule for which order leaves with which code is written in setup.

Which cities does Kargoist distribute to?

Coverage is not all of Turkey; the firm is based in Istanbul and has branches in certain cities. Two third-party sources give different city and branch counts and both are old, so we do not give a number here. Ask for the current list in writing before the agreement; you will need a second shipping firm for out-of-coverage orders.

Can I ship with Kargoist without my own agreement?

On the visible table you cannot. On one aggregator's supported-firms table the no-agreement shipping column is unmarked for this firm, so no path of opening a shipment on the tool's bulk rate is found. At some other shipping firms this path is open; here you need to make your own corporate contract.

Which documents are asked for the agreement?

No published information was found on the documents asked for, the contract flow or the approval time, so we do not give a list in this firm's name. In the sector a tax plate, a signature circular and a monthly volume statement are generally asked for; you need to ask for the exact list at the start of the meeting.

Does Kargoist have a corporate panel?

No information was found on the firm's own customer panel: its name, scope and whether a label can be printed could not be confirmed. Because the corporate site shows a maintenance notice, what sits behind the login also cannot be seen. If such a panel is given, asking for access during the agreement makes your work easier.

Why does the Kargoist site not open?

As of 26 August 2026 the corporate site shows only a maintenance notice; the service page, frequently asked questions and contact page are not live, and the consumer tracking screen is also closed. No closure or transfer news was found, so the status is unclear. That is why we recommend speaking with the firm directly before the contract and confirming that operations are continuing.

Which sources is the Kargoist information compiled from?

Because the firm's official sources cannot be read right now, the information here was compiled from the help documents of integration panels, from the technology press and from connection code published by an independent developer. Topics that could not be confirmed we wrote into the checklist instead of guessing; we also did not pass on unsourced rate and time claims.

Which integration panel should I choose?

At this firm panel choice is more decisive than at the others. You need to ask two questions: is the tracking number written on the Shopify order automatically, and is this firm in the standard scope. One aggregator does not list Shopify among the platforms it writes the tracking number on, another offers this firm as a paid and optional extra module.

When is the tracking number added to the order?

After the package enters the branch and the barcode is scanned. The barcode given during the declaration is the reference the firm uses to recognize the package; the tracking number is assigned after the package enters the flow. That is why the number is written on the order after the package enters the system, not at once.

If the tracking number never arrives, what should I check?

Look at four things in order: did the shipment declaration actually form, did the package enter the branch, does the panel you use write the tracking number on the Shopify order, and is the phone field on the shipping address filled. At this firm the third item is especially important, because one aggregator does not list this platform on its automatic-write-to-Shopify list.

If I cancel the order, is the shipment cancelled too?

It does not happen on its own; the declaration must be cancelled as well. At this firm the barcode number must be unique, so a declaration cannot be given again with the same number after a cancel; a new number is produced. On an address change the declaration is also cancelled and created again.

Does Kargoist do cash on delivery?

Charge type is among the declaration fields and cash-on-delivery by card sits as a separate value, so cash-on-delivery shipments are supported and the type is chosen at shipment level. No published information was found, though, on how long the money takes to reach the account or on the collection service fee; you need to take both lines from your contract.

Where do I choose the collection type?

At declaration time. At this firm charge type is one of the declaration fields: bulk shipment, a shipment the receiver pays for, prepaid and cash-on-delivery by card sit as separate values. Which order leaves with which value is tied to a rule in the integration; the Shopify counterpart is setting the payment method up as manual.

How is cash on delivery set up on the Shopify side?

In Settings, under payments, cash on delivery sits as a ready manual payment method. On such an order, payment opens as pending and is marked paid after collection happens. Restricting by region, setting an amount limit or adding a cash-on-delivery fee are not built into Shopify; those are solved with rate setup or an extra app.

How do I manage return processes?

No published information was found for this firm on whether the return code is fixed or one-time, or whether an easy-return agreement exists, so we do not claim a model. If you have return volume you need to settle the flow in the contract; otherwise every return is run by hand. Shopify's own return-label production flow does not work in Turkey.

What format is the label printed in?

No source was found on the label format for this firm; whether it arrives as a document or in a thermal-printer language could not be confirmed. If you will buy a thermal printer you need to ask this both to the firm and to your tool provider. The common size in ecommerce is a fifteen-by-ten-centimeter label; printing a label that arrives as a document on large paper shrinks the barcode until it will not scan.

Are shared barcode and split shipment supported?

On one aggregator's capability table, shared barcode and split shipment are marked as supported at this firm; cumulative shipment and marketplace shipping sit as not supported. On the same table no-agreement shipping is also unmarked. This information comes from a single third-party source, so confirming it in setup is good.

Does Shopify's own shipping label work in Turkey?

It does not. Shopify's own shipping is tied to shipping origins in eight countries and Turkey is not on that list; that is why the buy-a-label flow never appears on the order screen. The label is printed from the carrier's own system or from an integration. A return label can also be produced only inside the United States.

Can checkout show a live shipping rate?

Not with Turkish shipping firms. Pulling a live rate from the carrier's own account is available only on higher plans, and the supported carrier list has no Turkish firm. So the shipping charge at checkout in Turkey is a fixed or conditional rate you set by hand; you need to set it to your real cost.

How is a district field added at checkout?

On plans other than Plus you cannot add city and district pickers at checkout; a Shopify employee confirms this in a reply to a request from Turkey. The path used in the field is one: address line 2 is made required in checkout settings and renamed to district by editing the checkout language. At this firm the declaration wants city and district as separate and written correctly, so this correction is part of setup.

Does declaring with a fixed desi make sense?

One panel has an option to send every shipment with a fixed desi value and it is used a lot in practice. This simplifies the calculation, but it is a decision: if you choose the fixed value above your real packages you overpay, if you choose it below the carrier measures the real desi and the difference hits the invoice. The right path is defining your package standards and producing the declaration from them.

Why did my invoice come in higher than I expected?

The most common reason is the desi declaration. Because the Shopify product card has no length, width or height field, some integrations declare the shipment with a fixed desi; the carrier measures the real desi and the invoice is issued on the measured value. The shipping charge you took from the customer stays fixed, so the difference comes straight out of margin.

Does the app set the shipping price?

It does not. The rate comes from the agreement you made with the carrier and the invoice comes to you from the carrier; the integration only carries the data. At some firms, stores without their own agreement can ship on an intermediary's bulk rate, but at this firm that path is not visible, so the rate is directly your contract.

Can I use it together with a second shipping firm?

It is more accurate to say you need to. Because coverage is not all of Turkey, some of your shipments will leave from another firm. That is why the panel you use being multi-carrier is a requirement; you also need to define in setup the rule for which city goes to which firm.