A home-textiles brand on ikas is doing about 70 orders a day. The setup works: the ikas Kargo app is installed, three carriers are stacked in a priority list, labels come out in a batch every afternoon, tracking numbers flow back into the order records. Nothing is on fire.
But three things quietly bother the owner. First, she has no idea whether the carrier at the top of her priority list was the right choice for any given parcel — it's just the one that's first. Second, her inbox fills up every morning with "where is my order?" messages, even though the tracking number went out hours ago. Third, when her Aras deliveries started running two days late in one region last month, she found out from customer complaints, not from a report.
None of these are ikas failing at its job. ikas is a genuinely good storefront — fast, modern, built in Turkey for Turkish commerce, and its shipping features are far better than what most platforms ship with. The problem is a category difference: a store platform's job is to sell, and shipping features inside it are a means to get orders out the door. Running a shipping operation — pricing every parcel against alternatives, owning the post-purchase conversation, and measuring which carrier is actually costing you money — is a different job with different tools.
This guide is a straight assessment. What the ikas panel handles well (and you should keep using), the four specific places it stops, when in your growth that gap starts costing real money, and how to layer a shipping operation on top of ikas without touching your storefront.
What ikas Already Gives You
Start here, because a lot of advice in this category is written as if platform-native shipping doesn't exist. It does, and on ikas it's reasonably complete.
ikas Kargo — the platform's own contracted rates. Install the app from the ikas App Store and you get access to ikas's negotiated pricing with a set of carriers: currently Yurtiçi Kargo, Aras Kargo, HepsiJet, DHL, and Kolay Gelsin. There's no setup fee — you install it and pay only for what you ship, funded from a prepaid ikas Wallet balance. Pricing is desi-based and, notably, flat across the country: the same desi costs the same whether the parcel goes across town or to the far side of Turkey. Some of the agreements include pickup from your address.
Your own carrier agreements, connected separately. ikas also has standalone carrier integrations — Aras, Yurtiçi, DHL eCommerce, UPS, HepsiJet, Kolay Gelsin — that are explicitly not ikas's rates. You negotiate with the carrier yourself, then plug your own credentials in and ship on your own pricing. There are logistics integrations for other jobs too (ShipEntegra and Navlungo for cross-border, Oplog for fulfillment, Sendcloud as a shipping layer).
Bulk actions on the order list. You can select orders and approve them in bulk, and print shipping labels and invoices in bulk rather than one at a time. The order list filters usefully — for example, orders whose label has been printed but whose invoice hasn't.
Two carrier-selection modes. ikas Kargo lets you either rank carriers with a drag-and-drop priority list (the system tries the first, falls through to the next until one succeeds) or pick the carrier manually on every order.
A couple of setup requirements worth knowing before you blame the integration: you need at least one fully configured warehouse location, and customer phone numbers are mandatory for barcode generation.
Here's the honest verdict: if you're shipping 10–20 orders a day with one or two carriers on your ikas store and nothing else, this is enough. Use it. You do not need another tool to solve a problem you don't have yet. The rest of this guide is about what changes when you grow past that.
Where It Stops: Four Gaps That Show Up at Volume
1. A priority list is not rate comparison
This is the most expensive misunderstanding in platform-native shipping, and it's subtle because the feature looks like carrier choice.
A drag-and-drop priority list answers the question "if carrier A can't generate a barcode, who's next?" That's a reliability fallback. It does not answer "which of my available options is cheapest for this parcel, to this district, at this desi?" — which is a cost decision. With a priority list, the answer to the cost question is always "whoever I put first," on every order, forever.
Flat national pricing makes this bigger, not smaller. A single desi price for the whole country is genuinely convenient — but it means intra-city parcels are quietly subsidizing cross-country ones, and you can't see it. Meanwhile the alternative rate structures in the market look different: publicly reported 2026 e-commerce desi rates vary meaningfully by carrier, and every carrier applies its own minimum charge on top. Which structure wins depends entirely on your actual parcel mix — desi distribution, destination spread, COD share.
The cost of not comparing is a number you can calculate for your own store:
Monthly leak = monthly orders × average per-parcel gap between the carrier you used and the cheapest suitable option
Run it with your own numbers rather than trusting an example, because the answer is very sensitive to your mix. At 1,500 orders a month, a gap of even a few lira per parcel is a five-figure annual number — for a decision nobody is making, on purpose, on any order.
Fix it: the shipping layer should price every order against every option you have access to at the moment you create the label, and route accordingly. That's rate shopping inside a multi-carrier strategy, and it's one of the highest-leverage items in reducing shipping costs. Separately, once you have volume data you can use it to negotiate better agreements — evidence beats asking nicely.
2. Your own rates and the platform's rates never compete on the same screen
ikas supports both models — its own contracted pricing through ikas Kargo, and your negotiated agreements through the standalone carrier integrations. What it doesn't do is let those two compete, per parcel, in one place.
That matters more than it sounds. The realistic setup for a growing Turkish store is mixed: a good negotiated deal with one carrier on your bread-and-butter desi range, platform rates as a useful floor elsewhere, and a fast urban carrier for same-city orders. The right answer for a 2-desi Istanbul order and a 12-desi order to Van is often not the same carrier — and it's certainly not the same carrier as whoever happens to be at the top of a list.
Cash on delivery sharpens the point. COD is still a large share of Turkish e-commerce, and in 2026 it's priced as a separate value-added service on top of the desi charge, with the fee varying by carrier and by collection method. If a meaningful slice of your orders is COD, the carrier that's cheapest on plain parcels may not be cheapest once the COD fee lands — and that comparison has to happen at label time, per order, or it doesn't happen at all.
Fix it: you want one screen where your own agreements and any platform-provided rates are both live options, priced for the parcel in front of you.
3. The post-purchase experience belongs to the carrier, not to you
This is the gap that shows up in the support inbox.
ikas passes tracking numbers back into the order record and updates order status. Customer-facing notification, though, largely rides on the carrier: the DHL eCommerce integration, for instance, has an option to let DHL send status SMS if your agreement includes it. That's a reasonable arrangement, but look at what it means in practice — the message content, its timing, which statuses trigger it, and whose brand it appears under are all decided by the carrier, not by you. And if the customer wants to check on their own, they end up on a carrier's tracking page, which is where your brand experience ends and a logistics company's begins.
The predictable result is WISMO. "Where is my order?" runs 35–60% of e-commerce support contacts across multiple industry sources, and it's the highest-volume, lowest-value work your support person does — because in most cases the customer is asking for information you already had and didn't send. Proactive notifications that actually reach people reliably cut WISMO volumes by 40–80%. The stakes go beyond ticket cost: roughly 70% of shoppers won't buy again after a bad delivery experience, and much of what makes a delivery feel "bad" is silence rather than slowness.
Fix it: own the post-purchase channel. That means a branded tracking page on your domain instead of a carrier's, automatic notifications you control on the status changes that actually matter, and a clear estimated delivery date set before the customer has a reason to ask. Channel choice matters as much as content — WhatsApp is now the most-used app in Turkey, reaching 88.6% of individuals per TÜİK's 2025 figures, so a shipping update sent there gets read in a way an email often doesn't. If your support inbox is the symptom you care about most, the WISMO cost math is the place to start.
4. You can't see which carrier is actually costing you money
Ask your current setup a simple question: last month, which carrier had the worst on-time rate on my routes, and what did each one cost me per successfully delivered order?
Platform shipping features generally can't answer that, and ikas is no exception — there's no per-carrier performance reporting layer. You can see individual orders and individual tracking states. What you can't see is the aggregate: on-time rate against the date you promised, transit-time variability, first-attempt delivery rate, exception rate, damage and claim rate, and true cost per delivered order rather than per label printed.
Without that, carrier decisions get made on vibes and on whichever complaint is loudest this week. The textiles brand in the opening found out about a regional slowdown from customers — a per-carrier, per-route report would have shown it in the first week, while it was still a routing decision instead of a refund conversation.
Fix it: measure each carrier separately, by route, on a monthly cadence, and act on it — route by performance, rebalance volume, renegotiate with evidence, replace when it doesn't improve. Carrier performance scorecards covers the six metrics and how to build the review; shipping KPIs covers the store-wide layer above it.
A fifth, if you sell anywhere besides your ikas store
Plenty of ikas merchants also sell on Etsy, on Trendyol, or through a second storefront. The moment that's true, "shipping" stops being a single-panel problem: orders scatter, deadlines compete, and the channel with the loudest clock — usually the marketplace — starves the rest. That's a structural fix, covered in multichannel order management and, for the marketplace specifically, Trendyol order and shipping management.
When the Gap Starts Costing Real Money
There's no universal threshold, but the crossover is usually somewhere around 30–50 orders a day, and it's driven by four things rather than volume alone:
- Carrier count. One carrier means nothing to compare. Two or more, and every order is an uncosted decision.
- Parcel-mix spread. If your orders are all the same size to the same cities, a flat rate is fine. Wide desi and destination spread is where per-order routing starts paying.
- COD share. COD fees are large enough that a meaningful COD share changes which carrier is cheapest.
- Support load. Once one person spends real hours a week on tracking questions, notification infrastructure is cheaper than that person's time.
Practical signals that you're past the line:
- Shipping prep still expands to fill the afternoon, no matter how you reorganize it
- You've been asked "why is our shipping cost per order going up?" and couldn't answer with data
- A carrier problem reached you through customers rather than through a report
- You've considered outsourcing fulfillment mainly because the shipping day is exhausting
- Nobody at the company can say which carrier performed best last month
That last one is the tell. If the answer isn't available, no amount of negotiating or carrier-switching is going to be more than a guess. The trajectory here is the same one in scaling shipping operations from 10 to 1,000 orders a day: what breaks isn't capacity, it's the fact that decisions that used to be trivial now need data.
How to Layer a Shipping Operation on Top of ikas
The important framing: this is not a replacement for ikas. Your storefront, catalog, checkout, and customer records stay exactly where they are. You're adding a layer that takes over from the moment an order is paid.
Here's what that looks like with Shipink's ikas integration:
1. Connect the store once. You connect your ikas store, and from then on orders import automatically into one queue. Nobody refreshes a panel looking for new orders.
2. Bring your own agreements — or use ours. You can plug in your own negotiated carrier agreements, cash on delivery included, and you can attach several carrier accounts to the same sales channel. If you don't have agreements yet, or yours are weak at your current volume, Shipink's pre-negotiated rates are available from day one across 16 carriers — no volume commitment, pay per shipment. That combination is the point: your rates and ours, live on the same screen, competing per parcel.
3. Compare rates on every order. Rates are fetched and compared automatically, so the routing decision happens per parcel instead of once, months ago, in a priority list.
4. Print in bulk and let rules handle the routine. Batch label printing turns the afternoon block into a few minutes, and automation rules take the repetitive decisions — which carrier for which order profile, how to handle oversized or COD orders — off a human. Getting the label itself right matters more than it seems: bad address data is where surcharges and re-invoiced desi differences come from, and AI-assisted address correction catches a large share of it before the parcel moves.
5. Own the post-purchase channel. Automatic WhatsApp, SMS, and email notifications on status change, from your brand, plus a branded tracking page on your domain and alerts on delays and exceptions — so customers get the answer before they ask for it. (WhatsApp notifications are available on the Pro plan and above.)
6. Measure per carrier. Delivery performance reporting by carrier — on-time and success rates, cost and desi analysis, returns and damage — so next month's routing and next quarter's negotiation both run on evidence.
7. Close the loop with invoicing. Since the order data is already there, e-fatura and e-arşiv invoicing can be generated from it rather than re-typed at month-end. The e-invoicing guide covers the timing and legal side.
Two tests to aim for:
- Can you finish an entire shipping day without opening a carrier's own portal?
- Can you answer "which carrier cost me the most per delivered order last month" in under a minute?
If the answer to both is yes, you have a shipping operation. If either is no, you have shipping plumbing — which is fine at 15 orders a day and expensive at 70.
What Not to Change
Restraint is part of doing this well, and this is where a lot of merchants overcorrect:
- Don't rip out ikas Kargo if it's working for you. Platform-contracted rates are often genuinely competitive at low and mid volumes, especially if you haven't negotiated anything yourself. The goal is to have it as an option among others, not to remove it.
- Don't chase the cheapest rate at the cost of on-time delivery. The cheapest carrier that fails 8% of first attempts is not cheap — you pay it back in re-delivery, failed-delivery costs, support time, and lost repeat purchases. Route on cost within an acceptable performance band.
- Don't add carriers you can't measure. Five carriers with no scorecard is worse than two with one. Add capacity only as fast as you can evaluate it.
- Don't change your storefront to solve a shipping problem. Replatforming because shipping hurts is a very expensive way to fix the wrong layer.
Your ikas Shipping Checklist
Cost
- Every order is priced against all your available carrier options, not routed by a fixed priority list
- Your own negotiated agreements and any platform rates are both live options on the same screen
- COD fees are included when you compare carriers, not discovered on the invoice
- You know your true cost per delivered order, per carrier — not just per label
Workflow
- ikas orders import automatically; nobody refreshes a panel for new ones
- Labels print in bulk, and routine routing decisions are handled by rules
- Address problems are caught before the label is created, not after a failed delivery
- Invoices are generated from order data, not re-typed at month-end
Customer experience
- Customers get proactive shipped / out-for-delivery / delivered / delay notifications from your brand
- Tracking lives on a branded page on your domain, not only on the carrier's site
- An estimated delivery date is shown before the customer has a reason to ask
- WISMO contacts are trending down and you're measuring them
Measurement
- You review per-carrier on-time, exception, and damage rates monthly
- Carrier problems reach you through a report, not through complaints
- You can name last month's best and worst carrier on your main routes
Keep the Storefront. Upgrade the Operation.
The reason platform-native shipping feels adequate for so long is that it is adequate — right up to the point where the decisions it makes for you start being wrong often enough to matter. A priority list that was a sensible default at 15 orders a day is, at 70, a standing decision to not price 2,000 parcels a month. Notifications the carrier sends were fine when your brand was new and the tracking link was just a link; now the post-purchase weeks are most of the relationship you have with a customer. And a carrier roster you can't measure is a roster you can't improve.
None of that is an argument against ikas. It's an argument for putting the right tool on the right layer: keep the storefront that's working, and stop running your fulfillment out of it.
If you're on ikas and any of the four gaps above sound like your week, the fix is additive and reversible. Connect your ikas store to Shipink — your orders flow in automatically, your own agreements and ours compete on every parcel, your customers hear from you instead of a carrier, and at the end of the month you can finally say which carrier earned its volume. Shipink is free to start, with no volume commitment.
