Horizon research dossier · Türkiye · Digital, ICT and innovation · reviewed 2026-10-11
Türkiye digital commerce: a full decision dossier for a defined channel and operating proposition
Decision question: Under what evidence conditions should an overseas brand, marketplace service, technology company or exporter advance a Türkiye digital-commerce proposition to a controlled commercial pilot?
Verified facts
Official reporting documents substantial domestic e-commerce activity, category and payment patterns, but it does not establish an individual seller’s eligibility, customer demand, platform terms or delivery performance.
Horizon view
Türkiye warrants a detailed channel test for defined offers; national market scale alone does not determine the correct route or viable economics.
Commercial implication
Advance only after confirming buyer/channel, seller-of-record, product/documentation, payments, fulfilment, returns, service and contribution-margin evidence.
Dossier sequence
01
1. Decision scope and non-claim boundary
This dossier assesses a defined digital-commerce proposition in Türkiye. It does not say that a product can be sold, that a platform will accept it, that a foreign seller may operate without a local structure, or that a delivery route is commercially viable. The initial brief must specify the offer, category, customer, price position, target geography, sales channel, seller of record, product/documentation status, fulfilment promise, returns owner and decision horizon. The relevant question is whether a specific customer can receive, pay for, return and be supported for a specified product or service through an accountable operating model. “Large e-commerce market” is a context signal, not a route-to-market decision.
02
2. Dated market evidence
Türkiye’s Ministry of Trade reported 2025 e-commerce volume above TRY 4.5 trillion and retail e-commerce volume of TRY 2.46 trillion. It also reported a large number of e-commerce businesses and category-level patterns. These figures show domestic scale and can help frame category research. They do not prove traffic, conversion, listing acceptance, customer acquisition cost, contribution margin, payment settlement, returns exposure or sales for a particular foreign offer. The evidence log must retain publisher, report period, population, category definition and currency. Domestic e-commerce volume should not be merged with cross-border sales or used to infer a specific marketplace’s performance.
03
3. Product and customer unit
The market unit must be narrow: one SKU or service bundle, target customer profile, intended price band, purchase trigger, delivery promise and competing alternative. Apparel, accessories, beauty, home, B2B products, software services and marketplace enablement have distinct return patterns, information requirements, margins and operating obligations. The customer map should distinguish end user, purchaser, merchant, marketplace, fulfilment provider, importer, payment owner, customer-service owner and marketing decision maker. A national category statistic cannot establish whether a customer wants the particular proposition. The research target is evidence of a repeatable customer problem and a channel that can solve it at a viable cost. The segmentation record should preserve why each target group is in scope, the evidence supporting the assumption and the evidence that would disprove it. In practice this means recording price sensitivity, brand familiarity, local product alternatives, service expectations, delivery tolerance and potential reasons for return or abandonment rather than assuming that a strong category number applies to every offer.
04
4. Channel and seller-of-record architecture
The channel design must identify who contracts with the customer, invoices, receives payment, owns inventory, handles platform administration, processes returns, carries consumer-facing obligations and controls customer data. Direct cross-border sale, marketplace sale, local distributor, local entity, marketplace integrator and hybrid fulfilment arrangements allocate these responsibilities differently. The model should include an operating-responsibility matrix rather than call every local organisation a “partner”. A seller-of-record question is decisive because it affects payments, documentation, customer communication, tax and returns. A platform conversation or preliminary commercial discussion is discovery evidence only; it does not validate a legal, operational or economic model.
05
5. Product, import and documentary gate
No country or e-commerce statistic can determine treatment of a particular product. Before a sample, listing, advertisement or sale, establish product classification, required tests or certificates, labels and product information, origin evidence, import/export documentation, customs process, restricted substances or sector-specific rules, importer/seller responsibilities and customer-facing claims. The document matrix should name issuer, language or translation requirement, validity, product/SKU relevance, responsible party, review date and escalation path. This dossier is not customs, consumer or product-compliance advice. It ensures that a channel test cannot proceed on the unsafe assumption that a product can be listed simply because a marketplace or digital-sales route exists.
06
6. Payments, fraud and settlement
Payment statistics provide context, not confirmation of acceptance or settlement conditions for a given seller. The implementation file must identify payment method, acquirer or payment-service role, merchant onboarding requirement, settlement currency and cycle, reserve or holdback, fraud monitoring, chargeback and dispute process, customer refund route and financial owner. These mechanics affect cash conversion as much as a retail price or ad budget. A national prevalence of card payments does not establish that a foreign entity, product category or marketplace account can use the desired payment arrangement. The model should test a base and adverse settlement scenario and identify the point at which a chargeback, refund or failed collection changes the proposition from profitable to loss-making. It should also establish whether customer funds, marketplace proceeds and partner commissions are reconciled at order, shipment, delivery or return level, and who investigates discrepancies. A payment flow that cannot be reconciled cannot be safely scaled even if early sales figures appear encouraging.
07
7. Fulfilment, returns and customer service
The delivery architecture must specify origin, stock location, fulfilment party, order cut-off, packaging, track-and-trace, delivery commitment, failed-delivery process, return address, customer support language, complaint handling, replacement/refund authority, damage claims and reverse-logistics cost. Cross-border delivery is not merely domestic e-commerce plus freight: it creates additional documents, timing and customer-expectation risk. A provider’s website, a generic route description or a headline delivery estimate is not shipment evidence. The pilot must use current written terms and measure actual fulfilment, cancellation, return, complaint and payment experience. A brand should not promise delivery performance until the operating chain has been tested for the relevant product and geography. The operating test should identify the exact event that triggers a refund, return, replacement or claim, which party pays each cost and how damaged or returned stock is inspected and recorded. Those details determine customer satisfaction and margin more than a generic express-delivery capability statement.
08
8. Commercial and unit-economics model
The model should connect customer price to landed cost, marketplace or channel commission, payment cost, fulfilment, delivery, return/resale/destruction, customer service, advertising, promotion, partner margin, tax treatment, currency, working capital, stock loss and warranty. It must distinguish observed competitor price, supplier quote, platform indication and internal assumption. A large market number cannot validate a contribution margin. Test a base, promotion and adverse-returns case, and record the maximum customer-acquisition and return cost that the proposition can absorb. The first objective is not revenue volume but proof that one product/channel combination can sustain the delivery and service obligation it creates. The calculation should be reviewed against actual pilot data after a defined order count rather than only at campaign end. That makes it possible to stop a loss-making configuration early and distinguish a temporary launch cost from a structural gap in price, return, fulfilment or acquisition economics.
09
9. Marketplace and local counterparty diligence
If the route involves a marketplace, integrator, distributor, fulfilment provider, agency or customer-service operator, assess it as an accountable counterparty. Verify legal identity, ownership, contracting authority, platform permissions, product/category fit, warehouse/service footprint, payment settlement, data practices, customer support, conflicts, reporting, financial capacity and exit/transition terms. A local presence should solve an identified operating gap rather than provide only a logo or introduction. References must be relevant to the actual category, service level and payment flow. No listing, meeting or directory entry is enough to create a public or internal partner recommendation without current diligence evidence.
10
10. Marketing, claims and customer acquisition
Customer acquisition needs its own evidence plan. Define target audience, permitted product claims, content owner, local-language adaptation, advertising budget, attribution rule, promotion authority, marketplace search/discovery mechanism, influencer or affiliate terms where used, data access and feedback loop. Visibility does not equal demand, and campaign impressions do not establish profitable customer acquisition. Product performance, health, sustainability, delivery or pricing claims need substantiation and appropriate review. The first marketing test should have a limited budget, an attributable channel and pre-agreed measures such as qualified traffic, conversion, repeat purchase, return and margin. It should stop if the resulting economics cannot sustain the channel and service model.
11
11. Data, platform and technology control
A digital-commerce route creates data and system responsibilities that must be allocated. Identify account owner, platform access, customer-data controller, data categories, APIs/integrations, hosting, retention, identity management, contractor access, incident protocol, analytics rights, reporting cadence and handover obligations. A third party should not be granted broad access simply to speed up a launch. The Review corpus must contain no customer identities, private account data or credentials. Any future operational implementation requires its own authorised security, contractual and privacy controls. A dashboard, demo account or platform connection does not prove permission to use production data or demonstrate the reliability of a live order flow.
12
12. Pilot design
A valid pilot tests one bounded proposition: defined product/service, customer segment, channel, seller-of-record model, fulfilment route, budget, inventory level, timing, support, data rules and decision owner. It may be a controlled listing, a limited customer-account test, a marketplace onboarding, a technology integration or a sample-order programme. The scorecard should include onboarding completion, listing approval where relevant, qualified traffic, conversion, gross margin after all direct costs, payment collection, cancellation/return rate, delivery performance, support incidents and evidence of repeat demand. A summit, marketplace conversation or generic partner meeting is not a pilot. A successful pilot produces a documented go, hold or stop decision, not merely a report of activity. The charter should specify how inventory, customer questions, content assets, test credentials and remaining refunds are handled at close, who can expand scope, and what conditions require immediate pause. This protects the pilot from becoming an unbounded retail launch without tested responsibilities.
13
13. Contracting and governance
Before scale, the parties must define contract scope, territory, product set, exclusivity if any, minimum performance, price authority, inventory ownership, payment, data rights, marketing approvals, service levels, product claims, compliance responsibility, audit/reporting, confidentiality, IP, termination and transition. The contracting party must have authority to give the commitments described. A distributor or integrator cannot resolve a contract that leaves consumer obligations, returns, stock or data responsibilities undefined. The dossier should mark each required term as confirmed, proposed, unresolved or requiring specialist review. A verbal commercial intention does not establish a governance model. Contract review should make explicit how a marketplace account, customer record, product content, advertising asset and remaining inventory are transferred or closed when the relationship ends. If the answer depends on a platform or third party, the record must cite the applicable current term rather than rely on a partner’s informal explanation. Governance should be adequate for the pilot before it is used as the basis for scale.
14
14. Risk register and stopping conditions
Key risks include unavailable product documentation, rejected platform or merchant onboarding, unsuitable payment settlement, excessive customer-acquisition cost, high return or failed-delivery rate, currency and working-capital exposure, opaque partner performance, data/security issue, misleading claim, customs or return problem, service failure and loss of brand control. Each risk needs an owner, evidence source, mitigation, residual risk and explicit stop condition. Stop before promising consumer availability, granting exclusivity, committing bulk stock, extending credit, sharing sensitive data or spending beyond the pilot budget if the core product, payment, delivery or counterparty evidence is unresolved. An evidence-based stop is a successful outcome when it prevents a poorly governed market entry. The register should distinguish a risk that can be tested within the pilot from a structural exposure that cannot be solved by better marketing or a temporary discount. This makes the escalation decision transparent and prevents the team from treating every operational failure as merely a launch-learning cost.
15
15. Final decision gate
Advance only when the defined offer, named customer/channel path, seller-of-record, product/documentation package, payment and fulfilment model, unit economics, accountable counterparties and controlled pilot align. The decision record must distinguish verified facts from Horizon interpretation, identify outstanding matters, record specialist confirmation needs, name the approver and set a review date. A go outcome permits only the bounded step in the record; it does not authorise a public claim, unrestricted launch, exclusive mandate, customer-data transfer, credit commitment or capital investment. Reopen the dossier after a material product, channel, payment, document, counterparty, regulation or operating change. This is a research instrument, not a marketplace, customs, legal or commercial guarantee. The final outcome must be recorded as go, hold or stop, with the reason, conditions precedent, accountable owner and expiry date for time-sensitive evidence. A commercial deadline or platform invitation does not override an unresolved document, payment, fulfilment, customer-service or counterparty-risk issue. The evidence package must be retained so later activity cannot present an early exploratory test as an approved market launch. The decision owner must report material deviations promptly and obtain a fresh review before expansion. A hold is mandatory when the evidence is incomplete. All exceptions require written risk ownership and date-bound reassessment. The record must state which evidence remains provisional, who owns the deadline for resolution and which commercial action is prohibited until that evidence becomes current, independently verified and decision-ready.
What to verify before acting
This completed research dossier is not Turkish customs, tax, consumer-law, product-compliance, payments, data-protection, marketplace or legal advice. It does not approve a platform, partner, seller model, shipment or transaction.
Current market intelligence
Signals connected to this dossier
12 October 2026
TIF and BSTDB establish a framework for joint project preparation and financing
Companies and sponsors should prepare a financing-ready project note rather than a generic expression of interest: country and asset, sponsor and ownership, total cost and requested instrument, use of proceeds, revenue and repayment source, permits and land, procurement status, environmental and social position, local delivery model and evidence of additionality. Confirm whether TIF, BSTDB or a financial intermediary is the appropriate first counterpart.
15 October 2026
Türkiye’s services output grows 2.3%, led by information and communication
Digital, logistics, hospitality, property and professional-services firms should compare the official index with customer-specific indicators: buyer revenues and investment, procurement cycles, sector regulation, locations, pricing and channel conditions. Treat the index as a screening signal and validate with named counterparties before committing sales resources.
21 October 2026
Turkic customs authorities back wider eTIR use across regional corridors
Carriers, forwarders, customs-software providers and shippers should map each intended route separately. Confirm whether eTIR is live, the authorised operator and guarantee requirements, vehicle and goods eligibility, pre-declaration process, connected customs offices, document and data responsibilities, border hours, fallback procedures, training and support. Pilot one bounded movement before embedding promised savings in a customer SLA.
Relationship platforms