On this page
Turkish ecommerce return rates run around 25-26%, well above the EU average, yet ikas — one of the fastest-growing platforms for Turkish and MENA fashion brands — has almost no dedicated sizing tools in its app ecosystem. That gap is costing merchants money every single day a shopper guesses wrong and sends a package back.
ikas has become the default platform for a new generation of Turkish fashion brands moving off marketplaces and off legacy platforms like Ticimax or T-Soft onto something built for modern headless commerce. But app ecosystems take years to mature, and sizing — one of the single biggest levers on apparel return rates — is still a thin category on ikas compared to Shopify's crowded app store. For a merchant selling denim, outerwear, or fitted knitwear, that's not a minor gap. It's a live revenue problem.
Why Sizing Tools Lag Behind on ikas
ikas launched with a strong focus on checkout speed, localization for Turkish payment methods, and marketplace sync — not on the long tail of merchandising apps that Shopify has spent over a decade accumulating. That's a reasonable sequencing choice for a young platform, but it means categories like size recommendation, virtual try-on, and fit analytics simply haven't been built out yet by the ecosystem.
The practical effect: a Turkish fashion brand running on ikas today typically has two options. Either it ports over a static size chart image (the default on most template themes) or it goes without any sizing guidance at all beyond a product description note. Neither approach touches the actual behavior driving returns — shoppers who aren't sure whether they're a Medium or Large, and who either abandon the cart or order two sizes and return one.
What Turkey's Return Rate Actually Means for ikas Merchants
A 25-26% return rate is not an abstract benchmark — it's a direct hit to margin on every fitted or sized item a store sells. For comparison, the National Retail Federation has pegged the US online apparel return rate closer to 19-20%, and even that lower number is treated as a structural cost problem by US retailers. Turkey running several points above that average means local fashion brands are absorbing return shipping, restocking, and lost-sale costs at a rate most Western retailers would consider a crisis.
Layer on top of this that apparel and footwear return rates run well above other retail categories — shoes in particular are consistently among the highest — and the picture for an ikas store selling clothing or footwear gets sharper. Every product page without clear sizing guidance is a small bet against that 25-26% number, repeated across every order.
Cargo economics in Turkey make this worse than in many Western markets. Return shipping through domestic cargo carriers is not free for most merchants, and a bracketed order (a customer buying two sizes to keep one) doubles the outbound cost while only returning revenue on one unit. Reducing bracketing behavior specifically — not just returns overall — is one of the highest-leverage moves available to an ikas merchant right now.
Building a Size Recommendation Flow Without a Native App
Because ikas doesn't yet have a mature native app for this, most merchants reach for one of three approaches, each with real tradeoffs:
| Approach | Effort | Accuracy | Maintenance |
|---|---|---|---|
| Static size chart image | Low | Low — no personalization | None |
| Manual size guide page + FAQ | Low-Medium | Low-Medium | Ongoing content updates |
| Embedded third-party widget | Medium | High — personalized recommendation | Low once integrated |
A static chart asks the shopper to do the conversion work themselves, cross-referencing body measurements they usually don't have on hand. A manual guide page helps slightly but still requires the shopper to self-diagnose. An embedded widget — a script or iframe placed on the product page — shifts that cognitive load onto the tool: the shopper answers a few quick questions or inputs basic measurements, and gets a direct size recommendation for that specific product, not a generic chart.
For an ikas store, the embedded widget route is usually the most realistic near-term path, since it doesn't require waiting on ikas's own app store to catch up. It works by injecting a small snippet or embed on the theme's product template, which is well within reach on ikas given its flexible theme editor and API access for developers who want deeper control.
Where YourSizer Fits
YourSizer is a virtual sizing and try-on widget designed to drop onto a product page regardless of the underlying platform, which matters directly for ikas merchants who can't wait for a native size-recommendation app to appear in the ecosystem. Instead of a static image, shoppers get a short, guided flow that turns their inputs into a specific size recommendation for that product, informed by the brand's own size chart and fit data.
For Turkish fashion brands specifically, this addresses the return-rate problem at its source rather than after the fact. A recommendation shown before checkout costs nothing if it's wrong; a return shipped through domestic cargo after checkout costs real money on every bracketed order. Merchants evaluating this path can review how to choose a size recommendation solution before committing to an integration, since the right fit depends on catalog size, product complexity, and how much developer time is available for theme-level embedding versus a lighter no-code approach.
What to Expect After Adding a Sizing Widget
Based on returns patterns we see across fashion brands using YourSizer, the first measurable shift is usually in bracketing behavior — fewer customers ordering two sizes just to hedge their bet — rather than an instant collapse in overall return rate. That's a meaningful distinction for an ikas merchant modeling ROI: the near-term win is fewer double-size orders and the cargo costs that come with them, with the broader return-rate improvement compounding over subsequent months as the tool accumulates fit data on the catalog.
It's also worth setting expectations against a global returns cost that already runs past $40 billion a year for fashion brands, according to McKinsey — a figure that makes clear this isn't a Turkey-specific inefficiency but a structural one across fashion ecommerce that happens to hit harder in markets with above-average return rates.
Frequently Asked Questions
Does ikas support third-party embedded widgets on product pages?
Yes. ikas's theme editor and storefront API allow merchants to embed custom scripts and components on product templates, which is the same mechanism used to add live chat, reviews widgets, or upsell tools. A size recommendation widget can be added the same way, typically by a developer inserting a small snippet into the relevant theme section or by using an app-block style integration if one is available for the platform.
Will a sizing widget slow down my ikas store's page speed?
A well-built widget loads asynchronously and only activates when a shopper opens it, so the impact on initial page load should be minimal if implemented correctly. It's worth asking any vendor how their script loads — synchronous, render-blocking embeds are the main way a third-party tool can hurt Core Web Vitals, and that's avoidable with proper lazy-loading.
Is a size recommendation tool worth it for a small ikas catalog?
Even a catalog of a few dozen fitted SKUs can carry meaningful bracketing and return costs, especially at Turkey's return-rate levels. The setup effort for a widget is usually low relative to the ongoing cargo and restocking costs saved, and smaller catalogs often see faster payback simply because there's less product-by-product configuration required to get the tool live.
How is this different from just posting a detailed size chart?
A size chart asks the shopper to measure themselves and interpret which row applies to them, which is exactly the step most people skip or get wrong. A recommendation flow does that translation for the shopper based on a few inputs, which is why it tends to outperform static charts on both conversion and return rate — the comparison is laid out in more detail in size chart vs size recommendation.
Conclusion
ikas's app ecosystem will eventually catch up on sizing tools the way Shopify's did, but Turkish fashion merchants don't have to wait for that to happen — the same embed-based approach that works on more mature platforms is available today through the theme editor and API access ikas already offers. Given how much of Turkey's above-average return rate is tied to sizing uncertainty and bracketing, closing that gap now is one of the more direct ways an ikas store can protect margin while the platform's own app catalog matures around it.
